- 
                Notifications
    You must be signed in to change notification settings 
- Fork 15k
[clang][RISCV] support BITINT with mixed-type #156592
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 7 commits
      Commits
    
    
            Show all changes
          
          
            8 commits
          
        
        Select commit
          Hold shift + click to select a range
      
      0927005
              
                [clang][RISCV] support BITINT with mixed-type
              
              
                BeMg 2629dac
              
                Update format
              
              
                BeMg db42cea
              
                Refine the comment
              
              
                BeMg a2c03fa
              
                Drop the curly braces
              
              
                BeMg ded0caf
              
                Use Indirect when Size > 2 * XLEN
              
              
                BeMg 04d20af
              
                Add test for RV32 and fforce-enable-int128
              
              
                BeMg ca6cae9
              
                Make RV64 _BitInt(32) always signext
              
              
                BeMg 5333575
              
                !fixup update format
              
              
                BeMg 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
    
  
  
    
              
      
      Oops, something went wrong.
        
    
  
      
      Oops, something went wrong.
        
    
  
  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.
Can we call
extendTypehere and remove the special case for 32 above? Looks like extendType will call ABIArgInfo::getExtend if its not the special case.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.
There's something a bit strange happening here.
will be treated as 32 in
If we use the
extendTypedirectly,unsigned _BitInt(17)will turn into a signed extension in this case.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.
I'm guessing the call to
getContext().getTypeSize(Ty)in that function returned the size rounded up to a byte.I guess we can leave it how you have it then.