public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran via groups.io" <rebecca=os.amperecomputing.com@groups.io>
To: devel@edk2.groups.io, michael.d.kinney@intel.com,
	Rebecca Cran <rebecca@bsdio.com>,
	"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: Fri, 22 Nov 2024 15:30:29 -0700	[thread overview]
Message-ID: <c3e39083-8b05-4fb7-ad5b-e65360e1a19f@os.amperecomputing.com> (raw)
In-Reply-To: <CO1PR11MB4929113C604798DC381237C0D2232@CO1PR11MB4929.namprd11.prod.outlook.com>

All of them including GCC 4.8 and 4.9?


Rebecca


On 11/22/2024 2:08 PM, Michael D Kinney via groups.io wrote:
> Hi Rebecca,
>
> Yes.  I have collected feedback.  I have found some use of these toolchains.
>
> I do not have a date when the move to newer toolchains will be completed.
>
> Mike
>
>> -----Original Message-----
>> From: Rebecca Cran <rebecca@bsdio.com>
>> Sent: Thursday, November 21, 2024 9:05 PM
>> To: Kinney, Michael D <michael.d.kinney@intel.com>;
>> devel@edk2.groups.io; leif.lindholm@oss.qualcomm.com
>> Subject: Re: [edk2-devel] Removal of VS2015 (and maybe VS2017) and
>> deprecated toolchains (GCC48, GCC49, GCC5)
>>
>> Hi Mike,
>>
>>
>> I was wondering if you'd been able to collect any feedback or review the
>> proposal?
>>
>>
>> Rebecca
>>
>>
>> On 10/23/24 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 (#120820): https://edk2.groups.io/g/devel/message/120820
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]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-11-22 22:30 UTC|newest]

Thread overview: 13+ 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
2024-11-22  5:05     ` Rebecca Cran
2024-11-22 21:08       ` Michael D Kinney via groups.io
2024-11-22 22:30         ` Rebecca Cran via groups.io [this message]
2024-11-23  0:01           ` Michael D Kinney via groups.io
2024-11-24 17:56             ` Michael D Kinney via groups.io
2024-11-24 19:56               ` Rebecca Cran
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=c3e39083-8b05-4fb7-ad5b-e65360e1a19f@os.amperecomputing.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