This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] RISC-V: Allow 32-bit BFD to handle 64-bit objects

From: Jeff Law <law at redhat dot com>
To: Palmer Dabbelt <palmer at dabbelt dot com>, binutils at sourceware dot org
Cc: patches at groups dot riscv dot org
Date: Mon, 1 May 2017 16:05:23 -0600
Subject: Re: [PATCH] RISC-V: Allow 32-bit BFD to handle 64-bit objects
Authentication-results: sourceware.org; auth=none
Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=law at redhat dot com
Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 999DE31E962
Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 999DE31E962
References: <20170501203303.21729-1-palmer@dabbelt.com>

On 05/01/2017 02:33 PM, Palmer Dabbelt wrote:

We've been telling people that the riscv32-* and riscv64-* toolchains
are exactly the same, but it turns out we were lying: the riscv32-* BFD
doesn't handle 64-bit objects.  This fixes that difference, so the ports
are actually the same.

bfd/ChangeLog

2017-05-01  Palmer Dabbelt  <palmer@dabbelt.com>

         * config.bfd (riscv32-*): Enable unconditionally.
         (riscv64-*): Likewise.

This is obviously a decision for the binutils maintainers, but I canconfirm that with the patch installed, GCC is able to build throughtarget-libgcc for riscv32, which it couldn't previously do because theriscv32 BFD bits would blow up assembling the 64bit multilib codeproduced by GCC.


jeff

References:
- [PATCH] RISC-V: Allow 32-bit BFD to handle 64-bit objects
  - From: Palmer Dabbelt

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]