public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/66035] [5/6 Regression] gfortran ICE segfault Date: Wed, 06 May 2015 13:23:00 -0000 [thread overview] Message-ID: <bug-66035-4-PpSfrrXjLa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66035-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66035 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-05-06 CC| |pault at gcc dot gnu.org, | |vehre at gcc dot gnu.org Summary|[5.1 Regression] gfortran |[5/6 Regression] gfortran |ICE segfault |ICE segfault Ever confirmed|0 |1 --- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- The make completes without error with r219763 (2015-01-16). I get the ICE with r219823 (2015-01-18), likely revision r219801 (pr55932, pr60357, and pr61275). The ICE is still present on trunk (6.0 r222768). I'll try to reduce later today if nobody beats me.
next prev parent reply other threads:[~2015-05-06 13:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-06 11:21 [Bug fortran/66035] New: [5.1 " Melven.Roehrig-Zoellner at DLR dot de 2015-05-06 11:24 ` [Bug fortran/66035] " Melven.Roehrig-Zoellner at DLR dot de 2015-05-06 13:23 ` dominiq at lps dot ens.fr [this message] 2015-05-06 14:38 ` [Bug fortran/66035] [5/6 " vehre at gcc dot gnu.org 2015-05-06 17:01 ` vehre at gcc dot gnu.org 2015-05-09 9:35 ` evangelos at foutrelis dot com 2015-07-17 10:16 ` vehre at gcc dot gnu.org 2015-07-21 10:36 ` vehre 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-66035-4-PpSfrrXjLa@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).