You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I decided to look inside NYTProf on Win32, since Ive used it a couple times, but it has some dire warnings about it using Time::HiRes added in bc9145a , but looking at my binary shows this to be false, perl has had HAS_GETTIMEOFDAY since 2002 Perl/perl5@57ab3df in Win32 which a wrapper around Win32's GetSystemTimeAsFileTime C function. No compensation or adjustments are done to the time other than fixed unit conversions. So NYTProf doesn't use QueryPerformanceCounter directly (I'd like to implement that) or indirectly through Time::HiRes. Can you give some explanation about that comment about NYTProf on Win32?
I also have a PERL_NO_GET_CONTEXT patch almost done.
Also load_sub_callers_callback and pretty much all of NYTProf uses av_fetch a ton. Why not use AvARRAY everywhere? I assume the private av can't be tied.
The text was updated successfully, but these errors were encountered:
I decided to look inside NYTProf on Win32, since Ive used it a couple times, but it has some dire warnings about it using Time::HiRes added in bc9145a , but looking at my binary shows this to be false, perl has had HAS_GETTIMEOFDAY since 2002 Perl/perl5@57ab3df in Win32 which a wrapper around Win32's GetSystemTimeAsFileTime C function. No compensation or adjustments are done to the time other than fixed unit conversions. So NYTProf doesn't use QueryPerformanceCounter directly (I'd like to implement that) or indirectly through Time::HiRes. Can you give some explanation about that comment about NYTProf on Win32?
I also have a PERL_NO_GET_CONTEXT patch almost done.
Also why does https://github.com/timbunce/devel-nytprof/blob/master/NYTProf.xs#L4305
exist?
Also load_sub_callers_callback and pretty much all of NYTProf uses av_fetch a ton. Why not use AvARRAY everywhere? I assume the private av can't be tied.
The text was updated successfully, but these errors were encountered: