Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jonas Maebe <jonas.maebe@elis.ugent.be>
Cc: gdb-patches@sourceware.org
Subject: Re: Borland fastcall support (i386)
Date: Fri, 03 Apr 2009 14:55:00 -0000	[thread overview]
Message-ID: <m3k561aiw4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <E934FC11-D059-4FC9-B15C-5F56484AC11A@elis.ugent.be> (Jonas Maebe's message of "Fri\, 3 Apr 2009 15\:38\:13 +0200")

>>>>> "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.

Jonas> c) the patch is against Archer rather than against CVS head (although
Jonas> I don't know how different they are as far as the modified files are
Jonas> concerned)

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.

Alternatively, you could also pull from the gdb git repository and use
gdb/master, which I think is updated every half hour.

Tom


  reply	other threads:[~2009-04-03 14:55 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 [this message]
2009-04-05 21:29   ` Jonas Maebe
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=m3k561aiw4.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --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