public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rdsandiford@googlemail.com>
To: Matthew Fortune <Matthew.Fortune@imgtec.com>
Cc: "binutils\@sourceware.org" <binutils@sourceware.org>,
	 Rich Fuhler <Rich.Fuhler@imgtec.com>
Subject: Re: [PATCH][MIPS] Implement .module directive
Date: Tue, 20 May 2014 18:00:00 -0000	[thread overview]
Message-ID: <87tx8kib4k.fsf@talisman.default> (raw)
In-Reply-To: <6D39441BF12EF246A7ABCE6654B02353538578@LEMAIL01.le.imgtec.org>	(Matthew Fortune's message of "Tue, 20 May 2014 14:07:28 +0000")

Matthew Fortune <Matthew.Fortune@imgtec.com> writes:
> +  if (file_mips_opts.fp < 0)
> +    {
> +      /* No user specified float register size.
> +	 ??? GAS treats single-float processors as though they had 64-bit
> +	 float registers (although it complains when double-precision
> +	 instructions are used).  As things stand, saying they have 32-bit
> +	 registers would lead to spurious "register must be even" messages.
> +	 So here we assume float registers are never smaller than the
> +	 integer ones.  */
> +      if (file_mips_opts.gp == 64)
> +	/* 64-bit integer registers implies 64-bit float registers.  */
> +	file_mips_opts.fp = 64;
> +      else if ((file_mips_opts.ase & FP64_ASES)
> +	       && ISA_HAS_64BIT_FPRS (file_mips_opts.isa))
> +	/* -mips3d and -mdmx imply 64-bit float registers, if possible.  */
> +	file_mips_opts.fp = 64;

I assume you'll update this for the other patch.  Or we could just
make the comment vaguer: Handle ASEs that imply 64-bit float registers.

> +  /* MIPS3D and MDMX require 64-bit FPRs, so -mfp32 should stop those
> +     ASEs from being selected implicitly.  */
> +  if (file_mips_opts.fp != 64)
> +    file_ase_explicit |= ASE_MIPS3D | ASE_MDMX | ASE_MSA;

Same here.

> @@ -787,7 +787,7 @@ if { [istarget mips*-*-vxworks*] } {
>      run_dump_test "relax-swap1-mips2"
>      run_dump_test "relax-swap2"
>      run_dump_test_arches "relax-swap3"	[mips_arch_list_all]
> -    run_list_test_arches "relax-bc1any" "-mips3d -relax-branch" \
> +    run_list_test_arches "relax-bc1any" "-mips3d -64 -relax-branch" \
>  					[mips_arch_list_matching mips64 \
>  					    !micromips]
>      run_list_test_arches "relax-bposge" "-mdsp -relax-branch" \

Not all targets compile in support for n32 and n64, so -mabi=o64 would
be better than -64.

OK otherwise, thanks.

Richard

  reply	other threads:[~2014-05-20 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 14:07 Matthew Fortune
2014-05-20 18:00 ` Richard Sandiford [this message]
2014-05-20 21:41   ` Matthew Fortune
2014-05-20 22:07     ` Richard Sandiford

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=87tx8kib4k.fsf@talisman.default \
    --to=rdsandiford@googlemail.com \
    --cc=Matthew.Fortune@imgtec.com \
    --cc=Rich.Fuhler@imgtec.com \
    --cc=binutils@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).