public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/96613] SIGFPE on min1() with -ffpe-trap=invalid switch Date: Sun, 16 Aug 2020 19:55:26 +0000 [thread overview] Message-ID: <bug-96613-4-H2fn1YkP3B@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96613-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96613 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gcc dot gnu.org --- Comment #3 from anlauf at gcc dot gnu.org --- Created attachment 49066 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49066&action=edit WIP patch The underlying issue is visible in the tree-dump, see also comment#1 by Steve. Changing the type and kind of the temporary to a common argument one instead of the result, the issue is fixed. Playing around a little bit, one finds that even the GNU extension to MIN/MAX, allowing different argument kinds, is fishy. The attached patch appears regtesting fine, but the coverage of the borderline cases is insufficient yet. I'm not sure I got the GIMPLE magic right everywhere, so the patch may need extended testing before submitting.
next prev parent reply other threads:[~2020-08-16 19:55 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-14 9:09 [Bug libfortran/96613] New: " thomas.huxhorn at web dot de 2020-08-14 15:58 ` [Bug libfortran/96613] " kargl at gcc dot gnu.org 2020-08-14 15:59 ` [Bug fortran/96613] " kargl at gcc dot gnu.org 2020-08-16 19:55 ` anlauf at gcc dot gnu.org [this message] 2020-08-16 19:55 ` anlauf at gcc dot gnu.org 2020-08-16 21:52 ` kargl at gcc dot gnu.org 2020-08-17 18:03 ` anlauf at gcc dot gnu.org 2020-08-17 18:55 ` sgk at troutmask dot apl.washington.edu 2020-08-17 19:05 ` anlauf at gcc dot gnu.org 2020-08-17 20:37 ` anlauf at gcc dot gnu.org 2020-08-18 19:49 ` cvs-commit at gcc dot gnu.org 2020-08-18 20:08 ` anlauf at gcc dot gnu.org 2020-08-20 18:51 ` thomas.huxhorn at web dot de
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-96613-4-H2fn1YkP3B@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).