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 tree-optimization/103033] [12 regression] c-c++-common/auto-init-4.c ICEs starting with r12-4829 Date: Wed, 03 Nov 2021 10:13:06 +0000 [thread overview] Message-ID: <bug-103033-4-OPIxg7QsbS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103033-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103033 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:c081d0a3b0291297f04a05c833d2ffa8de3a7a1a commit r12-4859-gc081d0a3b0291297f04a05c833d2ffa8de3a7a1a Author: Richard Biener <rguenther@suse.de> Date: Wed Nov 3 11:10:19 2021 +0100 middle-end/103033 - drop native_interpret_expr with .DEFERRED_INIT expansion This drops the use of native_interpret_expr which can fail even though can_native_interpret_expr_p returns true in favor of simply folding the VIEW_CONVERT_EXPR punning. 2021-11-03 Richard Biener <rguenther@suse.de> PR middle-end/103033 * internal-fn.c (expand_DEFERRED_INIT): Elide the native_interpret_expr path in favor of folding the VIEW_CONVERT_EXPR generated when punning the RHS.
next prev parent reply other threads:[~2021-11-03 10:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-01 21:53 [Bug tree-optimization/103033] New: " seurer at gcc dot gnu.org 2021-11-02 8:34 ` [Bug tree-optimization/103033] " rguenth at gcc dot gnu.org 2021-11-02 8:40 ` rguenth at gcc dot gnu.org 2021-11-02 18:06 ` qinzhao at gcc dot gnu.org 2021-11-02 18:06 ` qinzhao at gcc dot gnu.org 2021-11-02 18:24 ` rguenth at gcc dot gnu.org 2021-11-03 10:13 ` cvs-commit at gcc dot gnu.org [this message] 2021-11-03 10:13 ` rguenth 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-103033-4-OPIxg7QsbS@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).