From: John David Anglin <dave.anglin@bell.net>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [committed] Fix typo in last change to pa.c
Date: Fri, 24 Oct 2014 01:40:00 -0000 [thread overview]
Message-ID: <BLU436-SMTP219EA1192FF7FC64D3C566097920@phx.gbl> (raw)
[-- Attachment #1: Type: text/plain, Size: 152 bytes --]
The attached change fixes a compile error caused by the last change to
pa.c.
Committed as obvious.
Dave
--
John David Anglin dave.anglin@bell.net
[-- Attachment #2: pa.c.d.txt --]
[-- Type: text/plain, Size: 586 bytes --]
2014-10-23 John David Anglin <danglin@gcc.gnu.org>
* config/pa/pa.c (pa_can_combine_p): Fix typo in last change.
Index: config/pa/pa.c
===================================================================
--- config/pa/pa.c (revision 216564)
+++ config/pa/pa.c (working copy)
@@ -9067,7 +9073,7 @@
basic_block bb = BLOCK_FOR_INSN (anchor);
if (insn_code_number < 0
|| (extract_insn (new_rtx),
- !constrain_operands (1, get_preferred_alternatives (new_rtx, bb)))
+ !constrain_operands (1, get_preferred_alternatives (new_rtx, bb))))
return 0;
if (reversed)
reply other threads:[~2014-10-23 23:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BLU436-SMTP219EA1192FF7FC64D3C566097920@phx.gbl \
--to=dave.anglin@bell.net \
--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).