Skip to content

ICH: Function unsafety does not affect incr. comp. hash #36914

Closed
@michaelwoerister

Description

@michaelwoerister
Member

Activity

retep998

retep998 commented on Oct 3, 2016

@retep998
Member

Does function unsafety actually affect the generated code? Shouldn't it only affect whether you're allowed to perform certain operations?

michaelwoerister

michaelwoerister commented on Oct 3, 2016

@michaelwoerister
MemberAuthor

I don't think it does yet but it likely will in the future because the compiler will be more conservative regarding optimizations around unsafe code. I think there's some information o that in http://smallcultfollowing.com/babysteps/blog/2016/05/27/the-tootsie-pop-model-for-unsafe-code.

Another thing to consider is that at some point we will cache more than just machine code, so if something influences just analysis, we also have to be able to track it.

added a commit that references this issue on Oct 6, 2016

Rollup merge of rust-lang#36974 - MathieuBordere:mb/36812_ICHFunction…

modified the milestones: Launch MIR into Orbit, Incremental compilation alpha on Oct 12, 2016
michaelwoerister

michaelwoerister commented on Oct 18, 2016

@michaelwoerister
MemberAuthor

Fixed by #36974 with additional tests in #37072.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-incr-compArea: Incremental compilation

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @nikomatsakis@retep998@michaelwoerister

        Issue actions

          ICH: Function unsafety does not affect incr. comp. hash · Issue #36914 · rust-lang/rust