public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/52258] __builtin_isgreaterequal is sometimes signaling on ARM Date: Sun, 19 Feb 2012 11:31:00 -0000 [thread overview] Message-ID: <bug-52258-4-xeLUgVYCK2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52258-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52258 Mikael Pettersson <mikpe at it dot uu.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikpe at it dot uu.se --- Comment #1 from Mikael Pettersson <mikpe at it dot uu.se> 2012-02-19 11:23:54 UTC --- Can you provide a standalone runtime test case that fails (with a SIGFPE I assume) when the bug is triggered?
next prev parent reply other threads:[~2012-02-19 11:24 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-15 10:24 [Bug target/52258] New: " aurelien at aurel32 dot net 2012-02-19 11:31 ` mikpe at it dot uu.se [this message] 2012-02-19 12:23 ` [Bug target/52258] " aurelien at aurel32 dot net 2012-02-19 23:49 ` mikpe at it dot uu.se 2012-02-23 2:24 ` ramana at gcc dot gnu.org 2021-07-19 18:48 ` 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-52258-4-xeLUgVYCK2@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: linkBe 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).