From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/syslogd: workaround a compiler bug with CS powerpc 2012.03
Date: Fri, 19 Feb 2016 23:38:49 +0100 [thread overview]
Message-ID: <56C79979.9080604@gmail.com> (raw)
In-Reply-To: <8760xonw41.fsf@dell.be.48ers.dk>
Hi Peter,
Le 16/02/2016 23:11, Peter Korsgaard a ?crit :
>>>>>> "Romain" == Romain Naour <romain.naour@gmail.com> writes:
> > The O3 optimization triggers a compiler bug with this toolchain,
> > change it with 02.
>
> > Fixes:
> > http://autobuild.buildroot.net/results/2fb/2fb94ecfdc32761a09da35e6fcbdd512847ec911
>
> > Signed-off-by: Romain Naour <romain.naour@gmail.com>
> > ---
> > package/sysklogd/sysklogd.mk | 8 ++++++++
> > 1 file changed, 8 insertions(+)
>
> > diff --git a/package/sysklogd/sysklogd.mk b/package/sysklogd/sysklogd.mk
> > index de2edf4..9e315bc 100644
> > --- a/package/sysklogd/sysklogd.mk
> > +++ b/package/sysklogd/sysklogd.mk
> > @@ -14,6 +14,14 @@ ifeq ($(BR2_PACKAGE_BUSYBOX),y)
> > SYSKLOGD_DEPENDENCIES = busybox
> > endif
>
> > +# CS PowerPC 2012.03 triggers compiler bug.
> > +ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_POWERPC_E500V2),y)
> > +define SYSKLOGD_WORKAROUND_COMPILER_BUG
> > + $(SED) 's/-O3/-O2/' $(@D)/Makefile
>
> Does this mean that sysklogd isn't using our TARGET_CFLAGS (where we
> most likely pass -Os)?
-O3 is added by SKFLAGS variable which is used as CFLAGS.
TARGET_CFLAGS is not taken into account :-/
>
> Why don't we fix that instead?
We could try to replace SKFLAGS by CFLAGS...
Best regards,
Romain
>
>
next prev parent reply other threads:[~2016-02-19 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 10:55 [Buildroot] [PATCH] package/syslogd: workaround a compiler bug with CS powerpc 2012.03 Romain Naour
2016-02-14 20:51 ` Thomas Petazzoni
2016-02-16 22:11 ` Peter Korsgaard
2016-02-19 22:38 ` Romain Naour [this message]
2016-02-20 9:21 ` Peter Korsgaard
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=56C79979.9080604@gmail.com \
--to=romain.naour@gmail.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