search for: addfoo

...t; No, the value will be discovered at link time, but we want instruction selection to treat the symbol as an immediate, not a GlobalAddress that will receive PIC and GOT treatment. If we use a declaration as you suggest, this example will compile awkwardly: @foo = external global i8 define i64 @addfoo(i64 %v) { %cast = ptrtoint i8* @foo to i64 %v1 = add i64 %v, %cast ret i64 %v1 } The ideal code is: addfoo: leaq foo(%rdi), %rax retq Today we select: addfoo: addq foo at GOTPCREL(%rip), %rdi movq %rdi, %rax retq We could use attributes to try to convince...

On Tue, Oct 25, 2016 at 5:49 AM, Rafael Espíndola < rafael.espindola at gmail.com> wrote: > >>> @foo = globalconst i32 42 > >>> > >>> > >>> This is equivalent to writing "foo = 42" in assembly? > >> > >> > >> Yes. > > > > > > Back in the day the idea was to use an alias whose ConstantExpr

...t asking for merge conflicts (e.g. > AMDGPUSubtarget has a ton of fields in it, and out of tree code is > constantly adding new fields for unreleased subtargets). It also mangles > BuildMI calls, where I believe every .add() should be on its own line, and > stringing this into BuildMI().addFoo().addBar() is way less readable. > > I also believe it’s 4 space indent on line wraps differs from the stated 2 > space indent level (and this also disagrees with emacs llvm-style) > > -Matt > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http...

(Copying from Discourse) All A couple of months ago I added the following page documentation Clang-Formatted-Status <http://clang.llvm.org/docs/ClangFormattedStatus.html> to track the status of “How Much” clang-formatted the LLVM/Clang project is. I’m a contributor to clang-format and would like to see LLVM 100% clang formatted so we can use LLVM as a massive test-suite for clang-format