Well, @Captain, I stand corrected.
(That was me in error.)
Charles
On Wed, 6 Nov 2024 13:20:58 -0800, Tom Ross wrote:
>>On Sun, 3 Nov 2024 14:59:20 -0600, Paul Gilmartin wr=
>>ote:
>>
>>>It would be a disservice to customers to retire 24-bit support berore
>>>all IBM programming interfaces s
>On Sun, 3 Nov 2024 14:59:20 -0600, Paul Gilmartin wr=
>ote:
>
>>It would be a disservice to customers to retire 24-bit support berore
>>all IBM programming interfaces support AMODE 31.
>
>Do *any* of the modern compilers (C, COBOL, PL/I) "support 24-bit addressin=
>g"? What would that mean, exact
On Mon, 4 Nov 2024 at 09:30, Seymour J Metz wrote:
> 1. No, it was an RPQ.
>
> 2. No, it was TSS/360.
>
> It turned out that there were practical issues with 32-bit code, e.g., BXH
> and BXLE used signed arithmetic.
>
That problem has returned with 64-bit mode in zArch.
1. No, it was an RPQ.
2. No, it was TSS/360.
It turned out that there were practical issues with 32-bit code, e.g., BXH and
BXLE used signed arithmetic.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
Sorry, I misspoke. The only OS that could use 32-bit addressing on a model
67 was TSS.
http://www.bitsavers.org/pdf/ibm/360/tss/C28-2008-0_TSSsysPgmr_Oct67.pdf
Joe
On Mon, Nov 4, 2024 at 1:04 AM Jay Maynard <
05997213d6c2-dmarc-requ...@listserv.ua.edu> wrote:
> Didn't CP/67
Didn't CP/67 support 32-bit addresses as well?
On Mon, Nov 4, 2024 at 12:03 AM Joe Monk <
05971158733e-dmarc-requ...@listserv.ua.edu> wrote:
> "I understand the model 67 supported 32-bit addresses."
>
> 1. It was an PRPQ
> 2. the only OS support for 32-bits
"I understand the model 67 supported 32-bit addresses."
1. It was an PRPQ
2. the only OS support for 32-bits was in ACP/TPF
Joe
On Sun, Nov 3, 2024 at 2:59 PM Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:
> On Fri, 1 Nov 2024 15:45:07 -050
ands).
>
>Are there any obstacles?
>
>Thank you, kind regards
>
>Bernd
>
>
>Am 02.11.2024 um 13:06 schrieb René Jansen:
>> Hi Linda,
>>
>> thank you - and your colleague - very much for this answer. I think people
>> who use 31-bit and 32-bit inte
On Sun, 3 Nov 2024 14:59:20 -0600, Paul Gilmartin wrote:
>It would be a disservice to customers to retire 24-bit support berore
>all IBM programming interfaces support AMODE 31.
Do *any* of the modern compilers (C, COBOL, PL/I) "support 24-bit addressing"?
What would that mean, exactly? Their l
docs/en/open-xl-c-cpp-zos/2.1?topic=new-32-bit-support .
>For downloading it:
>https://early-access.ibm.com/software/support/trial/cst/programwebsite.wss?siteId=2041&h=null&p=null
> .
>The documentation says that the compiler supports both 64-bit and 31-bit
>addressin
Tried to reply privately - but it bounced..
It's my understanding that the older IBM compiler continues to be supported for
some time yet, which affords a little time.
And - of course - there is the Dignus compiler - which continues to support IBM
mode for older programs and isn't tied to parti
very much for this answer. I think people who use 31-bit
and 32-bit interchangeably are missing a bit - the one that I sometimes used to weed out
impostors in job interviews. Also, Ed de Castro's "no mode bit!" (From The Soul
of a New Machine - Tracy Kidder - I can recommend tha
Hi Linda,
thank you - and your colleague - very much for this answer. I think people who
use 31-bit and 32-bit interchangeably are missing a bit - the one that I
sometimes used to weed out impostors in job interviews. Also, Ed de Castro's
"no mode bit!" (From The Soul of a New
On Fri, 1 Nov 2024 13:47:36 +0100, René Jansen wrote:
>Reading through the release notes (the "what's new") of the LLVM-Clang based
>C/C++ compiler for z/OS I see support for 32-bit programs and XPLINK32
>linkage. Now I have to admit that I not followed all news clo
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
> >
> >
> >
> >
> > From: IBM Mainframe Discussion List on
> behalf of Mike Schwab <05962a42dc49-dmarc-requ...@listserv.ua.edu>
> > Sent: Friday, November 1, 2024 1:15 PM
>
riday, November 1, 2024 1:15 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: 32 bit
>
> Caution: This email did not originate from George Mason’s mail system. Do not
> click links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
>
From: IBM Mainframe Discussion List on behalf of
Mike Schwab <05962a42dc49-dmarc-requ...@listserv.ua.edu>
Sent: Friday, November 1, 2024 1:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: 32 bit
Caution: This email did not originate from George Mason’s mail
I don't know if this is the case here, but it is possible to write a
program to run in addressing mode 64 but use 32 bit instructions so it
works inside the 4GB address range.
On Fri, Nov 1, 2024 at 11:46 AM Tony Harminc wrote:
>
> On Fri, 1 Nov 2024 at 08:59, René Jansen wrote:
&g
On Fri, 1 Nov 2024 at 08:59, René Jansen wrote:
> Reading through the release notes (the "what's new") of the LLVM-Clang
> based C/C++ compiler for z/OS I see support for 32-bit programs and
> XPLINK32 linkage. Now I have to admit that I not followed all news closely
Reading through the release notes (the "what's new") of the LLVM-Clang based
C/C++ compiler for z/OS I see support for 32-bit programs and XPLINK32 linkage.
Now I have to admit that I not followed all news closely but I even have a hard
time googling this. I thought there is 24-
tin
> Sent: Tuesday, March 14, 2017 2:31 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: C fprintf() format code for 32-bit float?
>
> On Mon, 13 Mar 2017 21:50:30 -0700, retired mainframer wrote:
>
> >fprintf is a variadic function. Therefore any float passed to the fu
On Mon, 13 Mar 2017 21:50:30 -0700, retired mainframer wrote:
>fprintf is a variadic function. Therefore any float passed to the function
>will be automatically promoted to double before the function is called (as
>long as the prototype is in scope). ...
>
Isn't that true even if the programmer
At a customer of mine we had a graphic package which did the
presentation layer of the scientific and technical applications (called
GKS,
graphic kernel system). The output of GKS went to plotters (Calcomp)
and graphic displays (via GDDM). The interesting thing about this was
that you had not to
DU
> Subject: C fprintf() format code for 32-bit float?
>
> Apologies for the basic question. About everything I know about floating
> point could be engraved on the back of a postage stamp.
>
> For C fprintf() and friends, how do I specify the formatting of a 32-bit
> floating poi
: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: C fprintf() format code for 32-bit float?
It’s a silly question, but why are you using single precession floating point.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send emai
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Charles Mills
Sent: Monday, March 13, 2017 6:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: C fprintf() format code for 32-bit float?
OK. I just coded a static_cast on @Gil's suggestion. Should not hurt anything;
actually makes the c
rley, Peter x23353
> Sent: Monday, March 13, 2017 4:32 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: C fprintf() format code for 32-bit float?
>
> I believe that formatting types e/E, f/F and g/G will all handle float,
> double and long double without casts.
>
>
eter x23353
Sent: Monday, March 13, 2017 4:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: C fprintf() format code for 32-bit float?
I believe that formatting types e/E, f/F and g/G will all handle float, double
and long double without casts.
Example CELEBF30 available in the Runtime Library Refe
scussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Monday, March 13, 2017 4:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: C fprintf() format code for 32-bit float?
On Mon, 13 Mar 2017 15:53:20 -0700, Charles Mills wrote:
>Apologies for the basic question. A
specifiers with no cast.
HTH
Peter
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Monday, March 13, 2017 7:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: C fprintf() format code for 32-bit float?
On Mon, 13 Mar 2017
On Mon, 13 Mar 2017 15:53:20 -0700, Charles Mills wrote:
>Apologies for the basic question. About everything I know about floating
>point could be engraved on the back of a postage stamp.
>
>For C fprintf() and friends, how do I specify the formatting of a 32-bit
>floating point
Apologies for the basic question. About everything I know about floating
point could be engraved on the back of a postage stamp.
For C fprintf() and friends, how do I specify the formatting of a 32-bit
floating point number (C type "float" as opposed to "double))? e, f or g
wit
32 matches
Mail list logo
