[Bug c/27992] New: random segfaults

[Bug c/27992] New: random segfaults

[thomas at koeller dot dyndns dot org]

I am encountering random segfaults when compiling sources. If I restart the
compilation after such a segfault, everything goes well. I found two older bug
reports that describe this phenomenon, namely
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9592 and
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10227. Remarkably, like the authors
of these bug reports, I am using an AMD Athlon K7 Processor. Having used
various gcc versions through the years, I have always encountered this problem,
cannot remember when it started.

Trying to use the -save-temps option to get preprocessed source code I found
that this made the problem disappear, and it turned out that it seems to be the
-pipe option, which I used all the time, was what caused the problem. I ran
some tests on my system to make sure that pipes are working, and found no
problems. Also, my system runs just fine and does not show any signs of
instability. I am positive that memory is o.k.

When compiling sources; I am normally using these settings:

CC="/usr/gcc/bin/gcc -march=athlon -mmmx -m3dnow"
CXX="/usr/gcc/bin/g++ -march=athlon -mmmx -m3dnow"
CFLAGS="-pipe -O3 -fomit-frame-pointer"
CXXFLAGS="-pipe -O3 -fomit-frame-pointer"


-- 
           Summary: random segfaults
           Product: gcc
           Version: 4.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: thomas at koeller dot dyndns dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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

[Bug c/27992] random segfaults

[pinskia at gcc dot gnu dot org]

------- Comment #1 from pinskia at gcc dot gnu dot org  2006-06-12 00:13 -------
If you compiling again works, that means you have some bad hardware and you
should replace it.

Closing as invalid as mention on the bugs page that you should check your
hardware (memory especially) before filing the bug report.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


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