public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/14791] [3.3/3.4/3.5 Regression] 13070 does not fix -Wformat with fprintf Date: Wed, 31 Mar 2004 00:31:00 -0000 [thread overview] Message-ID: <20040331003126.18125.qmail@sources.redhat.com> (raw) In-Reply-To: <20040331002409.14791.wmay@cisco.com> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-03-31 00:31 ------- Confirmed, reduced testcase: typedef struct _FILE FILE; FILE *stderr; extern "C" int fprintf (FILE *__restrict __stream, __const char *__restrict __format, ...); int main() { fprintf(stderr, "%d\n", 1, 1); } -- What |Removed |Added ---------------------------------------------------------------------------- CC| |roger at eyesopen dot com Status|UNCONFIRMED |NEW Ever Confirmed| |1 Keywords| |diagnostic Known to fail| |3.3.3 3.4.0 3.5.0 Known to work| |3.2.3 Last reconfirmed|0000-00-00 00:00:00 |2004-03-31 00:31:24 date| | Summary|13070 does not fix -Wformat |[3.3/3.4/3.5 Regression] |with fprintf |13070 does not fix -Wformat | |with fprintf Target Milestone|--- |3.4.1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14791
next prev parent reply other threads:[~2004-03-31 0:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-31 0:24 [Bug c++/14791] New: " wmay at cisco dot com 2004-03-31 0:26 ` [Bug c++/14791] " wmay at cisco dot com 2004-03-31 0:31 ` pinskia at gcc dot gnu dot org [this message] 2004-04-02 16:25 ` [Bug c++/14791] [3.3/3.4/3.5 Regression] " jakub at gcc dot gnu dot org 2004-04-25 15:43 ` giovannibajo at libero dot it 2004-06-10 8:08 ` cvs-commit at gcc dot gnu dot org 2004-06-12 21:50 ` mmitchel 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=20040331003126.18125.qmail@sources.redhat.com \ --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).