public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jenkinsj89 at yahoo dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60506] New: g++ reports "internal compiler error" using SSE2 and not entirely beautiful programming
Date: Wed, 12 Mar 2014 04:47:00 -0000	[thread overview]
Message-ID: <bug-60506-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60506
           Summary: g++ reports "internal compiler error" using SSE2 and
                    not entirely beautiful programming
           Product: gcc
           Version: 4.8.2
            Status: UNCONFIRMED
          Severity: blocker
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jenkinsj89 at yahoo dot ca
              Host: i86_64-pc-cygwin
            Target: i86_64-pc-cygwin -march=corei7

I compiled the enclosed program with:

g++ -S -v -Wall -Wextra -std=c++11 -march=corei7 -save-temps rabbit-gccbug.cc

and it reported the text hereafter pasted.  It reports the same error
if "-O2" is enabled, and it also reports the same error if 
"-fno-strict-aliasing -fwrapv -fno-aggressive-loop-optimizations"
is provided.

As requested, I am attaching the preprocessed output rather than the original
program, but please note that the only included file is <cstdint>.


             reply	other threads:[~2014-03-12  4:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12  4:47 jenkinsj89 at yahoo dot ca [this message]
2014-03-12  4:48 ` [Bug c++/60506] " jenkinsj89 at yahoo dot ca
2014-03-12  5:03 ` pinskia at gcc dot gnu.org
2014-03-12  5:09 ` pinskia at gcc dot gnu.org
2014-03-12  5:12 ` [Bug c++/60506] ICE with && on vectors in C++ pinskia 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-60506-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).