Re: is Vax addressing sane today

On Sun, 29 Sep 2024 09:39:27 -0700
Tim Rentsch <tr.17687@z991.linuxsc.com> wrote:
>

Michael S <already5chosen@yahoo.com> writes:
>

On Sat, 28 Sep 2024 23:59:23 -0700
Tim Rentsch <tr.17687@z991.linuxsc.com> wrote:

>
[...]
>

I am currently in the position of needing to take some code
written for Linux/Unix and get it running in MS Windows.
>
My attempts to use MSVC have been frustrating, because of some
limitations of that environment.  The two most prominent are
these:  long double is only 64 bits, and there are no integer
types of 128 bits that I could find.
>
Are there any MSVC folks here who can help with these problems?
I am not an MSVC expert by any means and easily could have missed
something.
>
I should mention that the code is written in C, not C++, and that
is not something I am at liberty to change.

>
Both of your problems have no [MSVC] solution right now.
>
In case of 128-bit integer, there is a chance that MSVC will support
it in the future.
>
In case of 80-bit long double, there is no chance.  If MSVC ever
supports binary floating point wider than 64-bit on x86-64 platform
then it would be IEEE binary128 implemented in software.  But even
then they would not use name 'long double' for a new type, because
it would break existing programs.

>
Thank you, this is helpful.
>

But if all you want is the program running on Windows, then the
solution is easy - use different compiler.
MSYS2 is just couple of clicks (and ~0.8 GB :( ) away.
After you have msys2 installed do
pacman -Sy
pacman mingw-w64-ucrt-x86_64-gcc
>
Several hundreds of MB more and you have gcc14
Possible, I'd have to install make separately, i.e.
pacman make.

>
Do I understand this right, that msys2 is to be installed
on Windows?  And that the pacman commands are to be run
within msys2 on the MS Windows system?

>
Yes and yes.
pacman has to be run from msys2 terminal window (bash).