public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/100815] [10/11/12 Regression] Segfault assigning to scalar allocatable polymorphic LHS Date: Mon, 31 May 2021 06:51:54 +0000 [thread overview] Message-ID: <bug-100815-4-0M49M8xfQQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100815-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100815 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code Summary|[10.3, 11 regression] |[10/11/12 Regression] |Segfault assigning to |Segfault assigning to |scalar allocatable |scalar allocatable |polymorphic LHS |polymorphic LHS Target Milestone|--- |10.4 Known to fail| |10.3.0 Known to work| |10.2.0
next prev parent reply other threads:[~2021-05-31 6:51 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-28 15:14 [Bug fortran/100815] New: [11 regression] " neil.n.carlson at gmail dot com 2021-05-28 15:38 ` [Bug fortran/100815] [10.3, 11 " neil.n.carlson at gmail dot com 2021-05-31 6:51 ` rguenth at gcc dot gnu.org [this message] 2021-05-31 8:43 ` [Bug fortran/100815] [10/11/12 Regression] Segfault assigning to scalar allocatable polymorphic LHS since r11-6253-gce8dcc9105cbd404 marxin at gcc dot gnu.org 2022-01-17 14:37 ` rguenth at gcc dot gnu.org 2022-06-28 10:45 ` [Bug fortran/100815] [10/11/12/13 " jakub at gcc dot gnu.org 2023-04-19 9:12 ` [Bug fortran/100815] [10/11/12/13/14 " pault at gcc dot gnu.org 2023-04-19 9:31 ` [Bug fortran/100815] [10/11 " marxin at gcc dot gnu.org 2023-04-20 6:46 ` pault at gcc dot gnu.org 2023-04-20 7:55 ` marxin at gcc dot gnu.org 2023-07-07 10:40 ` [Bug fortran/100815] [11 " rguenth at gcc dot gnu.org 2024-04-25 6:35 ` 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-100815-4-0M49M8xfQQ@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).