From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH 0/3] fixes for CLANG35 on ARM
Date: Thu, 13 Dec 2018 11:49:12 +0100 [thread overview]
Message-ID: <CAKv+Gu8hUciCxw_XUvycBaug+a3UmG7kKvDY236p9HzBXv+=eA@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu-RRasJQ6SGgyteHPVJ=MhV_-Qtv_Tt7Yxy62_3ruJvRQ@mail.gmail.com>
On Wed, 12 Dec 2018 at 15:19, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>
> On Wed, 12 Dec 2018 at 15:19, Gao, Liming <liming.gao@intel.com> wrote:
> >
> > Make sense. So, CLANG35 tool chain can also be used by CLANG 3.5 and above version compiler, like GCC49?
> >
>
> Exactly
>
Liming,
Are you happy with the MdePkg and BaseTools changes in this series?
next prev parent reply other threads:[~2018-12-13 10:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 10:33 [PATCH 0/3] fixes for CLANG35 on ARM Ard Biesheuvel
2018-12-12 10:33 ` [PATCH 1/3] MdePkg/BaseMemoryLibOptDxe ARM: add missing function annotations Ard Biesheuvel
2018-12-12 11:48 ` Laszlo Ersek
2018-12-12 10:33 ` [PATCH 2/3] BaseTools/tools_def ARM CLANG35: work around -mno-movt option name change Ard Biesheuvel
2018-12-12 11:49 ` Laszlo Ersek
2018-12-12 11:51 ` Ard Biesheuvel
2018-12-12 12:04 ` Laszlo Ersek
2018-12-12 12:30 ` Ard Biesheuvel
2018-12-12 12:34 ` Leif Lindholm
2018-12-12 10:33 ` [PATCH 3/3] ArmVirtPkg/PrePi ARM CLANG35: drop incompatible command line option Ard Biesheuvel
2018-12-12 11:51 ` Laszlo Ersek
2018-12-12 12:37 ` [PATCH 0/3] fixes for CLANG35 on ARM Leif Lindholm
2018-12-12 14:01 ` Gao, Liming
2018-12-12 14:02 ` Ard Biesheuvel
2018-12-12 14:19 ` Gao, Liming
2018-12-12 14:19 ` Ard Biesheuvel
2018-12-13 10:49 ` Ard Biesheuvel [this message]
2018-12-13 11:42 ` Gao, Liming
2018-12-13 11:49 ` Ard Biesheuvel
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+Gu8hUciCxw_XUvycBaug+a3UmG7kKvDY236p9HzBXv+=eA@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