public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "david.oshea at emulex dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/38299] internal error: segmentation fault
Date: Sat, 14 Apr 2012 16:52:00 -0000	[thread overview]
Message-ID: <bug-38299-4-JgmEYgrv3K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38299-4@http.gcc.gnu.org/bugzilla/>

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

David O'Shea <david.oshea at emulex dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |david.oshea at emulex dot
                   |                            |com

--- Comment #7 from David O'Shea <david.oshea at emulex dot com> 2012-04-14 16:51:46 UTC ---
In playing with the -O2 and -O flags, it would appear to be that the -fgcse
subflag of the -O2 flags causes the failure.  So you can substitute the
following and get the compiler to build the library  -O2 -no-gcse.
This builds a less great (no Global Common Subexpression Elimination) library,
but it builds on 3.2.1...
The result is a larger library, but at least it builds.


       reply	other threads:[~2012-04-14 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-38299-4@http.gcc.gnu.org/bugzilla/>
2012-04-14 16:52 ` david.oshea at emulex dot com [this message]
2012-04-14 17:58 ` david.oshea at emulex dot com
2008-11-28  8:48 [Bug c/38299] New: " sd dot israr at gmail dot com
2008-11-28  8:51 ` [Bug middle-end/38299] " pinskia at gcc dot gnu dot org
2008-11-29  3:18 ` pinskia at gcc dot gnu dot org
2009-01-05 19:41 ` grant dot b dot edwards at gmail dot com
2009-01-06 15:27 ` dave dot korn dot cygwin at gmail dot com
2009-03-05  8:42 ` zhijie dot t at gmail dot com
2010-03-19 23:37 ` ramana at gcc dot gnu dot 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-38299-4-JgmEYgrv3K@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).