Summary: | Wrong setjmp return value in FreeBSD 13 (at least on aarch64) | ||
---|---|---|---|
Product: | Base System | Reporter: | Philipp <pkk> |
Component: | misc | Assignee: | freebsd-bugs (Nobody) <bugs> |
Status: | Closed FIXED | ||
Severity: | Affects Many People | CC: | alois+freebsd, emaste, grahamperrin |
Priority: | --- | Keywords: | needs-qa |
Version: | 13.0-RELEASE | ||
Hardware: | Any | ||
OS: | Any | ||
See Also: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268521 |
Description
Philipp
2021-04-22 08:21:17 UTC
On FreeBSD's arm64 reference system I do not reproduce a problem FreeBSD ref13-amd64.nyi.freebsd.org 13.0-STABLE FreeBSD 13.0-STABLE #0 stable/13-n245208-5d02b30ebd8: Tue Apr 13 09:30:31 UTC 2021 root@build-13.freebsd.org:/usr/obj/usr/src/sys/CLUSTER13 amd64 FreeBSD clang version 11.0.1 (git@github.com:llvm/llvm-project.git llvmorg-11.0.1-0-g43ff75f2c3fe) Target: x86_64-unknown-freebsd13.0 Thread model: posix InstalledDir: /usr/bin ref13-amd64% cc test.c ref13-amd64% ./a.out ref13-amd64% I can still reproduce the issue on my Raspi 4 after upgrading to FreeBSD 13.1. I can confirm that this still affects aarch64 as of the FreeBSD CURRENT main branch. I have a patch and test case at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268521. This works for me now (FreeBSD 13.2). Looks like the following commit fixed it: https://cgit.freebsd.org/src/commit/?id=9fb118bebced1452a46756a13be0161021b10905 Thank you for identifying the commit. |