Live data from Hacker News

Usability Improvements in GCC 15

developers.redhat.com

211–220 of 231 posts

Re: Usability Improvements in GCC 15

#211

Earlier quoted context omitted.

Apple, Arm, OpenBSD, FreeBSD have all switched to Clang.

Why did OpenBSD switch to clang? Licensing issues?

Could be. They stuck with GPL2 GCC 4.x for a while. IIRC, they never switched to GPL3 GCC5+

Re: Usability Improvements in GCC 15

#212
post #82
post #15

Earlier quoted context omitted.

It's not like GCC or the embedded toolchains are a shining beacon of ISO compliance... and if you mean video game consoles, are any of them using GCC today? Sony and Nintendo are both LLVM and Microsoft is Microsoft

GCC has very good ISO compliance and ISO C23 is better supported than in Clang (which I expect to catch up soon though)

"substantially complete" C99 even

Re: Usability Improvements in GCC 15

#213
post #47

Earlier quoted context omitted.

Why would anyone bother with GCC then? :P

I believe GCC still wins by far on support for weird CPUs and embedded systems.

It's still a crapshoot.

GCC on xtensa adds extra instructions in several places.

GCC on Arm Cortex-M0 has awful register allocation, and M0 has half as many registers as most ARMs...

Re: Usability Improvements in GCC 15

#214
post #4

I hope gcc remains the default in Linux due to the GPL. But I expect someday clang will become the default. Plus I heard COBOL was merged in with the compiler collection, nice!

Yup, COBOL is that overnight sensation 4 years in the making. GCC COBOL is foremost an ISO COBOL compiler, with some extensions for IBM and MicroFocus syntax. We also extended gdb to recognize COBOL, so the GCC programmer has native COBOL compilation and source-level debugging.

Re: Usability Improvements in GCC 15

#215

Earlier quoted context omitted.

Browser makers should straight up remove the JS API for interacting with history. There are legitimate uses for it, but the malicious actors far outweigh the good ones at this point. Just remove it.

This type of thinking is what doomed uBlock Origin. I strongly disagree.

To be fair, uBlock Origin has always been a special case. It's so good and so important and so trusted that it should have access to browser internals that normal extensions can't access.

Honestly, uBlock Origin shouldn't be an extension to begin with, it should be a literally built in feature of all browsers. Only reason it's not is we can't trust ad companies to maintain an ad blocker.

Re: Usability Improvements in GCC 15

#216
post #82

Earlier quoted context omitted.

GCC has very good ISO compliance and ISO C23 is better supported than in Clang (which I expect to catch up soon though)

Knowing the history of GCC (more focused on C) and Clang (more focused on C++), it makes sense to me that GCC has better ISO C compliance. Clang has a very nice specific page for ISO C version compliance: https://clang.llvm.org/c_status.html#c2x I could not find the same for GCC, but I found an old one for C99: https://gcc.gnu.org/c99status.html CppRef has a joint page, but honestly, I am more likely to believe a pag…

I would not say that GCC is more focused on C. Also in GCC there is a lot more effort going into C++ than C. C is generally neglected, which is sad given its importance.

GCC's support for C23 is essentially complete. Clang is mostly catching up, but features I need that I am missing are storage class in compound literals and tag compatibility. It is also sad that Clang does not implement strict aliasing correctly (it applies C++'s rules also in C).

Re: Usability Improvements in GCC 15

#217
post #90

Big fan of all of this except for the emojis in my console

If you're using an OS that honors your font choices (i.e., not macOS), you can use a font like Symbola to provide emoji so that they're stylized, monochrome, and vectorized, rather than incongruous color bitmap images. That helps them play nice with terminal colorschemes and things like that. I'm not aware of any emoji fonts like Symbola which provide a monospace typeface, though. That would be a great option.

By honoring font choices, do you mean the ability to overwrite emojis as well? I’ve never had issues using custom/nerd fonts, but it’s true that the emojis have stayed true to the Apple style so far.

Re: Usability Improvements in GCC 15

#218

Earlier quoted context omitted.

Of course you can . I'd argue you shouldn't, but that's beside the point. There is clearly a difference between people being able to do something, and the compiler forcing it on them.

But the compiler isn't forcing it on anyone?

How isn't it? It's setting it by default which is equivalent to forcing it for the huge majority of users who won't even know that such a thing as a flag to disable these emojis exists

Re: Usability Improvements in GCC 15

#219

Already looking forward to `grep`ing warning emojis in output. What's next? Poop emoji for errors?

Same with their ‘’ quotation marks. I've had cases where I was searching for "'something'", and it didn't find anything, because it was printed as "‘something’".

Re: Usability Improvements in GCC 15

#220
post #217
post #90

Earlier quoted context omitted.

If you're using an OS that honors your font choices (i.e., not macOS), you can use a font like Symbola to provide emoji so that they're stylized, monochrome, and vectorized, rather than incongruous color bitmap images. That helps them play nice with terminal colorschemes and things like that. I'm not aware of any emoji fonts like Symbola which provide a monospace typeface, though. That would be a great option.

By honoring font choices, do you mean the ability to overwrite emojis as well? I’ve never had issues using custom/nerd fonts, but it’s true that the emojis have stayed true to the Apple style so far.

Indeed. Emoji are just characters, rendered via some font just like any text character. On non-Apple operating systems, you can select emoji sets via font configuration.

You can do it on macOS as well, but you have to disable SIP and modify/replace the files for the Apple Color Emoji font, because some widely used GUI libs are hardcoded to use it.

Idr the situation on Windows except that emoji glyphs are inherited from your other font choices, if your chosen font includes emoji. But on Linux it's generally easy to configure certain font substitutions only for some groups of characters, like emoji.

Post reply on HN