public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "Qi.Chen@windriver.com" <Qi.Chen@windriver.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH V2] lib32-64k-pagesize.inc: add conf for building 32bit binary with 64K alignment
Date: Wed, 8 Jan 2025 18:18:30 +0000	[thread overview]
Message-ID: <2EC4D86A-7376-43B8-A066-377EAEE49932@arm.com> (raw)
In-Reply-To: <7008933E-1611-4683-86A2-083772D4CE71@arm.com>



> On 8 Jan 2025, at 17:02, Ross Burton via lists.openembedded.org <ross.burton=arm.com@lists.openembedded.org> wrote:
> First, I should point out that changing the page size is an ABI break, and the 32-bit ABI was formalised long before 64kb pages were a thing, so things _will_ break.  That said the loader should work, as a decade ago binutils 2.25 changed the alignment to 64kb pages by default:
> 
> https://sourceware.org/git/?p=binutils-gdb.git;a=blobdiff;f=ld/emulparams/armelf_linux.sh;h=280db842208e06e3231ec3a8322369193630a07d;hp=35891f1fc91bddd03677aaefd7146ae5333e6cf0;hb=7572ca8989ead4c3425a1500bc241eaaeffa2c89;hpb=8335d6aa34b88ce31b62e1b578d54ab4aa364435

Which was subsequently effectively reverted:

https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=1a26a53a0dee39106ba58fcb15496c5f13074652

Fun times.

Ross

  reply	other threads:[~2025-01-08 18:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25  3:04 [OE-core][PATCH V2] lib32-64k-pagesize.inc: add conf for building 32bit binary with 64K alignment Qi.Chen
2025-01-08 17:02 ` Ross Burton
2025-01-08 18:18   ` Ross Burton [this message]
2025-01-09  1:54   ` Chen, Qi
2025-01-16  4:34     ` Chen, Qi
     [not found]     ` <181B122FF6A5F825.28670@lists.openembedded.org>
2025-01-22  3:02       ` ChenQi
2025-01-22  4:18         ` Khem Raj
2025-01-22  4:52           ` ChenQi
2025-01-22  5:01             ` Khem Raj

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-all 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=2EC4D86A-7376-43B8-A066-377EAEE49932@arm.com \
    --to=ross.burton@arm.com \
    --cc=Qi.Chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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