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]

Re: Optimization of conditional access to globals: thread-unsafe?


Michael Matz wrote:

456.hmmer is not a small benchmark, but a real world scientific application for protein sequence analysis using hidden markov models. It just so happens that it also is a standardized benchmark in cpu2006.

A single data point is not data in the sense I refer to. What you want is cumulated data over a significant body of real code. That's not normally a requirement for optimizations, but to me it is for one like this that is disruptive.

The fact that you have an optimization that can help in an individual
case *may* be justification for making it an option, but it is definitely not justification for making it the default when it
is disruptive.


Ciao,
Michael.



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