* any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc?
@ 2002-04-02 20:06 Chris Friesen
2002-04-02 20:14 ` Franz Sirl
2002-04-02 20:22 ` Andrew Bradley
0 siblings, 2 replies; 6+ messages in thread
From: Chris Friesen @ 2002-04-02 20:06 UTC (permalink / raw)
To: linuxppc-dev
We're looking at moving to gcc 3.x for 2.4.18, and are trying to decide what
version to use. It appears that there were some ppc-specific fixes that went in
to 3.1, and I'm not sure if they were ported back to 3.0.
Has anyone had any successes or failures using either of these versions on
2.4.18 on ppc?
Any gotchas?
Thanks,
Chris
PS. Please cc me on replies, as I'm not subscribed to the list at the moment.
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc?
2002-04-02 20:06 any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc? Chris Friesen
@ 2002-04-02 20:14 ` Franz Sirl
2002-04-02 20:30 ` Andrew Bradley
2002-04-02 20:22 ` Andrew Bradley
1 sibling, 1 reply; 6+ messages in thread
From: Franz Sirl @ 2002-04-02 20:14 UTC (permalink / raw)
To: Chris Friesen, linuxppc-dev
On Tuesday 02 April 2002 22:06, Chris Friesen wrote:
> We're looking at moving to gcc 3.x for 2.4.18, and are trying to decide
> what version to use. It appears that there were some ppc-specific fixes
> that went in to 3.1, and I'm not sure if they were ported back to 3.0.
>
> Has anyone had any successes or failures using either of these versions on
> 2.4.18 on ppc?
> Any gotchas?
Both 3.0.4 and the upcoming 3.1 are fine for use with the current PPC 2.4
kernels. There is only one known issue with inlined functions that take and
return 64-bit values, these may lead to extreme stack usage. A fix for this
might go into 3.1pre CVS during the next days.
After this has been decided I'll upload gcc-3.1pre RPMS and announce them.
Franz.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc?
2002-04-02 20:06 any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc? Chris Friesen
2002-04-02 20:14 ` Franz Sirl
@ 2002-04-02 20:22 ` Andrew Bradley
2002-04-02 20:33 ` Franz Sirl
1 sibling, 1 reply; 6+ messages in thread
From: Andrew Bradley @ 2002-04-02 20:22 UTC (permalink / raw)
To: Chris Friesen; +Cc: linuxppc-dev
Hi Chris,
I recently built the 2.4.18+patch kernel (patch details where on
http://www.penguinppc.org/) using "gcc version 2.95.3 20010319 (2.95.4
CVS + prerelease/franzo/20010912)" with out a hitch.
But my main goal is to use g++ 3.x as my default compiler to mimic GCC
3.0.2 on my solaris and linux systems I be using since November.
I tried (http://www.suse.com/~aj/gcc30.html) and found that there seems
to be an intermittent crash with the compiler.
I also tried building many of the snap shots. My last try was
gcc-20020318.
The Intermittent crashes sometimes go a way when I retry.
stage1/xgcc -Bstage1/ -B/usr/local/powerpc-unknown-linux-gnu/bin/ -c
-DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -Wtradi
../../gcc-20020318/gcc/expmed.c: In function `expand_mult':
../../gcc-20020318/gcc/expmed.c:2574: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[2]: *** [expmed.o] Error 1
make[2]: Leaving directory `/root/snap_shot/config/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory `/root/snap_shot/config/gcc'
make: *** [bootstrap] Error 2
I also tried downloading code sourcery's snap shots at
http://www.codesourcery.com/gcc_binary_snapshots.
The gcc-20020318 was incomplete.
Kaoru Fuki said he has "Newer binutils,glibc,gcc from cvs branch"
http://lists.linuxppc.org/linuxppc-user/200203/msg00125.html.
But his ftp seems to be down at:- ftp://sv5.linet.gr.jp/pub/PPC/
I am building on a Suse 7.3 (Mac8500 with G3 upgrade card).
I would appreciate finding other who have successfully built using GCC
3.0 on Apple Hardware. Most people seem to build it with a cross
compiler.
Regards
Andrew
On Tuesday, April 2, 2002, at 09:06 pm, Chris Friesen wrote:
>
> We're looking at moving to gcc 3.x for 2.4.18, and are trying to decide
> what
> version to use. It appears that there were some ppc-specific fixes
> that went in
> to 3.1, and I'm not sure if they were ported back to 3.0.
>
> Has anyone had any successes or failures using either of these versions
> on
> 2.4.18 on ppc?
> Any gotchas?
>
> Thanks,
>
> Chris
>
>
> PS. Please cc me on replies, as I'm not subscribed to the list at the
> moment.
>
>
> --
> Chris Friesen | MailStop: 043/33/F10
> Nortel Networks | work: (613) 765-0557
> 3500 Carling Avenue | fax: (613) 765-2986
> Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
>
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc?
2002-04-02 20:14 ` Franz Sirl
@ 2002-04-02 20:30 ` Andrew Bradley
0 siblings, 0 replies; 6+ messages in thread
From: Andrew Bradley @ 2002-04-02 20:30 UTC (permalink / raw)
To: Franz Sirl; +Cc: Chris Friesen, linuxppc-dev
Hello Franz,
It looks like only me that has this intermittent problem with GCC 3.x.
Building or using.
I have:-
glibc-2.2.4-53
binutils-2.11.90.0.29-14 and tried binutils-2.12
I was wondering whether I was the only one building GCC 3.x on apple
hardware.
What surprises me is that the "gcc version 2.95.3 20010319 (2.95.4CVS +
prerelease/franzo/20010912)"
is stable enough to build a kernel but not gcc 3.x on my system.
Any tips on finding this intermittent problem I have with every GCC 3.x
on my 8500 ?
Regards
Andrew
On Tuesday, April 2, 2002, at 09:14 pm, Franz Sirl wrote:
>
> On Tuesday 02 April 2002 22:06, Chris Friesen wrote:
>> We're looking at moving to gcc 3.x for 2.4.18, and are trying to decide
>> what version to use. It appears that there were some ppc-specific
>> fixes
>> that went in to 3.1, and I'm not sure if they were ported back to 3.0.
>>
>> Has anyone had any successes or failures using either of these
>> versions on
>> 2.4.18 on ppc?
>> Any gotchas?
>
> Both 3.0.4 and the upcoming 3.1 are fine for use with the current PPC
> 2.4
> kernels. There is only one known issue with inlined functions that take
> and
> return 64-bit values, these may lead to extreme stack usage. A fix for
> this
> might go into 3.1pre CVS during the next days.
> After this has been decided I'll upload gcc-3.1pre RPMS and announce
> them.
>
> Franz.
>
>
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc?
2002-04-02 20:22 ` Andrew Bradley
@ 2002-04-02 20:33 ` Franz Sirl
2002-04-02 21:36 ` Andrew Bradley
0 siblings, 1 reply; 6+ messages in thread
From: Franz Sirl @ 2002-04-02 20:33 UTC (permalink / raw)
To: Andrew Bradley, Chris Friesen; +Cc: linuxppc-dev
On Tuesday 02 April 2002 22:22, Andrew Bradley wrote:
> Hi Chris,
>
> I recently built the 2.4.18+patch kernel (patch details where on
> http://www.penguinppc.org/) using "gcc version 2.95.3 20010319 (2.95.4
> CVS + prerelease/franzo/20010912)" with out a hitch.
> But my main goal is to use g++ 3.x as my default compiler to mimic GCC
> 3.0.2 on my solaris and linux systems I be using since November.
> I tried (http://www.suse.com/~aj/gcc30.html) and found that there seems
> to be an intermittent crash with the compiler.
>
> I also tried building many of the snap shots. My last try was
> gcc-20020318.
> The Intermittent crashes sometimes go a way when I retry.
> stage1/xgcc -Bstage1/ -B/usr/local/powerpc-unknown-linux-gnu/bin/ -c
> -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
> -Wmissing-prototypes -Wtradi
> ../../gcc-20020318/gcc/expmed.c: In function `expand_mult':
> ../../gcc-20020318/gcc/expmed.c:2574: internal error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
> make[2]: *** [expmed.o] Error 1
> make[2]: Leaving directory `/root/snap_shot/config/gcc'
> make[1]: *** [stage2_build] Error 2
> make[1]: Leaving directory `/root/snap_shot/config/gcc'
> make: *** [bootstrap] Error 2
Are you sure you don't have any HW problems here? I'm building the compiler
nearly daily on 2 different machines without such problems.
> I also tried downloading code sourcery's snap shots at
> http://www.codesourcery.com/gcc_binary_snapshots.
> The gcc-20020318 was incomplete.
The build machine had some troubles, should be fixed now.
Franz.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc?
2002-04-02 20:33 ` Franz Sirl
@ 2002-04-02 21:36 ` Andrew Bradley
0 siblings, 0 replies; 6+ messages in thread
From: Andrew Bradley @ 2002-04-02 21:36 UTC (permalink / raw)
To: Franz Sirl; +Cc: Chris Friesen, linuxppc-dev
Franz,
I set the switches on my G3 card to the factory processor speed and a
setting lower on the factory cache speed and now the intermittent crash
has disappeared.
Thanks to your voice of reason.
I shall get back to building GCC 3.x and using GCC 3.0.2 to replicate my
work environment.
Regards
Andrew
On Tuesday, April 2, 2002, at 09:33 pm, Franz Sirl wrote:
> On Tuesday 02 April 2002 22:22, Andrew Bradley wrote:
>> Hi Chris,
>>
>> I recently built the 2.4.18+patch kernel (patch details where on
>> http://www.penguinppc.org/) using "gcc version 2.95.3 20010319 (2.95.4
>> CVS + prerelease/franzo/20010912)" with out a hitch.
>> But my main goal is to use g++ 3.x as my default compiler to mimic GCC
>> 3.0.2 on my solaris and linux systems I be using since November.
>> I tried (http://www.suse.com/~aj/gcc30.html) and found that there
>> seems
>> to be an intermittent crash with the compiler.
>>
>> I also tried building many of the snap shots. My last try was
>> gcc-20020318.
>> The Intermittent crashes sometimes go a way when I retry.
>> stage1/xgcc -Bstage1/ -B/usr/local/powerpc-unknown-linux-gnu/bin/ -c
>> -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
>> -Wmissing-prototypes -Wtradi
>> ../../gcc-20020318/gcc/expmed.c: In function `expand_mult':
>> ../../gcc-20020318/gcc/expmed.c:2574: internal error: Segmentation
>> fault
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>> make[2]: *** [expmed.o] Error 1
>> make[2]: Leaving directory `/root/snap_shot/config/gcc'
>> make[1]: *** [stage2_build] Error 2
>> make[1]: Leaving directory `/root/snap_shot/config/gcc'
>> make: *** [bootstrap] Error 2
>
> Are you sure you don't have any HW problems here? I'm building the
> compiler
> nearly daily on 2 different machines without such problems.
>
>> I also tried downloading code sourcery's snap shots at
>> http://www.codesourcery.com/gcc_binary_snapshots.
>> The gcc-20020318 was incomplete.
>
> The build machine had some troubles, should be fixed now.
>
> Franz.
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2002-04-02 21:36 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-04-02 20:06 any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc? Chris Friesen
2002-04-02 20:14 ` Franz Sirl
2002-04-02 20:30 ` Andrew Bradley
2002-04-02 20:22 ` Andrew Bradley
2002-04-02 20:33 ` Franz Sirl
2002-04-02 21:36 ` Andrew Bradley
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).