From: Paul Eggert <eggert@cs.ucla.edu>
To: Po Lu <luangruo@yahoo.com>
Cc: Spencer Baugh <sbaugh@janestreet.com>, 63556@debbugs.gnu.org
Subject: bug#63556: 29.0.90; Use of _Generic breaks Emacs build on GCC <4.9
Date: Thu, 18 May 2023 20:05:59 -0700 [thread overview]
Message-ID: <800a427a-514f-8ef5-326d-6abc06fb036a@cs.ucla.edu> (raw)
In-Reply-To: <87mt21408l.fsf@yahoo.com>
On 5/18/23 17:46, Po Lu wrote:
> How does intprops.h work on such systems?
It relies on _Generic. (Those systems use neither GCC nor Clang.)
> OK, but that's the second use of `long long' in src/ outside of
> NT-specific files. I can't help but be a little skittish.
Fair enough, although I see more than just one other use: EMACS_INT
(32-bit platforms configured --with-wide-int), color_distance,
time_from_jiffies (in Linux), system_process_attributes (in Linux).
Currently there's a 'verify (PTRDIFF_MAX <= ULLONG_MAX);' protecting the
use of elogb in lisp.h. Would it help to add a 'verify (max
(-MOST_NEGATIVE_FIXNUM, MOST_POSITIVE_FIXNUM) <= ULLONG_MAX);' to
protect its use in floatfns.c?
next prev parent reply other threads:[~2023-05-19 3:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 17:38 bug#63556: 29.0.90; Use of _Generic breaks Emacs build on GCC <4.9 Spencer Baugh
2023-05-17 17:45 ` Eli Zaretskii
2023-05-17 17:57 ` Paul Eggert
2023-05-18 11:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-18 11:42 ` Eli Zaretskii
2023-05-18 13:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-18 14:12 ` Eli Zaretskii
2023-05-18 14:40 ` Paul Eggert
2023-05-19 0:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-19 3:05 ` Paul Eggert [this message]
2023-05-19 3:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-18 20:32 ` Paul Eggert
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=800a427a-514f-8ef5-326d-6abc06fb036a@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=63556@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=sbaugh@janestreet.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).