All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greentime Hu <green.hu@gmail.com>
To: Nickhu <nickhu@andestech.com>
Cc: Greentime <greentime@andestech.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, Zong Li <zong@andestech.com>,
	Vincent Chen <deanbo422@gmail.com>
Subject: Re: [PATCH 1/1] nds32: Fix gcc 8.0 compiler option incompatible.
Date: Fri, 19 Oct 2018 17:24:24 +0800	[thread overview]
Message-ID: <CAEbi=3fPg0pCFuRiizmU68r8_N4jC8ANVThf0kQXunkp+rOuNw@mail.gmail.com> (raw)
In-Reply-To: <6f54200ae5c132634ede74df536a547e134554c2.1539654583.git.nickhu@andestech.com>

Nickhu <nickhu@andestech.com> 於 2018年10月18日 週四 下午4:38寫道：
>
>         When the kernel configs of ftrace and frame pointer options are
> choosed, the compiler option of kernel will incompatible.
>         Error message:
>                 nds32le-linux-gcc: error: -pg and -fomit-frame-pointer are incompatible
>
> Signed-off-by: Nickhu <nickhu@andestech.com>
> Signed-off-by: Zong Li <zong@andestech.com>
> ---
>  arch/nds32/mm/Makefile | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/arch/nds32/mm/Makefile b/arch/nds32/mm/Makefile
> index 6b6855852223..7c5c15ad854a 100644
> --- a/arch/nds32/mm/Makefile
> +++ b/arch/nds32/mm/Makefile
> @@ -4,4 +4,8 @@ obj-y                           := extable.o tlb.o \
>
>  obj-$(CONFIG_ALIGNMENT_TRAP)   += alignment.o
>  obj-$(CONFIG_HIGHMEM)           += highmem.o
> -CFLAGS_proc-n13.o              += -fomit-frame-pointer
> +
> +ifdef CONFIG_FUNCTION_TRACER
> +CFLAGS_REMOVE_proc.o     = $(CC_FLAGS_FTRACE)
> +endif
> +CFLAGS_proc.o              += -fomit-frame-pointer
Hi Nick,

Thanks.
Acked-by: Greentime Hu <greentime@andestech.com>

      reply	other threads:[~2018-10-19  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18  8:37 [PATCH 0/1] nds32: Fix gcc 8.0 compiler option incompatible Nickhu
2018-10-18  8:37 ` [PATCH 1/1] " Nickhu
2018-10-19  9:24   ` Greentime Hu [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='CAEbi=3fPg0pCFuRiizmU68r8_N4jC8ANVThf0kQXunkp+rOuNw@mail.gmail.com' \
    --to=green.hu@gmail.com \
    --cc=arnd@arndb.de \
    --cc=deanbo422@gmail.com \
    --cc=greentime@andestech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickhu@andestech.com \
    --cc=zong@andestech.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 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.