All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: backport xtensa trap pattern for 5.x
Date: Mon, 14 Nov 2016 22:55:53 +0100	[thread overview]
Message-ID: <20161114225553.0adf1094@free-electrons.com> (raw)
In-Reply-To: <1479117941-14895-1-git-send-email-jcmvbkbc@gmail.com>

Hello,

On Mon, 14 Nov 2016 02:05:41 -0800, Max Filippov wrote:
> gcc 5.x uses trap pattern extensively to mark locations where program
> execution should never get. Default pattern implementation emits a call
> to 'abort' function. This function however is not always available, e.g.
> it's not available for the libc dynamic linker. Backport implementation
> of the trap pattern for xtensa that does not result in a call to
> 'abort'.
> 
> Fixes:
>   http://autobuild.buildroot.net/results/0fbcc4475545904bf88f25a3bdf3ee552bf4960e
>   http://autobuild.buildroot.net/results/cb7f5bdfac615d774f3bcd1b802f8d74460bc557
>   http://autobuild.buildroot.net/results/cf3dc9ae4f74ff28b285f1a862b71d96384d7651
> 
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
>  .../5.4.0/875-xtensa-implement-trap-pattern.patch  | 67 ++++++++++++++++++++++
>  1 file changed, 67 insertions(+)
>  create mode 100644 package/gcc/5.4.0/875-xtensa-implement-trap-pattern.patch

Applied to master, thanks. However, I'm wondering if this backport
should also be done on gcc versions earlier than 5.x. Could you clarify
this point?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-11-14 21:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 10:05 [Buildroot] [PATCH] package/gcc: backport xtensa trap pattern for 5.x Max Filippov
2016-11-14 21:55 ` Thomas Petazzoni [this message]
2016-11-14 22:45   ` Thomas Petazzoni
2016-11-15  0:31   ` Max Filippov
2016-11-15 10:01     ` Thomas Petazzoni

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=20161114225553.0adf1094@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.