This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 5/6] Do not use explicit abort code definitions.
- From: Andi Kleen <andi at firstfloor dot org>
- To: libc-alpha at sourceware dot org
- Date: Mon, 02 Sep 2013 14:02:38 -0700
- Subject: Re: [PATCH 5/6] Do not use explicit abort code definitions.
- Authentication-results: sourceware.org; auth=none
- References: <20130902075228 dot GA4792 at linux dot vnet dot ibm dot com> <20130902081209 dot GE4997 at linux dot vnet dot ibm dot com>
Dominik Vogt <vogt@linux.vnet.ibm.com> writes:
> Using explicit abort code definitions is problematic because they are thrown at
> the creator of the outermost transaction who may misinterpret the user
> specified abort code because he does not know where it comes from.
>
> The lock elision implementation should refrain from using explicit abort code
> definitions and rather only interpret the flags of the abort code (as should
> other pieces of software that have abort handlers).
Nack nack.
This is used for profiling.
Overall the change doesn't make any sense at all for TSX.
-Andi
--
ak@linux.intel.com -- Speaking for myself only