public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/30811] __FUNCTION__ allowed in function declaration (i.e. add -Wpredefined-identifier-outside-function)
Date: Mon, 24 Jan 2022 20:12:49 +0000	[thread overview]
Message-ID: <bug-30811-4-jVQMzZBLnq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-30811-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30811

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|__FUNCTION__ allowed in     |__FUNCTION__ allowed in
                   |function declaration        |function declaration (i.e.
                   |                            |add
                   |                            |-Wpredefined-identifier-out
                   |                            |side-function)
             Blocks|                            |87403

--- Comment #10 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #9)
> Note clang warns but its warning is not so clear:
> <source>:4:27: warning: predefined identifier is only valid inside function
> [-Wpredefined-identifier-outside-function]
> void bar (const char *s = __FUNCTION__) { puts (s); }
>                           ^
> <source>:5:27: warning: predefined identifier is only valid inside function
> [-Wpredefined-identifier-outside-function]
> void baz (const char *s = __PRETTY_FUNCTION__) { puts (s); }
>                           ^
> 
> At least MSVC is clear on what is going on:
> <source>(4): error C2457: '__FUNCTION__': predefined macro cannot appear
> outside of a function body

adding clang's name for the warning to the title, so that this can block the
"new warning" meta-bug


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403
[Bug 87403] [Meta-bug] Issues that suggest a new warning

      parent reply	other threads:[~2022-01-24 20:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-30811-4@http.gcc.gnu.org/bugzilla/>
2022-01-24 18:29 ` [Bug c++/30811] __FUNCTION__ allowed in function declaration pinskia at gcc dot gnu.org
2022-01-24 20:12 ` egallager at gcc dot gnu.org [this message]

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=bug-30811-4-jVQMzZBLnq@http.gcc.gnu.org/bugzilla/ \
    --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: link
Be 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).