Dani (:cxx: Antifascista)
C++ nerd, WG21, INFJ, electrical engineer, she/her, science connoisseur, jazz addict
Sponsoring member: Wikimedia, Greenpeace, Digitalcourage, noyb, and more
@DanielaKEngert
- Posts
- 5,899
- Followers
- 557
- Following
- 263
-
RE: https://social.heise.de/@heiseonline/116579236611912317
Unsere "Regierung" sollte endlich mal *für* die Interessen der Mehrheit der Bevölkerung handeln, anstatt irgendwelchen Quatsch zu ventilieren.
-
RE: https://follow.ethanmarcotte.com/@beep/116574876011931316
Wow, what a statement!
Quote from the article :
"... it is not a technology problem. It is a leadership problem. AI does not make bad executives worse. It gives them a faster way to prove they are bad."
-
CW: "colourful language" ahead
This pile of shit called CMake and package managers is happening again.
Back from the last ISO C++ meeting in Croydon where we voted on the appetite for inclusion of mp-units into the next standard, I tried to get even the *chance* to compile it using the recommended Conan, CMake, and other dependencies.
And failed spectacularly again:
* at some point, the current VS2026 compiler is spat out ("what even is this thing" coming from the attempt to deal with Catch2.Ok, switch off testing for now.
* next some complaints about "avg_speed-headers" missing some support from CMake. What the heck?
The fact that compiler options seem incomplete for full C++23 conformance is certainly only minor, right?
To me, this sounds like building with VS is seriously lacking (in particular CMake).
Therefore I will do what I usually do: move CMakeLists.txt over to a build system, that works for years now, and retain only the source tree.
-
@uecker @Codeberg @mattgodbolt
Wat?As a Codeberg member myself, I checked your example here as well. The @compiler_explorer UI seems to handle the link just fine: if you click on the offered link, the raw file content is shown as you would expect. Then, the compiler is complaining about the file where the CE-internal machinery has supposedly put down the source text that it has downloaded from Codeberg.
So, there seem to be two different code paths in play. One, close to the UI, that works. And another one, hidden in the background, that doesn't.
-
I'm a bit ashamed to admit that I once owned a quite extensive list of "unintended" opcodes in then popular microprocessors like the 6502 or the Z80, but somehow lost it after having finished university and moved on to later technologies. 😭
So, at some time between the end of the 80s and now, my virtual cat or imagined dog must have eaten it. 😉
May be you can still find that stuff on the interwebs, hidden somewhere in between all that AI slop. Wikipedia might help you.
To give you a hint from ancient memories: The Z80 could architecturally access its registers in both 8 bit and 16 bit chunks - except for the IX and IY ones. Documented as index registers like the well-known HL one (i.e. concatenated H and L), they were portrayed as non-splittable. But they were as people found out, giving you more independently manipulatable registers for situations where you could take advantage of that capability. The IX/IY prefixes were functional pretty much everywhere. Later implementations of the Z80 architecture may have lost that undocumented capability.