Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Linux-specific ppc32 ABI
Date: Fri, 11 Jan 2008 15:58:00 -0000	[thread overview]
Message-ID: <20080111155733.GA3240@caradoc.them.org> (raw)
In-Reply-To: <1200066920.26270.9.camel@gargoyle>

On Fri, Jan 11, 2008 at 01:55:20PM -0200, Luis Machado wrote:
> > How about an extra flag inside the gdbarch_tdep structure that
> > you'll be using inside the push dummy call?  It would be a shame
> > duplicate this function when most of it is common.
> 
> Yes. This would work, but putting linux specific code inside the
> ppc-sysv-tdep.c file doesn't look quite right. But if there isn't a
> better way of doing this, should be OK.

For practical reasons, this is how it is usually done.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-01-11 15:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10 19:00 Luis Machado
2008-01-10 19:13 ` Daniel Jacobowitz
2008-01-10 19:26   ` Thiago Jung Bauermann
2008-01-11  6:06 ` Joel Brobecker
2008-01-11 15:55   ` Luis Machado
2008-01-11 15:58     ` Daniel Jacobowitz [this message]
2008-01-11 21:26       ` Luis Machado
2008-01-25 16:13         ` Thiago Jung Bauermann
2008-01-25 16:51           ` Thiago Jung Bauermann
2008-01-26 18:18           ` Mark Kettenis
2008-01-26 19:08             ` Joseph S. Myers
2008-01-26 19:10               ` Mark Kettenis
2008-01-28 20:32             ` Thiago Jung Bauermann
2008-02-01 21:42             ` Thiago Jung Bauermann
2008-02-01 22:39             ` Joel Brobecker
2008-02-02  0:27               ` Mark Kettenis
2008-02-06  3:57                 ` Thiago Jung Bauermann

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=20080111155733.GA3240@caradoc.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.com \
    /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