From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: fix xtensa gas segfault with --text-section-literals
Date: Sat, 11 Jul 2015 12:33:31 +0200 [thread overview]
Message-ID: <20150711123331.03f9c605@free-electrons.com> (raw)
In-Reply-To: <1432628640-29876-1-git-send-email-jcmvbkbc@gmail.com>
Dear Max Filippov,
On Tue, 26 May 2015 11:24:00 +0300, Max Filippov wrote:
> Building libgcc with TARGET_ABI flags results in assembler segfault on
> xtensa, because code in sections .init and .fini emits literals w/o
> .literal_position directive. This patch turns the segfault into assembly
> error.
>
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
> ...x-gas-segfault-with-text-section-literals.patch | 56 ++++++++++++++++++++++
> ...x-gas-segfault-with-text-section-literals.patch | 56 ++++++++++++++++++++++
> ...x-gas-segfault-with-text-section-literals.patch | 56 ++++++++++++++++++++++
> ...x-gas-segfault-with-text-section-literals.patch | 56 ++++++++++++++++++++++
> 4 files changed, 224 insertions(+)
> create mode 100644 package/binutils/2.22/912-xtensa-fix-gas-segfault-with-text-section-literals.patch
> create mode 100644 package/binutils/2.23.2/912-xtensa-fix-gas-segfault-with-text-section-literals.patch
> create mode 100644 package/binutils/2.24/912-xtensa-fix-gas-segfault-with-text-section-literals.patch
> create mode 100644 package/binutils/2.25/912-xtensa-fix-gas-segfault-with-text-section-literals.patch
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-11 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 8:24 [Buildroot] [PATCH] binutils: fix xtensa gas segfault with --text-section-literals Max Filippov
2015-07-11 10:33 ` Thomas Petazzoni [this message]
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=20150711123331.03f9c605@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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