public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lei at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/15393] [gfortran] Initialization of automatic objects not detected, causes ICE Date: Thu, 13 May 2004 00:27:00 -0000 [thread overview] Message-ID: <20040512122110.3356.qmail@sourceware.org> (raw) In-Reply-To: <20040512114938.15393.lei@il.ibm.com> ------- Additional Comments From lei at il dot ibm dot com 2004-05-12 12:21 ------- Subject: Re: [gfortran] Initialization of automatic objects not detected, causes ICE Oops. I should have seen it -- sorry! Victor "pinskia at gcc dot gnu dot org" To: Victor Leikehman/Haifa/IBM@IBMIL <gcc-bugzilla@gcc cc: .gnu.org> Subject: [Bug fortran/15393] [gfortran] Initialization of automatic objects not detected, causes ICE 05/12/04 02:57 PM Please respond to gcc-bugzilla ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-05-12 11:57 ------- *** Bug 15370 has been marked as a duplicate of this bug. *** -- What |Removed |Added ---------------------------------------------------------------------------- CC| |jblomqvi at cc dot hut dot | |fi http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15393 ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15393
next prev parent reply other threads:[~2004-05-12 12:21 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-05-12 23:01 [Bug fortran/15393] New: " lei at il dot ibm dot com 2004-05-12 23:10 ` [Bug fortran/15393] [gfortran] " pinskia at gcc dot gnu dot org 2004-05-12 23:47 ` pinskia at gcc dot gnu dot org 2004-05-13 0:27 ` lei at il dot ibm dot com [this message] 2004-05-13 14:39 ` lei at il dot ibm dot com 2004-05-14 14:07 ` pinskia at gcc dot gnu dot org 2004-05-16 21:41 ` pbrook 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=20040512122110.3356.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).