------- Comment #4 from simon dot marshall at misys dot com 2008-02-19 12:04
-------
OK, before I start hacking, what is it that you need once I have found a
function?
What I can do is try to identify a function or minimal functions that, when
compiled in a file with optimisation, will cause Emacs to detect inconsistent
internal state, but not when compiled without optimisation. I can compile this
file with "-g -O0 -fno-unit-at-a-time", "-g -O1 -fno-unit-at-a-time" and "-g
-O2 -fno-unit-at-a-time". I can compile all other files with "-g -O2
-fno-unit-at-a-time". Does this sound right?
Once I've found it, what would be useful to you? Output from -E for that file?
Files generated by -S for that file using the flags above? Some other
internal gcc output?
Assuming that I am able to debug this function, any pointers as to what I could
look for that might explain why it is functionally different when compiled with
optimisation?
--
simon dot marshall at misys dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|middle-end |c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35249
