This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: enable maximum integer type to be 128 bits
- From: "Jan Beulich" <JBeulich at novell dot com>
- To: <jsm at polyomino dot org dot uk>
- Cc: <zack at codesourcery dot com>,<gcc-patches at gcc dot gnu dot org>
- Date: Wed, 07 Jul 2004 11:40:28 +0200
- Subject: Re: enable maximum integer type to be 128 bits
But this isn't intended for just a single target architecture. Any
64-bit one can benefit from this. If a command line option is more
suitable, then if at all this ought to be a common one. But then again
restricting it to intmax_t would seem odd; all other built-in types
could then be modifiable as easily. This, however, would perhaps require
the whole current scheme of setting up these types to be changed (i.e.
the target headers would then only specifiy the defaults for all of
them), and it would also make pointless the -fshort-wchar option. Is
this really the way to go?
Thanks, Jan
>>> "Joseph S. Myers" <jsm@polyomino.org.uk> 07.07.04 11:13:47 >>>
On Wed, 7 Jul 2004, Jan Beulich wrote:
> the compiler being able support this (which is why I made this a
> configure option rather than something each target would have to
> introduce by itself, allowing this to be easily turned own for
> experimenting). Of course, I'd like to learn what alternatives you
> see...
ABI-changing options to vary the size of long double on x86 have been
implemented as -m options to the compiler rather than configure
options.
Naturally implementing and documenting such an option, with similar
warnings about ABI changes, makes experimentation more convenient than
a
configure-time option.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)