search for: ldc2

...test.ll /opt/msp430/bin/llc: target does not support generation of this file type! That sequence works fine for x86. Could someone help shed some light into this discrepancy? (Maybe it will also help me figure out why LDC refuses to directly generate MSP430 object files [1]). Thanks, Luís [1] $ ldc2 -mtriple=msp430 -c test.d no support for asm output UNREACHABLE executed at ../driver/toobj.cpp:130! 0 ldc2 0x0000000107e19c9c llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 60 1 ldc2 0x0000000107e1a1e9 PrintStackTraceSignalHandler(void*) + 25 2 ldc2...

...o_join()   File "/usr/lib/python2.7/dist-packages/samba/join.py", line 1381, in do_join     ctx.join_add_objects()   File "/usr/lib/python2.7/dist-packages/samba/join.py", line 616, in join_add_objects /etc/hosts: 10.220.1.19     ldc1.testdomain.org.tr      ldc1 10.220.1.20     ldc2.testdomain.org.tr      ldc2 10.220.1.22     ldc4.testdomain.org.tr      ldc4 /etc/hostname: ldc4 ----------------- I tested with "LDC3" hostname first, then changed hostname to "LDC4" after seeing a deleted DC record with "LDC3" name.  # ldbsearch -H /var/lib/samba/...

...compiler contains all IR and target specific passes. You can view it as combined llc/opt tool. It uses the same strategy as opt to collect the passes with the NameParser. Like llc, it calls Target.addPassesToEmitFile() to add the target specific passes. I now get the following error message: ldc2.exe: CommandLine Error: Option 'aarch64-branch-relax' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options Reason is that the option 'aarch64-branch-relax' is registered in file lib/Target/AArch64/AArch64BranchRelaxation.cpp and a second time thr...

...b/python2.7/dist-packages/samba/join.py", line 1381, in > do_join ctx.join_add_objects() File > "/usr/lib/python2.7/dist-packages/samba/join.py", line 616, in > join_add_objects > > /etc/hosts: > 10.220.1.19     ldc1.testdomain.org.tr      ldc1 > 10.220.1.20     ldc2.testdomain.org.tr      ldc2 > 10.220.1.22     ldc4.testdomain.org.tr      ldc4 > > /etc/hostname: > ldc4 > ----------------- > > I tested with "LDC3" hostname first, then changed hostname to "LDC4" > after seeing a deleted DC record with "LDC3&quot...

Hi all, We have a Samba AD DC service running on Ubuntu 16.0.4 with Samba 4.3.11. We are planning to upgrade it to a recent version, probably 4.8.3. I think that I have two options: a) Package upgrade via 3rd party repositories (Louis Van Belle's repo) by following wiki. b) A fresh install of 4.8.3 on another VM then join it to 4.3.11 as backup DC, then transfer all FSMO roles on new and

hi LLVM community, Maybe it is the wrong place, sorry LDC it is a D compiler D1 : http://www.dsource.org/projects/ldc D2 : http://bitbucket.org/prokhin_alexey/ldc2 We need some LLVM developper for help this project, they are an ric channel on freenode #ldc Any help are welcome Thanks for all Yours sincerely, -- jonathan MERCIER <bioinfornatics at gmail.com>

In first, i hope i can discuss here I would like generate a shared lib without gcc but i fail. With my D compiler i do: $ ldc2 --output-bc --output-o -op -release -c -relocation-model=pic -od=../build *.d llvm bytecode finish with .wc and are in ../build directory $ cd ../build $ lvm-ld -link-as-library -o libDparser.bc -L/usr/local/lib64/ -L/usr/lib64 -ldruntime-ldc -llphobos2 -lm -ldl -lrt -soname=Dparser *.bc $ llc -...

...target specific passes. You can view it > as combined llc/opt tool. It uses the same strategy as opt to collect > the passes with the NameParser. Like llc, it calls > Target.addPassesToEmitFile() to add the target specific passes. > > I now get the following error message: > > ldc2.exe: CommandLine Error: Option 'aarch64-branch-relax' registered > more than once! > LLVM ERROR: inconsistency in registered CommandLine options > > Reason is that the option 'aarch64-branch-relax' is registered in file > lib/Target/AArch64/AArch64BranchRelaxation.cpp...

...te the assembler for > you. > We should probably make that the default for MSP430. > Cool. When I did that on macOS, LDC generated a lot of complaints, possibly because it is assuming mach-o files. I tried changing from -mtriple=msp430 to -mtriple=msp430-unknown-elf, to no avail. E.g.: $ ldc2 -mtriple=msp430-unknown-elf -c -no-integrated-as qosd.d ldc-ad1c8f0.s:3:11: error: mach-o section specifier requires a segment whose length is between 1 and 16 characters .section .text._D4qosd3fooFZi,"axG", at progbits,_D4qosd3fooFZi,comdat ^ ldc-ad1c8f0....

Hello all! I extended the LDC2 with a pragma to register a funcion in the llvm.global_ctors or llvm.global_dtors list. On Linux, references to these functions are placed in .ctors and .dtors sections and everything runs fine. On Windows, functions from llvm.global_ctors are placed in section .CRT$XCU, which is automatically...

In summary we have no less than six patches required to support Win64 SEH MinGW. The first five could be committed after review and LGTM but the last one also requires Ray Donnelly approval. Please comment in the Phabricator so the comments would be kept in context. 'unreachable' trap http://reviews.llvm.org/D3417 Win64 SEH (LLVM) http://reviews.llvm.org/D3418 Win64 SEH (clang)