From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: nios2 Backport nios2 r31 fix
Date: Sun, 9 Oct 2016 14:05:46 +0200 [thread overview]
Message-ID: <20161009140546.223f5049@free-electrons.com> (raw)
In-Reply-To: <1475934412-29919-1-git-send-email-romain.naour@gmail.com>
Hello,
On Sat, 8 Oct 2016 15:46:52 +0200, Romain Naour wrote:
> As reported on the mailing list, gcc5 with binutils 2.26.1 produce some
> assembler error "r31 cannot be used with jmp; use ret instead" [1]
>
> The bug is reported upstream [2], but gcc 5.4 needs an upstream patch to
> fix this issue.
>
> Note: openembedded backported the same patch for gcc 5.3 [3]
>
> [1] http://lists.busybox.net/pipermail/buildroot/2016-September/172932.html
> [2] https://sourceware.org/bugzilla/show_bug.cgi?id=20674
> [3] http://lists.openembedded.org/pipermail/openembedded-core/2016-February/117633.html
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
> .../5.4.0/880-gcc-nios2-Add-IJMP_REGS-enum.patch | 103 +++++++++++++++++++++
> 1 file changed, 103 insertions(+)
> create mode 100644 package/gcc/5.4.0/880-gcc-nios2-Add-IJMP_REGS-enum.patch
Applied to master after adding the references to the autobuilder
failures.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-09 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 13:46 [Buildroot] [PATCH] package/gcc: nios2 Backport nios2 r31 fix Romain Naour
2016-10-08 13:56 ` Romain Naour
2016-10-09 12:05 ` Thomas Petazzoni [this message]
2016-10-09 20:14 ` Romain Naour
2016-10-09 20:20 ` Thomas Petazzoni
2016-10-09 20:24 ` Romain Naour
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=20161009140546.223f5049@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