Re: [PATCH v2 1/1] BaseTools/tools_def: Add GCC49xASL Toolchain support

[Chris Co <Christopher.Co@microsoft.com>]

> -----Original Message-----
> From: Leif Lindholm <leif.lindholm@linaro.org>
> Sent: Monday, June 25, 2018 12:10 PM
> To: Chris Co <Christopher.Co@microsoft.com>
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>; edk2-devel@lists.01.org;
> Charles Garcia-Tobin <Charles.Garcia-Tobin@arm.com>
> Subject: Re: [edk2] [PATCH v2 1/1] BaseTools/tools_def: Add GCC49xASL
> Toolchain support
> 
> 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frelea
> >
> ses.linaro.org%2Farchive%2F14.09%2Fcomponents%2Ftoolchain%2Fbinaries
> %2
> > Fgcc-linaro-arm-none-eabi-4.9-
> 2014.09_win32.zip&amp;data=02%7C01%7CChr
> >
> istopher.Co%40microsoft.com%7Ca9d03e6d31b549abfc2808d5dacf49f1%7C7
> 2f98
> >
> 8bf86f141af91ab2d7cd011db47%7C1%7C0%7C636655506193987833&amp;sda
> ta=ZCa
> >
> 5y37luGBu2wG%2FUWUG2ZQ4Npts0JlXqS1AAZjgbZE%3D&amp;reserved=0
> > 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frelea
> >
> ses.linaro.org%2Farchive%2F14.09%2Fcomponents%2Ftoolchain%2Fbinaries
> %2
> > Fgcc-linaro-arm-none-eabi-4.9-
> 2014.09_win32.zip&amp;data=02%7C01%7CChr
> >
> istopher.Co%40microsoft.com%7Ca9d03e6d31b549abfc2808d5dacf49f1%7C7
> 2f98
> >
> 8bf86f141af91ab2d7cd011db47%7C1%7C0%7C636655506193987833&amp;sda
> ta=ZCa
> >
> 5y37luGBu2wG%2FUWUG2ZQ4Npts0JlXqS1AAZjgbZE%3D&amp;reserved=0
> > I would love to use GCC5 if toolchain exes are readily available for
> Windows.
> 
> We can do better than that:
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freleas
> es.linaro.org%2Fcomponents%2Ftoolchain%2Fbinaries%2F7.3-
> 2018.05%2Farm-eabi%2Fgcc-linaro-7.3.1-2018.05-i686-mingw32_arm-
> eabi.tar.xz&amp;data=02%7C01%7CChristopher.Co%40microsoft.com%7Ca9
> d03e6d31b549abfc2808d5dacf49f1%7C72f988bf86f141af91ab2d7cd011db47%
> 7C1%7C0%7C636655506193987833&amp;sdata=Xzo1HRrUAqyovKFyWCVXDa
> nTwaA7hKBhkFo14UzslGc%3D&amp;reserved=0
> Should build with GCC5 profile.
> 

Thanks Leif for the pointer!  There was some trepidation on using MinGW in the past, though admittedly I wasn't around when those decisions were made and it always confused me... Anyways, I will try out the GCC7.3 toolchain with the GCC5 profile.

> /
>     Leif