indicated that I should mention that I do not have
write access, since I'm a first-time contributor.
On Sat, Feb 3, 2024 at 2:31 PM Ian McCormack wrote:
> Multiple `for` loops across `libdecnumber` contain boolean expressions
> where memory is accessed prior to checking if the pointer is s
This patch fixes a minor instance of undefined behavior in libdecnumber. It was
discovered in the Rust bindings for libdecnumber (`dec`) using a custom version
of MIRI that can execute foreign functions.
Within the function `decFloatFMA`, the pointer `lo->msd` is initialized to
point to a byte
This patch fixes a minor instance of undefined behavior in libdecnumber. It was
discovered in the Rust bindings for libdecnumber (`dec`) using a custom version
of MIRI that can execute foreign functions.
On the last iteration of the `while` loop in `decNumberGetBCD`, the pointer
`up` will be in
I've confirmed that these changes fix the error in MIRI, too. I'll post
an updated patch once I confirm that there aren't any regressions.
On Fri, Feb 2, 2024 at 10:38 AM Jakub Jelinek wrote:
> On Fri, Feb 02, 2024 at 04:32:09PM +0100, Jakub Jelinek wrote:
> > Anyway, I think all of
> > decBasic
Multiple `for` loops across `libdecnumber` contain boolean expressions where
memory is accessed prior to checking if the pointer is still within a valid
range, which can lead to out-of-bounds reads.
This patch moves the range conditions to appear before the memory accesses in
each conjunction s
