This is the mail archive of the gcc@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]

Re: Loop unrolling


Kaz Kylheku writes:
 > Of course, the compiler in question is GCC, which must meet additional
 > requirements because it is intended to support access to hardware
 > and threading. For that reason it must honor the volatile attribute
 > for static objects, objects referred to through pointers and auto
 > objects whose address is taken, to be safe.

Why can't GCC go a step farther and honor the volatile attribute for
any auto object?  

                                             -gavin...



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