pro64-support
[Top] [All Lists]

Re: A question on feedback in the Pro64

To: "A. Cameron Macdonell" <cam@xxxxxxxxxxxxxx>, <pro64-support@xxxxxxxxxxx>
Subject: Re: A question on feedback in the Pro64
From: "dxq" <dxq@xxxxxxxxx>
Date: Fri, 20 Apr 2001 10:43:44 +0800
References: <Pine.LNX.4.21.0103201442170.7655-100000@sunset.cs.ualberta.ca>
Sender: owner-pro64-support@xxxxxxxxxxx
If you want to enable dynamic profile which has feedback,you
should compile as next steps:
  1) sgicc -fb_create feed_back_file matrix.c  (do instrumentation work)
  2)a.out ( I don't know whether your program read the input file itself,
      if it can't, you should manually send the input to a.out)
  3) sgicc -fb feed_back_file matrix.c (read feedback info and annotation)
  4) a.out  
 but the older version Pro64 did't have a lib "libinstr.so", it is said that 
the 
newest version Pro64 publish the lib. 
  In  driver.cxx , the function WN_Annotate is used to read the feedback 
and annotation. There are transforms and optimizations, so in hyperblock 
formation phase, the edge freq maybe is not the true frequency.
  BTW: In now Pro64 edge does not  have not freq info,but has probability info.
basic block has freq info and does not have prob info.

  a  beginner.
----- Original Message ----- 
From: "A. Cameron Macdonell" <cam@xxxxxxxxxxxxxx>
To: <pro64-support@xxxxxxxxxxx>
Sent: Wednesday, March 21, 2001 5:44 AM
Subject: A question on feedback in the Pro64 


> 
> My question is: do you know if SGI introduced automatic
> profiling in the PRo64. Or else any facilities to enable
> profile feedback optimization. 
> 
> For instance if I have an aplication, say matrix.c, and
> a typical input file, say matrix.inp. What
> would be the compilation steps that I would have to do
> to make sure that the Pro64 hyperblock formation uses
> the edge frequency in the CFG from my input file.
> 
> I can find lots of places in the code where it says it will 
> feedback data if exists but I can't determine how or where
> its being outputted or how to trace it. 
> 
> A pointer to the right place is as good as a direct answer.
> 
> Thanks,
> Cam
> 
> 
>              
> 
> 
> 

<Prev in Thread] Current Thread [Next in Thread>