public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59664] avx512f-ceil-sfix-vec-2.c and avx512f-floor-sfix-vec-2.c FAIL on Solaris9/x86
Date: Mon, 06 Jan 2014 13:05:00 -0000 [thread overview]
Message-ID: <bug-59664-4-BEkUg8Ierh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59664-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59664
--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> I guess it is problematic to include <math.h> in the test, because then you
> rely on whatever the vendor math.h does.
>
> Does it still FAIL if you remove the #include <math.h>
> and instead add say
> #define floor(x) __builtin_floor (x)
> #define ceil(x) __builtin_ceil (x)
> #define M_PI __builtin_acos (-1.0)
>
> ?
It does, while the *-vec-1.c files which actually include <math.h> still pass.
Rainer
next prev parent reply other threads:[~2014-01-06 13:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 13:24 [Bug target/59664] New: " ro at gcc dot gnu.org
2014-01-03 13:24 ` [Bug target/59664] " ro at gcc dot gnu.org
2014-01-03 13:25 ` ro at gcc dot gnu.org
2014-01-06 13:05 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2014-04-22 11:36 ` jakub at gcc dot gnu.org
2014-07-16 13:28 ` jakub at gcc dot gnu.org
2014-10-30 10:38 ` jakub at gcc dot gnu.org
2015-06-26 20:16 ` jakub at gcc dot gnu.org
2015-06-26 20:37 ` jakub at gcc dot gnu.org
2015-06-26 21:20 ` pinskia at gcc dot gnu.org
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=bug-59664-4-BEkUg8Ierh@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).