tcc-doc.texi: Explain VT_LLOCAL a bit better.
And delete the sentence about it being removed.
This commit is contained in:
		
							parent
							
								
									ff3f9aa6ba
								
							
						
					
					
						commit
						86c850fc58
					
				
					 1 changed files with 4 additions and 2 deletions
				
			
		| 
						 | 
				
			
			@ -1180,8 +1180,10 @@ if the lvalue has an integer type, then these flags give its real
 | 
			
		|||
type. The type alone is not enough in case of cast optimisations.
 | 
			
		||||
 | 
			
		||||
@item VT_LLOCAL
 | 
			
		||||
is a saved lvalue on the stack. @code{VT_LLOCAL} should be eliminated
 | 
			
		||||
ASAP because its semantics are rather complicated.
 | 
			
		||||
is a saved lvalue on the stack. @code{VT_LVAL} must also be set with
 | 
			
		||||
@code{VT_LLOCAL}. @code{VT_LLOCAL} can arise when a @code{VT_LVAL} in
 | 
			
		||||
a register has to be saved to the stack, or it can come from an
 | 
			
		||||
architecture-specific calling convention.
 | 
			
		||||
 | 
			
		||||
@item VT_MUSTCAST
 | 
			
		||||
indicates that a cast to the value type must be performed if the value
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
	Add table
		
		Reference in a new issue