This is the mail archive of the
mailing list for the GCC project.
Re: libgcc_s, Linux, and PT_GNU_EH_FRAME, and binutils
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Richard Henderson <rth at redhat dot com>, "Martin v. Loewis" <martin at v dot loewis dot de>, Richard Henderson <rth at twiddle dot net>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Tue, 06 Aug 2002 10:03:54 -0700
- Subject: Re: libgcc_s, Linux, and PT_GNU_EH_FRAME, and binutils
I looked into C++ standard and couldn't find anything about
int :64; needing exactly the same treatment as long long :64.
In particular, 2.4.II.1.b.
> Hum. The patch I remember doesn't seem to have been written. :-(
> As discussed on the thread, __m64 needs to be a vector type so
> that the x86-64 calling conventions put it in the right set of
> registers. Which means a large repetitious patch to mmintrin.h.
Well, I'm not too concerned about x86-64 just yet. There still isn't
any hardware out there. I can't see holding the release for this.
Not x86-64, but it makes a difference on i686 too (ie. whether __m64
fields in structures are 64-bit or just 32-bit aligned).
This is a C ABI issue in addition to being a C++ ABI issue.
At some point, we'll break the C ABI to fix this, and with it the C++
ABI -- for programs that use this extended type.
The bottom line is that we don't have a patch. Unless someone is going
to make one PDQ, what are we going to do?
Mark Mitchell firstname.lastname@example.org
CodeSourcery, LLC http://www.codesourcery.com