From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Qiu, Michael" <michael.qiu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] test: Disable strict-aliasing warnings
Date: Fri, 27 Mar 2015 08:57:15 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8972727CBDB@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <533710CFB86FA344BFBF2D6802E60286D18E59@SHSMSX101.ccr.corp.intel.com>
> -----Original Message-----
> From: Qiu, Michael
> Sent: Friday, March 27, 2015 8:41 AM
> To: De Lara Guarch, Pablo; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] test: Disable strict-aliasing warnings
>
> On 3/27/2015 3:18 AM, Pablo de Lara wrote:
> > DPDK does not build on gcc 4.4, as it complains due to
>
> Why? Will gcc 4.4 not supported?
Afaik, we still support gcc 4.4, since it is part of RHEL 6.5.
Thanks,
Pablo
>
> Thanks,
> Michael
> > strict-aliasing rules in virtual_pmd and link_bonding_mode4 tests,
> > with no errors in next gcc versions:
> >
> > CC virtual_pmd.o
> > CC test_link_bonding_mode4.o
> > cc1: warnings being treated as errors
> > /root/dpdk/app/test/test_link_bonding_mode4.c: In function
> 'test_mode4_expired':
> > /root/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring.h:645: error:
> dereferencing pointer 'pkt.409' does break strict-aliasing rules
> > /root/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring.h:729: error:
> dereferencing pointer 'pkt.409' does break strict-aliasing rules
> > ...
> > cc1: warnings being treated as errors
> > /root/dpdk/app/test/virtual_pmd.c: In function
> 'virtual_ethdev_stats_reset':
> > /root/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring.h:645: error:
> dereferencing pointer 'pkt.338' does break strict-aliasing rules
> > /root/dpdk/x86_64-native-linuxapp-gcc/include/rte_ring.h:729: error:
> dereferencing pointer 'pkt.338' does break strict-aliasing rules
> >
> > This patch fixes the compilation by disabling
> > these warnings.
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> > ---
> > app/test/Makefile | 5 +++++
> > 1 files changed, 5 insertions(+), 0 deletions(-)
> >
> > diff --git a/app/test/Makefile b/app/test/Makefile
> > index 4aca77c..0d62d07 100644
> > --- a/app/test/Makefile
> > +++ b/app/test/Makefile
> > @@ -158,6 +158,11 @@ CFLAGS_test_memcpy_perf.o += -fno-var-
> tracking-assignments
> > endif
> > endif
> >
> > +# Disable warnings of no-strict-aliasing in virtual_pmd
> > +# and test_link_bonding_mode4 tests
> > +CFLAGS_virtual_pmd.o += -Wno-strict-aliasing
> > +CFLAGS_test_link_bonding_mode4.o += -Wno-strict-aliasing
> > +
> > # this application needs libraries first
> > DEPDIRS-y += lib
> >
next prev parent reply other threads:[~2015-03-27 8:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 19:17 Pablo de Lara
2015-03-27 8:41 ` Qiu, Michael
2015-03-27 8:57 ` De Lara Guarch, Pablo [this message]
2015-03-27 9:20 ` Thomas Monjalon
2015-03-27 9:29 ` De Lara Guarch, Pablo
2015-03-27 10:00 ` Thomas Monjalon
2015-03-27 10:11 ` De Lara Guarch, Pablo
2015-03-30 11:11 ` De Lara Guarch, Pablo
2015-03-27 10:55 ` [dpdk-dev] [PATCH v2 0/2] test: fix strict aliasing rule errors in gcc 4.4 Pawel Wodkowski
2015-03-27 10:56 ` [dpdk-dev] [PATCH v2 1/2] test: fix strict aliasing rule error in virtual pmd Pawel Wodkowski
2015-03-27 15:47 ` Stephen Hemminger
2015-03-27 10:56 ` [dpdk-dev] [PATCH v2 2/2] test: fix strict aliasing rule error in link bonding mode 4 test Pawel Wodkowski
2015-03-30 20:48 ` [dpdk-dev] [PATCH v2 0/2] test: fix strict aliasing rule errors in gcc 4.4 Thomas Monjalon
2015-03-27 15:46 ` [dpdk-dev] [PATCH] test: Disable strict-aliasing warnings Stephen Hemminger
2015-03-27 15:48 ` De Lara Guarch, Pablo
2015-03-30 11:06 ` [dpdk-dev] [PATCH v2] DPDK does not build on gcc 4.4, as it complains due to strict-aliasing rules in virtual_pmd and link_bonding_mode4 tests, with no errors in next gcc versions: Pablo de Lara
2015-03-30 20:47 ` Thomas Monjalon
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=E115CCD9D858EF4F90C690B0DCB4D8972727CBDB@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=michael.qiu@intel.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).