[Bug middle-end/34282] Unnecessary load from volatile var

2007-12-26 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2007-12-26 14:29 --- This is correct, return z is an access. I don't see why you would think otherwise. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added -

[Bug middle-end/34282] Unnecessary load from volatile var

2007-11-29 Thread rguenth at gcc dot gnu dot org
--- Comment #3 from rguenth at gcc dot gnu dot org 2007-11-29 10:33 --- Yes, I also think 'return z' is a load from z which cannot be optimized away. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34282

[Bug middle-end/34282] Unnecessary load from volatile var

2007-11-29 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-11-29 10:29 --- I think "return z" is an access. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34282

[Bug middle-end/34282] Unnecessary load from volatile var

2007-11-28 Thread ebotcazou at gcc dot gnu dot org
--- Comment #1 from ebotcazou at gcc dot gnu dot org 2007-11-29 07:13 --- > IMO, there is no need for (1), since we already have correct value in %eax. > However, even when value lives in another register, we should load it into > the return register from the reg, not from mem location.