search for: floatabitype

...r (http://code.google.com/p/data-race-test/) to find and remove races in a larger program that uses LLVM as a library. One of the things that I found is that the TargetOptions are all global; you could create a TargetMachine targeting ARM and X86 in two threads, but they both have to share the same FloatABIType setting. This is silly, and I plan to fix it by moving all the globals in TargetOptions into getters and setters on TargetMachine. This means that the TargetMachine object is going to get a bit bigger to accommodate, but at least two users of llvm linked into one program won't step on each oth...

Targetting the raspberry pi, what triple/flags should I set? I tried triple: armv4t-unknown-linux-gnueabi and ld fails with: a.out uses VFP register arguments if i set hardfloat (using optdata.FloatABIType = FloatABI::Hard), ld fails with an assertion: 2.22 assertion fail ../../bfd/elf32-arm.c:11477 what am I missing?

...e.com/p/data-race-test/) to find and remove races in > a larger program that uses LLVM as a library. One of the things that I > found is that the TargetOptions are all global; you could create a > TargetMachine targeting ARM and X86 in two threads, but they both have > to share the same FloatABIType setting. > > This is silly, and I plan to fix it by moving all the globals in > TargetOptions into getters and setters on TargetMachine. This means > that the TargetMachine object is going to get a bit bigger to > accommodate, but at least two users of llvm linked into one program &...

...opts, Reloc::Default, CodeModel::Default, OLvl)); assert(tmachine && "Could not allocate target machine!"); assert(module && "Should have exited if we didn't have a module!"); if (FloatABIForCalls != FloatABI::Default) targetopts.FloatABIType = FloatABIForCalls; std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); if (!objoutstream) return 1; legacy::PassManager passmanager; TargetLibraryInfoImpl TLII(moduletriple); TargetLibraryInfoWrapperPass *tliwp =...

...> >> assert(tmachine && "Could not allocate target machine!"); >> >> assert(module && "Should have exited if we didn't have a module!"); >> if (FloatABIForCalls != FloatABI::Default) >> targetopts.FloatABIType = FloatABIForCalls; >> >> >> std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); >> if (!objoutstream) return 1; >> >> legacy::PassManager passmanager; >> >> TargetLibraryInf...

...l::Default, OLvl)); > > assert(tmachine && "Could not allocate target machine!"); > > assert(module && "Should have exited if we didn't have a module!"); > if (FloatABIForCalls != FloatABI::Default) > targetopts.FloatABIType = FloatABIForCalls; > > > std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); > if (!objoutstream) return 1; > > legacy::PassManager passmanager; > > TargetLibraryInfoImpl TLII(moduletriple); >...

...achine && "Could not allocate target machine!"); >>>> >>>> assert(module && "Should have exited if we didn't have a module!"); >>>> if (FloatABIForCalls != FloatABI::Default) >>>> targetopts.FloatABIType = FloatABIForCalls; >>>> >>>> >>>> std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); >>>> if (!objoutstream) return 1; >>>> >>>> legacy::PassManager passmana...

...t; assert(tmachine && "Could not allocate target machine!"); >>> >>> assert(module && "Should have exited if we didn't have a module!"); >>> if (FloatABIForCalls != FloatABI::Default) >>> targetopts.FloatABIType = FloatABIForCalls; >>> >>> >>> std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); >>> if (!objoutstream) return 1; >>> >>> legacy::PassManager passmanager; >>> &...

...t allocate target machine!"); >>>>>> >>>>>> assert(module && "Should have exited if we didn't have a module!"); >>>>>> if (FloatABIForCalls != FloatABI::Default) >>>>>> targetopts.FloatABIType = FloatABIForCalls; >>>>>> >>>>>> >>>>>> std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); >>>>>> if (!objoutstream) return 1; >>>>>> >>&...

...; "Could not allocate target machine!"); >>>>> >>>>> assert(module && "Should have exited if we didn't have a module!"); >>>>> if (FloatABIForCalls != FloatABI::Default) >>>>> targetopts.FloatABIType = FloatABIForCalls; >>>>> >>>>> >>>>> std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); >>>>> if (!objoutstream) return 1; >>>>> >>>>> lega...

...inly have a mismatch. David On 30 Dec 2012, at 10:42, Carlo Kok wrote: > Targetting the raspberry pi, what triple/flags should I set? > > I tried triple: armv4t-unknown-linux-gnueabi and ld fails with: > a.out uses VFP register arguments > > if i set hardfloat (using optdata.FloatABIType = FloatABI::Hard), ld fails with an assertion: > 2.22 assertion fail ../../bfd/elf32-arm.c:11477 > > what am I missing? > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.u...

Hi David, For ARM, you will need to use the MCJIT ExecutionEngine as the legacy one is broken for ARM. (call EngineBuilder::setUseMCJIT()). When creating your TargetOptions, setting FloatABIType to FloatABI::Hard should trigger codegen for the correct ABI. Amara

...); >>>>>>>> >>>>>>>> assert(module && "Should have exited if we didn't have a module!"); >>>>>>>> if (FloatABIForCalls != FloatABI::Default) >>>>>>>> targetopts.FloatABIType = FloatABIForCalls; >>>>>>>> >>>>>>>> >>>>>>>> std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); >>>>>>>> if (!objoutstream) return 1; >&gt...

...t machine!"); >>>>>>> >>>>>>> assert(module && "Should have exited if we didn't have a module!"); >>>>>>> if (FloatABIForCalls != FloatABI::Default) >>>>>>> targetopts.FloatABIType = FloatABIForCalls; >>>>>>> >>>>>>> >>>>>>> std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); >>>>>>> if (!objoutstream) return 1; >>>>>&gt...

...gt;>>>>> >>>>>>>>> assert(module && "Should have exited if we didn't have a module!"); >>>>>>>>> if (FloatABIForCalls != FloatABI::Default) >>>>>>>>> targetopts.FloatABIType = FloatABIForCalls; >>>>>>>>> >>>>>>>>> >>>>>>>>> std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); >>>>>>>>> if (!objoutstream) r...

...gt;>> >>>>>>>>>> assert(module && "Should have exited if we didn't have a module!"); >>>>>>>>>> if (FloatABIForCalls != FloatABI::Default) >>>>>>>>>> targetopts.FloatABIType = FloatABIForCalls; >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); >>>>>>>>>> if (...

...e-test/) to find and remove races in >> a larger program that uses LLVM as a library. One of the things that I >> found is that the TargetOptions are all global; you could create a >> TargetMachine targeting ARM and X86 in two threads, but they both have >> to share the same FloatABIType setting. >> >> This is silly, and I plan to fix it by moving all the globals in >> TargetOptions into getters and setters on TargetMachine. This means >> that the TargetMachine object is going to get a bit bigger to >> accommodate, but at least two users of llvm linked...

...>>>>>>>>>>> assert(module && "Should have exited if we didn't have a module!"); >>>>>>>>>>> if (FloatABIForCalls != FloatABI::Default) >>>>>>>>>>> targetopts.FloatABIType = FloatABIForCalls; >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); >>>>>>>>>&...

...;>>>>>>>>>> assert(module && "Should have exited if we didn't have a module!"); >>>>>>>>>>>> if (FloatABIForCalls != FloatABI::Default) >>>>>>>>>>>> targetopts.FloatABIType = FloatABIForCalls; >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> std::unique_ptr<tool_output_file> objoutstream = getOutputFileStream(module, srcname); >>>>>>&...

Renato Golin wrote: [...] > Try setting armv7a-unknown-linux-gnueabihf and see if it works better. No, that doesn't work either. [...] > JIT was never the forte of ARM and I haven't tried yet, but I doubt > it'll be any Debian misconfiguration. The whole architecture > configuration is a bit odd... Debian's clang packages are totally broken on armhf --- the compiler