public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "4303843KIWEMNPULN at kabelmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/56270] New: loop over array of struct float causes compiler error: segmentation fault
Date: Sat, 09 Feb 2013 23:41:00 -0000	[thread overview]
Message-ID: <bug-56270-4@http.gcc.gnu.org/bugzilla/> (raw)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56270

             Bug #: 56270
           Summary: loop over array of struct float causes compiler error:
                    segmentation fault
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: 4303843KIWEMNPULN@kabelmail.de


Created attachment 29408
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29408
Preprocessed file, comment, compiler call, compiler configuration

Compiling a loop over an array of struct with members of type float leads to:
internal compiler error: Segmentation Fault

Occurs optimizing with -O3

Affected gcc versions: 4.7.2, 4.6.3, 4.6.1, 4.5.2 (at least)
NOT affected versions: 3.4.3 (at least)

Platforms: Solaris 11.1, Ubuntu 12.04.2 LTS (precise), Linux Mint 12 (Lisa);
(Ubuntu and LinuxMint in Virtual Box)

Solaris uname -a: SunOS xxx 5.11 11.1 i86pc i386 i86pc
Ubuntu uname -a Linux xxx 3.2.0-37-generic #58-Ubuntu SMP Thu Jan 24 15:28:10
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
LinuxMint uname -a: Linux xxx 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7
14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux


Attachment contains preprocessed file and further information


             reply	other threads:[~2013-02-09 23:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09 23:41 4303843KIWEMNPULN at kabelmail dot de [this message]
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 ` [Bug tree-optimization/56270] [4.6/4.7 " rguenth at gcc dot gnu.org
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@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).