From: vladimir.murzin@arm.com (Vladimir Murzin)
To: linux-arm-kernel@lists.infradead.org
Subject: [question] kernel build fails with O0 gcc optimization flag
Date: Wed, 25 Nov 2015 17:45:40 +0000 [thread overview]
Message-ID: <5655F3C4.2070503@arm.com> (raw)
In-Reply-To: <20151125171229.GA8415@yury-N73SV>
On 25/11/15 17:12, Yury Norov wrote:
> Hi all.
>
> I changed optimization from O2 to O0 in Makefile:
> 609 ifdef CONFIG_CC_OPTIMIZE_FOR_SIZE
> 610 KBUILD_CFLAGS += -Os $(call cc-disable-warning,maybe-uninitialized,)
> 611 else
> 612 KBUILD_CFLAGS += -O2 <-- here
> 613 endif
>
> And broke the build. O1 looks fine.
>
> I tried Ubuntu and Cavium GCC:
> gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu1)
> gcc version 5.2.0 (Cavium Development Version)
>
> Kernel is v4.3, defconfig, ARCH=arm64.
>
> What am I doing wrong?
Related -00 question has been recently discussed in [1]
[1] http://www.spinics.net/lists/arm-kernel/msg435802.html
Cheers
Vladimir
next prev parent reply other threads:[~2015-11-25 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 17:12 [question] kernel build fails with O0 gcc optimization flag Yury Norov
2015-11-25 17:45 ` Vladimir Murzin [this message]
2015-11-25 18:06 ` Russell King - ARM Linux
2015-11-25 19:56 ` Yury Norov
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=5655F3C4.2070503@arm.com \
--to=vladimir.murzin@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.