Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jonas.maebe@elis.ugent.be
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch] Set calling convention of methods
Date: Wed, 22 Apr 2009 22:16:00 -0000	[thread overview]
Message-ID: <200904222215.n3MMF0p2006994@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <691B0BA8-C606-42FF-A796-76CC9C31556A@elis.ugent.be> (message 	from Jonas Maebe on Wed, 22 Apr 2009 19:45:22 +0200)

> From: Jonas Maebe <jonas.maebe@elis.ugent.be>
> Date: Wed, 22 Apr 2009 19:45:22 +0200
> 
> On 20 Apr 2009, at 20:25, Tom Tromey wrote:
> 
> > "dwarf2.h" is not included in many places in gdb, and not by any
> > header.  So, assuming your uses of this field will end up in truly
> > generic code, I think the thing to do is introduce a new enum, and
> > then translate values in the DWARF reader.  It is tempting to simply
> > reuse the DWARF enum internally, but I think that goes against the GDB
> > style.
> 
> Ok, I can adapt my patch to clean that up. I'd prefer my i386 Borland  
> fastcall patch to be committed first though, since changing this  
> calling convention stuff would also affect that patch. Is that  
> possible given my current in-progress state as far as the copyright  
> assignment process is concerned? If so, Mark, could you tell me  
> whether anything should still be changed in the last version I sent you?

That last diff is ok with me, but Tom has a point here.  The effect on
the i386-specific bits should be fairly minimal.

The copyright assignment process needs to be dealt with before we move
forward though.


  parent reply	other threads:[~2009-04-22 22:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 19:51 Jonas Maebe
2009-04-10 17:34 ` Tom Tromey
2009-04-20  8:40   ` Jonas Maebe
2009-04-20 18:27     ` Tom Tromey
2009-04-22 17:45       ` Jonas Maebe
2009-04-22 19:22         ` Tom Tromey
2009-04-22 22:16         ` Mark Kettenis [this message]
2009-06-04  8:23           ` Jonas Maebe
2009-06-04 18:19             ` Tom Tromey
2009-06-10 20:44               ` Jonas Maebe
2009-06-18 21:45                 ` Fwd: " Jonas Maebe
2009-09-30  0:02                 ` Joel Brobecker
2009-09-30 11:18                   ` Jonas Maebe
2009-09-30 14:54                     ` Jonas Maebe
2009-09-30 15:22                       ` Mark Kettenis
2009-09-30 16:25                       ` Joel Brobecker
2009-10-01  9:18                         ` Jonas Maebe
2009-10-01 22:04                           ` Joel Brobecker
2009-10-02  9:21                           ` Mark Kettenis
2009-09-30 16:10                     ` Joel Brobecker
2009-09-30 17:36                       ` Joel Brobecker
2009-09-30 16:47                     ` Tom Tromey
2009-09-30 17:32                       ` Joel Brobecker
2009-09-30 17:35                         ` Tom Tromey
2009-10-01  9:21                           ` Jonas Maebe
2009-11-03  9:43                         ` Jonas Maebe
2009-11-03 14:19                           ` Joel Brobecker
2009-07-06 20:50               ` Jonas Maebe

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=200904222215.n3MMF0p2006994@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=jonas.maebe@elis.ugent.be \
    --cc=tromey@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