From: Richard Sandiford <rdsandiford@googlemail.com>
To: Matthew Fortune <Matthew.Fortune@imgtec.com>
Cc: "binutils\@sourceware.org" <binutils@sourceware.org>, "Moore\,
Catherine" <Catherine_Moore@mentor.com>,
"macro\@codesourcery.com" <macro@codesourcery.com>,
"Joseph Myers \(joseph\@codesourcery.com\)"
<joseph@codesourcery.com>
Subject: Re: [PATCHv4] Add support for O32 FPXX ABI
Date: Sun, 27 Jul 2014 09:17:00 -0000 [thread overview]
Message-ID: <87fvhnma8u.fsf@talisman.default> (raw)
In-Reply-To: <6D39441BF12EF246A7ABCE6654B0235320EB4042@LEMAIL01.le.imgtec.org> (Matthew Fortune's message of "Fri, 25 Jul 2014 15:00:19 +0000")
Matthew Fortune <Matthew.Fortune@imgtec.com> writes:
> @@ -258,6 +258,10 @@ struct mips_set_options
> Changed by .set singlefloat or .set doublefloat, command-line options
> -msingle-float or -mdouble-float. The default is false. */
> bfd_boolean single_float;
> +
> + /* 1 if single-precision operations on odd-numbered registers are
> + not allowed (even if supported by ISA_HAS_ODD_SINGLE_FPR). */
> + int nooddspreg;
> };
I think "oddspreg" would be better, partly for consistency with the
ISA_HAS_* macro and partly to avoid the double negative in things like:
bfd_boolean oddspreg = (ISA_HAS_ODD_SINGLE_FPR (mips_opts.isa, mips_opts.arch)
|| FPR_SIZE == 64)
&& !mips_opts.nooddspreg;
> - /* Single-precision coprocessor loads and moves are OK too. */
> + /* Single-precision coprocessor loads and moves are OK for 32-bit registers,
> + otherwise it depends on oddspreg. */
> if ((insn->pinfo & FP_S)
> - && (insn->pinfo & (INSN_COPROC_MEMORY_DELAY | INSN_STORE_MEMORY
> - | INSN_LOAD_COPROC_DELAY | INSN_COPROC_MOVE_DELAY)))
> + && (insn->pinfo & INSN_FP_32_MOVE))
> + return FPR_SIZE == 32 || oddspreg;
Why do you need a new flag for this?
> @@ -18643,7 +18687,16 @@ md_mips_end (void)
> file_mips_check_options ();
>
> /* Set a floating-point ABI if the user did not. */
> - if (!obj_elf_seen_attribute (OBJ_ATTR_GNU, Tag_GNU_MIPS_ABI_FP))
> + if (obj_elf_seen_attribute (OBJ_ATTR_GNU, Tag_GNU_MIPS_ABI_FP))
> + {
> +
> + /* Perform consistency checks on the floating-point ABI. */
Excess blank line.
Looks good otherwise, thanks.
Richard
next prev parent reply other threads:[~2014-07-27 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 15:00 Matthew Fortune
2014-07-27 9:17 ` Richard Sandiford [this message]
2014-07-28 12:05 ` Matthew Fortune
2014-07-28 20:56 ` Richard Sandiford
2014-07-28 21:14 ` Maciej W. Rozycki
2014-07-29 10:33 ` Matthew Fortune
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=87fvhnma8u.fsf@talisman.default \
--to=rdsandiford@googlemail.com \
--cc=Catherine_Moore@mentor.com \
--cc=Matthew.Fortune@imgtec.com \
--cc=binutils@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=macro@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).