public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "geoffk at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/11377] fault or warn modifiable static in extern inline definition Date: Wed, 01 Nov 2006 04:48:00 -0000 [thread overview] Message-ID: <20061101044828.7427.qmail@sourceware.org> (raw) In-Reply-To: <bug-11377-1536@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from geoffk at gcc dot gnu dot org 2006-11-01 04:48 ------- Subject: Bug 11377 Author: geoffk Date: Wed Nov 1 04:48:15 2006 New Revision: 118357 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=118357 Log: * c-decl.c (grokdeclarator): Don't set DECL_EXTERNAL on inline static functions in c99 mode. PR 16622 * doc/extend.texi (Inline): Update. * c-tree.h (struct language_function): Remove field 'extern_inline'. * c-decl.c (current_extern_inline): Delete. (pop_scope): Adjust test for an undefined nested function. Add warning about undeclared inline function. (diagnose_mismatched_decls): Update comments. Disallow overriding of inline functions in a translation unit in C99. Allow inline declarations in C99 at any time. (merge_decls): Boolize variables. Handle C99 'extern inline' semantics. (grokdeclarator): Set DECL_EXTERNAL here for functions. Handle C99 inline semantics. (start_function): Don't clear current_extern_inline. Don't set DECL_EXTERNAL. (c_push_function_context): Don't push current_extern_inline. (c_pop_function_context): Don't restore current_extern_inline. PR 11377 * c-typeck.c (build_external_ref): Warn about static variables used in extern inline functions. * c-decl.c (start_decl): Warn about static variables declared in extern inline functions. Modified: trunk/gcc/doc/extend.texi -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11377
next prev parent reply other threads:[~2006-11-01 4:48 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-11377-1536@http.gcc.gnu.org/bugzilla/> 2006-05-04 21:49 ` geoffk at gcc dot gnu dot org 2006-10-16 21:53 ` geoffk at gcc dot gnu dot org 2006-11-01 4:47 ` geoffk at gcc dot gnu dot org 2006-11-01 4:48 ` geoffk at gcc dot gnu dot org [this message] 2006-11-01 5:40 ` geoffk at gcc dot gnu dot org 2006-11-30 19:26 ` chaoyingfu at gcc dot gnu dot org 2003-06-30 10:25 [Bug c/11377] New: " algrant at myrealbox dot com 2003-07-18 22:52 ` [Bug c/11377] " dhazeghi at yahoo dot com 2003-08-23 0:36 ` dhazeghi at yahoo dot com 2003-11-27 16:46 ` pinskia at gcc dot gnu dot org 2004-08-07 0:18 ` hozelda at yahoo dot com 2004-08-11 21:05 ` 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=20061101044828.7427.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).