public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jojelino at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/45633] [4.6 regression] internal compiler error: verify_stmts failed Date: Sat, 11 Sep 2010 20:59:00 -0000 [thread overview] Message-ID: <20100911205923.11765.qmail@sourceware.org> (raw) In-Reply-To: <bug-45633-13856@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from jojelino at gmail dot com 2010-09-11 20:59 ------- this causes ICE confirmed with gcc -O3 -msse2 -std=gnu99 reduced testcase typedef unsigned char uint8_t; typedef struct foo2 { int offset[4]; uint8_t* ref[4]; } foo2; int foo(const foo2 *fooval) { uint8_t *source[4] = { fooval->ref[0], fooval->ref[1], fooval->ref[2] }; int strides[4] = { fooval->offset[0], fooval->offset[1], fooval->offset[2] }; for (int i = 0; i < 4; i++) { strides[i] = -strides[i]; source[i] -= strides[i]; } return source[0]; } int main() { foo2 fool; int ret = foo(&fool); return ret; } -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45633
next prev parent reply other threads:[~2010-09-11 20:59 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-10 11:18 [Bug tree-optimization/45633] New: " jojelino at gmail dot com 2010-09-10 11:20 ` [Bug tree-optimization/45633] " jojelino at gmail dot com 2010-09-10 11:29 ` rguenth at gcc dot gnu dot org 2010-09-10 12:13 ` jojelino at gmail dot com 2010-09-11 20:59 ` jojelino at gmail dot com [this message] 2010-09-14 15:24 ` jakub at gcc dot gnu dot org 2010-09-14 16:18 ` jakub at gcc dot gnu dot org 2010-09-14 16:20 ` jakub at gcc dot gnu dot org 2010-09-14 17:16 ` jakub at gcc dot gnu dot org 2010-09-14 18:43 ` jakub at gcc dot gnu dot org 2010-09-15 15:43 ` jakub at gcc dot gnu dot org 2010-09-15 16:06 ` jakub at gcc dot gnu dot org [not found] <bug-45633-4@http.gcc.gnu.org/bugzilla/> 2015-02-05 23:45 ` law at redhat dot com
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=20100911205923.11765.qmail@sourceware.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).