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.
I tried specifying INLINE(AUTO,REPORT,100,1000) in the compiler PARM input to get the "Inline Report" as documented in the C/C++ User's Guide but I never get an inlined procedure report. Is there some other PARM I need to specify to the compiler to get that report in the SYSPRINT output, or is this another case of a compiler bug, or worse yet "you can't get there from here" because it is MetalC and not plain C? Peter This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
