On Fri, 10 Feb 2023 at 12:25, Paul Gilmartin < 0000042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:
> On Fri, 10 Feb 2023 16:58:49 +0000, Farley, Peter wrote: > > >I have been writing some MetalC programs and ran into a case where the > normal OPTIMIZE setting (OPT(2)) provably inlined a couple of small > functions. It is not immediately obvious in the MetalC ASM output, but > when the functions are inlined there is no entry point for them, no FPB or > FEPM compiler control data generated for them, etc. > > ... > That's just wrong. Even if the compiler intends to generate inline code > for calls to a function, it > should generate an externally callable entry name, perhaps to an inline > code body, regardless of > optimization level. > Really? What would that be useful for? Pretty much by definition inlined code doesn't have documented calling conventions (indeed they may well vary each time the inlined code is emitted depending on context). I suppose it would be good for there to be an external name for the places the inlined function is called (an ER style entry), but surely not for the actual inlined code. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
