This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: C++ ABI and ILP64


On Thursday 16 December 2004 13:21, Richard Sandiford wrote:
> "Markus F.X.J. Oberhumer" <markus@oberhumer.com> writes:
> > Currently MIPS (with the -mint64 option) is the only official gcc ILP64
> > target,
>
> I'm not sure from your message whether you're actually interested
> in MIPS or not, but for the record:

The presence of the -mint64 MIPS option was the initial motivation for trying 
the experimental ILP64 port on AMD64, but I'm not actually using MIPS64.

> I don't think MIPS/-mint64 is really an official target.  There's no
> well-defined MIPS ABI that uses 64-bit integers and it's unclear whether
> anyone thought through the consequences of taking an official ABI and
> slapping a 64-bit int onto it.  (I'm talking about the impact on gcc
> internals as well as user expectations here.)
>
> FWIW, EricC and I were wondering about phasing it out...

I'm not trying to advocate ILP64, I'm just showing that is does have some 
usefulness in certain situations.

And it's fine for me if it will get officially removed - still, PR18744 
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18744 shows that the C++ ABI is 
incomplete wrt ILP64 and that we are currently getting an ICE. 

This ABI issue should get addressed IMHO, even it results in explicit 
non-support.

~Markus

-- 
Markus F.X.J. Oberhumer
http://www.oberhumer.com/


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