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/102285] New flag -ftrivial-auto-var-init=zero causes crash in pr82421.c Date: Mon, 04 Oct 2021 14:54:05 +0000 [thread overview] Message-ID: <bug-102285-4-PS1Swl1ygG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102285-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102285 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #24 from Richard Biener <rguenth at gcc dot gnu.org> --- commit 7e0c0500808d58bca5b8e23cbd474022c32234e4 (origin/master, origin/HEAD) Author: Richard Biener <rguenther@suse.de> Date: Mon Oct 4 11:34:27 2021 +0200 middle-end/102285 - refine .DEFERRED_INIT expansion This refines the way we figure whether we are facing a register that cannot be initialized by emitting a memset away from inspecting expanded RTL of the LHS to using the predicates expand_assignment is using to detect decls or MEM_REFs with non-memory DECL_RTL. 2021-10-04 Richard Biener <rguenther@suse.de> * expr.h (non_mem_decl_p): Declare. (mem_ref_refers_to_non_mem_p): Likewise. * expr.c (non_mem_decl_p): Export. (mem_ref_refers_to_non_mem_p): Likewise. * internal-fn.c (expand_DEFERRED_INIT): Do not expand the LHS but check the base with mem_ref_refers_to_non_mem_p and non_mem_decl_p. * c-c++-common/pr102285.c: New testcase.
next prev parent reply other threads:[~2021-10-04 14:54 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-10 21:50 [Bug c/102285] New: New flag -ftrivial-auto-var-init=zero causes many crashes in the testsuite dcb314 at hotmail dot com 2021-09-10 22:11 ` [Bug middle-end/102285] " qinzhao at gcc dot gnu.org 2021-09-10 22:28 ` qinzhao at gcc dot gnu.org 2021-09-10 22:34 ` pinskia at gcc dot gnu.org 2021-09-10 23:10 ` qing.zhao at oracle dot com 2021-09-12 3:33 ` qinzhao at gcc dot gnu.org 2021-09-12 8:06 ` dcb314 at hotmail dot com 2021-09-13 10:25 ` rguenth at gcc dot gnu.org 2021-09-13 17:30 ` qinzhao at gcc dot gnu.org 2021-09-29 22:44 ` [Bug middle-end/102285] New flag -ftrivial-auto-var-init=zero causes crash in pr82421.c qinzhao at gcc dot gnu.org 2021-09-30 19:30 ` qinzhao at gcc dot gnu.org 2021-09-30 20:22 ` qinzhao at gcc dot gnu.org 2021-09-30 20:53 ` dcb314 at hotmail dot com 2021-09-30 22:09 ` qinzhao at gcc dot gnu.org 2021-10-01 6:51 ` rguenth at gcc dot gnu.org 2021-10-01 9:45 ` egallager at gcc dot gnu.org 2021-10-01 16:16 ` qinzhao at gcc dot gnu.org 2021-10-01 16:43 ` qing.zhao at oracle dot com 2021-10-01 20:09 ` qinzhao at gcc dot gnu.org 2021-10-01 20:23 ` qinzhao at gcc dot gnu.org 2021-10-04 6:27 ` rguenther at suse dot de 2021-10-04 6:29 ` rguenther at suse dot de 2021-10-04 9:10 ` rguenth at gcc dot gnu.org 2021-10-04 9:30 ` rguenth at gcc dot gnu.org 2021-10-04 11:53 ` rguenth at gcc dot gnu.org 2021-10-04 14:54 ` rguenth at gcc dot gnu.org [this message] 2021-10-04 17:16 ` qinzhao at gcc dot gnu.org 2021-10-04 20:34 ` qinzhao at gcc dot gnu.org 2021-10-04 20:59 ` qinzhao at gcc dot gnu.org 2021-10-04 21:44 ` qinzhao at gcc dot gnu.org 2021-10-05 8:36 ` cvs-commit at gcc dot gnu.org 2021-10-05 8:47 ` 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-102285-4-PS1Swl1ygG@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).