Skip to content

Conversation

@jpsamaroo
Copy link
Member

Fixes #364

@jpsamaroo jpsamaroo added bug Something isn't working upstream labels Oct 26, 2022
@jpsamaroo jpsamaroo requested a review from maleadt October 26, 2022 21:11
@maleadt
Copy link
Member

maleadt commented Oct 27, 2022

Maybe use a NamedTuple or Dict you conditionally append the new parameter to, and splat that when calling the CodegenParams ctor, just to avoid some duplication. But LGTM otherwise.

@jpsamaroo jpsamaroo force-pushed the jps/no-entry-safepoints branch from f473c87 to d8e725d Compare October 28, 2022 13:09
@jpsamaroo jpsamaroo merged commit f5a0645 into master Oct 31, 2022
@jpsamaroo jpsamaroo deleted the jps/no-entry-safepoints branch October 31, 2022 17:28
@pxl-th
Copy link
Member

pxl-th commented Nov 1, 2022

Can we also tag a release to fix crashing CIs?

debug_info_kind = Cint(debug_info_kind),
lookup = Base.unsafe_convert(Ptr{Nothing}, lookup_cb))
@static if VERSION >= v"1.9.0-DEV.1660"
cgparams = merge(cgparams, (;safepoint_on_entry = false))
Copy link
Member

Choose a reason for hiding this comment

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

Nit, this is not high-priority. But the CPU users like Enzyme would actually want these to be emitted. So it needs to be job-dependent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working upstream

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Adapt to function entry safepoint changes

5 participants