libctf: having debugging enabled is unlikely

The deduplicator can emit enormous amounts of debugging output,
so much so that a later commit will introduce a new configure flag
that configures most of it out (and configures it out by default).

It became clear that when this configure flag is on, but debugging is
not enabled via the LIBCTF_DEBUG environment variable, up to 10% of
runtime can be spent on branch mispredictions checking the _libctf_debug
variable.  Mark it unlikely to be set (when it is set, performance is
likely to be the least of your concerns).

libctf/
	* ctf-subr.c (ctf_dprintf): _libctf_debug is unlikely to be set.
This commit is contained in:
Nick Alcock
2020-06-02 21:00:35 +01:00
parent 601e455b75
commit 5ec7465fec
2 changed files with 5 additions and 1 deletions

@ -183,7 +183,7 @@ int ctf_getdebug (void)
_libctf_printflike_ (1, 2)
void ctf_dprintf (const char *format, ...)
{
if (_libctf_debug)
if (_libctf_unlikely_ (_libctf_debug))
{
va_list alist;