I thought that I was cynical, but I would not have predicted it.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Assembler List [[email protected]] on behalf 
of Kerry Liles [[email protected]]
Sent: Sunday, June 7, 2020 9:57 PM
To: [email protected]
Subject: Re: Does the z architecture have something like the SIMD instructions

Ed, I too would be interested in your presentation from March 2017 SHARE ...

I can only imagine the barrage of knee-jerk responses you likely
encountered.
Sad but unfortunately predictable.

regards,

Kerry Liles


On Sun, 7 Jun 2020 at 18:23, Ed Jaffe <[email protected]> wrote:

> On 6/7/2020 9:23 AM, Farley, Peter x23353 wrote:
> > Is there any chance you could provide (maybe eventually in a SHARE
> session presentation?) a set of good examples of using the vector
> instructions as you say you do?
>
> Peter,
>
> There was a thread called "Count Words" into which at one time I posted
> some pseudo code and/or an example of our generalized string find code
> that went into the field with (E)JES in Sep 2016.
>
> I endured wise cracks, imagined 16-byte limitations, and erroneous
> claims to the effect: we were using the wrong instructions, performance
> no longer matters, such coding is best left to compilers, etc.
>
> Rather than deal with any more of that "static," I've decided to
> directly email you a copy of Slide 21 from my March 2017 SHARE San Jose
> session entitled, "z13s User Experiences" (which won a best session
> award BTW) in which I touted the new Vector Facility as being a "game
> changer" for our platform and provided sample code anyone can use to
> replaces SRST with a loop of vector instructions.
>
> Thanks...
>
> --
> Phoenix Software International
> Edward E. Jaffe
> 831 Parkview Drive North
> El Segundo, CA 90245
> https://secure-web.cisco.com/1NHljwdIbMHXIaBdyDWCAwFHvBswn2N8TE-tMXDX6qMM_iRCQgrx7LjjckSfsxacJhM_JxM4evtTAjUeOFYzQPe7Xcn4b0vuwI6EgTZbJa3HGxL4kzY_jyvqcEvfbUZRRwl8qPAhQ7xVjgFDCQf4nx3n8RyvC8JEOY-2BazrQH6akCTVXbhzyQ_J8evtapPyGPp3P4nEyPK_IbhJN_v4KB437fpx-ToLHBnWxxNZ8xIeKjrzn3aIprRcGbESiBM5lV03_poFfo1KZnhecmUyCxgRM3e4Of-STVCecm_WUKdvSFRxGu8Su7XXwqG2jZaTvsuzNF1p4PvadRi-DKw63Sp0XgE68mvj8nuzbUw2SP2T7p-bOQfGQbp2d9FpGO5jRCkSqYgUNs-ubfVflc34ULOz81kGSCgpiNovI9tFAMlZoTIvrns17SCcWmj-xJA83/https%3A%2F%2Fwww.phoenixsoftware.com%2F
>
>
>
> --------------------------------------------------------------------------------
> This e-mail message, including any attachments, appended messages and the
> information contained therein, is for the sole use of the intended
> recipient(s). If you are not an intended recipient or have otherwise
> received this email message in error, any use, dissemination, distribution,
> review, storage or copying of this e-mail message and the information
> contained therein is strictly prohibited. If you are not an intended
> recipient, please contact the sender by reply e-mail and destroy all copies
> of this email message and do not otherwise utilize or retain this email
> message or any or all of the information contained therein. Although this
> email message and any attachments or appended messages are believed to be
> free of any virus or other defect that might affect any computer system
> into
> which it is received and opened, it is the responsibility of the recipient
> to ensure that it is virus free and no responsibility is accepted by the
> sender for any loss or damage arising in any way from its opening or use.
>

Reply via email to