From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) by mx.groups.io with SMTP id smtpd.web10.18324.1676042394788371708 for ; Fri, 10 Feb 2023 07:19:54 -0800 Authentication-Results: mx.groups.io; dkim=fail reason="body hash did not verify" header.i=@quicinc.com header.s=qcppdkim1 header.b=Vhrfpb8v; spf=permerror, err=parse error for token &{10 18 %{ir}.%{v}.%{d}.spf.has.pphosted.com}: invalid domain name (domain: quicinc.com, ip: 205.220.168.131, mailfrom: quic_llindhol@quicinc.com) Received: from pps.filterd (m0279863.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 31AEm7fJ011137; Fri, 10 Feb 2023 15:19:44 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h=message-id : date : mime-version : subject : to : cc : references : from : in-reply-to : content-type : content-transfer-encoding; s=qcppdkim1; bh=G8BZeB0AsuM9rHEG7qOF1BA3Z/+xUuynBpW3cYHYzUk=; b=Vhrfpb8v0GqChhV5ImblJmR5lr//pozGynDe2f8OAvAmijmoXhegCP9fHduLbe5QJFrY nOQtv6PIliZT9d/ErErRVAOsc1bE9A2KojPOXBwVKCiRyQIWVG/VToTw7Pow3GIXX0CX gRpDkwrp4ulcrT8x64qxZhZExQdheoYp0MBmSsqvO5PnMN3hPbRYZ63Nzq/NxLhYOY9S Ht+yTAvj1v5+w53+5q0e2GgPpDi7TpRcr77CpQhl1YbqmZPnpR8qU+lznzj5MhFFZXqw 9CK7JxIesPV/q1t6GXUskd/nCGW6vCAMQyQjEPedi4IdoTI1MLtboCRhOw8ewE1MZZ8g PA== Received: from nasanppmta03.qualcomm.com (i-global254.qualcomm.com [199.106.103.254]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3nnhpwgyn0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 10 Feb 2023 15:19:43 +0000 Received: from nasanex01c.na.qualcomm.com (nasanex01c.na.qualcomm.com [10.45.79.139]) by NASANPPMTA03.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 31AFJhWN013932 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 10 Feb 2023 15:19:43 GMT Received: from [10.111.136.8] (10.80.80.8) by nasanex01c.na.qualcomm.com (10.45.79.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.36; Fri, 10 Feb 2023 07:19:41 -0800 Message-ID: <540fd56f-269b-5767-613e-67a0321bb1fe@quicinc.com> Date: Fri, 10 Feb 2023 15:19:38 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.7.2 Subject: Re: [edk2-devel] [PATCH 2/2] MdePkg: Update code to be more C11 compliant by using __func__ To: , , CC: , "Gao, Liming" , "Liu, Zhiguang" References: <20230209154507.81877-1-rebecca@quicinc.com> <20230209154507.81877-2-rebecca@quicinc.com> From: "Leif Lindholm" In-Reply-To: X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01b.na.qualcomm.com (10.46.141.250) To nasanex01c.na.qualcomm.com (10.45.79.139) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-ORIG-GUID: gGIPyhiVUNPVnuSexN95c5ROKA31py4e X-Proofpoint-GUID: gGIPyhiVUNPVnuSexN95c5ROKA31py4e X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.219,Aquarius:18.0.930,Hydra:6.0.562,FMLib:17.11.170.22 definitions=2023-02-10_09,2023-02-09_03,2023-02-09_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 bulkscore=0 adultscore=0 mlxlogscore=999 spamscore=0 lowpriorityscore=0 clxscore=1011 impostorscore=0 mlxscore=0 phishscore=0 suspectscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2302100127 X-MIME-Autoconverted: from 8bit to quoted-printable by mx0a-0031df01.pphosted.com id 31AEm7fJ011137 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: quoted-printable On 2023-02-10 11:45, Ard Biesheuvel wrote: >> I wasn't sure if we cared about EBC builds these days. Given the link = on >> https://www.intel.com/content/www/us/en/architecture-and-technology/un= ified-extensible-firmware-interface/efi-homepage-general-technology.html >> to the compiler goes to a generic page that doesn't mention it, is it >> possible to get a copy if I want to verify if changes I'm making are >> compatible? >=20 > We tried to get access to this at Linaro, but I don't think it is > still available. Leif may remember better. After asking around, some shady character in a caf=C3=A9 passed me a very= =20 long and customized URL on a note in a brown paper bag, and I was able=20 to procure a single license for ARM. I don't think we succeeded for Linar= o. > I wonder whether we should simply drop EBC support? It is unlikely > that all the changes that went into EDK2 over the years have not > caused a single EBC regression in the library components that are > needed to build UEFI drivers that target EBC. The appearance of RISC-V and Loongarch since those days highlight why=20 architecture independent drivers would be a good thing, but EBC is=20 pining for the fjords. If we don't drop EBC now, we should start drafting a timeline for when=20 we will. / Leif