search for: gethosttripl

On Jul 29, 2011, at 6:42 AM, 陳韋任 wrote: > Currently, I handcode "Arch = "arm"" to make native compiled LLVM > pass most test cases [2]. Is there a better way to make sys::getHostTriple > handle this situation? Two ways: a) Add support for armv7l to llvm :) b) Pass --host=<arm arch you want>-… when you configure. -eric -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110808/0af5a...

On Aug 8, 2011, at 6:53 PM, 陳韋任 wrote: >>>> b) Pass --host=<arm arch you want>-… when you configure. >> >> Either way. But it sounds like you were ok with arm-linux-gnu so that's what I'd suggest you pass using --host. > > So what you suggest is passing arm-linux-gnu NOT armvX-linux-gnu, > right? I thought <arm arch you want> can be

Hi, Eric > Two ways: > > a) Add support for armv7l to llvm :) > b) Pass --host=<arm arch you want>-… when you configure. Do you mean both way have to be done, or either way? I don't understand if I ignore option a, which means LLVM does NOT support armv7l right now, how can --host=<arm arch you want> work? Or I misunderstood what you said? Regards, chenwj --

On Aug 8, 2011, at 6:27 PM, 陳韋任 wrote: > Hi, Eric > >> Two ways: >> >> a) Add support for armv7l to llvm :) >> b) Pass --host=<arm arch you want>-… when you configure. > > Do you mean both way have to be done, or either way? I don't > understand if I ignore option a, which means LLVM does NOT > support armv7l right now, how can

On Aug 9, 2011, at 12:48 AM, James Molloy wrote: > Hi, > > My patch, sent a few months back was meant to make this easier to update. Eric has discussed it internally in Apple I believe and has some ideas how the driver can be improved, but I haven't heard back further about a schedule for providing such a patch. > You weren't the only one on vacation ;) > Eric - I'd

> >> b) Pass --host=<arm arch you want>-… when you configure. > > Either way. But it sounds like you were ok with arm-linux-gnu so that's what I'd suggest you pass using --host. So what you suggest is passing arm-linux-gnu NOT armvX-linux-gnu, right? I thought <arm arch you want> can be armvX-linux-gnu, that confuse me. Regards, chenwj -- Wei-Ren Chen

...0 AM, Alexey Samsonov <vonosmas at gmail.com> wrote: > The problem is we "guess" that the host architecture is i686, and fail > when we find out that we can't target it (__i686__ is not defined). > This guess originates from get_host_triple() call > in cmake/modules/GetHostTriple.cmake. > Probably, it makes sense to fix that to return i568 on openSUSE, and then > test for i586 in the same way we already test for i386/i686. > > > On Fri, Jul 17, 2015 at 11:23 AM, Hans Wennborg <hans at chromium.org> wrote: > >> Seems on OpenSUSE x86, it's c...

...0\VC\bin\x86_amd64\cl.exe C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\cl.exe D:\src\llvm\build\ninja>cmake ..\.. -- Target triple: i686-pc-win32 -- Native target architecture is X86 In both cases my triple is the same. This seems to boil down to some code in llvm\cmake\modules\GetHostTriple.cmake. It uses the variable CMAKE_CL_64. From what I can tell, the value of this variable depends on your CMake generator, and not on your toolchain. Some googling suggests that CMAKE_CL_64 will be set to 1 if you run cmake -G "Visual Studio 12 Win64". I can't even get this to wor...

...cutionEngine/. Those failure are disappeared when I cross compile LLVM. Maybe LLVM_HOSTTRIPLE got the *right* value, i.e., arm-unknown-linux-gnueabi. Currently, I handcode "Arch = "arm"" to make native compiled LLVM pass most test cases [2]. Is there a better way to make sys::getHostTriple handle this situation? Thanks! Regards, chenwj [1] http://llvm.org/viewvc/llvm-project?view=rev&revision=131463 [2] see attach llvm-131466-fix-gcc-4.4.1-native-arm2.log -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886...

Seems on OpenSUSE x86, it's called i586, not i686 :-( +Alexey: do you think we can handle this in the compiler-rt cmake files somehow? Maybe try targeting both i686 and i586 unless that would break something else? On Fri, Jul 17, 2015 at 1:31 AM, Nikola Smiljanic <popizdeh at gmail.com> wrote: > CMake Error at projects/compiler-rt/cmake/config-ix.cmake:125 (message): > Cannot

...tializeAllAsmPrinters(); InitializeAllAsmParsers(); Triple *TheTriple = NULL; if ( DoMingw ) { TheTriple = new Triple("i686-pc-mingw32"); } else { TheTriple = new Triple("i686-pc-win32"); } Assert(!TheTriple->getTriple().empty()) //TheTriple.setTriple(sys::getHostTriple()); 9 std::string Err; const Target *TheTarget = TargetRegistry::lookupTarget(TheTriple->getTriple(), Err); if (TheTarget == 0) { printf( "Error selecting target\n" ); return false; } /* CodeGenOpt::None CodeGenOpt::Less CodeGenOpt::Default CodeGenOpt::Aggress...

...s error is that if I instead output the ARM assembly language then assembly it on the build host using the Android NDK toolchain, it assembles without any problem at all. The library usage to generate the assembly is: std::string errorStr; std::string targetTriple = llvm::sys::getHostTriple(); const llvm::Target *target = llvm::TargetRegistry::lookupTarget( targetTriple, errorStr ); llvm::TargetMachine *targetMachine = target->createTargetMachine( targetTriple, "" ); targetMachine->setAsmVerbosityDefault( true ); llvm::FunctionPassMan...

...nst char **argv, char * const *envp) { void *MainAddr = (void*) (intptr_t) GetExecutablePath; llvm::sys::Path Path = GetExecutablePath(argv[0]); TextDiagnosticPrinter DiagClient(llvm::errs(), DiagnosticOptions()); Diagnostic Diags(&DiagClient); Driver TheDriver(Path.str(), llvm::sys::getHostTriple(), "a.out", /*IsProduction=*/false, /*CXXIsProduction=*/false, Diags); TheDriver.setTitle("clang interpreter"); // FIXME: This is a hack to try to force the driver to do something we can // recognize. We need to extend the driver lib...

Hi Daniel, > Sebastian, this looks like it is most likely some kind of fallout from > your changes. Thanks for letting me know about these failing testcases. In the logs of the buildbot: http://lab.llvm.org:8011/builders/llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi/builds/273/steps/run.build.step.configure_llvm_1/logs/stdio I see that the bot is configuring llvm with:

I tried what you said, now I get: LLVM ERROR: Program used external function 'yipee' which could not be resolved! Stack dump: 0. Running pass 'X86 Machine Code Emitter' on function '@main' did not even get as far as a breakpoint. Óscar Fuentes wrote: > > gafferuk <gafferuk at gmail.com> writes: > >> Im confused. The function i wish to call is

gafferuk <gafferuk at gmail.com> writes: > Im confused. The function i wish to call is a return type of int. > Im calling it with int dd = yipee(1); > > What's wrong? Declare the function: int yipee(int); int main() { int dd = yipee(1); return 0; } If that still crashes, put a breakpoint on `yipee' and see if the execution gets there, if the argument is

...ig.guess: /mnt/disk3/llvmtruck/llvm/autoconf/config.guess: 68: /mnt/disk3/llvmtruck/llvm/a: not foundfig.guess: /mnt/disk3/llvmtruck/llvm/autoconf/config.guess: 71: /mnt/disk3/llvmtruck/llvm/autoconf/config.guess: Syntax error: word unexpected (expecting "in") CMake Error at cmake/modules/GetHostTriple.cmake:24 (message): Failed to execute /mnt/disk3/llvmtruck/llvm/autoconf/config.guess Call Stack (most recent call first): cmake/config-ix.cmake:331 (get_host_triple) CMakeLists.txt:407 (include) Steven Shi Intel\SSG\STO\UEFI Firmware Tel: +86 021-61166522 iNet: 821-6522 From: metafoo...

Hi Richard, Thank you for the info. I build my code in Ubuntu-64bits with simply commands: “clang X64.c”, then run “./a.out” to see the output. If I replace my va_list, va_start, va_arg va_end with __builtin_ms_va_list, __builtin_ms_va_start, __builtin_ms_va_arg, __builtin_ms_va_end, my code will build fail in Ubuntu with below message. Do you suggest I should build it in windows and not in

...er(Buffer, SMLoc()); - AsmParser Parser(SrcMgr, OutContext, OutStreamer, *MAI); - OwningPtr<TargetAsmParser> TAP(TM.getTarget().createAsmParser(Parser)); + // FIXME: Doesn't work with cross-compilation currently. + OwningPtr<AsmParser> TAP(TM.getTarget().createAsmParser(sys::getHostTriple(), + SrcMgr, OutContext, + OutStreamer, *MAI)); if (!TAP) report_fatal_error("Inline asm not supported by this streamer because" " we don...