From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-10-10
Date: Fri, 11 Oct 2013 16:57:40 +0200 [thread overview]
Message-ID: <20131011165740.0ab665cc@skate> (raw)
In-Reply-To: <CAAXf6LUAR7P6mEwFEoeCHMq0KX_8P3LQVQvte_VvN=OTCr9T=g@mail.gmail.com>
Dear Thomas De Schampheleire,
On Fri, 11 Oct 2013 16:51:29 +0200, Thomas De Schampheleire wrote:
> > Should this be done only for the SuperH architecture? Only for the
> > affected external toolchains?
>
> Not sure what the best approach is. Checking just for the architecture
> is the simplest.
>
> Checking on the toolchain is complex:
> - for the Sourcery toolchains: the problem shows with the most recent
> SuperH toolchain we support at the moment, so I don't think it's worth
> trying to avoid -O2 on older toolchains than that.
>
> - for other external, or internal toolchains, we can't predict whether
> the problem would show (I don't know which combinations of gcc, libc,
> ... are the killer)
>
> What do you think?
Just do it for SuperH as a whole, with a nice comment on top of this
line. That's the easiest way.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-11 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-10-10 Thomas Petazzoni
2013-10-11 7:59 ` Lionel Orry
2013-10-11 14:30 ` Thomas De Schampheleire
2013-10-11 14:31 ` Thomas Petazzoni
2013-10-11 14:43 ` Lionel Orry
2013-10-11 14:51 ` Thomas De Schampheleire
2013-10-11 14:57 ` Thomas Petazzoni [this message]
2013-10-11 14:41 ` Lionel Orry
2013-10-11 14:52 ` Thomas De Schampheleire
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=20131011165740.0ab665cc@skate \
--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