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.web10.51708.1680259985642975747 for ; Fri, 31 Mar 2023 03:53:06 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=gkxuVfHj; 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=1680259984; 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=L6gv9UHL8sl2xoMduoa7HmJXm5D2YrZ5vbOpfMWrIk4=; b=gkxuVfHjFVtbhAPpkiofJWTeRLlrqKxVWpuR4ypzdgwb7oydpG9lOH8OVQq11bxBd7TI3w ddTFWrZniDRfK+BVPSMeuoze2f5Mg80hqYxgfLLPwUweSVxX/7tdq9uxhEQudC1cOeo44+ zHIvFIPorZ90EK1SBWAMUsm38veM4bc= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-501-qBxI3gLiPKyCk0S-Uw3ZGA-1; Fri, 31 Mar 2023 06:53:01 -0400 X-MC-Unique: qBxI3gLiPKyCk0S-Uw3ZGA-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id AD3E83C0F22E; Fri, 31 Mar 2023 10:53:00 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.193.100]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3DA0A4042AC0; Fri, 31 Mar 2023 10:53:00 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id D08E118000A3; Fri, 31 Mar 2023 12:52:58 +0200 (CEST) Date: Fri, 31 Mar 2023 12:52:58 +0200 From: "Gerd Hoffmann" To: Ard Biesheuvel Cc: Marvin =?utf-8?Q?H=C3=A4user?= , devel@edk2.groups.io, Rebecca Cran , Andrew Fish Subject: Re: [edk2-devel] [RFT PATCH v2 1/6] BaseTools/tools_def XCODE: Link X64 with -read_only_relocs suppress Message-ID: References: MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Hi, > > However, those issues might have been fixed and it’s not impossible > > Vitaly will give it another try eventually. In any case, I think our > > downstream variant of XCODE5 doesn’t require any level of special > > care, so it doesn’t really matter to us. > > > > (Another thing to consider is despite the bugs are fixed, mtoc has a > > much higher overall code quality and more safety checks than GenFw, > > which is used for CLANGDWARF.) > > > > The upstream toolchain has no future in my opinion, as mtoc has been > > deprecated and already failed to compile certain things (like it > > lacked Standalone MM types). The reason it still “worked” was > > because homebrew silently shipped a variant with a subset of our > > ocmtoc patches. So as I see it, taking our changes or dropping it > > entirely are the only sane options, even regardless of this > > particular issue you’re trying to fix. Personally, I have no > > preference. > > I think both GenFw and mtoc are horrible hacks that should be phased > out once we can - with good cross-architecture Clang support for > native PE binaries, I'd hope macOS could move to CLANGPDB for all > targets. What is the difference between CLANGPDB and CLANGDWARF? Just the debug info format? What is the support status? Is CLANGDWARF expected to build edk2 on all platforms? Including cross-builds? Or will that work only after Rebecca's toolchain fix/cleanup series being merged? Should we eventually switch from gcc to clang on linux too? take care, Gerd