Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>,
	"Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] Prepare Solaris x86 for 64-bit Solaris 10
Date: Sat, 30 Oct 2004 21:59:00 -0000	[thread overview]
Message-ID: <418400B0.50006@gnu.org> (raw)
In-Reply-To: <200410302113.i9ULDPPR009389@elgar.sibelius.xs4all.nl>

Mark Kettenis wrote:
>    Date: Sat, 30 Oct 2004 15:52:58 -0400
>    From: Andrew Cagney <cagney@gnu.org>
> 
>    Mark Kettenis wrote:
>    > Including a .c file is perhaps a bit unorthodox, but this really is
>    > the most elegant way I can think of to solve the issue with the
>    > upcoming 64-bit Solaris 10.
> 
>    Why not have 368-sol2-nat inherit i386v4-nat's target vector?
> 
> There's nothing there to inherit :-(.  I'm still thinking about the
> proper way to regset-ize fill_gregset(), fill_fpregset(),
> supply_gregset() and supply_fpregset() in relation to the SVR4-like
> /proc filesystem.
> 
> Oh, and I'm slowly beating the /proc support into shape such that I
> can it can be inherited.  Will take some time though before this
> becomes reality.

Sounds like something Joseph could help with.  He's the one with the 
immediate desire to get sol10/amd64 supported.

What we're not going to add is screwed up #include inheritance, can you 
revert that?

Andrew


  reply	other threads:[~2004-10-30 21:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-30 19:51 Mark Kettenis
2004-10-30 19:59 ` Joseph S. Myers
2004-10-30 20:53 ` Andrew Cagney
2004-10-30 21:13   ` Mark Kettenis
2004-10-30 21:59     ` Andrew Cagney [this message]
2004-10-31 15:35       ` Mark Kettenis
2004-10-31 15:58         ` Andrew Cagney
2004-10-31 21:24         ` Joseph S. Myers

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=418400B0.50006@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=mark.kettenis@xs4all.nl \
    /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