From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, jake@nvidia.com
Cc: Ard Biesheuvel <ardb@kernel.org>,
"rebecca@bsdio.com" <rebecca@bsdio.com>,
"gaoliming@byosoft.com.cn" <gaoliming@byosoft.com.cn>,
"bob.c.feng@intel.com" <bob.c.feng@intel.com>,
"yuwei.chen@intel.com" <yuwei.chen@intel.com>,
"ardb+tianocore@kernel.org" <ardb+tianocore@kernel.org>
Subject: Re: [edk2-devel] [PATCH] BaseTools/GenFw: Change opcode when converting ADR to ADRP
Date: Fri, 27 Oct 2023 15:12:46 +0100 [thread overview]
Message-ID: <CAKbZUD0B-LWFiWjAVPoZuniBNz3BUQqgWO827WmrU1f1QyFy=Q@mail.gmail.com> (raw)
In-Reply-To: <PH0PR12MB78889BE29EB9A39DA2848642ADDCA@PH0PR12MB7888.namprd12.prod.outlook.com>
On Fri, Oct 27, 2023 at 3:09 PM Jake Garver via groups.io
<jake=nvidia.com@groups.io> wrote:
>
> Hi Ard:
>
> > Can you double check the object file? I suspect this is a linker relaxation not a compiler issue.
>
> With LTO in play, is there a way to check the object file? It's not in aarch64 assembly.
Unless you pass -ffat-lto-objects, no. But, in the case of LTO, I
doubt we'll get many answers. LTO will significantly distort things
before doing the actual "link".
--
Pedro
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#110210): https://edk2.groups.io/g/devel/message/110210
Mute This Topic: https://groups.io/mt/102202314/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-10-27 14:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 15:31 [edk2-devel] [PATCH] BaseTools/GenFw: Change opcode when converting ADR to ADRP Jake Garver via groups.io
2023-10-26 18:46 ` Pedro Falcato
2023-10-27 12:44 ` Jake Garver via groups.io
2023-10-27 13:46 ` Ard Biesheuvel
2023-10-27 14:09 ` Jake Garver via groups.io
2023-10-27 14:12 ` Pedro Falcato [this message]
2023-10-27 14:13 ` Ard Biesheuvel
2023-10-27 14:26 ` Pedro Falcato
2023-10-27 14:43 ` Ard Biesheuvel
2023-10-27 15:52 ` Jake Garver via groups.io
2023-11-02 11:47 ` Jake Garver via groups.io
2023-11-02 12:47 ` Pedro Falcato
2023-12-06 16:51 ` Jake Garver via groups.io
2023-12-12 9:22 ` Ard Biesheuvel
2023-12-13 14:57 ` Jake Garver via groups.io
2023-12-13 17:31 ` Ard Biesheuvel
2023-12-13 18:01 ` Pedro Falcato
2023-12-13 19:47 ` Jake Garver via groups.io
2023-12-19 23:29 ` Jake Garver via groups.io
2023-12-20 7:34 ` Ard Biesheuvel
2023-10-27 14:10 ` Pedro Falcato
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKbZUD0B-LWFiWjAVPoZuniBNz3BUQqgWO827WmrU1f1QyFy=Q@mail.gmail.com' \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox