From: Uros Bizjak <ubizjak@gmail.com>
To: Kirill Yukhin <kirill.yukhin@gmail.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>,
"H.J. Lu" <hjl.tools@gmail.com>,
vbyakovl23@gmail.com
Subject: Re: [PATCH, testsuite, i386] FMA3 testcases + typo fix in MD
Date: Mon, 10 Oct 2011 21:14:00 -0000 [thread overview]
Message-ID: <CAFULd4ZNoNO8TTLZfKa4Jxp_Tkr6CzrAi_MEEw6b687t84fwog@mail.gmail.com> (raw)
In-Reply-To: <CAGs3Rfv_F75N9-rxjhtq6hRectrE=xTg-zA8pFMyBiNiBddpCw@mail.gmail.com>
On Thu, Oct 6, 2011 at 3:48 PM, Kirill Yukhin <kirill.yukhin@gmail.com> wrote:
>>
>> BTW, don't you also need "-mfmpath=sse" in dg-options?
>>
>
> According to doc/invoke.texi
> ...
> @itemx -mfma
> ...
> These options will enable GCC to use these extended instructions in
> generated code, even without @option{-mfpmath=sse}.
>
> Seems it -mfpmath=sse is useless..
> Although, if this is wrong, we probably have to update doc as well.
Apparently [1], this is wrong, you need -mfpmath=sse in dg-options.
The reason you didn't see these failures with -m32 is due to
-mfpmath=sse added to your ./configure flags.
[1] http://gcc.gnu.org/ml/gcc-testresults/2011-10/msg01151.html
Uros.
next prev parent reply other threads:[~2011-10-10 20:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 11:16 Kirill Yukhin
2011-10-05 18:51 ` Uros Bizjak
2011-10-06 9:48 ` Kirill Yukhin
2011-10-06 10:14 ` Uros Bizjak
2011-10-06 12:58 ` Kirill Yukhin
2011-10-06 13:04 ` Uros Bizjak
2011-10-06 13:05 ` Uros Bizjak
2011-10-06 13:49 ` Kirill Yukhin
2011-10-06 20:17 ` Uros Bizjak
2011-10-09 19:56 ` Kirill Yukhin
2011-10-10 16:20 ` H.J. Lu
2011-10-10 16:23 ` Kirill Yukhin
2011-10-10 21:14 ` Uros Bizjak [this message]
2011-10-10 21:18 ` Uros Bizjak
2011-10-11 10:38 ` Kirill Yukhin
2011-10-11 10:53 ` Uros Bizjak
2011-10-11 10:59 ` Kirill Yukhin
2011-10-11 16:12 ` H.J. Lu
2011-10-12 18:12 ` H.J. Lu
2011-10-06 13:07 ` Kirill Yukhin
2011-10-15 10:42 ` Andreas Schwab
2011-10-15 10:45 ` Uros Bizjak
2011-10-15 14:45 ` Uros Bizjak
2011-10-17 13:17 ` Kirill Yukhin
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=CAFULd4ZNoNO8TTLZfKa4Jxp_Tkr6CzrAi_MEEw6b687t84fwog@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=kirill.yukhin@gmail.com \
--cc=vbyakovl23@gmail.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).