zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>
Subject: Re: -Wrestrict warning on cc 8.3.0
Date: Thu, 4 Apr 2019 11:21:31 +0100	[thread overview]
Message-ID: <1554373291.5874.3.camel@samsung.com> (raw)
In-Reply-To: <CAEpdsia8j9iKU_fv2yoA84bNhJOS14AtjfE8YkJEPz7rHJsJsw@mail.gmail.com>

On Wed, 2019-04-03 at 20:59 +0200, Wesley Schwengle wrote:
> During a make of the latest master I got the following warning:
> 
> gcc -c -I. -I../../Src -I../../Src -I../../Src/Zle -I.  -DHAVE_CONFIG_H
> -DMODULE -Wall -Wmissing-prototypes -O2 -fPIC -o compctl..o compctl.c
> compctl.c: In function ‘makecomplistflags.isra.6’:
> compctl.c:3340:7: warning: ‘strcpy’ accessing 1 byte at offsets [0,
> 9223372036854775807] and [0,9223372036854775807] may overlap 1 byte at
> offset 0 [-Wrestrict]
> strcpy(p, p + bl);
> ^~~~~~~~~~~~~~~~~
> rm -f compctl.so

This warning is thoroughly opaque --- and not occurring with a locally
compiled gcc 8.3.0 on my Ubuntu 16.04 64-bit Intel system --- but the
code isn't exactly crystal clear, either (subtracting a number off then
adding it immediately back on again isn't generally regarded as great
style), and it's quite possible the copy is overlapping.  Also, the last
person to worry about code optimisation in compctl emigrated to the
Undying Lands a decade ago (maybe I can still find the postcard...)

Can somebody verify the following is equivalent apart from dealing with
a possible overlapping copy?  I've no way of ensuring this code gets
exercised.

Separately, I seem to be having severe problems with --enable-zsh-mem
with that configuration.  It looked like some failed optimisation
involving realloc().  I think we had something similar a while ago?

Cheers
pws


diff --git a/Src/Zle/compctl.c b/Src/Zle/compctl.c
index fe87409..f963d57 100644
--- a/Src/Zle/compctl.c
+++ b/Src/Zle/compctl.c
@@ -3331,13 +3331,11 @@ makecomplistflags(Compctl cc, char *s, int incmd, int compadd)
 	    zlemetaline[end] = save;
 	    if (brend) {
 		Brinfo bp;
-		char *p;
-		int bl;
 
 		for (bp = brend; bp; bp = bp->next) {
-		    p = lpsuf + (we - zlemetacs) - bp->qpos -
-			(bl = strlen(bp->str));
-		    strcpy(p, p + bl);
+		    char *p2 = lpsuf + (we - zlemetacs) - bp->qpos;
+		    char *p1 = p2 - strlen(bp->str);
+		    memmove(p1, p2, strlen(p2) + 1);
 		}
 	    }
 	    if (!(lpsuf = strchr(lpsuf, '/')) && sf2)


  reply	other threads:[~2019-04-04 10:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190403190049epcas3p4c02406857f7f26510ea8969c969a655e@epcas3p4.samsung.com>
2019-04-03 18:59 ` Wesley Schwengle
2019-04-04 10:21   ` Peter Stephenson [this message]
2019-04-10  8:48     ` Peter Stephenson
2019-04-10  8:58       ` Roman Perepelitsa

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=1554373291.5874.3.camel@samsung.com \
    --to=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).