public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "freebse at live dot jp" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/40910]  New: -04 -fsee libgcc2.c
Date: Thu, 30 Jul 2009 08:48:00 -0000	[thread overview]
Message-ID: <bug-40910-18004@http.gcc.gnu.org/bugzilla/> (raw)

Computer Environment
OS:FreeBSD 8.0 Beta 2
CPU:Intel Pentium 4 3.06GHz(HT Enabled)
Mem:1.5GB(Memtest86+ Passed)

Situation
Installed from ports
GCC 4.4.1 Recomplie from GCC 4.4.1

Compile flag
/*
CFLAGS= -fmudflapir -fsel-sched-pipelining-outer-loops -fsel-sched-pipelining
-funsafe-loop-optimizations -fgcse-las -ftracer -O4 -pipe -mtune=pentium4
-fno-strict-aliasing -mmmx -msse -msse2 -mfpmath=both -ffast-math -fforce-addr
-funroll-loops -frerun-loop-opt -frounding-math -fbranch-target-load-optimize2 
-freciprocal-math -fassociative-math -fmodulo-sched -fira-coalesce -fsee
*/

Result
libgcc2.c In Function '__divdi3':
libgcc2.c:1098:Internal compile error: Segment fault: 11


-- 
           Summary: -04 -fsee libgcc2.c
           Product: gcc
           Version: 4.4.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: freebse at live dot jp
 GCC build triplet: 20090721


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


             reply	other threads:[~2009-07-30  8:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30  8:48 freebse at live dot jp [this message]
2009-07-30 10:22 ` [Bug c/40910] " rguenth at gcc dot gnu dot org
2009-07-30 11:34 ` manu at gcc dot gnu dot org
2009-07-30 16:08 ` pinskia at gcc dot gnu dot org
2009-07-30 16:36 ` steven at gcc dot gnu dot org
2009-07-30 16:55 ` pinskia at gcc dot gnu dot org
2009-08-01  7:16 ` freebse at live dot jp

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-40910-18004@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).