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] |
Other format: | [Raw text] |
On Fri, 7 May 2004, Daniel Jacobowitz wrote:
[By the way, I'm surprised to hear that CodeWarrior will schedule outside code interleaved with an asm block. That seems like a really bad idea!]
It is a really bad idea.
If you're doing driver-level work, then you need barriers to ensure writes occur in the correct order and are flushed out properly. If you schedule other code in between, this may not work properly.
Toshi
Just to keep things in perspective, it doesn't seem that CW does much rearrangement, in fact I don't remember ever seeing it do that. One could imagine Metrowerks taking a conservative approach and treating all but the most innocuous instructions as barriers.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |