From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-338774-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 30292 invoked by alias); 27 Mar 2013 14:18:48 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 30270 invoked by uid 89); 27 Mar 2013 14:18:40 -0000
X-Spam-SWARE-Status: No, score=-4.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1
Received: from mail-wg0-f53.google.com (HELO mail-wg0-f53.google.com) (74.125.82.53)    by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 27 Mar 2013 14:18:38 +0000
Received: by mail-wg0-f53.google.com with SMTP id c11so554878wgh.20        for <gcc-patches@gcc.gnu.org>; Wed, 27 Mar 2013 07:18:36 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.21.233 with SMTP id y9mr31906960wje.47.1364393913612; Wed, 27 Mar 2013 07:18:33 -0700 (PDT)
Received: by 10.194.56.100 with HTTP; Wed, 27 Mar 2013 07:18:33 -0700 (PDT)
In-Reply-To: <512D530E.5050204@naturalbridge.com>
References: <506C72C7.7090207@naturalbridge.com>	<CAFiYyc3viOLSJA_188-3w-Lc7ugL17j7uBXOvHQ4gnU3u7L6_Q@mail.gmail.com>	<506D9544.7020408@naturalbridge.com>	<CAFiYyc0No3S6dmRjrzDZbuN=ujbsgUog3R4S2gVn4z2sihBiiw@mail.gmail.com>	<506DD085.7080608@naturalbridge.com>	<87txuaox52.fsf@talisman.home>	<CAFiYyc1GP46Sf9Tr=YWL1EhWwhcfRFBQoiH8jV-PZv-krsWJmg@mail.gmail.com>	<87lifli6oj.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com>	<CAFiYyc1RYvJ-2_6WaYosA3qm5JhiGhmXnczX3DCNfKt_zg46+g@mail.gmail.com>	<87ehldi2kr.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com>	<CAFiYyc0B27i23X8Sg+=yOd_SqKedB3RunBDs4b-Jm-fSAD-hwA@mail.gmail.com>	<87a9w1hzq1.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com>	<CAFiYyc0Sj3+yBXRjLUG=0=_NGQiU1VqJk35hjsWqHR9bCnqspg@mail.gmail.com>	<506F0C1A.5010705@naturalbridge.com>	<87lifkhlo9.fsf@sandifor-thinkpad.stglab.manchester.uk.ibm.com>	<506F5B50.2040800@naturalbridge.com>	<506F63CC.40507@naturalbridge.com>	<512D530E.5050204@naturalbridge.com>
Date: Wed, 27 Mar 2013 14:18:00 -0000
Message-ID: <CAFiYyc3nvowZS4atYoRwsmY=sNcwVT_aDWmLHZvqzdcS167t=g@mail.gmail.com>
Subject: Re: patch to fix constant math - second small patch -patch ping for next stage 1
From: Richard Biener <richard.guenther@gmail.com>
To: Kenneth Zadeck <zadeck@naturalbridge.com>
Cc: Mike Stump <mikestump@comcast.net>, gcc-patches <gcc-patches@gcc.gnu.org>, 	rdsandiford@googlemail.com, Ian Lance Taylor <iant@google.com>
Content-Type: text/plain; charset=ISO-8859-1
X-SW-Source: 2013-03/txt/msg01149.txt.bz2

On Wed, Feb 27, 2013 at 1:27 AM, Kenneth Zadeck
<zadeck@naturalbridge.com> wrote:
> Here is the second of my wide int patches with the patch rot removed.
>
> I would like to get these pre approved for the next stage 1.
> On 10/05/2012 06:48 PM, Kenneth Zadeck wrote:
>>
>> This patch adds machinery to genmodes.c so that largest possible sizes of
>> various data structures can be determined at gcc build time. These functions
>> create 3 symbols that are available in insn-modes.h:
>> MAX_BITSIZE_MODE_INT - the bitsize of the largest int.
>> MAX_BITSIZE_MODE_PARTIAL_INT - the bitsize of the largest partial int.
>> MAX_BITSIZE_MODE_ANY_INT - the largest bitsize of any kind of int.

I remember we have discussed about the need to special-case/handle partial
integer modes.  Do further patches use the _INT and _PARTIAL_INT sizes
at all?  I'm fine with providing MAX_BITSIZE_MODE_ANY_INT.

Richard.