[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Lisp_Marker size on 32bit systems
From: |
Stefan Monnier |
Subject: |
Re: Lisp_Marker size on 32bit systems |
Date: |
Thu, 06 Sep 2018 08:17:40 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
>> used to be 24 (bytes) when we used Lisp_Misc, but it is now 32
>> (bytes) instead!
> I'll take a look at it.
Thanks. AFAICT the only solution is to use the GCALIGNED_UNION trick in
each and every "real Lisp_Object struct" rather than once and forall in
vectorlike_header.
Maybe we should use a LISP_STRUCT macro like
#define LISP_STRUCT(name, fields) \
struct name { union { struct { fields } s; GCALIGNED_UNION; } u; }
> I was hoping those 8 bytes wouldn't make enough
> difference to worry about, but evidently not....
It's really the 4 extra padding bytes incurred by all vectorlikes that
annoy me. The resulting extra 8 bytes in markers is just a symptom ;-)
Stefan
- Lisp_Marker size on 32bit systems, Stefan Monnier, 2018/09/05
- Re: Lisp_Marker size on 32bit systems, Paul Eggert, 2018/09/06
- Re: Lisp_Marker size on 32bit systems,
Stefan Monnier <=
- Re: Lisp_Marker size on 32bit systems, Paul Eggert, 2018/09/07
- Re: Lisp_Marker size on 32bit systems, Eli Zaretskii, 2018/09/07
- Re: Lisp_Marker size on 32bit systems, Paul Eggert, 2018/09/07
- GDB and compiler-operations (was: Lisp_Marker size on 32bit systems), Stefan Monnier, 2018/09/07
- Re: GDB and compiler-operations (was: Lisp_Marker size on 32bit systems), Eli Zaretskii, 2018/09/07
- Re: GDB and compiler-operations, Andreas Schwab, 2018/09/07
- Re: GDB and compiler-operations (was: Lisp_Marker size on 32bit systems), Paul Eggert, 2018/09/07
- Re: GDB and compiler-operations, Stefan Monnier, 2018/09/07
- Re: GDB and compiler-operations, Eli Zaretskii, 2018/09/07
- Re: GDB and compiler-operations, Paul Eggert, 2018/09/07