public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/100960] var-tracking: parameter location in subregister not tracked Date: Tue, 08 Jun 2021 09:14:33 +0000 [thread overview] Message-ID: <bug-100960-4-cEm2KKOLan@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100960-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100960 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aoliva at gcc dot gnu.org, | |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- We have two different VALUEs here, (value/u:SI 5:5 @0x4a99810/0x4a402e0) locs: from insn 1 (value/u:SI 6:261 @0x4a99828/0x4a40310) from insn 1 (entry_value:SI (reg:SI 2 %r2 [ x ])) from insn 1 (reg:SI 2 %r2 [ x ]) no addrs and (value/u:DI 15:15 @0x4a99900/0x4a404c0) locs: from insn 17 (reg:DI 12 %r12 [63]) from insn 17 (reg:DI 2 %r2 [ x+-4 ]) no addrs and cselib doesn't record that when insn 17 copies the 15:15 value to a new location it effectively copies also the 5:5 value which is present in its low bits. Maybe it would be better to record among the locs of 5:5 that it is equivalent to lowpart subreg of (value:DI 15:15), perhaps at the point where the value 15:15 is created or so?
next prev parent reply other threads:[~2021-06-08 9:14 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-08 8:33 [Bug debug/100960] New: " stefansf at linux dot ibm.com 2021-06-08 8:53 ` [Bug debug/100960] " rguenth at gcc dot gnu.org 2021-06-08 9:14 ` jakub at gcc dot gnu.org [this message] 2021-06-08 9:48 ` jakub at gcc dot gnu.org 2022-08-11 9:22 ` stefansf at linux dot ibm.com 2022-08-11 9:25 ` stefansf at linux dot ibm.com 2022-08-11 9:27 ` stefansf at linux dot ibm.com
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-100960-4-cEm2KKOLan@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).