public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109278] New: a note without a warning Date: Fri, 24 Mar 2023 20:57:04 +0000 [thread overview] Message-ID: <bug-109278-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109278 Bug ID: 109278 Summary: a note without a warning Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: diagnostic, needs-reduction Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- the attached unreduced testcase when compiled with -w -std=c++20, gives: t.cc: In static member function ‘static int __iseqsig_type<_Float128>::__call(_Float128, _Float128)’: t.cc:90092:36: note: initializing argument 1 of ‘int __iseqsigl(long double, long double)’ 90092 | extern int __iseqsigl (long double __x, long double __y) noexcept (true); | ~~~~~~~~~~~~^~~ t.cc:90092:53: note: initializing argument 2 of ‘int __iseqsigl(long double, long double)’ 90092 | extern int __iseqsigl (long double __x, long double __y) noexcept (true); | ~~~~~~~~~~~~^~~ Which is wrong as the warnings are supressed but still providing the note.
next reply other threads:[~2023-03-24 20:57 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-24 20:57 pinskia at gcc dot gnu.org [this message] 2023-03-24 20:57 ` [Bug c++/109278] " pinskia at gcc dot gnu.org 2023-03-24 21:01 ` pinskia at gcc dot gnu.org 2023-03-24 21:34 ` jakub at gcc dot gnu.org 2023-03-24 21:42 ` jakub at gcc dot gnu.org 2023-03-30 7:35 ` cvs-commit at gcc dot gnu.org 2023-03-30 7:37 ` jakub at gcc dot gnu.org 2023-04-25 12:42 ` cvs-commit at gcc dot gnu.org 2023-04-26 8:37 ` cvs-commit 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-109278-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: 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).