[Bug bootstrap/36948] New: cc1.exe: internal compiler error: Segmentation fault

[Bug bootstrap/36948] New: cc1.exe: internal compiler error: Segmentation fault

[andry at inbox dot ru]

xgcc.exe (GCC; Mingw; 32bit; i686; NLS) 4.3.1
Copyright (C) 2008 Free Software Foundation, Inc.
configure:2369: $? = 0
configure:2371: /c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/./gcc/xgcc
-B/c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/./gcc/
-L/c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/i686-pc-mingw32/winsup/mingw
-L/c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/i686-pc-mingw32/winsup/w32api/lib
-isystem /c/_GccBuilds/gcc-4.3.1/winsup/mingw/include -isystem
/c/_GccBuilds/gcc-4.3.1/winsup/w32api/include
-B/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/bin/
-B/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/lib/ -isystem
/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/include -isystem
/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/sys-include -v
</dev/null >&5
configure:2374: $? = 5
configure:2376: /c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/./gcc/xgcc
-B/c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/./gcc/
-L/c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/i686-pc-mingw32/winsup/mingw
-L/c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/i686-pc-mingw32/winsup/w32api/lib
-isystem /c/_GccBuilds/gcc-4.3.1/winsup/mingw/include -isystem
/c/_GccBuilds/gcc-4.3.1/winsup/w32api/include
-B/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/bin/
-B/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/lib/ -isystem
/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/include -isystem
/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/sys-include -V
</dev/null >&5
configure:2379: $? = 5
configure:2398: /c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/./gcc/xgcc
-B/c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/./gcc/
-L/c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/i686-pc-mingw32/winsup/mingw
-L/c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/i686-pc-mingw32/winsup/w32api/lib
-isystem /c/_GccBuilds/gcc-4.3.1/winsup/mingw/include -isystem
/c/_GccBuilds/gcc-4.3.1/winsup/w32api/include
-B/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/bin/
-B/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/lib/ -isystem
/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/include -isystem
/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/sys-include -o
conftest -O2   conftest.c  >&5
cc1.exe: internal compiler error: Segmentation fault
configure:2401: $? = 1
configure:2567: checking for suffix of object files
configure:2588: /c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/./gcc/xgcc
-B/c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/./gcc/
-L/c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/i686-pc-mingw32/winsup/mingw
-L/c/_GccBuilds/gcc-4.3.1-build/mingw-32-i686/i686-pc-mingw32/winsup/w32api/lib
-isystem /c/_GccBuilds/gcc-4.3.1/winsup/mingw/include -isystem
/c/_GccBuilds/gcc-4.3.1/winsup/w32api/include
-B/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/bin/
-B/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/lib/ -isystem
/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/include -isystem
/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686/i686-pc-mingw32/sys-include -c
-O2  conftest.c >&5
cc1.exe: internal compiler error: Segmentation fault
configure:2591: $? = 1
configure: failed program was:
| /* confdefs.h.  */
| 
| #define PACKAGE_NAME "GNU C Runtime Library"
| #define PACKAGE_TARNAME "libgcc"
| #define PACKAGE_VERSION "1.0"
| #define PACKAGE_STRING "GNU C Runtime Library 1.0"
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h.  */
| 
| int
| main ()
| {
| 
|   ;
|   return 0;
| }
configure:2605: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.


-- 
           Summary: cc1.exe: internal compiler error: Segmentation fault
           Product: gcc
           Version: 4.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: andry at inbox dot ru
  GCC host triplet: i686-pc-mingw32


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[andry at inbox dot ru]

------- Comment #1 from andry at inbox dot ru  2008-07-27 14:01 -------
Created an attachment (id=15966)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15966&action=view)
Root config log


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[andry at inbox dot ru]

------- Comment #2 from andry at inbox dot ru  2008-07-27 14:01 -------
Created an attachment (id=15967)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15967&action=view)
libgcc config log


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[andry at inbox dot ru]

------- Comment #3 from andry at inbox dot ru  2008-07-27 14:03 -------
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[1]: *** [configure-target-libgcc] Error 1
make: *** [all] Error 2 


-- 

andry at inbox dot ru changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|cc1.exe: internal compiler  |cc1.exe: internal compiler
                   |error: Segmentation fault   |error: Segmentation fault


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[andry at inbox dot ru]

------- Comment #4 from andry at inbox dot ru  2008-07-27 17:52 -------
Seems that crash happens when GCC run with "-O2" flag:
make CFLAGS="-O2" CFLAGS_FOR_TARGET="-O2"


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[andry at inbox dot ru]

------- Comment #5 from andry at inbox dot ru  2008-08-01 02:14 -------
I check it without these flags and crash happend again, here:
"xgcc.exe -v"


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[dannysmith at users dot sourceforge dot net]

------- Comment #6 from dannysmith at users dot sourceforge dot net  2008-08-01 04:34 -------
This kind of path
'--prefix=/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686' may be understood by
your  shell, but  won't be found by the xgcc driver or cc1.exe which are native
windows apps.  Search the mingw site for  a build script that will work with
the msys shell.

Danny


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[andry at inbox dot ru]

------- Comment #7 from andry at inbox dot ru  2008-08-02 11:10 -------
(In reply to comment #6)
> This kind of path
> '--prefix=/c/_GccBuilds/gcc-4.3.1-install/mingw-32-i686' may be understood by
But this is Mingw compatible path, isn't it?


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[brian at dessent dot net]

------- Comment #8 from brian at dessent dot net  2008-08-02 16:56 -------
Subject: Re:  cc1.exe: internal compiler error: Segmentation 
 fault

It's a valid MinGW path only if you have created a physical directory
named "c" at the root of the current drive, i.e. X:\c\_GccBuilds\...


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[andry at inbox dot ru]

------- Comment #9 from andry at inbox dot ru  2008-08-02 18:01 -------
(In reply to comment #8)
> It's a valid MinGW path only if you have created a physical directory
> named "c" at the root of the current drive, i.e. X:\c\_GccBuilds\...
> 
>From "/msys/1.0/doc/MSYS_VS_CYGWIN":
/cygdrive:  There is no such item.  All devices and mapped shares are auto
mounted with the device letter as the mount point.  E.G.: the C:\ drive is
referenced as /c.

>From this, "/c" is automount point to "c:".


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[brian at dessent dot net]

------- Comment #10 from brian at dessent dot net  2008-08-02 19:24 -------
Subject: Re:  cc1.exe: internal compiler error: Segmentation 
 fault

/c/foo/bar is valid for *MSYS* apps.  But we're talking about gcc which
is NOT a MSYS app, it is a MinGW app, i.e. native win32.  /c/foo/bar is
*not* valid for such an app.  In fact the whole point of MSYS is to
rewrite these paths as c:/foo/bar when invoking MinGW apps, but that is
only possible if they are passed on a command line.  The gcc build
system sometimes embeds them in filenames and they won't be translated. 
Thus you have to be careful to avoid using them.


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[andry at inbox dot ru]

------- Comment #11 from andry at inbox dot ru  2008-08-02 20:41 -------
> /c/foo/bar is valid for *MSYS* apps.  But we're talking about gcc which
> is NOT a MSYS app, it is a MinGW app, i.e. native win32.  /c/foo/bar is
> *not* valid for such an app.
Not true, for example, Mingw GCC 3.4.4 perfectly understands BOTH type of
paths. You can simply test it putting paths in to environment variables like
"CPATH" or in "-I" key on command line.

> In fact the whole point of MSYS is to
> rewrite these paths as c:/foo/bar when invoking MinGW apps, but that is
> only possible if they are passed on a command line.  The gcc build
> system sometimes embeds them in filenames and they won't be translated. 
> Thus you have to be careful to avoid using them.

If all this was true, then build should be crash on early stage then first
"incorrect" path come on commend line, but it wouldn't happend.

I test build with "c:\" and with "c:/" paths, the build crashes the same. I
think this is not a point of the bug.


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[brian at dessent dot net]

------- Comment #12 from brian at dessent dot net  2008-08-02 21:02 -------
Subject: Re:  cc1.exe: internal compiler error: Segmentation 
 fault

You're not really testing what you think you are, because MSYS
translates everything on the command line, so saying that "gcc
-I/foo/bar" works just means that MSYS actually executed "gcc
-Ic:/path/to/foo/bar".  MinGW apps like gcc have *no* way of
interpreting anything but Win32 paths.

And yes, using Win32 paths with colons also fails because the gcc build
system isn't expecting paths with colons.


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[andry at inbox dot ru]

------- Comment #13 from andry at inbox dot ru  2008-08-03 01:50 -------
(In reply to comment #12)
> You're not really testing what you think you are
Ok, i found that Msys console converts all application arguments and
environment variables before run any application. So, i missed out that in
Windows console GCC compiler doesn't understand MSYS paths.

> And yes, using Win32 paths with colons also fails because the gcc build
> system isn't expecting paths with colons.
So, have i any chances to pass in --prefix argument path in Windows form to not
mingw directory?


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[andry at inbox dot ru]

------- Comment #14 from andry at inbox dot ru  2008-08-03 02:42 -------
(In reply to comment #12)
> MinGW apps like gcc have *no* way of interpreting anything but Win32 paths.
It is, i found that Msys bash shell (not console) converts all this stuff with
Msys paths. So xgcc already gothering paths in windows form.

> And yes, using Win32 paths with colons also fails because the gcc build
> system isn't expecting paths with colons.
Fails not the build, fails call to cc1.exe, in "/gcc" in build directory. I try
simply run it and it fails. Maybe problem in some library and in another
thing...


-- 


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

[Bug bootstrap/36948] cc1.exe: internal compiler error: Segmentation fault

[andry at inbox dot ru]

------- Comment #15 from andry at inbox dot ru  2008-08-03 12:18 -------
I found where the bug is:
"/mingw/lib/libmsvcrt.a" and "/mingw/lib/libmsvcrtd.a" should be Microsoft
Visual Studio v6.0 libraries. I just run "gccmrt.bat" attached to TDM builds of
GCC (http://www.tdragon.net/recentgcc/) and forgot to revert changes maded by
this script back. After reverting changes back crash is disappered. But i think
bug with what crash on incorrect library should be fixed or at least, warning
should persists in output.


-- 

andry at inbox dot ru changed:

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


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