Re: [PATCH v4] Add support for creating new types from the Python API

[Eli Zaretskii <eliz@gnu.org>]

> From: Matheus Branco Borella <dark.ryu.550@gmail.com>
> Cc: eli@gnu.org
> Date: Tue, 16 Jan 2024 15:20:24 -0300
> X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00, DKIM_SIGNED,
>  DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT,
>  FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP,
>  T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
> 
> Apologies for my previous empty response, my email client got a little
> trigger-happy (And I'm still getting the hang of it).
> 
> On Jan 16, 2024, at 9:45=E2=80=AFAM, Eli Zaretskii <eliz@gnu.org> wrote:
> > I asked previously what does BIT_SIZE mean for pointer types.  Is it
> > the size of the pointer or of the data type to which the pointer
> > points?  If it's the size of the pointer, then does it mean this
> > function can create pointers of arbitrary sizes regardless of the
> > sizes of pointers that are supported by the target?
> 
> It's the size of the pointer itself.

How can that work?  AFAIU, most architectures only allow pointers of
certain sizes, some allow pointers of just one size.  E.g., what
happens if I create a 16-bit pointer on a 64-bit target?