public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/96073] [11.0 regression] regression in gfc_format_decoder
Date: Mon, 06 Jul 2020 12:23:45 +0000 [thread overview]
Message-ID: <bug-96073-4-5RDYRYd5NG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96073-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96073
--- Comment #1 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Next step, full error message:
ibtool: compile: gfortran -I../basics -I../utilities -I../testing -I../system
-I../combinatorics -I../rng -I../physics -I../fastjet -I../qft -I../types
-I../particles -I../../circe1/src -I../../circe2/src -I../pdf_builtin
-I../lhapdf -I../qed_pdf -I../variables -I../expr_base -I../parsing -g -O2 -c
sf_lhapdf.f90 -fPIC -o .libs/sf_lhapdf.o
in gfc_format_decoder, at fortran/error.c:970
0x5f46ce gfc_format_decoder
../../gcc/fortran/error.c:970
0x18b722c pp_format(pretty_printer*, text_info*)
../../gcc/pretty-print.c:1475
0x189c41e diagnostic_report_diagnostic(diagnostic_context*, diagnostic_info*)
../../gcc/diagnostic.c:1159
0x807a05 gfc_report_diagnostic
../../gcc/fortran/error.c:782
0x807a05 gfc_warning
../../gcc/fortran/error.c:815
0x808016 gfc_warning(int, char const*, ...)
../../gcc/fortran/error.c:846
0x9572bf check_against_globals
../../gcc/fortran/frontend-passes.c:5528
0x8a8b02 do_traverse_symtree
../../gcc/fortran/symbol.c:4170
0x95f5d1 gfc_check_externals(gfc_namespace*)
../../gcc/fortran/frontend-passes.c:5563
0x86e554 gfc_parse_file()
../../gcc/fortran/parse.c:6499
0x8bf9bf gfc_be_parse_file
../../gcc/fortran/f95-lang.c:212
Please submit a full bug report,
Code will follow in a minute.
next prev parent reply other threads:[~2020-07-06 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 9:42 [Bug fortran/96073] New: " juergen.reuter at desy dot de
2020-07-06 12:23 ` juergen.reuter at desy dot de [this message]
2020-07-06 15:32 ` [Bug fortran/96073] [11 Regression] " rguenth at gcc dot gnu.org
2020-07-06 16:03 ` [Bug fortran/96073] [11.0 regression] " juergen.reuter at desy dot de
2020-07-06 17:51 ` tkoenig at gcc dot gnu.org
2020-07-07 8:56 ` marxin at gcc dot gnu.org
2020-07-11 9:42 ` tkoenig at gcc dot gnu.org
2020-07-11 9:57 ` tkoenig at gcc dot gnu.org
2020-07-11 13:11 ` tkoenig at gcc dot gnu.org
2020-07-11 17:19 ` cvs-commit at gcc dot gnu.org
2020-07-11 17:25 ` tkoenig at gcc dot gnu.org
2020-07-11 17:25 ` tkoenig 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-96073-4-5RDYRYd5NG@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).