|
Message-ID: <20240226013056.GE4163@brightrain.aerifal.cx> Date: Sun, 25 Feb 2024 20:30:56 -0500 From: Rich Felker <dalias@...c.org> To: Markus Wichmann <nullplan@....net> Cc: musl@...ts.openwall.com, Anuraag Agrawal <anuraaga@...il.com> Subject: Re: Large overflow in __intscan ignored On Sat, Dec 02, 2023 at 11:29:41AM -0500, Rich Felker wrote: > On Sat, Dec 02, 2023 at 09:48:58AM +0100, Markus Wichmann wrote: > > Am Sat, Dec 02, 2023 at 10:42:11AM +0900 schrieb Anuraag Agrawal: > > > Hello, > > > > > > Thanks for checking and very sorry for the noise, I didn't read the loop > > > condition correctly. I am using Webassembly so the issue must be specific > > > to it somehow. I will report on wasi-libc to follow up. > > > > > > Thanks, > > > > Don't worry about it. The only way I see this could overflow is if > > ULLONG_MAX is not the correct limit for what the compiler implements as > > "unsigned long long". Though I don't see how that could be, since musl > > defines ULLONG_MAX as the minimum value the type can have according to > > the C standard. > > > > Or else, of course, maybe the compiler's implementation of 64-bit > > multiplication is broken. > > Ouch, sounds like this is going to be some sort of big wasm bug... Was this bug ever reported/tracked-down/fixed on the wasm side? Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.