Re: 回复: 回复: [edk2-devel] [PATCH v2 00/13] BaseTools,CryptoPkg,MdePkg,OvmfPkg: Delete CLANG35,CLANG38,GCC48,GCC49, rename GCC5 to GCC, update CLANGDWARF, delete VS 2008-2013, EBC

["Rebecca Cran" <rebecca@bsdio.com>]

Thanks, deprecating it for a while makes a lot of sense. We can consider 
removing it in 6-12 months maybe?


-- 

Rebecca Cran


On 4/4/2023 12:29 PM, Kinney, Michael D wrote:
> Add GCC and leave GCC5 for now and give time for all downstream
> consumers to accommodate the name change.
>
> At a later date, remove GCC5.
>
> We have seen significant downstream issues on name changes in the
> past.  Splitting into 2 different patch series allows downstream
> to merge in the change that adds the new name.  Give time to update
> all dependencies to use the new name, and then at a later date
> remove the old name.
>
> This is a common practice to announce deprecation and support
> new and old for a period of time.
>
> Mike
>
>> -----Original Message-----
>> From: Rebecca Cran <rebecca@bsdio.com>
>> Sent: Tuesday, April 4, 2023 11:04 AM
>> To: Pedro Falcato <pedro.falcato@gmail.com>; Kinney, Michael D <michael.d.kinney@intel.com>
>> Cc: devel@edk2.groups.io; Leif Lindholm <quic_llindhol@quicinc.com>; Gao, Liming <gaoliming@byosoft.com.cn>; Oliver Smith-
>> Denny <osd@smith-denny.com>; Jiang, Guomin <guomin.jiang@intel.com>; Lu, Xiaoyu1 <xiaoyu1.lu@intel.com>; Wang, Jian J
>> <jian.j.wang@intel.com>; Yao, Jiewen <jiewen.yao@intel.com>; Ard Biesheuvel <ardb+tianocore@kernel.org>; Justen, Jordan L
>> <jordan.l.justen@intel.com>; Gerd Hoffmann <kraxel@redhat.com>; Feng, Bob C <bob.c.feng@intel.com>; Andrew Fish
>> <afish@apple.com>
>> Subject: Re: 回复: 回复: [edk2-devel] [PATCH v2 00/13] BaseTools,CryptoPkg,MdePkg,OvmfPkg: Delete
>> CLANG35,CLANG38,GCC48,GCC49, rename GCC5 to GCC, update CLANGDWARF, delete VS 2008-2013, EBC
>>
>>
>> On 4/4/23 11:57 AM, Pedro Falcato wrote:
>>> On Tue, Apr 4, 2023 at 6:52 PM Kinney, Michael D
>>> <michael.d.kinney@intel.com> wrote:
>>>> I see value in adding a new name.
>>>>
>>>> I see no value in a non-backwards compatible change to delete/rename a fully supported one.
>>> As Leif said, you reduce all sorts of possible confusion.
>>>
>>> VS2013 builds only for Visual Studio 2013 tools, VS2017 does the same
>>> for 2017, GCC5 meanwhile builds on anything from (probably GCC 4.x,
>>> since LTO, 2011) to GCC 13 (to be released soon, 2023).
>>>
>>> Surely downstreams can adapt to *this one cosmetic change* that
>>> changes no behavior.
>> Nope, GCC5 currently only builds on GCC _6_ and newer, since we don't
>> specify -std=c++11. Which makes this discussion even more ridiculous IMO.
>>
>>
>> --
>> Rebecca Cran