DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Qiu, Michael" <michael.qiu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] examples/ip_pipeline: Fix compile issue with strict-aliasing
Date: Wed, 09 Dec 2015 21:38:22 +0100	[thread overview]
Message-ID: <4810660.9qnD8sC8sF@xps13> (raw)
In-Reply-To: <54CBAA185211B4429112C315DA58FF6DD8FBE4@IRSMSX103.ger.corp.intel.com>

> > Compile ip_pipeline in CentOS 6.5 with kernel 2.6.32-431 GCC 4.4.7, will lead
> > below error:
> > 
> >     pipeline_routing_be.c: In function
> > ‘pipeline_routing_msg_req_arp_add_handler’:
> >     pipeline_routing_be.c:1817: error: dereferencing pointer ‘({anonymous})’
> > 				does break strict-aliasing rules
> > 
> > This because the code break strict-aliasing rule.
> > The patch solve this issue.
> > 
> > Fixes: 0ae7275810f1 (examples/ip_pipeline: add more functions to routing
> > pipeline)
> > 
> > Signed-off-by: Michael Qiu <michael.qiu@intel.com>
> 
> Acked-by: Jasvinder Singh <jasvinder.singh@intel.com>

Applied, thanks

      reply	other threads:[~2015-12-09 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09  8:44 Michael Qiu
2015-12-09  9:22 ` Singh, Jasvinder
2015-12-09 20:38   ` Thomas Monjalon [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=4810660.9qnD8sC8sF@xps13 \
    --to=thomas.monjalon@6wind.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).