llvm-mirror/test/Assembler/inalloca.ll

; RUN: llvm-as %s -o /dev/null
; RUN: verify-uselistorder %s

define void @a() {
entry:
  %0 = alloca inalloca i32
  %1 = alloca inalloca [2 x i32]
  %2 = alloca inalloca i32, i32 2
  %3 = alloca inalloca i32, i32 2, align 16
  %4 = alloca inalloca i32, i32 2, align 16, !foo !0
  %5 = alloca i32, i32 2, align 16, !foo !0
  %6 = alloca i32, i32 2, align 16
  ret void
}

!0 = metadata !{i32 662302, null}
!foo = !{ !0 }
Add an inalloca flag to allocas Summary: The only current use of this flag is to mark the alloca as dynamic, even if its in the entry block. The stack adjustment for the alloca can never be folded into the prologue because the call may clear it and it has to be allocated at the top of the stack. Reviewers: majnemer CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D2571 llvm-svn: 199525 2014-01-18 00:58:17 +01:00			`; RUN: llvm-as %s -o /dev/null`
verify-uselistorder: Force -preserve-bc-use-list-order llvm-svn: 216022 2014-08-19 23:08:27 +02:00			`; RUN: verify-uselistorder %s`
Add an inalloca flag to allocas Summary: The only current use of this flag is to mark the alloca as dynamic, even if its in the entry block. The stack adjustment for the alloca can never be folded into the prologue because the call may clear it and it has to be allocated at the top of the stack. Reviewers: majnemer CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D2571 llvm-svn: 199525 2014-01-18 00:58:17 +01:00
			`define void @a() {`
			`entry:`
IR: Change inalloca's grammar a bit The grammar for LLVM IR is not well specified in any document but seems to obey the following rules: - Attributes which have parenthesized arguments are never preceded by commas. This form of attribute is the only one which ever has optional arguments. However, not all of these attributes support optional arguments: 'thread_local' supports an optional argument but 'addrspace' does not. Interestingly, 'addrspace' is documented as being a "qualifier". What constitutes a qualifier? I cannot find a definition. - Some attributes use a space between the keyword and the value. Examples of this form are 'align' and 'section'. These are always preceded by a comma. - Otherwise, the attribute has no argument. These attributes do not have a preceding comma. Sometimes an attribute goes before the instruction, between the instruction and it's type, or after it's type. 'atomicrmw' has 'volatile' between the instruction and the type while 'call' has 'tail' preceding the instruction. With all this in mind, it seems most consistent for 'inalloca' on an 'inalloca' instruction to occur before between the instruction and the type. Unlike the current formulation, there would be no preceding comma. The combination 'alloca inalloca' doesn't look particularly appetizing, perhaps a better spelling of 'inalloca' is down the road. llvm-svn: 203376 2014-03-09 07:41:58 +01:00			`%0 = alloca inalloca i32`
			`%1 = alloca inalloca [2 x i32]`
			`%2 = alloca inalloca i32, i32 2`
			`%3 = alloca inalloca i32, i32 2, align 16`
			`%4 = alloca inalloca i32, i32 2, align 16, !foo !0`
Add an inalloca flag to allocas Summary: The only current use of this flag is to mark the alloca as dynamic, even if its in the entry block. The stack adjustment for the alloca can never be folded into the prologue because the call may clear it and it has to be allocated at the top of the stack. Reviewers: majnemer CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D2571 llvm-svn: 199525 2014-01-18 00:58:17 +01:00			`%5 = alloca i32, i32 2, align 16, !foo !0`
			`%6 = alloca i32, i32 2, align 16`
			`ret void`
			`}`

			`!0 = metadata !{i32 662302, null}`
			`!foo = !{ !0 }`