From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by sourceware.org (Postfix) with ESMTPS id 7A83C385780F for ; Fri, 6 May 2022 16:46:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 7A83C385780F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cs.columbia.edu Authentication-Results: sourceware.org; spf=none smtp.mailfrom=cs.columbia.edu Received: from compute02.cs.columbia.edu (compute02.cs.columbia.edu [128.59.11.32]) by mailbackend.panix.com (Postfix) with ESMTPSA id 4KvxKF08kCz3mTV for ; Fri, 6 May 2022 12:46:08 -0400 (EDT) Resent-Message-ID: <25205.20680.588287.250361@compute02.cs.columbia.edu> Resent-Date: Fri, 6 May 2022 12:46:00 -0400 Resent-From: Jonathan Lennox Resent-To: gcc@gcc.gnu.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <25205.20262.994817.37250@compute02.cs.columbia.edu> In-Reply-To: References: X-Mailer: VM 8.2.0b under 24.5.1 (x86_64-pc-linux-gnu) From: Jonathan Lennox To: matthias.gehre@amd.com (Matthias Gehre) Subject: Re: AW: [RFC] Adding division/modulo on arbitrary =?iso-8859-1?Q?precision=A0integers=A0to=A0libgcc?= Date: Fri, 6 May 2022 12:39:02 -0400 X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_LINKBAIT, NICE_REPLY_A, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2022 16:46:11 -0000 On Friday, May 6 2022, "Matthias Gehre" wrote to "lennox" saying: > Jakub Jelinek wrote: > > Rather than uint32_t, wouldn't using the word size (64-bit for lp64, 32-bit > for ilp32) be better? > Is there a portable way to specify this in C? (size_t, uintptr_t?) And is the word size > clearly defined for each target? (I'm not a backend expert). Wouldn't this just be 'unsigned long' by definition? -- Jonathan Lennox lennox@cs.columbia.edu