From: Jonathan Liu <net147@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] systemd: disable problematic GCC 5.2 optimizations
Date: Mon, 21 Sep 2015 22:31:35 +1000 [thread overview]
Message-ID: <55FFF8A7.1090809@gmail.com> (raw)
In-Reply-To: <CAJTo0LYjGD_u+Lj7DpMfGYXx55jbg1aQr_i06=kCQOWyJuu95g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
On 21/09/2015 10:23 PM, Burton, Ross wrote:
>
> On 21 September 2015 at 12:23, Jonathan Liu <net147@gmail.com
> <mailto:net147@gmail.com>> wrote:
>
> +FULL_OPTIMIZATION += "-fno-schedule-insns -fno-schedule-insns2"
>
>
> Are these bugs with the gcc optimisations or the systemd source code,
> and if its gcc's fault are the problematic optimisations specific to a
> particular architecture (such as ARM)? Just wondering if we can use
> overrides to only change the optimisations where they're a problem.
>
> Ross
I am not sure how to isolate if it's an issue in the systemd source code
but the issue is not present when using GCC 4.9.
Haven't checked if this is occuring on other architectures. Any feedback
whether this occurs on other platforms (Raspberry Pi 2 is ARMv7) is welcome.
Regards,
Jonathan
[-- Attachment #2: Type: text/html, Size: 1893 bytes --]
next prev parent reply other threads:[~2015-09-21 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 11:23 [PATCH] systemd: disable problematic GCC 5.2 optimizations Jonathan Liu
2015-09-21 12:23 ` Burton, Ross
2015-09-21 12:31 ` Jonathan Liu [this message]
2015-09-21 12:45 ` Adrian Freihofer
2015-09-21 12:49 ` Jonathan Liu
2015-09-21 13:53 ` Adrian Freihofer
2015-09-21 17:05 ` Khem Raj
2015-09-21 18:04 ` Jonathan Liu
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=55FFF8A7.1090809@gmail.com \
--to=net147@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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