Skip to content

Conversation

@arsenm
Copy link
Contributor

@arsenm arsenm commented Nov 8, 2025

No description provided.

Copy link
Contributor Author

arsenm commented Nov 8, 2025

This stack of pull requests is managed by Graphite. Learn more about stacking.

@arsenm arsenm force-pushed the users/arsenm/runtime-libcalls/add-memcpy-memmove-memset-chk-functions branch from 31b8490 to e551019 Compare November 10, 2025 18:18
@arsenm arsenm force-pushed the users/arsenm/runtime-libcalls/add-mustprogress-common-fn-attrs branch from 47b2103 to 238ad7d Compare November 10, 2025 18:18
@arsenm arsenm force-pushed the users/arsenm/runtime-libcalls/add-memcpy-memmove-memset-chk-functions branch from e551019 to 9b770d3 Compare November 10, 2025 19:22
@arsenm arsenm force-pushed the users/arsenm/runtime-libcalls/add-mustprogress-common-fn-attrs branch 2 times, most recently from ad1d7cb to b7cc28e Compare November 12, 2025 00:57
@arsenm arsenm force-pushed the users/arsenm/runtime-libcalls/add-memcpy-memmove-memset-chk-functions branch from 9b770d3 to abbd23c Compare November 12, 2025 00:57
@arsenm arsenm force-pushed the users/arsenm/runtime-libcalls/add-mustprogress-common-fn-attrs branch from b7cc28e to ddc5a54 Compare November 12, 2025 02:11
@arsenm arsenm force-pushed the users/arsenm/runtime-libcalls/add-memcpy-memmove-memset-chk-functions branch from 06269dd to abf1fe1 Compare November 12, 2025 03:24
@arsenm arsenm force-pushed the users/arsenm/runtime-libcalls/add-mustprogress-common-fn-attrs branch from ddc5a54 to 22df2fb Compare November 12, 2025 03:24
@arsenm
Copy link
Contributor Author

arsenm commented Nov 21, 2025

ping

Copy link
Collaborator

@RKSimon RKSimon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - but I don't know all the idiosyncrasies of mustprogress tbh, but the language reference suggests this should be fine.

These are floating-point functions recorded in TargetLibraryInfo,
but missing from RuntimeLibcalls.
These were in TargetLibraryInfo, but missing from RuntimeLibcalls.
This only adds the cases that already have the non-chk variants
already. Copies the enabled-by-default logic from TargetLibraryInfo,
which is probably overly permissive. Only isPS opts-out.
@arsenm arsenm force-pushed the users/arsenm/runtime-libcalls/add-mustprogress-common-fn-attrs branch from 22df2fb to a921be6 Compare November 25, 2025 13:43
@arsenm arsenm force-pushed the users/arsenm/runtime-libcalls/add-memcpy-memmove-memset-chk-functions branch from abf1fe1 to 65e64a8 Compare November 25, 2025 13:43
Base automatically changed from users/arsenm/runtime-libcalls/add-memcpy-memmove-memset-chk-functions to main November 25, 2025 14:39
@arsenm arsenm merged commit eb5297e into main Nov 25, 2025
13 of 17 checks passed
@arsenm arsenm deleted the users/arsenm/runtime-libcalls/add-mustprogress-common-fn-attrs branch November 25, 2025 14:48
@nikic
Copy link
Contributor

nikic commented Dec 2, 2025

I'm confused by this change -- why are we adding mustprogress? For intrinsics willreturn is the relevant attribute, and it's already set.

@arsenm
Copy link
Contributor Author

arsenm commented Dec 2, 2025

I'm confused by this change -- why are we adding mustprogress? For intrinsics willreturn is the relevant attribute, and it's already set.

These aren't intrinsics, they're libcall function declarations?

@nikic
Copy link
Contributor

nikic commented Dec 2, 2025

I'm confused by this change -- why are we adding mustprogress? For intrinsics willreturn is the relevant attribute, and it's already set.

These aren't intrinsics, they're libcall function declarations?

Same thing. The purpose of mustprogress is to allow inferring willreturn. It is not useful for declarations that are willreturn anyway.

The PR has no description, can you please explain what the motivation here was?

augusto2112 pushed a commit to augusto2112/llvm-project that referenced this pull request Dec 3, 2025
kcloudy0717 pushed a commit to kcloudy0717/llvm-project that referenced this pull request Dec 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants