public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111907] ICE: in curr_insn_transform, at lra-constraints.cc:4294 unable to generate reloads for: {*andnottf3} with -mavx512f -mno-evex512 Date: Sat, 04 Nov 2023 22:34:31 +0000 [thread overview] Message-ID: <bug-111907-4-fGcYroOXAo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111907-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111907 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|ICE: in |ICE: in |curr_insn_transform, at |curr_insn_transform, at |lra-constraints.cc:4294 |lra-constraints.cc:4294 |unable to generate reloads |unable to generate reloads |for: {*andnottf3} with |for: {*andnottf3} with |-mavx512f -mno-evex512 |-mavx512f -mno-evex512 |-mbionic | --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Simplified testcase: ``` _Float128 foo (_Float128 d, _Float128 e) { return __builtin_copysignf128 (d, e); } ``` Just use `-mavx512f -mno-evex512` . No reason for the `-mbionic` here (which changes `long double` into the IEEE128 bit long double rather than the 90bit long double.
next prev parent reply other threads:[~2023-11-04 22:34 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-21 9:20 [Bug target/111907] New: ICE: in curr_insn_transform, at lra-constraints.cc:4294 unable to generate reloads for: {*andnottf3} with -mavx512f -mno-evex512 -mbionic zsojka at seznam dot cz 2023-11-04 22:34 ` pinskia at gcc dot gnu.org [this message] 2023-11-04 22:34 ` [Bug target/111907] ICE: in curr_insn_transform, at lra-constraints.cc:4294 unable to generate reloads for: {*andnottf3} with -mavx512f -mno-evex512 pinskia at gcc dot gnu.org 2023-11-04 22:44 ` pinskia at gcc dot gnu.org 2023-11-06 2:54 ` haochen.jiang at intel dot com 2023-11-06 2:59 ` haochen.jiang at intel dot com 2023-11-07 2:28 ` haochen.jiang at intel dot com 2023-11-08 5:51 ` cvs-commit at gcc dot gnu.org 2023-11-08 5:52 ` haochen.jiang at intel dot com 2023-11-30 10:45 ` liuhongt 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-111907-4-fGcYroOXAo@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).