Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Frederic Riss <frederic.riss@gmail.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: RFC: optimized-out pieces
Date: Tue, 15 Jun 2010 15:54:00 -0000	[thread overview]
Message-ID: <m37hm0watj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <AANLkTikomBCDF7DS_ZtFZe7tNOHKM6POgiI1K08H0wSQ@mail.gmail.com>	(Frederic Riss's message of "Mon, 14 Jun 2010 14:07:19 +0200")

>>>>> "Frederic" == Frederic Riss <frederic.riss@gmail.com> writes:

Tom> I am checking in the latest version of this patch.

Frederic> I think this patch regresses on architectures that mark registers as
Frederic> optimized in their CFI.

Thanks for the detailed report.  It looks like Ulrich already fixed
this.  I'm sorry about the breakage; I'm looking at setting up a
buildbot so we can more easily regression test on multiple
architectures.

Frederic> I fixed that by preventing frame_register_unwind to call
Frederic> value_contents_all in the optimized case (not providing the one-liner
Frederic> as I don't have the copyright assignment in place anymore).

A short patch like that would not require an assignment.

However... why not get a new assignment?  It will be fun and rewarding!

Tom


  reply	other threads:[~2010-06-15 15:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04 19:19 Tom Tromey
2010-06-04 21:42 ` Tom Tromey
2010-06-07 22:35 ` Jan Kratochvil
2010-06-08 18:36   ` Tom Tromey
2010-06-08 18:42     ` Jan Kratochvil
2010-06-08 18:57       ` Tom Tromey
2010-06-09  5:50         ` Jan Kratochvil
2010-06-10 17:14           ` Tom Tromey
2010-06-11 15:34             ` Tom Tromey
2010-06-14 12:07               ` Frederic Riss
2010-06-15 15:54                 ` Tom Tromey [this message]
2010-06-09 18:44         ` Jan Kratochvil
2010-06-14 12:13 ` [commit] Fix "return" command (Re: RFC: optimized-out pieces) Ulrich Weigand
2010-06-15 15:58   ` Tom Tromey

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=m37hm0watj.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=frederic.riss@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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