public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug other/55925] New: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
@ 2013-01-09 19:23 lailavrazda1979 at gmail dot com
2013-01-13 13:39 ` [Bug other/55925] " ubizjak at gmail dot com
` (8 more replies)
0 siblings, 9 replies; 10+ messages in thread
From: lailavrazda1979 at gmail dot com @ 2013-01-09 19:23 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
Bug #: 55925
Summary: Unrecognized command line option '-mfxsr' when
building x86_64-w64-mingw32 native compiler
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: other
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: lailavrazda1979@gmail.com
When building a native x86_64-w64-mingw32 compiler using a 4.7.2 cross
compiler, I get the following:
x86_64-w64-mingw32-gcc -L/root/win64-build/native/x86_64-w64-mingw32/lib
-L/root/win64-build/native/mingw/lib -isystem
/root/win64-build/native/x86_64-w64-mingw32/include -isystem
/root/win64-build/native/mingw/include -g -O2 -O2 -g -O2 -DIN_GCC -W
-Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes
-Wmissing-prototypes -Wold-style-definition -isystem ./include -g
-DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -I. -I. -I../.././gcc
-I../../../gcc-4.8.0/libgcc -I../../../gcc-4.8.0/libgcc/.
-I../../../gcc-4.8.0/libgcc/../gcc -I../../../gcc-4.8.0/libgcc/../include
-I../../../gcc-4.8.0/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT
-DHAVE_CC_TLS -DUSE_EMUTLS -o crtfastmath.o -MT crtfastmath.o -MD -MP -MF
crtfastmath.dep -mfxsr -msse -c
../../../gcc-4.8.0/libgcc/config/i386/crtfastmath.c
x86_64-w64-mingw32-gcc: error: unrecognized command line option '-mfxsr'
make[2]: *** [crtfastmath.o] Error 1
make[2]: Leaving directory
`/root/win64-build/src/gcc-build/x86_64-w64-mingw32/libgcc'
make[1]: *** [all-target-libgcc] Error 2
make[1]: Leaving directory `/root/win64-build/src/gcc-build'
make: *** [all] Error 2
I can't find any documentation at all on this '-mfxsr' option. What is it, and
why is it being used here?
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
2013-01-09 19:23 [Bug other/55925] New: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler lailavrazda1979 at gmail dot com
@ 2013-01-13 13:39 ` ubizjak at gmail dot com
2013-01-13 23:31 ` lailavrazda1979 at gmail dot com
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: ubizjak at gmail dot com @ 2013-01-13 13:39 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
--- Comment #1 from Uros Bizjak <ubizjak at gmail dot com> 2013-01-13 13:39:25 UTC ---
(In reply to comment #0)
> When building a native x86_64-w64-mingw32 compiler using a 4.7.2 cross
> compiler, I get the following:
>
> x86_64-w64-mingw32-gcc -L/root/win64-build/native/x86_64-w64-mingw32/lib
[...]
> I can't find any documentation at all on this '-mfxsr' option. What is it, and
> why is it being used here?
crtfastmath.c should be compiled with newly built compiler. "-mfxsr" option is
used to compile __builtin_ia32_fxsave builtin to fxsr instruction, newly built
compiler will recognize this option.
How did you configure gcc?
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
2013-01-09 19:23 [Bug other/55925] New: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler lailavrazda1979 at gmail dot com
2013-01-13 13:39 ` [Bug other/55925] " ubizjak at gmail dot com
@ 2013-01-13 23:31 ` lailavrazda1979 at gmail dot com
2013-01-14 13:37 ` ubizjak at gmail dot com
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: lailavrazda1979 at gmail dot com @ 2013-01-13 23:31 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
--- Comment #2 from lailavrazda1979 at gmail dot com 2013-01-13 23:31:01 UTC ---
How did I configure which GCC? The cross compiler or the native one?
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
2013-01-09 19:23 [Bug other/55925] New: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler lailavrazda1979 at gmail dot com
2013-01-13 13:39 ` [Bug other/55925] " ubizjak at gmail dot com
2013-01-13 23:31 ` lailavrazda1979 at gmail dot com
@ 2013-01-14 13:37 ` ubizjak at gmail dot com
2013-01-14 21:27 ` lailavrazda1979 at gmail dot com
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: ubizjak at gmail dot com @ 2013-01-14 13:37 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
--- Comment #3 from Uros Bizjak <ubizjak at gmail dot com> 2013-01-14 13:37:14 UTC ---
(In reply to comment #2)
> How did I configure which GCC? The cross compiler or the native one?
The crosscompiler.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
2013-01-09 19:23 [Bug other/55925] New: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler lailavrazda1979 at gmail dot com
` (2 preceding siblings ...)
2013-01-14 13:37 ` ubizjak at gmail dot com
@ 2013-01-14 21:27 ` lailavrazda1979 at gmail dot com
2013-01-14 21:53 ` ubizjak at gmail dot com
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: lailavrazda1979 at gmail dot com @ 2013-01-14 21:27 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
--- Comment #4 from lailavrazda1979 at gmail dot com 2013-01-14 21:26:36 UTC ---
I tried building several compilers (4.7.2), none of which understand the
'-mfxsr' option. One was configured with:
../gcc-4.7.2/configure --build=x86_64-unknown-linux-gnu
--host=x86_64-unknown-linux-gnu --target=x86_64-w64-mingw32 --prefix=$CROSS_DIR
--libexecdir=$CROSS_DIR/lib --enable-clocale=gnu --enable-__cxa_atexit
--enable-languages=c,c++ --enable-targets=all --enable-cloog-backend=ppl
--disable-shared --disable-nls --disable-werror --with-host-libstdcxx="-lstdc++
-lsupc++" --with-local-prefix=$CROSS_DIR --with-sysroot=$CROSS_DIR
--with-ppl=$CROSS_DIR --with-cloog=$CROSS_DIR
make all-gcc && make install-gcc
After that, I build the mingw-w64 library, went back to my GCC build dir, and
did:
make && make install
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
2013-01-09 19:23 [Bug other/55925] New: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler lailavrazda1979 at gmail dot com
` (3 preceding siblings ...)
2013-01-14 21:27 ` lailavrazda1979 at gmail dot com
@ 2013-01-14 21:53 ` ubizjak at gmail dot com
2013-01-14 23:18 ` lailavrazda1979 at gmail dot com
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: ubizjak at gmail dot com @ 2013-01-14 21:53 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
--- Comment #5 from Uros Bizjak <ubizjak at gmail dot com> 2013-01-14 21:53:16 UTC ---
(In reply to comment #4)
> I tried building several compilers (4.7.2), none of which understand the
> '-mfxsr' option. One was configured with:
True. -mfxsr option was added to 4.8.0.
After that, I build the mingw-w64 library, went back to my GCC build dir, and
did:
make && make install
This command should first build a 4.8.0 crosscompiler, and then compile the
library with the newly built compiler. The command should look like:
/home/uros/gcc-build/./gcc/xgcc -B/home/uros/gcc-build/./gcc/
-B/usr/local/x86_64-unknown-linux-gnu/bin/
-B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem
/usr/local/x86_64-unknown-linux-gnu/include -isystem
/usr/local/x86_64-unknown-linux-gnu/sys-include -g -O2 -O2 -g -O2 -DIN_GCC
-W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes
-Wmissing-prototypes -Wold-style-definition -isystem ./include -fpic
-mlong-double-80 -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -fpic
-mlong-double-80 -I. -I. -I../.././gcc -I../../../gcc-svn/trunk/libgcc
-I../../../gcc-svn/trunk/libgcc/. -I../../../gcc-svn/trunk/libgcc/../gcc
-I../../../gcc-svn/trunk/libgcc/../include
-I../../../gcc-svn/trunk/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT
-DHAVE_CC_TLS -DUSE_TLS -o crtfastmath.o -MT crtfastmath.o -MD -MP -MF
crtfastmath.dep -mfxsr -msse -c
../../../gcc-svn/trunk/libgcc/config/i386/crtfastmath.c
As you can see, using -mfxsr does not fail here.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
2013-01-09 19:23 [Bug other/55925] New: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler lailavrazda1979 at gmail dot com
` (4 preceding siblings ...)
2013-01-14 21:53 ` ubizjak at gmail dot com
@ 2013-01-14 23:18 ` lailavrazda1979 at gmail dot com
2013-01-14 23:32 ` pinskia at gcc dot gnu.org
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: lailavrazda1979 at gmail dot com @ 2013-01-14 23:18 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
--- Comment #6 from lailavrazda1979 at gmail dot com 2013-01-14 23:18:30 UTC ---
So, you need GCC 4.8 to build GCC 4.8? That's just... why? Doesn't that mean
it's basically impossible to build GCC 4.8 without a binary of it first?
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
2013-01-09 19:23 [Bug other/55925] New: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler lailavrazda1979 at gmail dot com
` (5 preceding siblings ...)
2013-01-14 23:18 ` lailavrazda1979 at gmail dot com
@ 2013-01-14 23:32 ` pinskia at gcc dot gnu.org
2013-01-14 23:44 ` lailavrazda1979 at gmail dot com
2013-01-15 1:17 ` pinskia at gcc dot gnu.org
8 siblings, 0 replies; 10+ messages in thread
From: pinskia at gcc dot gnu.org @ 2013-01-14 23:32 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-01-14 23:32:17 UTC ---
(In reply to comment #6)
> So, you need GCC 4.8 to build GCC 4.8? That's just... why? Doesn't that mean
> it's basically impossible to build GCC 4.8 without a binary of it first?
No you need a 4.8 cross compiler to build a 4.8 "native" compiler. So you
should build a 4.8 cross compiler which will include all the target libraries
and then you do a 4.8 Canadian cross (you just need to do "make all-host &&
make install-host" as you already have all the libraries done by the normal
cross).
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
2013-01-09 19:23 [Bug other/55925] New: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler lailavrazda1979 at gmail dot com
` (6 preceding siblings ...)
2013-01-14 23:32 ` pinskia at gcc dot gnu.org
@ 2013-01-14 23:44 ` lailavrazda1979 at gmail dot com
2013-01-15 1:17 ` pinskia at gcc dot gnu.org
8 siblings, 0 replies; 10+ messages in thread
From: lailavrazda1979 at gmail dot com @ 2013-01-14 23:44 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
lailavrazda1979 at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
--- Comment #8 from lailavrazda1979 at gmail dot com 2013-01-14 23:43:54 UTC ---
Oh, okay. That makes sense. Thank you.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
2013-01-09 19:23 [Bug other/55925] New: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler lailavrazda1979 at gmail dot com
` (7 preceding siblings ...)
2013-01-14 23:44 ` lailavrazda1979 at gmail dot com
@ 2013-01-15 1:17 ` pinskia at gcc dot gnu.org
8 siblings, 0 replies; 10+ messages in thread
From: pinskia at gcc dot gnu.org @ 2013-01-15 1:17 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-01-15 01:17:32 UTC ---
.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2013-01-15 1:17 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-01-09 19:23 [Bug other/55925] New: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler lailavrazda1979 at gmail dot com
2013-01-13 13:39 ` [Bug other/55925] " ubizjak at gmail dot com
2013-01-13 23:31 ` lailavrazda1979 at gmail dot com
2013-01-14 13:37 ` ubizjak at gmail dot com
2013-01-14 21:27 ` lailavrazda1979 at gmail dot com
2013-01-14 21:53 ` ubizjak at gmail dot com
2013-01-14 23:18 ` lailavrazda1979 at gmail dot com
2013-01-14 23:32 ` pinskia at gcc dot gnu.org
2013-01-14 23:44 ` lailavrazda1979 at gmail dot com
2013-01-15 1:17 ` pinskia at gcc dot gnu.org
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).