From: Po Lu <luangruo@yahoo.com>
To: Gregory Heytings <gregory@heytings.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: master 37889523278: Add new `swap` macro and use it
Date: Tue, 30 Jan 2024 10:41:47 +0800 [thread overview]
Message-ID: <87wmrrfspg.fsf@yahoo.com> (raw)
In-Reply-To: <148534ba184067c6fc39@heytings.org> (Gregory Heytings's message of "Tue, 30 Jan 2024 02:00:43 +0000")
Gregory Heytings <gregory@heytings.org> writes:
> You did not, otherwise you would not have explained the build failure
> with something that had no relationship whatsoever with it.
Your build failure is one which we have _fixed_, and holds absolutely no
bearing on our expectations of C compilers.
> All that is irrelevant in the matter at hand.
You don't decide what is relevant or irrelevant.
> That's wrong. Again you are just ignoring the information I gave
> you. So I'll say it again: alignas, a C11 feature, was introduced
> unconditionally in Emacs by e32a579975 in July 2012, and it was made
> conditional only ten years later, by 1e2bc1bbf4 in December 2021 (to
> support builds with older version of TCC). Without the "# define
> alignas(a)" line in lisp.h, which was added by 1e2bc1bbf4 and was
> therefore not present in Emacs 25-28, Sun C 5.8 fails to compile Emacs
> 29 in the same way it fails to compile Emacs 25-28.
In e32a579975's lisp.h:
#ifndef alignas
# define alignas(alignment) /* empty */
# if USE_LSB_TAG
This definition was lost unintentionally to a succession of changes, and
promptly restored when its absence was brought to our attention.
I'm sorry to be blunt, but if in decision-making you consider and cite
only historical factors to your liking, or in argument you cannot make
the distinction between errors arising from some fundamental limitation
of a compiler and those caused by operator error, to wit, the failure to
provide several required compiler flags and install patches firmly
recommended by the supplier, whether a compiler can and should compile
Emacs is not for you to decide. So believe what you want--you don't use
Solaris, or TCC, so the subject of your assertions cannot affect you to
any extent.
next prev parent reply other threads:[~2024-01-30 2:41 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170452579053.27998.16123231327386305897@vcs2.savannah.gnu.org>
[not found] ` <20240106072311.28B8FC0034E@vcs2.savannah.gnu.org>
2024-01-06 7:39 ` master 37889523278: Add new `swap` macro and use it Po Lu
2024-01-06 8:44 ` Eli Zaretskii
2024-01-06 8:45 ` Po Lu
2024-01-06 9:18 ` Stefan Kangas
2024-01-06 10:33 ` Po Lu
2024-01-06 11:30 ` Stefan Kangas
2024-01-06 13:13 ` Po Lu
2024-01-06 13:59 ` Eli Zaretskii
2024-01-06 14:41 ` Po Lu
2024-01-06 15:34 ` Eli Zaretskii
2024-01-07 1:39 ` Po Lu
2024-01-07 6:34 ` Stefan Kangas
2024-01-07 7:50 ` Po Lu
2024-01-07 8:33 ` Eli Zaretskii
2024-01-07 9:45 ` Stefan Kangas
2024-01-07 10:36 ` Po Lu
2024-01-07 11:34 ` Eli Zaretskii
2024-01-07 11:53 ` Po Lu
2024-01-07 14:37 ` Eli Zaretskii
2024-01-07 17:32 ` Stefan Kangas
2024-01-08 2:15 ` Po Lu
2024-01-07 7:09 ` Eli Zaretskii
2024-01-12 0:50 ` Gregory Heytings
2024-01-13 10:16 ` Stefan Kangas
2024-01-14 3:03 ` Richard Stallman
2024-01-14 5:14 ` Po Lu
2024-01-14 7:07 ` Eli Zaretskii
2024-01-14 8:05 ` Po Lu
2024-01-14 9:31 ` Eli Zaretskii
2024-01-15 1:32 ` Gregory Heytings
2024-01-15 12:41 ` Eli Zaretskii
2024-01-15 13:56 ` Po Lu
2024-01-15 14:13 ` Eli Zaretskii
2024-01-18 1:01 ` Gregory Heytings
2024-01-18 2:11 ` Po Lu
2024-01-27 1:26 ` Gregory Heytings
2024-01-27 2:58 ` Po Lu
2024-01-27 23:44 ` Stefan Kangas
2024-01-28 1:51 ` Po Lu
2024-01-28 2:35 ` Stefan Kangas
2024-01-28 4:17 ` Po Lu
2024-01-28 6:28 ` Eli Zaretskii
2024-01-28 2:22 ` Gregory Heytings
2024-01-28 4:03 ` Po Lu
2024-01-30 2:00 ` Gregory Heytings
2024-01-30 2:41 ` Po Lu [this message]
2024-01-28 6:40 ` Eli Zaretskii
2024-01-30 1:59 ` Gregory Heytings
2024-01-30 12:41 ` Eli Zaretskii
2024-01-18 6:22 ` Eli Zaretskii
2024-01-27 1:25 ` Gregory Heytings
2024-01-27 3:08 ` Po Lu
2024-01-27 7:19 ` Eli Zaretskii
2024-01-17 3:29 ` Richard Stallman
2024-01-17 10:16 ` Stefan Kangas
2024-01-17 11:15 ` Po Lu
2024-01-17 21:15 ` Stefan Kangas
2024-01-18 0:39 ` Po Lu
2024-01-18 19:17 ` Stefan Kangas
2024-01-19 1:10 ` Po Lu
2024-01-20 20:31 ` Stefan Kangas
2024-01-22 3:35 ` Richard Stallman
2024-01-22 4:48 ` Po Lu
2024-01-22 18:21 ` Dmitry Gutov
2024-01-23 0:50 ` Po Lu
2024-01-25 23:38 ` Stefan Kangas
2024-01-26 2:02 ` Po Lu
2024-01-26 7:53 ` Eli Zaretskii
2024-01-26 7:38 ` Eli Zaretskii
2024-01-19 3:32 ` Richard Stallman
2024-01-19 4:12 ` Po Lu
2024-01-27 1:27 ` Gregory Heytings
2024-01-27 23:56 ` Stefan Kangas
2024-01-28 2:23 ` Gregory Heytings
2024-01-13 8:02 ` Stefan Kangas
2024-01-13 9:14 ` Eli Zaretskii
2024-01-13 9:50 ` Mattias Engdegård
2024-01-06 8:50 ` Stefan Kangas
2024-01-06 9:09 ` Po Lu
2024-01-06 9:52 ` Andreas Schwab
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmrrfspg.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=stefankangas@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.