search for: sebal007

I am sorry, just noticed i repeated myself :( 2017-07-10 15:20 GMT+02:00 Alexander Benikowski <sebal007 at googlemail.com>: > Thanks for starting! > Btw here is my CMD version: > > cmd /Q /V:ON /c "for /F "tokens=4" %l in ('dir llvm*.lib') do (for /F > "tokens=2" %e in ('dumpbin /linkermember:1 %l ^| findstr "_LLVM"') do (set >...

...excluded in this example but can be added easily i think) 2017-07-06 20:16 GMT+02:00 Jakob Bornecrantz <wallbraker at gmail.com>: > Made a bit of headway here: https://reviews.llvm.org/D35077 > > Cheers, Jakob. > > On Thu, Apr 6, 2017 at 2:34 PM, Alexander Benikowski > <sebal007 at googlemail.com> wrote: > > Maybe someone can use this as a startingpoint to add the windows-specific > > commandblock which is triggered instead of the Darwin one together with a > > proper setup of targets to have the libs build before. > > > > 2017-04-06 14:30...

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 := LLVMGetTargetFr...

I'd vote for having each component in a seperated Repository and using a Monorepo with Submodules to work with. Since CLang depends on LLVM but not vice versa (if i am not mistaken. I'm new here), i'd prefer to just work with the LLVM repo if it is desired. 2016-09-08 21:49 GMT+02:00 Renato Golin via llvm-dev < llvm-dev at lists.llvm.org>: > On 8 September 2016 at 19:37,

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,

Made a bit of headway here: https://reviews.llvm.org/D35077 Cheers, Jakob. On Thu, Apr 6, 2017 at 2:34 PM, Alexander Benikowski <sebal007 at googlemail.com> wrote: > Maybe someone can use this as a startingpoint to add the windows-specific > commandblock which is triggered instead of the Darwin one together with a > proper setup of targets to have the libs build before. > > 2017-04-06 14:30 GMT+02:00 Alexander Benik...

Hello, I downloaded the LLVM 10 release for windows and noticed, that the LLVM-C.dll for x86 has a size of 9kb, which seems strangely small. Both, the dll for x86 and x64, have no export directory. It is not possible to link them statically to Delphi code or call GetProcAddress on them. I do remember that this worked initially when https://reviews.llvm.org/D56774 was done when compiling the dll

...e where I would have expected the reverse, that is LLVM in the source tree of Clang and optionally compiled when compiling Clang. On Fri, Sep 9, 2016 at 3:11 PM, Mehdi Amini via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Sep 9, 2016, at 2:11 AM, Alexander Benikowski <sebal007 at googlemail.com> > wrote: > > I'd vote for having each component in a seperated Repository and using a > Monorepo with Submodules to work with. > Since CLang depends on LLVM but not vice versa (if i am not mistaken. I'm > new here), i'd prefer to just work with th...

> > Note: C does not support this. GCC has an extension (variable length > arrays in structs), but clang doesn’t support it and it’s a terrible idea. It might be complex but it is not terrible. Depends on the language capabilities implementing it. Delphi for example allows exactly that and finalizes its records through RTTI which allows to automatically free up the memory. 2017-07-14

The following is an older commandline i used. Have a more recent one at home. But basically you can write it as batch and trigger it within a target during the build(never got targets into correct order, i am a cmake noob) So for reference, i'll post this one and look for the recent one at home(if that didn't go down with my recent hdd crash): cmd /Q /V:ON /c "for /F

...LLVMTypeRef *ParamTypes, unsigned ParamCount, > LLVMBool IsVarArg); > In this case it is the other way around. 0 means False and anything else means true :/ (so it acts more like a "traditional" bool) 2016-09-12 11:17 GMT+02:00 Alexander Benikowski <sebal007 at googlemail.com>: > Of course, this is normal for C-APIs. But maybe change the name to > LLVMResult to propagate the real use? I am not arguing about the results > themself. They are standard. But the name is missguiding. As long as it's > consistent i know that i have to writ...

Of course, this is normal for C-APIs. But maybe change the name to LLVMResult to propagate the real use? I am not arguing about the results themself. They are standard. But the name is missguiding. As long as it's consistent i know that i have to write an extra record operator in Delphi to reflect this. 2016-09-12 11:11 GMT+02:00 David Chisnall <David.Chisnall at cl.cam.ac.uk>: > On

On Wed, Mar 27, 2019 at 2:03 AM Saleem Abdulrasool <compnerd at compnerd.org> wrote: > On Tue, Mar 26, 2019 at 11:13 AM bd1976 llvm <bd1976llvm at gmail.com> wrote: > >> Thanks Saleem/James. >> >> On Tue, Mar 26, 2019 at 5:15 AM Saleem Abdulrasool <compnerd at compnerd.org> >> wrote: >> >>> Yes, I don't think that supporting all