public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "devurandom at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/43653] ICE: in reload, at reload1.c:1188 with -O1 -ftree-vectorize and empty struct
Date: Sat, 25 Dec 2010 23:43:00 -0000 [thread overview]
Message-ID: <bug-43653-4-fxrXowD5oB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43653-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43653
--- Comment #3 from devurandom at gmx dot net 2010-12-25 23:43:13 UTC ---
4.5.1 shows the same issue when building Clang 2.8.
next parent reply other threads:[~2010-12-25 23:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43653-4@http.gcc.gnu.org/bugzilla/>
2010-12-25 23:43 ` devurandom at gmx dot net [this message]
2011-01-03 18:24 ` devurandom at gmx dot net
2011-01-03 19:59 ` [Bug rtl-optimization/43653] [4.3/4.4/4.5/4.6 Regression] " rguenth at gcc dot gnu.org
2011-01-03 20:00 ` rguenth at gcc dot gnu.org
2011-01-03 20:42 ` hjl.tools at gmail dot com
2011-02-15 17:51 ` [Bug rtl-optimization/43653] [4.3/4.4/4.5/4.6 Regression] ICE " law at redhat dot com
2011-02-15 18:36 ` ubizjak at gmail dot com
2011-02-15 19:21 ` law at redhat dot com
2011-02-15 21:07 ` law at redhat dot com
2011-02-15 22:43 ` ubizjak at gmail dot com
2011-02-16 5:08 ` law at redhat dot com
2011-02-16 8:32 ` [Bug target/43653] " ubizjak at gmail dot com
2011-02-16 11:29 ` ubizjak at gmail dot com
2011-02-17 8:34 ` uros at gcc dot gnu.org
2011-02-17 20:26 ` law at redhat dot com
2011-02-17 21:34 ` ubizjak at gmail dot com
2011-02-17 22:11 ` uros at gcc dot gnu.org
2011-02-17 23:23 ` uros at gcc dot gnu.org
2010-04-05 20:10 [Bug rtl-optimization/43653] New: ICE: in reload, at reload1.c:1188 with -O2 " zsojka at seznam dot cz
2010-04-11 20:36 ` [Bug rtl-optimization/43653] ICE: in reload, at reload1.c:1188 with -O1 " ubizjak at gmail 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=bug-43653-4-fxrXowD5oB@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: 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).