From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>, gcc-patches@gcc.gnu.org
Cc: jasonwucj@gmail.com, shiva0217@gmail.com
Subject: Re: [PATCH] nds32: Fix casesi (PR70668)
Date: Thu, 28 Apr 2016 15:59:00 -0000 [thread overview]
Message-ID: <f4d821ff-1b2d-384a-c8e3-9fda88d37674@redhat.com> (raw)
In-Reply-To: <21f11c9d07b31a70a5372333865564073fb68519.1461857901.git.segher@kernel.crashing.org>
On 04/28/2016 09:45 AM, Segher Boessenkool wrote:
> Expanders do not have more elements in the operands array than declared
> in the pattern. So, we cannot use operands[5] here. Instead just
> declare and use another rtx.
>
> Built with a cross compiler; not tested otherwise. Is this okay for trunk?
>
>
> Segher
>
>
> 2016-04-28 Segher Boessenkool <segher@kernel.crashing.org>
>
> PR target/70668
> * config/nds32/nds32.md (casesi): Don't access the operands array
> out of bounds.
OK.
jeff
prev parent reply other threads:[~2016-04-28 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 15:46 Segher Boessenkool
2016-04-28 15:59 ` Jeff Law [this message]
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=f4d821ff-1b2d-384a-c8e3-9fda88d37674@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jasonwucj@gmail.com \
--cc=segher@kernel.crashing.org \
--cc=shiva0217@gmail.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).