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++/112838] Compiler is unable to show the exact error location when calling copy ctor for a non-copyable object
Date: Tue, 05 Dec 2023 21:02:01 +0000	[thread overview]
Message-ID: <bug-112838-4-7dsLfdbpdX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112838-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Ahmad Nour from comment #7)
> (In reply to Andrew Pinski from comment #3)
> > (In reply to Ahmad Nour from comment #2)
> > > 
> > > Thanks for confirmation.
> > > I tried with clang-12 -Wall -Wextra main.cpp, but I didn't get that
> > > hint/note. Am I missing something?
> > 
> > Oh I tried with -std=c++20 which provided that note.  Sorry about that. But
> > it might be the case that adding this for -std=c++17 might be hard ...
> 
> Hmmmmm this is what I'm getting with c++20. I can't find that note where it
> points to line #13
> 
> >> clang-12 -Wall -Wextra main.cpp -std=c++20

well clang-12 was released 2 years ago ... I am trying to say that clang
already fixed this case for -std=c++20 in a newer clang version and GCC should
fix this too, that is what PR 109551 is about.  Note compiler developers tend
to try to the trunk (mainline) sources of each compiler to see if what other
compilers do and don't really look into older releases of the other compiler to
see when it was added especially when it comes to diagnostic improvments.

      parent reply	other threads:[~2023-12-05 21:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03 20:10 [Bug c++/112838] New: " eng.ahmad.nour at gmail dot com
2023-12-03 20:27 ` [Bug c++/112838] " pinskia at gcc dot gnu.org
2023-12-03 20:38 ` eng.ahmad.nour at gmail dot com
2023-12-03 20:53 ` pinskia at gcc dot gnu.org
2023-12-04 11:24 ` redi at gcc dot gnu.org
2023-12-04 11:30 ` redi at gcc dot gnu.org
2023-12-05  8:57 ` eng.ahmad.nour at gmail dot com
2023-12-05  9:01 ` eng.ahmad.nour at gmail dot com
2023-12-05 21:02 ` pinskia 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-112838-4-7dsLfdbpdX@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).