public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manfred99 at gmx dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95090] ICE: identifier overflow: 129
Date: Thu, 28 May 2020 08:39:24 +0000 [thread overview]
Message-ID: <bug-95090-4-KjFNwSjb45@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95090-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95090
Manfred Schwarb <manfred99 at gmx dot ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manfred99 at gmx dot ch
--- Comment #4 from Manfred Schwarb <manfred99 at gmx dot ch> ---
This breaks for me in i686, see
http://gfortran.meteodat.ch/download/i686/nightlies/gcc-trunk-20200528-gfe7ebef7fe4f9acb79658ed9db0749b07efc3105-README.txt
See also HJ's test in
https://gcc.gnu.org/pipermail/gcc-testresults/2020-May/562121.html
x86_64 seems is OK. Error message is not really revealing:
Executing on host:
/tmp/gcc-trunk-32bit-build/gcc/testsuite/gfortran2/../../gfortran
-B/tmp/gcc-trunk-32bit-build/gcc/testsuite/gfortran2/../../
-B/tmp/gcc-trunk-32bit-build/i686-linux/./libgfortran/
/tmp/gcc-trunk-source/gcc/gcc/testsuite/gfortran.dg/pr95090.f90
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -O -fcoarray=lib
-fsecond-underscore -S -o pr95090.s (timeout = 300)
spawn -ignore SIGHUP
/tmp/gcc-trunk-32bit-build/gcc/testsuite/gfortran2/../../gfortran
-B/tmp/gcc-trunk-32bit-build/gcc/testsuite/gfortran2/../../
-B/tmp/gcc-trunk-32bit-build/i686-linux/./libgfortran/
/tmp/gcc-trunk-source/gcc/gcc/testsuite/gfortran.dg/pr95090.f90
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -fno-diagnostics-show-caret
-fno-diagnostics-show-line-numbers -fdiagnostics-color=never
-fdiagnostics-urls=never -O -fcoarray=lib -fsecond-underscore -S -o pr95090.s
f951: internal compiler error: Segmentation fault
0x83cf0ac ???
../sysdeps/i386/start.S:117
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
compiler exited with status 1
FAIL: gfortran.dg/pr95090.f90 -O (internal compiler error)
next prev parent reply other threads:[~2020-05-28 8:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 16:43 [Bug fortran/95090] New: " gscfq@t-online.de
2020-05-26 21:04 ` [Bug fortran/95090] " anlauf at gcc dot gnu.org
2020-05-27 19:20 ` cvs-commit at gcc dot gnu.org
2020-05-27 19:22 ` anlauf at gcc dot gnu.org
2020-05-28 8:39 ` manfred99 at gmx dot ch [this message]
2020-05-28 9:31 ` manfred99 at gmx dot ch
2020-05-28 17:26 ` anlauf at gcc dot gnu.org
2020-05-28 18:50 ` anlauf at gcc dot gnu.org
2020-05-28 23:36 ` manfred99 at gmx dot ch
2020-05-29 10:58 ` manfred99 at gmx dot ch
2020-05-29 14:33 ` manfred99 at gmx dot ch
2020-05-29 18:49 ` anlauf at gcc dot gnu.org
2020-05-29 19:19 ` cvs-commit at gcc dot gnu.org
2020-05-30 18:51 ` cvs-commit at gcc dot gnu.org
2020-06-05 19:32 ` cvs-commit at gcc dot gnu.org
2020-06-05 19:32 ` cvs-commit at gcc dot gnu.org
2020-06-05 19:32 ` cvs-commit at gcc dot gnu.org
2020-06-05 20:53 ` anlauf at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-95090-4-KjFNwSjb45@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).