From: Leif Lindholm <leif.lindholm@linaro.org>
To: Chris Co <Christopher.Co@microsoft.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Charles Garcia-Tobin <Charles.Garcia-Tobin@arm.com>
Subject: Re: [PATCH v2 1/1] BaseTools/tools_def: Add GCC49xASL Toolchain support
Date: Mon, 25 Jun 2018 20:10:12 +0100 [thread overview]
Message-ID: <20180625191012.vx7ntwkdmjiaspol@bivouac.eciton.net> (raw)
In-Reply-To: <DM5PR2101MB11285765EC9702660CCC7678944A0@DM5PR2101MB1128.namprd21.prod.outlook.com>
On Mon, Jun 25, 2018 at 06:21:27PM +0000, Chris Co wrote:
> > >-----Original Message-----
> > >From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
> > >Sent: Monday, June 25, 2018 3:34 PM
> > >To: Gao, Liming <liming.gao@intel.com>
> > >Cc: Chris Co <Christopher.Co@microsoft.com>; edk2-devel@lists.01.org;
> > >Leif Lindholm <leif.lindholm@linaro.org>; Charles Garcia-Tobin
> > ><Charles.Garcia- Tobin@arm.com>
> > >Subject: Re: [edk2] [PATCH v2 1/1] BaseTools/tools_def: Add GCC49xASL
> > >Toolchain support
> > >
> > >(+ Charles)
> > >
> > >On 25 June 2018 at 03:38, Gao, Liming <liming.gao@intel.com> wrote:
> > >> Chris:
> > >> GCC 4.9 targeting arm-none-eabi. This GCC4.9 should run in Windows
> > OS.
> > >So, could you give some info where windows GCC49 is from.
> > >>
>
> We get Windows GCC49 from linaro: https://releases.linaro.org/archive/14.09/components/toolchain/binaries/gcc-linaro-arm-none-eabi-4.9-2014.09_win32.zip
> Make comes from MinGW
>
> > >
> > >OK, so first of all, could you elaborate on why we need a different ASL
> > >compiler? We have spent the past 5 years in conference calls and
> > >meeting rooms to standardize ACPI on ARM, so I am rather disappointed
> > >that we have this discrepancy.
> > >
> > >Then, could you explain why you chose GCC49? We have GCC5 now as well,
> > >which enables LTO and generally results in smaller code. Also, is there
> > >any way we could parameterize the existing GCCx toolchains to allow a
> > >different ASL compiler to be selected?
> > >
>
> We are using GCC49 because this was the last GCC build for Windows as exe we could find. We use these tools to build using GCC on Windows: https://releases.linaro.org/archive/14.09/components/toolchain/binaries/gcc-linaro-arm-none-eabi-4.9-2014.09_win32.zip
> I would love to use GCC5 if toolchain exes are readily available for Windows.
We can do better than that:
https://releases.linaro.org/components/toolchain/binaries/7.3-2018.05/arm-eabi/gcc-linaro-7.3.1-2018.05-i686-mingw32_arm-eabi.tar.xz
Should build with GCC5 profile.
/
Leif
next prev parent reply other threads:[~2018-06-25 19:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 0:57 [PATCH v2 0/1] BaseTools/tools_def: Add GCC49xASL Toolchain support Chris Co
2018-06-23 0:57 ` [PATCH v2 1/1] " Chris Co
2018-06-25 1:38 ` Gao, Liming
2018-06-25 7:33 ` Ard Biesheuvel
2018-06-25 8:15 ` Gao, Liming
2018-06-25 18:21 ` Chris Co
2018-06-25 19:10 ` Leif Lindholm [this message]
2018-06-25 19:50 ` Chris Co
2018-06-26 4:40 ` Gao, Liming
2018-06-26 8:22 ` Ard Biesheuvel
2018-06-26 18:42 ` Chris Co
2018-06-26 18:51 ` Ard Biesheuvel
2018-06-27 4:14 ` Chris Co
2018-06-27 5:07 ` Ard Biesheuvel
2018-06-29 3:49 ` Chris Co
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=20180625191012.vx7ntwkdmjiaspol@bivouac.eciton.net \
--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