From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: Mahdi Moradmand Badie <mahdi.mbadie@gmail.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Assembly code
Date: Wed, 22 Jun 2016 03:27:27 +0000 [thread overview]
Message-ID: <ED26CBA2FAD1BF48A8719AEF02201E361060B114@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <CAM=H7wcr8ryJOW_gEGdKVG70J=kxQZvZzrjLKkn26vPDrCmYoQ@mail.gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Mahdi Moradmand
> Badie
> Sent: Wednesday, June 22, 2016 5:21 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Assembly code
>
> Dear All,
>
> I used the default format of Makefile (as follow) which is available in the
> examples,
> I was wondering how I could generate the assembly (main.s) related to my
> main.c, via Makefile.
The output file is named main.o. If you add line like " CFLAGS += -S", you can find the assembly code there.
Thanks,
Jianfeng
>
> PS. using -S doesn't work :(
>
> ifeq ($(RTE_SDK),)
> $(error "Please define RTE_SDK environment variable")
> endif
>
> # Default target, can be overriden by command line or environment
> RTE_TARGET ?= x86_64-native-linuxapp-gcc
>
> include $(RTE_SDK)/mk/rte.vars.mk
>
> # binary name
> APP = Mahdi_test
>
> INC += $(wildcard include/*.h)
>
> # all source are stored in SRCS-y
> SRCS-y := main.c
>
> CFLAGS += $(WERROR_FLAGS) -I $(SRCDIR)/include -I/usr/local/include
>
> EXTRA_CFLAGS += -O3
> EXTRA_CFLAGS += -Wno-error
> EXTRA_CFLAGS += -std=c99
>
> # rte.extapp.mk : External application
> include $(RTE_SDK)/mk/rte.extapp.mk
>
> --
> M@hdi Mor@dm@nd B@die
prev parent reply other threads:[~2016-06-22 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 21:21 Mahdi Moradmand Badie
2016-06-22 3:27 ` Tan, Jianfeng [this message]
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-all 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=ED26CBA2FAD1BF48A8719AEF02201E361060B114@SHSMSX103.ccr.corp.intel.com \
--to=jianfeng.tan@intel.com \
--cc=dev@dpdk.org \
--cc=mahdi.mbadie@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).