[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cb1d47ddc86ad1b2235dbd430fed28f6d6cd1c80.camel@physik.fu-berlin.de>
Date: Thu, 13 Mar 2025 11:36:21 +0100
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: Geert Uytterhoeven <geert@...ux-m68k.org>, Artur Rojek
<contact@...ur-rojek.eu>
Cc: Yoshinori Sato <ysato@...rs.sourceforge.jp>, Rich Felker
<dalias@...c.org>, Daniel Lezcano <daniel.lezcano@...aro.org>, Thomas
Gleixner <tglx@...utronix.de>, Uros Bizjak <ubizjak@...il.com>, "D . Jeff
Dionne" <jeff@...esemi.io>, Rob Landley <rob@...dley.net>,
linux-sh@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] sh: align .bss section padding to 8-byte boundary
Hi Geert,
On Wed, 2025-03-12 at 09:06 +0100, Geert Uytterhoeven wrote:
> What about moving (or duplicating, e.g. sbss_align alignment is
> done before and after __bss_start) the stop_align alignment
> from BSS_SECTION() into BSS() instead, i.e. just changing
> include/asm-generic/vmlinux.lds.h for everyone? I don't think that
> would hurt any platforms, while fixing the issue for good.
> IMHO it is a bit strange that the size of the bss section can differ
> from __bss_stop - __bss_start.
This sounds reasonable. Could you send a patch? I assume that would go
through a different tree as we're touching generic code.
> One last question though: what about sbss? How does the TurtleBoard
> loader handle that? __bss_stop - __bss_start is not the size of bss,
> but the sum of the sizes of sbss and bss, plus extra alignment in
> between. The latter might cause trouble, too.
Does the compiler actually generate the SBSS section on SH?
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Powered by blists - more mailing lists