search for: metadatavar

Displaying 7 results from an estimated 7 matches for "metadatavar".

2015 Jan 13
3
[LLVMdev] [RFC] First-class debug info IR: MDLocation (redux)
...n: 7, scope: !4) Now it's: !6 = !MDLocation(line: 43, column: 7, scope: !4) Here's why: - Dropped 'metadata' since `Metadata` is now typeless \O/. - Added a '!' since it makes the parser simpler (no changes to the lexer, since we can unambiguously reuse the `MetadataVar` token), and follows the rule that "All metadata are identified in syntax by a[n] exclamation point" [3]. (If people are opposed to the extra '!' I can update this sentence instead, but it seems like a handy mnemonic to maintain.) [3]: http://llvm.org/docs/LangRe...
2015 Jan 13
2
[LLVMdev] [RFC] First-class debug info IR: MDLocation (redux)
...!6 = !MDLocation(line: 43, column: 7, scope: !4) > > Here's why: > > - Dropped 'metadata' since `Metadata` is now typeless \O/. > > - Added a '!' since it makes the parser simpler (no changes to the > lexer, since we can unambiguously reuse the `MetadataVar` token), > and follows the rule that "All metadata are identified in syntax by > a[n] exclamation point" [3]. (If people are opposed to the extra > '!' I can update this sentence instead, but it seems like a handy > mnemonic to maintain.) > > [3]...
2015 Jan 13
2
[LLVMdev] [RFC] First-class debug info IR: MDLocation (redux)
...!6 = !MDLocation(line: 43, column: 7, scope: !4) > > Here's why: > > - Dropped 'metadata' since `Metadata` is now typeless \O/. > > - Added a '!' since it makes the parser simpler (no changes to the > lexer, since we can unambiguously reuse the `MetadataVar` token), > and follows the rule that "All metadata are identified in syntax by > a[n] exclamation point" [3]. (If people are opposed to the extra > '!' I can update this sentence instead, but it seems like a handy > mnemonic to maintain.) > > [3...
2010 Feb 11
0
[LLVMdev] Metadata
On Wednesday 10 February 2010 14:58:58 Dan Gohman wrote: > On Feb 10, 2010, at 12:42 PM, David Greene wrote: > > On Wednesday 10 February 2010 12:58:25 Chris Lattner wrote: > >> I think that adding a bit to LoadSDNode and StoreSDNode would make > >> sense. > > > > Ok. The consequence is that a number of functions will have to change to > > propagate
2010 Feb 10
3
[LLVMdev] Metadata
On Feb 10, 2010, at 12:42 PM, David Greene wrote: > On Wednesday 10 February 2010 12:58:25 Chris Lattner wrote: > >> I think that adding a bit to LoadSDNode and StoreSDNode would make sense. > > Ok. The consequence is that a number of functions will have to change to > propagate this bit, analogous to what happens with isVolatile. It's > essentially what we do
2010 Feb 11
3
[LLVMdev] Metadata
...xcess comma at the /// end. bool LLParser::ParseOptionalCommaAlign(unsigned &Alignment, bool &AteExtraComma) { AteExtraComma = false; while (EatIfPresent(lltok::comma)) { // Metadata at the end is an early exit. if (Lex.getKind() == lltok::MetadataVar) { AteExtraComma = true; return false; } if (Lex.getKind() == lltok::kw_align) { if (ParseOptionalAlignment(Alignment)) return true; } else return true; } return false; } Either ParseLoad and probably other instructions need to look for metadata explic...
2015 Jan 15
2
[LLVMdev] [RFC] First-class debug info IR: MDLocation (redux)
...t;>> >>> Here's why: >>> >>> - Dropped 'metadata' since `Metadata` is now typeless \O/. >>> >>> - Added a '!' since it makes the parser simpler (no changes to the >>> lexer, since we can unambiguously reuse the `MetadataVar` token), >>> and follows the rule that "All metadata are identified in syntax by >>> a[n] exclamation point" [3]. (If people are opposed to the extra >>> '!' I can update this sentence instead, but it seems like a handy >>> mnemonic...