From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9811 invoked by alias); 13 Oct 2006 12:44:00 -0000 Received: (qmail 9753 invoked by uid 48); 13 Oct 2006 12:43:50 -0000 Date: Fri, 13 Oct 2006 12:44:00 -0000 Message-ID: <20061013124350.9752.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/28656] duplicated null argument warning on memcpy() In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "falk at debian dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-10/txt/msg01126.txt.bz2 List-Id: ------- Comment #2 from falk at debian dot org 2006-10-13 12:43 ------- >>From the standard: [...] n can have the value zero on a call to that function. Unless explicitly stated otherwise in the description of a particular function in this subclause, pointer arguments on such a call shall still have valid values. So the warning is justified (but not giving it twice). For the missing warning on the second memcpy, please file a second report since this is a totally different problem (and would require some aliasing analysis to detect). -- falk at debian dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|unhelpful null argument |duplicated null argument |warning on memcpy() |warning on memcpy() http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28656