search for: funccall

...have a separate test case for each of these: statement functions intrinsic functions (print, cos, etc) loops, goto statments scalarized array operations function calls with *no arguments* simple common blocks Function calls with more than one argument don't work. Specifically: ..../gfortran funccall-1arg.f -o funccall-1arg.exe ..../llvm/lib/VMCore/Instructions.cpp:209: failed assertion `(Params.size() == FTy->getNumParams() || (FTy->isVarArg() && Params.size() > FTy->getNumParams())) && "Calling a function with bad signature!"' funccall-1arg.f: In func...

...statement functions > intrinsic functions (print, cos, etc) > loops, goto statments > scalarized array operations > function calls with *no arguments* > simple common blocks Great! > Function calls with more than one argument don't work. Specifically: > > ..../gfortran funccall-1arg.f -o funccall-1arg.exe > ..../llvm/lib/VMCore/Instructions.cpp:209: failed assertion > `(Params.size() == FTy->getNumParams() || (FTy->isVarArg() && > Params.size() > FTy->getNumParams())) && "Calling a function with bad > signature!"' >...

...of expected passes 2726 # of unexpected failures 58 # of expected failures 6 * With ARM debug support === Summary === # of expected passes 2727 # of unexpected failures 57 # of expected failures 6 The extra success test is funccall.ll from test/DebugInfo. In order to build successfully LLVM on ARM Linux EABI platform, I put in comment the usage of __register_frame into JIT.cpp because it seems that __register_frame function is not into my libgcc. Could you mention which tools and versions that must to be used in order to buil...

...zbl %al, %eax #FP_REG_KILL ret Abort trap (core dumped) FAIL: /usr/home/llvm/obj/../test/Regression/CodeGen/X86/fast-cc-pass-in-regs.ll: Does not have a RUN line Running /usr/home/llvm/obj/../test/Regression/Debugger/dg.exp ... FAIL: /usr/home/llvm/obj/../test/Regression/Debugger/funccall.ll:

...# of unexpected failures 58 > # of expected failures 6 > * With ARM debug support > === Summary === > # of expected passes 2727 > # of unexpected failures 57 > # of expected failures 6 > > The extra success test is funccall.ll from test/DebugInfo. In order > to build > successfully LLVM on ARM Linux EABI platform, I put in comment the > usage of > __register_frame into JIT.cpp because it seems that __register_frame > function is not into my libgcc. Could you mention which tools and > versions &...

...58 >> # of expected failures 6 >> * With ARM debug support >> === Summary === >> # of expected passes 2727 >> # of unexpected failures 57 >> # of expected failures 6 >> >> The extra success test is funccall.ll from test/DebugInfo. In order >> to build >> successfully LLVM on ARM Linux EABI platform, I put in comment the >> usage of >> __register_frame into JIT.cpp because it seems that __register_frame >> function is not into my libgcc. Could you mention which tools a...

...# of unexpected failures 58 > # of expected failures 6 > * With ARM debug support > === Summary === > # of expected passes 2727 > # of unexpected failures 57 > # of expected failures 6 > > The extra success test is funccall.ll from test/DebugInfo. In order > to build > successfully LLVM on ARM Linux EABI platform, I put in comment the > usage of > __register_frame into JIT.cpp because it seems that __register_frame > function is not into my libgcc. Could you mention which tools and > versions &...

...expected failures 6 >>> * With ARM debug support >>> === Summary === >>> # of expected passes 2727 >>> # of unexpected failures 57 >>> # of expected failures 6 >>> >>> The extra success test is funccall.ll from test/DebugInfo. In order >>> to build >>> successfully LLVM on ARM Linux EABI platform, I put in comment the >>> usage of >>> __register_frame into JIT.cpp because it seems that __register_frame >>> function is not into my libgcc. Could you menti...

...s were for platform specific things, would that be incorrect? > - Pick a more generic name. Possibly "StackOverflowGuard"? > - Use two parameters. First, "minimum guard region size" (non-negative > integer number of bytes). Second, "test mechanism" (enum (FuncCall, Load, > Store, ConditionalCheck)). For the conditional check version, you'd need a > way to specify a failure handler. For the func call version, you need a > way to set the routine. > > > Now, I realize this is well beyond what you originally wanted to > implement. I...

...gt;>>> * With ARM debug support >>>> === Summary === >>>> # of expected passes 2727 >>>> # of unexpected failures 57 >>>> # of expected failures 6 >>>> >>>> The extra success test is funccall.ll from test/DebugInfo. In order >>>> to build >>>> successfully LLVM on ARM Linux EABI platform, I put in comment the >>>> usage of >>>> __register_frame into JIT.cpp because it seems that __register_frame >>>> function is not into my lib...

The point of this is to cheaply detect all stack overflows using a guard page. For a guard page to actually detect all stack overflows, we need to ensure that the code touches each page of the stack in the right order, otherwise it could skip the guard page and write outside the stack. That is very bad for languages such as Rust which provides memory safety, so it currently does an explicit

Hi, I just wanted to doublecheck that the docs on the debugger intrinsics as seen on http://llvm.cs.uiuc.edu/docs/Sour ceLevelDebugging.html are out of date w.r.t. function types being displayed: ie, shouldn't %D1 = call {}* %llvm.dbg.func.start(%lldb.global* %d.main) be %D1 = call {}* (%lldb.global*)* %llvm.dbg.func.start(%lldb.global* %d.main) ? and, call {} *

...end/2002-07-30-VarArgsCallFailure.c Index: test/Regression/CFrontend/2002-08-02-UnionTest.c Index: test/Regression/CFrontend/2002-09-08-PointerShifts.c Index: test/Regression/CFrontend/2002-10-12-TooManyArguments.c Index: test/Regression/CodeGen/Generic/BasicInstrs.c Index: test/Regression/Debugger/funccall.c Index: tools/bugpoint/BugDriver.h Index: tools/bugpoint/Miscompilation.cpp Index: tools/bugpoint/OptimizerDriver.cpp Index: utils/Burg/b.h Index: utils/Burg/be.c Index: utils/Burg/burs.c Index: utils/Burg/closure.c Index: utils/Burg/delta.c Index: utils/Burg/fe.c Index: utils/Burg/fe.h Index: uti...

...ly, they don't seem to be. > > > > >> - Pick a more generic name. Possibly "StackOverflowGuard"? >> - Use two parameters. First, "minimum guard region size" (non-negative >> integer number of bytes). Second, "test mechanism" (enum (FuncCall, Load, >> Store, ConditionalCheck)). For the conditional check version, you'd need a >> way to specify a failure handler. For the func call version, you need a >> way to set the routine. >> >> >> Now, I realize this is well beyond what you originally want...