From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f52.google.com (mail-pa0-f52.google.com [209.85.220.52]) by dpdk.org (Postfix) with ESMTP id 9A66EAFDC for ; Mon, 23 Jun 2014 19:15:49 +0200 (CEST) Received: by mail-pa0-f52.google.com with SMTP id eu11so6071647pac.25 for ; Mon, 23 Jun 2014 10:16:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-type:content-transfer-encoding; bh=UPh5qMWKkZYVEaDRmTomHv0sU5BECqJfQajbaJK6SQQ=; b=KosvSEniPcD7SFOicKhaUXRT95vfnFITDIed11F/aoKXq2JmWAizMQMKgtEsEQ8NQQ eayl4qMmGjcyY/R+x/2oGpT70Bf0sw/8iEKw7hLe8obuaqHEYPWc4kLOuZVBYN6BurwD t5Wxq9CF1XgCf2RzoStJoDeVgcxu/tXpVgirVJrb8Q/tAb//wupTu709JWdQK+JdTPpl exTT4QaCjWJFaQapjYDlEgKxFN/L0fx+FzcJaOYOmweeo9qhono22xma8hBNml1HnUjT dH5absrI/hy4spcNzuvofVON6EvUrN0UT00AaCtefHtudDtCHHffBeFAxQ2RFcFFtO2P I3nA== X-Gm-Message-State: ALoCoQkg16a7p/2FW1/9A8w5kg63QUim6YA/oBpsI6k68rtx8ttVACBIIEOmpJlFKvuXGswCNLDq X-Received: by 10.66.254.136 with SMTP id ai8mr30611120pad.37.1403543766786; Mon, 23 Jun 2014 10:16:06 -0700 (PDT) Received: from nehalam.linuxnetplumber.net (static-50-53-83-51.bvtn.or.frontiernet.net. [50.53.83.51]) by mx.google.com with ESMTPSA id zn9sm96489981pac.31.2014.06.23.10.16.06 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 23 Jun 2014 10:16:06 -0700 (PDT) Date: Mon, 23 Jun 2014 10:16:03 -0700 From: Stephen Hemminger To: dev@dpdk.org Message-ID: <20140623101603.54a5d887@nehalam.linuxnetplumber.net> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [dpdk-dev] Why rte_snprintf at all? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 17:15:50 -0000 Why does rte_snprintf exist? It seems like a misunderstanding or broken implementation of snprintf in some other C library. For standard Glibc, I get same result from rte_snprintf and snprintf for all inputs including boundary cases