similar to: Can LLVM emit machine code faster with no optimization passes?

Compiling the IR code at http://pastebin.com/hSwdLdD0 for target triple x86_64-apple-macosx fails with : assert(Symbol->isUndefined() && "Cannot define a symbol twice!"); `anon'::MCMachOStreamer::EmitLabel(llvm::MCSymbol * Symbol) llvm::DwarfDebug::emitDebugInfo() Line 1752 + 0x3c bytes C++ llvm::DwarfDebug::endModule() Line 865 C++

Just got started and stuck at the same time. Working with the C-Api, i have come to the point where i want to emit a binary file for my module. I queried the X86-Target and called LLVMCreateTargetMachine this way: > LTarget := LLVMGetTargetFromName('x86'); > LMachine := LLVMCreateTargetMachine(LTarget, 'i386-win32-msvc', nil, > nil, LLVMCodeGenLevelDefault,

Dear Community, The ponyc<https://github.com/CausalityLtd/ponyc/tree/llvm37> (llvm37 branch) project is facing an issue on Windows: When optimizations are turned on (llvm 3.7.0-final and more specifically<https://github.com/CausalityLtd/ponyc/blob/llvm37/src/libponyc/codegen/genopt.cc>, opt-level 3, BBVectorize, LoopVectorize, SLPVectorize, RerollLoops, LoadCombine + a custom heap

Prior to "win32" i used "windows" 2017-09-19 19:09 GMT+02:00 Alexander Benikowski <sebal007 at googlemail.com>: > Just got started and stuck at the same time. Working with the C-Api, i > have come to the point where i want to emit a binary file for my module. I > queried the X86-Target and called LLVMCreateTargetMachine this way: > >> LTarget :=

On 12/10/16 20:32, Matthias Braun via llvm-dev wrote: > But just as food for though: What if msvc did some minimal > optimisations, found out that half the sourcecode is unreachable and > removes it, while llvm with no optimisations just compiles everything? llvm is actually extremely slow when it has to remove lots of dead code. I experienced that in the beginning when working on our

This got me into thinking. Indeed the problem is related to Windows exceptions, so I am not sure whether the bug reported<https://llvm.org/bugs/show_bug.cgi?id=24374> is actually fixed. Compiling Pony code (helloworld) that includes no exceptions does work fine (with optimizations). As soon as exceptions on windows come into play, writing the object file dies with the mentioned error in

… Also, it doesn’t appear that you are running on windows… From: David Majnemer Date: Saturday 12 September 2015 18:31 To: Sebastian Blessing Cc: Reid Kleckner, "llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>" Subject: Re: [llvm-dev] Optimizer issues on Windows $ ~/llvm/Debug+Asserts/bin/llc try.ll $ echo $? 0 On Sat, Sep 12, 2015 at 6:39 AM, Sebastian Blessing

Hi, I'm trying to run the benchmark suite: http://llvm.org/docs/TestingGuide.html#test-suite-quickstart I'm doing it the lnt way, as described at: http://llvm.org/docs/lnt/quickstart.html I don't know what to expect but the results seems to be quite noisy and unstable. E.g I've done two runs on two different commits that only differ by a space in CODE_OWNERS.txt on my 12

Dear Intel Engineers, I am unable to get Intel integrated graphics (IGD) VGA passthrough to work with Xen 4.0.1-rc6-pre, Xen 4.0.1-RELEASE, pv-ops dom0 kernel 2.6.32.19 and 2.6.32.21. The moment the command "xm create <Windows XP HVM guest>" is executed, the screen immediately goes blank with the label "NO SIGNAL". It may take anywhere from 3-10 minutes before

Dear Intel Engineers, I am unable to get Intel integrated graphics (IGD) VGA passthrough to work with Xen 4.0.1-rc6-pre, Xen 4.0.1-RELEASE, pv-ops dom0 kernel 2.6.32.19 and 2.6.32.21. The moment the command "xm create <Windows XP HVM guest>" is executed, the screen immediately goes blank with the label "NO SIGNAL". It may take anywhere from 3-10 minutes before

Who maintains apt.llvm.org? On 11/27/18 9:25 AM, Andrew Kelley wrote: > ---------- Forwarded message --------- > From: Andrew Kelley <superjoe30 at gmail.com> > Date: Mon, Nov 26, 2018 at 10:38 AM > Subject: apt.llvm.org has the wrong binaries/headers for llvm-toolchain-xenial-7 > To: LLVM Dev <llvm-dev at lists.llvm.org> > > > This build worked on Nov 24 and

Two other things: 1) I get massively more stable execution times on 16.04 than on 14.04 on both x86 and ARM because 16.04 does far fewer gratuitous moves from one core to another, even without explicit pinning. 2) turn off ASLR: "echo 0 > /proc/sys/kernel/randomize_va_space". As well as getting stable addresses for debugging repeatability, it also stabilizes execution time

hello, Configurations: DC1 FILESERVER member of DC1 Fileserver have extend acls enable and works. /mnt/strdc1 - share via Computer Management [storage] path = /mnt/strdc1 read only = no *image example link:* http://i.imgur.com/YVO7Emz.png The 3 groups have Full Control set. *security tab* *image example link:* http://i.imgur.com/Mw8xEfc.png The 3 groups have

On 03/12/2015 14:29, Leon Fauster wrote: > Am 03.12.2015 um 15:06 schrieb Duncan Brown <centos2 at duncb.co.uk>: >> On 03/12/2015 13:54, Jonathan Billings wrote: >>> On Thu, Dec 03, 2015 at 01:44:47PM +0000, Duncan Brown wrote: >>>> The last message before it is "switching to clocksource hpet" >>>> >>>> Then the panic scrolls by

Hi Yongjie, I have just compiled and installed Xen 4.3-unstable changeset 26666 and Linux kernel 3.8.1, according to your specifications. However, I still cannot get success with Intel HD Graphics 4600 IGD VGA passthrough. Although in Device Manager in Windows 7 HVM domU, it says "This device is working properly" for Intel HD Graphics 4600, I can only get 16 colors. Please refer to

Hi Yongjie, I have just compiled and installed Xen 4.3-unstable changeset 26666 and Linux kernel 3.8.1, according to your specifications. However, I still cannot get success with Intel HD Graphics 4600 IGD VGA passthrough. Although in Device Manager in Windows 7 HVM domU, it says "This device is working properly" for Intel HD Graphics 4600, I can only get 16 colors. Please refer to

Hello, Based on yesterday's R-help thread (help: program efficiency), and following Bill's suggestions, it appeared that sequence: > sequence function (nvec) unlist(lapply(nvec, seq_len)) <environment: namespace:base> could benefit from being written in C to avoid unnecessary memory allocations. I made this version using inline: require( inline ) sequence_c <- local( {

On 2018-09-20 10:01, Hans Wennborg via llvm-dev wrote: > Yes, it's a manual process. The binaries are build and tested by > volunteers, and the set of folks who volunteers differs a little > between releases. I would assume LLVM has some kind of CI infrastructure. That should be able to build the release binaries. > The pre-built binaries are really mostly for users who want to

I've got a patched LLD 5.0.0 like this: diff --git a/deps/lld/COFF/Driver.cpp b/deps/lld/COFF/Driver.cpp index 854c3e69..8bab1c11 100644 --- a/deps/lld/COFF/Driver.cpp +++ b/deps/lld/COFF/Driver.cpp @@ -1030,7 +1030,7 @@ void LinkerDriver::link(ArrayRef<const char *> ArgsArr) { if (!Args.hasArgNoClaim(OPT_INPUT)) { fixupExports(); createImportLibrary(/*AsLib=*/true); -

Hi r-help, I have a weird problem. When I plot anything, say plot(1:10), a plot window opens but it's empty. It looks just like this: http://i.imgur.com/9uqO6.png I have to resize the window, either by clicking the fullscreen icon on the menu bar, or by dragging the borders. Then the plot is shown, but strangely in the original size of the window, where it was before the resize: