[Bug debug/100960] var-tracking: parameter location in subregister not tracked

2022-08-11 Thread stefansf at linux dot ibm.com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100960 --- Comment #6 from Stefan Schulze Frielinghaus --- Created attachment 53433 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53433=edit a-t2.c.325r.vartrack

[Bug debug/100960] var-tracking: parameter location in subregister not tracked

2022-08-11 Thread stefansf at linux dot ibm.com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100960 --- Comment #5 from Stefan Schulze Frielinghaus --- However, I found another example (see attachment a-t2.c.325r.vartrack) which does not profit from the patch: __attribute__((noinline, noclone)) void fn1 (int x) { __asm volatile ("" : "+r"

[Bug debug/100960] var-tracking: parameter location in subregister not tracked

2022-08-11 Thread stefansf at linux dot ibm.com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100960 --- Comment #4 from Stefan Schulze Frielinghaus --- I really like the idea of enhancing cselib since there is a chance that other passes might profit from it, too. The following patch fixes the initial reported problem: diff --git

[Bug debug/100960] var-tracking: parameter location in subregister not tracked

2021-06-08 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100960 --- Comment #3 from Jakub Jelinek --- Slightly related was https://gcc.gnu.org/legacy-ml/gcc-patches/2010-03/msg01379.html So, perhaps for the case where we do not track the source register in the wider mode we could for var-tracking purpose

[Bug debug/100960] var-tracking: parameter location in subregister not tracked

2021-06-08 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100960 Jakub Jelinek changed: What|Removed |Added CC||aoliva at gcc dot gnu.org,

[Bug debug/100960] var-tracking: parameter location in subregister not tracked

2021-06-08 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100960 --- Comment #1 from Richard Biener --- sounds like an implementation oversight to me.