From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] m68k: add special gcc flag to avoid ICE for coldfire
Date: Sun, 27 Nov 2016 16:27:50 +0100 [thread overview]
Message-ID: <20161127152750.GE14207@waldemar-brodkorb.de> (raw)
In-Reply-To: <30093dc7-15f9-144b-77c3-e5f2236019a4@mind.be>
Hi Arnout,
Arnout Vandecappelle wrote,
> On 26-11-16 09:51, Waldemar Brodkorb wrote:
> > Fixes:
> > http://autobuild.buildroot.net/results/d47fa41aa860d82471b83ac90967d3a3dacd8611
> > http://autobuild.buildroot.net/results/a21de4747f40a5ce93108c8979fbc0277d040e79
>
> Did you test whether exception handling still works?
Tested with attached C++ app.
Before and after the patches.
> > Requires this as prerequisite:
> > http://patchwork.ozlabs.org/patch/683830/
> >
> > Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
>
> Not sure if this warrants a Sob from me, but OK.
>
> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Will you provide the bigger patch Thomas wants to have?
best regards
Waldemar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: foo.cc
Type: text/x-c++src
Size: 2835 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20161127/64501825/attachment.cc>
next prev parent reply other threads:[~2016-11-27 15:27 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 [this message]
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
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=20161127152750.GE14207@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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