Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Roland Schwingel <roland@onevision.com>
To: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH v3] Add dll trampoline code handling for windows 64bit
Date: Fri, 30 Mar 2012 06:47:00 -0000	[thread overview]
Message-ID: <4F7556D4.4010404@onevision.com> (raw)

Hi Joel,

gdb-patches-owner@sourceware.org wrote on 29.03.2012 20:21:02:
 > > 2012-03-16  Roland Schwingel <roland.schwingel@onevision.com>
 > >
 > >         * amd64-windows-tdep.c: #include "frame.h".
 > >         (amd64_windows_skip_trampoline_code): New function.
 > >         (amd64_windows_init_abi): Add trampoline registration.
 >
 > No one reviewed þhe patch as far as I can tell, I am sorry about that.
 > As a general guideline, it's OK to ping us every week or two...
Thanks for taking the time and looking at it.

 > I think the code looks pretty good, and you can commit, with a couple
 > of very minor almost-nitpicky little comments (a apologize for asking
 > for your forgiveness)...
No problem.

 > Hmmm, I actually cannot find any copyright assignment for you on
 > file. Do you have one? Or is this done on behalf of your employer
 > who might have one? Please let me know... We can give you write-
 > after-approval priviledges as soon as we have confirmed that you
 > do have an assignment on file.
Tom Tromey sent me the necessary informations on march 15th. One day 
later I sent out the mail to fsf-records@gnu.org but yet have not 
received *any* response. I asked Tom some days ago and he told me to 
wait for some more days before I send in a ping. I already got a CVS 
account on sourceware and I am just awaiting my okays ...

 > > +      /* Get address of function pointer at end of pc.  */
 > > +      CORE_ADDR indirect_addr = pc + offset + 6;
 >
 > I think it would be useful to explain where the magic constant "6"
 > comes from... I'd almost write the expression "pc + 6 + offset".
PC relative instructions always count starting from the end of the 
instruction itself. pc in this situation points to the beginning of the 
instruction. The instruction itself is (with operands) 6 bytes long. If 
you like to I will change the order of addition on commit.

 > > +      struct minimal_symbol *indsym =
 > > +        indirect_addr ? lookup_minimal_symbol_by_pc 
(indirect_addr) : 0;
 > > +      const char *symname = indsym ? SYMBOL_LINKAGE_NAME (indsym) : 0;
 >
 > I'd rather you used NULL instead of 0, even if we're pretty much
 > guaranteed that NULL will always be zero. That's really nit-picky,
 > but it seems clearer that way, at least for me.
Sure I can do that (on commit). I did it the same way as the 32bit code 
in i386_pe_skip_trampoline_code() does hoping it would be easier for the 
approver if he sees familiar code ...

The other 2 formatting I will also correct on commit. But if you want I 
am doing a 4th version of my patch with your suggested changes and send 
it in. Elsewise I will sit and wait until my assignment stuff gets done 
and commit it later on and avoid unneccessary noise.

Roland


             reply	other threads:[~2012-03-30  6:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30  6:47 Roland Schwingel [this message]
2012-03-30  9:15 ` Pedro Alves
  -- strict thread matches above, loose matches on Subject: below --
2012-03-16  9:56 Roland Schwingel
2012-03-29 18:21 ` Joel Brobecker

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=4F7556D4.4010404@onevision.com \
    --to=roland@onevision.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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