From: "Rebecca Cran" <rebecca@bsdio.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"leif.lindholm@oss.qualcomm.com" <leif.lindholm@oss.qualcomm.com>
Subject: Re: [edk2-devel] Removal of VS2015 (and maybe VS2017) and deprecated toolchains (GCC48, GCC49, GCC5)
Date: Wed, 23 Oct 2024 23:14:04 -0600 [thread overview]
Message-ID: <3fa81754-85fe-48ae-a976-50510c4cb34e@app.fastmail.com> (raw)
In-Reply-To: <CO1PR11MB4929E1EB6B7FBA33FBF45628D24E2@CO1PR11MB4929.namprd11.prod.outlook.com>
Sure, that’s not a problem.
On Wed, Oct 23, 2024, at 9:23 PM, Kinney, Michael D wrote:
> Hi,
>
> I will need more time to review this impacts of this proposal.
>
> Can we extend the timeline for comments to mid November.
>
> Thanks,
>
> Mike
>
>> -----Original Message-----
>> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Leif
>> Lindholm via groups.io
>> Sent: Tuesday, October 22, 2024 5:15 AM
>> To: devel@edk2.groups.io; rebecca@bsdio.com
>> Subject: Re: [edk2-devel] Removal of VS2015 (and maybe VS2017) and
>> deprecated toolchains (GCC48, GCC49, GCC5)
>>
>> On Tue, 22 Oct 2024 at 12:19, Rebecca Cran <rebecca@bsdio.com> wrote:
>> > In addition, since GCC48, GCC49 and GCC5 have been marked deprecated
>> for
>> > over a year, I'd like to proceed with removing them as well.
>> >
>> > Please provide feedback by Thursday October 31st. In the absence of
>> > feedback I'll plan to proceed with removing VS2015, GCC48, GCC49 and
>> GCC5.
>>
>> No comment on the VS ones, but for the GCC ones, I'm all for it.
>>
>> We might also want to raise an issue on deleting workarounds put into
>> place for ancient toolchains.
>> For gcc48/49 that was redundant initialization due to broken
>> use-uninitialized detection.
>> e.g.
>> https://github.com/tianocore/edk2/blob/master/OvmfPkg/Library/X86QemuLoa
>> dImageLib/X86QemuLoadImageLib.c#L346
>>
>> /
>> Leif
>>
>>
>>
>>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120679): https://edk2.groups.io/g/devel/message/120679
Mute This Topic: https://groups.io/mt/109150018/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-10-24 5:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 11:18 [edk2-devel] Removal of VS2015 (and maybe VS2017) and deprecated toolchains (GCC48, GCC49, GCC5) Rebecca Cran
2024-10-22 12:14 ` Leif Lindholm via groups.io
2024-10-24 3:23 ` Michael D Kinney
2024-10-24 5:14 ` Rebecca Cran [this message]
2024-10-22 15:53 ` [edk2-devel] [edk2-discuss] " Sean
2024-10-22 17:38 ` Michael D Kinney
2024-10-22 23:16 ` Rebecca Cran
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=3fa81754-85fe-48ae-a976-50510c4cb34e@app.fastmail.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