[M3devel] More testing needed for m3back, was: RE: m3back/longint/atomics

[Coleburn, Randy]

I can certainly run some tests on Windows.

I don't have any code that uses longint, so either someone needs to identify which existing programs I can build and run to do the tests, OR I suppose I can write something if you can give me an idea of how extensive the tests you want.

I've been trying to keep my system updated to the latest sources on the main trunk, but I've been swamped lately and I'm afraid I'm a few weeks stale right now.  I'll remedy that shortly.

Regards,
Randy

________________________________
From: Olaf Wagner [wagner at elegosoft.com]
Sent: Thursday, February 18, 2010 6:57 AM
To: Jay K
Cc: m3devel
Subject: [M3devel] More testing needed for m3back, was: RE: m3back/longint/atomics

If I understand Jay correctly, it wouldn't be too difficult to bring
the m3ack LONGINT changes for Windows into the release branch, but
more testing would be needed.

Randy, you're the only one I remember offhand who actively uses M3
on Windows except for Jay. Could you have a closer look at it?
(Changes are only on the trunk right now.)

Or is anybody else here lurking and eager to do some Windows-based tests?

If nobody volunteers, I'm afraid we will have to release without 64bit
LONGINT on Windows.

Olaf

Quoting Jay K <jay.krell at cornell.edu>:

> NT386/longint changes are almost entirely in the m3back package.
>
> There is also some small easy stuff in
> m3-libs/m3core/src/Csupport/common/hand.c.
>
> It'd be really great if anyone could test any of this and if
> anyone could review the diff between release and head.
>
> Not just me.
>
> The changes for longint are quite large, even if local.
>
> I can port them, in the case of m3back, just copy, and make sure
> the atomics stuff doesn't cause problems (it should be unused).
>
> There is also a small change in m3front so that longint can be initialized.
> That affects all platforms.
>
> And a small change in m3cc/parse.c for div/mod of longint on non-NT386.
> I have to test mod yet but my fix probably helps it.
>
> It'd be really great if anyone could do anything with this stuff.
> ie. for now in head, then could easily port to release.
>
> We can of course release either way, depending on how satisfied people
> are with 32bit longint on NT386. i.e. longint isn't useful portably, but it
> is useful on non-NT386 platforms.
>
>  - Jay
>
>> Date: Tue, 16 Feb 2010 16:12:52 +0100
>> From: wagner at elegosoft.com
>> To: m3devel at elegosoft.com
>> Subject: Re: [M3devel] m3back/longint/atomics
>>
>> Quoting Jay K <jay.krell at cornell.edu>:
>>
>> >
>> > As far as I know/can remember, longint and atomics should all work
>> > now on NT386.
>> >
>> > Atomics only currently for 32bit types.
>> > There are still a few small inefficiencies to maybe deal with.
>> > I'll add 64bit shortly and maybe 8 and 16.
>> >
>> >
>> > We should probably add *a lot* more test coverage in p226 and p227.
>> >
>> > e.g. longint multiply/add/sub/divide, not just insert/extract like I
>> > did a bunch of.
>>
>> Any volunteers to increase the test coverage?
>>
>> > Still to fix the Win32 m3core/libm3 to not always truncate file sizes.
>> >
>> > Still maybe to do something about rd/wr...?
>> >
>> > Still to wonder about NT386/longint support in the release branch?
>>
>> Should we / will you merge this stuff to the release branch?
>> Or should we release without it? How local are the changes?
>>
>> Olaf
--
Olaf Wagner -- elego Software Solutions GmbH
                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
    http://www.elegosoft.com<http://www.elegosoft.com/> | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100218/da32f98d/attachment-0002.html>