From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3108 invoked by alias); 18 May 2009 19:24:23 -0000 Received: (qmail 3083 invoked by uid 22791); 18 May 2009 19:24:17 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 18 May 2009 19:24:11 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n4IJNi2g027413; Mon, 18 May 2009 15:23:44 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n4IJNhkm027458; Mon, 18 May 2009 15:23:43 -0400 Received: from opsy.redhat.com (vpn-12-127.rdu.redhat.com [10.11.12.127]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n4IJNgNc021184; Mon, 18 May 2009 15:23:42 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 261E63784BC; Mon, 18 May 2009 13:23:42 -0600 (MDT) To: Joel Brobecker Cc: muller@ics.u-strasbg.fr, gdb-patches@sourceware.org Subject: Re: [ARI] Add "bzero" References: <200904301028.29435.pedro@codesourcery.com> <200905061038.11004.pedro@codesourcery.com> <20090506160250.GJ10734@adacore.com> From: Tom Tromey Reply-To: tromey@redhat.com Date: Mon, 18 May 2009 19:24:00 -0000 In-Reply-To: <20090506160250.GJ10734@adacore.com> (Joel Brobecker's message of "Wed\, 6 May 2009 09\:02\:50 -0700") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-05/txt/msg00372.txt.bz2 >>>>> "Joel" == Joel Brobecker writes: Joel> Would you mind adding bzero to the list of functions in the ARI that Joel> should not be used? I think this would be useful to have. The following Joel> patch should work, but I'm not sure how you test it, and i'm also not Joel> sure about the right category... For this specific case, and some others like it, perhaps using #pragma poison would be better. That would result in a compile time error, rather than a report on a web page. Tom