Re: Trace Scheduling in GCC

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

 



> >
> >I am right about the functionalities of these options?
> >It seems to me that none of these options meets my objective of studying 
> >traces that have mltiple entrances and multiple exits. Please correct me 
> >if I am wrong. And if I am right, is there another way for me to get what 
> >I want, may be by doing some quick hack that bypasses tail duplication 
> >under the -fsched2-use-tarces option -does this make sense?
> >
> > 
> >
> Sorry, I don't know this code well.  I am in the same position as you. 
> I should research the code to answer your questions.  I think Jan is 
> the right person to do it.  Because he wrote this code.

The -fsched2-use-traces is simple superblock scheduler that is preceeded
by trace discovery and tail duplication pass.
So if you want traces directly, you might steal the code from tracer.c
but except for that I don't think it suits your needs very well,
unforutnately.

Honza
> 
> Vlad
> 

[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