public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/101683] Floating point exception for double->unsigned conversion on avx512 only Date: Mon, 02 Aug 2021 14:47:39 +0000 [thread overview] Message-ID: <bug-101683-4-EVFRzJxUIt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101683-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101683 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:99b520f031c0e491d7e170916df11dd645d60617 commit r12-2659-g99b520f031c0e491d7e170916df11dd645d60617 Author: Andrew Pinski <apinski@marvell.com> Date: Thu Jul 29 19:48:46 2021 -0700 Fix PR 101683: FP exceptions for float->unsigned Just like the old bug PR9651, unsigned_fix rtl should also be handled as a trapping instruction. OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions. gcc/ChangeLog: PR rtl-optimization/101683 * rtlanal.c (may_trap_p_1): Handle UNSIGNED_FIX.
next prev parent reply other threads:[~2021-08-02 14:47 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-30 2:30 [Bug target/101683] New: " bartoldeman at users dot sourceforge.net 2021-07-30 2:40 ` [Bug rtl-optimization/101683] " pinskia at gcc dot gnu.org 2021-07-30 2:41 ` pinskia at gcc dot gnu.org 2021-07-30 2:47 ` pinskia at gcc dot gnu.org 2021-07-30 6:17 ` rguenth at gcc dot gnu.org 2021-07-30 6:24 ` pinskia at gcc dot gnu.org 2021-07-30 11:25 ` bartoldeman at users dot sourceforge.net 2021-08-02 14:47 ` cvs-commit at gcc dot gnu.org [this message] 2021-08-02 14:49 ` 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-101683-4-EVFRzJxUIt@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).