public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/23449] New: vortex fails without -fno-strict-aliasing Date: Wed, 17 Aug 2005 23:53:00 -0000 [thread overview] Message-ID: <20050817234924.23449.janis@gcc.gnu.org> (raw) The SPEC CPU2000 test vortex segfaults on powerpc64-linux with current mainline for either -m32 or -m64 with -O2. It succeeds when compiled with -fno-strict-aliasing. It's quite likely that this is due to invalid code in vortex itself, but nothing jumped out at me. I'm about to go on a two-week vacation, so I'm recording this in case someone else would like to continue the investigation. If mem00.c is compiled with "-O2 -fno-strict-aliasing" and the rest of vortex is compiled with "-O2", the test passes. Variables ChunkAddrChunk and NumChunkChunks, defined in mem00.h, are static and their values never change. If either one is made global instead, the test passes. If either variable is replaced with a global variable with the same value at lines 240-248, the test passes. If the for loop at line 240 is changed to increment ChunkChunk as the third expression in for loop instead of in the second expression, the test passes. -- Summary: vortex fails without -fno-strict-aliasing Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: janis at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC target triplet: powerpc-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23449
next reply other threads:[~2005-08-17 23:49 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-17 23:53 janis at gcc dot gnu dot org [this message] 2005-09-02 20:34 ` [Bug tree-optimization/23449] " janis at gcc dot gnu dot org 2005-09-07 21:07 ` janis at gcc dot gnu dot org
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=20050817234924.23449.janis@gcc.gnu.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).