public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d.g.gorbachev at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/47890] New: [4.5/4.6 Regression] internal compiler error: in vect_get_vec_def_for_stmt_copy, at tree-vect-stmts.c:1186 Date: Fri, 25 Feb 2011 02:59:00 -0000 [thread overview] Message-ID: <bug-47890-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47890 Summary: [4.5/4.6 Regression] internal compiler error: in vect_get_vec_def_for_stmt_copy, at tree-vect-stmts.c:1186 Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: d.g.gorbachev@gmail.com Created attachment 23462 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23462 Backtrace $ cat > bug.c void f(char *s) { signed short i; for (i = 0; i < 19; i = i + 1) s[i] = i; } ^D $ gcc -O3 -march=pentium4 bug.c
next reply other threads:[~2011-02-25 1:40 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-25 2:59 d.g.gorbachev at gmail dot com [this message] 2011-02-25 3:01 ` [Bug tree-optimization/47890] " d.g.gorbachev at gmail dot com 2011-02-25 10:49 ` rguenth at gcc dot gnu.org 2011-02-25 17:24 ` rguenth at gcc dot gnu.org 2011-02-26 14:00 ` irar at il dot ibm.com 2011-02-26 15:22 ` irar at il dot ibm.com 2011-03-01 10:36 ` rguenth at gcc dot gnu.org 2011-03-01 13:18 ` rguenth at gcc dot gnu.org 2011-03-01 13:19 ` [Bug tree-optimization/47890] [4.5 " rguenth at gcc dot gnu.org 2011-03-01 17:04 ` rguenth at gcc dot gnu.org 2011-03-01 17:05 ` rguenth at gcc dot gnu.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=bug-47890-4@http.gcc.gnu.org/bugzilla/ \ --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).