architecture-dependent optimizations

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

 



Hi all,
I'm trying to compile an application for two different target architectures 
using gcc. My goal is to obtain 2 output binaries that have the same control 
flow graph structure. The problem is that , some architecture-dependent 
optimizations tend to modify the cfg structure by removing/merging basic 
blocks etc. Trying to disable such optimizations (using command line 
options), I found that this was rather a complex task cause they are 
dispersed across different  optimization passes, and some times mixed with 
other types of optimizations.
So my question is : Is there a simple and clean why to disable/enable 
architecture-dependent optimizations that affect the cfg structure in gcc?

Thanks in advance for any hint or comment

Aimen


[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