On 07/04/2025 17:08, Paul Gilmartin wrote:
On 4/7/25 08:25, Jonathan Scott wrote:
Peter, please change the thread subject when asking a different question. I've done so now. And
although I'm often around now (being retired) any new question should be addressed to the list!
.
And here I re
On 4/7/25 10:13, Peter Sylvester wrote:
...
My question was badly written. i did not want to talk about the asm
END statement, but about the END record/card in the object deck. well,
one can use HEWLDIA and friends.
.
In fact, I was modifying a FOSS compiler which generated an object file
d
On Mon, 7 Apr 2025 15:25:44 +0100 Jonathan Scott
wrote:
:>1. If you overlay a relocatable field with another relocatable field, you are
giving the assembler two conflicting definitions of the same storage location.
There will be more than one RLD (not ESD) entry and the results are likely to
hi: On 07/04/2025 16:31, Charles Mills wrote:
Right, your example is almost exactly what is said in the doc of the org
instructiion
With the ORG statement, you can give two instructions the same location counter values. In such a
case, the second instruction does not always eliminate the effec
On 4/7/25 08:25, Jonathan Scott wrote:
Peter, please change the thread subject when asking a different question. I've
done so now. And although I'm often around now (being retired) any new
question should be addressed to the list!
.
And here I respond to only one question, not two.
Should
On 4/7/25 08:31, Charles Mills wrote:
With regard to the first one, I don' think it will generate any ESDs unless you
code EXTRN (or similar) for each of your whatevers.
If you do so, then I think HLASM generates an ESD even in cases where a human
could tell it was problematic coding. For exam
Peter, please change the thread subject when asking a different question. I've
done so now. And although I'm often around now (being retired) any new
question should be addressed to the list!
1. If you overlay a relocatable field with another relocatable field, you are
giving the assembler tw
hi js,
i have two questions about hlasm
1 - which the following snippet in a csect
dc f'1'
x dc a(whatever)
org x
dc a(whatever)
it seem that one gets two esd entires ... that are supposed to treated by the
binder how?
(i may not use my personal eyeball utility
On Mon, 7 Apr 2025 13:25:12 +0100 Martin Ward wrote:
:>At the end of a listing is the line: "N Object Records Written".
:>How many bytes is each object record?
:>I have a large number of listings, but no access to the object files,
:>and would like to know the size distribution of object files
:
If you simply want to know program sizes, you can normally get accurate values
from the CSECT (SD) lengths shown in the ESD section of the listing.
Jonathan Scott
The object record format is fully documented:
https://www.ibm.com/docs/en/hla-and-tf/1.6.0?topic=output-object-deck
There are normally 56 bytes of module data in each TXT record, but there may be
less if there is a location counter break, for example for a non-empty DS, ORG,
or some forms of al
At the end of a listing is the line: "N Object Records Written".
How many bytes is each object record?
I have a large number of listings, but no access to the object files,
and would like to know the size distribution of object files
(eg how many fit into 1K, how many fit into 4K etc).
Thanks!
12 matches
Mail list logo
