linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Changbin Du <changbin.du@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] init/Kconfig: make CC_OPTIMIZE_FOR_DEBUGGING visible only for GCC
Date: Sat, 10 Nov 2018 00:03:13 +0900	[thread overview]
Message-ID: <CAK7LNARFMPn2SN5vShCWX94UbTGF5WY6fjnVnS8ZFmFpXj-TpQ@mail.gmail.com> (raw)
In-Reply-To: <20181105151719.4552-1-changbin.du@gmail.com>

On Tue, Nov 6, 2018 at 12:18 AM Changbin Du <changbin.du@gmail.com> wrote:
>
> Currently CC_OPTIMIZE_FOR_DEBUGGING is only able to build with GCC.
> For clang, -Og optimization level could break kernel build. So make
> CC_OPTIMIZE_FOR_DEBUGGING visible only for GCC.
>
> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
> Signed-off-by: Changbin Du <changbin.du@gmail.com>
> ---

I squashed this into the previous patch in the kbuild tree.

Thanks!


>  init/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index 0fb9c0b5f1a1..d5fb0ee1400a 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -1107,6 +1107,7 @@ config CC_OPTIMIZE_FOR_SIZE
>
>  config CC_OPTIMIZE_FOR_DEBUGGING
>         bool "Optimize for better debugging experience (-Og)"
> +       depends on CC_IS_GCC
>         depends on $(cc-option,-Og)
>         select NO_AUTO_INLINE
>         help
> --
> 2.17.1
>


-- 
Best Regards
Masahiro Yamada

      reply	other threads:[~2018-11-09 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 15:17 [PATCH] init/Kconfig: make CC_OPTIMIZE_FOR_DEBUGGING visible only for GCC Changbin Du
2018-11-09 15:03 ` Masahiro Yamada [this message]

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=CAK7LNARFMPn2SN5vShCWX94UbTGF5WY6fjnVnS8ZFmFpXj-TpQ@mail.gmail.com \
    --to=yamada.masahiro@socionext.com \
    --cc=arnd@arndb.de \
    --cc=changbin.du@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).