search for: lore97drk

So we come back to my earlier comment: can you produce a one-file, < 100 lines that reproduce the issue? -- Mehdi > On Mar 24, 2016, at 10:16 AM, Lorenzo Laneve <lore97drk at icloud.com> wrote: > > Those lines of code are in a function that is called before calling the moduleToObjectFile() function > > On Mar 24, 2016, at 6:07 PM, Mehdi Amini <mehdi.amini at apple.com <mailto:mehdi.amini at apple.com>> wrote: > >> You may want t...

...assRegistry::getPassRegistry(); initializeCore(*Registry); initializeCodeGen(*Registry); initializeLoopStrengthReducePass(*Registry); initializeLowerIntrinsicsPass(*Registry); initializeUnreachableBlockElimPass(*Registry); -- Mehdi > On Mar 24, 2016, at 9:59 AM, Lorenzo Laneve <lore97drk at icloud.com> wrote: > > Update: > Sorry my bad. I built llvm and tried it with debugging version. > It was an assertion (IR/LegacyPassManager.cpp:764) saying that it expects all immutable passes to be initialized. > > On Mar 24, 2016, at 2:00 AM, Lorenzo Laneve <lore97dr...

...; > initializeCodeGen(*Registry); > initializeLoopStrengthReducePass(*Registry); > initializeLowerIntrinsicsPass(*Registry); > initializeUnreachableBlockElimPass(*Registry); > > > -- > Mehdi > > > >> On Mar 24, 2016, at 9:59 AM, Lorenzo Laneve <lore97drk at icloud.com> wrote: >> >> Update: >> Sorry my bad. I built llvm and tried it with debugging version. >> It was an assertion (IR/LegacyPassManager.cpp:764) saying that it expects all immutable passes to be initialized. >> >>> On Mar 24, 2016, at 2:00 AM,...

...PM, Mehdi Amini <mehdi.amini at apple.com <mailto:mehdi.amini at apple.com>> wrote: > So we come back to my earlier comment: can you produce a one-file, < 100 lines that reproduce the issue? > > -- > Mehdi > >> On Mar 24, 2016, at 10:16 AM, Lorenzo Laneve <lore97drk at icloud.com <mailto:lore97drk at icloud.com>> wrote: >> >> Those lines of code are in a function that is called before calling the moduleToObjectFile() function >> >> On Mar 24, 2016, at 6:07 PM, Mehdi Amini <mehdi.amini at apple.com <mailto:mehdi.amini at...

...uild LLVM yourself? Which version are you using and can you reduce the test case to be "minimal" so that someone can reproduce? > (for instance you don't need a module to create a pass manager) > > -- > Mehdi > >> On Mar 23, 2016, at 5:50 PM, Lorenzo Laneve <lore97drk at icloud.com <mailto:lore97drk at icloud.com>> wrote: >> >> Sorry, that's a pure crash I think, assertions are not triggered. >> Xcode doesn’t map those 2 functions to line numbers because they’re in precompiled libraries >> >> >> On Mar 24, 2016...

Update: Sorry my bad. I built llvm and tried it with debugging version. It was an assertion (IR/LegacyPassManager.cpp:764) saying that it expects all immutable passes to be initialized. > On Mar 24, 2016, at 2:00 AM, Lorenzo Laneve <lore97drk at icloud.com> wrote: > > I’m using LLVM 3.8.0, and no, it’s the precompiled version > That’s why it doesn’t give me enough info for debug > >> On 24 Mar 2016, at 1:53 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: >> >> This code path is not likely to c...

...at 6:21 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: >> >> So we come back to my earlier comment: can you produce a one-file, < 100 lines that reproduce the issue? >> >> -- >> Mehdi >> >>> On Mar 24, 2016, at 10:16 AM, Lorenzo Laneve <lore97drk at icloud.com> wrote: >>> >>> Those lines of code are in a function that is called before calling the moduleToObjectFile() function >>> >>>> On Mar 24, 2016, at 6:07 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: >>>> >>>&gt...

...y to crash usually. Did you build LLVM yourself? Which version are you using and can you reduce the test case to be "minimal" so that someone can reproduce? (for instance you don't need a module to create a pass manager) -- Mehdi > On Mar 23, 2016, at 5:50 PM, Lorenzo Laneve <lore97drk at icloud.com> wrote: > > Sorry, that's a pure crash I think, assertions are not triggered. > Xcode doesn’t map those 2 functions to line numbers because they’re in precompiled libraries > > > On Mar 24, 2016, at 1:44 AM, Mehdi Amini <mehdi.amini at apple.com <mail...

...are not triggered. Xcode doesn’t map those 2 functions to line numbers because they’re in precompiled libraries On Mar 24, 2016, at 1:44 AM, Mehdi Amini <mehdi.amini at apple.com <mailto:mehdi.amini at apple.com>> wrote: > >> On Mar 23, 2016, at 5:41 PM, Lorenzo Laneve <lore97drk at icloud.com <mailto:lore97drk at icloud.com>> wrote: >> >> The stack trace: >> llvm::PMTopLevelManager::addImmutablePass(llvm::ImmutablePass*) >> llvm::PMTopLevelManager::schedulePass(llvm::Pass*) >> moduleToObjectFile(llvm::Module*,std::string&,llvm::L...

On 23 May 2016, at 12:00, Lorenzo Laneve <lore97drk at icloud.com> wrote: > > This is the point, No, you are still failing to make a point. > High-level OO languages don't use malloc(), they use something else. That’s not entirely true. They need to get the memory that they provide to programs from somewhere. They may provide t...

...library instead of the libc, I'm talking about letting people create a library optimized for a specific frontend, regardless of the target. > On May 23, 2016, at 1:06 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > >> On 23 May 2016, at 12:00, Lorenzo Laneve <lore97drk at icloud.com> wrote: >> >> This is the point, > > No, you are still failing to make a point. > >> High-level OO languages don't use malloc(), they use something else. > > That’s not entirely true. They need to get the memory that they provide to program...

On 23 May 2016, at 10:13, Lorenzo Laneve <lore97drk at icloud.com> wrote: > > I know but maybe malloc() is a bit higher level than a hypothetical __alloc(), which may be lower-level and then faster. How? > And malloc() is contained in the libc as Matthias said and so maybe a program using malloc() even for a non-C language linking aga...

...n the runtime library. Obviously this is a stupid example maybe a better implementation can be done. Something like this can be done for I/O. > On May 23, 2016, at 11:28 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > >> On 23 May 2016, at 10:13, Lorenzo Laneve <lore97drk at icloud.com> wrote: >> >> I know but maybe malloc() is a bit higher level than a hypothetical __alloc(), which may be lower-level and then faster. > > How? > >> And malloc() is contained in the libc as Matthias said and so maybe a program using malloc() even for a...

On 23 May 2016, at 12:16, Lorenzo Laneve <lore97drk at icloud.com> wrote: > > I'm not talking about a new library instead of the libc, I'm talking about letting people create a library optimized for a specific frontend, regardless of the target. It sounded as if you were talking about a library that sits underneath such a thing....

...ages have different semantics for the DETAILS of how you do certain things (error handling could be throwing exceptions, returning error codes, aborting the execution - or some combination thereof based on compiler or language pragma, etc, etc). -- Mats On 23 May 2016 at 12:35, Lorenzo Laneve <lore97drk at icloud.com> wrote: > You guys are saying that the library which defines the runtime library is > written in C for many languages. > The problem is that such functions are in the libc and so the object files > have to be linked against the **entire** libc. > Sorry if I'm wr...

...years of experience in writing my own LLVM frontend, and I guarantee that optimising string output is dead easy to do "later". Getting the compiler to deal with some of the more complex parts of whatever language it is will not be... -- Mats On 20 March 2016 at 12:34, Lorenzo Laneve <lore97drk at icloud.com> wrote: > My goal is a complete and independent compiler for a new, safe and > portable programming language. > I read the code you put the link of earlier, but I still don't get it. If > I link against that library will that main function included and started on &...

...for the DETAILS of how you do certain things (error handling could be throwing exceptions, returning error codes, aborting the execution - or some combination thereof based on compiler or language pragma, etc, etc). > > -- > Mats > >> On 23 May 2016 at 12:35, Lorenzo Laneve <lore97drk at icloud.com> wrote: >> You guys are saying that the library which defines the runtime library is written in C for many languages. >> The problem is that such functions are in the libc and so the object files have to be linked against the **entire** libc. >> Sorry if I'm w...

...ain() ? I was thinking about maybe trying to make the languages runtimes independent from the C runtime. Wouldn't it make runtimes faster? > On May 23, 2016, at 1:19 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > >> On 23 May 2016, at 12:16, Lorenzo Laneve <lore97drk at icloud.com> wrote: >> >> I'm not talking about a new library instead of the libc, I'm talking about letting people create a library optimized for a specific frontend, regardless of the target. > > It sounded as if you were talking about a library that sits undernea...

Thanks, so what’s the point of these rules? Do they grant something like safety or faster execution? > C and C++ have what's called "integer promotion rules", which apply to > most expressions involving types smaller than int and insert an > implicit promotion to int before anything else happens (in this case > another implicit conversion to double). > >> Can

> On Mar 23, 2016, at 5:41 PM, Lorenzo Laneve <lore97drk at icloud.com> wrote: > > The stack trace: > llvm::PMTopLevelManager::addImmutablePass(llvm::ImmutablePass*) > llvm::PMTopLevelManager::schedulePass(llvm::Pass*) > moduleToObjectFile(llvm::Module*,std::string&,llvm::LLVMContext&) Without mapping to line numbers this is...