From: Lars Ingebrigtsen <larsi@gnus.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Angelo Graziosi <angelo.g0@libero.it>,
Philippe Spiesser <ann.onymous@orange.fr>,
Stefan Kangas <stefankangas@gmail.com>,
43152@debbugs.gnu.org
Subject: bug#43152: 28.0.50; when building emacs 28.0.50 ./temacs is stopped with core
Date: Sat, 05 Sep 2020 23:36:05 +0200 [thread overview]
Message-ID: <87pn6z29fe.fsf@gnus.org> (raw)
In-Reply-To: <c2a929a0-29c2-6b3c-4ef8-fd12a755ac8f@cs.ucla.edu> (Paul Eggert's message of "Sat, 5 Sep 2020 12:27:42 -0700")
Poking about a bit with that checkout, I find that if I do:
diff --git a/lib/verify.h b/lib/verify.h
index 6d7b961db7..e2f0cacd03 100644
--- a/lib/verify.h
+++ b/lib/verify.h
@@ -246,13 +246,6 @@ #define _GL_VERIFY_TRUE(R, DIAGNOSTIC) \
/* @assert.h omit start@ */
-#if defined __has_builtin
-/* <https://clang.llvm.org/docs/LanguageExtensions.html#builtin-functions> */
-# define _GL_HAS_BUILTIN_ASSUME __has_builtin (__builtin_assume)
-#else
-# define _GL_HAS_BUILTIN_ASSUME 0
-#endif
-
#if 3 < __GNUC__ + (3 < __GNUC_MINOR__ + (4 <= __GNUC_PATCHLEVEL__))
# define _GL_HAS_BUILTIN_TRAP 1
#elif defined __has_builtin
... then there's no segmentation fault any more.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-05 21:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1457551226.863660.1599040446670@mail1.libero.it>
[not found] ` <CADwFkmnymz3jBD41GjfONHAreqQgYDN2-5+sPfzEg5V0Yh=M=w@mail.gmail.com>
2020-09-02 20:09 ` bug#43152: 28.0.50; when building emacs 28.0.50 ./temacs is stopped with core Paul Eggert
2020-09-03 12:30 ` Anonymous
2020-09-03 15:35 ` Angelo Graziosi
2020-09-03 19:17 ` Paul Eggert
2020-09-03 23:17 ` Angelo Graziosi
2020-09-03 23:53 ` Angelo Graziosi
2020-09-04 20:32 ` Paul Eggert
2020-09-04 21:24 ` Angelo Graziosi
2020-09-04 21:34 ` Angelo Graziosi
2020-09-04 21:56 ` Paul Eggert
2020-09-05 6:30 ` Angelo Graziosi
2020-09-05 12:05 ` Lars Ingebrigtsen
2020-09-05 19:27 ` Paul Eggert
2020-09-05 21:30 ` Lars Ingebrigtsen
2020-09-06 0:58 ` Paul Eggert
2020-09-06 11:50 ` Lars Ingebrigtsen
2020-09-05 21:36 ` Lars Ingebrigtsen [this message]
2020-09-05 21:41 ` Lars Ingebrigtsen
2020-09-01 9:37 Philippe Spiesser
2020-09-01 11:10 ` Stefan Kangas
2020-09-01 14:19 ` Anonymous
2020-09-01 14:29 ` Eli Zaretskii
2020-09-01 16:49 ` Anonymous
2020-09-01 17:09 ` Eli Zaretskii
2020-09-01 17:15 ` Stefan Kangas
2020-09-02 10:00 ` Anonymous
2020-09-06 14:31 ` Mattias Engdegård
2020-09-06 14:38 ` Lars Ingebrigtsen
2020-09-06 15:44 ` Mattias Engdegård
2020-09-06 23:07 ` Lars Ingebrigtsen
2020-09-07 7:25 ` Mattias Engdegård
2020-09-07 10:20 ` Lars Ingebrigtsen
2020-09-07 12:24 ` Angelo Graziosi
2020-09-07 12:58 ` Anonymous
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=87pn6z29fe.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43152@debbugs.gnu.org \
--cc=angelo.g0@libero.it \
--cc=ann.onymous@orange.fr \
--cc=eggert@cs.ucla.edu \
--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 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).