From: Alexandre Oliva <aoliva@redhat.com>
To: "Richard Guenther" <richard.guenther@gmail.com>
Cc: "GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC] New SSA variable mapping infrastructure
Date: Mon, 12 Nov 2007 18:40:00 -0000 [thread overview]
Message-ID: <orlk93xsf0.fsf@oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <84fc9c000711090153m32ec85fo760209f1a5375603@mail.gmail.com> (Richard Guenther's message of "Fri\, 9 Nov 2007 10\:53\:11 +0100")
On Nov 9, 2007, "Richard Guenther" <richard.guenther@gmail.com> wrote:
> What our approach basically does is to identify all names that a
> computed value has at any point during program execution.
I.e., you disregard pretty much all information as to where the value
gains each name, and as to where it ceases to have that name. Do you
have any evidence that this can possibly get you better (not only more
complete, but also more correct) debug information than what we have
now? The problem of non-concurrent uses being noted in debug info as
concurrent seems particularly serious to me (the mapping of c to both
x and y we debated before).
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2007-11-12 17:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 18:26 Richard Guenther
2007-10-04 6:27 ` Michael Matz
2007-11-07 8:29 ` Alexandre Oliva
2007-10-18 12:46 ` Paolo Bonzini
2007-11-07 8:14 ` Alexandre Oliva
2007-11-07 10:34 ` Richard Guenther
2007-11-07 19:29 ` Alexandre Oliva
2007-11-08 9:25 ` Richard Guenther
2007-11-08 17:25 ` Alexandre Oliva
2007-11-08 20:51 ` Richard Guenther
2007-11-09 1:11 ` Alexandre Oliva
2007-11-09 11:55 ` Richard Guenther
2007-11-12 18:40 ` Alexandre Oliva [this message]
2007-11-13 11:13 ` Richard Guenther
2007-11-25 11:23 ` Alexandre Oliva
2007-11-25 13:38 ` Richard Guenther
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=orlk93xsf0.fsf@oliva.athome.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).