Displaying 4 results from an estimated 4 matches for "profile_fil".
Did you mean:
profile_file
2015 Aug 08
3
RFC: PGO Late instrumentation for LLVM
...38.22% 39.96% 15.58%
4. Implementation Details:
We need to add new option(s) for the alternative PGO instrumentation pass
in the middle end. It can in one of the following forms:
(1) Complete new options that are on par with current PGO options:
-fprofile-late-instr-generate[=<profile_file>]? for PGO Instrumentation,
and -fprofile-late-instr-use[=<profile_file>]? for PGO USE.
(2) Or, late instrumentation can be turned on with an additional option
-fprofile-instr-late with current PGO options. I. e. -fprofile-instr-late
-fprofile-instr-generate[=<profile_file>]? for...
2015 Aug 08
2
RFC: PGO Late instrumentation for LLVM
...Details:
>>
>> We need to add new option(s) for the alternative PGO instrumentation pass
>> in the middle end. It can in one of the following forms:
>>
>> (1) Complete new options that are on par with current PGO options:
>> -fprofile-late-instr-generate[=<profile_file>]? for PGO Instrumentation,
>> and -fprofile-late-instr-use[=<profile_file>]? for PGO USE.
>> (2) Or, late instrumentation can be turned on with an additional
>> option -fprofile-instr-late with current PGO options. I. e.
>> -fprofile-instr-late -fprofile-instr-...
2015 Aug 10
3
RFC: PGO Late instrumentation for LLVM
...d new option(s) for the alternative PGO instrumentation
> pass
> >>> in the middle end. It can in one of the following forms:
> >>>
> >>> (1) Complete new options that are on par with current PGO options:
> >>> -fprofile-late-instr-generate[=<profile_file>]? for PGO
> Instrumentation, and
> >>> -fprofile-late-instr-use[=<profile_file>]? for PGO USE.
> >>> (2) Or, late instrumentation can be turned on with an additional
> >>> option -fprofile-instr-late with current PGO options. I. e.
> >>&...
2011 Jul 21
0
Templates and self-knowledge
...(actually, it generates more than that, as I pass in
zfs_root=>"c1" or whatever is necessary. However, while this is very
flexible, it''s also very ... specific. As in, the define that I''ve created
to use this file isn''t really re-usable elsewhere:
define profile_file($zfs_root = "undef") {
>
> file{"/jumpstart/Profiles/$name":
>
> require => File["/jumpstart/Profiles"],
>
> content => template("jumpstart/solaris_profile.erb"),
>
> mode => 0644
>
> }
>
&g...