Date: Fri, 6 May 2022 14:38:38 +0100
Sorry Aaron
I have a conflict today, so won't be able to join
Clive
On Mon, Apr 25, 2022 at 6:56 PM Aaron Ballman via Liaison <
liaison_at_[hidden]> wrote:
> Our next meeting will be on Fri May 6, 2022 at 15:00 UTC
> (
> https://www.timeanddate.com/worldclock/converter.html?iso=20220506T150000&p1=tz_pt&p2=tz_mt&p3=tz_ct&p4=tz_et&p5=1440
> ).
>
> You can join the meeting at https://iso.zoom.us/j/5513145100
>
> We will be discussing the following papers:
>
> WG14 N2888 (http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2888.htm)
> Require exact-width integer type interfaces
> Proposes changes to the definition of the intmax_t and uintmax_t
> typedefs so that extended exact-width integer types do not factor into
> the definition. Thus, these types are required to be large enough to
> represent a `long long` type, but do not have to be widened for an
> implementation to support e.g., __int128 as an extended integer type.
> The author is looking for feedback on whether this approach will be a
> palatable way forward given the ABI concerns around changing the size
> or alignment of these types.
>
> WG14 N2889 (http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2889.htm)
> Pointers and integer types
> Proposes making intptr_t and uinptr_t mandatory types instead of
> optional. The author is looking for feedback on whether there will be
> any difficulties with this change.
>
> Thanks!
>
> ~Aaron
> _______________________________________________
> Liaison mailing list
> Liaison_at_[hidden]
> Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/liaison
> Link to this post: http://lists.isocpp.org/liaison/2022/04/1058.php
>
I have a conflict today, so won't be able to join
Clive
On Mon, Apr 25, 2022 at 6:56 PM Aaron Ballman via Liaison <
liaison_at_[hidden]> wrote:
> Our next meeting will be on Fri May 6, 2022 at 15:00 UTC
> (
> https://www.timeanddate.com/worldclock/converter.html?iso=20220506T150000&p1=tz_pt&p2=tz_mt&p3=tz_ct&p4=tz_et&p5=1440
> ).
>
> You can join the meeting at https://iso.zoom.us/j/5513145100
>
> We will be discussing the following papers:
>
> WG14 N2888 (http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2888.htm)
> Require exact-width integer type interfaces
> Proposes changes to the definition of the intmax_t and uintmax_t
> typedefs so that extended exact-width integer types do not factor into
> the definition. Thus, these types are required to be large enough to
> represent a `long long` type, but do not have to be widened for an
> implementation to support e.g., __int128 as an extended integer type.
> The author is looking for feedback on whether this approach will be a
> palatable way forward given the ABI concerns around changing the size
> or alignment of these types.
>
> WG14 N2889 (http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2889.htm)
> Pointers and integer types
> Proposes making intptr_t and uinptr_t mandatory types instead of
> optional. The author is looking for feedback on whether there will be
> any difficulties with this change.
>
> Thanks!
>
> ~Aaron
> _______________________________________________
> Liaison mailing list
> Liaison_at_[hidden]
> Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/liaison
> Link to this post: http://lists.isocpp.org/liaison/2022/04/1058.php
>
Received on 2022-05-06 13:38:49