From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 85819 invoked by alias); 9 Feb 2020 16:34:13 -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 85811 invoked by uid 89); 9 Feb 2020 16:34:13 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=2.2 required=5.0 tests=AWL,BAYES_00,KAM_COUK autolearn=no version=3.3.1 spammy=H*MI:local, HX-Languages-Length:545, H*M:local, gary X-HELO: ezhosts.net Received: from ezhosts.net (HELO ezhosts.net) (185.40.20.55) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 09 Feb 2020 16:34:11 +0000 Received: from localhost (localhost [127.0.0.1]) by ezhosts.net (Postfix) with ESMTP id 7FCBFBC53C for ; Sun, 9 Feb 2020 17:33:53 +0100 (CET) Received: from ezhosts.net ([127.0.0.1]) by localhost (ezhosts.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id DtJk5EISg3x1 for ; Sun, 9 Feb 2020 17:33:37 +0100 (CET) Received: from remote.partis.co.uk (unknown [94.7.195.121]) (Authenticated sender: postmaster@ezhosts.net) by ezhosts.net (Postfix) with ESMTPSA id 2F1D1BC538 for ; Sun, 9 Feb 2020 17:33:37 +0100 (CET) Received: from SERVER.partis.local ([fe80::206d:c9d1:9e38:c7c1]) by SERVER.partis.local ([fe80::206d:c9d1:9e38:c7c1%10]) with mapi id 14.01.0438.000; Sun, 9 Feb 2020 16:33:20 +0000 From: Gary Partis To: "binutils@sourceware.org" Subject: Linker --fix-v4bx problem Date: Sun, 09 Feb 2020 16:34:00 -0000 Message-ID: <6773ED2626D769428AEACF6C2B03437185F2671E@SERVER.partis.local> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00126.txt.bz2 Hello I am using GNU ld version 2.31.1 to target ARMv3 (ARM610/710) processors. P= rimarily, GCC's libgcc contains "BX LR" instructions which we want changed = to "MOV PC,LR" so to be compatible with older processors, but after running= the linker with the "--fix-vxb4" directive the BX instructions are still t= here (we use objdump to disassemble the resultant ELF file to check). Are we missing something really obvious or is the "--fix-v4bx" directive br= oken in some way? Thanks in advance. Kind regards Gary Partis