From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from esa4.mentor.iphmx.com (esa4.mentor.iphmx.com [68.232.137.252]) by sourceware.org (Postfix) with ESMTPS id EA4BE3858D3C for ; Mon, 27 Sep 2021 16:00:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org EA4BE3858D3C Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=codesourcery.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mentor.com IronPort-SDR: VnCQDiiJmTWc62KycrtpBau7WN4ECkSyRnmFVATXTZvegyzW9Gk1zhSNByWJujgL19sO2g+sgg f8iBoUsmZgvvUfVs7sVaSi9YtUINIMhAuF5JrSvNYWp4ysFgdODH6lKFup0J3cBjJ6caHIBet6 +wNA/OOCL2cb3go54/XtFnmDAcOj9lTJE+PJv3cix81tDuqCyP5YUJN8y4mS93QwZ2DoIivsIc As2ArwaKnfRRhrq4f3vjsh7aUB3sRgtuBJZeO7/+adCzst3+pEacHxm0Me9mdawWvKx1AaOzk1 rX0C94wqSDClJOTlzvDXIYWb X-IronPort-AV: E=Sophos;i="5.85,326,1624348800"; d="scan'208";a="66516922" Received: from orw-gwy-01-in.mentorg.com ([192.94.38.165]) by esa4.mentor.iphmx.com with ESMTP; 27 Sep 2021 08:00:47 -0800 IronPort-SDR: X6zb321dnxMT19CHvCnwyz+7+zn25NWJpti1rANJTYlUPVoZgVi3P5kGWpW/1ENACw4xs/HPFK Q2trhCvqmKwYCX0FJsZq25kduAcKZerkHQRPZjWHFDd+GDc2kH+9DStadWBq/DuSnzGjgIPUX7 U7zz5vXblmAb6Ff5S+clftRM8UVeb2KcbicKYpd+Z5mCkUq+WFp3xhWQAHoBibTAdkyqguuZRi eaXnVO/ZJaF1Z0St0nxJQxhZBtrfbGRc2Uy/6/J905fxkmRrLBFHPbmESPelCSU8aRdTxoTlMZ XZQ= Date: Mon, 27 Sep 2021 16:00:41 +0000 From: Joseph Myers X-X-Sender: jsm28@digraph.polyomino.org.uk To: Lukasz Majewski CC: Adhemerval Zanella , Florian Weimer , libc-alpha Subject: Re: [PATCH] dl: Use "adr" assembler command to get proper load address In-Reply-To: <20210926215830.2d7d2ea6@ktm> Message-ID: References: <20210907131616.23472-1-lukma@denx.de> <20210907164906.yt6nonvfyhvbrx6p@google.com> <20210907193227.6047f9cc@ktm> <20210907174417.sctsswphsyae4mpc@google.com> <20210908170524.4be44bf0@ktm> <16812ef5-e21b-ba69-7ee7-a0c5a094ad01@linaro.org> <20210908223421.3befe316@ktm> <20210909091806.25d6ac87@ktm> <20210909114936.318c22c8@ktm> <20210910121007.6b6bc81a@ktm> <20210917102918.49b2d79a@ktm> <20210926215830.2d7d2ea6@ktm> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Originating-IP: [137.202.0.90] X-ClientProxiedBy: svr-ies-mbx-02.mgc.mentorg.com (139.181.222.2) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-Spam-Status: No, score=-3118.1 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Sep 2021 16:00:50 -0000 On Sun, 26 Sep 2021, Lukasz Majewski wrote: > > QEMU only becomes relevant if you have a binary that works when > > executed on hardware but not on QEMU (or vice versa). > > > > (a) Do you have such a binary working on hardware but not on QEMU? > > Yes. I can run Beagle Bone generated image on the HW (without the fix), > but it breaks down on QEMU. If this is system QEMU emulation, that strongly suggests a QEMU bug, not a glibc bug - meaning you should find where the execution diverges between QEMU and hardware to identify the mis-emulated instruction. (For QEMU usermode emulation, different address space layout compared to running natively under the Linux kernel could be an issue.) -- Joseph S. Myers joseph@codesourcery.com