From: Bruce Richardson <bruce.richardson@intel.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>,
"Jacob, Jerin" <Jerin.Jacob@cavium.com>,
Jan Viktorin <viktorin@rehivetech.com>
Subject: Re: [dpdk-dev] pmdinfogen issues: cross compilation for ARM fails with older host compiler
Date: Fri, 18 Nov 2016 16:37:38 +0000 [thread overview]
Message-ID: <20161118163737.GA11072@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <20161118135052.GA29049@hmsreliant.think-freely.org>
On Fri, Nov 18, 2016 at 08:50:52AM -0500, Neil Horman wrote:
> On Fri, Nov 18, 2016 at 12:03:19PM +0000, Hemant Agrawal wrote:
> > > -----Original Message-----
> > > From: Neil Horman [mailto:nhorman@tuxdriver.com]
> > > On Tue, Nov 15, 2016 at 09:34:16AM +0000, Hemant Agrawal wrote:
> > > > > On Mon, Nov 14, 2016 at 02:29:24AM +0530, Jerin Jacob wrote:
> > > > > > On Fri, Nov 11, 2016 at 10:34:39AM +0000, Hemant Agrawal wrote:
> > > > > > > Hi Neil,
> > > > > > > Pmdinfogen compiles with host compiler. It usages
> > > rte_byteorder.h
> > > > > of the target platform.
> > > > > > > However, if the host compiler is older than 4.8, it will be an issue during
> > > cross
> > > > > compilation for some platforms.
> > > > > > > e.g. if we are compiling on x86 host for ARM, x86 host compiler will not
> > > > > understand the arm asm instructions.
> > > > > > >
> > > > > > > /* fix missing __builtin_bswap16 for gcc older then 4.8 */ #if
> > > > > > > !(__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ >= 8)) static
> > > > > > > inline uint16_t rte_arch_bswap16(uint16_t _x) {
> > > > > > > register uint16_t x = _x;
> > > > > > > asm volatile ("rev16 %0,%1"
> > > > > > > : "=r" (x)
> > > > > > > : "r" (x)
> > > > > > > );
> > > > > > > return x;
> > > > > > > }
> > > > > > > #endif
> > > > > > >
> > > > > > > One easy solution is that we add compiler platform check in this
> > > > > > > code section of rte_byteorder.h e.g #if !(defined __arm__ || defined
> > > > > > > __aarch64__) static inline uint16_t rte_arch_bswap16(uint16_t _x) {
> > > > > > > return (_x >> 8) | ((_x << 8) & 0xff00); } #else ….
> > > > > > >
> > > > > > > Is there a better way to fix it?
> > > > > >
> > > > > > IMO, It is a HOST build infrastructure issue. If a host app is using
> > > > > > the dpdk service then it should compile and link against HOST
> > > > > > target(in this specific case, build/x86_64-native-linuxapp-gcc). I
> > > > > > think, introducing the HOSTTARGET kind of scheme is a clean solution.
> > > > > >
> > > > > > /Jerin
> > > > > >
> > > > > >
> > > > > That would be accurate. That is to say, pmdinfogen is a tool that should only
> > > be
> > > > > run on the host doing the build, by the host doing the build, and so should be
> > > > > compiled to run on the host, not on the target being built for.
> > > > >
> > > > > Yeah, so what we need is a way to get to the host version of rte_byteorder.h
> > > > > when building in a cross environment
> > > > >
> > > > +1
> > > >
> > > > > Neil
> > > >
> > >
> > > Give this a try, I've tested it on linux, but not BSD. From what I read the
> > > functions are not posix compliant, though they should exist on all BSD and Linux
> > > systems in recent history. There may be some fiddling needed for Net and
> > > OpenBSD variants, but I think this is the right general direction.
> >
> > + 1
> > This patch works good for Linux.
> >
> Can someone test it on BSD? I'd like to ensure we don't need to modify it for
> that platform
>
> Neil
>
> > >
> > >
> > > diff --git a/buildtools/pmdinfogen/pmdinfogen.h
> > > b/buildtools/pmdinfogen/pmdinfogen.h
> > > index 1da2966..c5ef89d 100644
> > > --- a/buildtools/pmdinfogen/pmdinfogen.h
> > > +++ b/buildtools/pmdinfogen/pmdinfogen.h
> > > @@ -21,7 +21,6 @@
> > > #include <elf.h>
> > > #include <rte_config.h>
> > > #include <rte_pci.h>
> > > -#include <rte_byteorder.h>
> > >
> > > /* On BSD-alike OSes elf.h defines these according to host's word size */
> > > #undef ELF_ST_BIND
> > > @@ -75,9 +74,9 @@
> > > #define CONVERT_NATIVE(fend, width, x) ({ \
> > > typeof(x) ___x; \
> > > if ((fend) == ELFDATA2LSB) \
> > > - ___x = rte_le_to_cpu_##width(x); \
> > > + ___x = le##width##toh(x); \
> > > else \
> > > - ___x = rte_be_to_cpu_##width(x); \
> > > + ___x = be##width##toh(x); \
> > > ___x; \
> > > })
> > >
For compile on FreeBSD 10 we need "#include <sys/endian.h>" and this
works.
/Bruce
next prev parent reply other threads:[~2016-11-18 16:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 10:34 Hemant Agrawal
2016-11-11 13:48 ` Jan Viktorin
2016-11-11 19:25 ` Neil Horman
2016-11-13 20:59 ` Jerin Jacob
2016-11-14 14:48 ` Neil Horman
2016-11-15 9:34 ` Hemant Agrawal
2016-11-15 14:27 ` Neil Horman
2016-11-15 16:33 ` Thomas Monjalon
2016-11-15 15:08 ` Neil Horman
2016-11-18 12:03 ` Hemant Agrawal
2016-11-18 13:50 ` Neil Horman
2016-11-18 16:37 ` Bruce Richardson [this message]
2016-11-18 18:39 ` Neil Horman
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=20161118163737.GA11072@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=Jerin.Jacob@cavium.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=nhorman@tuxdriver.com \
--cc=users@dpdk.org \
--cc=viktorin@rehivetech.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).