From: HK <hk1020@t-online.de>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Cygwin 32bit: Can't use gcc -mfpmath=sse
Date: Thu, 10 Sep 2015 20:52:00 -0000 [thread overview]
Message-ID: <op.x4rlk1hl6wtfvl@orion> (raw)
On Thu, 10 Sep 2015 13:19:04 +0200, V?clav_Haisman wrote:
> On 10 September 2015 at 01:30, HK wrote:
>> I've just run across this strange behavior on a recent 32bit
>> installation:
>>
>> vega> cat hello.c
>> #include <stdio.h>
>> int main(int argc, char** argv){
>> printf("hello world\n");
>> }
>> vega> gcc -mfpmath=sse hello.c
>> hello.c:1:0: warning: SSE instruction set disabled, using 387
>> arithmetics
>
> Does it help to use `-march=native`? My hunch is that this is because
> the default CPU type is set to such that does not have SSE.
>
Yep, that did the trick. Thanks for the suggestion. Now, is this a gcc
build
build problem? The 64bit version doesn't need -march=native and that is on
the same computer.
>> #include <stdio.h>
>> ^
>>
>> Why is this? I am pretty sure this used to work in the past. On the
>> 64bit
>> installtion it works just fine.
>>
>> For reference:
>>
>> vega> gcc -v
>> Using built-in specs.
>> COLLECT_GCC=gcc
>> COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-pc-cygwin/4.9.3/lto-wrapper.exe
>> Target: i686-pc-cygwin
>> Configured with:
>> /cygdrive/i/szsz/tmpp/gcc/gcc-4.9.3-1.i686/src/gcc-4.9.3/configure
>> --srcdir=/cygdrive/i/szsz/tmpp/gcc/gcc-4.9.3-1.i686/src/gcc-4.9.3
>> --prefix=/usr --exec-prefix=/usr --localstatedir=/var --sysconfdir=/etc
>> --docdir=/usr/share/doc/gcc --htmldir=/usr/share/doc/gcc/html -C
>> --build=i686-pc-cygwin --host=i686-pc-cygwin --target=i686-pc-cygwin
>> --without-libiconv-prefix --without-libintl-prefix --libexecdir=/usr/lib
>> --enable-shared --enable-shared-libgcc --enable-static
>> --enable-version-specific-runtime-libs --enable-bootstrap
>> --enable-__cxa_atexit --with-dwarf2 --with-arch=i686 --with-tune=generic
>> --disable-sjlj-exceptions
>> --enable-languages=ada,c,c++,fortran,java,lto,objc,obj-c++
>> --enable-graphite
>> --enable-threads=posix --enable-libatomic --enable-libgomp
>> --disable-libitm
>> --enable-libquadmath --enable-libquadmath-support --enable-libssp
>> --enable-libada --enable-libjava --enable-libgcj-sublibs
>> --disable-java-awt
>> --disable-symvers --with-ecj-jar=/usr/share/java/ecj.jar --with-gnu-ld
>> --with-gnu-as --with-cloog-include=/usr/include/cloog-isl
>> --without-libiconv-prefix --without-libintl-prefix --with-system-zlib
>> --enable-linker-build-id
>> Thread model: posix
>> gcc version 4.9.3 (GCC)
>> vega>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2015-09-10 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 20:52 HK [this message]
2015-09-10 21:20 ` Yaakov Selkowitz
[not found] ` <1999691441959416@web12o.yandex.ru>
2015-09-11 12:04 ` HK
2015-09-11 13:40 ` Tim Prince
-- strict thread matches above, loose matches on Subject: below --
2015-09-09 23:30 HK
2015-09-10 11:19 ` Václav Haisman
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=op.x4rlk1hl6wtfvl@orion \
--to=hk1020@t-online.de \
--cc=cygwin@cygwin.com \
/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).