From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: gdb-patches@sourceware.org
Subject: Re: Borland fastcall support (i386)
Date: Sun, 05 Apr 2009 21:29:00 -0000 [thread overview]
Message-ID: <390385D8-5B6E-4844-8940-4002C012140F@elis.ugent.be> (raw)
In-Reply-To: <m3k561aiw4.fsf@fleche.redhat.com>
On 03 Apr 2009, at 16:53, Tom Tromey wrote:
>>>>>> "Jonas" == Jonas Maebe <jonas.maebe@elis.ugent.be> writes:
>
> Jonas> b) one of the modified headers (include/elf/dwarf2.h) appears
> to be
> Jonas> imported from gcc, so I guess I should submit that change to
> gcc first
> Jonas> or instead?
>
> I recently noticed that the src and gcc versions of this file have
> diverged. Oops. It would be good to have just a single copy; most of
> the work to be done here is in the gcc repository.
I've submitted the patch to gcc-patches.
> The 'master' branch of Archer's git repository is updated from CVS
> head semi-regularly. If you are using some other branch, then yeah,
> there may be other changes in the way.
The patch was against the "master" branch. I've made some minor
adjustments to it in the mean time, and I've also received word from
my employer's contracts department that there will be no problem with
getting a disclaimer :)
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)
Thanks,
Jonas
next prev parent reply other threads:[~2009-04-05 21:29 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 [this message]
2009-04-06 2:15 ` Tom Tromey
2009-04-06 2:54 ` Daniel Jacobowitz
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=390385D8-5B6E-4844-8940-4002C012140F@elis.ugent.be \
--to=jonas.maebe@elis.ugent.be \
--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