From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ptpd2: fix bfin compile by avoiding gcc bug
Date: Tue, 22 Nov 2016 11:12:20 +0100 [thread overview]
Message-ID: <20161122101219.GT27313@waldemar-brodkorb.de> (raw)
In-Reply-To: <20161121220442.77263bd3@free-electrons.com>
Hi Thomas,
Thomas Petazzoni wrote,
> Hello,
>
> On Mon, 21 Nov 2016 19:32:18 +0100, Waldemar Brodkorb wrote:
>
> > +# GCC bug with Os/O1/O2/O3
> > +# internal compiler error: in gen_add2_insn, at optabs.c:4454
> > +ifeq ($(BR2_bfin),y)
> > +PTPD2_CONF_ENV += CFLAGS="-O0"
>
> You forgot to pass $(TARGET_CFLAGS) here. With your change, we loose
> TARGET_CFLAGS. So I've fixed that up and applied.
>
> However, I continue to dislike such hacks: when the problem gets fixed
> by gcc, how will we notice?
Either when we get notice that the PR is closed, this time I need to
create one. But we have similar issues where we already have PR's.
Or we check when a new gcc release come out, if the results from
"grep bfin package/*/*mk" are still required.
I think better then never ending autobuild failures.
best regards
Waldemar
next prev parent reply other threads:[~2016-11-22 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 18:32 [Buildroot] [PATCH] ptpd2: fix bfin compile by avoiding gcc bug Waldemar Brodkorb
2016-11-21 21:04 ` Thomas Petazzoni
2016-11-22 10:12 ` Waldemar Brodkorb [this message]
2016-11-22 10:16 ` 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=20161122101219.GT27313@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