* Re: egcs-ss-970821 on m68k-next-nextstep3
@ 1997-08-24 3:43 Jeffrey A Law
1997-08-24 3:43 ` New bugs in egcs H.J. Lu
0 siblings, 1 reply; 9+ messages in thread
From: Jeffrey A Law @ 1997-08-24 3:43 UTC (permalink / raw)
To: egcs
In message <9708231749.AA05178@moene.indiv.nluug.nl>you write:
> stage2/xgcc -Bstage2/ -c -DIN_GCC -O -g -O3 -W -Wall -If
> -I./f -I. -I. -I./config f/data.c -o f/data.o
> f/data.c: In function `ffedata_gather_':
> f/data.c:1333: warning: `unexp' might be used uninitialized in this
> function
> xgcc: Internal compiler error: program cc1 got fatal signal 6
>
> i.e. the stage3 compiler (hope I have the stageN numbering right
> now *) can't compile the data.c file in the Fortran language
> directory.
Close :-) the stage2 compiler chokes on data.c during the stage3
build.
I've got a 68k bootstrap running right now; it'll take a _long_
time to finish, but hopefully it'll enable me to track down some
of your problems (assuming they're generic 68k bugs).
Jeff
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: New bugs in egcs
1997-08-24 3:43 egcs-ss-970821 on m68k-next-nextstep3 Jeffrey A Law
@ 1997-08-24 3:43 ` H.J. Lu
0 siblings, 0 replies; 9+ messages in thread
From: H.J. Lu @ 1997-08-24 3:43 UTC (permalink / raw)
To: egcs
>
>
> In message <m0x2JoO-0004ecC@ocean.lucon.org>you write:
> > Hi,
> >
> > Those extra failures don't exist in my gcc2 ss-970802.
> So, after re-building gcc with jfc's patch, then re-running the
> testsuite, how many of these new failures remain?
>
> Jeff
>
>
>
Here is the partial list. Somehow egcs screws up the real constant
numbers when the compiler is compiled with -O6 -g. I am looking into
it. I may not be able to find time before next weekend.
Also, that cp/tree.c change bug I reported earlier still exists,
although it is also in gcc2 ss-970802.
I also reported/fixed a few bugs and I have sent my patches to
gcc2. Should I resend them to egcs? My patches may look ugly. But
the bugs are real.
H.J.
--
H.J. Lu (hjl@gnu.ai.mit.edu)
---
ERROR: execute/cvt-1.c: compiled program got signal 6: -O3 -fno-omit-frame-pointer -pipe
ERROR: execute/cvt-1.c: compiled program got signal 6: -O3 -fomit-frame-pointer -pipe
ERROR: execute/cvt-1.c: compiled program got signal 6: -O3 -funroll-all-loops -pipe
ERROR: execute/conversion.c: compiled program got signal 6: -O3 -fno-omit-frame-pointer -pipe
ERROR: execute/conversion.c: compiled program got signal 6: -O3 -fomit-frame-pointer -pipe
ERROR: execute/conversion.c: compiled program got signal 6: -O3 -funroll-all-loops -pipe
ERROR: execute/cvt-1.c: compiled program got signal 6: -O3 -fno-omit-frame-pointer -fpic -pipe
ERROR: execute/cvt-1.c: compiled program got signal 6: -O3 -fomit-frame-pointer -fpic -pipe
ERROR: execute/cvt-1.c: compiled program got signal 6: -O3 -funroll-all-loops -fpic -pipe
ERROR: execute/conversion.c: compiled program got signal 6: -O3 -fno-omit-frame-pointer -fpic -pipe
ERROR: execute/conversion.c: compiled program got signal 6: -O3 -fomit-frame-pointer -fpic -pipe
ERROR: execute/conversion.c: compiled program got signal 6: -O3 -funroll-all-loops -fpic -pipe
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: New bugs in egcs
1997-08-24 23:47 H.J. Lu
@ 1997-08-25 1:40 ` Jeffrey A Law
0 siblings, 0 replies; 9+ messages in thread
From: Jeffrey A Law @ 1997-08-25 1:40 UTC (permalink / raw)
To: egcs
In message <m0x2mUF-0004ecC@ocean.lucon.org>you write:
> But I was told that it was not a bug while I am keeping getting it. I
> am afraid that egcs may be released with that cp/tree.c bug, which may
> be specific to x86.
Ummm, what I remember reading was that your _patch_ was incorrect;
I don't think Jason (or anyone) said that it was not a bug. He
asked you to verify that the bug still exists after the next snapshot.
Please do that with tonight's snapshot using the libstdc++ included
therein (no, I haven't made the snapshot yet, but the plan is to
get it done before I go to sleep tongiht).
jeff
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: New bugs in egcs
@ 1997-08-24 23:47 Jim Wilson
0 siblings, 0 replies; 9+ messages in thread
From: Jim Wilson @ 1997-08-24 23:47 UTC (permalink / raw)
To: egcs
Great. Now only if I can compile libg++ with egcs. Is someone
working on that cp/tree.c bug I reported?
I am looking into all bugs that have been reported (excepting C++ ones out
of my area of expertise). Please be patient, and I will get to it as soon
as I can.
Jim
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: New bugs in egcs
@ 1997-08-24 23:47 H.J. Lu
1997-08-25 1:40 ` Jeffrey A Law
0 siblings, 1 reply; 9+ messages in thread
From: H.J. Lu @ 1997-08-24 23:47 UTC (permalink / raw)
To: egcs
>
> Great. Now only if I can compile libg++ with egcs. Is someone
> working on that cp/tree.c bug I reported?
>
> I am looking into all bugs that have been reported (excepting C++ ones out
Thanks.
> of my area of expertise). Please be patient, and I will get to it as soon
> as I can.
>
But I was told that it was not a bug while I am keeping getting it. I
am afraid that egcs may be released with that cp/tree.c bug, which may
be specific to x86.
--
H.J. Lu (hjl@gnu.ai.mit.edu)
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: New bugs in egcs
@ 1997-08-24 12:16 H.J. Lu
0 siblings, 0 replies; 9+ messages in thread
From: H.J. Lu @ 1997-08-24 12:16 UTC (permalink / raw)
To: egcs
>
> Those extra failures don't exist in my gcc2 ss-970802.
>
> These problems all go away with my alias.c patch and jfc's unroll.c patch
> applied.
>
> I get exactly the same c-torture results for egcs and gcc2, with egcs
> bootstrapped using -O6 -g.
>
Great. Now only if I can compile libg++ with egcs. Is someone
working on that cp/tree.c bug I reported?
--
H.J. Lu (hjl@gnu.ai.mit.edu)
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: New bugs in egcs
@ 1997-08-24 6:02 Jim Wilson
0 siblings, 0 replies; 9+ messages in thread
From: Jim Wilson @ 1997-08-24 6:02 UTC (permalink / raw)
To: egcs
Those extra failures don't exist in my gcc2 ss-970802.
These problems all go away with my alias.c patch and jfc's unroll.c patch
applied.
I get exactly the same c-torture results for egcs and gcc2, with egcs
bootstrapped using -O6 -g.
Jim
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: New bugs in egcs
1997-08-24 3:43 This can't be right Jeffrey A Law
@ 1997-08-24 3:43 ` Jeffrey A Law
0 siblings, 0 replies; 9+ messages in thread
From: Jeffrey A Law @ 1997-08-24 3:43 UTC (permalink / raw)
To: egcs
In message <m0x2JoO-0004ecC@ocean.lucon.org>you write:
> Hi,
>
> Those extra failures don't exist in my gcc2 ss-970802.
So, after re-building gcc with jfc's patch, then re-running the
testsuite, how many of these new failures remain?
Jeff
^ permalink raw reply [flat|nested] 9+ messages in thread
* New bugs in egcs
1997-08-23 17:08 egcs-ss-970821 - Run-Time Library Cross Problems Joel Sherrill
@ 1997-08-23 17:08 ` H.J. Lu
0 siblings, 0 replies; 9+ messages in thread
From: H.J. Lu @ 1997-08-23 17:08 UTC (permalink / raw)
To: egcs
Hi,
Those extra failures don't exist in my gcc2 ss-970802.
--
H.J. Lu (hjl@gnu.ai.mit.edu)
--
ERROR: execute/cvt-1.c: compiled program got signal 6: -O3 -fno-omit-frame-pointer -pipe
ERROR: execute/cvt-1.c: compiled program got signal 6: -O3 -fomit-frame-pointer -pipe
ERROR: execute/cvt-1.c: compiled program got signal 6: -O3 -funroll-all-loops -pipe
ERROR: execute/conversion.c: compiled program got signal 6: -O3 -fno-omit-frame-pointer -pipe
ERROR: execute/conversion.c: compiled program got signal 6: -O3 -fomit-frame-pointer -pipe
ERROR: execute/conversion.c: compiled program got signal 6: -O3 -funroll-all-loops -pipe
ERROR: execute/920625-1.c: compiled program got signal 6: -O3 -funroll-all-loops -pipe
ERROR: 970731-1/runit: shell script returned error status: -O2 -fno-omit-frame-pointer -pipe
ERROR: 970731-1/runit: shell script returned error status: -O3 -fno-omit-frame-pointer -pipe
ERROR: 970731-1/runit: shell script returned error status: -O3 -funroll-all-loops -pipe
ERROR: execute/cvt-1.c: compiled program got signal 6: -O3 -fno-omit-frame-pointer -fpic -pipe
ERROR: execute/cvt-1.c: compiled program got signal 6: -O3 -fomit-frame-pointer -fpic -pipe
ERROR: execute/cvt-1.c: compiled program got signal 6: -O3 -funroll-all-loops -fpic -pipe
ERROR: execute/conversion.c: compiled program got signal 6: -O3 -fno-omit-frame-pointer -fpic -pipe
ERROR: execute/conversion.c: compiled program got signal 6: -O3 -fomit-frame-pointer -fpic -pipe
ERROR: execute/conversion.c: compiled program got signal 6: -O3 -funroll-all-loops -fpic -pipe
ERROR: execute/920625-1.c: compiled program got signal 6: -O3 -funroll-all-loops -fpic -pipe
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~1997-08-25 1:40 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1997-08-24 3:43 egcs-ss-970821 on m68k-next-nextstep3 Jeffrey A Law
1997-08-24 3:43 ` New bugs in egcs H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
1997-08-24 23:47 Jim Wilson
1997-08-24 23:47 H.J. Lu
1997-08-25 1:40 ` Jeffrey A Law
1997-08-24 12:16 H.J. Lu
1997-08-24 6:02 Jim Wilson
1997-08-24 3:43 This can't be right Jeffrey A Law
1997-08-24 3:43 ` New bugs in egcs Jeffrey A Law
1997-08-23 17:08 egcs-ss-970821 - Run-Time Library Cross Problems Joel Sherrill
1997-08-23 17:08 ` New bugs in egcs H.J. Lu
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 read-only IMAP folder(s) and NNTP newsgroup(s).