public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/36167] ICE in gfc_conv_descriptor_dimension, at fortran/trans-array.c:242 Date: Sun, 18 May 2008 21:02:00 -0000 [thread overview] Message-ID: <20080518210207.6732.qmail@sourceware.org> (raw) In-Reply-To: <bug-36167-16157@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from pault at gcc dot gnu dot org 2008-05-18 21:02 ------- Frank, I am downgrading this to 'normal' severity - 'major' is reserved for fairly cataclysmic bugs for the whole of gcc. 'ice-on-valid-code' will catch the attention of gfortran developers. I'll try to come back to it when I have sorted the allocatable component memory leaks. Thanks Paul -- pault at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36167
next prev parent reply other threads:[~2008-05-18 21:02 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-07 9:31 [Bug fortran/36167] New: internal compiler error: " fmuldoo at me dot lsu dot edu 2008-05-07 9:32 ` [Bug fortran/36167] " fmuldoo at me dot lsu dot edu 2008-05-07 14:08 ` [Bug fortran/36167] ICE " burnus at gcc dot gnu dot org 2008-05-17 16:21 ` pault at gcc dot gnu dot org 2008-05-18 21:02 ` pault at gcc dot gnu dot org [this message] 2008-05-20 20:40 ` fmuldoo at me dot lsu dot edu 2008-09-08 8:29 ` domob at gcc dot gnu dot org 2008-09-08 13:54 ` domob at gcc dot gnu dot org 2008-09-08 13:56 ` domob at gcc dot gnu dot 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=20080518210207.6732.qmail@sourceware.org \ --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).