Re: lang/gbc write overflow

2024-04-02 Thread Theo Buehler
> Also delete BROKEN-sparc64, but I don't have a sparc64. I suspect > that (yy_size_t *)&result was not a multiple of 8 and raised a SIGBUS > for misalignment on sparc64, but I don't know. It did. I tried a while back and ended up using bc-gh in libcrypto regress because it works on all architect

Re: lang/gbc write overflow

2024-04-01 Thread George Koehler
On Mon, 1 Apr 2024 08:36:08 -0400 "Ivan \"Rambius\" Ivanov" wrote: > Ok from me. I committed the patch. My subject was wrong; port is math/gbc, not lang/gbc.

Re: lang/gbc write overflow

2024-04-01 Thread Ivan "Rambius" Ivanov
Ok from me. On Wed, Mar 27, 2024, 7:04 PM George Koehler wrote: > Here's a diff to fix GNU bc 1.07.1 in OpenBSD ports. > > Wrong code in bc/scan.c was using (yy_size_t *)&result to write to an > int. This was an overflow on LP64_ARCHS, by writing 8 bytes to a > 4-byte int. The problem was more

lang/gbc write overflow

2024-03-27 Thread George Koehler
Here's a diff to fix GNU bc 1.07.1 in OpenBSD ports. Wrong code in bc/scan.c was using (yy_size_t *)&result to write to an int. This was an overflow on LP64_ARCHS, by writing 8 bytes to a 4-byte int. The problem was more obvious when big-endian. If we would read 51 bytes, - a little-endian amd