public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Douglas Mencken <dougmencken@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Iain Sandoe <iain@codesourcery.com>
Subject: Re: Please accept this commit for the trunk
Date: Wed, 07 Feb 2018 23:52:00 -0000	[thread overview]
Message-ID: <706C3A3C-7CA8-44C8-8C70-CC330E0C0FBB@comcast.net> (raw)
In-Reply-To: <CACYvZ7g7G83aYi6mOp_6Z-bb4eSLd+=UObwvY9nak=35+iVqig@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

On Feb 5, 2018, at 8:42 AM, Douglas Mencken <dougmencken@gmail.com> wrote:
> 
> I’m about
> 
> “ [PATCH 2/4] [Darwin,PPC] Remove uses of LR in
> restore_world ” https://gcc.gnu.org/bugzilla/attachment.cgi?id=42304
> 
> look at bug #84113 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84113 for
> more info
> 
> “ One important question ’s yet: Why this patch has been ignored despite
> it’s been made just in time? ”

I dusted the pointed to patch off and check it in.  Let us know how it goes.

Does this resolve all of PR84113?  If so, I can push the bug along.

What PR was the attachment url from?

Thanks for your help.


[-- Attachment #2: ppc-darwin.patch.txt --]
[-- Type: text/plain, Size: 1358 bytes --]

2018-02-07  Iain Sandoe  <iain@codesourcery.com>

	* config/rs6000/altivec.md (*restore_world): Remove LR use.
	* config/rs6000/predicates.md (restore_world_operation): Adjust op
	count, remove one USE.

Index: gcc/config/rs6000/altivec.md
===================================================================
--- gcc/config/rs6000/altivec.md	(revision 257471)
+++ gcc/config/rs6000/altivec.md	(working copy)
@@ -419,7 +419,6 @@
 (define_insn "*restore_world"
  [(match_parallel 0 "restore_world_operation"
                   [(return)
-		   (use (reg:SI LR_REGNO))
                    (use (match_operand:SI 1 "call_operand" "s"))
                    (clobber (match_operand:SI 2 "gpc_reg_operand" "=r"))])]
  "TARGET_MACHO && (DEFAULT_ABI == ABI_DARWIN) && TARGET_32BIT"
Index: gcc/config/rs6000/predicates.md
===================================================================
--- gcc/config/rs6000/predicates.md	(revision 257471)
+++ gcc/config/rs6000/predicates.md	(working copy)
@@ -1295,13 +1295,12 @@
   rtx elt;
   int count = XVECLEN (op, 0);
 
-  if (count != 59)
+  if (count != 58)
     return 0;
 
   index = 0;
   if (GET_CODE (XVECEXP (op, 0, index++)) != RETURN
       || GET_CODE (XVECEXP (op, 0, index++)) != USE
-      || GET_CODE (XVECEXP (op, 0, index++)) != USE
       || GET_CODE (XVECEXP (op, 0, index++)) != CLOBBER)
     return 0;
 

  reply	other threads:[~2018-02-07 23:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 16:42 Douglas Mencken
2018-02-07 23:52 ` Mike Stump [this message]
     [not found]   ` <CACYvZ7jH6LG6o7VXfhFrEw=B2kCzfU8qj=Ry9Fat5FGPK-rmJQ@mail.gmail.com>
2018-02-08 17:40     ` Fwd: " Douglas Mencken
2018-02-08 20:36   ` Segher Boessenkool
2018-02-09  2:06     ` Mike Stump
2018-02-09 17:14       ` Segher Boessenkool

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=706C3A3C-7CA8-44C8-8C70-CC330E0C0FBB@comcast.net \
    --to=mikestump@comcast.net \
    --cc=dougmencken@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iain@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).