Echoing Binyamin’s post, why is this not simply flagged by the assembler?
Assuming it’s valid code, Is the result of its execution to put the section
offset of MYLABEL in the low half of R3 (leaving the high half unaltered)?
Keven
> On Nov 24, 2020, at 00:06, Binyamin Dissen wrote:
>
> On
Yes, definitely interesting stuff. I'm pretty pedestrian and have only used the
newer insert instructions with actual immediate values, probably as the
designers intended...
IILF R2,C'HOLA'
IILF R2,EquHOLA
EquHOLA EQU C'HOLA'
Resulting in x'C8D6D3C1' in R2. But when C'HOLA' is defined as
On Mon, 23 Nov 2020 20:11:45 -0500 Melvyn Maltz
<072265160664-dmarc-requ...@listserv.uga.edu> wrote:
:>I have to thank my esteemed colleague Don Higgins for enabling this post
:>IILF R3,MYLABEL
...
:>MYLABEL DC 'HELLO'
:>This is interesting on a number of levels, yes, the immediate value is
IILF and LGFI will load whatever is in the immediate operand. PoOps is
perfectly clear on that. What goes into the high bit is an assembler issue, but
anything but 0 would cause problems. If you're going to us it in, e.g., BASSM,
the use FOO+X'8000' rather than FOO for switching to 31 bit mo
I have to thank my esteemed colleague Don Higgins for enabling this post
IILF R3,MYLABEL
...
MYLABEL DC 'HELLO'
This is interesting on a number of levels, yes, the immediate value is
relocatable
I guess this is a 'good thing' for 32-bit immediate instructions...hmmm
My concern is though, are th
I thought I could segregate the SRB code which had references to external
module
Meaning put the external =V CSRC calls
And keep it in the same
Class from the doc it seemed that XATTR would have external module in the same
class I could then move the entire class to
CSA
You seem to say
Ref: Your note of Sun, 22 Nov 2020 17:03:38 -0500
Joe Reichman writes:
> I wrapped my SRB code around a CATTR since it going to be moved my question
> now is to reference the starting address is that a V con or A con
I don't know why you would want to use CATTR for this purpose,
and I cannot t
