From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>,
gdb-patches@sourceware.org,
Richard Sandiford <rdsandiford@googlemail.com>
Subject: Re: [RFA] MIPS/GDB: Fix the handling of MIPS16 thunks
Date: Sat, 21 Apr 2012 18:55:00 -0000 [thread overview]
Message-ID: <CAN9gPaEmrh1R7Mn9=bwxSGnr33vO3KTmixYW3VGUp2DtJpyfOA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1204201519120.19835@tp.orcam.me.uk>
On Fri, Apr 20, 2012 at 11:40 AM, Maciej W. Rozycki
<macro@codesourcery.com> wrote:
> Hi Pedro,
>
> [Cc-ing Daniel for the question below.]
>
>> > + /* macro/2005-03-31: This hack skips over MIPS16 call thunks as
>>
>>
>> Eh, that long? Might want to update that date to the check in date,
>> or drop it. Otherwise it's just useless, IMO.
>
> Yes, sigh... And fair enough :) -- I'll tweak the date. The comment
> might need updating once new GCC's unwind information Richard mentioned
> has been tested.
>
> There's another note, that is even older, by Daniel -- Daniel, would you
> mind if I updated the date on your note to the check in date too -- IOW,
> do you continue to stand by it?
It's all the same to me. I haven't thought about that note since I
wrote it in 2004... I wasn't even at CodeSourcery yet.
--
Thanks,
Daniel
next prev parent reply other threads:[~2012-04-21 17:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 22:36 Maciej W. Rozycki
2012-04-11 19:16 ` Richard Sandiford
2012-04-12 13:09 ` Maciej W. Rozycki
2012-04-12 19:39 ` Richard Sandiford
2012-04-13 20:46 ` Maciej W. Rozycki
2012-04-20 14:54 ` Pedro Alves
2012-04-20 16:01 ` Maciej W. Rozycki
2012-04-21 18:55 ` Daniel Jacobowitz [this message]
2012-04-26 0:10 ` Maciej W. Rozycki
2012-04-26 13:10 ` Pedro Alves
2012-04-26 17:27 ` Maciej W. Rozycki
2012-04-26 13:23 ` gdb_test_multiple and empty $message Pedro Alves
2012-04-26 13:34 ` Pedro Alves
2012-04-26 14:31 ` Tom Tromey
2012-04-26 14:42 ` Joel Brobecker
2012-04-27 20:23 ` Maciej W. Rozycki
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='CAN9gPaEmrh1R7Mn9=bwxSGnr33vO3KTmixYW3VGUp2DtJpyfOA@mail.gmail.com' \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@codesourcery.com \
--cc=palves@redhat.com \
--cc=rdsandiford@googlemail.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