public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/31463] [patch] inconsistent warnings if function return value is not set Date: Tue, 29 Jan 2008 03:33:00 -0000 [thread overview] Message-ID: <20080129012618.16509.qmail@sourceware.org> (raw) In-Reply-To: <bug-31463-14284@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from dfranke at gcc dot gnu dot org 2008-01-29 01:26 ------- Mine. For patch, see URL above. -- dfranke at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |dfranke at gcc dot gnu dot |dot org |org URL| |http://gcc.gnu.org/ml/fortra | |n/2008-01/msg00355.html Status|NEW |ASSIGNED Keywords| |patch Last reconfirmed|2008-01-28 14:45:55 |2008-01-29 01:26:18 date| | Summary|gfortran prints no warning |[patch] inconsistent |message when an unset return|warnings if function return |value is an array |value is not set Target Milestone|--- |4.4.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31463
next prev parent reply other threads:[~2008-01-29 1:27 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-04-03 16:37 [Bug fortran/31463] New: gfortran prints no warning message when an unset return value is an array michael dot a dot richmond at nasa dot gov 2007-04-03 17:45 ` [Bug fortran/31463] " michael dot a dot richmond at nasa dot gov 2007-04-18 5:52 ` fxcoudert at gcc dot gnu dot org 2008-01-28 15:46 ` dfranke at gcc dot gnu dot org 2008-01-29 3:33 ` dfranke at gcc dot gnu dot org [this message] 2008-01-29 10:18 ` [Bug fortran/31463] [patch] inconsistent warnings if function return value is not set burnus at gcc dot gnu dot org 2008-01-29 10:27 ` dfranke at gcc dot gnu dot org 2008-02-28 20:24 ` dfranke at gcc dot gnu dot org 2008-02-28 20:26 ` dfranke 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=20080129012618.16509.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).