- 
                Notifications
    You must be signed in to change notification settings 
- Fork 13.9k
          add enable-warnings flag for llvm, and disable it by default.
          #108991
        
          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
| (rustbot has picked a reviewer for you, use r? to override) | 
        
          
                src/bootstrap/native.rs
              
                Outdated
          
        
      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.
enable-warnings flag for llvmenable-warnings flag for llvm and update llvm defaults of config.user.toml
      49691b5    to
    71ab299      
    Compare
  
    | I think you might be interested looking 2nd commit of this PR @jyn514 | 
enable-warnings flag for llvm and update llvm defaults of config.user.tomlenable-warnings flag for llvm
      8dd1629    to
    71ab299      
    Compare
  
    | I think the  | 
| 
 Agree for codegen, but I am not sure about that CI checking warnings | 
| This PR changes src/bootstrap/defaults/config.codegen.toml. If appropriate, please also update  | 
03097c2    to
    507a15c      
    Compare
  
    | I'm misreading, or it should be  | 
| 
 Currently, it's always on. With this PR, we are able to turn it off. The explanation doesn't target the default value or how the flag works. It explains what this PR brings. | 
| ☔ The latest upstream changes (presumably #109056) made this pull request unmergeable. Please resolve the merge conflicts. | 
507a15c    to
    857685a      
    Compare
  
    | Can you add an entry to the changelog please (it is located in  | 
04337f0    to
    ab65baa      
    Compare
  
    | @rustbot ready | 
Signed-off-by: ozkanonur <work@onurozkan.dev>
c14b7ff    to
    2e7249f      
    Compare
  
    | Thanks for the PR! | 
| @bors r+ | 
| 
 
 And now it will be default off, or I'm wrong (maybe i read bootstrap code wrong)? Oh, so it is changes defaults. | 
| The warnings will be off by default, except when using the  | 
| 
 Yes, but title says only about adding ability to switch warning, not changing it's current behavior (see my first message). | 
| The title is not the source of truth. | 
enable-warnings flag for llvmenable-warnings flag for llvm, and enable it by default.
      enable-warnings flag for llvm, and enable it by default.enable-warnings flag for llvm, and disable it by default.
      | 
 You can't change the behaviour of llvm compilation warnings without the changes this PR provides. PR doesn't just turn off warnings automatically. It gives the ability of switching llvm compilation warnings on and off. | 
Rollup of 7 pull requests Successful merges: - rust-lang#108991 (add `enable-warnings` flag for llvm, and disable it by default.) - rust-lang#109109 (Use `unused_generic_params` from crate metadata) - rust-lang#109111 (Create dirs for build_triple) - rust-lang#109136 (Simplify proc macro signature validity check) - rust-lang#109150 (Update cargo) - rust-lang#109154 (Fix MappingToUnit to support no span of arg_ty) - rust-lang#109157 (Remove mw from review rotation for a while) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
This flag allows to turn off warnings of llvm compilation for people who are not interested on those warnings.