Hi Steve,
Thx for the input. Right. Yes, I know about the idea to have a macro to
align to a 256 bytes boundary.
Philippe
You can make a macro that will do this. At Amdahl we had such at one time.
Where I currently work, we have a macro called ALIGN. It was developed long
before the G3 chipset (where 256byte cache lines came about IIRC).
If you make use of you could control how your expansion works, by
passing
the difference is the option used
THREAD
NOTHREAD
Default THREAD
THREAD Specifies that the assembler not reset the location counter to zero
at the beginning of each CSECT.
NOTHREAD Specifies that the assembler reset the location counter to zero at
the beginning of each CSECT, except for the
; Subject: Rif: Re: Rif: Re: EXECUTE Instruction and location of its
> target instruction
> Sent by: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
>
> > What effect does an unconditional branch have on branch
> prediction/pipelining?
> >
> What effect does an unconditional branch have on branch
prediction/pipelining?
> Is LOCTR a help? I can imagine the frustration of a programmer trying
to
> Does HLASM have an instruction to cause cache line alignment? Such an
> instruction would need to be model-sensitive, perhaps governed by
serv.uga.edu>
> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
> Date: 24/11/2016 00:50
> Subject: Re: Rif: Re: EXECUTE Instruction and location of its target
> instruction
> Sent by: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
>
> On 2016-11-23 07:1
Hi Paul,
Thx much for the input.
ref:Is LOCTR a help?
Actually, I got nicely some infos from Martin T, about LOCTR possible use in
such case, this can be found at
http://www.pi-sysprog.de/free/makerel.html
Philippe
Hi Abe,
Very good point, about old processors. Thx much Philippe
Hi Steve,
Thx for the additional infos relating some similar experience you got. Philippe
On 2016-11-23 07:19, aldo.cro...@csebo.it wrote:
> I think it is appropriate to use a EXRL (execute remote) intest a EX.
> I also think that it is appropriate to place the subject of education
> execute close to the EX, preferably after a statement of unconditional
> branch.
>
Is it recommended
Philippe,
Most of your questions have already been answered by others.
The one thing not yet addressed is this one:
> Reviewing old Assembler programs, I guess I am surprised to see enough often
> that all target instructions for ALL the Execute instructions coded in the
> programs grouped
BTW -- I understand your situation. I have ALC code that I have to bring
forward from a 1980ish coding style to RENT and G3 chipset compliant.
And while it is high priority to get done, I get hit with higher priority work.
So I get limited time to actually make things happen.
I make large
you can also use excel not baseless without problems.
Aldo Crosio
tel: 051-4991812 /3488858416
fax: 051-6255762
CSE Consorzio Servizi Bancari
Società consortile a responsabilità limitata
Via Emilia n. 272
40068-San Lazzaro di Savena (BO)
Ai sensi del D.Lgs. 196/2003 si precisa che le
Hi Aldo,
Thx much for the input. Unfortunately I cannot for that project to implement
Baseless processing therefore I cannot use EXRL instruction. Point is to keep
the target of the execute is in a I-bank cache line, to be ok.
regards Philippe
Hi Steve,
Thx for your input, yes this is my understanding of the process.
Philippe
As long as the target of the execute is not in a D-bank cache line, you
shouldn't see a big "hit" in processing cycles.
If it is, then it has to be flushed out, refetched to I-bank, pulled into the
pipe, processed, flushed back out, and then back to D-bank (if still needed).
This is based on
Martin,
Thx for the input. Unfortunately for current project I am working on, to
convert old asm programs to Baseless processing is NOT an option, there is no
time and no budget to :) .
Later
Philippe
Rob,
>> Most likely for 90% of the code you will never gain back the time you
>> spend on this.
I do more than agree (maybe even 99%) but I will insist that making code
"baseless" eliminates all possibilities I can think of (with 370
instructions) to modify code on the fly and thus improve
Hi Rob,
ref:It's in the same cache line or it's not.
Actually this was exactly my point and I was confused about seen various coding
approaches to reach that purpose to optimize
as much as possible CPU use.
later
Philippe
It's not like we would walk all the way to the location that "more far" is
expensive. It's in the same cache line or it's not. I have a macro to
generate the target in-line to ensure that HLASM knows the USING that
applies to the target, accepting the fact that I sometimes need to branch
over it.
Hi,
My understanding is, we should keep as closest as possible, the EXECUTE
instruction and its target instruction...EXECUTE instruction being greedy
enough in term of CPU use...to be clear dozens of Cycles needed to complete its
execution.
Reviewing old Assembler programs, I guess I am
21 matches
Mail list logo