Tom Wijsman <[email protected]> added the comment: I want to help if it doesn't involve hours of time; so, I was wondering if there is an easy way to just replicate the error without having to rebuild pypy every time. Switching from -march=native (picks corei7) to -march=x86-64 made it build; per the suggestion from someone else, but it would be nice to have it build in a native way to avoid people in the future from experiencing this again.
So, what is a minimal test case to find more of such instructions? ---------- status: resolved -> chatting ________________________________________ PyPy bug tracker <[email protected]> <https://bugs.pypy.org/issue1587> ________________________________________ _______________________________________________ pypy-issue mailing list [email protected] http://mail.python.org/mailman/listinfo/pypy-issue
