https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931
--- Comment #27 from rguenther at suse dot de <rguenther at suse dot de> --- On Tue, 23 Jan 2024, jakub at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107931 > > --- Comment #26 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > (In reply to Richard Biener from comment #25) > > Btw, I'd rather go the opposite and make the testcase at hand always invalid > > and diagnosed which means diagnose taking the address of always-inline > > declared functions and never emit an out-of-line body for them. > > That would need an exception at least for gnu extern inline always_inline > functions, > because the way they are used in glibc requires &open etc. to be valid (and > use > then as fallback the out of line open). Sure, already the C frontend should resolve to the out-of-line open call there, we shouldn't do this in the middle-end. Yes, indirect 'open' will then not be fortified, but so what.
