From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22610 invoked by alias); 8 Sep 2008 15:32:18 -0000 Received: (qmail 22600 invoked by uid 22791); 8 Sep 2008 15:32:17 -0000 X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 08 Sep 2008 15:31:38 +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 m88FV1c4001303 for ; Mon, 8 Sep 2008 11:31:22 -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 m88FUoXs007786 for ; Mon, 8 Sep 2008 11:30:50 -0400 Received: from opsy.redhat.com (vpn-10-97.bos.redhat.com [10.16.10.97]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id m88FUmom024589; Mon, 8 Sep 2008 11:30:48 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id E9871378174; Mon, 8 Sep 2008 09:30:47 -0600 (MDT) To: Jan Kratochvil Cc: gdb-patches@sourceware.org Subject: Re: [patch] static_kind -> bit0, bit1 [Re: [gdb] Fortran dynamic arrays] References: <20080818111120.GE16894@adacore.com> <200808181553.m7IFrG3w005270@d12av02.megacenter.de.ibm.com> <48A59B3C.9050801@net-b.de> <20080818111120.GE16894@adacore.com> <20080907115637.GA12939@host0.dyn.jankratochvil.net> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Mon, 08 Sep 2008 15:32:00 -0000 In-Reply-To: <20080907115637.GA12939@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Sun\, 7 Sep 2008 13\:56\:37 +0200") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (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: 2008-09/txt/msg00164.txt.bz2 >>>>> "Jan" == Jan Kratochvil writes: Jan> One of such spare space there is `enum array_bound_type' Except Jan> for BOUND_CANNOT_BE_DETERMINED it is never set anywhere. Jan> BOUND_BY_* are read only in f-valprint.c. In fact it could be Jan> probably used for the new bits TYPE_BOUND_IS_DWARF_BLOCK and Jan> possibly TYPE_HIGH_BOUND_IS_COUNT but I would rather like to Jan> later remove `enum array_bound_type' and its fields at all. This sounds like a good cleanup to me. Jan> The patch modifies a lot of sources trying to follow the new Jan> style of main_type bitfields instead of the former FLAGS Jan> variable. I do not think current main_type layout is right but Jan> the patch tries to follow the current main_type style. Do you mean the main_type layout after this patch, or before this patch? If before -- could you be more specific? Tom