[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Suspicious warning in W64 build
From: |
Eli Zaretskii |
Subject: |
Re: Suspicious warning in W64 build |
Date: |
Sat, 16 Sep 2017 10:45:46 +0300 |
> From: Fabrice Popineau <address@hidden>
> Date: Fri, 15 Sep 2017 23:02:45 +0200
> Cc: Andy Moreton <address@hidden>, Emacs developers <address@hidden>
>
> Remaining warnings :
>
> - indent.c:scan_for_column() -> you reported it
>
> - search.c:Freplace_match()
>
> ../../emacs/src/search.c: In function 'Freplace_match':
> ../../emacs/src/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 ../../emacs/src/search.c:24:0:
> ../../emacs/src/lisp.h:4440:14: note: in a call to allocation function
> 'xmalloc' declared here
> extern void *xmalloc (size_t) ATTRIBUTE_MALLOC_SIZE ((1));
> ^~~~~~~
I already reported this, it looks like a bug in Gnulib's
manywarnings.m4.
> - data.c:
>
> ../../emacs/src/data.c: In function 'minmax_driver':
> ../../emacs/src/data.c:3022:9: warning: 'accum.i' may be used uninitialized
> in this function
> [-Wmaybe-uninitialized]
> return accum;
> ^~~~~
So now even eassume is not enough? Anyway, should be fixed now.
> - eval.c
>
> ../../emacs/src/eval.c: In function 'internal_catch':
> ../../emacs/src/eval.c:1431:19: warning: variable 'c' might be clobbered by
> 'longjmp' or 'vfork' [-Wclobbered]
> struct handler *c = handlerlist->nextfree;
> ^
> ../../emacs/src/eval.c: In function 'internal_condition_case':
> ../../emacs/src/eval.c:1431:19: warning: variable 'c' might be clobbered by
> 'longjmp' or 'vfork' [-Wclobbered]
> ../../emacs/src/eval.c: In function 'internal_condition_case_1':
> ../../emacs/src/eval.c:1431:19: warning: variable 'c' might be clobbered by
> 'longjmp' or 'vfork' [-Wclobbered]
> ../../emacs/src/eval.c: In function 'internal_condition_case_2':
> ../../emacs/src/eval.c:1431:19: warning: variable 'c' might be clobbered by
> 'longjmp' or 'vfork' [-Wclobbered]
> ../../emacs/src/eval.c: In function 'internal_condition_case_n':
> ../../emacs/src/eval.c:1431:19: warning: variable 'c' might be clobbered by
> 'longjmp' or 'vfork' [-Wclobbered]
> ../../emacs/src/eval.c: In function 'internal_catch.constprop':
> ../../emacs/src/eval.c:1431:19: warning: variable 'c' might be clobbered by
> 'longjmp' or 'vfork' [-Wclobbered]
Already reported.
> - w32.c
>
> ../../emacs/src/w32.c:7551:1: warning: no previous prototype for
> 'sys_strerror' [-Wmissing-prototypes]
> sys_strerror (int error_no)
> ^~~~~~~~~~~~
Already reported; I need the MinGW64 users figure why what works for
mingw.org doesn't for MinGW64. See my response to Richard.
- Re: Suspicious warning in W64 build, (continued)
- Re: Suspicious warning in W64 build, Richard Stallman, 2017/09/17
- Re: Suspicious warning in W64 build, Fabrice Popineau, 2017/09/14
- Re: Suspicious warning in W64 build, Andy Moreton, 2017/09/14
- Re: Suspicious warning in W64 build, Fabrice Popineau, 2017/09/15
- Re: Suspicious warning in W64 build, Eli Zaretskii, 2017/09/15
- Re: Suspicious warning in W64 build, Fabrice Popineau, 2017/09/15
- Re: Suspicious warning in W64 build, Eli Zaretskii, 2017/09/15
- Re: Suspicious warning in W64 build, Fabrice Popineau, 2017/09/15
- Re: Suspicious warning in W64 build, Eli Zaretskii, 2017/09/15
- Re: Suspicious warning in W64 build, Fabrice Popineau, 2017/09/15
- Re: Suspicious warning in W64 build,
Eli Zaretskii <=
- Re: Suspicious warning in W64 build, Paul Eggert, 2017/09/17
- Re: Suspicious warning in W64 build, Eli Zaretskii, 2017/09/17
- Re: Suspicious warning in W64 build, Philipp Stephani, 2017/09/17
- Re: Suspicious warning in W64 build, Paul Eggert, 2017/09/17
- Re: Suspicious warning in W64 build, Paul Eggert, 2017/09/17
- Re: Suspicious warning in W64 build, Eli Zaretskii, 2017/09/17
- Re: Suspicious warning in W64 build, Paul Eggert, 2017/09/17
- Re: Suspicious warning in W64 build, Eli Zaretskii, 2017/09/17
- Re: Suspicious warning in W64 build, Paul Eggert, 2017/09/17
- Re: Suspicious warning in W64 build, Eli Zaretskii, 2017/09/17