https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104633
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104633
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:c8cb5098c7854a1ed07e85c6165ef0c348d6df1d
commit r12-7358-gc8cb5098c7854a1ed07e85c6165ef0c348d6df1d
Author: Jakub Jelinek
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104633
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104633
Jakub Jelinek changed:
What|Removed |Added
Last reconfirmed||2022-02-22
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104633
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104633
--- Comment #2 from Richard Biener ---
The following is a valid use of extern inline I think
extern int memcmp (const void * p, const void *q, unsigned long size);
extern inline __attribute__((always_inline,gnu_inline))
int memcmp (const void
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104633
--- Comment #1 from Richard Biener ---
Note the inline function needs __attribute__((gnu_inline)) or -fgnu89-inline to
not compile to an endless recursion, but we then still get the undesired
diagnostic.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104633
Richard Biener changed:
What|Removed |Added
Keywords||diagnostic
Target Milestone|---
