From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Michael Zimmermann <sigmaepsilon92@gmail.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Cohen, Eugene" <eugene@hp.com>
Subject: Re: [PATCH 3/3] BaseTools GCC/ARM: add -fno-builtin to CC flags
Date: Fri, 5 Aug 2016 16:34:11 +0200 [thread overview]
Message-ID: <CAKv+Gu_+TyVdYipy0Kv1AKNB4a8+M1gT9xFiSrxiuJjbksJ51Q@mail.gmail.com> (raw)
In-Reply-To: <CAN9vWDJoe8kGqRn3j00N=KP0UaL7SgzTvHG+WjZi+8CO9uYPig@mail.gmail.com>
On 4 August 2016 at 18:01, Michael Zimmermann <sigmaepsilon92@gmail.com> wrote:
> not directly related but could we add nostdinc too? At least for my platform
> that works perfectly and it prevents you from accidentally including any
> libc/libgcc/whatever headers from your toolchain.(nostdlib is already
> enabled)
>
That sounds like a sensible idea, yes.
next prev parent reply other threads:[~2016-08-05 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 14:42 [PATCH 0/3] Build fixes for ARM/OpenSSL Ard Biesheuvel
2016-08-04 14:42 ` [PATCH 1/3] ArmPkg/ArmSoftFloatLib: disable LTO build for GCC Ard Biesheuvel
2016-08-06 14:18 ` Michael Zimmermann
2016-08-06 14:42 ` Ard Biesheuvel
2016-08-06 14:53 ` Michael Zimmermann
2016-08-07 9:28 ` Michael Zimmermann
2016-08-07 10:29 ` Ard Biesheuvel
2016-08-04 14:42 ` [PATCH 2/3] ArmPkg/CompilerIntrinsicsLib: make the default memset() weak Ard Biesheuvel
2016-08-04 14:42 ` [PATCH 3/3] BaseTools GCC/ARM: add -fno-builtin to CC flags Ard Biesheuvel
2016-08-04 16:01 ` Michael Zimmermann
2016-08-05 14:34 ` Ard Biesheuvel [this message]
2016-08-05 14:26 ` Gao, Liming
2016-08-05 14:33 ` Ard Biesheuvel
2016-08-05 12:53 ` [PATCH 0/3] Build fixes for ARM/OpenSSL Leif Lindholm
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-list 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=CAKv+Gu_+TyVdYipy0Kv1AKNB4a8+M1gT9xFiSrxiuJjbksJ51Q@mail.gmail.com \
--to=devel@edk2.groups.io \
/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