From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.groups.io with SMTP id smtpd.web11.67119.1680519525878287469 for ; Mon, 03 Apr 2023 03:58:46 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=fgkOfLvw; spf=pass (domain: redhat.com, ip: 170.10.129.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680519524; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ythXiqhdDwPZmxupDbvRQftYMOvvB6iB0HYH5y2eb50=; b=fgkOfLvwmZWcRS7NGf3H7b4XyKMMcnrE13uKwc7rj2QsdzpyWotst8bdr/DwNR+N8OV1+t 3xxEjuGZGegVr7doWuuew0xdy0tqep5TGZpAt6P7MPnmVsGpgHRZ3dGfvWaknjYsS+P97d Awwb5p+YgfG992dFSk//Gs9fc19NN/E= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-447-vj_Sgw2_PPeoU6S0UOBmzQ-1; Mon, 03 Apr 2023 06:58:43 -0400 X-MC-Unique: vj_Sgw2_PPeoU6S0UOBmzQ-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 2B68D885621; Mon, 3 Apr 2023 10:58:43 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.193.241]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7100E202701E; Mon, 3 Apr 2023 10:58:41 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id CF1441800393; Mon, 3 Apr 2023 12:58:37 +0200 (CEST) Date: Mon, 3 Apr 2023 12:58:37 +0200 From: "Gerd Hoffmann" To: devel@edk2.groups.io, lichao@loongson.cn Cc: maobibo@loongson.cn, WANG Xuerui , qemu-devel , Song Gao , =?utf-8?B?5p2o5bCP5aif?= Subject: Re: [edk2-devel] On integrating LoongArch EDK2 firmware into QEMU build process Message-ID: References: <1f1d3d9f-c3df-4f29-df66-886410994cc3@xen0n.name> <67517424-0f32-09f8-6446-53f71ebd59b5@loongson.cn> <317e3008-e2bd-8af6-2cf5-dad49d98cb8d@loongson.cn> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.4 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit On Mon, Apr 03, 2023 at 06:13:41PM +0800, Chao Li wrote: > Hi Bibo, > > gcc-13 will support this new feature, so we expect this issue to be resolved > when using gcc-13, which may be released at this month. > > If Fedora38 does not plan to use gcc-13 now, I suggest that CI can download > a LoongArch cross gcc-13 when creating a docker image, just like EDK2 CI > process. You can refer following link for more information: The non-cross gcc already is at 13. Fedora builds the distro with pre-release gcc so gcc gets some serious real-world testing before release. The cross compilers lagging behind a bit, not sure whenever there is some actual problem or whenever maintainers are just waiting for the final gcc-13 release. > https://github.com/tianocore/containers/blob/main/Fedora-37/Dockerfile . > EDK2 CI uses Fedora35 and Fedora37 docker images for LoongArch,  they will > download a LoongArch cross gcc-13 when the CI targets is LoongArch. While that works as temporary stopgap for edk2 CI it is a non-starter for fedora distro builds. Any builds must be done using compilers shipped by fedora. So, fedora shipping edk2-loongarch (or ipxe-loongarch) packages is blocked by this. > We are really sorry about that, I think this solution will make more work > for you, but I think it is the best way for now, and I believe it will be > solved when Fedora uses gcc-13 in the future. I'll go just wait for gcc-13 cross compilers land in fedora then. take care, Gerd