unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-28 9c222b9: Port to C compilers that lack size-0 arrays
Date: Fri, 3 Dec 2021 11:42:08 -0800	[thread overview]
Message-ID: <18c9aeb7-3b9e-3e94-a24b-b52ea10ce75d@cs.ucla.edu> (raw)
In-Reply-To: <83tufp7dae.fsf@gnu.org>

On 12/3/21 10:29, Eli Zaretskii wrote:
>> What I experienced was a ton of diagnostics with both the Oracle Solaris
>> and the IBM AIX C compilers, which made it difficult for me to see the
>> real problems on those platforms (of which there were some).
> Any reason why we should be concerned about these two platforms?

Emacs has run on Solaris and AIX for decades, these platforms are stable 
and are supported by Oracle and IBM respectively, and there's very 
little trouble keeping Emacs working on these platforms.

And it's not just these two platforms. My bigger motivation for this 
particular change was that the old code violates a constraint specified 
by the C standard. Even though the old code works on GCC, Clang and 
MSVC, there's a reasonable chance it won't work on less-commonly-used 
compilers and there's little point to taking that risk when the fix is 
so simple.




  reply	other threads:[~2021-12-03 19:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03  8:16 emacs-28 9c222b9: Port to C compilers that lack size-0 arrays Eli Zaretskii
2021-12-03 16:46 ` Paul Eggert
2021-12-03 18:29   ` Eli Zaretskii
2021-12-03 19:42     ` Paul Eggert [this message]
2021-12-03 20:01       ` Eli Zaretskii
2021-12-03 23:32         ` Paul Eggert
2021-12-04  7:35           ` Eli Zaretskii
2021-12-04 10:47             ` Stefan Kangas
2021-12-04 11:24               ` Po Lu
2021-12-04  0:37         ` 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=18c9aeb7-3b9e-3e94-a24b-b52ea10ce75d@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).