gm2
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Partial success building the trunk on MSYS2/Windows platform


From: Fischlin Andreas
Subject: Re: Partial success building the trunk on MSYS2/Windows platform
Date: Mon, 7 Nov 2022 16:15:57 +0000

Dear Gaius,

Follow up: For our portable floating point arithmetic module FloatPortab (Dialogue Machine) we have also implemented checks in terms of type lengths that may succeed or not across hard- and software (compilers) by running a little overhead checking code during module initialisation. This needs only to be done once and then you can rely on correct interpretation and any numerical use of routines from that module have to pay no performance penalty at all.

Andreas


ETH Zurich
Prof. em. Dr. Andreas Fischlin
IPCC Vice-Chair WGII
Systems Ecology - Institute of Biogeochemistry and Pollutant Dynamics
CHN E 24
Universitaetstrasse 16
8092 Zurich
SWITZERLAND


+41 44 633-6090 phone
+41 44 633-1136 fax
+41 79 595-4050 mobile

             Make it as simple as possible, but distrust it!
________________________________________________________________________









On 07/11/2022, at 16:04, Gaius Mulley <gaiusmod2@gmail.com> wrote:

"Fischlin  Andreas" <andreas.fischlin@env.ethz.ch> writes:

I fully concur with Benjamin’s arguments. gm2 developers please listen. ;-) Thanks.

Andreas

Hi Andreas,

yes indeed - thanks for the prod - I've been contemplating these ideas.

It does make sense to move the sized types (CARDINAL8 et al) out of
SYSTEM and place them to their own definition module, say gcc_CARDINAL8.
The gcc_CARDINAL8 implementation module could implement the range
checking found in gcc/m2/m2expr.cc and also draw upon the gcc internal
datatypes (and ranger functions) if they are supported and if not then
execute modula-2.  Furthermore there shouldn't be a performance penalty
(if the hardware supports the datatypes) as the procedure functions
could be inlined.

I've wanted to simplifiy m2expr.cc and also re-implement large sets -
and the above approach - would achieve both changes,

regards,
Gaius

Attachment: smime.p7s
Description: S/MIME cryptographic signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]