Assembly good first issues

This issue requires a manual proofreading of transcribed code for the ERASABLE_ASSIGNMENTS file against original scans. The task involves comparing 2635 lines of densely commented code, spanning 62 pages, and multiple pull requests are encouraged for manageable chunks of work.

This issue proposes adding native Mach-O support for macOS to the Rubix compiler. Currently, Rubix only generates ELF64 (Linux) and PE64 (Windows) executables. The goal is to modify the compiler to produce Mach-O binaries by adjusting segment/section declarations, syscall offsets, and symbol naming conventions, enabling the creation of runnable macOS executables.

This issue proposes adding support for ARM64 (AArch64) architecture to the Rubix compiler. The goal is to enable Rubix to generate machine code for devices like Raspberry Pi and Apple Silicon, requiring modifications to register mapping and instruction emission.

This issue aims to improve memory safety in array handling by adding a length header to dynamic arrays and implementing runtime bounds checking for array accesses. This will prevent out-of-bounds reads and writes, which currently lead to memory corruption, and instead trigger a clear runtime error.

This feature request aims to implement a pure assembly implementation of the BSD sockets API within the Rubix runtime. The goal is to provide native socket primitives for network programming without relying on libc, enabling the creation of network services and connected applications. The implementation will involve adding syscall wrappers in `lib/runtime.s` and potentially touching `src/parser.s`, with a key acceptance criterion being a functional HTTP server example.

This issue proposes to refactor the `rubixc` compiler to directly generate ELF64 executable binaries instead of relying on GNU assembler (`as`) and linker (`ld`). The goal is to eliminate external dependencies by writing the ELF header, program headers, and machine instructions directly into binary format.

This issue aims to complete the self-hosting compiler for Rubix, written in its own language (.ix). The goal is to expand the lexer, parser, and code emitter to support the full language specification, enabling Rubix to compile its own compiler without relying on the current assembly version. This will involve implementing features like structs, dynamic arrays, and float operators.

This issue aims to complete the Python bindings for hipDNN's TensorAttributes, exposing all public tensor metadata and pass-by-value APIs. This includes adding support for scalar tensor construction, various getter/setter methods for metadata like pass-by-value and compile-time constants, and handling ragged offsets and alignment. The goal is to achieve full frontend parity and enable DLPack integration without implementing the DLPack parsing itself.

This is an open Request for Comments (RFC) proposing a policy for AI-generated or AI-assisted contributions across gbdev projects. The policy aims to define acceptable levels of AI involvement in all community interactions, from code to discussions, and to communicate the community's stance on such contributions.

The user is encountering an 'Unimplemented instruction' error when running compiled BASIC and FORTRAN programs on a UCSD p-System IV.0 distribution. This error appears to be caused by missing floating-point support modules (specifically FP4.CODE) required by the interpreter (SYSTEM.INTERP). Attempts to manually link the interpreter with a recovered FP4.CODE module failed to integrate it correctly.

This issue addresses a "unsafe-buffer-usage" compiler warning in the `amd_inline_asm.hpp` and `generic_memory_space_atomic.hpp` files. The problem involves unsafe pointer arithmetic and direct pointer usage for buffer access, which needs to be fixed as a quality improvement. While a workaround was previously implemented, this issue calls for a full resolution.

The Spike reference model's CSR/HPM customization is only applied during initialization and is not reset-stable. This means hart resets can silently alter the model's behavior and cause desynchronization between modeled counters and readable CSRs.

This is a feature request for a screensaver that displays the current time. The user suggests potential enhancements like different fonts and clock styles, but emphasizes that a basic time display is sufficient. This is a straightforward enhancement request.

The user is reporting that extended logical FAT32 partitions on their CF card are not being recognized by the system. Windows displays them correctly as two partitions, but the system only sees the first one, with the second being a logical partition that isn't accessible.

This issue proposes an experiment to verify the impact of warp pipeline stage priorities on the performance of 8-wave GEMM kernels. The goal is to measure TFLOPS and MFMA efficiency under different priority configurations to determine if the current 'memory-outranks-compute' setting is beneficial or inert.

A bug in the frontend's prediction logic causes the RAS (Return Address Stack) push/pop operations to be incorrectly cleared when a not-taken branch in a lower fetch slot is followed by a call or return in an upper fetch slot. This leads to mispredictions for return addresses, corrupting the stack's state.

This issue proposes extending relaxed affine tensor shape requirements for BatchNorm operations within hipDNN. Currently, this feature is only implemented for the base BatchNorm operation, and needs to be applied to BatchNormBackwardNode, BatchNormInferenceNode, and BatchNormInferenceNodeVarianceExt to provide full user benefit.

This issue proposes exposing a comprehensive set of hipDNN Graph lifecycle, plan management, inspection, and serialization APIs to Python. The goal is to make these functionalities accessible for users to build, inspect, execute, and serialize compiled graph plans, including support for runtime shape overrides. This will involve adding new Python bindings and ensuring compatibility with existing behaviors and error reporting mechanisms.

This issue addresses gaps in hipDNN's handling of SDPA backward gradient property inference and validation. Currently, hipDNN infers gradient dimensions correctly but accepts caller-supplied gradient metadata too loosely, potentially allowing incorrect shapes to pass validation. It also lacks proper validation for caller-provided strides, which can lead to backend failures.

The user is experiencing a system hang after calling a BIOS function (hbios CIOOUT) which leads to a `RLCA` instruction. This hang occurs both during single-stepping and when running from a floppy, with the floppy drive remaining active. The user suspects a bug or a misunderstanding of how `cbios` should be used, as standard CPM output works fine.

This issue proposes updating various platform-specific structs in the codebase to utilize Go 1.23's new `structs.HostLayout` type. This change is intended to guarantee that these structs conform to the C ABI, mitigating potential future compatibility issues if Go's internal struct layout were to change.

A bug has been identified in the CVA6 project where a debug loop iterates beyond the bounds of unpacked arrays. This out-of-bounds access, occurring when the loop index exceeds 10 for arrays with 11 elements (indexed 0-10), can lead to simulator warnings or undefined behavior. The suggested fix is to limit the loop to the actual size of the arrays, preferably using the `$size()` function for better maintainability.

This bug report indicates that the `frontend/instr_scan` module in CVA6 incorrectly identifies reserved or invalid compressed instructions as valid RVC jump instructions. Specifically, `c.jr` with `rs1=x0` and `c.ebreak` are being misclassified, leading to incorrect behavior in the instruction decoding pipeline.

This issue proposes adding user feedback when the input buffer in `read_line` reaches its maximum length. Currently, exceeding the limit results in silent input rejection. The task is to implement a visual or auditory cue (like a PC speaker beep) to inform the user that the buffer is full, while ensuring existing functionality like Enter, Backspace, and history navigation remains unaffected.

This issue proposes adding a new 32-bit decimal printing routine, `print_dec32`, to the kernel's assembly code. This is needed because the existing 16-bit routine limits the display of usable memory to 65535 MB, which is inaccurate on systems with more RAM. The new routine will allow for accurate display of larger memory values.

This issue proposes implementing signed GitHub releases to improve security and verification. The plan involves researching best practices, setting up necessary tooling, signing the next release, and updating the Debian packaging repository to verify these signatures.

This issue is a "good first issue" related to graphics and store signs for the Ruby/Sapphire game boards. It specifically points to the `data/board_data/{board}.inc` files as the area for modification.

This issue requests the implementation of graphics for the 'Sapphire Ball Power Up' and 'Hole' lights within the game's data files. The developer is directed to use the 'Ruby board' as a reference for how graphics are organized and folded.