1 7 3 dup rot 173duprot

Foreward

This document was originally written several years ago. At the time I was working as an execution core verification engineer at Arm. The following points are coloured heavily by working in and around the execution cores of various processors. Apply a pinch of salt; points contain varying degrees of opinion.

It is still my opinion that RISC-V could be much better designed; though I will also say that if I was building a 32 or 64-bit CPU today I'd likely implement the architecture to benefit from the existing tooling.

Mostly based upon the RISC-V ISA spec v2.0. Some updates have been made for v2.2

Original Foreword: Some Opinion

The RISC-V ISA has pursued minimalism to a fault. There is a large emphasis on minimizing instruction count, normalizing encoding, etc. This pursuit of minimalism has resulted in false orthogonalities (such as reusing the same instruction for branches, calls and returns) and a requirement for superfluous instructions which impacts code density both in terms of size and

About

It is possible to redirect some input to TTY device by standard IO redirection.

echo ahoj > /dev/tty1

Such redirection will however end in the output buffer of the TTY device so the characters will be ghosts - visible on the terminal, but not effective. It is, in fact, not possible by standard tools to redirect input to terminal as if it is a real input from keyboard.

Orthodox C++

What is Orthodox C++?

Orthodox C++ (sometimes referred as C+) is minimal subset of C++ that improves C, but avoids all unnecessary things from so called Modern C++. It's exactly opposite of what Modern C++ suppose to be.

	// Jeff Preshing's example that shows the reordering of Intel CPUs made to
	// work on both Linux and macOS.
	//
	// Original source:
	//
	// https://preshing.com/20120515/memory-reordering-caught-in-the-act/
	//
	// Apple semaphore change is based on the answer by dho at:
	//
	// https://stackoverflow.com/questions/27736618/why-are-sem-init-sem-getvalue-sem-destroy-deprecated-on-mac-os-x-and-w

	/*
	* Minimal .NET Forth implementation. Just an experiment. Do not use for anything serious.
	* by Tycho Luyben (https://github.com/tluyben)
	*
	* The only 'primitive' (built-in) is an foreign function interface word which allows you to define
	* whatever is needed, for example:
	*
	* hello System.String System.Console.WriteLine ffi
	*
	* will print hello.

	WAYLAND_PROTOCOLS=/usr/share/wayland-protocols

	# wayland-scanner is a tool which generates C headers and rigging for Wayland
	# protocols, which are specified in XML. wlroots requires you to rig these up
	# to your build system yourself and provide them in the include path.
	xdg-shell-protocol.h:
	wayland-scanner server-header \
	$(WAYLAND_PROTOCOLS)/stable/xdg-shell/xdg-shell.xml $@

	xdg-shell-protocol.c: xdg-shell-protocol.h

	# Config that is very close to a i3 window manager's keybinding.

	set -s escape-time 0
	setw -g aggressive-resize on

	# First remove all keybindings
	unbind-key -a

	# List keys
	bind-key ? list-keys

	#!/bin/bash

	#no PATH, no way to accidently run any programs
	PATH=''

	#useful variables
	term_height=0
	term_width=0
	term_scroll_height=0
	status_line_row=0

	default:
	cc ccsmtp.c -o ccsmtpd -lpthread