Hi!
What's the reason why ppc-linux and s390-linux targetted GCC
requires 64-bit HWI these days?
If it is a native compiler, this means using long long in a huge part
of the compiler and therefore slower compile times and bigger memory
consumption.
ppc-linux configured compiler (nor s390-linux) is
>
> Hi!
>
> What's the reason why ppc-linux and s390-linux targetted GCC
> requires 64-bit HWI these days?
> If it is a native compiler, this means using long long in a huge part
> of the compiler and therefore slower compile times and bigger memory
> consumption.
powerpc-linux supports -mpowerp
On Sat, Nov 26, 2005 at 03:38:18AM -0500, Jakub Jelinek wrote:
> What's the reason why ppc-linux and s390-linux targetted GCC
> requires 64-bit HWI these days?
Be careful with ppc; altivec may need hwi 64bit.
r~
On Nov 22, 2005, at 7:52 AM, Richard Earnshaw wrote:
3) A volatile load isn't moved across any store that may alias (though
I'd expect that to be volatile if there's a real risk of aliasning, so
maybe we could have another dimension in the 'may-alias' test here).
? Is this just a restatement o
On Nov 22, 2005, at 8:10 AM, Robert Dewar wrote:
I think this is a bad idea in practice, since volatile will be used
to describe memory mapped devices, and combining can completely
mess up the access.
Only if one missed a restriction.
On Nov 25, 2005, at 9:49 AM, Michael Garvin wrote:
I would like to jump in and start contributing,
Welcome aboard.
but I'm wondering if I need to create a designer account anywhere,
or join the project electronicly?
Things you need to do, file paper work if you want to contribute
anythin
On Nov 23, 2005, at 10:30 AM, Diego Novillo wrote:
I'll keep an eye on the apple branch. Will gfortran work on the
branch?
I generally like to keep Java and Fortran working on it. For moments
in time, it can have various breakages, though, they tend to be
obvious/trivial to fix. For som
