The Glasgow Haskell Compiler (GHC) is a state-of-the-art compiler and interactive environment for the functional language Haskell.

The Glasgow Haskell Compiler (GHC) is a state-of-the-art compiler and interactive environment for the functional language Haskell.

The Glasgow Haskell Compiler (GHC) is a state-of-the-art compiler and interactive environment for the functional language Haskell.

The Glasgow Haskell Compiler (GHC) is a state-of-the-art compiler and interactive environment for the functional language Haskell.

The Glasgow Haskell Compiler (GHC) is a state-of-the-art compiler and interactive environment for the functional language Haskell.

The Glasgow Haskell Compiler (GHC) is a state-of-the-art compiler and interactive environment for the functional language Haskell.

The Neko programming language is a high-level dynamically typed programming language. It can be used as an embedded scripting language. It has been designed to provide a common runtime for several different languages. You can easily extend the language with C libraries. You can also write generators from your own language to Neko and then use the Neko Runtime to compile, run, and access existing libraries.

Neko has a compiler and a virtual machine. The Virtual Machine is both very lightweight and well optimized, so it can run very quickly. The VM can be easily embedded into any application and your libraries can be accessed using the C foreign function interface.

You can use the compiler as standalone command line executable separate from the VM, or as a Neko library to perform compile-and-run functions for interactive languages.

HashLink (HL) is a virtual machine for the Haxe language. It can run bytecode produced by the Haxe compiler, or converted to C by HL. The HashLink runtime includes the following features:

• Fully compatible with the Haxe specification

• Support file I/O, regular expressions, network, etc.

• Unicode strings by default

• Mark-and-not-sweep Garbage Collector

• x86 and x86-64 HL/C compilation

• x86 and x86-64 HL/JIT compilation

While the standard HL runtime provides support for Haxe standard library, HashLink also provides several libraries that can optionally be used to build HL-specific applications. This includes the FMT library for compression and image support and SDL for mouse, keyboard, and game controller support, OpenGL, and more.

Haxe is a toolkit based on a modern, high level, static-typed programming language, a cross-compiler, a complete cross-platform standard library and ways to access each platform's native capabilities. This package includes the compiler and library manager.

Open Logic implements commonly used design units in a reusable and vendor/tool-independent way. It is written following the VHDL 2008 standard, but can also be used from System Verilog.

Open source materials intended for reference by the IEEE standard 1076, as approved and published by the VHDL Analysis and Standardization Group.

The JSON-for-VHDL library provides a parser to query JSON data structures from external files on disk. It provides a context to be used in the declarative section of design units.

Neorv32 is a small, customizable 32 bits microcontroller-like system on chip written in platform-independent VHDL.

This package provides a dev.cpio file usable as a base for heads' initrd.

This package provides tool, language and decoders for working with binary data, aiming to be jq, hexdump, dd and gdb for files combined into one.

bvi is a display-oriented editor for binary files, based on the vi text editor.

hexedit shows a file both in ASCII and in hexadecimal. The file can be a device as the file is read a piece at a time. You can modify the file and search through it.

This package provides a C-like domain-specific language used for specifying patterns in the ImHex Hex Editor.

Dhex is hex editor which includes a diff mode, which can be used to easily and conveniently compare two binary files. It is based on Ncurses and is themeable.

ImHex is a hex editor with many advanced features that can often only be found in paid applications. Such features are a completely custom binary template and pattern language to decode and highlight structures in the data, a graphical node-based data processor to pre-process values before they're displayed, a disassembler, diffing support, bookmarks and much much more.

cowsql (/ˈkaʊ,siːkwəl/ listen) is a C library that implements an embeddable and replicated SQL database engine with high availability and automatic failover.

cowsql extends SQLite with a network protocol that can connect together various instances of your application and have them act as a highly-available cluster, with no dependency on external databases.

Libqb is a library with the primary purpose of providing high-performance, reusable features for client-server architecture, such as logging, tracing, IPC and polling. Libqb is not intended to be an all-encompassing library, but instead provide focused APIs that are highly tuned for maximum performance for client-server applications.

Kronosnet, often referred to as knet, is a network abstraction layer designed for High Availability use cases, where redundancy, security, fault tolerance and fast fail-over are the core requirements of your application.

Kronosnet is the new underlying network protocol for Linux HA components (Corosync), that features ability to use multiple links between nodes, active/active and active/passive link failover policies, automatic link recovery, FIPS compliant encryption (nss and/or openssl), automatic PMTUd and in general better performances compared to the old network protocol.

Pacemaker is a high-availability cluster resource manager.

It achieves maximum availability for your cluster services (a.k.a. resources) by detecting and recovering from node- and resource-level failures by making use of the messaging and membership capabilities provided by Corosync.

It can do this for clusters of practically any size and comes with a powerful dependency model that allows the administrator to accurately express the relationships (both ordering and location) between the cluster resources.

Virtually anything that can be scripted can be managed as part of a Pacemaker cluster.