[Bug inline-asm/36639] pointer referenced in asm statement not regarded as VUSE

2021-08-02 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36639 Andrew Pinski changed: What|Removed |Added CC||moinakb001 at gmail dot com --- Comment

[Bug inline-asm/36639] pointer referenced in asm statement not regarded as VUSE

2008-06-26 Thread aoliva at gcc dot gnu dot org
--- Comment #4 from aoliva at gcc dot gnu dot org 2008-06-26 18:10 --- I have not tried 4.4. Anyhow, I have looked further into this issue, and I came to the conclusion that a memory clobber (that should have always been there anyway) will get things right. I cannot tell for sure that

[Bug inline-asm/36639] pointer referenced in asm statement not regarded as VUSE

2008-06-26 Thread rguenth at gcc dot gnu dot org
--- Comment #3 from rguenth at gcc dot gnu dot org 2008-06-26 10:15 --- I wasn't able to follow your example, but eventually this "bug" is fixed with the call-clobber reorganize patch? -- rguenth at gcc dot gnu dot org changed: What|Removed |Added

[Bug inline-asm/36639] pointer referenced in asm statement not regarded as VUSE

2008-06-25 Thread aoliva at gcc dot gnu dot org
--- Comment #2 from aoliva at gcc dot gnu dot org 2008-06-26 05:12 --- It is indeed documented that way, but one gets to wonder if that's desirable. Consider that in the original testcase the pointer is converted to a physical address (integral type) that must not be dereferenced, and t

[Bug inline-asm/36639] pointer referenced in asm statement not regarded as VUSE

2008-06-25 Thread pinskia at gmail dot com
--- Comment #1 from pinskia at gmail dot com 2008-06-26 03:46 --- Subject: Re: New: pointer referenced in asm statement not regarded as VUSE This is correct as you are just using the address and not the contents itself. This is how inline-asm is documented to work also. -- Andrew