public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/96023] New: Line number for error message differs for x86-64 vs all other architectures
@ 2020-07-01 17:47 dje at gcc dot gnu.org
2020-07-01 17:47 ` [Bug fortran/96023] " dje at gcc dot gnu.org
2020-07-02 6:42 ` rguenth at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: dje at gcc dot gnu.org @ 2020-07-01 17:47 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96023
Bug ID: 96023
Summary: Line number for error message differs for x86-64 vs
all other architectures
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: dje at gcc dot gnu.org
Target Milestone: ---
I don't know how this is possible, but the line number associated with the
error message for gfortran.dg/pr95690.f90 is different for x86-64 than for all
other architectures.
As seen by the lack of failures in x86-64 testsuite reports, the test succeeds
on that target. Manually running the testcase on x86-64 (gcc67) elicits:
pr95690.f90:5:0:
5 | print *, (erfc) ! { dg-error "not a floating constant" }
|
Error: initializer for floating value is not a floating constant
Running the testcase on powerpc64le-linux, powerpc-ibm-aix, s390x-linux,
aarch64-linux, etc. elicits:
pr95690.f90:6:0:
6 | end
|
Error: initializer for floating value is not a floating constant
Same error message associated with a different line.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug fortran/96023] Line number for error message differs for x86-64 vs all other architectures
2020-07-01 17:47 [Bug fortran/96023] New: Line number for error message differs for x86-64 vs all other architectures dje at gcc dot gnu.org
@ 2020-07-01 17:47 ` dje at gcc dot gnu.org
2020-07-02 6:42 ` rguenth at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: dje at gcc dot gnu.org @ 2020-07-01 17:47 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96023
David Edelsohn <dje at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2020-07-01
Status|UNCONFIRMED |NEW
--- Comment #1 from David Edelsohn <dje at gcc dot gnu.org> ---
Confirmed.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug fortran/96023] Line number for error message differs for x86-64 vs all other architectures
2020-07-01 17:47 [Bug fortran/96023] New: Line number for error message differs for x86-64 vs all other architectures dje at gcc dot gnu.org
2020-07-01 17:47 ` [Bug fortran/96023] " dje at gcc dot gnu.org
@ 2020-07-02 6:42 ` rguenth at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: rguenth at gcc dot gnu.org @ 2020-07-02 6:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96023
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Duplicate.
*** This bug has been marked as a duplicate of bug 95706 ***
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-07-02 6:42 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-01 17:47 [Bug fortran/96023] New: Line number for error message differs for x86-64 vs all other architectures dje at gcc dot gnu.org
2020-07-01 17:47 ` [Bug fortran/96023] " dje at gcc dot gnu.org
2020-07-02 6:42 ` rguenth at gcc dot gnu.org
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).