From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6989 invoked by alias); 23 Nov 2011 14:16:55 -0000 Received: (qmail 6979 invoked by uid 22791); 23 Nov 2011 14:16:54 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO glazunov.sibelius.xs4all.nl) (83.163.83.176) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 23 Nov 2011 14:16:37 +0000 Received: from glazunov.sibelius.xs4all.nl (kettenis@localhost [127.0.0.1]) by glazunov.sibelius.xs4all.nl (8.14.5/8.14.3) with ESMTP id pANEGE7P028290; Wed, 23 Nov 2011 15:16:14 +0100 (CET) Received: (from kettenis@localhost) by glazunov.sibelius.xs4all.nl (8.14.5/8.14.3/Submit) id pANEGBpB026549; Wed, 23 Nov 2011 15:16:11 +0100 (CET) Date: Wed, 23 Nov 2011 14:16:00 -0000 Message-Id: <201111231416.pANEGBpB026549@glazunov.sibelius.xs4all.nl> From: Mark Kettenis To: tromey@redhat.com CC: pedro@codesourcery.com, gdb-patches@sourceware.org, werner@almesberger.net, jon@beniston.com In-reply-to: (message from Tom Tromey on Mon, 14 Nov 2011 09:20:36 -0700) Subject: Re: [PATCH] 32 bit-ism in lm32-tdep.c (and some sloppy macros) References: <20111111233808.GA10815@ws> <201111141612.17372.pedro@codesourcery.com> 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: 2011-11/txt/msg00613.txt.bz2 > From: Tom Tromey > Date: Mon, 14 Nov 2011 09:20:36 -0700 > > >>>>> "Pedro" == Pedro Alves writes: > > Pedro> On Monday 14 November 2011 15:48:48, Tom Tromey wrote: > >> I was a little surprised to find out we already use int16_t in gdb. > > Pedro> We pull stdint.h from gnulib. > > I was meaning to ask ... do we have a gnulib update policy? > I wanted to pull in stdbool.h and start using bool in gdb; plus maybe > some other bits so we can use O_CLOEXEC and friends (but only maybe -- > it isn't clear to me that gnulib is the best way to tackle this > problem). Anyway, then I noticed that the existing files are not > up-to-date against gnulib git. > > It seemed to me that updating now, just before a release, was maybe not > the best time. Any thoughts? I'd say we should only update if there is a specific need.