unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs pretest 28.1.90 is out
Date: Fri, 01 Jul 2022 09:15:43 +0200	[thread overview]
Message-ID: <86o7y9xq00.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=wkmCoq3z=yotQq_6sVcT-ZwEahrcONwqTSSP1FyQ24w@mail.gmail.com> (Stefan Kangas's message of "Thu, 30 Jun 2022 05:52:37 -0700")

Stefan Kangas <stefan@marxist.se> writes:

> The first pretest for what will be the 28.2 release of Emacs (the
> extensible text editor) is available at:
>
>   https://alpha.gnu.org/gnu/emacs/pretest/emacs-28.1.90.tar.xz

Thanks, builds fine on Win10 with Mingw64 (I ran only ./configure and
make).  I get only these warnings:

  CCLD     make-docfile.exe
  CCLD     make-fingerprint.exe
In function 'main':
cc1.exe: warning: '__builtin_memcpy' writing 12 bytes into a region of size between 0 and 7 [-Wstringop-overflow=]
In file included from ctags.c:2:
etags.c:1429:21: note: destination object of size [0, 7] allocated by 'xmalloc'
 1429 |         char *cmd = xmalloc (2 * strlen (tagfile) + sizeof "sort -u -o..");
      |                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
etags.c:1435:14: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
 1435 |         *z++ = ' ';
      |         ~~~~~^~~~~
etags.c:1429:21: note: at offset 11 into destination object of size [0, 7] allocated by 'xmalloc'
 1429 |         char *cmd = xmalloc (2 * strlen (tagfile) + sizeof "sort -u -o..");
      |                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
etags.c:1434:13: warning: 'stpcpy' writing 1 or more bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]
 1434 |         z = stpcpy (z, tagfile);
      |             ^~~~~~~~~~~~~~~~~~~
etags.c:1429:21: note: at offset 11 into destination object of size [0, 7] allocated by 'xmalloc'
 1429 |         char *cmd = xmalloc (2 * strlen (tagfile) + sizeof "sort -u -o..");
      |                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
etags.c:1436:9: warning: 'strcpy' writing 1 or more bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]
 1436 |         strcpy (z, tagfile);
      |         ^~~~~~~~~~~~~~~~~~~
etags.c:1429:21: note: at offset 12 into destination object of size [0, 7] allocated by 'xmalloc'
 1429 |         char *cmd = xmalloc (2 * strlen (tagfile) + sizeof "sort -u -o..");
      |                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I can't tell if they can be ignored or not.  This is with gcc 12.1.0.

Best, Arash



  reply	other threads:[~2022-07-01  7:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 12:52 Emacs pretest 28.1.90 is out Stefan Kangas
2022-07-01  7:15 ` Arash Esbati [this message]
2022-07-01 10:59   ` Eli Zaretskii
2022-07-01 12:13     ` Andreas Schwab
2022-07-01 12:42       ` 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

  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=86o7y9xq00.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefan@marxist.se \
    /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).