Skip to content

Add support for __fp16 where appropriate #8323

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

Merged
merged 1 commit into from
Jun 11, 2024

Conversation

tautschnig
Copy link
Collaborator

GCC supports this since version 4.5 (but only on ARM platforms), Clang supports it since version 6 on all targets.

  • Each commit message has a non-empty body, explaining why the change was made.
  • n/a Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • n/a The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • n/a My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.

GCC supports this since version 4.5 (but only on ARM platforms), Clang
supports it since version 6 on all targets.
@kroening kroening assigned tautschnig and unassigned kroening Jun 11, 2024
@tautschnig tautschnig assigned feliperodri and unassigned tautschnig Jun 11, 2024
@kroening kroening merged commit 9df8637 into diffblue:develop Jun 11, 2024
36 of 38 checks passed
@tautschnig tautschnig deleted the features/__fp16 branch June 11, 2024 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants