From: Kai Tietz <ktietz70@googlemail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Roland Schwingel <roland@onevision.com>,
gdb-patches@sourceware.org,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH v4] Add dll trampoline code handling for windows 64bit
Date: Wed, 25 Jul 2012 17:57:00 -0000 [thread overview]
Message-ID: <CAEwic4bshVyoozFjQO-UjzX+mhtj-jpK-w=0Li3FkwBdK+raDA@mail.gmail.com> (raw)
In-Reply-To: <4F79CABA.8010009@redhat.com>
Hello,
I have now this patch for a while on my radar. I contacted Roland
Schwingel about the status of his paperwork with FSF, and he told me
that he completed it. So I want to ping this patch for him, as he
isn't able to ping on that patch himself for the next week(s).
Regards,
Kai
2012/4/2 Pedro Alves <palves@redhat.com>:
> On 04/02/2012 03:53 PM, Roland Schwingel wrote:
>
>>> Please send an updated patch, so we have in the archives the exact
>>> patch as what is
>>> checked in, and in case some other maintainer wants to take a look,
>>> best have him look at
>>> the refreshed patch. In fact, if you had sent it already in that
>>> email, there'd have been
>>> no extra noise, right? ;-)
>> Regarding the noise right. But not regarding generating additional work.
>
>
> Sorry, I can't be sympathetic to that. You would be making the changes anyway.
> I can't believe that pasting a patch at the end of an email is extra work by
> any valid measure. What's real extra work is someone reading an out of
> date patch, and trying to figure out from several messages in a thread what
> would be the final state of the patch.
>
>> 2012-04-02 Roland Schwingel <roland.schwingel@onevision.com>
>
> ^
>
> Should be two spaces after your name.
>
>>
>> * amd64-windows-tdep.c: #include "frame.h".
>> (amd64_windows_skip_trampoline_code): New function.
>> (amd64_windows_init_abi): Add trampoline registration.
>
>
> On 04/02/2012 03:53 PM, Roland Schwingel wrote:
>> +/* Check win64 DLL jmp trampolines and find jump destination. */
>
> The correct spelling is "Win64" capitalized.
>
>> static void
>> amd64_windows_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
>> {
>> struct gdbarch_tdep *tdep = gdbarch_tdep (gdbarch);
>>
>> + /* Register trampoline handling code. */
>> + set_gdbarch_skip_trampoline_code (gdbarch, amd64_windows_skip_trampoline_code);
>
> A nit, but it'd be cleaner/clearer to put this after the amd64_init_abi call, or
> better, near the end of the function, after set_gdbarch_skip_main_prologue. The current
> code reads "initialize the base arch, then install overrides.". This new call
> here breaks that flow.
>
>> +
>> amd64_init_abi (info, gdbarch);
>>
>> /* On Windows, "long"s are only 32bit. */
>
>
> Having once written the equivalent arm-wince-tdep.c:arm_pe_skip_trampoline_code
> for ARM WinCE, this generally looks good to me too.
>
> --
> Pedro Alves
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
next prev parent reply other threads:[~2012-07-25 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 14:54 Roland Schwingel
2012-04-02 15:51 ` Pedro Alves
2012-07-25 17:57 ` Kai Tietz [this message]
2012-07-27 17:25 ` Pedro Alves
2012-07-30 6:57 Roland Schwingel
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='CAEwic4bshVyoozFjQO-UjzX+mhtj-jpK-w=0Li3FkwBdK+raDA@mail.gmail.com' \
--to=ktietz70@googlemail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=roland@onevision.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