From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>, Paul Eggert <eggert@cs.ucla.edu>
Cc: fabrice.popineau@centralesupelec.fr, emacs-devel@gnu.org
Subject: Re: Suspicious warning in W64 build
Date: Fri, 15 Sep 2017 11:59:47 +0300 [thread overview]
Message-ID: <83d16smj5o.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58og455aSJTq=Cg=upvwo2TGO-x3MEW1pE+6J+OK-BGQ4nA@mail.gmail.com> (message from Richard Copley on Thu, 14 Sep 2017 20:34:42 +0100)
> From: Richard Copley <rcopley@gmail.com>
> Date: Thu, 14 Sep 2017 20:34:42 +0100
> Cc: Fabrice Popineau <fabrice.popineau@centralesupelec.fr>,
> Emacs Development <emacs-devel@gnu.org>
>
> On 14 September 2017 at 18:47, Eli Zaretskii <eliz@gnu.org> wrote:
> > It was a mess, but I hope I fixed these warnings now. Please try the
> > latest master and see if any fallout remains.
>
> Not much. Here's another transcript. It's a lot better.
Some of the warnings are not Windows specific, so I'm CC'ing Paul.
CC eval.o
eval.c: In function 'internal_catch':
eval.c:1431:19: warning: variable 'c' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]
struct handler *c = handlerlist->nextfree;
^
eval.c: In function 'internal_condition_case':
eval.c:1431:19: warning: variable 'c' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]
eval.c: In function 'internal_condition_case_1':
eval.c:1431:19: warning: variable 'c' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]
eval.c: In function 'internal_condition_case_2':
eval.c:1431:19: warning: variable 'c' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]
eval.c: In function 'internal_condition_case_n':
eval.c:1431:19: warning: variable 'c' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]
eval.c: In function 'internal_catch.constprop':
eval.c:1431:19: warning: variable 'c' might be clobbered by 'longjmp' or 'vfork' [-Wclobbered]
Not sure what to do about this. Add 'volatile' to the declaration of
'c'?
CC search.o
search.c: In function 'Freplace_match':
search.c:2621:15: warning: argument 1 value '2305843009213693951' exceeds maximum object size 2147483647 [-Walloc-size-larger-than=]
substed = xmalloc (substed_alloc_size);
~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from search.c:24:0:
lisp.h:4439:14: note: in a call to allocation function 'xmalloc' declared here
extern void *xmalloc (size_t) ATTRIBUTE_MALLOC_SIZE ((1));
^~~~~~~
This seems to imply that m4/manywarnings.m4 has a bug: it somehow
deduces that a 64-bit Windows build can only allocate up to LONG_MAX
bytes. But 'long' is a 32-bit type on 64-bit MS-Windows, whereas
'size_t' is a 64-bit type, as is 'ptrdiff_t', which might be the
reason for this problem, if manywarnings.m4 somehow assumes that this
combination cannot happen.
next prev parent reply other threads:[~2017-09-15 8:59 UTC|newest]
Thread overview: 123+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 13:38 Suspicious warning in W64 build Angelo Graziosi
2017-09-05 14:04 ` Richard Copley
2017-09-07 15:16 ` Eli Zaretskii
2017-09-07 15:42 ` Angelo Graziosi
2017-09-07 17:52 ` Richard Copley
2017-09-07 17:58 ` Richard Copley
2017-09-07 19:00 ` Angelo Graziosi
2017-09-07 19:21 ` Richard Copley
2017-09-09 4:58 ` Herring, Davis
2017-09-09 9:55 ` Richard Copley
2017-09-09 10:20 ` Eli Zaretskii
2017-09-09 11:24 ` Angelo Graziosi
2017-09-09 13:25 ` Eli Zaretskii
2017-09-09 11:16 ` Angelo Graziosi
2017-09-07 18:58 ` Eli Zaretskii
2017-09-07 19:26 ` Paul Eggert
2017-09-07 19:50 ` Richard Copley
2017-09-07 20:02 ` Richard Copley
2017-09-08 6:49 ` Eli Zaretskii
2017-09-08 8:02 ` Eli Zaretskii
2017-09-08 19:31 ` Richard Copley
2017-09-08 20:17 ` Eli Zaretskii
2017-09-08 21:08 ` Richard Copley
2017-09-08 21:37 ` Richard Copley
2017-09-09 7:37 ` Eli Zaretskii
2017-09-08 22:20 ` Richard Copley
2017-09-09 7:33 ` Eli Zaretskii
2017-09-09 9:36 ` Richard Copley
2017-09-09 10:42 ` Eli Zaretskii
2017-09-09 10:52 ` Eli Zaretskii
2017-09-09 11:17 ` Richard Copley
2017-09-09 16:07 ` Eli Zaretskii
2017-09-10 1:01 ` Richard Copley
2017-09-10 14:40 ` Eli Zaretskii
2017-09-10 19:14 ` Richard Copley
2017-09-10 19:38 ` Angelo Graziosi
2017-09-11 16:17 ` Eli Zaretskii
2017-09-11 22:21 ` Angelo Graziosi
2017-09-11 16:39 ` Óscar Fuentes
2017-09-11 17:20 ` Eli Zaretskii
2017-09-12 17:49 ` Eli Zaretskii
2017-09-12 18:01 ` Fabrice Popineau
2017-09-12 18:37 ` Richard Copley
2017-09-12 18:59 ` Eli Zaretskii
2017-09-12 19:14 ` Richard Copley
2017-09-12 18:38 ` Eli Zaretskii
2017-09-14 17:47 ` Eli Zaretskii
2017-09-14 19:34 ` Richard Copley
2017-09-15 8:54 ` Eli Zaretskii
2017-09-15 23:05 ` Richard Copley
2017-09-16 6:40 ` Eli Zaretskii
2017-09-16 8:19 ` Richard Copley
2017-09-16 8:34 ` Richard Copley
2017-09-16 8:54 ` Eli Zaretskii
2017-09-16 9:07 ` Richard Copley
2017-09-16 11:54 ` Fabrice Popineau
2017-09-16 8:52 ` Eli Zaretskii
2017-09-15 8:59 ` Eli Zaretskii [this message]
2017-09-15 14:43 ` Eli Zaretskii
2017-09-17 6:42 ` Paul Eggert
2017-09-17 7:14 ` Richard Copley
2017-09-17 14:31 ` Eli Zaretskii
2017-09-17 6:40 ` Paul Eggert
2017-09-17 14:29 ` Eli Zaretskii
2017-09-17 16:39 ` Fabrice Popineau
2017-09-17 16:52 ` Eli Zaretskii
2017-09-18 0:26 ` Paul Eggert
2017-09-18 11:47 ` Fabrice Popineau
2017-09-18 14:46 ` Eli Zaretskii
2017-09-18 0:01 ` Richard Stallman
2017-09-14 19:36 ` Fabrice Popineau
2017-09-14 21:17 ` Andy Moreton
2017-09-15 6:55 ` Fabrice Popineau
2017-09-15 9:12 ` Eli Zaretskii
2017-09-15 15:33 ` Fabrice Popineau
2017-09-15 15:45 ` Eli Zaretskii
2017-09-15 18:15 ` Fabrice Popineau
2017-09-15 19:00 ` Eli Zaretskii
2017-09-15 21:02 ` Fabrice Popineau
2017-09-16 7:45 ` Eli Zaretskii
2017-09-17 7:01 ` Paul Eggert
2017-09-17 14:31 ` Eli Zaretskii
2017-09-17 14:52 ` Philipp Stephani
2017-09-17 22:34 ` Paul Eggert
2017-09-17 17:07 ` Paul Eggert
2017-09-17 17:14 ` Eli Zaretskii
2017-09-17 18:53 ` Paul Eggert
2017-09-17 19:30 ` Eli Zaretskii
2017-09-17 20:34 ` Paul Eggert
2017-09-18 2:30 ` Eli Zaretskii
2017-09-18 4:52 ` Paul Eggert
2017-09-18 14:41 ` Eli Zaretskii
2017-09-18 17:35 ` Paul Eggert
2017-09-18 17:58 ` Andy Moreton
2017-09-19 9:05 ` Paul Eggert
2017-09-18 18:01 ` Eli Zaretskii
2017-09-17 20:45 ` Paul Eggert
2017-09-16 13:17 ` Andy Moreton
2017-09-16 13:46 ` Eli Zaretskii
2017-09-16 18:57 ` Richard Copley
2017-09-16 19:21 ` Eli Zaretskii
2017-09-15 9:03 ` Eli Zaretskii
2017-09-09 8:49 ` Angelo Graziosi
2017-09-09 10:37 ` Eli Zaretskii
2017-09-09 11:32 ` Angelo Graziosi
2017-09-09 13:28 ` Eli Zaretskii
2017-09-09 13:33 ` Fabrice Popineau
2017-09-09 14:55 ` Angelo Graziosi
2017-09-09 16:37 ` Eli Zaretskii
2017-09-09 18:38 ` Angelo Graziosi
2017-09-09 18:59 ` Eli Zaretskii
2017-09-09 21:29 ` Angelo Graziosi
2017-09-10 14:56 ` Eli Zaretskii
2017-09-10 15:45 ` Angelo Graziosi
2017-09-10 16:02 ` Eli Zaretskii
2017-09-10 18:45 ` Angelo Graziosi
2017-09-10 19:43 ` Eli Zaretskii
2017-09-09 15:40 ` Angelo Graziosi
2017-09-09 16:40 ` Eli Zaretskii
2017-09-09 18:33 ` Fabrice Popineau
2017-09-07 20:20 ` Eli Zaretskii
2017-09-07 21:59 ` Angelo Graziosi
2017-09-08 8:01 ` Eli Zaretskii
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=83d16smj5o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=fabrice.popineau@centralesupelec.fr \
--cc=rcopley@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 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.