From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Woodrow Douglass <wdouglass@carnegierobotics.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] package/chicken: move literals into text section for xtensa architecture
Date: Fri, 2 Aug 2024 19:43:15 +0200 [thread overview]
Message-ID: <20240802194315.2de20808@windsurf> (raw)
In-Reply-To: <CAMo8BfK7FSn8imzqjTW8BLS7mPk6HLTKvCM4aBFaJw93z-ZpmQ@mail.gmail.com>
Hello Max,
On Fri, 2 Aug 2024 10:24:20 -0700
Max Filippov <jcmvbkbc@gmail.com> wrote:
> > ++ifeq ($(ARCH),xtensa)
> > ++C_COMPILER_OPTIONS += -mtext-section-literals
> > ++LINKER_OPTIONS += -mtext-section-literals
>
> There's a stronger version of this option, -mauto-litpools, in the xtensa
> TARGET_ABI and it is passed to the TARGET_CFLAGS. Why does
> this package need special treatment?
It causes build failures:
http://autobuild.buildroot.net/results/ce36170d67c4702f34bee025d8a46e5269c4573e/
There's some explanation from the patch contributor in the commit
message BTW:
This solves a build problem -- by default xtensa-gcc puts literals in a
different section of memory then the program text, and chicken is a very
literal-heavy program, so they don't all fit there. This avoids that problem.
Note: I'm not at all an expert with Xtensa, so I'd be happy to have
your input on this!
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-02 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 17:06 [Buildroot] [git commit] package/chicken: move literals into text section for xtensa architecture Thomas Petazzoni via buildroot
2024-08-02 17:24 ` Max Filippov
2024-08-02 17:43 ` Thomas Petazzoni via buildroot [this message]
2024-08-02 18:00 ` Max Filippov
2024-08-02 20:05 ` Thomas Petazzoni via buildroot
2024-08-05 15:47 ` Woody Douglass via buildroot
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=20240802194315.2de20808@windsurf \
--to=buildroot@buildroot.org \
--cc=jcmvbkbc@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=wdouglass@carnegierobotics.com \
/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