public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/44375] goto_locus lost at -O0 during cfg cleanup
Date: Wed, 02 Jun 2010 13:34:00 -0000 [thread overview]
Message-ID: <20100602133354.8892.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44375-87@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from pinskia at gmail dot com 2010-06-02 13:33 -------
Subject: Re: New: goto_locus lost at -O0 during cfg cleanup
I think this is a dup of a much older bug.
Sent from my iPhone
On Jun 2, 2010, at 3:30 AM, "jakub at gcc dot gnu dot org"
<gcc-bugzilla@gcc.gnu.org
> wrote:
> As mentioned in
> http://gcc.gnu.org/ml/gcc-patches/2010-06/msg00115.html
> for -O0 we sometimes, e.g. for return without value or for C++ NRV
> optimized
> return don't emit any insns with the location of the return stmt,
> which results
> in worse debug experience.
>
>
> --
> Summary: goto_locus lost at -O0 during cfg cleanup
> Product: gcc
> Version: 4.6.0
> Status: UNCONFIRMED
> Severity: normal
> Priority: P3
> Component: debug
> AssignedTo: unassigned at gcc dot gnu dot org
> ReportedBy: jakub at gcc dot gnu dot org
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44375
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44375
next prev parent reply other threads:[~2010-06-02 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 10:30 [Bug debug/44375] New: " jakub at gcc dot gnu dot org
2010-06-02 10:37 ` [Bug debug/44375] " jakub at gcc dot gnu dot org
2010-06-02 11:33 ` jakub at gcc dot gnu dot org
2010-06-02 13:33 ` [Bug debug/44375] New: " Andrew Pinski
2010-06-02 13:34 ` pinskia at gmail dot com [this message]
2010-06-02 15:29 ` [Bug debug/44375] " pinskia at gcc dot gnu dot org
2010-06-03 12:08 ` jakub at gcc dot gnu dot org
2010-07-27 8:58 ` jakub at gcc dot gnu dot 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=20100602133354.8892.qmail@sourceware.org \
--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).