From: "Basil L. Contovounesios" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 58254@debbugs.gnu.org
Subject: bug#58254: 29.0.50; Untracked lib/assert.h with Clang 14
Date: Mon, 03 Oct 2022 16:00:51 +0300 [thread overview]
Message-ID: <87lepxrri4.fsf@tcd.ie> (raw)
In-Reply-To: <c59296e2-9715-5789-8c11-a76c9b5d0507@cs.ucla.edu> (Paul Eggert's message of "Sun, 2 Oct 2022 13:20:48 -0700")
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
Paul Eggert [2022-10-02 13:20 -0700] wrote:
> On 10/2/22 09:10, Basil L. Contovounesios wrote:
>> This file is not generated with the default CC=gcc; there is only a
>> lib/assert.in.h present.
>
> That's odd. As far as I can see, lib/assert.h is needed only if you need to
> compile lib/filevercmp.c, lib/nanosleep.c, lib/pipe2.c, lib/rawmemchr.c, or
> lib/strtoimax.c, and I don't see why choosing clang over gcc would affect
> whether these files need to be compiled.
Out of these, only rawmemchr.c and strtoimax.c are not compiled.
The rest are compiled with both Clang and GCC.
I suspect there's a different culprit: skimming through the attached
build output and config.log files, one set with Clang and the other with
GCC, I see that, in the GCC case, static_assert is determined to be an
<assert.h> macro, whereas in the Clang case the static_assert test
fails. As a result, gl_ASSERT_H sets GL_GENERATE_ASSERT_H=true.
Is that correct?
Thanks,
--
Basil
[-- Attachment #2: emacs-bug58254.tar.gz --]
[-- Type: application/gzip, Size: 159138 bytes --]
next prev parent reply other threads:[~2022-10-03 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 16:10 bug#58254: 29.0.50; Untracked lib/assert.h with Clang 14 Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-02 20:20 ` Paul Eggert
2022-10-03 13:00 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-11-03 2:53 ` 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=87lepxrri4.fsf@tcd.ie \
--to=bug-gnu-emacs@gnu.org \
--cc=58254@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=eggert@cs.ucla.edu \
/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).