From: David Laight <david.laight.linux@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Uros Bizjak <ubizjak@gmail.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Artur Rojek <contact@artur-rojek.eu>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"D . Jeff Dionne" <jeff@coresemi.io>,
Rob Landley <rob@landley.net>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] sh: align .bss section padding to 8-byte boundary
Date: Thu, 13 Mar 2025 09:38:38 +0000 [thread overview]
Message-ID: <20250313093838.10749599@pumpkin> (raw)
In-Reply-To: <CAMuHMdXaw117mimN_7UgwbfbG9grVg09WfjKa2Lz4eGqM24EvA@mail.gmail.com>
On Wed, 12 Mar 2025 10:47:00 +0100
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> Hi Uros,
>
> On Wed, 12 Mar 2025 at 09:32, Uros Bizjak <ubizjak@gmail.com> wrote:
> > On Wed, Mar 12, 2025 at 9:22 AM John Paul Adrian Glaubitz
> > <glaubitz@physik.fu-berlin.de> wrote:
....
> > > OK. FWIW, do you understand what SBSS is for? I couldn't find any explanation
> > > for it.
> >
> > Small BSS section. The compiler can put data objects under a certain
> > size threshold to the .sbss section. Looking at GCC sh config, sh does
> > not use this section.
The .sbss (and .sdata) sections are used by some architectures (eg Nios2)
for data that can be accessed using a 16bit offset from a fixed register.
(Although using the register as global register variable generates better code.)
Historically they may have been used for data at the top/bottom of the
addresses space (for the same reason).
There is no reason to just use it for 'small' (eg 8 bytes or less)
data, that is just some empirical default.
I guess they could also be used on cpu like the strongarm for memory
that used the 'small data cache' (useful for screen buffer memory!).
David
next prev parent reply other threads:[~2025-03-13 9:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 17:55 [PATCH 0/2] J2 Turtle Board fixes Artur Rojek
2025-02-16 17:55 ` [PATCH 1/2] sh: align .bss section padding to 8-byte boundary Artur Rojek
2025-02-18 12:41 ` Rob Landley
2025-03-11 17:28 ` John Paul Adrian Glaubitz
2025-03-11 23:40 ` Artur Rojek
2025-03-12 8:06 ` Geert Uytterhoeven
2025-03-13 10:36 ` John Paul Adrian Glaubitz
2025-03-12 8:21 ` John Paul Adrian Glaubitz
2025-03-12 8:32 ` Uros Bizjak
2025-03-12 8:44 ` John Paul Adrian Glaubitz
2025-03-12 9:47 ` Geert Uytterhoeven
2025-03-12 9:55 ` Uros Bizjak
2025-03-13 9:38 ` David Laight [this message]
2025-04-05 17:38 ` John Paul Adrian Glaubitz
2025-02-16 17:55 ` [PATCH 2/2] irqchip: clocksource: fix jcore-pit irq request Artur Rojek
2025-02-17 7:14 ` Uros Bizjak
2025-02-18 12:43 ` Rob Landley
2025-02-19 14:43 ` Daniel Lezcano
2025-02-19 14:50 ` Geert Uytterhoeven
2025-02-19 14:52 ` Daniel Lezcano
2025-02-27 7:52 ` [PATCH 0/2] J2 Turtle Board fixes John Paul Adrian Glaubitz
2025-02-28 3:03 ` Rob Landley
2025-02-28 8:34 ` John Paul Adrian Glaubitz
2025-02-28 22:19 ` Rob Landley
2025-02-28 22:34 ` John Paul Adrian Glaubitz
2025-03-01 3:20 ` Rob Landley
2025-04-08 15:23 ` John Paul Adrian Glaubitz
2025-04-11 11:25 ` Rob Landley
2025-06-09 10:01 ` John Paul Adrian Glaubitz
2025-06-10 20:22 ` Rob Landley
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=20250313093838.10749599@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=contact@artur-rojek.eu \
--cc=dalias@libc.org \
--cc=daniel.lezcano@linaro.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jeff@coresemi.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rob@landley.net \
--cc=tglx@linutronix.de \
--cc=ubizjak@gmail.com \
--cc=ysato@users.sourceforge.jp \
/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