This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: fix for 64bit uncleanliness in cp/class.c
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Subject: Re: fix for 64bit uncleanliness in cp/class.c
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Sat, 22 Jan 2000 23:57:17 -0700
- cc: rth at cygnus dot com, gcc-patches at gcc dot gnu dot org, geoffk at cygnus dot com, lucier at math dot purdue dot edu
- Reply-To: law at cygnus dot com
In message <200001222013.PAA12774@caip.rutgers.edu>you write:
> > The problem being that we don't have arbitrary size integer support,
> > only enough for two host integers. So in supporting cross compiles
> > from a 32-bit host to a 64-bit target that has a 128-bit integer type,
> > we need the host to use 64-bit integers as well.
>
>
> Okay I stand corrected. I'm still pretty sure Jeff nixed
> generically making HOST_WIDE_INT a long long because of a slowdown he
> saw (7%?) on x86. (Darned search engine, can't find the URL. Help!)
> But it seems like you are talking about very narrow cases here in
> which it happens only when specifically needed.
Richard is talking about specific host/target combos where we need to have a
64bit HOST_WIDE_INT (consider if you want to be able to deal with TImode
constants).
Such ports are rare (possibly none in the official GCC sources), but they do
exist.
jeff