theshank the-shank

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

To create a bidirectional unix IPC:

Server creates a sockets and binds it to an address (typically a file). Do NOT use connect as all send/recv operation will be done using connect's address!
Client creates a socket and binds it to its own address. However the socket connects to the address of server.
Server uses recv_from to get data from socket along side with the address of the client that sent the data. This way it can use the address to send a response back to client.

Example in `Rust`

`server.rs`

Announcing cargo-udeps

One of the biggest issues that most people have with Rust are the long compile times. One of the reasons why compile times are so long is because many projects use quite a few dependencies from crates.io. Your dependencies have dependencies of their own, and they in turn have dependencies as well, and so on. This results in really big graphs of crates that all have to be compiled by cargo. Sometimes however, a crate actually doesn't use anything of some of its dependencies. Then those dependencies can be removed, resulting in faster builds for that crate. But how do you detect them? Often they sit in Cargo.toml for a long time until someone discovers they are actually unused and removes them (example). This is where cargo-udeps comes in. cargo-udeps is an automated tool to find dependencies that were specified in Cargo.toml but never used in the cra

	#! /bin/bash

	# ECHO COMMAND
	# echo Hello World!

	# VARIABLES
	# Uppercase by convention
	# Letters, numbers, underscores
	NAME="Bob"
	# echo "My name is $NAME"

	# gruvbox-dark colorscheme for kitty
	# snazzy theme used as base

	foreground #ebdbb2
	background #272727
	selection_foreground #655b53
	selection_background #ebdbb2
	url_color #d65c0d

	# black

	defmodule MyApp.Factory do
	use ExUnitProperties
	alias MyApp.{Repo, User, Comment}

	### Generators

	def generator(:user) do
	gen all name <- string(:alphanumeric, min_length: 2),
	email <- generator(:email),
	age <- integer(10..130) do

	# Base16 Gruvbox dark, hard 256 - alacritty color config
	# Dawid Kurek ([email protected]), morhetz (https://github.com/morhetz/gruvbox)
	colors:
	# Default colors
	primary:
	background: '0x1d2021'
	foreground: '0xd5c4a1'

	# Colors the cursor will use if `custom_cursor_colors` is true
	cursor:

	# Colors (Gruvbox Material Dark Medium)
	colors:
	primary:
	background: '0x282828'
	foreground: '0xdfbf8e'

	normal:
	black: '0x665c54'
	red: '0xea6962'
	green: '0xa9b665'

	from . import app
	from flask.sqlalchemy import get_debug_queries

	if app.debug:
	app.after_request(sql_debug)


	def sql_debug(response):
	queries = list(get_debug_queries())
	query_str = ''