BITSIZE of "SET OF SomeEnumeration" has been made flexible? (C backend, ARM64_DARWIN)
dragisha opened this issue · 2 comments
dragisha commented
Using ARM64_DARWIN with C backend and hit into a situation where BITSIZE(INTEGER) # BITSIZE(SET OF {A, B, C}).
I was using a lot of LOOPHOLE for interfacing libevent library with my Modula-3 code and it worked and works quite well with earlier (GCC backend) cm3 compilers on several platforms.
Is there a way to set old behavior with some switch to the current compiler?
RodneyBates commented
Sorry, I changed small sets to occupy the smallest of 8, 16, 32, or 64 that
will hold the value, because I have some very small sets that occur as fields
of objects with very high instance counts and didn't want so much space taken up
I'll look at making this optional.
…On 1/15/23 17:10, Dragiša Durić wrote:
Using ARM64_DARWIN with C backend and hit into a situation where BITSIZE(INTEGER) # BITSIZE(SET OF {A, B, C}).
I was using a lot of LOOPHOLE for interfacing libevent library with my Modula-3 code and it worked and works quite well with earlier (GCC backend) cm3 compilers on several platforms.
Is there a way to set old behavior with some switch to the current compiler?
—
Reply to this email directly, view it on GitHub <#1141>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSVZNAMHQNMY3ZF7DYWUYDWSR7X7ANCNFSM6AAAAAAT4D4ZNA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
dragisha commented
Please do not spend your time on this. I will create alternative for myself :).
Just push forward. Big thanks to you and other guys for keeping cm3 alive!
… On 16. 1. 2023., at 00:34, Rodney M. Bates ***@***.***> wrote:
Sorry, I changed small sets to occupy the smallest of 8, 16, 32, or 64 that
will hold the value, because I have some very small sets that occur as fields
of objects with very high instance counts and didn't want so much space taken up
I'll look at making this optional.
On 1/15/23 17:10, Dragiša Durić wrote:
>
> Using ARM64_DARWIN with C backend and hit into a situation where BITSIZE(INTEGER) # BITSIZE(SET OF {A, B, C}).
>
> I was using a lot of LOOPHOLE for interfacing libevent library with my Modula-3 code and it worked and works quite well with earlier (GCC backend) cm3 compilers on several platforms.
>
> Is there a way to set old behavior with some switch to the current compiler?
>
> —
> Reply to this email directly, view it on GitHub <#1141>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSVZNAMHQNMY3ZF7DYWUYDWSR7X7ANCNFSM6AAAAAAT4D4ZNA>.
> You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#1141 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5ZBWDV5CROP6DJG4W4FBDWSSCPRANCNFSM6AAAAAAT4D4ZNA>.
You are receiving this because you authored the thread.