From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3 3/5] hash: add fallback to software CRC32 implementation Date: Tue, 18 Nov 2014 14:43:37 +0100 Message-ID: <4195462.uvHhYJc7eD@xps13> References: <1416160760-16087-1-git-send-email-e_zhumabekov@sts.kz> <546AD178.9070109@sts.kz> <20141118133307.GA32375@hmsreliant.think-freely.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit To: dev-VfR2kkLFssw@public.gmane.org Return-path: In-Reply-To: <20141118133307.GA32375-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 2014-11-18 08:33, Neil Horman: > On Tue, Nov 18, 2014 at 10:56:24AM +0600, Yerden Zhumabekov wrote: > > Sorry, maybe I made a mistake here. > > > > Accoring to lib/librte_eal/common/eal_common_cpuflags.c code, it seemed > > to me that constructor attribute is not supported by intel compiler. So > > in that case here I decided to leave the code for autodetection. Am I > > correct? > > I don't think thats correct. The Intel Compiler claims support for most GCC > features, except where explicitly stated in the release notes, and I don't find > any documentation clearly excepting the constructor attribute from that list. > That said, since the intel compiler isn't open, I don't have access to it and > cannot confirm either way, though if its the case, the DPDK has a major issue, > as __attribute__((constructor)) is used extensively throughout the code The comment of rte_cpu_check_supported() is: "with ICC, the check is generated by the compiler" So in my understanding, the constructor attribute is not set because this function isn't needed for ICC. I'd like to see an explanation of how CPU flags are set by ICC. -- Thomas