public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Tiger Liu(BJ-RD)" <TigerLiu@zhaoxin.com>
To: "Gao, Liming" <liming.gao@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: difference between asm16 and asm files
Date: Tue, 30 Jan 2018 01:45:03 +0000	[thread overview]
Message-ID: <c08eef5524cb43c393e3d5021cae959a@zhaoxin.com> (raw)

Hi, Liming:
Thanks for your reply!

I have another question:
Why not let sec code complied to obj file and linked to lib and EFI image?

I met a problem:
I tried to use IFDEF marco in an assembly inc file,  and this inc file would be included by ResetVec.asm16
But failed, it seemed asm 16 complier not recognize this marco exist.
If I changed ResetVec.asm16 to ResetVec.asm, and compiled again, the complier will recognize this marco exist.
But the last step failed, GenFds.exe seems search a binary file, and not found.

Thanks
-----邮件原件-----
发件人: Gao, Liming [mailto:liming.gao@intel.com]
发送时间: 2018年1月29日 22:30
收件人: Tiger Liu(BJ-RD) <TigerLiu@zhaoxin.com>; edk2-devel@lists.01.org
主题: RE: [edk2] difference between asm16 and asm files

Asm16 is compiled to the binary file. Asm is compiled to the obj file, and linked into lib and EFI image.

Now, asm16 is replaced by nasmb. Asm is replaced by nasm. If you check SecCore.inf, you will find ResetVec.asm16 is not used, and ResetVec.nasmb is used. I will send the patch to remove the unused ResetVec.asm16 to avoid the confuse.

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Tiger Liu(BJ-RD)
> Sent: Monday, January 29, 2018 6:49 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] difference between asm16 and asm files
>
> Hi, experts:
> I have a question about asm16 postfix and asm postfix.
>
> Such as:
> UefiCpuPkg\SecCore\Ia32\ResetVec.asm16
>
> Why not use asm as postfix?
>
> Thanks
>
> Best wishes,
>
>
> ?????
> ?????????????????????????????????????????????????????
> CONFIDENTIAL NOTE:
> This email contains confidential or legally privileged information and
> is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


保密声明:
本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。
CONFIDENTIAL NOTE:
This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.

             reply	other threads:[~2018-01-30  1:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30  1:45 Tiger Liu(BJ-RD) [this message]
2018-01-30  2:18 ` difference between asm16 and asm files Gao, Liming
  -- strict thread matches above, loose matches on Subject: below --
2018-02-02 11:04 Tiger Liu(BJ-RD)
2018-01-31  5:17 Tiger Liu(BJ-RD)
2018-01-31  9:44 ` Gao, Liming
2018-01-29 10:48 Tiger Liu(BJ-RD)
2018-01-29 14:29 ` Gao, Liming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c08eef5524cb43c393e3d5021cae959a@zhaoxin.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox