https://github.com/libfirm/cparser

C99 parser and frontend for libfirm
https://github.com/libfirm/cparser

c c99 compiler libfirm preprocessor

Last synced: 7 days ago
JSON representation

C99 parser and frontend for libfirm

• Host: GitHub
• URL: https://github.com/libfirm/cparser
• Owner: libfirm
• License: gpl-2.0
• Created: 2009-04-22T02:47:13.000Z (over 15 years ago)
• Default Branch: master
• Last Pushed: 2023-11-03T23:52:37.000Z (about 1 year ago)
• Last Synced: 2024-03-25T22:14:44.526Z (9 months ago)
• Topics: c, c99, compiler, libfirm, preprocessor
• Language: C
• Homepage: http://pp.ipd.kit.edu/firm
• Size: 9.04 MB
• Stars: 316
• Watchers: 18
• Forks: 39
• Open Issues: 38
• Metadata Files:
  • Readme: README.md
  • License: COPYING
  • Support: support/check_options.py

Awesome Lists containing this project

• AwesomeCompiler - cparser

README

        
cparser - A C99 parser (with GNU extensions)

============================================

Introduction

------------

cparser is a recursive descent C99 parser written in C99.  It contains a

preprocessor, lexer, parser, constructs an AST and does semantic analysis.  It

acts as a frontend to the libFirm intermediate representation library.  This

way optimization and code generation is performed. The compiler supports cross

compilation to multiple target architectures with a command-line switch.  It

comes with driver logic for calling assemblers and linkers as well as parsing

command-line options.  This allows it to be a drop-in replacement for gcc or

clang in many situations.

Building and Installation

-------------------------

Requirements:

* A C99 compiler (gcc and icc are known to work).

* libFirm-1.22

### Building with make

Unpack libfirm in a directory called libfirm in the source directory

alternatively you may setup an alternate location with a 'config.mak' file.

Just type 'make' in the source directory. The results are put into a directory

called "build". You can override the existing preprocessor, compiler and linker

flags and built-in paths for include directories by creating a 'config.mak'

file.

### Building with cmake

cparser has an additional cmake build system. CMake is a complexer build system

than the make based build and most cparser developers do not use it.  However

it can adapt the compiler and linker flags to build shared libraries for a

wider range of systems, provides an installation target and is often more

familiar for people preparing packages for distribution.

### Notes for a cparser installation

While cparser often runs fine from the source/build directory, a proper

installation should be configured with correct system paths. For this a

`config.mak` file should be created and the following variables set apropriately

for the system: `PREFIX`, `SYSTEM_INCLUDE_DIR`, `LOCAL_INCLUDE_DIR`,

`COMPILER_INCLUDE_DIR`, `MULTILIB_M32_TRIPLE`, `MULTILIB_M64_TRIPLE`,

`variant=optimize`.

The variable may be defined empty; See `config.default.mak` and `Makefile` for

details.

Further Information and Contact

-------------------------------

Official website: http://libfirm.org/

Contact E-Mail: [email protected]

Mailing list: https://lists.ira.uni-karlsruhe.de/mailman/listinfo/firm

Bugtracker: http://pp.ipd.kit.edu/~firm/bugs

Internet relay chat: irc://chat.freenode.net/#firm