From: Andrew Cagney <ac131313@ges.redhat.com>
To: Michael Snyder <msnyder@redhat.com>, Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] 64-bit support for Irix 6
Date: Thu, 01 Aug 2002 16:38:00 -0000 [thread overview]
Message-ID: <3D49C678.1020106@ges.redhat.com> (raw)
In-Reply-To: <3D49A814.A75E2C66@redhat.com>
> If you mean mips_push_arguments, then that is already part of the
>> multi-arch vector.
>
>
> Umm... no it isn't. I can see why you think it is
> (set_gdbarch_push_arguments is called), but the call to
> PUSH_ARGUMENTS is still going thru the macro in tm-mips.h.
I think the macro can be yanked. Not sure why it has remained.
>> Just don't forget that any changes to that function
>> should be multi-arch friendly.
>
>
> So I can use code similar to what is already there
> (eg. "if (tdep->mips_abi == MIPS_ABI_N32)")
> rather than splitting the function into variously
> mips_n32_push_argument etc.?
Adding ``if (.. == MIPS_ABI_N32)'' wouldn't be multi-arch unfriendly.
However, it would definitly be GDB developer/maintainer unfriendly. The
MIPS is held up as an example of how to not implement the push arguments
function.
If the MIPS doesn't support your new ABI then I think you are way better
off creating a new mips_ABI_push_arguments() function and model its
implementation on the Arm. Even cloning mips_push_arguments() and then
stripping out all the irrelenvant guff would be better.
That way you would be sure it didn't break any of the other ABIs.
enjoy,
Andrew
prev parent reply other threads:[~2002-08-01 23:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 11:23 Kevin Buettner
2002-08-01 8:11 ` Andrew Cagney
2002-08-01 9:53 ` Kevin Buettner
2002-08-01 10:42 ` Andrew Cagney
2002-08-01 13:08 ` Kevin Buettner
2002-08-01 13:28 ` Andrew Cagney
2002-08-01 16:17 ` Kevin Buettner
2002-08-01 13:54 ` Michael Snyder
2002-08-01 14:25 ` Andrew Cagney
2002-08-01 14:47 ` Michael Snyder
2002-08-01 16:38 ` Andrew Cagney [this message]
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=3D49C678.1020106@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=msnyder@redhat.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