public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "accelerator0099 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106584] g++ not showing correct line number in "use of deleted function" error
Date: Fri, 12 Aug 2022 06:52:14 +0000	[thread overview]
Message-ID: <bug-106584-4-NNNgYdErLH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106584-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Devourer Station <accelerator0099 at gmail dot com> ---
(In reply to Andrew Pinski from comment #4)
> Actually clang references the call:
> f(cl);
> 
> When it comes to the copy constructor.

At least it tells you about where the error is, otherwise you may fall into
thousands of lines of source code without knowing where to edit

      parent reply	other threads:[~2022-08-12  6:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 15:14 [Bug c++/106584] New: " accelerator0099 at gmail dot com
2022-08-11 15:15 ` [Bug c++/106584] " accelerator0099 at gmail dot com
2022-08-11 15:16 ` accelerator0099 at gmail dot com
2022-08-11 15:42 ` pinskia at gcc dot gnu.org
2022-08-11 15:43 ` pinskia at gcc dot gnu.org
2022-08-12  6:52 ` accelerator0099 at gmail dot com [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-106584-4-NNNgYdErLH@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).