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/99545] New: [11.0 regression] ICE in gfc_trans_assignment Date: Thu, 11 Mar 2021 07:46:28 +0000 [thread overview] Message-ID: <bug-99545-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99545 Bug ID: 99545 Summary: [11.0 regression] ICE in gfc_trans_assignment Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: juergen.reuter at desy dot de Target Milestone: --- This regression must have been introduced between Dec 6, 2020 and now, sorry, no better containment at the moment: ommands.f90:5466:60: 5466 | allocate (range_int_t :: cmd%range (cmd%n_values)) | 1 internal compiler error: in gfc_trans_assignment_1, at fortran/trans-expr.c:11247 This is only a problem when compiling with full debug flags, i.e. -O0 -fbacktrace -fcheck=all -Wconversion -Wconversion-extra -Wsurprising A short reproducer will follow but for those of you that know the Whizard project, https://whizard.hepforge.org could check this already, take the last tarball 3.0.0beta or 2.8.5.
next reply other threads:[~2021-03-11 7:46 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-11 7:46 juergen.reuter at desy dot de [this message] 2021-03-11 7:47 ` [Bug fortran/99545] " juergen.reuter at desy dot de 2021-03-11 8:46 ` [Bug fortran/99545] [11 Regression] " rguenth at gcc dot gnu.org 2021-03-11 9:42 ` marxin at gcc dot gnu.org 2021-03-11 11:13 ` juergen.reuter at desy dot de 2021-03-11 13:02 ` marxin at gcc dot gnu.org 2021-03-11 13:04 ` juergen.reuter at desy dot de 2021-03-11 14:43 ` juergen.reuter at desy dot de 2021-03-11 14:52 ` juergen.reuter at desy dot de 2021-03-11 16:01 ` [Bug fortran/99545] [11 Regression] ICE in gfc_trans_assignment since r11-6253-gce8dcc9105cbd404 marxin at gcc dot gnu.org 2021-03-15 8:34 ` pault at gcc dot gnu.org 2021-03-15 9:33 ` cvs-commit at gcc dot gnu.org 2021-03-15 11:09 ` cvs-commit at gcc dot gnu.org 2021-03-15 12:09 ` cvs-commit at gcc dot gnu.org 2021-03-15 13:15 ` juergen.reuter at desy dot de 2021-03-15 14:51 ` pault at gcc dot gnu.org 2021-03-15 14:52 ` juergen.reuter at desy dot de 2021-03-15 17:50 ` pault 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-99545-4@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: linkBe 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).