From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) by sourceware.org (Postfix) with ESMTPS id A92D9385802B for ; Thu, 9 Dec 2021 22:37:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A92D9385802B Received: by mail-pg1-x532.google.com with SMTP id 137so6405437pgg.3 for ; Thu, 09 Dec 2021 14:37:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=HLB4xK6DeLfx+p+uHHzPyluTpLOf+Ts9dqXFirhFK1o=; b=oY/ZCTe1yUm+YMGPgZ02it0xJq+4X9z0dduViNbWzkH/ZWNH3x+Gexv6h7yCG5pRpm LAyK8ipw6ZXXxmdoF5+lbH6sKK3ZWsdqpjio1BxZ95gme+DLZwJfgnueDnWGe8HOxAl0 hZZ1eJO2gavkwuypmeoVjdlYwUZdOVyn23fPyZ3T3yPcwjKe7m7uj+6p7y1nhqE6riE2 djxKnE3mCu4O5x+3OInw62FAVxw9yQDSqYxFRy2ToOF/0Z89Z81kBo4OLSg4jMJ5q7FA yUNw/sxtyKHF9JFq2YqeDep9HTpO7vIKgK8qkNBk5c8aRp7X9ADVHCnSuQFQV9AVeFSR ffAw== X-Gm-Message-State: AOAM5329tcZbpRWWfb0hMyJllp+cyYoGHGk7+GbwqT0DOcsPPe6dlJAq f6AazH5lHQt+59N1dUFhZ+ozFa+riwo= X-Google-Smtp-Source: ABdhPJxq+bPmbeZTWR5jTc4mX1TdA2AS5/dmztQeM3lRVRIRe3hWtALGuHimfUnMJnG4jI8RB+qRcA== X-Received: by 2002:a63:c142:: with SMTP id p2mr36773248pgi.576.1639089477923; Thu, 09 Dec 2021 14:37:57 -0800 (PST) Received: from squeak.grove.modra.org (158.106.96.58.static.exetel.com.au. [58.96.106.158]) by smtp.gmail.com with ESMTPSA id f8sm705475pfc.77.2021.12.09.14.37.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 09 Dec 2021 14:37:57 -0800 (PST) Received: by squeak.grove.modra.org (Postfix, from userid 1000) id 92A481140496; Fri, 10 Dec 2021 09:07:54 +1030 (ACDT) Date: Fri, 10 Dec 2021 09:07:54 +1030 From: Alan Modra To: Jim Wilson Cc: binutils@sourceware.org Subject: Re: Don't compile some opcodes files when bfd is 32-bit only Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-3032.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: binutils@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Binutils mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2021 22:38:00 -0000 On Thu, Dec 09, 2021 at 02:05:54PM -0800, Jim Wilson wrote: > On Thu, Dec 2, 2021 at 2:02 PM Alan Modra via Binutils < > binutils@sourceware.org> wrote: > > > Reverting the opcodes Makefile changes will currently result in > > opcodes failing to link. The riscv opcodes objects now depend on > > riscv bfd objects that are only compiled for a 64-bit bfd. > > > > Nelson Chu submitted a patch Nov 12 to fix 32-bit riscv32 builds, but at > the time the patch didn't seem necessary. I think this should be > revisited. I think this patch would fix some of these issues people are > having with 32-bit enable-targets=all builds. > https://sourceware.org/pipermail/binutils/2021-November/118498.html I am of course fine with a patch that makes it possible for a 32-bit objdump to disassemble riscv object files. What I'd like to avoid is compiling useless code into libopcodes. It's not just a matter of being able to build binutils/sim but also for bfd to recognise and opcodes to disassemble the target object files. (I haven't tried out Nelson's patch, this is a general comment not one specific to the patch.) -- Alan Modra Australia Development Lab, IBM