This is the mail archive of the gcc-patches@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: [rtlopt] Value profiling and optimalizations


> > > Hello,
> > > 
> > > > >   #define GCOV_TAG_LOOP_HISTOGRAMS ((unsigned)0x01a30000)
> > > > > + #define GCOV_TAG_VALUE_HISTOGRAMS ((unsigned)0x01a50000)
> > > > What makes value histograms different from loop histograms for gcov?
> > > > It would perhaps make sense to comonize more of the loop and value
> > > > histograms code.
> > > 
> > > There is nothing different in them; I use different tags because loop
> > > histograms and value histograms may be used independently (or both
> > > together). A bit more of the code could indeed be shared (mostly the parts in
> > > libgcc2.c).
> > Hmm, I am not sure, but perhaps it would make more sense if profiling code
> > allowed measuring histogram of any quantities and loop code just used it
> > for the iteration counts and other code for other values?
> 
> It already uses the same code for measuring the histograms; I definitely
> want to keep the counters separated, but I am going to rewrite the
You mean the basic block counters or the loop iteration histograms?
In first case I agree.
In second case what makes the loop iteration histograms different?
> libgcc part soon so that the storing is done in a more generic way.
Thanks!

Honza
> 
> Zdenek


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