Date: Fri, 24 May 2024 10:55:40 +0000 From: bugzilla-noreply@freebsd.org To: numerics@FreeBSD.org Subject: [Bug 272758] c16rtomb and c32rtomb wrong return value (at least on aarch64) Message-ID: <bug-272758-18636-oZl1bXRe32@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-272758-18636@https.bugs.freebsd.org/bugzilla/> References: <bug-272758-18636@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272758 Philipp <pkk@spth.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|Works As Intended |--- Status|Closed |Open --- Comment #6 from Philipp <pkk@spth.de> --- Maybe this "Works As Intended", since the user can "zero the mbstate_t stru= ct and it should all work well". But then this should be clearly documented as= an intentional deviation from the C standard. The C standard clearly states that mbrtoc16, when writing a null wide character, puts the mbstate_t object into the initial conversion state. It doesn't matter if that happens via zeroing or any other way. But, accord= ing to the C standard, mbrtoc16 does it, the user doesn't have to do it. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272758-18636-oZl1bXRe32>