Hi Liming,

For Q2, all ECC errors is come from register naming. I think what you are pointing out is not UEFI SPEC, we have the LoongArch ISA manual on GitHub where all of register naming are defined. Dose that means it is a public SPEC? If yes, what should I do to get the Azure CI ECC to pass?

LoongArch ISA manual link: https://loongson.github.io/LoongArch-Documentation/LoongArch-Vol1-EN.html

Hope you reply, thank you!

--
Thanks,
Chao
------------------------


On 4月 20 2022, at 7:39 早上, "gaoliming" <gaoliming@byosoft.com.cn> wrote:
For Q2, if key word is defined in public spec, they can be handled as the exception.  You can see MdePkg\MdePkg.ci.yaml EccCheck section that has ExceptionList and IgnoreFiles.

 

Thanks

Liming

发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Sean
发送时间: 2022年4月20日 0:39
收件人: Chao Li <lichao@loongson.cn>; devel@edk2.groups.io
主题: Re: [edk2-devel] Some questions about Azure CI
 

Q1 - There should be more details in the actual log file, but your code has formatting errors.   In the last few months, the uncrusitfy tool has been introduced to get common formatting errors fixed.   See details here: EDK II Code Formatting · tianocore/tianocore.github.io Wiki

Q2 - New code additions require passing ECC.  You will just need to work through the reported errors. 

Thanks
Sean

Sent from Mailspring