DPDK patches and discussions
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5] eal_common_cpuflags: Fix %rbx corruption, and simplify the code
Date: Wed, 16 Apr 2014 08:53:42 -0400	[thread overview]
Message-ID: <20140416125342.GA11887@localhost.localdomain> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8970829D24B@IRSMSX103.ger.corp.intel.com>

On Wed, Apr 16, 2014 at 11:09:46AM +0000, De Lara Guarch, Pablo wrote:
> Hi Neil,
> 
> >Oh wow, yes, the if conditionals definately should be checked for each iteration of the for loop. Good eye.
> 
> >Still though, seems like a bug in gcc to check the state of the loop index on exit, when its never used to index the array at that value.  Seems a bit like this bug:
> >http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45180
> 
> >Thomas I'll send a patch to fix this directly Neil
> 
> Actually, that index may be used in cause last "ret" value is 0:
> 
> if (!ret) {
>                         fprintf(stderr,
>                                 "ERROR: This system does not support \"%s\".\n"
>                                 "Please check that RTE_MACHINE is set correctly.\n",
>                                 cpu_feature_table[compile_time_flags[i]].name);
>                         exit(1);
>                 }
> 
Ah, well there you have it.  Thank you.  Either way though, those two error
checks need to be encased in brackets.  It appears I missed it in my previous
patch as the for loop only had one if, and so didn't need additional brackets,
and I extended the check, requiring brackets that I never added.  apologies.

I've sent a patch for review
Neil

> Thanks,
> 
> Pablo de Lara
> DPDK SW Engineer
> 
> --------------------------------------------------------------
> Intel Shannon Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 Business address: Dromore House, East Park, Shannon, Co. Clare
> 
> 
> 
>  
> 

  reply	other threads:[~2014-04-16 12:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16  8:58 De Lara Guarch, Pablo
2014-04-16  9:06 ` Thomas Monjalon
2014-04-16 10:49 ` Neil Horman
2014-04-16 11:09   ` De Lara Guarch, Pablo
2014-04-16 12:53     ` Neil Horman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-15 14:09 De Lara Guarch, Pablo
2014-04-15 14:56 ` Neil Horman
2014-04-16  8:36   ` De Lara Guarch, Pablo
2014-03-20 16:39 [dpdk-dev] [RFC UNTESTED PATCH] " Neil Horman
2014-03-25 19:52 ` [dpdk-dev] [PATCH v5] " Neil Horman
2014-03-25 20:51   ` H. Peter Anvin
2014-04-02 11:16     ` Neil Horman
2014-04-02 11:53       ` Thomas Monjalon
2014-04-02 12:42     ` 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=20140416125342.GA11887@localhost.localdomain \
    --to=nhorman@tuxdriver.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@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).