RE: Which optimizations cause violation of SESE blocks ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The -O0 (that's oh-zero) supposedly turns off all optimizations.  I don't know if that would affect the types of things that you're talking about, though.

Good luck,
Lyle

-----Original Message-----
From: gcc-help-owner@xxxxxxxxxxx [mailto:gcc-help-owner@xxxxxxxxxxx]On
Behalf Of Siddhartha Shivshankar

platform, and our work requires assembly code produced by gcc
to be structured. (single entry single exit blocks, no side entries, exits from
loops, conditionals with clear merge points, etc. ) We would like to
turn off gcc optimizations that cause such code to be produced.

Is it possible to define such a set of optimizations at all at the outset ?


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux