public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@arm.com>
To: gcc-patches@gcc.gnu.org
Subject: Ping: [06/11] [mips] Fix ambiguous .md attribute uses
Date: Fri, 12 Jul 2019 08:24:00 -0000	[thread overview]
Message-ID: <mptims7hdlu.fsf_-_@arm.com> (raw)
In-Reply-To: <mpt1rz4y0hs.fsf@arm.com> (Richard Sandiford's message of "Fri,	05 Jul 2019 16:17:19 +0100")

Ping.  I think this is the only one of the series left.

(I should probably have treated the patch as obvious, but it always
seems wrong to do that retrospectively.)

Thanks,
Richard

Richard Sandiford <richard.sandiford@arm.com> writes:
> This patch is part of a series that fixes ambiguous attribute
> uses in .md files, i.e. cases in which attributes didn't use
> <ITER:ATTR> to specify an iterator, and in which <ATTR> could
> have different values depending on the iterator chosen.
>
> No behavioural change -- produces the same code as before.
>
>
> 2019-07-05  Richard Sandiford  <richard.sandiford@arm.com>
>
> gcc/
> 	* config/mips/micromips.md (*movep<MOVEP1:mode><MOVEP2:mode>):
> 	Explicitly use <MOVEP1:MODE> for the mode attribute.
>
> Index: gcc/config/mips/micromips.md
> ===================================================================
> --- gcc/config/mips/micromips.md	2019-03-08 18:15:39.000731609 +0000
> +++ gcc/config/mips/micromips.md	2019-07-05 15:07:29.083455268 +0100
> @@ -133,5 +133,5 @@ (define_insn "*movep<MOVEP1:mode><MOVEP2
>      return "movep\t%2,%0,%z3,%z1";
>  }
>    [(set_attr "type" "move")
> -   (set_attr "mode" "<MODE>")
> +   (set_attr "mode" "<MOVEP1:MODE>")
>     (set_attr "can_delay" "no")])

  reply	other threads:[~2019-07-12  8:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05 15:08 [00/11] Diagnose " Richard Sandiford
2019-07-05 15:10 ` [01/11] [arch64] Fix " Richard Sandiford
2019-07-05 15:12 ` [02/11] [arm] " Richard Sandiford
2019-07-05 15:52   ` Kyrill Tkachov
2019-07-05 15:13 ` [03/11] [amdgcn] " Richard Sandiford
2019-07-05 15:43   ` Andrew Stubbs
2019-07-05 15:15 ` [04/11] [h8300] " Richard Sandiford
2019-07-05 17:23   ` Jeff Law
2019-07-05 15:17 ` [05/11] [i386] " Richard Sandiford
2019-07-05 15:45   ` Uros Bizjak
2019-07-05 15:19 ` [06/11] [mips] " Richard Sandiford
2019-07-12  8:24   ` Richard Sandiford [this message]
2019-07-15 20:24     ` Ping: " Jim Wilson
2019-07-05 15:20 ` [07/11] [riscv] " Richard Sandiford
2019-07-08  4:41   ` Jim Wilson
2019-07-05 15:22 ` [08/11] [rs6000] " Richard Sandiford
2019-07-05 16:03   ` Segher Boessenkool
2019-07-05 16:38     ` Richard Sandiford
2019-07-05 17:26       ` Segher Boessenkool
2019-07-05 17:38         ` Richard Sandiford
2019-07-05 15:27 ` [09/11] [s390] " Richard Sandiford
2019-07-05 15:59   ` Andreas Krebbel
2019-07-05 15:31 ` [10/11] Use file_location for md_reader's ptr_loc Richard Sandiford
2019-07-05 15:39 ` [11/11] Report ambiguous uses of .md attributes 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=mptims7hdlu.fsf_-_@arm.com \
    --to=richard.sandiford@arm.com \
    --cc=gcc-patches@gcc.gnu.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).