[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 09:39:21 +0300 |
> From: Po Lu <luangruo@yahoo.com>
> Cc: mattias.engdegard@gmail.com, vibhavp@gmail.com, rpluim@gmail.com,
> emacs-devel@gnu.org
> Date: Sat, 01 Apr 2023 14:31:06 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I've read your request, and decided not to apply this to the release
> > branch.
>
> Even if GCC 13 (or GCC 14) generates incorrect code for the function?
I don't want to make changes on the release branch without a positive
evidence that the existing code causes verifiable problems. And even
then I prefer to make changes only for platforms where those problems
happen.
- 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 <=
- 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, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS, Po Lu, 2023/04/01
- Re: HAVE_FAST_UNALIGNED_ACCESS, Po Lu, 2023/04/01