* Re: g77.f-torture/execute/alpha1.f is strange
@ 1997-11-04 7:26 Kate Hedstrom
1997-11-04 11:12 ` Dave Love
0 siblings, 1 reply; 12+ messages in thread
From: Kate Hedstrom @ 1997-11-04 7:26 UTC (permalink / raw)
To: d.love, egcs
> Toon> This code will only complete normally by chance, so I think it
> Toon> needs updating.
>
> Yes. I didn't understand what it was about when I looked at this
> stuff; I think it appeared to be testing for a compiler abort and
> looked as though it might be in the wrong directory, though I don't
> understand the testing stuff. I also didn't recognize some of the
> other things there, but anyway, could regression tests be commented
> with an indication of the problem and fix made?
Sure they could be commented, although all I have is some code snippets
which once failed and no indication of what was wrong or what was
fixed.
> Is Kate C-in-C this stuff if I extract more test cases from the bug
> archives now I can get at them again?
As far as I know I still am, although I have to admit that I've been
working on other things lately. You can take over if you think that
makes more sense.
Kate
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: g77.f-torture/execute/alpha1.f is strange
1997-11-04 7:26 g77.f-torture/execute/alpha1.f is strange Kate Hedstrom
@ 1997-11-04 11:12 ` Dave Love
0 siblings, 0 replies; 12+ messages in thread
From: Dave Love @ 1997-11-04 11:12 UTC (permalink / raw)
To: egcs
>>>>> "Kate" == Kate Hedstrom <kate@imcs.rutgers.edu> writes:
Kate> You can take over if you think that makes more sense.
I don't know dejagnu. (Doubtless a poor reflexion...)
[I can't currently read the g77 mail archives as I thought I could.]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: g77.f-torture/execute/alpha1.f is strange
1997-11-04 15:19 ` Jeffrey A Law
@ 1997-11-09 15:48 ` Craig Burley
0 siblings, 0 replies; 12+ messages in thread
From: Craig Burley @ 1997-11-09 15:48 UTC (permalink / raw)
To: egcs
>ok ok ok :-) I'll take out the initialization and move the test..
That restores the test to its original status, but its status
as "executable" also is preserved by compiling it with
"-finit-local-zero", which might be useful as well, though
in this case not involving a past bug-fix I'm aware of
(though, if the test had any local variables of COMPLEX type,
it would ;-).
(This is an example of why I'm not thrilled with categorizing
the *source* code of a test based on its *uses*, since the
use can straddle categories...I think of uses as attributes,
perhaps, I guess. But that's not worth discussing right now.)
tq vm, (burley)
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: g77.f-torture/execute/alpha1.f is strange
1997-11-03 16:02 ` Toon Moene
@ 1997-11-04 15:19 ` Jeffrey A Law
1997-11-09 15:48 ` Craig Burley
0 siblings, 1 reply; 12+ messages in thread
From: Jeffrey A Law @ 1997-11-04 15:19 UTC (permalink / raw)
To: Toon Moene; +Cc: egcs
In message < 9711032343.AA10247@moene.indiv.nluug.nl >you write:
> Jeff wrote:
>
> > Thanks. Yes, the initialization needs to be explicit.
> > I've updated the test.
>
> OTOH, it might simply be that Dave Love was right (which seems to
> be supported by the comment in the code) that this was a *compiler*
> crash, and that it therefore should reside in the `compile'
> directory and not the `execute' directory.
ok ok ok :-) I'll take out the initialization and move the test..
jeff
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: g77.f-torture/execute/alpha1.f is strange
1997-11-03 16:02 ` Jeffrey A Law
@ 1997-11-04 15:02 ` Dave Love
0 siblings, 0 replies; 12+ messages in thread
From: Dave Love @ 1997-11-04 15:02 UTC (permalink / raw)
To: egcs
>>>>> "Jeffrey" == Jeffrey A Law <law@cygnus.com> writes:
>> Hmmm, since the compiler aborted, I think the orifinal test should
>> be copied
Jeffrey> It could be, but I'm not planning on it.
It sounds as though the test is then useless, though I can't prove my
suspicion about what the bug was. FWIW, I got the original alpha-test
report from 1996-12-01 (thanks, nemo).
--------------
Well, I have a new one and I'll repeat the last one...
both these code segments compile fine under g77 linux, but
cause Internal compiler errors on the Alpha.
[...]
=================================================
REAL*8 A,B,C
REAL*4 RARRAY(19)/19*(-1)/
INTEGER BOTTOM,RIGHT
INTEGER IARRAY(19)/0,0,0,0,0,0,0,0,0,0,0,0,13,14,0,0,0,0,0/
EQUIVALENCE (RARRAY(13),BOTTOM),(RARRAY(14),RIGHT)
C
IF(I.NE.0) STOP
C gcc: Internal compiler error: program f771 got fatal signal 11
C at this point!
END
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: g77.f-torture/execute/alpha1.f is strange
1997-11-03 16:02 ` Joern Rennecke
@ 1997-11-03 16:02 ` Jeffrey A Law
1997-11-04 15:02 ` Dave Love
0 siblings, 1 reply; 12+ messages in thread
From: Jeffrey A Law @ 1997-11-03 16:02 UTC (permalink / raw)
To: Joern Rennecke; +Cc: hjl, egcs
In message < 199711031846.SAA03155@phal.cygnus.co.uk >you write:
> > Thanks. Yes, the initialization needs to be explicit. I've
> > updatedthe test.
>
> Hmmm, since the compiler aborted, I think the orifinal test should
> be copied
It could be, but I'm not planning on it.
jeff
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: g77.f-torture/execute/alpha1.f is strange
1997-11-02 22:12 ` Jeffrey A Law
1997-11-03 16:02 ` Joern Rennecke
@ 1997-11-03 16:02 ` Toon Moene
1997-11-04 15:19 ` Jeffrey A Law
1 sibling, 1 reply; 12+ messages in thread
From: Toon Moene @ 1997-11-03 16:02 UTC (permalink / raw)
To: law; +Cc: egcs
Jeff wrote:
> Thanks. Yes, the initialization needs to be explicit.
> I've updated the test.
OTOH, it might simply be that Dave Love was right (which seems to
be supported by the comment in the code) that this was a *compiler*
crash, and that it therefore should reside in the `compile'
directory and not the `execute' directory.
HTH,
Toon.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: g77.f-torture/execute/alpha1.f is strange
1997-11-02 22:12 ` Jeffrey A Law
@ 1997-11-03 16:02 ` Joern Rennecke
1997-11-03 16:02 ` Jeffrey A Law
1997-11-03 16:02 ` Toon Moene
1 sibling, 1 reply; 12+ messages in thread
From: Joern Rennecke @ 1997-11-03 16:02 UTC (permalink / raw)
To: law; +Cc: hjl, egcs
> Thanks. Yes, the initialization needs to be explicit. I've updated
> the test.
Hmmm, since the compiler aborted, I think the orifinal test should be copied
into the compile or noncompile directory (depending on whatever that fortran
language says should happen when you try to compile this code)
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: g77.f-torture/execute/alpha1.f is strange
1997-11-01 19:02 H.J. Lu
1997-11-02 3:14 ` Toon Moene
@ 1997-11-02 22:12 ` Jeffrey A Law
1997-11-03 16:02 ` Joern Rennecke
1997-11-03 16:02 ` Toon Moene
1 sibling, 2 replies; 12+ messages in thread
From: Jeffrey A Law @ 1997-11-02 22:12 UTC (permalink / raw)
To: H.J. Lu; +Cc: egcs
In message < m0xRqJB-0004ecC@ocean.lucon.org >you write:
> Here is g77.f-torture/execute/alpha1.f. It may call exit (1) if I
> doesn't happen to be 0. I don't remember what Fortran should be in
> this case. I think I is default to INTEGER. But I don't know if
> it should be initialized to 0. From the x86 asm code, gcc doesn't
> initialize it at all. In any case, I got the exit value 1 on
> linux/x86/glibc 2 and linux/alpha/glibc 2.0.5c.
Thanks. Yes, the initialization needs to be explicit. I've updated
the test.
jeff
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: g77.f-torture/execute/alpha1.f is strange
1997-11-02 3:14 ` Toon Moene
@ 1997-11-02 7:20 ` Dave Love
0 siblings, 0 replies; 12+ messages in thread
From: Dave Love @ 1997-11-02 7:20 UTC (permalink / raw)
To: egcs
>>>>> "Toon" == Toon Moene <toon@moene.indiv.nluug.nl> writes:
Toon> This code will only complete normally by chance, so I think it
Toon> needs updating.
Yes. I didn't understand what it was about when I looked at this
stuff; I think it appeared to be testing for a compiler abort and
looked as though it might be in the wrong directory, though I don't
understand the testing stuff. I also didn't recognize some of the
other things there, but anyway, could regression tests be commented
with an indication of the problem and fix made?
Is Kate C-in-C this stuff if I extract more test cases from the bug
archives now I can get at them again?
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: g77.f-torture/execute/alpha1.f is strange
1997-11-01 19:02 H.J. Lu
@ 1997-11-02 3:14 ` Toon Moene
1997-11-02 7:20 ` Dave Love
1997-11-02 22:12 ` Jeffrey A Law
1 sibling, 1 reply; 12+ messages in thread
From: Toon Moene @ 1997-11-02 3:14 UTC (permalink / raw)
To: H.J. Lu; +Cc: egcs
> Here is g77.f-torture/execute/alpha1.f. It may call exit
> (1) if I doesn't happen to be 0. I don't remember what
> Fortran should be in this case. I think I is default to
> INTEGER. But I don't know if it should be initialized to
> 0. From the x86 asm code, gcc doesn't initialize it at
> all. In any case, I got the exit value 1 on
> linux/x86/glibc 2 and linux/alpha/glibc 2.0.5c.
>
>
> -- H.J. Lu (hjl@gnu.ai.mit.edu)
> ---g77.f-torture/execute/alpha1.f---
> REAL*8 A,B,C
> REAL*4 RARRAY(19)/19*(-1)/
> INTEGER BOTTOM,RIGHT
> INTEGER IARRAY(19)/0,0,0,0,0,0,0,0,0,0,0,0,13,14,0,0,0,0,0/
> EQUIVALENCE (RARRAY(13),BOTTOM),(RARRAY(14),RIGHT)
> C
> IF(I.NE.0) call exit(1)
>C gcc: Internal compiler error: program f771 got fatal signal 11
>C at this point!
> END
Yep, just using a variable I without initialising it is a deadly
sin - you might be glad g77 didn't start WW III on it - as per the
comp.lang.fortran FAQ. Probably the right optional hardware wasn't
installed ?
This code will only complete normally by chance, so I think it
needs updating.
Toon.
^ permalink raw reply [flat|nested] 12+ messages in thread
* g77.f-torture/execute/alpha1.f is strange
@ 1997-11-01 19:02 H.J. Lu
1997-11-02 3:14 ` Toon Moene
1997-11-02 22:12 ` Jeffrey A Law
0 siblings, 2 replies; 12+ messages in thread
From: H.J. Lu @ 1997-11-01 19:02 UTC (permalink / raw)
To: egcs
Here is g77.f-torture/execute/alpha1.f. It may call exit (1) if I
doesn't happen to be 0. I don't remember what Fortran should be in
this case. I think I is default to INTEGER. But I don't know if
it should be initialized to 0. From the x86 asm code, gcc doesn't
initialize it at all. In any case, I got the exit value 1 on
linux/x86/glibc 2 and linux/alpha/glibc 2.0.5c.
--
H.J. Lu (hjl@gnu.ai.mit.edu)
---g77.f-torture/execute/alpha1.f---
REAL*8 A,B,C
REAL*4 RARRAY(19)/19*(-1)/
INTEGER BOTTOM,RIGHT
INTEGER IARRAY(19)/0,0,0,0,0,0,0,0,0,0,0,0,13,14,0,0,0,0,0/
EQUIVALENCE (RARRAY(13),BOTTOM),(RARRAY(14),RIGHT)
C
IF(I.NE.0) call exit(1)
C gcc: Internal compiler error: program f771 got fatal signal 11
C at this point!
END
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~1997-11-09 15:48 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1997-11-04 7:26 g77.f-torture/execute/alpha1.f is strange Kate Hedstrom
1997-11-04 11:12 ` Dave Love
-- strict thread matches above, loose matches on Subject: below --
1997-11-01 19:02 H.J. Lu
1997-11-02 3:14 ` Toon Moene
1997-11-02 7:20 ` Dave Love
1997-11-02 22:12 ` Jeffrey A Law
1997-11-03 16:02 ` Joern Rennecke
1997-11-03 16:02 ` Jeffrey A Law
1997-11-04 15:02 ` Dave Love
1997-11-03 16:02 ` Toon Moene
1997-11-04 15:19 ` Jeffrey A Law
1997-11-09 15:48 ` Craig Burley
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).