Displaying 19 results from an estimated 19 matches for "unknown_function".
2016 May 24
5
The state of IRPGO (3 remaining work items)
...ied 3 classes of issues which manifest as spammy warnings when
applying profile data with IRPGO (these affect FEPGO also I believe, but we
looked in depth at IRPGO):
1. The main concerning one is that getPGOFuncName mangles the filename into
the counter name. This causes us to get instrprof_error::unknown_function
when the pgo-use build is done in a different build directory from the
training build (which is a reasonable thing to support). In this situation,
PGO data is useless for all `static` functions (and as a byproduct results
in a huge volume of warnings).
2. In different TU's, pre-instr inlining...
2016 May 25
3
The state of IRPGO (3 remaining work items)
...ings when
>> applying profile data with IRPGO (these affect FEPGO also I believe, but we
>> looked in depth at IRPGO):
>>
>> 1. The main concerning one is that getPGOFuncName mangles the filename
>> into the counter name. This causes us to get
>> instrprof_error::unknown_function when the pgo-use build is done in a
>> different build directory from the training build (which is a reasonable
>> thing to support). In this situation, PGO data is useless for all `static`
>> functions (and as a byproduct results in a huge volume of warnings).
>>
>
>...
2016 May 25
0
The state of IRPGO (3 remaining work items)
...manifest as spammy warnings when
> applying profile data with IRPGO (these affect FEPGO also I believe, but we
> looked in depth at IRPGO):
>
> 1. The main concerning one is that getPGOFuncName mangles the filename
> into the counter name. This causes us to get
> instrprof_error::unknown_function when the pgo-use build is done in a
> different build directory from the training build (which is a reasonable
> thing to support). In this situation, PGO data is useless for all `static`
> functions (and as a byproduct results in a huge volume of warnings).
>
Rong, I was just looking...
2016 May 25
0
The state of IRPGO (3 remaining work items)
...pplying profile data with IRPGO (these affect FEPGO also I believe, but we
>>> looked in depth at IRPGO):
>>>
>>> 1. The main concerning one is that getPGOFuncName mangles the filename
>>> into the counter name. This causes us to get
>>> instrprof_error::unknown_function when the pgo-use build is done in a
>>> different build directory from the training build (which is a reasonable
>>> thing to support). In this situation, PGO data is useless for all `static`
>>> functions (and as a byproduct results in a huge volume of warnings).
>>...
2016 May 24
0
The state of IRPGO (3 remaining work items)
...manifest as spammy warnings when
> applying profile data with IRPGO (these affect FEPGO also I believe, but we
> looked in depth at IRPGO):
>
> 1. The main concerning one is that getPGOFuncName mangles the filename
> into the counter name. This causes us to get
> instrprof_error::unknown_function when the pgo-use build is done in a
> different build directory from the training build (which is a reasonable
> thing to support). In this situation, PGO data is useless for all `static`
> functions (and as a byproduct results in a huge volume of warnings).
>
This can be enhanced with...
2016 May 25
0
The state of IRPGO (3 remaining work items)
...as spammy warnings when
> applying profile data with IRPGO (these affect FEPGO also I believe, but we
> looked in depth at IRPGO):
> >
> > 1. The main concerning one is that getPGOFuncName mangles the filename
> into the counter name. This causes us to get
> instrprof_error::unknown_function when the pgo-use build is done in a
> different build directory from the training build (which is a reasonable
> thing to support). In this situation, PGO data is useless for all `static`
> functions (and as a byproduct results in a huge volume of warnings).
> >
> > This can be...
2016 Jun 03
2
The state of IRPGO (3 remaining work items)
...pammy warnings when applying profile data with IRPGO (these affect FEPGO also I believe, but we looked in depth at IRPGO):
>>>> >
>>>> > 1. The main concerning one is that getPGOFuncName mangles the filename into the counter name. This causes us to get instrprof_error::unknown_function when the pgo-use build is done in a different build directory from the training build (which is a reasonable thing to support). In this situation, PGO data is useless for all `static` functions (and as a byproduct results in a huge volume of warnings).
>>>> >
>>>> > Th...
2016 May 24
6
The state of IRPGO (3 remaining work items)
...ses of issues which manifest as spammy warnings when applying profile data with IRPGO (these affect FEPGO also I believe, but we looked in depth at IRPGO):
>
> 1. The main concerning one is that getPGOFuncName mangles the filename into the counter name. This causes us to get instrprof_error::unknown_function when the pgo-use build is done in a different build directory from the training build (which is a reasonable thing to support). In this situation, PGO data is useless for all `static` functions (and as a byproduct results in a huge volume of warnings).
>
> This can be enhanced with an user o...
2016 May 25
2
The state of IRPGO (3 remaining work items)
...gt; when applying profile data with IRPGO (these affect FEPGO also I believe,
>> but we looked in depth at IRPGO):
>> >
>> > 1. The main concerning one is that getPGOFuncName mangles the filename
>> into the counter name. This causes us to get
>> instrprof_error::unknown_function when the pgo-use build is done in a
>> different build directory from the training build (which is a reasonable
>> thing to support). In this situation, PGO data is useless for all `static`
>> functions (and as a byproduct results in a huge volume of warnings).
>> >
>&...
2016 Jun 01
4
The state of IRPGO (3 remaining work items)
...sues which manifest as spammy warnings when applying profile data with IRPGO (these affect FEPGO also I believe, but we looked in depth at IRPGO):
> >
> > 1. The main concerning one is that getPGOFuncName mangles the filename into the counter name. This causes us to get instrprof_error::unknown_function when the pgo-use build is done in a different build directory from the training build (which is a reasonable thing to support). In this situation, PGO data is useless for all `static` functions (and as a byproduct results in a huge volume of warnings).
> >
> > This can be enhanced with...
2007 Jul 14
1
accessing list components with a variable
Let's say I have a list called the_list consisting of three components:
the_list$component_1
the_list$component_2
the_list$component_3
Now, I want to access it using a variable called comp.
comp <- "component_1"
I'm looking for some function that let's me do this:
unknown_function(the_list, comp)
Which should do the same thing as:
the_list$component_1
Any ideas? I'd be open to other ways of doing this, too. I explored
this way, but it didn't seem to get me anywhere:
the_list$"component_1"
I possibly could have gotten further along if I knew how to do...
2020 Jun 01
1
[PATCH] erlang: Port to libei for Erlang 23
...ils.h"
+#include "actions.h"
+
guestfs_h *g;
-extern ETERM *dispatch (ETERM *message);
-extern int atom_equals (ETERM *atom, const char *name);
-extern ETERM *make_error (const char *funname);
-extern ETERM *unknown_optarg (const char *funname, ETERM *optargname);
-extern ETERM *unknown_function (ETERM *fun);
-extern ETERM *make_string_list (char **r);
-extern ETERM *make_table (char **r);
-extern ETERM *make_bool (int r);
-extern char **get_string_list (ETERM *term);
-extern int get_bool (ETERM *term);
-extern int get_int (ETERM *term);
-extern int64_t get_int64 (ETERM *term);
-
/* This...
2016 Jun 02
2
The state of IRPGO (3 remaining work items)
...ch manifest as spammy warnings when applying profile data with IRPGO (these affect FEPGO also I believe, but we looked in depth at IRPGO):
>> >
>> > 1. The main concerning one is that getPGOFuncName mangles the filename into the counter name. This causes us to get instrprof_error::unknown_function when the pgo-use build is done in a different build directory from the training build (which is a reasonable thing to support). In this situation, PGO data is useless for all `static` functions (and as a byproduct results in a huge volume of warnings).
>> >
>> > This can be enhanc...
2016 Jun 02
4
The state of IRPGO (3 remaining work items)
...est as spammy warnings when applying profile data with IRPGO (these affect FEPGO also I believe, but we looked in depth at IRPGO):
>>> >
>>> > 1. The main concerning one is that getPGOFuncName mangles the filename into the counter name. This causes us to get instrprof_error::unknown_function when the pgo-use build is done in a different build directory from the training build (which is a reasonable thing to support). In this situation, PGO data is useless for all `static` functions (and as a byproduct results in a huge volume of warnings).
>>> >
>>> > This can b...
2016 Jun 03
5
The state of IRPGO (3 remaining work items)
...O also I believe,
>>>>> but we looked in depth at IRPGO):
>>>>> >
>>>>> > 1. The main concerning one is that getPGOFuncName mangles the
>>>>> filename into the counter name. This causes us to get
>>>>> instrprof_error::unknown_function when the pgo-use build is done in a
>>>>> different build directory from the training build (which is a reasonable
>>>>> thing to support). In this situation, PGO data is useless for all `static`
>>>>> functions (and as a byproduct results in a huge volu...
2016 Jun 13
2
The state of IRPGO (3 remaining work items)
...lieve, but we looked in depth at IRPGO):
>>>>>>> >
>>>>>>> > 1. The main concerning one is that getPGOFuncName mangles the
>>>>>>> filename into the counter name. This causes us to get
>>>>>>> instrprof_error::unknown_function when the pgo-use build is done in a
>>>>>>> different build directory from the training build (which is a reasonable
>>>>>>> thing to support). In this situation, PGO data is useless for all `static`
>>>>>>> functions (and as a byproduc...
2016 Jun 23
0
The state of IRPGO (3 remaining work items)
...t;>>>>> but we looked in depth at IRPGO):
>>>>>> >
>>>>>> > 1. The main concerning one is that getPGOFuncName mangles the
>>>>>> filename into the counter name. This causes us to get
>>>>>> instrprof_error::unknown_function when the pgo-use build is done in a
>>>>>> different build directory from the training build (which is a reasonable
>>>>>> thing to support). In this situation, PGO data is useless for all `static`
>>>>>> functions (and as a byproduct results in...
2013 Feb 04
1
[PATCH] generator: Add visibility to action struct
...pr "\
@@ -480,7 +480,7 @@ dispatch (ETERM *message)
pr "if (atom_equals (fun, \"%s\"))\n" name;
pr " return run_%s (message);\n" name;
pr " else ";
- ) all_functions_sorted;
+ ) external_functions_sorted;
pr "return unknown_function (fun);
}
diff --git a/generator/fish.ml b/generator/fish.ml
index 077a0b4..411cf11 100644
--- a/generator/fish.ml
+++ b/generator/fish.ml
@@ -31,6 +31,9 @@ open Prepopts
open C
open Events
+let fish_functions_and_commands_sorted =
+ List.sort action_compare (fish_functions_sorted @ fish_comma...
2016 Sep 02
6
[PATCH 0/4] generator: Some work to split large C files
By splitting up large C files we can make parallel compiles
a bit faster.
Rich.