This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [commit] [testsuite patch] Fix gdb.btrace/tailcall-only.exp errors on x86_64-m32

On 07/20/2016 03:38 PM, Jan Kratochvil wrote:
> On Wed, 20 Jul 2016 16:36:46 +0200, Pedro Alves wrote:
>> Not sure this particular commit, but AFAIK, there's no target
>> triplet for x32, even.
> ->
> x86_64-x32-linux

AFAICS, that "x32" is in the "vendor" part of the triplet, which should
never mean anything for the tools themselves, being a free field to use by
whoever builds the tools, in order to give the binaries a unique
file name (x86_64-x32-linux-gcc, etc.), and for branding, like
x86_64-redhat-linux-gcc.  AFAICS, nothing in config.sub, and the
different configure scripts in binutils-gdb select on *-x32-*.

ISTR that a triplet like x86_64-*-linux-gnux32 or x86_64-*-linux-gnu-x32
was originally proposed, but then the toolchain ended using strictly
multilib flags to select/detect x32.  But, actually, now that I grep, I find
a few hits on "x86_64-*-linux-gnux32", though not many, so it looks like
there's a triplet after all.

Pedro Alves

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]