Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix building gdb-7.0 on x86_64-*-freebsd
Date: Sat, 17 Oct 2009 00:17:00 -0000	[thread overview]
Message-ID: <20091017001631.GA60006@troutmask.apl.washington.edu> (raw)
In-Reply-To: <20091016232238.GV5288@adacore.com>

On Fri, Oct 16, 2009 at 04:22:38PM -0700, Joel Brobecker wrote:
> [gdb-patches added back]
> 
> I sent a private note to Mark asking whether he wanted to review
> this patch and he approved it.   The version number was further
> refined based on feedback from the FreeBSD developers, I believe.
> 
> So I checked in this change for Mark (who is currently traveling).
> 
> What I am not sure I understand completely is whether this patch
> is required for gdb-7.x or not.  On the one hand, you say it should
> compile fine on FreeBSD 8.0 (which is coming up for release, hopefully
> soon).  But then you say that the fields has been removed from
> 8.0 and mainline, and so it's needed.  I wonder if it was just a typo
> meaning ix86-*-freebsd instead of x86_64-*-freebsd.  If this is the
> case, then the patch is needed for gdb-7.1 to build on FreeBSD 8.x
> and later.

The patch is required for x86_64-*-freebsd.

I'm deleting a bunch of context to get to the relevant portion
of the diff.

> > +#if (__FreeBSD_version <  800075)
> >    regcache_raw_supply (regcache, AMD64_DS_REGNUM, &pcb->pcb_ds);
> >    regcache_raw_supply (regcache, AMD64_ES_REGNUM, &pcb->pcb_es);
> >    regcache_raw_supply (regcache, AMD64_FS_REGNUM, &pcb->pcb_fs);
> >    regcache_raw_supply (regcache, AMD64_GS_REGNUM, &pcb->pcb_gs);
> > +#endif

The above number 800075 means that any version of FreeBSD
with __FreeBSD_version less than 800075 will have a struct pcb
with the pcb_{fged} members.  Any version with __FreeBSD_version
greater than or equal to 800075 will have these structure members
removed.  The '8' in 800075 signifies the FreeBSD 8-branch.
The '75' signifies that 75 changes have occurred on the FreeBSD
8-branch that might need special handling.  The removal of the
struct members occurred on 2009-04-01 while the version number
was bumped to 800075 on 2009-04-06.  It's the closest version
number that will work in the '#if (...)'  that will allow the
gdb-7.x branch to build on all versions of FreeBSD on the amd64
architecture including the 8.0-Release Candidates (ie., the 
beta releases).

-- 
Steve


  reply	other threads:[~2009-10-17  0:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 21:55 Steve Kargl
     [not found] ` <20091014050550.GV5272@adacore.com>
     [not found]   ` <1530bbfee75f68f9c32262460f1ec7f9.squirrel@webmail.xs4all.nl>
     [not found]     ` <20091015021317.GD5288@adacore.com>
     [not found]       ` <20091015230013.GA49371@troutmask.apl.washington.edu>
2009-10-16 23:22         ` Joel Brobecker
2009-10-17  0:17           ` Steve Kargl [this message]
2009-10-17  4:19             ` Joel Brobecker
2009-10-17  5:06             ` Sérgio Durigan Júnior
2009-10-19 19:53               ` Joel Brobecker
2009-10-19 20:34                 ` Steve Kargl

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=20091017001631.GA60006@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --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