From: Lars Ingebrigtsen <larsi@gnus.org>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: ./configure --enable-check-lisp-object-type
Date: Tue, 12 Apr 2022 18:58:54 +0200 [thread overview]
Message-ID: <878rsack6p.fsf@gnus.org> (raw)
For the first time in a while I enabled the Lisp object type, and I was
given a wall of
dispnew.c:6593:1: note: in expansion of macro ‘DEFUN’
6593 | DEFUN ("internal-show-cursor-p", Finternal_show_cursor_p,
| ^~~~~
lisp.h:3179:5: warning: missing braces around initializer [-Wmissing-braces]
3179 | {{{{ PVEC_SUBR << PSEUDOVECTOR_AREA_BITS }, \
| ^
for every DEFUN. That's new, isn't it? (This is on Debian/bookworm.)
This is from this:
#define DEFUN(lname, fnname, sname, minargs, maxargs, intspec, doc) \
SUBR_SECTION_ATTRIBUTE \
static union Aligned_Lisp_Subr sname = \
{{{ PVEC_SUBR << PSEUDOVECTOR_AREA_BITS }, \
{ .a ## maxargs = fnname }, \
minargs, maxargs, lname, {intspec}, 0}}; \
Lisp_Object fnname
That seems like beaucoup de braces, so is that a gcc bug or something?
(Adding more braces makes compilation fail.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next reply other threads:[~2022-04-12 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 16:58 Lars Ingebrigtsen [this message]
2022-04-12 17:23 ` ./configure --enable-check-lisp-object-type Stefan Monnier
2022-04-12 17:43 ` Eli Zaretskii
2022-04-12 18:27 ` Lars Ingebrigtsen
2022-04-12 18:34 ` Eli Zaretskii
2022-04-12 18:40 ` Lars Ingebrigtsen
2022-04-12 19:05 ` Eli Zaretskii
2022-04-12 22:20 ` Stefan Monnier
2022-04-13 8:47 ` martin rudalics
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=878rsack6p.fsf@gnus.org \
--to=larsi@gnus.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).