https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56298
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56298
--- Comment #10 from Piotr Wyderski
2013-02-15 11:41:07 UTC ---
(In reply to comment #1)
More related problems -- do they deserve their own bug reports?
1. The following workaround provided by Jakub
doesen't solve the #error problem:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56298
--- Comment #9 from Piotr Wyderski 2013-02-12
17:22:08 UTC ---
(In reply to comment #8)
> Compiling that with icc -S t.c results in
>
> f:
> # parameter 1: %xmm0
> # parameter 2: %xmm1
> ..B1.1: # Preds ..B1.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56298
--- Comment #8 from Richard Biener 2013-02-12
15:47:33 UTC ---
(In reply to comment #6)
> #include
>
> __m128i f(__m128i x, __m128i y) {
>
> return _mm_aesenc_si128(x, y);
> }
Compiling that with icc -S t.c results in
f:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56298
--- Comment #7 from Jakub Jelinek 2013-02-12
14:08:05 UTC ---
Headers are one thing, but you certainly can't use AES builtins in code not
compiled with -maes or functions not using __attribute__((target ("aes"))) or
similar. That just can
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56298
--- Comment #6 from Piotr Wyderski 2013-02-12
13:55:08 UTC ---
#include
__m128i f(__m128i x, __m128i y) {
return _mm_aesenc_si128(x, y);
}
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56298
--- Comment #5 from Richard Biener 2013-02-12
13:49:41 UTC ---
Can you give me a testcase that I can compile?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56298
--- Comment #4 from Piotr Wyderski 2013-02-12
13:30:37 UTC ---
@Richard: I don't have ICC right now, so a follow-up question is:
does ICC "enable" those built-in intrinsics conditionally (as does GCC)
or not (as MSVC). I think that ICC is
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56298
--- Comment #3 from Piotr Wyderski 2013-02-12
13:22:04 UTC ---
I beg to disagree, Jakub. In that case all the intrinsics
headers are written in a wrong way. At least if one takes
MSVC as a reference (which behaves exactly as I expected).
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56298
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-*, i?86-*-*
10 matches
Mail list logo
