From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 63628 invoked by alias); 9 Aug 2018 12:55:34 -0000 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 Received: (qmail 63507 invoked by uid 89); 9 Aug 2018 12:55:33 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=H*r:4001 X-HELO: eggs.gnu.org Received: from eggs.gnu.org (HELO eggs.gnu.org) (208.118.235.92) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 09 Aug 2018 12:55:31 +0000 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fnkTN-0007X8-E6 for gdb-patches@sourceware.org; Thu, 09 Aug 2018 08:55:29 -0400 Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39191) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fnkTN-0007X1-9I; Thu, 09 Aug 2018 08:55:25 -0400 Received: from [176.228.60.248] (port=4001 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fnkTM-0006Vc-L4; Thu, 09 Aug 2018 08:55:25 -0400 Date: Thu, 09 Aug 2018 12:55:00 -0000 Message-Id: <831sb7pumd.fsf@gnu.org> From: Eli Zaretskii To: Jim Wilson CC: tom@tromey.com, palmer@sifive.com, gdb-patches@sourceware.org In-reply-to: (message from Jim Wilson on Wed, 8 Aug 2018 20:43:20 -0700) Subject: Re: [PATCH 5/5] RISC-V: Add configure support riscv*-linux*. References: <878t5gjv94.fsf@tromey.com> <83600kp8pc.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-IsSubscribed: yes X-SW-Source: 2018-08/txt/msg00209.txt.bz2 > From: Jim Wilson > Date: Wed, 8 Aug 2018 20:43:20 -0700 > Cc: Tom Tromey , Palmer Dabbelt , gdb-patches@sourceware.org > > Since I'm looking at this at the moment... > > BFD will automatically enable 64-bit support if you configure on a > host with 64-bit support, or configure for a target with 64-bit > support. It will also enable 64-bit support if you use > --enable-64-bit-bfd. 64-bit support means you can use 64-bit integer > types such as long long on a 32-bit host or long on a 64-bit LP64 > host. If 64-bit support is enabled, and your compiler doesn't support > it, then you get a configure error. > > If you use --disable-64-bit-bfd, then bfd will disallow use of 64-bit > integer types. If you configure for a 64-bit target, you will get a > configure error. > > As a practical matter, I think --enable/disable-64-bit-bfd doesn't > really do anything useful unless you are configuring with > --enable-targets=all. In this case, 64-bit targets will be enabled by > default, and will fail to build on a 32-bit host with a compiler that > doesn't support long long. Thanks. So you are saying that building on a 64-bit hosts will enable this by default, while a 32-bit build with --enable-64-bit-bfd only makes sense if --enable-targets=all is also used, is that right?