Modernize obsolete inline order #4196
Conversation
|
The one test failure is |
|
yes, may be same issue as sometimes seen in Azure - the CI jobs simply get scheduled on varying generations of hardware |
|
It is in -Wextra since gcc3. Is it becoming a problem recently? |
It is not an immediate problem, but I can see no reason why it should not be fixed. AFAIK the last time this syntax was legal was K&R C, before the C89 standard. Compilers are still accepting it, but this should not be relied upon, unless there is a good reason for it. Standard violations have a tendency to haunt you after a long period of no problems. The CBLAS hidden argument problems were also a case where violating the standard was OK for a long time, until one day it was not. |
|
Good job, its really continuous maintenance, like 2-3 nonsensical warning appearing with each new compiler release, like wrong front spacing or double vertical spacing.... |
3 participants
A handful of functions are declared like this:
static void __inline .....Apparently this is a non-standard, obsolete format, as the C standard demands that
static,inlineand similar must be specified before the return type. If extra warnings are enabled during build, GCC 11 issues this:warning: ‘__inline’ is not at beginning of declaration [-Wold-style-declaration]I am not aware that this causes any issues, but it is better to conform to the standard, unless there is reason not to.
This PR switches the placement of inline wherever applicable.