From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Arsen Arsenović" <arsen@aarsen.me>,
mattias.engdegard@gmail.com, vibhavp@gmail.com, rpluim@gmail.com,
emacs-devel@gnu.org
Subject: Re: HAVE_FAST_UNALIGNED_ACCESS
Date: Sun, 02 Apr 2023 08:50:22 +0800 [thread overview]
Message-ID: <87edp3rttd.fsf@yahoo.com> (raw)
In-Reply-To: <83jzyvy3l3.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Apr 2023 19:22:48 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
-fsanitize=undefined is intended to detect these ``real-life cases''
before they occur.
We are talking about code that is less than three years old, in the
context of a procedure that has not been changed much since the days of
the Unicode branch! How can you be so certain of its safety?
next prev parent reply other threads:[~2023-04-02 0:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 9:34 HAVE_FAST_UNALIGNED_ACCESS Robert Pluim
2023-03-30 10:26 ` HAVE_FAST_UNALIGNED_ACCESS Eli Zaretskii
2023-03-30 11:09 ` HAVE_FAST_UNALIGNED_ACCESS Sam James
2023-03-30 12:18 ` HAVE_FAST_UNALIGNED_ACCESS Arsen Arsenović
[not found] ` <87v8ihu3t8.fsf@yahoo.com>
2023-03-31 7:15 ` HAVE_FAST_UNALIGNED_ACCESS Robert Pluim
2023-03-31 7:45 ` HAVE_FAST_UNALIGNED_ACCESS Arsen Arsenović
2023-03-31 17:29 ` HAVE_FAST_UNALIGNED_ACCESS Mattias Engdegård
2023-03-31 20:13 ` HAVE_FAST_UNALIGNED_ACCESS Arsen Arsenović
2023-03-30 10:28 ` HAVE_FAST_UNALIGNED_ACCESS Mattias Engdegård
2023-03-30 11:38 ` HAVE_FAST_UNALIGNED_ACCESS Vibhav Pant
2023-03-31 16:57 ` HAVE_FAST_UNALIGNED_ACCESS Mattias Engdegård
2023-03-31 17:59 ` HAVE_FAST_UNALIGNED_ACCESS Eli Zaretskii
2023-03-31 18:03 ` HAVE_FAST_UNALIGNED_ACCESS Mattias Engdegård
2023-03-31 18:12 ` HAVE_FAST_UNALIGNED_ACCESS Eli Zaretskii
2023-04-01 0:45 ` HAVE_FAST_UNALIGNED_ACCESS Po Lu
2023-04-01 5:43 ` HAVE_FAST_UNALIGNED_ACCESS Eli Zaretskii
2023-04-01 6:31 ` HAVE_FAST_UNALIGNED_ACCESS Po Lu
2023-04-01 6:39 ` HAVE_FAST_UNALIGNED_ACCESS Eli Zaretskii
2023-04-01 7:42 ` HAVE_FAST_UNALIGNED_ACCESS Mattias Engdegård
2023-04-01 8:19 ` HAVE_FAST_UNALIGNED_ACCESS Eli Zaretskii
2023-04-01 9:17 ` HAVE_FAST_UNALIGNED_ACCESS Po Lu
2023-04-01 11:25 ` HAVE_FAST_UNALIGNED_ACCESS Eli Zaretskii
2023-04-01 12:59 ` HAVE_FAST_UNALIGNED_ACCESS Arsen Arsenović
2023-04-01 13:33 ` HAVE_FAST_UNALIGNED_ACCESS Eli Zaretskii
2023-04-01 15:22 ` HAVE_FAST_UNALIGNED_ACCESS Arsen Arsenović
2023-04-01 16:22 ` HAVE_FAST_UNALIGNED_ACCESS Eli Zaretskii
2023-04-02 0:50 ` Po Lu [this message]
2023-04-02 0:48 ` HAVE_FAST_UNALIGNED_ACCESS Po Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edp3rttd.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=arsen@aarsen.me \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=rpluim@gmail.com \
--cc=vibhavp@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).