Follow-up: I was directed by one of the esteemed members of this list to an IBM
discussion list in the "IBM Z and LinuxONE Community" for C/C++ issues, where I
posed this same question. I received a reasonably prompt response from a
person in the IBM compiler development team, which I will past
I said in the pmap, i.e. the section of the listing produced by the LIST
compiler option.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Andrew Rowley
Sent: Friday, February 10, 2023 5:45 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How to get MetalC "I
On 11/02/2023 7:42 am, Farley, Peter wrote:
I'd consider this to be a bug in the compiler. The listing pmap should show all
source statements, at the place where they are executed. If they are inlined
twice, they should be listed twice.
That sounds like it would ultimately be confusing. An in
Schmitt, Michael
Sent: Friday, February 10, 2023 3:33 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How to get MetalC "INLINE" report
There are two cases for inlining:
1. The performed paragraph was only performed from one place
2. The performed paragraph was performed from multiple plac
iscussion List On Behalf Of
Farley, Peter
Sent: Friday, February 10, 2023 11:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How to get MetalC "INLINE" report
AFAIK, not the way inlining works on any z/OS compiler output I have ever seen.
Recent versions of Enterprise COBOL, for instance
On Fri, 10 Feb 2023 12:32:28 -0500, Tony Harminc wrote:
>On Fri, 10 Feb 2023 at 12:25, Paul Gilmartin wrote:
>...
>> 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
Subject: Re: How to get MetalC "INLINE" report
AFAIK, not the way inlining works on any z/OS compiler output I have ever seen.
Recent versions of Enterprise COBOL, for instance, can inline performed
paragraphs (and tell you that they did so) such that no HLL debugger known to
me can le
to get MetalC "INLINE" report
On Fri, 10 Feb 2023 16:58:49 +, 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 th
On Fri, 10 Feb 2023 at 12:25, Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:
> On Fri, 10 Feb 2023 16:58:49 +, 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
On Fri, 10 Feb 2023 16:58:49 +, 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
>
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 compi
11 matches
Mail list logo
