From: Thiemo Seufer <ths@networkno.de>
To: gdb-patches@sourceware.org,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: [rfc] Propagate constants into MIPS ABI routines, remove some knobs
Date: Tue, 01 May 2007 23:10:00 -0000 [thread overview]
Message-ID: <20070501231043.GF30083@networkno.de> (raw)
In-Reply-To: <20070501203647.GB23630@caradoc.them.org>
Daniel Jacobowitz wrote:
> This patch removes the "set mips stack-arg-size" and "set mips
> saved-gpreg-size" commands. As far as I can tell, they are obsoleted
> by "set mips abi". saved-gpreg-size was originally added for EABI
> -mgp32, which was not setting any e_flags bit that GDB could use to
> identify it; but nowadays we have an ABI marker in a section name, and
> we have the "set mips abi" command to specify it manually.
>
> So I replaced uses of the separate mips_stack_argsize with
> mips_abi_regsize, and then I propagated constant ABI register sizes
> into the n32, n64, o32, and o64 routines and deleted some of the
> obvious resulting dead code. If we've decided to have separate
> implementations for all of these we may as well make them more
> readable. I have a lot of ABI-related failures on mips64-linux,
> which I'll track down some other time.
>
> Maciej, do you know of anyone who needs to use the stack-arg-size /
> saved-gpreg-size commands? I couldn't find any uses when I searched
> for them. I didn't touch the FP options in this pass.
Maybe we should have a .mdebug.abi32-fp64 ABI marker for -mabi=32 -mfp64
objects. I probably should also move over to binutils so it can handle
assembler files. What do you think?
Thiemo
next prev parent reply other threads:[~2007-05-01 23:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 20:37 Daniel Jacobowitz
2007-05-01 23:10 ` Thiemo Seufer [this message]
2007-05-01 23:40 ` Daniel Jacobowitz
2007-05-02 3:04 ` Eli Zaretskii
2007-05-02 11:07 ` Daniel Jacobowitz
2007-05-02 19:07 ` Eli Zaretskii
2007-05-02 13:07 ` Maciej W. Rozycki
2007-05-02 13:29 ` Daniel Jacobowitz
2007-05-02 13:40 ` Maciej W. Rozycki
2007-05-16 14:17 ` Daniel Jacobowitz
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=20070501231043.GF30083@networkno.de \
--to=ths@networkno.de \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.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