Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jonas Maebe <jonas.maebe@elis.ugent.be>
Cc: gdb-patches@sourceware.org
Subject: Re: Borland fastcall support (i386)
Date: Mon, 06 Apr 2009 02:54:00 -0000	[thread overview]
Message-ID: <20090406025401.GA29656@caradoc.them.org> (raw)
In-Reply-To: <390385D8-5B6E-4844-8940-4002C012140F@elis.ugent.be>

On Sun, Apr 05, 2009 at 11:28:57PM +0200, Jonas Maebe wrote:
> I've continued working on gdb to also support calling Pascal methods, and 
> I've run a bit into a hitch: the calling_convention field is part of a 
> union that also contains cplus_stuff (inside main_type in gdbtypes.h), and 
> I need both for methods using a non-standard calling convention. Is there 
> a problem with moving the calling_convention field out of the 
> type_specific union, and if not, is there anything I should pay particular 
> attention to? (other than adjusting a couple of macros)

Why is cplus_stuff used in this case?

    /* CPLUS_STUFF is for TYPE_CODE_STRUCT.  It is initialized to point to
       cplus_struct_default, a default static instance of a struct
       cplus_struct_type. */

    struct cplus_struct_type *cplus_stuff;

Methods don't have base classes, methods of their own, or so forth.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2009-04-06  2:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 13:39 Jonas Maebe
2009-04-03 14:55 ` Tom Tromey
2009-04-05 21:29   ` Jonas Maebe
2009-04-06  2:15     ` Tom Tromey
2009-04-06  2:54     ` Daniel Jacobowitz [this message]
2009-04-06  6:20       ` 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=20090406025401.GA29656@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jonas.maebe@elis.ugent.be \
    /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