|
Message-ID: <alpine.LNX.2.20.13.1707061957580.21060@monopod.intra.ispras.ru> Date: Thu, 6 Jul 2017 20:02:12 +0300 (MSK) From: Alexander Monakov <amonakov@...ras.ru> To: musl@...ts.openwall.com Subject: Re: Documentation of memcpy and undefined behavior in memset 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? Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.