Is there any reason to ask this? GCC plugins have been good since 4.8. 4.5 lacked some essential features; 4.6 would be fine if not for the annoyance of trying to support a plugin that works across the C++ transition. Of course, you can just use the Python plugin to save yourself a lot of sanity ...

They work. You can use them? They haven't gone anywhere and the Linux kernel relies on them extensively, among other things.

> What I wish GCC and Clang would do instead, is formally document the magic ANSI C89 incantations that trigger the optimization, e.g. `#define ROL(x, n) (((x) << (n)) | ((x) >> (64 - (n))))`. That way we can have clean portable code with less #ifdef hell along with assurances it'll go fast when -O is passed.

Well they don’t commit to that happening, so they want to provide you with an alternative.

> How about some __int128 literals

There are _BitInt literals (wb and uwb), look adequate https://godbolt.org/z/xjEEM5Pa4 despite clang's "is a C23 extension" noise.

I do not want any emojis from my compiler's output, heck, in my terminal in general. Please, do not make it the default behavior.

(BTW my terminal does not even support emojis.)

Why would you grep for the emoji? The actual pattern you want to match is the standard format of the error message that proceeds it, which hasn’t changed in eons:

    my $line = "infinite-loop-linked-list.c:30:10: warning: infinite loop [CWE-835] [-Wanalyzer-infinite-loop]";
    grammar gcc {
        token filename { <-[:]>+ };
        token linenumber { \d+ };
        token colnumber { \d+ };
        token severity { info|warning|error };
        token message { .* $$ };
        regex diagnostic {        <filename>
                           [\:]   <linenumber>
                           [\:]   <colnumber>
                           [\:]\s <severity>
                           [\:]\s <message>
                         };
        token TOP { <diagnostic> };
    }
    
    say gcc.parse($line);

which when run produces the obvious output:

    ｢infinite-loop-linked-list.c:30:10: warning: infinite loop [CWE-835] [-Wanalyzer-infinite-loop]｣
     diagnostic => ｢infinite-loop-linked-list.c:30:10: warning: infinite loop [CWE-835] [-Wanalyzer-infinite-loop]｣
      filename => ｢infinite-loop-linked-list.c｣
      linenumber => ｢30｣
      colnumber => ｢10｣
      severity => ｢warning｣
      message => ｢infinite loop [CWE-835] [-Wanalyzer-infinite-loop]｣

I’ll leave handling filenames containing colons as an exercise for the reader.

The emoji just focus the reader’s eye on the most critical line of the explanation.

Why wouldn't you just keep search for the "warning:" or "error:" anchor, like people (and editors) have been doing forever? Even if that wasn't true it's not like searching for emojis is hard anyway. If it takes longer than 2 seconds for you to open a picker then you should ask for a refund for your computer.

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’".