public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/26475] tree-ssa loses line numbers for initializations (constants for PHIs)
Date: Fri, 24 Jul 2009 23:40:00 -0000 [thread overview]
Message-ID: <20090724234033.20293.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26475-3264@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from manu at gcc dot gnu dot org 2009-07-24 23:40 -------
(In reply to comment #1)
> Dan Berlin, Diego, and I bounced this around on IRC a little. A couple of
> things that came up:
>
> - Diego suggested putting locuses on unshared INTEGER_CSTs as another
> possible approach.
What would be the cost of this? This will help to give accurate diagnostics
even without optimization.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26475
next prev parent reply other threads:[~2009-07-24 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 21:02 [Bug debug/26475] New: tree-ssa loses line numbers for initializations drow at gcc dot gnu dot org
2006-02-27 21:13 ` [Bug debug/26475] " drow at gcc dot gnu dot org
2008-02-10 14:51 ` [Bug debug/26475] tree-ssa loses line numbers for initializations (constants for PHIs) manu at gcc dot gnu dot org
2009-07-24 23:40 ` manu at gcc dot gnu dot org [this message]
2009-07-25 9:50 ` rguenth at gcc dot gnu dot org
2009-07-30 18:40 ` amacleod at redhat dot com
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=20090724234033.20293.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).