From: Richard Biener <richard.guenther@gmail.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Dehao Chen <dehao@google.com>,
Eric Botcazou <ebotcazou@adacore.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
David Li <davidxl@google.com>
Subject: Re: [PATCH] Reset source location for instructions moved out of its original residing basic block
Date: Mon, 26 Nov 2012 14:47:00 -0000 [thread overview]
Message-ID: <CAFiYyc2ACm+OomLZu7-VkubFdoY0C8aR4HwOEbCw2KLt7gDkGA@mail.gmail.com> (raw)
In-Reply-To: <orr4o9gg3g.fsf@livre.localdomain>
On Sun, Nov 4, 2012 at 11:26 PM, Alexandre Oliva <aoliva@redhat.com> wrote:
> On Nov 1, 2012, Dehao Chen <dehao@google.com> wrote:
>
>> I see your point. How about we guard these changes with a flag, say
>> -gless-jumpy
>
> The right (DWARF-expected) approach to avoid this sortof jumpiness is to
> teach GCC to emit .locs with is_stmt=1, along the lines (and
> limitations) described in my GCC Summit paper on stmt frontier notes,
> that proposes further extensions to deal with the foreseen limitations.
Right. gdb could also instead of show a single line (and that changing
all the time) show all currently "active" lines (thus scan the current
function for lines that appear and compute their "liveness"). A step
would then jump to the next stmt that changes line liveness.
Richard.
> http://people.redhat.com/~aoliva/papers/sfn/gcc2010.pdf
>
> --
> Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
> You must be the change you wish to see in the world. -- Gandhi
> Be Free! -- http://FSFLA.org/ FSF Latin America board member
> Free Software Evangelist Red Hat Brazil Compiler Engineer
prev parent reply other threads:[~2012-11-26 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 5:03 Dehao Chen
2012-11-01 8:56 ` Eric Botcazou
2012-11-01 14:36 ` Dehao Chen
2012-11-01 15:04 ` Eric Botcazou
2012-11-01 17:00 ` Dehao Chen
2012-11-01 22:57 ` Ian Lance Taylor
2012-11-01 23:07 ` Xinliang David Li
2012-11-01 23:16 ` Dehao Chen
2012-11-01 23:36 ` Xinliang David Li
2012-11-04 22:26 ` Alexandre Oliva
2012-11-26 14:47 ` Richard Biener [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=CAFiYyc2ACm+OomLZu7-VkubFdoY0C8aR4HwOEbCw2KLt7gDkGA@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=aoliva@redhat.com \
--cc=davidxl@google.com \
--cc=dehao@google.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@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).