similar to: [LLVMdev] libc dependencies, code generation questions

Hi Jonas, > I'm looking into creating an llvm backend for the Free Pascal > Compiler (<http://www.freepascal.org>). After reading a bit through > the documentation and looking at some code generated by llvm-gcc, I > have a couple of questions: I've been working on getting the gcc Ada front-end to work in llvm-gcc. Since Ada evolved from Pascal, it may be worth

Hi Jonas. I'm very interested in an llvm backend for freepascal. Could you give some more details? Is there already something to try and test? Will the code be avaiable on svn? Thanks, Nicola On 6/7/07, Jonas Maebe <jonas.maebe at elis.ugent.be> wrote: > > Hello, > > I'm looking into creating an llvm backend for the Free Pascal > Compiler

On 01 Nov 2010, at 18:37, Duncan Sands wrote: > I think the "fact" that x86 long double is 16 byte aligned on x86-64 is > hard-wired in. Note that it's not just about alignment, but mainly about the reserved storage size. > I'm not sure how hard this would be to control via a > command line option (i.e. -m96bit-long-double). Is there no different way to go about

On 7 jun 2007, at 11:22, Duncan Sands wrote: > I've been working on getting the gcc Ada front-end to work in llvm- > gcc. > Since Ada evolved from Pascal, it may be worth your while to see how > llvm-gcc handles these kinds of issues (most of the work is done in > llvm-convert.cpp). Thanks, I will certainly do so. >> [llvm helpers such as malloc, free, memcpy, memset,

Adrian Prantl via llvm-dev wrote on Mon, 02 Nov 2015: > Looking at the code in clang CGDebugInfo just passes through the > width of the type as it is described by the TypeInfo, which in turn > is defined by the Target. At the moment I do not understand why an > x86_fp80 is reported to be 128 bits wide. The x86-64 and Darwin/i386 ABI define the size of the 80 bits extended

On 29 October 2015 at 10:25, Jonas Maebe via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hi, > > Regarding the previously voiced concerns of incompatibilities between the > Apache and GPLv2 license, I'd like to add one more thing. > > I work on a, at this time mostly LLVM-unrelated [1], "GPLv2 or later" > licensed compiler: the Free Pascal Compiler. Some

On 2009-02-08, at 05:59, Jonas Maebe wrote: > The proposal suggests to change/split the existing sub/add/mul > opcodes. This makes me wonder to what extent it is (currently, or > ever) advisable for an external compiler to generate LLVM IR. Is > there a plan to stabilise at some point and guarantee backwards > compatibility to a certain extent, or should compilers that are

Hello, In case there are other users of the AsteriskWin32 port... I haven't really used the AGI feature of Asterisk to run an application from extensions.conf. *Win32 supports Perl, which I don't know. Apparently, it's also possible to write AGI applications as EXE's (there's a eagi-test.exe file installed by default). => When a call comes in, I'd like an AGI

Hi Everyone, Those of you who have a simple home-based Asterisk box might be interested in a "simple" Win32 (Win2K or WinXP) interface to the AMI manager. The quick-start versions merely require unzipping with NO Installation - hence, NO Uninstall (i.e., no registry writes at any time by the install nor by the program). (Unfortunately) the INSTALL version does write to the

On 08 Feb 2009, at 14:41, Gordon Henriksen wrote: > On 2009-02-08, at 05:59, Jonas Maebe wrote: > >> The proposal suggests to change/split the existing sub/add/mul >> opcodes. This makes me wonder to what extent it is (currently, or >> ever) advisable for an external compiler to generate LLVM IR. Is >> there a plan to stabilise at some point and guarantee backwards

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

On Nov 1, 2010, at 12:03 PM, Jonas Maebe wrote: > > On 01 Nov 2010, at 18:37, Duncan Sands wrote: > >> I think the "fact" that x86 long double is 16 byte aligned on x86-64 is >> hard-wired in. > > Note that it's not just about alignment, but mainly about the reserved storage size. > >> I'm not sure how hard this would be to control via a

All, I am a FreePascal programmer. I am making a Pascal-based application now, and want to use vorbis as its sound files. What should I do so that I can use libvorbis with FreePascal? (Actually, I use Lazarus as the Windows development environment) Thanks. -- Comodo Firewall Pro -- Powerful & Free, Forever! Visit www.comodo.com Support patent-free audio! Visit www.playogg.org Use

> This means that LLVM requires an assembler and linker. Call it > GCC or binutils, it is irrelevant. The OP point is that LLVM > is not a self-sufficient tool on this aspect. > > Of course, if this is a serious problem for the OP, the > correct way of dealing with it is to take constructive, polite > actions for correcting it :-) I know one compiler (Free Pascal) that

On 30 Jun 2010, at 18:40, Devang Patel wrote: > On Wed, Jun 30, 2010 at 1:57 AM, Artur Pietrek <pietreka at gmail.com> > wrote: >> The problem is that you put difference between two labels >> .Lset7 = .Lsection_line_begin-.Lsection_line ## DW_AT_stmt_list >> and that will be evaluated by assembler to a constant. It has to be >> a label, >> not a

Hello all, is it possible to use the native Linux libraries instead of their Windows builds? This can be a newbie question. :) I have a database program based on PostgreSQL and I think that coyping the Windows libraries for the application to run is a bit luxury when the same but native libraries with the same functions already exist for Linux and they are already installed on my system. I

Hi, Having just found an ABI conformance bug in a compiler front-end, I am curious: is the state of target-independent argument lowering in LLVM still the same as when this thread was taking place?: http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-February/thread.html#59387 Vadim -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 01/08/14 19:37, Reid Kleckner wrote: > What happens if you drop appending linkage? I think it will just work, > since you are already using a custom section, which will ensure that all > the data appears contiguously in memory. Thanks for the suggestion, but it still puts everything in a single .section statement. > Although, I do worry about what LLVM's alias analysis will

On 30 Jul 2014, at 21:29, Ulrich Weigand wrote: > The ELFv1 ABI is used on 64-bit big-endian Linux and AIX. There's one small difference between the two: with the 64 bit ELFv1/ SVR4 ABI, tail padding for structs passed by value is only performed in case the struct is larger than 8 bytes, while for AIX 64 bit it's always done. As an aside, on Darwin/ppc64 it's done if the

As I migrate away from Windows, I need to move the data out of my old rolodex program (written in Pascal back in the late 80's) into something that runs on Linux. The data is stored in csv lines in a text file. That old custom program output the data to rolodex cards on a pin-feed dot matrix printer. (Yea...I'm dating myself). Anyway, does anyone know of a decent rolodex program on