From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mx.groups.io with SMTP id smtpd.web12.11504.1605121534052198333 for ; Wed, 11 Nov 2020 11:05:34 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=TubDmNji; spf=pass (domain: redhat.com, ip: 216.205.24.124, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1605121533; 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=7g4h/+V/5I6A+NwG/M+hLCtdCNGbpLoBgaMjYqSRRfI=; b=TubDmNjikPcCFE5fk8+1z+sUQVJAnfY4yxZtethj8idkz/GnQW89vqfIR/ahrtm1rN3Zec WMiJQM2Cb9u9hTeITw9GcsVWhrd4U1hgK+L27UJJQdd+GqzUmiTQYYz+E+j93dDeGWurw7 daI/EsvWq+E1RfQfioazT5DlKSuD974= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-219-K_tB1_nhN7eWe7gXQIxnZg-1; Wed, 11 Nov 2020 14:05:29 -0500 X-MC-Unique: K_tB1_nhN7eWe7gXQIxnZg-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A43319CC05; Wed, 11 Nov 2020 19:05:27 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-113-85.ams2.redhat.com [10.36.113.85]) by smtp.corp.redhat.com (Postfix) with ESMTP id A234F5C62B; Wed, 11 Nov 2020 19:05:24 +0000 (UTC) Subject: =?UTF-8?B?UmU6IOWbnuWkjTogW2VkazItZGV2ZWxdIFtQQVRDSCB2NSAwLzJdIENyeXB0b1BrZy9PcGVuc3NsTGliOiBBZGQgbmF0aXZlIGluc3RydWN0aW9uIHN1cHBvcnQgZm9yIFg2NA==?= To: gaoliming , "'Yao, Jiewen'" , "'Zurcher, Christopher J'" Cc: devel@edk2.groups.io, "'Wang, Jian J'" , "'Lu, XiaoyuX'" , "'Kinney, Michael D'" , 'Ard Biesheuvel' References: <20201103215834.7533-1-christopher.j.zurcher@intel.com> <1644D590FF4B7423.25549@groups.io> <7D73B5FD-CBCA-4E8C-B73B-930722C9FCF7@intel.com> <903654d9-f903-734c-1d07-2f83a8c40099@redhat.com> <00e301d6b76d$cb4fc810$61ef5830$@byosoft.com.cn> From: "Laszlo Ersek" Message-ID: <8e8db464-8ac6-44d5-1299-86d449a2fbdf@redhat.com> Date: Wed, 11 Nov 2020 20:05:23 +0100 MIME-Version: 1.0 In-Reply-To: <00e301d6b76d$cb4fc810$61ef5830$@byosoft.com.cn> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 11/10/20 15:28, gaoliming wrote: > Laszlo: > Those assembly files are auto generated from openssl. Now, the generated nasm files use the syntax for win64 object only. So, they can't be used for GCC and XCODE. > Zurcher mentions GAS assembly files can also be generated. If there is the issue in them, they can be re-generated together when edk2 updates to new openssl version. So, there is no additional maintain effort for them. Hmmm, good point. I missed that the NASM files too were generated. Sorry about my mistake, it's been quite difficult to follow so many contexts. Thanks Laszlo