This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Support for Intel X1000
- From: "Kinsella, Ray" <ray dot kinsella at intel dot com>
- To: "dalias at libc dot org" <dalias at libc dot org>
- Cc: "carlos at redhat dot com" <carlos at redhat dot com>, "fweimer at redhat dot com" <fweimer at redhat dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Thu, 14 May 2015 08:58:32 +0000
- Subject: Re: Support for Intel X1000
- Authentication-results: sourceware.org; auth=none
- References: <1431426490 dot 3246 dot 29 dot camel at intel dot com> <5552104C dot 1020806 at redhat dot com> <20150512152207 dot GW17573 at brightrain dot aerifal dot cx> <1431513937 dot 2622 dot 24 dot camel at intel dot com> <20150513170809 dot GY17573 at brightrain dot aerifal dot cx>
On Wed, 2015-05-13 at 13:08 -0400, dalias@libc.org wrote:
> I think it's rather dangerous to produce such binaries -- someone
> might compile on such a hacked distro and move the binary to a
> different system, unaware of the issues. If anyone is seriously
> considering this approach, I think there needs to be some way of
> tagging the binaries to make sure this can't happen.
Understood
> it would make a lot more sense to put the hack that
> NOPs out the lock prefix into the assembler. Then you can just build
> all programs with the hacked binutils and get working binaries.
Seems to be most straight forward way to avoid modifying code
everywhere, at the expense of portability.
Ray K