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/18799] [3.4 Regression] error: static declaration of 'x' follows non-static declaration Date: Thu, 02 Dec 2004 23:23:00 -0000 [thread overview] Message-ID: <20041202232337.25826.qmail@sourceware.org> (raw) In-Reply-To: <20041202212109.18799.markus@oberhumer.com> -- What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic Known to fail| |3.4.3 Known to work| |3.3.3 4.0.0 Summary|error: static declaration of|[3.4 Regression] error: |'x' follows non-static |static declaration of 'x' |declaration |follows non-static | |declaration Target Milestone|4.0.0 |3.4.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18799
next prev parent reply other threads:[~2004-12-02 23:23 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-02 21:21 [Bug c/18799] New: " markus at oberhumer dot com 2004-12-02 21:24 ` [Bug c/18799] " pinskia at gcc dot gnu dot org 2004-12-02 23:12 ` markus at oberhumer dot com 2004-12-02 23:23 ` pinskia at gcc dot gnu dot org [this message] 2004-12-03 9:13 ` [Bug c/18799] [3.4 Regression] " falk at debian dot org 2005-04-30 0:04 ` jsm28 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=20041202232337.25826.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).