We have an IRC channel (#firm on FreeNode), a mailing list (see libfirm.org) and there are github mirrors for cparser (https://github.com/MatzeB/cparser) and libfirm (https://github.com/MatzeB/libfirm/). If you want to…
Fixed, thanks for the report. (: (stupid gcc extensions sigh)
libFirm is not tied to compiling C. It is a more general intermediate representation library, which provides an API to attach a frontend, e.g. there is one for X10, too. Further, I doubt that we have enough good C…
The main points of this (i.e my) post on the mailing list still apply. Nowadays everything is even more nice. (:
One important difference to LLVM is the backend (machine code generation). libFirm uses its graph-based intermediate representation with explicit data dependencies not only in the "middleend" (i.e. for…
It's sufficiently compatible to handle e.g. glibc, which is quite a feat, because it uses many and somewhat obscure gcc extensions.
We have an IRC channel (#firm on FreeNode), a mailing list (see libfirm.org) and there are github mirrors for cparser (https://github.com/MatzeB/cparser) and libfirm (https://github.com/MatzeB/libfirm/). If you want to…
Fixed, thanks for the report. (: (stupid gcc extensions sigh)
libFirm is not tied to compiling C. It is a more general intermediate representation library, which provides an API to attach a frontend, e.g. there is one for X10, too. Further, I doubt that we have enough good C…
The main points of this (i.e my) post on the mailing list still apply. Nowadays everything is even more nice. (:
One important difference to LLVM is the backend (machine code generation). libFirm uses its graph-based intermediate representation with explicit data dependencies not only in the "middleend" (i.e. for…
It's sufficiently compatible to handle e.g. glibc, which is quite a feat, because it uses many and somewhat obscure gcc extensions.