search for: machiel

...4 standard with a host application that is compiled with the C++17 standard (Both on Windows/MSVC). I am running into an incompatibility for which I filed a bug report: https://bugs.llvm.org/show_bug.cgi?id=44131 However, I was wondering if C++17 host applications are even supported? Regards, Machiel van Hooren

Hi All, A preliminary version of removable code support has been posted for review in https://reviews.llvm.org/D79312. This patch removes all uses of VModuleKeys (except for Legacy layers) and takes a whole-JITDylib-at-a-time approach to removal. Removing whole JITDylibs requires more work from clients (compared to per-module removal): Modules to be removed must be placed into throw-away

Hello everyone A previous thread about OrcJIT brought up bug reports on Bugzilla. A quick search gives 20+ results: https://bugs.llvm.org/buglist.cgi?component=OrcJIT&list_id=162232&query_format=advanced&resolution=--- While some of them are obviously outdated (addModuleSet API cleanup [1]), others may actually be relevant again (Small code model? [2]). If you reported one of them,

Hi All, This week I've been focused on removing some of the blockers for people transitioning from ORCv1 to ORCv2. Issue #1 (http://llvm.org/PR40074, http://llvm.org/PR44337): When LLVM codegens floating point constants for COFF we produce named constant pool entries of the form __real@<bitval>. These are stored in COFF COMDAT sections [1] which allow duplicate symbol definitions to

Hi, I have just tagged the 10.0.1-rc1 release. Testers can begin testing and uploading binaries. If you still want to get a fix into the 10.0.1 release, you still have about a month to get your fix in. To request a patch be backported to the release/10.x branch, file a bug and mark it as a blocker of the release-10.0.1 meta bug. -Tom

...d=24159 > > Back in 2016 I simply didn't know about the Bugzilla tracker. > From today's perspective, I think, we should try and revive this spirit > and share rough plans there. > > @Praveen very good initiative! > https://bugs.llvm.org/show_bug.cgi?id=41075 > > @Machiel: This is quite recent, but didn't land after it was accepted. > Objections? > https://reviews.llvm.org/D61599 > > Cheers > -------- Forwarded Message -------- > Subject: Bugzilla OrcJIT Tickets > Date: Sat, 18 May 2019 17:47:58 +0200 > From: Stefan Gränitz <stefan.gra...

...Next Writable Address: 0*2KB Free Blocks: 2297888*2KB Track Size: 2297888*2KB The result ============= root@ghost /usr/local/video/iso $ dvdrecord -vv -dao dev=1,0,0 out/DivX1.iso dvdrtools v0.1.4 ^^^ note: this is actually dvdrtools_fbsd-0.1.5 downloaded from http://machiel.generaal.net/files/ [ snip licence ] Based on: Cdrecord 1.11a15 (i386-unknown-freebsd4.8) Copyright (C) 1995-2001 J?rg Schilling TOC Type: 1 = CD-ROM scsidev: '1,0,0' scsibus: 1 target: 0 lun: 0 Using libscg version 'bero-0.5a' dvdrecord: Warning: using inofficial version of libs...

Hi All, In the interests of improving visibility into ORC JIT development I'm going to try writing weekly status updates for the community. I hope they will provide insight into the design and state of development of LLVM's JIT APIs, as well as serving as a convenient space for discussions among LLVM's large and growing community of JIT API users. The length and detail will vary