Notices by pinskia (pinskia@hachyderm.io)

@void_friend "barring the use of the ABI-breaking -fshort-enums option" Except some targets' ABI requires that (e.g arm eabi; at least for aarch64 abi arm decided not to do that by default).

@navi I can think of examples where the base operator might not show up at least directly when dealing with operator overloads. E.g. you provide a "backwards" compatible API for the overload. Like say multiprecision; then you either have the backwards compatible API call into the new overload instead of the other way around.

And yes it is awful semantics for more than above too.

@12 @puppygirlhornypost2"they actively block building newer gcc on Solaris 10" well considering Sun^wOracle no longer supports Solaris 10 and the folks who support Solaris for GCC are truely volunteers, it is hard to support older Solaris. If you want to come up with a path to support it and put in the maintance work in it; I suspect the maintainers for solaris on the GCC will like the help.

@pervognsen Removal of non-prototypes declaration and implicit declarations is nice too.

@aachrisg Same is true even on aarch64:
https://godbolt.org/z/TWenG8vbh

@mastodonmigration @blogdiva Sounds very Elizabeth Holmes like.

@14mission @Alon @mekkaokereke It was all about the rich needing to bypassing the city and avoiding seeing what they are doing to it. Nothing else.

@luatic @lizzy `import std;` in C++26 :) and the plan IIRC is to include the std module for GCC 15.

@luatic @lizzy "even if you skip the iostream verbosity and use C puts" What are you using? C++98 or something? std::print exists in C++23 so :).

@luatic @lizzy With C++23 (if the std module exists; I think std module only made it into C++26 though), it is would be just `import std; int main() { std::print("Hello world!\n"); }`

I look fat in this picture but I do feel cute though. Oh the cat made an appearance in the mirror to say hi to the internet too.

@lizzy I prefer no x86 ISAs. But when it comes to x86 ISA, AT&T Syntax is easier to understand than Microsoft^wIntel format.

@hipsterelectron That is a good question, there are some global reviews which could ok the patch though. In this case the big change is just:
`/#define INCLUDE_MEMORY/d`.
which to some extend is an obvious enough change that nobody will mind.
Note GCC has an obvious rule (https://gcc.gnu.org/gitwrite.html) which has been used before but folks try not to abuse it.

I have used the obvious rule to fix a build/bootstrap failure, to commit some new testcases, some doc fixes . But I try not to abuse it.

@navi I just got this spam too. WTF?

I am working on a patch which touches over 500 files in GCC. Well I could get away with only touching 5 or so but I want to remove the `#define` in the files which is no longer needed to be defined.

#LifeAsAGCCDeveloper

@RL_Dane @cobweb You missed the `(j/k)` part. And cpan is 10x better than rust and pip. rust package manager is just to show there are many duplicated packages that might have security holes in it (not due to memory issues though).

@cobweb @RL_Dane it is about cpan (j/k)

PeanutButter, why do I love you so much. I could just swim in you for days on end. Eat you up. The extra chunky version of you is the best. Running on a Toasted buns. So good.

Well improving slightly aarch64 builtins. Always love doing that ...

Repeat after me, don't reply to folks on reddit even in r/gcc and then decide to look at their profile to just find racist/transpobic things posted.
I replied to someone on r/gcc to help them out. And then when they didn't understand simple C, I went to look at their posts. They posted a link to someone going off on a "purge of anti-woke folks" from the Godot game engine. It was a youtube channel that was pro-open source too.