From: Jeff Law <law@redhat.com>
To: janisjo@codesourcery.com
Cc: Janis Johnson <janis_johnson@mentor.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [testsuite] fix loop index for gcc.dg/webizer.c
Date: Tue, 15 Jan 2013 22:02:00 -0000 [thread overview]
Message-ID: <50F5D1D0.3040009@redhat.com> (raw)
In-Reply-To: <50F5D0B6.6000708@mentor.com>
On 01/15/2013 02:57 PM, Janis Johnson wrote:
> Execution of test gcc.dg/webizer.c fails with a segfault for
> powerpc-eabi with the GNU simulator. The test has an array of size 2
> and accesses that array with indices of 1 and 2. This patch fixes the
> bounds of the loop index.
>
> Tested on powerpc-none-eabi; OK for trunk?
Based on:
http://gcc.gnu.org/ml/gcc-patches/2012-10/msg01259.html
I think the the loop variables are fairly important. I think we're less
likely to perturb the test by increasing the size of the array.
Jeff
next prev parent reply other threads:[~2013-01-15 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 21:55 Janis Johnson
2013-01-15 22:02 ` Jeff Law [this message]
2013-01-15 22:06 ` Janis Johnson
2013-01-15 22:16 ` Jeff Law
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=50F5D1D0.3040009@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=janis_johnson@mentor.com \
--cc=janisjo@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).