This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.
Update: I've disabled comments as of 2025-01-26 to avoid everyone having notifications for something a year on if someone wants to suggest a correction. Folks are free to email to suggest corrections still, of course.
| Clang GCC Xcode | |
| 2023.03.17 16.0.0 | |
| 2022.09.06 15.0.0 | |
| 2022.03.25 14.0.0 | |
| 2021.10.04 13.0.0 | |
| 2021.06.01 9.4 | |
| 2021.04.14 12.0.0 | |
| 2020.10.12 11.0.0 | |
| 2020.03.24 10.0.0 | |
| 2020.03.04 8.4 |
This is a minimal example that shows the 4 main building-blocks needed to write concurrent/async coroutine code.
This example defines a basic task type that fulfills this purpose.
The semantics of inline are one of the areas where C and C++ are pretty different. This post is about the C++ semantics, but the history is interesting, so here's a short summary of it.
The meaning of "inline" is intuitively easy to understand: It gives the compiler a hint that it'd be nice if a function could be inlined. It gets a bit complicated because of two issues:
| #!/bin/bash | |
| CONFIG_PATH=~/.config/Code | |
| for i in $CONFIG_PATH/User/workspaceStorage/*; do | |
| if [ -f $i/workspace.json ]; then | |
| folder="$(python3 -c "import sys, json; print(json.load(open(sys.argv[1], 'r'))['folder'])" $i/workspace.json 2>/dev/null | sed 's#^file://##;s/+/ /g;s/%\(..\)/\\x\1/g;')" | |
| if [ -n "$folder" ] && [ ! -d "$folder" ]; then | |
| echo "Removing workspace $(basename $i) for deleted folder $folder of size $(du -sh $i|cut -f1)" |
| use git2::Delta; | |
| use git2::DiffOptions; | |
| use git2::Repository; | |
| use std::collections::BTreeMap; | |
| use std::env::set_current_dir; | |
| use std::process::Command; | |
| fn main() { | |
| let repo = Repository::open_from_env().unwrap(); | |
| set_current_dir(repo.workdir().unwrap()).unwrap(); |
| /* | |
| See https://gitlab.com/nedopc/npc5/blob/master/emu-rv32i.c for the latest version, with more features and less bugs :-) | |
| RISCV emulator for the RV32I architecture | |
| based on TinyEMU by Fabrice Bellard, see https://bellard.org/tinyemu/ | |
| stripped down for RV32I only, all "gotos" removed, and fixed some bugs for the compliance test | |
| by Frank Buss, 2018 | |
| Requires libelf-dev: |
What is strict aliasing? First we will describe what is aliasing and then we can learn what being strict about it means.
In C and C++ aliasing has to do with what expression types we are allowed to access stored values through. In both C and C++ the standard specifies which expression types are allowed to alias which types. The compiler and optimizer are allowed to assume we follow the aliasing rules strictly, hence the term strict aliasing rule. If we attempt to access a value using a type not allowed it is classified as undefined behavior(UB). Once we have undefined behavior all bets are off, the results of our program are no longer reliable.
Unfortunately with strict aliasing violations, we will often obtain the results we expect, leaving the possibility the a future version of a compiler with a new optimization will break code we th
