From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/11680 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Documentation of memcpy and undefined behavior in memset Date: Thu, 6 Jul 2017 13:11:01 -0400 Message-ID: <20170706171101.GD1627@brightrain.aerifal.cx> References: <0F9B48AD-C5B3-44B6-8D82-0985CF8604A0@trust-in-soft.com> <20170706162353.GC1627@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1499361080 7923 195.159.176.226 (6 Jul 2017 17:11:20 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 6 Jul 2017 17:11:20 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-11693-gllmg-musl=m.gmane.org@lists.openwall.com Thu Jul 06 19:11:16 2017 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1dTAJ4-0001ab-8M for gllmg-musl@m.gmane.org; Thu, 06 Jul 2017 19:11:10 +0200 Original-Received: (qmail 17426 invoked by uid 550); 6 Jul 2017 17:11:13 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 17408 invoked from network); 6 Jul 2017 17:11:13 -0000 Content-Disposition: inline In-Reply-To: Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:11680 Archived-At: On Thu, Jul 06, 2017 at 08:02:12PM +0300, Alexander Monakov wrote: > On Thu, 6 Jul 2017, Rich Felker wrote: > > FWIW, I think GCC may do aggressive optimization based on the > > assumption that memcpy implies the pointer points to an object (of > > size at least 1) > > The compiler can deduce that the pointer is non-null (and that's > fine), but otherwise I don't see what possible optimizations could > take place. Did you have something specific in mind? It could presumably move loads from after a branch to before. E.g. memcpy(q,p,0); if (whatever) { y=*p; ... } /* y not used after here */ to: memcpy(q,p,0); y=*p; if (whatever) { ... } /* y not used after here */ If p points to one past the end of an object that ends on a page boundary, this transformation could introduce a crash. Rich