From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 29448 invoked from network); 18 Dec 2022 12:23:43 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 18 Dec 2022 12:23:43 -0000 Received: (qmail 30099 invoked by uid 550); 18 Dec 2022 12:23:38 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 30040 invoked from network); 18 Dec 2022 12:23:37 -0000 Date: Sun, 18 Dec 2022 13:23:25 +0100 From: Szabolcs Nagy To: Domingo Alvarez Duarte Cc: musl@lists.openwall.com Message-ID: <20221218122325.GB78424@port70.net> Mail-Followup-To: Domingo Alvarez Duarte , musl@lists.openwall.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [musl] Bug in atoll strtoll, the output of then differ * Domingo Alvarez Duarte [2022-12-18 10:32:10 +0100]: > Doing some work with emscripten with this project > https://github.com/mingodad/CG-SQL-Lua-playground I was getting some errors > with the usage of "atoll" and with this small program to compare the output > of "musl" and "glibc" I found what seems to be a bug in "atoll" because with > "musl" it gives a different output than "strtoll". as others pointed out using ato* is a bug here. glibc does not guarantee ato* to to be compatible with strto* either and it just got around fixing its internal ato* usage: https://sourceware.org/pipermail/libc-alpha/2022-December/144147.html