--- Comment #7 from aleksazr at gmail dot com 2010-07-30 14:00 ---
Poor listings = listings without debug info.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45127
--- Comment #6 from aleksazr at gmail dot com 2010-07-30 13:56 ---
Anyway, the files can be used to generate poor listings,
and that is also a bug. See method2.lss
--
aleksazr at gmail dot com changed:
What|Removed |Added
--
--- Comment #5 from aleksazr at gmail dot com 2010-07-29 19:19 ---
Thank you for a good explanation. Cheers!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45127
--- Comment #4 from rearnsha at gcc dot gnu dot org 2010-07-29 16:29
---
Volatile alone won't prevent re-ordering of non-volatile memory operations.
The volatile keyword only applies to that particular location (requiring the
compiler not to remove it, or change the number of accesses)
--- Comment #3 from aleksazr at gmail dot com 2010-07-29 14:56 ---
Created an attachment (id=21351)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21351&action=view)
all sources
--
aleksazr at gmail dot com changed:
What|Removed |Added
---
