[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: HAVE_FAST_UNALIGNED_ACCESS
From: |
Eli Zaretskii |
Subject: |
Re: HAVE_FAST_UNALIGNED_ACCESS |
Date: |
Sat, 01 Apr 2023 19:22:48 +0300 |
> From: Arsen Arsenović <arsen@aarsen.me>
> Cc: luangruo@yahoo.com, mattias.engdegard@gmail.com, vibhavp@gmail.com,
> rpluim@gmail.com, emacs-devel@gnu.org
> Date: Sat, 01 Apr 2023 17:22:48 +0200
>
> I understand why you're arguing this, and I have to thank you for it -
> such efforts keep Emacs as stable as it is - but this feels like an
> example that is too trivial to apply such judgment to, hence my
> position. I am certain that you have an understanding of the issue at
> hand, I'm only trying to provide a solution that's safe enough for 29.
Among other reasons, we'd need a real-life case where this code fails
to test any solutions.
- Re: HAVE_FAST_UNALIGNED_ACCESS, Eli Zaretskii, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS, Po Lu, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS, Eli Zaretskii, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS, Mattias Engdegård, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS, Eli Zaretskii, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS, Po Lu, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS, Eli Zaretskii, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS, Arsen Arsenović, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS, Eli Zaretskii, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS, Arsen Arsenović, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS,
Eli Zaretskii <=
- Re: HAVE_FAST_UNALIGNED_ACCESS, Po Lu, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS, Po Lu, 2023/04/01