public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111082] [14 Regression] ICE in expand_fn_using_insn, at internal-fn.cc:214 (AVX512 related) Date: Mon, 21 Aug 2023 09:05:51 +0000 [thread overview] Message-ID: <bug-111082-4-3ZjKqeth16@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111082-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111082 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Interestingly we have CODE_FOR_reduc_smin_scal_v2di at vectorizable_bb_reduc_epilogue time where we check && (!reduction_fn_for_scalar_code (reduc_code, &reduc_fn) || reduc_fn == IFN_LAST || !direct_internal_fn_supported_p (reduc_fn, vectype, OPTIMIZE_FOR_BOTH))) which passes. But at that point we have a signed MIN. I have a patch.
next prev parent reply other threads:[~2023-08-21 9:05 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-20 12:23 [Bug middle-end/111082] New: " manuel.lauss at googlemail dot com 2023-08-20 12:33 ` [Bug middle-end/111082] " manuel.lauss at googlemail dot com 2023-08-20 17:29 ` [Bug middle-end/111082] [14 Regression] " pinskia at gcc dot gnu.org 2023-08-20 23:30 ` pinskia at gcc dot gnu.org 2023-08-21 8:41 ` rguenth at gcc dot gnu.org 2023-08-21 9:05 ` rguenth at gcc dot gnu.org [this message] 2023-08-21 9:48 ` cvs-commit at gcc dot gnu.org 2023-08-21 9:48 ` rguenth at gcc dot gnu.org 2023-08-21 16:35 ` 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-111082-4-3ZjKqeth16@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).