- 
                Notifications
    You must be signed in to change notification settings 
- Fork 13.9k
Refactor vtable encoding and optimize it for the case of multiple marker traits #113856
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
    
  
     Merged
                    Changes from all commits
      Commits
    
    
            Show all changes
          
          
            9 commits
          
        
        Select commit
          Hold shift + click to select a range
      
      eabd306
              
                Document `PredicateSet::insert`
              
              
                WaffleLapkin 348f26e
              
                Use `?` in `prepare_vtable_segments`
              
              
                WaffleLapkin f8f5d7a
              
                Replace `if let` with `unwrap` in `prepare_vtable_segments`
              
              
                WaffleLapkin 364fc44
              
                Refactor 'diving_in loop internals in `prepare_vtable_segments`
              
              
                WaffleLapkin d567f0f
              
                Slightly refactor 'exiting_out loop in `prepare_vtable_segments`
              
              
                WaffleLapkin d87db8e
              
                Simplify last `prepare_vtable_segments` loop even more
              
              
                WaffleLapkin f33936c
              
                Fix comment
              
              
                WaffleLapkin b5d1228
              
                Add a (failing test) for issue `113840`
              
              
                WaffleLapkin 1f02c75
              
                Don't emit useless vptrs for marker traits
              
              
                WaffleLapkin File filter
Filter by extension
Conversations
          Failed to load comments.   
        
        
          
      Loading
        
  Jump to
        
          Jump to file
        
      
      
          Failed to load files.   
        
        
          
      Loading
        
  Diff view
Diff view
There are no files selected for viewing
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              | Original file line number | Diff line number | Diff line change | 
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| // Regression test for <https://github.com/rust-lang/rust/issues/113840> | ||
| // | ||
| // This test makes sure that multiple marker (method-less) traits can reuse the | ||
| // same pointer for upcasting. | ||
| // | ||
| // build-fail | ||
| #![crate_type = "lib"] | ||
| #![feature(rustc_attrs)] | ||
|  | ||
| // Markers | ||
| trait M0 {} | ||
| trait M1 {} | ||
| trait M2 {} | ||
|  | ||
| // Just a trait with a method | ||
| trait T { | ||
| fn method(&self) {} | ||
| } | ||
|  | ||
| #[rustc_dump_vtable] | ||
| trait A: M0 + M1 + M2 + T {} //~ error: vtable entries for `<S as A>`: | ||
|  | ||
| #[rustc_dump_vtable] | ||
| trait B: M0 + M1 + T + M2 {} //~ error: vtable entries for `<S as B>`: | ||
|  | ||
| #[rustc_dump_vtable] | ||
| trait C: M0 + T + M1 + M2 {} //~ error: vtable entries for `<S as C>`: | ||
|  | ||
| #[rustc_dump_vtable] | ||
| trait D: T + M0 + M1 + M2 {} //~ error: vtable entries for `<S as D>`: | ||
|  | ||
| struct S; | ||
|  | ||
| impl M0 for S {} | ||
| impl M1 for S {} | ||
| impl M2 for S {} | ||
| impl T for S {} | ||
| impl A for S {} | ||
| impl B for S {} | ||
| impl C for S {} | ||
| impl D for S {} | ||
|  | ||
| pub fn require_vtables() { | ||
| fn require_vtables(_: &dyn A, _: &dyn B, _: &dyn C, _: &dyn D) {} | ||
|  | ||
| require_vtables(&S, &S, &S, &S) | ||
| } | 
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              | Original file line number | Diff line number | Diff line change | 
|---|---|---|
| @@ -0,0 +1,52 @@ | ||
| error: vtable entries for `<S as A>`: [ | ||
| MetadataDropInPlace, | ||
| MetadataSize, | ||
| MetadataAlign, | ||
| Method(<S as T>::method), | ||
| ] | ||
| --> $DIR/multiple-markers.rs:21:1 | ||
| | | ||
| LL | trait A: M0 + M1 + M2 + T {} | ||
| | ^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|  | ||
| error: vtable entries for `<S as B>`: [ | ||
| MetadataDropInPlace, | ||
| MetadataSize, | ||
| MetadataAlign, | ||
| Method(<S as T>::method), | ||
| TraitVPtr(<S as M2>), | ||
| ] | ||
| --> $DIR/multiple-markers.rs:24:1 | ||
| | | ||
| LL | trait B: M0 + M1 + T + M2 {} | ||
| | ^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|  | ||
| error: vtable entries for `<S as C>`: [ | ||
| MetadataDropInPlace, | ||
| MetadataSize, | ||
| MetadataAlign, | ||
| Method(<S as T>::method), | ||
| TraitVPtr(<S as M1>), | ||
| TraitVPtr(<S as M2>), | ||
| ] | ||
| --> $DIR/multiple-markers.rs:27:1 | ||
| | | ||
| LL | trait C: M0 + T + M1 + M2 {} | ||
| | ^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|  | ||
| error: vtable entries for `<S as D>`: [ | ||
| MetadataDropInPlace, | ||
| MetadataSize, | ||
| MetadataAlign, | ||
| Method(<S as T>::method), | ||
| TraitVPtr(<S as M0>), | ||
| TraitVPtr(<S as M1>), | ||
| TraitVPtr(<S as M2>), | ||
| ] | ||
| --> $DIR/multiple-markers.rs:30:1 | ||
| | | ||
| LL | trait D: T + M0 + M1 + M2 {} | ||
| | ^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|  | ||
| error: aborting due to 4 previous errors | ||
|  | ||
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is TraitVPtr needed for M2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The short answer: it is not needed. The longer answer is that we currently keep the order of all things from the traits, so since
M2comes afterT, it can't be inlined there. I've filled #114942 to track this.