From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] m68k: add special gcc flag to avoid ICE for coldfire
Date: Fri, 10 Mar 2017 10:23:54 +0100 [thread overview]
Message-ID: <20170310102354.6cb110c5@free-electrons.com> (raw)
In-Reply-To: <20161126085144.GA23223@waldemar-brodkorb.de>
Hello,
On Sat, 26 Nov 2016 09:51:44 +0100, Waldemar Brodkorb wrote:
> Fixes:
> http://autobuild.buildroot.net/results/d47fa41aa860d82471b83ac90967d3a3dacd8611
> http://autobuild.buildroot.net/results/a21de4747f40a5ce93108c8979fbc0277d040e79
>
> Requires this as prerequisite:
> http://patchwork.ozlabs.org/patch/683830/
>
> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
> Tested-by: Waldemar Brodkorb <wbx@openadk.org>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
We've added -fno-dwarf2-cfi-asm to 4 packages so far, and it seems to
have fixed the problem. So I would for now prefer to keep this as it is
today, and not use the wrapper to pass this flag to all packages.
I'll mark your patch as Rejected in patchwork, since it anyway cannot
be applied because Arnout patches have not been merged.
Let me know if you disagree, of course.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-03-10 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 8:51 [Buildroot] [PATCH] m68k: add special gcc flag to avoid ICE for coldfire Waldemar Brodkorb
2016-11-26 10:47 ` Arnout Vandecappelle
2016-11-27 15:27 ` Waldemar Brodkorb
2016-11-26 13:52 ` Thomas Petazzoni
2016-11-26 13:59 ` Arnout Vandecappelle
2016-11-26 14:12 ` Thomas Petazzoni
2016-12-11 14:51 ` Thomas Petazzoni
2016-12-11 20:38 ` Arnout Vandecappelle
2017-03-10 9:23 ` 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=20170310102354.6cb110c5@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