public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Zoltan Hidvegi <hzoli@austin.ibm.com>
To: gcc-gnats@gcc.gnu.org
Subject: optimization/3384: PowerPC -funroll-loops -fbranch-count-reg misoptimization
Date: Fri, 22 Jun 2001 16:36:00 -0000 [thread overview]
Message-ID: <200106222331.SAA28662@vlad.austin.ibm.com> (raw)
>Number: 3384
>Category: optimization
>Synopsis: PowerPC -funroll-loops -fbranch-count-reg misoptimization
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Fri Jun 22 16:36:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Zoltan Hidvegi
>Release: 3.0
>Organization:
>Environment:
System: AIX vlad 3 4 0005BA2F4C00
host: powerpc-ibm-aix4.3.3.0
build: powerpc-ibm-aix4.3.3.0
target: powerpc-ibm-aix4.3.3.0
configured with: ../gcc-3.0/configure --enable-languages=c,c++,java --enable-version-specific-runtime-libs --disable-nls
>Description:
gcc-3.0 miscompiles code with -O2 -funroll-loops
Workaround: use -fno-branch-count-reg or do not use -funroll-loops
This is a regression to 2.95.3 but only if you use -funroll-loops.
The testcase:
------------ BEGIN ---------------
typedef unsigned long ulong;
void
set_offsets(ulong *t, ulong idx, ulong n, ulong v)
{
ulong i;
for (i = idx; i < n; i += 2) {
t[i] = v;
}
}
int
main(void)
{
ulong a[8];
set_offsets(a, 0, 7, 0xdeafcabe);
return 1;
}
------------- END ----------------
>How-To-Repeat:
% gcc -O2 -funroll-loops -o bug bug.c
% ./bug
zsh: 16798 segmentation fault ./bug
>Fix:
Use -fno-branch-count-reg or do not use -funroll-loops
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-06-22 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 16:36 Zoltan Hidvegi [this message]
2001-07-20 10:39 dje
2001-07-20 20:25 dje
2002-04-02 14:32 dje
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=200106222331.SAA28662@vlad.austin.ibm.com \
--to=hzoli@austin.ibm.com \
--cc=gcc-gnats@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).