- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1.8k
Ruby: enable overlay compilation #19731
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
Conversation
4875dcb    to
    3d78f35      
    Compare
  
    04c2743    to
    f29f327      
    Compare
  
    c9e7be7    to
    c968a95      
    Compare
  
    f29f327    to
    b96dc5a      
    Compare
  
    e36a625    to
    a9ddf00      
    Compare
  
    b96dc5a    to
    6fcb669      
    Compare
  
    2c0ac5e    to
    770dd30      
    Compare
  
    6fcb669    to
    14b6c47      
    Compare
  
    770dd30    to
    4a725ba      
    Compare
  
    14b6c47    to
    b4ab74b      
    Compare
  
    4a725ba    to
    3c4a528      
    Compare
  
    b4ab74b    to
    55f9231      
    Compare
  
    1eda55d    to
    e1f2433      
    Compare
  
    55f9231    to
    ab9ba02      
    Compare
  
    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.
Pull Request Overview
This PR enables overlay compilation for the Ruby CodeQL library by adding the compileForOverlayEval: true configuration option to the qlpack.yml file. This change allows the Ruby library to be compiled in a way that supports overlay evaluation, which is typically used for performance optimization or dynamic analysis scenarios.
- Adds overlay compilation capability to the Ruby CodeQL library
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.
From the Foundations team, I believe we are ready to enable overlay compilation. In theory, this should not affect the semantics for non-overlay evaluation but may affect performance of non-overlay evaluation. DCA shows no alert differences (though DCA skips rb/polynomial-redos for jeremyevans__sequel for both base and variant due to the number of results) and a slight speedup.
DIL size increases significantly for several queries. I sampled a few queries and didn't see anything concerning.
Stacked on top of #19989