From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 118878 invoked by alias); 19 Feb 2020 04:26:53 -0000 Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org Received: (qmail 118869 invoked by uid 89); 19 Feb 2020 04:26:53 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_INFOUSMEBIZ,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.1 spammy=selfish, Feel, HX-Languages-Length:1342, H*Ad:U*pinskia X-HELO: mail-pf1-f196.google.com Received: from mail-pf1-f196.google.com (HELO mail-pf1-f196.google.com) (209.85.210.196) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 19 Feb 2020 04:26:51 +0000 Received: by mail-pf1-f196.google.com with SMTP id p14so11829421pfn.4 for ; Tue, 18 Feb 2020 20:26:51 -0800 (PST) Return-Path: Received: from localhost ([2601:647:4b01:ae80::51fb]) by smtp.gmail.com with ESMTPSA id t8sm494338pjy.20.2020.02.18.20.26.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 18 Feb 2020 20:26:48 -0800 (PST) Date: Wed, 19 Feb 2020 04:26:00 -0000 From: Fangrui Song To: "Maciej W. Rozycki" Cc: Andrew Pinski , binutils Subject: Re: [MIPS] Can we have R_MIPS_PC64? Message-ID: <20200219042647.rw2fdnb7gbtbmzbz@google.com> References: <20200205071944.tberxwpcrkhnat4h@gmail.com> <20200208183958.v4vfdtfstlwtod3p@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-SW-Source: 2020-02/txt/msg00442.txt.bz2 On 2020-02-17, Maciej W. Rozycki wrote: >On Sat, 8 Feb 2020, Fangrui Song wrote: > >> I hope someone can add back R_MIPS_PC64. > > You don't need R_MIPS_PC64. You can yield the same effect the usual >MIPS64 way, that is by composing R_MIPS_PC32 with R_MIPS_64 (similarly to >e.g. how R_MIPS_REL32 composes with R_MIPS_64). > > Of course the toolchain may not as it stands support this composition. >Feel free to post patches to take care of your use case. > > HTH, > > Maciej Thank you for your comments. Sorry that I cannot create a patch, as I know very little about MIPS. I raised these MIPS issues (including the recent DT_MIPS_XHASH https://sourceware.org/ml/binutils/2020-01/msg00451.html) not because I have anything to do with MIPS. I started the threads from the viewpoint of a toolchain maintainer. I noticed MIPS introduced complexity in a number of areas, where other architectures can share a simple common implementation. (It is weird that .quad foo - . is not representable on MIPS64.) For my own selfish purposes, I will be sad if someone wants to add some peculiar MIPS features (e.g. DT_MIPS_XHASH) to LLVM binary utilities or lld. I hope we can get rid of things like https://reviews.llvm.org/D72228 at some point. I hope someone can implement PC64, or something similar for MIPS.