public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/35017] [4.3 Regression] PR11377 pedwarns even about valid code Date: Tue, 29 Jan 2008 23:46:00 -0000 [thread overview] Message-ID: <20080129231952.11120.qmail@sourceware.org> (raw) In-Reply-To: <bug-35017-87@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from jakub at gcc dot gnu dot org 2008-01-29 23:19 ------- Subject: Bug 35017 Author: jakub Date: Tue Jan 29 23:19:07 2008 New Revision: 131945 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=131945 Log: PR c/35017 * c-decl.c (start_decl): Don't pedwarn about TREE_READONLY static decls. * c-typeck.c (build_external_ref): Don't pedwarn about static vars in current function's scope. * gcc.dg/inline-25.c: New test. * gcc.dg/inline-26.c: New test. * gcc.dg/inline-27.c: New test. Added: trunk/gcc/testsuite/gcc.dg/inline-25.c trunk/gcc/testsuite/gcc.dg/inline-26.c trunk/gcc/testsuite/gcc.dg/inline-27.c Modified: trunk/gcc/ChangeLog trunk/gcc/c-decl.c trunk/gcc/c-typeck.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35017
next prev parent reply other threads:[~2008-01-29 23:20 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-29 15:25 [Bug c/35017] New: " jakub at gcc dot gnu dot org 2008-01-29 15:25 ` [Bug c/35017] " jakub at gcc dot gnu dot org 2008-01-29 15:48 ` rguenth at gcc dot gnu dot org 2008-01-29 16:06 ` jakub at gcc dot gnu dot org 2008-01-29 17:27 ` pinskia at gcc dot gnu dot org 2008-01-29 17:52 ` jakub at gcc dot gnu dot org 2008-01-29 18:00 ` jakub at gcc dot gnu dot org 2008-01-29 19:37 ` jakub at gcc dot gnu dot org 2008-01-29 19:52 ` joseph at codesourcery dot com 2008-01-29 23:46 ` jakub at gcc dot gnu dot org [this message] 2008-01-30 0:03 ` jakub 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=20080129231952.11120.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).