From: Tim Prince <n8tm@aol.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin 32bit: Can't use gcc -mfpmath=sse
Date: Fri, 11 Sep 2015 13:40:00 -0000 [thread overview]
Message-ID: <55F2D9B7.5030209@aol.com> (raw)
In-Reply-To: <op.x4srsuxx6wtfvl@orion>
On 9/11/2015 8:03 AM, HK wrote:
> On Fri, 11 Sep 2015 10:16:56 +0200, Evgeny Grin <k2k@yandex.ru> wrote:
>
>> 10.09.2015, 23:52, "HK" <hk1020@t-online.de>:
>>> On Thu, 10 Sep 2015 13:19:04 +0200, V?clav_Haisman wrote:
>>>> On 10 September 2015 at 01:30, HK wrote:
>>>>> 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.
>>
>> It's not a problem as by default GCC generate code compatible with
>> maximum number of CPU models.
>> If you need to generate an SSE instructions, you have to use at lest
>> -march=pentium3.
>> For x86-64 version, SSE is always enabled as all x86-64 CPUs support
>> SSE and SSE2.
>> See http://gcc.gnu.org/onlinedocs/gcc/x86-Options.html#x86-Options
>
> Thanks. While I don't quite agree with the choice of defaults it makes
> sense.
> So does my 32bit window next to the 64bit window on the same computer
> really
> have a different instruction set? Anyway, case closed.
Intel compilers made SSE2 the default even for 32-bit mode, subsequent
to all CPUs which supported 387 but not SSE3 going out of production.
There's still a lot of interest in 387 mode, however.
You might argue for making SSE3 the default, but it's generally
important nowadays to set an appropriate option for the target platforms.
--
Tim Prince
--
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 prev parent reply other threads:[~2015-09-11 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 20:52 HK
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 [this message]
-- 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=55F2D9B7.5030209@aol.com \
--to=n8tm@aol.com \
--cc=cygwin@cygwin.com \
--cc=tprince@computer.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).