Skip to content

item-bodies/item-types timings regressed for issue-32062-equality-relations #33889

Description

@nagisa

See this and this.

Activity

  1. added
    I-slowIssue: Problems and improvements with respect to performance of generated code.
    on May 26, 2016
  2. nagisa commented on May 26, 2016

    @nagisa
    MemberAuthor
  3. jonas-schievink commented on May 26, 2016

    @jonas-schievink
    Contributor
  4. Marwes commented on May 27, 2016

    @Marwes
    Contributor

    While testing #33816 on my projects I figured I'd run through this example on that version of rustc as well and it seems it doesn't seem to give this slowdown and given that #33816 seems to be rebased on top of master after this slowdown occurred it might have been fixed by that PR (if only by chance?). I may take a look at this sometime this weekend if I get the time though as it still seems unfortunate. (It would be really nice if perf.rust-lang.org could display the commit hash of each run it does. That would make it much easier to pin down which version introduced a regression).

  5. nikomatsakis commented on Jun 2, 2016

    @nikomatsakis
    Contributor

    Probably the same problem is causing a regr in jld-day15-parser

  6. nikomatsakis commented on Jun 2, 2016

    @nikomatsakis
    Contributor

    triage: P-high

  7. nikomatsakis commented on Jun 2, 2016

    @nikomatsakis
    Contributor

    It'd be great to do some sort of bisection to try to narrow down what is causing this.

  8. self-assigned this
    on Jun 2, 2016
  9. added
    I-compiletimeIssue: Problems and improvements with respect to compile times.
    and removed
    I-slowIssue: Problems and improvements with respect to performance of generated code.
    on Jun 3, 2016
  10. eddyb commented on Jun 4, 2016

    @eddyb
    Contributor

    @nikomatsakis Doesn't look like it, the regression is in translation for jld-day15-parser.

  11. arielb1 commented on Jun 4, 2016

    @arielb1
    Contributor

    The problematic PR here is 75e23e1 (#33137). Seems logical - that probably broke the caching

  12. eddyb commented on Jun 4, 2016

    @eddyb
    Contributor

    @arielb1 So the solution is to move forward with #33816?

  13. arielb1 commented on Jun 4, 2016

    @arielb1
    Contributor

    That sounds like it.

  14. arielb1 commented on Jun 5, 2016

    @arielb1
    Contributor

    This is fixed as #33816 landed.

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

Metadata

Metadata

Assignees

Labels

A-type-systemArea: Type systemI-compiletimeIssue: Problems and improvements with respect to compile times.P-highHigh priority

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions