From: David Ponce via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 70568@debbugs.gnu.org
Subject: bug#70568: 30.0.50; build warnings on 'x86_64-pc-linux-gnu'
Date: Thu, 25 Apr 2024 17:11:54 +0200 [thread overview]
Message-ID: <44d83703-e398-468b-a336-2e019984b2d0@orange.fr> (raw)
Hello,
When I build Emacs configured for 'x86_64-pc-linux-gnu' on Fedora 39 with gcc 13.2.1
the below warnings are reported:
1) ./configure --with-x-toolkit=lucid --with-native-compilation=no
..
CC xterm.o
xterm.c: In function ‘x_alloc_nearest_color_1’:
xterm.c:9374:27: warning: potential null pointer dereference [-Wnull-dereference]
9374 | if (dpyinfo->visual_info.class == DirectColor)
| ~~~~~~~~~~~~~~~~~~~~^~~~~~
xterm.c:9374:27: warning: potential null pointer dereference [-Wnull-dereference]
...
CC eval.o
In file included from eval.c:25:
lisp.h: In function ‘internal_lisp_condition_case’:
lisp.h:1129:15: warning: variable ‘sym’ might be clobbered by ‘longjmp’ or ‘vfork’ [-Wclobbered]
1129 | Lisp_Object sym = XSYMBOL_WITH_POS (a)->sym;
| ^~~
eval.c:1413:43: warning: argument ‘var’ might be clobbered by ‘longjmp’ or ‘vfork’ [-Wclobbered]
1413 | internal_lisp_condition_case (Lisp_Object var, Lisp_Object bodyform,
| ~~~~~~~~~~~~^~~
...
2) ./configure --with-x-toolkit=gtk3 --with-cairo-xcb --with-native-compilation=no
...
CC eval.o
In file included from eval.c:25:
lisp.h: In function ‘internal_lisp_condition_case’:
lisp.h:1129:15: warning: variable ‘sym’ might be clobbered by ‘longjmp’ or ‘vfork’ [-Wclobbered]
1129 | Lisp_Object sym = XSYMBOL_WITH_POS (a)->sym;
| ^~~
eval.c:1413:43: warning: argument ‘var’ might be clobbered by ‘longjmp’ or ‘vfork’ [-Wclobbered]
1413 | internal_lisp_condition_case (Lisp_Object var, Lisp_Object bodyform,
| ~~~~~~~~~~~~^~~
...
In both cases (Lucid, gtk3) the reported warnings don't seem to affect run.
Thanks
next reply other threads:[~2024-04-25 15:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 15:11 David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-04-27 9:37 ` bug#70568: 30.0.50; build warnings on 'x86_64-pc-linux-gnu' Eli Zaretskii
2024-04-27 22:20 ` Paul Eggert
2024-04-28 5:04 ` Eli Zaretskii
2024-04-28 5:05 ` Eli Zaretskii
2024-04-28 5:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-01 7:18 ` David Ponce via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-01 7:26 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44d83703-e398-468b-a336-2e019984b2d0@orange.fr \
--to=bug-gnu-emacs@gnu.org \
--cc=70568@debbugs.gnu.org \
--cc=da_vid@orange.fr \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.