This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tree-optimization/63375] reordering of reads across fences


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63375

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-09-26
          Component|rtl-optimization            |tree-optimization
     Ever confirmed|0                           |1

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>A read within the region of code enclosed by barriers is being moved out of the regions. 

Actually no.  What is happening is a volatile read is being changed into a non
volatile one.  This is happening during early SRA.

Also this does not happen if val was a global variable rather than a stack
variable.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]