Free c and c clogs software for linux

Obfuscated Tiny C Compiler (OTCC) is a very small C compiler I wrote in order to win the International Obfuscated C Code Contest (IOCCC) in 2002.

My goal was to write the smallest C compiler which is able to compile itself. I choose a subset of C which was general enough to write a small C compiler. Then I extended the C subset until I reached the maximum size authorized by the contest: 2048 bytes of C source excluding the ;, {, } and space characters.

I choose to generate i386 code. The original OTCC code could only run on i386 Linux because it relied on endianness and unaligned access. It generated the program in memory and launched it directly. External symbols were resolved with dlsym().

In order to have a portable version of OTCC, I made a variant called OTCCELF. It is only a little larger than OTCC, but it generates directly a dynamically linked i386 ELF executable from a C source without relying on any binutils tools! OTCCELF was tested succesfully on i386 Linux and on Sparc Solaris.

NOTE: My other project TinyCC which is a fully featured ISOC99 C compiler was written by starting from the source code of OTCC !

Compilation:

gcc -O2 otcc.c -o otcc -ldl
gcc -O2 otccelf.c -o otccelf

Self-compilation:

./otccelf otccelf.c otccelf1

EasyEclipse for C and C++ is bare-bones Eclipse distro for experienced C and C++ developers who are new to Eclipse.
EasyEclipse for C and C++ is all you need to start developing C and C++ code with Eclipse.
This distribution includes the following plugins:
Core components:
- Eclipse Platform 3.2.1 - Shared platform services from Eclipse.
- Eclipse Tools 3.2.1 - Common libraries for various Eclipse projects.
- Java for Windows 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Windows only)
- Java for Linux 1.5.0.09 - Run Java application on Sun Java(tm) runtime, packaged for Eclipse use. (Linux only)
Tools for general C and C++ development:
- Eclipse C and C++ Development Tool 3.1.1 - Create, compile, tests and debug and C and C++ applications and programs..
Version Control tools (note that CVS support is included in the Eclipse Platform):
- Subclipse 1.1.8 - Access and manage Subversion repositories within Eclipse.
Miscellaneous:
- AnyEdit Tools 1.5.6.2 - Useful right-click menus in editors: "Open file under cursor", "Open type under cursor", et cetera.
- Color Editor 1.2.4 - Edit with syntax highlighting over 100+ file formats.

Tiny C compiles so fast that even for big projects Makefiles may not be necessary.
TinyCC (aka TCC) is a small but hyper fast C compiler. Unlike other C compilers, it is meant to be self-relying: you do not need an external assembler or linker because TCC does that for you.
TCC not only supports ANSI C, but also most of the new ISO C99 standard and many GNUC extensions including inline assembly.
TCC can also be used to make C scripts, i.e. pieces of C source that you run as a Perl or Python script. Compilation is so fast that your script will be as fast as if it was an executable. TCC can also automatically generate memory and bound checks while allowing all C pointers operations. TCC can do these checks even if non patched libraries are used.
With libtcc, you can use TCC as a backend for dynamic code generation
TCC mainly supports the i386 target on Linux and Windows. There are alpha ports for the ARM (arm-tcc) and the TMS320C67xx targets (c67-tcc).
Main features:
- SMALL! You can compile and execute C code everywhere, for example on rescue disks (about 100KB for x86 TCC executable, including C preprocessor, C compiler, assembler and linker).
- FAST! tcc generates optimized x86 code. No byte code overhead. Compile, assemble and link several times faster than GCC.
- UNLIMITED! Any C dynamic library can be used directly. TCC is heading torward full ISOC99 compliance. TCC can of course compile itself.
- SAFE! tcc includes an optional memory and bound checker. Bound checked code can be mixed freely with standard code.
- Compile and execute C source directly. No linking or assembly necessary. Full C preprocessor and GNU-like assembler included.
- C script supported : just add #!/usr/local/bin/tcc -run at the first line of your C source, and execute it directly from the command line.
- With libtcc, you can use TCC as a backend for dynamic code generation.
Enhancements:
- initial PE executable format for windows version (grischka)
- #pragma pack support (grischka)
- #include_next support (Bernhard Fischer)
- ignore -pipe option
- added -f[no-]leading-underscore
- preprocessor function macro parsing fix (grischka)

Intel C++ Compiler application is a full fledged C/C++ compiler and debugger suite. Its aim is to provide outstanding performance for all Intel 32-bit and 64-bit processors, while not requiring the need for porting applications from other compilers.

It provides optimization technology, threaded application support, and features to take advantage of Hyper-Threading technology. It is substantially source and object code compatible with GNU C, providing fullest compatibility with GCC and G++ 3.x/4.x both in terms of code and of API. It is thereby also easy to integrate with existing development environments.

C Generic Library is a generic data structure library is a bunch of data structures that are designed and created in as generic a fashion as possible.
Each data structure will contain its own basic memory management, be able to handle any object type, and hopefully constraint to strict algorithmic constraints. When the library hits version 1.0, it will contain the following data structures:
- Doubly Linked List - Done
- List-based Queue - Done
- List-based Deque - Done
- List-based Stack - Done
- Vector - Done
- Vector-based Queue - Done
- Vector-based Deque - Done
- Vector-based Stack -Done
- Binary Tree - Done(No BFS/DFS iterators)
- Hash Table - In progress
- Priority Queue - In progress
- Heap - In progress
- Memory Manager
- Object Cache w/ Garbage Collection
- AB Tree
- Split Lists
- RB Tree
- AVL Tree
Enhancements:
- Support for compilation on Windows using VS.net was added.

C::Scan::Constants Perl module contains slurp constants from specified C header (.h) files.

SYNOPSIS

## Intended for use in your modules Makefile.PL file, to
## add DWIMery to use of C constants within your module.

use C::Scan::Constants;

my @hdr_files = (
"/path/to/first_header.h",
"/path/to/second_header.h",
);

## Slurp a list of constant information from C headers
my @constants = extract_constants_from( @hdr_files );

## Create the C, XS, and pure-Perl machinery needed to
## provide automagical access to C constants at runtime.
write_constants_module( "Your::Module", @constants );

This module provides an alternative to using the h2ph command to generate Perl header (.ph) files that are then subsequently required by your module code. When you need access to C numeric and enumerated type constants, especially in a dynamic source tree environment, there are times when youd like something a little more automagical and closely tailored to what you actually need. Now you have it, in this module.

C::Scan::Constants was born out of a recognition that ModPerl::CScan and ExtUtils::Constant provide a wealth of capabilities in the area of C code parsing and autogenerated XS access to C constants, but that the actual mechanisms for harnessing them to do those things were really rather opaque. This module should help take (most of) the mystery out of those activities.

C::Scan is a Perl module that can scan C language files for easily recognized constructs.

SYNOPSIS

$c = new C::Scan filename => $filename, filename_filter => $filter,
add_cppflags => $addflags;
$c->set(includeDirs => [$Config::Config{shrpdir}]);

my $fdec = $c->get(parsed_fdecls);

This description is VERY incomplete.

This module uses Data::Flow interface, thus one uses it in the following fashion:

$c = new C::Scan(attr1 => $value1, attr2 => $value2);
$c->set( attr3 => $value3 );

$value4 = $c->get(attr4);

Attributes are depending on some other attributes. The only required attribute, i.e., the attribute which should be set, is filename, which denotes which file to parse.

All other attributes are either optional, or would be calculated basing on values of required and optional attributes.

aifc2wav is an aifc (ima4, sowt or sdx2) to wav translator.

I made this little piece of software, because I wanted to listen to some khoomei music (23 Jul 2005: link appears to be dead), and some of those AIFC files were not handled by sox, nor xmms, nor mplayer. Those files were in AIFC IMA4 format.

How to use it?

Unzip the C file with gunzip.

You will need a C compiler (gcc is fine). Simply compile it (for instance gcc -o aifc2wav aifc2wav-4.c), and you are done.

It handles AIFC IMA4 files, AIFC SOWT files and AIFC SDX2 files, both mono and stereo (not sure for SDX2). The SOWT scheme has not been widely tested, if your file sounds strange, contact me. (Same for SDX2.)

It will produce a WAV file. Why WAV? Because WAV files are handled by almost everyone. If you want raw data, you can skip the 44 bytes long header (something like dd if=INPUT_FILE of=OUTPUT_FILE bs=44 skip=1 under unix). Or use sox, which is a good program.

It is supposed to work on any machine, little/big endian. The only problem that might appear is because of this silly 80 bits extended float used by those silly coders. Who needs that much precision for a frequency? Well, so they did, so they did. I dont know if I handle this correctly or not.