From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Bernd Schmidt <bschmidt@redhat.com>
Cc: "Joseph Myers" <joseph@codesourcery.com>,
"Richard Henderson" <rth@redhat.com>,
gcc-patches@gcc.gnu.org, "David Malcolm" <dmalcolm@redhat.com>,
"Manuel López-Ibáñez" <lopezibanez@gmail.com>,
"Patrick Palka" <patrick@parcs.ath.cx>,
"Andreas Krebbel" <krebbel@linux.vnet.ibm.com>
Subject: Re: [PATCH v2] [PR debug/67192] Fix C loops' back-jump location
Date: Wed, 04 Nov 2015 14:53:00 -0000 [thread overview]
Message-ID: <m3fv0l24ug.fsf@oc1027705133.ibm.com> (raw)
In-Reply-To: <m3pozx1ot0.fsf@oc1027705133.ibm.com> (Andreas Arnez's message of "Thu, 29 Oct 2015 20:02:03 +0100")
On Thu, Oct 29 2015, Andreas Arnez wrote:
> On Thu, Oct 29 2015, Bernd Schmidt wrote:
>> [...]
>> i.e. the breakpoint on the code inside the loop is reached before the
>> while statement itself. This may be the expected behaviour with your
>> patch, but I'm not sure it's really desirable for debugging.
>
> [...]
> Maybe we could also improve the behavior of breaking on "while (1)" by
> generating a NOP for it? Or by using the first loop body's token
> instead?
I've basically tried the latter, and it seems to work pretty well. It
solves all the issues discussed in this mail thread, and I haven't found
any other issues with it. I'll post the patch separately.
>> I'd suggest you commit your original patch to fix the
>> misleading-indent problem while we sort this out.
>
> I can certainly do that. But note that the original patch does not
> solve the misleading-indent regression caused for f2() in the new
> version of pr67192.c. Thus the PR is not really fixed by it.
I've slightly changed the test case for that one, so I'll repost it as
well before committing it.
--
Andreas
prev parent reply other threads:[~2015-11-04 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 9:15 Andreas Arnez
2015-10-29 13:16 ` Andreas Arnez
2015-10-29 14:24 ` Bernd Schmidt
2015-10-29 19:20 ` Andreas Arnez
2015-11-04 14:53 ` Andreas Arnez [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=m3fv0l24ug.fsf@oc1027705133.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=bschmidt@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=krebbel@linux.vnet.ibm.com \
--cc=lopezibanez@gmail.com \
--cc=patrick@parcs.ath.cx \
--cc=rth@redhat.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).