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 target/99648] [11 regression] gcc.dg/torture/pr71522.c fails starting with r11-165 for 32 bits Date: Fri, 19 Mar 2021 07:39:19 +0000 [thread overview] Message-ID: <bug-99648-4-aVFHfyY0Y8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99648-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99648 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code Last reconfirmed| |2021-03-19 Target Milestone|--- |11.0 Status|UNCONFIRMED |WAITING Ever confirmed|0 |1 Component|other |target --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Yes, there's cfgexpand.c avoid_type_punning_on_regs which looks for integral accesses of FP registers but only disables + && maybe_lt (GET_MODE_PRECISION (DECL_MODE (base)), + GET_MODE_BITSIZE (GET_MODE_INNER (DECL_MODE (base)))) so the question is how the situation is with the case where it execute FAILs (I can't check/verify that easily). Can you please show failing assembler and RTL?
next prev parent reply other threads:[~2021-03-19 7:39 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-18 15:31 [Bug other/99648] New: " seurer at gcc dot gnu.org 2021-03-18 16:42 ` [Bug other/99648] " jakub at gcc dot gnu.org 2021-03-19 7:39 ` rguenth at gcc dot gnu.org [this message] 2021-03-30 20:01 ` [Bug target/99648] " seurer at gcc dot gnu.org 2021-03-30 20:06 ` seurer at gcc dot gnu.org 2021-03-31 7:41 ` rguenth at gcc dot gnu.org 2021-04-09 16:48 ` jakub at gcc dot gnu.org 2021-04-09 17:42 ` jakub at gcc dot gnu.org 2021-04-12 6:44 ` rguenth at gcc dot gnu.org 2021-04-12 9:10 ` jakub at gcc dot gnu.org 2021-04-12 10:27 ` jakub at gcc dot gnu.org 2021-04-12 11:30 ` rguenth at gcc dot gnu.org 2021-04-12 11:34 ` jakub at gcc dot gnu.org 2021-04-13 7:42 ` cvs-commit at gcc dot gnu.org 2021-04-13 7:42 ` jakub 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-99648-4-aVFHfyY0Y8@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).