search for: cconv

Hi, 3.5.1-rc1 has been tagged, so it is time to begin testing. We can always use more testers, so if you would like to volunteer, let me know. For those that are new to testing, please review the documentation for how validate a new release: http://llvm.org/docs/ReleaseProcess.html Remember that when we check for regressions we want to compare the test results of 3.5.1-rc1 with 3.5.0-final.

...eGen/AMDGPU/smrd.ll > LLVM :: CodeGen/AMDGPU/unhandled-loop-condition-assertion.ll > LLVM :: CodeGen/ARM/build-attributes.ll > LLVM :: CodeGen/ARM/float-helpers.s > LLVM :: CodeGen/ARM/select-imm.ll > LLVM :: CodeGen/ARM/struct_byval_arm_t1_t2.ll > LLVM :: CodeGen/Mips/cconv/arguments-float.ll > LLVM :: CodeGen/Mips/cconv/arguments-hard-float-varargs.ll > LLVM :: CodeGen/Mips/cconv/arguments-hard-float.ll > LLVM :: CodeGen/Mips/cconv/arguments-varargs.ll > LLVM :: CodeGen/Mips/cconv/arguments.ll > LLVM :: CodeGen/Mips/cconv/return-hard-fp128.ll...

...to build on the 3.5 > branch. I'm not sure how it ever worked before, but I need to merge > r220117 to make it work. > > I also got two test failures. I haven't checked yet if they also occur > in 3.5, but I'm not sure they matter on Windows: > > LLVM: CodeGen/Mips/cconv/arguments-struct.ll > Clang: Modules/compiler_builtins.m > > I've uploaded it to the sftp: > LLVM-3.5.1-rc1-win32.exe > sha1: 3c3892daa5119e60ee7b0917c4c1ac8251a949c6 > > - Hans > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http:/...

2014-12-15 13:00 GMT+01:00 Daniel Sanders <Daniel.Sanders at imgtec.com>: >> LLVM: CodeGen/Mips/cconv/arguments-struct.ll > > Do you have the verbose lit output for this test? > I ran it again in verbose mode, but there were no additional outputs. Cheers, Sebastian

...Sebastian Dreßler >> Sent: 15 December 2014 14:08 >> Cc: Ben Pope; Nikola Smiljanic; llvmdev >> Subject: Re: [LLVMdev] 3.5.1 Testing Phase Begins >> >> 2014-12-15 13:00 GMT+01:00 Daniel Sanders <Daniel.Sanders at imgtec.com>: >>>> LLVM: CodeGen/Mips/cconv/arguments-struct.ll >>> >>> Do you have the verbose lit output for this test? >>> >> >> I ran it again in verbose mode, but there were no additional outputs. >> >> Cheers, >> Sebastian > > Just to double check: Is that with -v or -...

...) is for obtaining the operands only. There is no dedicated method to obtain the result. {I was expecting something like Instruction->getResult().} Instruction * Inst; ... Value * Res = Inst; Is the above the right way to do the work? For an other example: <result> = [tail] call [cconv <http://llvm.org/docs/LangRef.html#callingconv>] [ret attrs <http://llvm.org/docs/LangRef.html#paramattrs>]<ty> [<fnty>*]<fnptrval>(<function args>) [fn attrs <http://llvm.org/docs/LangRef.html#fnattrs>] According to the LLVM Language reference, CallI...

I'd like to (re)start a discussion on a few gotchas in FileCheck that I've noticed working on various tests in llvm's suites. This begain in a review [1], but I'll try to summarize here so it gets the right audience before decisions are made on it (so to speak). 1: https://reviews.llvm.org/D77227 The main sticking point is the abundance of checks in FileCheck tests that appear to

...in several hundred lines of duplicated code. This patch refines the copies so that diff reveals refactoring opportunities instead of noise. Okay to commit? (My goal is to introduce a crazy new ABI.) — Gordon -------------- next part -------------- A non-text attachment was scrubbed... Name: cconv.patch Type: application/octet-stream Size: 22971 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20071231/4368eace/attachment.obj> -------------- next part --------------

...icated method to obtain the result. > {I was expecting something like Instruction->getResult().} > > > Instruction * Inst; > ... > Value * Res = Inst; > > Is the above the right way to do the work? > > For an other example: > > <result> = [tail] call [cconv <http://llvm.org/docs/LangRef.html#callingconv>] [ret attrs <http://llvm.org/docs/LangRef.html#paramattrs>]<ty> [<fnty>*]<fnptrval>(<function args>) [fn attrs <http://llvm.org/docs/LangRef.html#fnattrs>] > > > According to the LLVM Language ref...

...test/CodeGen/Hexagon/tail-call-mem-intrinsics.ll > llvm/trunk/test/CodeGen/MSP430/memset.ll > llvm/trunk/test/CodeGen/Mips/2012-12-12-ExpandMemcpy.ll > llvm/trunk/test/CodeGen/Mips/Fast-ISel/memtest1.ll > llvm/trunk/test/CodeGen/Mips/biggot.ll > llvm/trunk/test/CodeGen/Mips/cconv/arguments-small-structure > s-bigger-than-32bits.ll > llvm/trunk/test/CodeGen/Mips/cconv/arguments-varargs-small-s > tructs-byte.ll > llvm/trunk/test/CodeGen/Mips/cconv/arguments-varargs-small-s > tructs-combinations.ll > llvm/trunk/test/CodeGen/Mips/cconv/return-struct.ll &...

...k-object.ll llvm/trunk/test/CodeGen/Hexagon/tail-call-mem-intrinsics.ll llvm/trunk/test/CodeGen/MSP430/memset.ll llvm/trunk/test/CodeGen/Mips/2012-12-12-ExpandMemcpy.ll llvm/trunk/test/CodeGen/Mips/Fast-ISel/memtest1.ll llvm/trunk/test/CodeGen/Mips/biggot.ll llvm/trunk/test/CodeGen/Mips/cconv/arguments-small-structures-bigger-than-32bits.ll llvm/trunk/test/CodeGen/Mips/cconv/arguments-varargs-small-structs-byte.ll llvm/trunk/test/CodeGen/Mips/cconv/arguments-varargs-small-structs-combinations.ll llvm/trunk/test/CodeGen/Mips/cconv/return-struct.ll llvm/trunk/test/CodeGen/Mips/lar...

.../tail-call-mem-intrinsics.ll >> llvm/trunk/test/CodeGen/MSP430/memset.ll >> llvm/trunk/test/CodeGen/Mips/2012-12-12-ExpandMemcpy.ll >> llvm/trunk/test/CodeGen/Mips/Fast-ISel/memtest1.ll >> llvm/trunk/test/CodeGen/Mips/biggot.ll >> llvm/trunk/test/CodeGen/Mips/cconv/arguments-small-structure >> s-bigger-than-32bits.ll >> llvm/trunk/test/CodeGen/Mips/cconv/arguments-varargs-small-s >> tructs-byte.ll >> llvm/trunk/test/CodeGen/Mips/cconv/arguments-varargs-small-s >> tructs-combinations.ll >> llvm/trunk/test/CodeGen/Mips/...

...nsics.ll >>> llvm/trunk/test/CodeGen/MSP430/memset.ll >>> llvm/trunk/test/CodeGen/Mips/2012-12-12-ExpandMemcpy.ll >>> llvm/trunk/test/CodeGen/Mips/Fast-ISel/memtest1.ll >>> llvm/trunk/test/CodeGen/Mips/biggot.ll >>> llvm/trunk/test/CodeGen/Mips/cconv/arguments-small-structure >>> s-bigger-than-32bits.ll >>> llvm/trunk/test/CodeGen/Mips/cconv/arguments-varargs-small-s >>> tructs-byte.ll >>> llvm/trunk/test/CodeGen/Mips/cconv/arguments-varargs-small-s >>> tructs-combinations.ll >>> llvm/...

...k-object.ll llvm/trunk/test/CodeGen/Hexagon/tail-call-mem-intrinsics.ll llvm/trunk/test/CodeGen/MSP430/memset.ll llvm/trunk/test/CodeGen/Mips/2012-12-12-ExpandMemcpy.ll llvm/trunk/test/CodeGen/Mips/Fast-ISel/memtest1.ll llvm/trunk/test/CodeGen/Mips/biggot.ll llvm/trunk/test/CodeGen/Mips/cconv/arguments-small-structures-bigger-than-32bits.ll llvm/trunk/test/CodeGen/Mips/cconv/arguments-varargs-small-structs-byte.ll llvm/trunk/test/CodeGen/Mips/cconv/arguments-varargs-small-structs-combinations.ll llvm/trunk/test/CodeGen/Mips/cconv/return-struct.ll llvm/trunk/test/CodeGen/Mips/lar...

...k-object.ll llvm/trunk/test/CodeGen/Hexagon/tail-call-mem-intrinsics.ll llvm/trunk/test/CodeGen/MSP430/memset.ll llvm/trunk/test/CodeGen/Mips/2012-12-12-ExpandMemcpy.ll llvm/trunk/test/CodeGen/Mips/Fast-ISel/memtest1.ll llvm/trunk/test/CodeGen/Mips/biggot.ll llvm/trunk/test/CodeGen/Mips/cconv/arguments-small-structures-bigger-than-32bits.ll llvm/trunk/test/CodeGen/Mips/cconv/arguments-varargs-small-structs-byte.ll llvm/trunk/test/CodeGen/Mips/cconv/arguments-varargs-small-structs-combinations.ll llvm/trunk/test/CodeGen/Mips/cconv/return-struct.ll llvm/trunk/test/CodeGen/Mips/lar...

Hi, I don't find the formal definition of "declare", although it is used in ~300 hundred of places. Do I miss something? If it is not formally defined, should it be defined? Thanks. https://llvm.org/docs/LangRef.html -- Regards, Peng

Hao Shen wrote: > Dear all, > > I compiled c program with llvm and found something strange with > function pointer as following small example . > > ------------- In C Code -------------- > float a (int value) { > return value + 1; > }; > > typedef float (*funcptr_t) (int); > > funcptr_t get_ptr(funcptr_t p) { > return p; > } > > float

...char * ptr = malloc(...); ///... //with use(s) of ptr later The LLVM IR for the above code would be: %0 = tail call noalias i8* @malloc(i32 137) nounwind ///... // use(s) of %0 LLVM's Language Reference has the instruction format for CallInst: <result> = [tail] call [cconv <http://llvm.org/docs/LangRef.html#callingconv>] [ret attrs <http://llvm.org/docs/LangRef.html#paramattrs>]<ty> [<fnty>*]<fnptrval>(<function args>) [fn attrs <http://llvm.org/docs/LangRef.html#fnattrs>] Does that mean any LLVM IR that has a valid res...

Dear all, I compiled c program with llvm and found something strange with function pointer as following small example . ------------- In C Code -------------- float a (int value) { return value + 1; }; typedef float (*funcptr_t) (int); funcptr_t get_ptr(funcptr_t p) { return p; } float result = get_ptr(a)(4); ------------- In LLVM Code -------------- %4 = call float (i32)* (float

...undles may be attached to a call or an invoke. The intended use of these values is to support "frame introspection"-like functionality for managed languages. # Abstract Syntax The syntax of a call instruction will be changed to look like this: <result> = [tail | musttail] call [cconv] [ret attrs] <ty> [<fnty>*] <fnptrval>(<function args>) [operand_bundle*] [fn attrs] where operand_bundle = tag '('[ value ] (',' value )* ')' value = normal SSA values tag = "< some name >" In other words, after the...