-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump QEMU to v8.1.0 #1334
Bump QEMU to v8.1.0 #1334
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, yeah, IIRC I hit that some where before and then I bump my local qemu to latest, but seems like I never create PR to bump that. also this gcc fix are necessary for bare-metal testing, but anyway I am fine to bump that first.
Anyway, LGTM :P
Looks like this causes a few newlib failures - I'll look into why
|
I guess those fails will gone after you apply the fix that I mention before to GCC will drop all fails, if so I am OK to put those fails to allowlist for now. |
After cherry-picking that the GCC fix, all those listed failures are resolved. I've added the failures to the allowlist with a link to the fixing commit. Weirdly enough we get a new failure with the cherry-picked commit, but it's fixed on trunk so I'm not going to worry about it :)
|
Feel free to merge once you think OK :) |
2630024
to
def9c29
Compare
QEMU v7.1.0 has an issue with some vector instructions. This manifests in the (trunk) GCC testsuite with failures like this:
Bumping to v8.1.0 resolves these failures.