Hi Andi,
I'll work on putting together some good documentation before sending
this and follow-on support to trunk. As David mentions, the plan for
the subsequent patch to add the hooks that enable users to trigger
gcc's value profiling on particular variables. This first patch simply
allows users
> ===
> --- gcc/builtins.c(revision 210019)
> +++ gcc/builtins.c(working copy)
> @@ -87,6 +87,9 @@ static rtx result_vector (int, rtx);
> #endif
> static void expand_builtin_update_setjmp_buf (rtx);
> static void expand_buil
On Fri, May 09, 2014 at 08:11:40PM -0700, Teresa Johnson wrote:
> Thanks for catching that, I will fix it.
BTW I first misunderstood the goal of you patch.
(probably because there is no documentation ... something that should
also be fixed)
I originally thought it was a way to let user code use
Thanks for catching that, I will fix it.
Teresa
On Fri, May 9, 2014 at 7:49 PM, Andi Kleen wrote:
> Teresa Johnson writes:
>>
>> Passes regression tests. Ok for google branches?
>
> +{
> + char parameter[1000];
> + sprintf (parameter, "%s=%ld",
> + curr_parm->macro_na
Teresa Johnson writes:
>
> Passes regression tests. Ok for google branches?
+{
+ char parameter[1000];
+ sprintf (parameter, "%s=%ld",
The attached patch adds support for user-guided feedback-directed
library optimization, for google/gcc-4_8 initially (to be ported to
google/gcc-4_9).
Cc'ing Honza for any comments since I would eventually like to send
this and follow-on work to trunk.
Patch to add support for user-guided feedbac
