Re: [jamboost] mipspro-tools.jam file

From: Dan Gohman (gohmandj_at_[hidden])
Date: 2002-06-11 15:56:33

On Tue, Jun 11, 2002 at 03:33:10PM -0500, Rene Rivera wrote:
> On 2002-06-11 at 03:14 PM, gohmandj_at_[hidden] (Dan Gohman) wrote:
> 
> >On Mon, Jun 10, 2002 at 02:20:03PM -0500, Rene Rivera wrote:
> >> On 2002-06-10 at 01:54 PM, gohmandj_at_[hidden] (Dan Gohman) wrote:
> >> >I'm thinking about suggesting something like this:
> >> >
> >> > feature integer-model : unspecified ilp32 lp64 ; # add others as
> needed
> >> 
> >> Good name! It's specific enough that other options that also affect the
> ABI
> >> on other platforms don't collide :-)
> >> 
> >> Question, though... What does "ilp" and "lp" stand for?
> >
> >i, l, and p stand for int, long, and pointer. It really isn't that useful
> >to be able to specify the size of `int' or `long' (as long as
> ><boost/cstdint.hpp> works :-)), but being able to specify the pointer
> >size is very useful.
> >
> >Maybe the feature would be more appropriately be named `pointer-size'.
> >
> > # This feature specifies the pointer size in bits.
> > feature pointer-size : unspecified 16 32 64 ;
> >
> >Optionally, `default' might look better than `unspecified' in everyone's
> >build directories. How does that sound?
> 
> I'm on my way back to confusion...
> 
> What is it that the n64/32 specify for the mips compiler? pointer, integer,
> register, or float size?

For our purposes, it specifies long and pointer sizes. Of these, long's
size isn't very important because there are ways of getting a 64-bit
integer type in both (so typedefs like int64_t are always possible).

Being able to specify the pointer size is important though, because some
hardware platforms don't support n64, while using n64 on the ones that
support it means being able to address more than 2 G of memory.

Dan

-- 
Dan Gohman
gohmandj_at_[hidden]