public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105377] New: Likely a misleading clang warning -Wc++20-attribute-extensions
Date: Mon, 25 Apr 2022 13:46:55 +0000	[thread overview]
Message-ID: <bug-105377-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105377
           Summary: Likely a misleading clang warning
                    -Wc++20-attribute-extensions
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: mpolacek at gcc dot gnu.org, redi at gcc dot gnu.org
  Target Milestone: ---

I noticed the following warning:

clang++  -I/home/marxin/Programming/gcc/libcpp -I.
-I/home/marxin/Programming/gcc/libcpp/../include
-I/home/marxin/Programming/gcc/libcpp/include  -g -O2     -W -Wall
-Wno-narrowing -Wwrite-strings -Wmissing-format-attribute -pedantic
-Wno-long-long  -fno-exceptions -fno-rtti -I/home/marxin/Programming/gcc/libcpp
-I. -I/home/marxin/Programming/gcc/libcpp/../include
-I/home/marxin/Programming/gcc/libcpp/include  -fPIC -fcf-protection -c -o
lex.o -MT lex.o -MMD -MP -MF .deps/lex.Tpo
/home/marxin/Programming/gcc/libcpp/lex.cc -std=c++17
/home/marxin/Programming/gcc/libcpp/lex.cc:1289:7: warning: use of the 'likely'
attribute is a C++20 extension [-Wc++20-attribute-extensions]
      ATTR_LIKELY case kind::NONE:
      ^~~~~~~~~~~
/home/marxin/Programming/gcc/libcpp/system.h:427:25: note: expanded from macro
'ATTR_LIKELY'
#  define ATTR_LIKELY [[likely]]
                      ~~^~~~~~~~

             reply	other threads:[~2022-04-25 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 13:46 marxin at gcc dot gnu.org [this message]
2022-04-25 13:55 ` [Bug c++/105377] " jakub at gcc dot gnu.org
2022-04-25 13:58 ` mpolacek at gcc dot gnu.org
2022-04-25 14:00 ` egallager at gcc dot gnu.org
2022-04-25 14:44 ` redi at gcc dot gnu.org
2022-04-25 20:25 ` marxin at gcc dot gnu.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=bug-105377-4@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).