nonarkitten

This is a work-in-progress note pad of all the things I've found about gcc to make the best code possible.

Do not use ixemul

Ever.

Generally, most other PC libraries are okay, including SDL and OpenGL, but ixemul will take awesome performing code and make it run like it's walking through a tar pit -- especially on any stdio file operations. When porting "small and dirty" POSIX applications where performance does not matter, then who cares, use ixemul. For everything else, don't. Don't even use libnix. Try as much as possible to use AmigaOS native functions like AllocVec over C standard functions like malloc.

Using register parameters

zserge

#define _GNU_SOURCE
#include <errno.h>
#include <sched.h>
#include <signal.h>
#include <stdio.h>
#include <stdlib.h>
#include <sys/mount.h>
#include <sys/stat.h>
#include <sys/syscall.h>
#include <sys/types.h>

zserge

# A tiny 16-bit guest "kernel" that infinitely prints an incremented number to the debug port

#
# Build it:
#
# as -32 guest.S -o guest.o
#	ld -m elf_i386 --oformat binary -N -e _start -Ttext 0x10000 -o guest guest.o
#

.globl _start

shakna-israel

Let's Destroy C

I have a pet project I work on, every now and then. CNoEvil.

The concept is simple enough.

What if, for a moment, we forgot all the rules we know. That we ignore every good idea, and accept all the terrible ones. That nothing is off limits. Can we turn C into a new language? Can we do what Lisp and Forth let the over-eager programmer do, but in C?

---

jblang

RC2014 Links

I couldn't find a comprehensive list of links for the RC2014 so I started one. Suggestions welcome.

Documentation

• RC2014 Website - descriptions of all official RC2014 boards
• RC2014 Github Repo - official ROMs and example code
• RC2014 CP/M Guide - guide to setting up CP/M on the RC2014
• Decoding RC2014 ROM Labels - explanation of what RC2014 ROM labels mean
• RC2014 Module Template - Kicad template for building RC2014 boards