From: David Daney <ddaney@avtrex.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: dwarf2-frame vs set_loc
Date: Fri, 29 Sep 2006 20:09:00 -0000 [thread overview]
Message-ID: <451D7D8D.7020802@avtrex.com> (raw)
In-Reply-To: <20060929193704.GA30056@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Fri, Sep 29, 2006 at 12:33:44PM -0700, Joel Brobecker wrote:
>
>>What's the status at the compiler level, by the way? Still backed out?
>>If this is the case, I might have to work a bit harder to still be able
>>to reproduce the problem, because the compiler I have access to is
>>rebuilt nightly. I should have made a copy of the compiler :-/.
>
>
> Still backed out; presumably going to stay that way, since Jakub made
> some entirely correct points about why this is a bad idea.
>
That is not quite accurate. The original patch (r 116604) is still in
place. An additional patch (r 117114) was applied to correct most of
the problems with the original patch.
David Daney.
next prev parent reply other threads:[~2006-09-29 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 22:42 Daniel Jacobowitz
2006-09-29 19:33 ` Joel Brobecker
2006-09-29 19:37 ` Daniel Jacobowitz
2006-09-29 20:09 ` David Daney [this message]
2006-10-04 3:14 ` Joel Brobecker
2006-10-04 13:37 ` Daniel Jacobowitz
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=451D7D8D.7020802@avtrex.com \
--to=ddaney@avtrex.com \
--cc=drow@false.org \
--cc=gdb@sourceware.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