public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56270] [4.6/4.7 Regression] loop over array of struct float causes compiler error: segmentation fault
Date: Tue, 05 Mar 2013 09:56:00 -0000 [thread overview]
Message-ID: <bug-56270-4-o8dpvZqN3A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56270-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56270
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |4.8.0
Summary|[4.6/4.7/4.8 Regression] |[4.6/4.7 Regression] loop
|loop over array of struct |over array of struct float
|float causes compiler |causes compiler error:
|error: segmentation fault |segmentation fault
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> 2013-03-05 09:55:18 UTC ---
Fixed on trunk sofar.
next prev parent reply other threads:[~2013-03-05 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 23:41 [Bug c/56270] New: " 4303843KIWEMNPULN at kabelmail dot de
2013-02-09 23:47 ` [Bug tree-optimization/56270] " pinskia at gcc dot gnu.org
2013-03-03 19:43 ` mikpe at it dot uu.se
2013-03-04 10:57 ` rguenth at gcc dot gnu.org
2013-03-04 13:05 ` [Bug tree-optimization/56270] [4.6/4.7/4.8 Regression] " rguenth at gcc dot gnu.org
2013-03-04 13:14 ` rguenth at gcc dot gnu.org
2013-03-04 14:19 ` rguenth at gcc dot gnu.org
2013-03-05 9:55 ` rguenth at gcc dot gnu.org
2013-03-05 9:56 ` rguenth at gcc dot gnu.org [this message]
2013-03-26 10:15 ` [Bug tree-optimization/56270] [4.6 " rguenth at gcc dot gnu.org
2013-04-12 16:29 ` jakub 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-56270-4-o8dpvZqN3A@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).