Skip to content
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

unrecognized instruction mnemonic on MacOS arm64 #94

Open
huww98 opened this issue Dec 15, 2024 · 0 comments
Open

unrecognized instruction mnemonic on MacOS arm64 #94

huww98 opened this issue Dec 15, 2024 · 0 comments

Comments

@huww98
Copy link

huww98 commented Dec 15, 2024

Describe the bug
Build failure on MacBook Pro 2023, with Apple M2 Pro:

DuckX/test/iterator_tests.cpp:57:5: error: unrecognized instruction mnemonic, did you mean: bit, cnt, hint, ins, not?
   57 |     CHECK_EQ(begin(doc.paragraphs()), begin(doc.paragraphs()));
      |     ^
DuckX/test/doctest.h:2521:18: note: expanded from macro 'CHECK_EQ'
 2521 | #define CHECK_EQ DOCTEST_CHECK_EQ
      |                  ^
DuckX/test/doctest.h:2128:31: note: expanded from macro 'DOCTEST_CHECK_EQ'
 2128 | #define DOCTEST_CHECK_EQ(...) DOCTEST_BINARY_ASSERT(DT_CHECK_EQ, eq, __VA_ARGS__)
      |                               ^
DuckX/test/doctest.h:2104:9: note: expanded from macro 'DOCTEST_BINARY_ASSERT'
 2104 |         DOCTEST_ASSERT_LOG_AND_REACT(_DOCTEST_RB);                                                 \
      |         ^
DuckX/test/doctest.h:1729:9: note: expanded from macro 'DOCTEST_ASSERT_LOG_AND_REACT'
 1729 |         DOCTEST_BREAK_INTO_DEBUGGER();                                                             \
      |         ^
DuckX/test/doctest.h:350:47: note: expanded from macro 'DOCTEST_BREAK_INTO_DEBUGGER'
  350 | #define DOCTEST_BREAK_INTO_DEBUGGER() __asm__("int $3\n" : :)
      |                                               ^
<inline asm>:1:2: note: instantiated into assembly here
    1 |         int $3
      |         ^

To Reproduce
Steps to reproduce the behavior:

  1. build this project

Expected behavior
Build success

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant