public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59821] __builtin_LINE and __builtin_FILE for new'd objects is wrong
Date: Wed, 15 Jan 2014 11:47:00 -0000	[thread overview]
Message-ID: <bug-59821-4-fQouKdsd5S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59821-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59821

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-debug
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-01-15
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
    [t.C : 12:3] Foo::Foo ([t.C : 12] &D.2242, 12);
    [t.C : 12:42] try
      {
        [t.C : 12:3] D.2247 = D.2242.line;
        [t.C : 12:3] D.2244 = 5;
        [t.C : 12:3] D.2243 = operator new (4);
        [t.C : 12:3] try
          {
            [t.C : 12:3] Foo::Foo (D.2243, D.2244);

looks like location info is broken for the new case.


       reply	other threads:[~2014-01-15 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-59821-4@http.gcc.gnu.org/bugzilla/>
2014-01-15 11:47 ` rguenth at gcc dot gnu.org [this message]
2014-01-16 17:06 ` jason at gcc dot gnu.org
2014-01-16 17:10 ` jakub at gcc dot gnu.org
2014-01-16 18:02 ` aldyh at gcc dot gnu.org
2014-01-16 18:41 ` jason at gcc dot gnu.org
2014-01-16 19:55 ` jason at gcc dot gnu.org
2014-01-16 19:57 ` jason at gcc dot gnu.org
2014-01-17 12:41 ` rguenth 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-59821-4-fQouKdsd5S@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).