Displaying 9 results from an estimated 9 matches for "instrumentor".
Did you mean:
instrumenter
2009 Jul 11
1
[LLVMdev] Path profiling interface proposal
...ualberta.ca/~pejic/PathProfiling.html
>
> Slobodan,
>
> This looks interesting. I have a few questions.
Thanks for taking the time to look through!
>
> Is there anything about your proposed profiling method that requires the
> use of lli or llvm-ld? I'm assuming the instrumentor itself will simply
> be a Pass. Will this work in setups that use the machine's native linker
> as long as it links in libprofile_rt?
The current static library libprofile_rt is being built as a .bca file
(archive of .bc files.) Presumably the build process can be changed to
create a n...
2009 Jul 10
0
[LLVMdev] Path profiling interface proposal
...someone has any amendments, I
> can incorporate them.
>
> http://www.cs.ualberta.ca/~pejic/PathProfiling.html
Slobodan,
This looks interesting. I have a few questions.
Is there anything about your proposed profiling method that requires the
use of lli or llvm-ld? I'm assuming the instrumentor itself will simply
be a Pass. Will this work in setups that use the machine's native linker
as long as it links in libprofile_rt?
Is libprofile_rt built during the LLVM build process? Is the intent for
libprofile_rt to be the home for all profiling runtime or just path
profiling? If the lat...
2009 Jul 10
3
[LLVMdev] Path profiling interface proposal
Hello,
I am planning on contributing path profiling to LLVM by the end of
August. I have written a document of what the interface to the path
profiles would look like at that time. If someone has any amendments, I
can incorporate them.
http://www.cs.ualberta.ca/~pejic/PathProfiling.html
Slobodan Pejic
2016 Jun 27
2
The state of IRPGO (3 remaining work items)
...liang David Li <davidxl at google.com>
wrote:
> There is some misunderstanding about the intention of this flag. The
> purpose of the flag is not to turn on profile instrumentation (which
> already has -fprofile-instr-generate or -fprofile-generate for it), but to
> select which instrumentors to use for PGO (IR or FE). I prefer fewer flags
> too, but sharing flags for completely different purpose does not seem like
> the right thing to do.
>
>
Ah, right. It does seem like I'm misunderstanding the intention for that
flag.
FWIW, I think consolidating the flags can happe...
2016 Jun 27
0
The state of IRPGO (3 remaining work items)
There is some misunderstanding about the intention of this flag. The
purpose of the flag is not to turn on profile instrumentation (which
already has -fprofile-instr-generate or -fprofile-generate for it), but to
select which instrumentors to use for PGO (IR or FE). I prefer fewer flags
too, but sharing flags for completely different purpose does not seem like
the right thing to do.
David
On Sun, Jun 26, 2016 at 9:39 PM, Dean Michael Berris <dberris at google.com>
wrote:
> On Fri, Jun 24, 2016 at 1:44 AM Eric Christoph...
2016 Jun 27
2
The state of IRPGO (3 remaining work items)
On Fri, Jun 24, 2016 at 1:44 AM Eric Christopher via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
>
>
> On Thu, Jun 2, 2016, 6:41 PM Xinliang David Li via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>>
>> Sounds fine to me, though I am not a fan of using unstable in the option.
>> I think a more meaningful way (that capture the essence of the
2016 Jun 27
0
The state of IRPGO (3 remaining work items)
...l at google.com>
> wrote:
>
>> There is some misunderstanding about the intention of this flag. The
>> purpose of the flag is not to turn on profile instrumentation (which
>> already has -fprofile-instr-generate or -fprofile-generate for it), but to
>> select which instrumentors to use for PGO (IR or FE). I prefer fewer flags
>> too, but sharing flags for completely different purpose does not seem like
>> the right thing to do.
>>
>>
> Ah, right. It does seem like I'm misunderstanding the intention for that
> flag.
>
> FWIW, I thin...
2016 Mar 09
3
PGO question
Hi,
I have a question regarding PGO.
I collected profile data with the instrumentation build
(-fprofile-instr-generate) and provided for PGO optimization in the second
build (with -fprofile-instr-use=xxx.profdata). This works fine.
Then I tried to provide the profile data to opt using the option
-pgo-instr-use, but this causes an error with the message: "Not an IR level
instrumentation
2016 Mar 12
2
RFC: Pass to prune redundant profiling instrumentation
On Fri, Mar 11, 2016 at 7:04 PM, Sean Silva <chisophugis at gmail.com> wrote:
>
>
> On Fri, Mar 11, 2016 at 6:00 PM, Vedant Kumar <vsk at apple.com> wrote:
>
>>
>> > On Mar 11, 2016, at 5:28 PM, Sean Silva <chisophugis at gmail.com> wrote:
>> >
>> >
>> >
>> > On Fri, Mar 11, 2016 at 12:47 PM, Vedant Kumar <vsk at