public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109083] [10/11/12/13 Regression] Incorrect static_assert shown in diagnostics
Date: Wed, 15 Mar 2023 14:33:32 +0000	[thread overview]
Message-ID: <bug-109083-4-tUnzwtagem@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109083-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
We don't instantiate in that case, just look up a specialization which might be
or might not be later instantiated (which is when it is diagnosed).
One way to fix this would be to drop locations from the expressions in the
template arguments if we use them from multiple spots.  But that could result
in less accurate diagnostics.

  parent reply	other threads:[~2023-03-15 14:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 19:23 [Bug c++/109083] New: " markus-t314 at gmx dot de
2023-03-09 19:37 ` [Bug c++/109083] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org
2023-03-15 10:49 ` jakub at gcc dot gnu.org
2023-03-15 11:40 ` jakub at gcc dot gnu.org
2023-03-15 14:29 ` rguenth at gcc dot gnu.org
2023-03-15 14:33 ` jakub at gcc dot gnu.org [this message]
2023-03-15 17:42 ` jason at gcc dot gnu.org
2023-03-27  8:11 ` rguenth at gcc dot gnu.org
2023-04-26  6:58 ` [Bug c++/109083] [10/11/12/13/14 " rguenth at gcc dot gnu.org
2023-07-27  9:25 ` [Bug c++/109083] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-05-21  9:14 ` [Bug c++/109083] [11/12/13/14/15 " jakub 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-109083-4-tUnzwtagem@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).