search for: llvm7

Hey Tim, Sadly I have currently only a release build of LLVM7 with no assertions turned on... So I just know that the line of code I posted is crashing. No output, no anything....just...Crash... Kind greetings Björn -----Original Message----- From: Tim Northover <t.p.northover at gmail.com> Sent: Dienstag, 15. Januar 2019 13:28 To: Gaier, Bjoern <B...

...gmx.net> Cc: llvm-dev <llvm-dev at lists.llvm.org> Subject: RE: [llvm-dev] Building LLVM with VisualStudio 2017 Hey Stella, (Gaier is my last name :0) I do the same steps as you do! The resulting Clang compiler is indeed working. I have problems with the LLVM library. When I build the LLVM7 I use the libraries of it in a different project - a JIT client. When I compile this solution with Visual Studio 2017 and the MSVC compiler, then I get no problems. But, when I switch to the Clang-cl compiler in Visual Studio 2017, then I get suddenly these undefined references. The strange thing...

Hello everyone, I want to use the LLVM to write a JIT client, that works with shared memory. Currently I proceed as following: I wrote an own class that inherits "RTDyldMemoryManager". The functions "allocateCodeSection" and "allocateDataSection" are allocating local non-shared memory. I store there addresses in a std::vector. When the function

...then I will end up having two shared memories, because the >>> second module will go through the same steps as the first one. But I want >>> to have one coherent memory. >>> >>> >>> >>> Also the applying of the mapping causes a bug with the new LLVM7 – I >>> already filled out a bug report for this. But I have no idea how things >>> will progress from that point… Still I have no idea about the system… >>> >>> >>> >>> *From:* David Blaikie <dblaikie at gmail.com> >>> *Sent:* Mi...

Dear testers, 7.0.0-rc3 was just tagged (from branch revision r341805). No further release candidates are currently planned, so this is a release candidate in the real sense: unless any serious issues surface, this is what the final release will look like. Please run the test script, share your results and upload binaries. Please also take a look at the release notes and other docs; small

...at gmail.com>; Mehdi AMINI <joker.eph at gmail.com>; llvm-dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] Function - replaceAllUsesWith On Tue, 15 Jan 2019 at 12:35, Gaier, Bjoern <Bjoern.Gaier at horiba.com> wrote: > Sadly I have currently only a release build of LLVM7 with no assertions turned on... That's definitely the first thing you should fix. Preferably a debug build too. The only reason you should ever be debugging against a release build of LLVM is if you have a Heisenbug that doesn't happen otherwise. It's a horrible experience. > So I...

Hey Stefan, The function looks like this: “; Function Attrs: nounwind declare i32 @puts(i8* nocapture readonly) local_unnamed_addr #2” I wondered if I can do the external symbol resolution without using the JIT and RuntimeDyld (for now). For me it sounds like something that could be possible… Kind greetings Björn From: Stefan Gränitz <stefan.graenitz at gmail.com> Sent: Dienstag, 15.