Hacker News Reader

Comment by nurettin | Hacker News Reader

This thread is the unfortunate side effect of a highly skilled developer making a simple mistake which can be understood and thus scrutinized by your average web guy. People thinking it is a compiler bug, people who want to milk controversy because some test in some bitcoin library dependency is affected. You are not getting a discussion worth a spit because the topic is extremely trivial and there is no genuine depth in it.

View on HN

What do you mean? This is from the first patch message on the mailing list:

> An enhancement to GCC 10 to improve the expansion of strncmp calls with strings with embedded nuls introduced a regression in similar calls to memcmp.

That patch was approved and merged. Sounds like a compiler bug to me.

Thing is that people try to look for conspiracies where this is probably just an honest mistake.

I agree on the conspiracy stuff. But GGP seemed to say it was the reporters fault, and not a compiler bug.

From what I understand, it _was_ a compiler bug, and it's now being fixed. That's right, isn't it?

It was posted in the correct place, but you can avoid it entirely using the same compiler by skipping builtins. So it is a library bug rather than platform lexer parser or optimizer.

Builtins are functions that are built into the compiler rather than (or in addition to) being provided as part of any library. That is why they are called builtins. A bug in their implementation is a compiler bug, not a library bug.

It is a bug in a library which you can avoid using with a flag. Take what you want from that. I won't reply to this nonsense.

Reply on news.ycombinator.com