public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "qinzhao at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103038] ICE in set_mem_attributes_minus_bitpos, at emit-rtl.c:2092 since r12-4829-g429e3b7d8bf6609d Date: Tue, 02 Nov 2021 15:52:20 +0000 [thread overview] Message-ID: <bug-103038-4-otBC3GzWA4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103038-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103038 --- Comment #6 from qinzhao at gcc dot gnu.org --- just wondering why the ICE after my fix to PR102281. and found the reason: Before the fix to PR102281, the IR before expansion phase is: void test () { <<< Unknown tree: offset_type >>> PtrMem; <bb 2> : PtrMem = .DEFERRED_INIT (8, 1, 0); GIMPLE_NOP PtrMem ={v} {CLOBBER}; return; } After the fix to PR102281, the IR before expansion phase is: void test () { <<< Unknown tree: offset_type >>> PtrMem; <bb 2> : PtrMem_1 = .DEFERRED_INIT (8, 1, 0); return; } the key difference is, Before the PR102281 Fix, the LHS of the call to .DEFERRED_INIT is a VAR_DECL(due to the additional call to __builtin_clear_padding (&PtrMem, ...), and folded to GIMPLE_NOP later). as a result, the RTL expansion for this call went through the MEMSET expansion and succeed. After the PR102281 Fix, the LHS of the call is a SSA name. as a result, the RTL expansion for this call went thought the ASSIGN expansion and exposed the issues for OFFSET_TYPE.
prev parent reply other threads:[~2021-11-02 15:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-02 7:58 [Bug tree-optimization/103038] New: " marxin at gcc dot gnu.org 2021-11-02 7:58 ` [Bug tree-optimization/103038] " marxin at gcc dot gnu.org 2021-11-02 8:51 ` pinskia at gcc dot gnu.org 2021-11-02 8:52 ` rguenth at gcc dot gnu.org 2021-11-02 8:53 ` rguenth at gcc dot gnu.org 2021-11-02 13:17 ` rguenth at gcc dot gnu.org 2021-11-02 13:17 ` cvs-commit at gcc dot gnu.org 2021-11-02 15:52 ` qinzhao at gcc dot gnu.org [this message]
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-103038-4-otBC3GzWA4@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).