Skip to content

Remove #pragma that disables optimization on _PyEval_EvalFrameDefault on MSVC #129244

Closed

Description

@mdboom

Feature or enhancement

Proposal:

The bug that caused a compiler crash has now been fixed upstream. We should remove our workaround to disable optimization on PGO builds on MSVC (and presumably get a modest speedup).

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

No response

Linked PRs

Activity

  1. self-assigned this
    on Jan 23, 2025
  2. added a commit that references this issue on Jan 25, 2025
  3. itamaro commented on Jan 25, 2025

    @itamaro
    Contributor

    Looks like this is done, closing.

  4. reopened this on Feb 11, 2025
  5. ambv commented on Feb 11, 2025

    @ambv
    Contributor

    This will have to be reverted for now as the 3.14.0a5 build is failing.

  6. ambv commented on Feb 11, 2025

    @ambv
    Contributor

    See #130004.

  7. ambv commented on Feb 11, 2025

    @ambv
    Contributor

    As we are using the Azure Pipelines VMs to build, we are not controlling the version of the compiler and so far the version available on the image we're using (2025020.1.0 with Visual Studio 2022 17.12.12+1cce77968) there does not have the fix.

    @mdboom do you know which VS version would be sufficient to reintroduce the change from this ticket?

  8. mdboom commented on Feb 11, 2025

    @mdboom
    ContributorAuthor

    The minimum version of cl.exe required is 19.43.34618, which is currently in prerelease. I was under the (wrong) impression that this would be backported to the maintenance branch, which is why I submitted the PR. We can add a version check now so that when this does eventually make it into a primary release, we will be ready.

  9. Fidget-Spinner commented on Feb 11, 2025

    @Fidget-Spinner
    Member

    Marking as deferred blocker so we don't forget to fix this by 3.14 final.

  10. added a commit that references this issue on Feb 11, 2025
  11. chris-eibl commented on Feb 11, 2025

    @chris-eibl
    Member

    Upgrading to Visual Studio 2022 17.13.0 Preview 5.0, which ships with cl.exe 19.43.34808, works for me.
    I had those issues on 17.12.4 and 17.12.3, too.

  12. added a commit that references this issue on Feb 11, 2025
  13. encukou commented on Feb 17, 2025

    @encukou
    Member

    With #130011 merged, can this be closed?

  14. hugovk commented on Mar 14, 2025

    @hugovk
    Member

    No-one objected in a month, let's close. Please re-open if still needed.

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

Metadata

Metadata

Assignees

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions