search for: tail_call1

...> "tail calls can only be optimized when [fastcc], the GHC or the HiPE > convention is used." That note in the documentation seems to be incorrect, because LLVM will do tail call optimisations on at least x86 when using the "ccc" calling convention. For example: $ cat tail_call1.c void foo(int arg); void bar(int arg) { foo(arg); } $ clang tail_call1.c -S -o - -O2 ... bar: # @bar ... jmp foo # TAILCALL ... However, LLVM doesn't emit a tail call at -O0. Maybe what the documentation means to say is that ta...

On 2013-07-30 22:11, Eli Bendersky wrote: > we've published an initial version of the PNaCl bitcode reference > manual online - > http://www.chromium.org/nativeclient/pnacl/bitcode-abi. The PNaCl > bitcode is a restricted subset of LLVM IR. > > Any comments would be most welcome. Hi Eli, I appreciate you for opening the process for input and comments. One question stood

Hi Mark, On 2013-08-02 04:11, Mark Seaborn wrote: > That note in the documentation seems to be incorrect, because LLVM > will do tail call optimisations on at least x86 when using the "ccc" > calling convention. For example: > > $ cat tail_call1.c > void foo(int arg); > void bar(int arg) { > foo(arg); > } > > $ clang tail_call1.c -S -o - -O2 > ... > bar: # @bar > ... > jmp foo # TAILCALL > ... That's actually a sibling call, which is a mu...

Hello, Following an earlier email ( http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-June/063010.html), we've published an initial version of the PNaCl bitcode reference manual online - http://www.chromium.org/nativeclient/pnacl/bitcode-abi. The PNaCl bitcode is a restricted subset of LLVM IR. The reference manual is quite terse, so for the bigger picture I'll repost links to the design