public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, yuwei.chen@intel.com
Cc: "Gao, Liming" <gaoliming@byosoft.com.cn>,
	Rebecca Cran <rebecca@bsdio.com>,
	 "Zimmer, Vincent" <vincent.zimmer@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	 Leif Lindholm <quic_llindhol@quicinc.com>,
	Andrew Fish <afish@apple.com>,
	 "Feng, Bob C" <bob.c.feng@intel.com>,
	"Yang, Yuting2" <yuting2.yang@intel.com>,
	 "Hartung, Stephen" <stephen.hartung@intel.com>
Subject: Re: [edk2-devel] [edk2-stable202311][PATCH] BaseTools: Python VfrCompiler implementation
Date: Fri, 15 Dec 2023 17:04:11 +0000	[thread overview]
Message-ID: <CAKbZUD0AOrUZx7Kht+wobNXjuGMNwihiGLzHDuW-X1gVwhehOw@mail.gmail.com> (raw)
In-Reply-To: <MW5PR11MB5906C2D3A12DE9CD7EC383BC968BA@MW5PR11MB5906.namprd11.prod.outlook.com>

On Thu, Dec 7, 2023 at 9:08 AM Yuwei Chen <yuwei.chen@intel.com> wrote:
>
> Hi Liming,
>
>
>
> Is this feature been tested and reviewed these two weeks? 😊

Two questions:

1) What testing strategy do you have to test for regressions in such a
huge rewrite?
2) What's the point in shipping this to upstream if you're not aiming
for the replacement of the original VfrCompiler?
3) What's the value of rewriting this in Python? If the existing
VfrCompiler is already working fine (AFAIK?), a python version will
likely just be slower (unless the original C version is super badly
written).
I *seriously* struggle to understand what this Python movement is
supposed to do, except gratuitously rewrite large bits of BaseTools
for a net loss (performance)

-- 
Pedro


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112604): https://edk2.groups.io/g/devel/message/112604
Mute This Topic: https://groups.io/mt/102486097/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  parent reply	other threads:[~2023-12-15 17:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 14:19 [edk2-devel] [edk2-stable202311][PATCH] BaseTools: Python VfrCompiler implementation gaoliming via groups.io
2023-11-13  0:32 ` Yuwei Chen
     [not found] ` <1797076B3E222792.28092@groups.io>
2023-12-07  9:08   ` Yuwei Chen
2023-12-11  9:33     ` 回复: " gaoliming via groups.io
2023-12-15  2:40       ` Yuting Yang
2023-12-15 17:04     ` Pedro Falcato [this message]
2023-12-15 17:31       ` Michael D Kinney
2024-01-09  8:23         ` Yuwei Chen
2024-03-06 15:04           ` Chang, Abner via groups.io

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=CAKbZUD0AOrUZx7Kht+wobNXjuGMNwihiGLzHDuW-X1gVwhehOw@mail.gmail.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