[Gluster-devel] Gluster and GCC 5.1
josferna at redhat.com
Fri Jul 3 03:08:18 UTC 2015
Agree with Jeff
But now the question is should we have this patch go through or leave it to float in time and space :)
The patch just makes the existing inline calls static or extern appropriately without causing any harm to the existing
code but removes the risk of undefined symbols for normal inline functions in gcc 5 and above!
----- Original Message -----
From: "Jeff Darcy" <jdarcy at redhat.com>
To: "Kaleb S. KEITHLEY" <kkeithle at redhat.com>
Cc: "gluster-infra" <gluster-infra at gluster.org>, "Gluster Devel" <gluster-devel at gluster.org>
Sent: Friday, July 3, 2015 6:05:14 AM
Subject: Re: [Gluster-devel] Gluster and GCC 5.1
> Or perhaps we could just get everyone to stop using 'inline'
I agree that it would be a good thing to reduce/modify our use of
'inline' significantly. Any advantage gained from avoiding normal
function-all entry/exit has to be weighed against cache pollution from
having the same code repeated over and over each place the function is
invoked. Careful use of 'extern inline' can be good for performance
and/or readability once in a great while, but IMO we should avoid
'inline' except in cases where the benefits are *proven*.
On a similar note, can we please please please get people to stop
abusing macros so much? I get that they're sometimes useful to get
around C's lack of generics or other features, but many of our long
complicated macros have no such justification. These pollute the cache
just like 'inline' does, plus they make code harder to debug or edit.
Gluster-devel mailing list
Gluster-devel at gluster.org
More information about the Gluster-devel