On 2017-02-23, at 07:57, Steve Thompson wrote:
> Ah, I see why you all are having a problem with this.
>
> And me, being an old ALC programmer, this is intuitively obvious. In fact,
> there are several changes to HLASM that I disagreed with, because they then
> caused programs I had written earlier to start getting informative messages,
> where they didn't get them before.
>
Informative? Or Warning? Do you then disagree with warnings on
multiple base-displacement resolutions?
> So, you want the immediate area to be filled with a replication. But that
> means that the assembler now must pay attention to the replication value --
> which it may not know until after the instruction has to be generated, and
> ensure that it does not exceed the immediate are of the instruction.
>
Any self-defining term ought to be acceptable as an immediate operand.
But can a self-defining term contain a replication factor?
On Wed, 22 Feb 2017 16:18:38 -0500, Melvyn Maltz wrote:
>Immediate operands won't accept a duplication factor...why not ?
>Can't find a reason in the HLASM manual
>
>Try these...
>AHI R1,2X'FF'
>AHI R1,X'FFFF'
>AHI R1,-1
>
How do you (and HLASM) feel about?:
AHI R1,X'00FFFF'
-- gil
