News for hackers. Stuff that matters.
Re:Memcmp being wrongly stripped like strcmp by gnud on Friday October 09, 2020 @05:05AM (#24728109)
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.

Re:Memcmp being wrongly stripped like strcmp by abollaert on Friday October 09, 2020 @05:13AM (#24728144)
Thing is that people try to look for conspiracies where this is probably just an honest mistake.
Re:Memcmp being wrongly stripped like strcmp by gnud on Friday October 09, 2020 @06:54AM (#24728658)
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?

Re:Memcmp being wrongly stripped like strcmp by nurettin on Friday October 09, 2020 @04:50PM (#24734298)
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.
Re:Memcmp being wrongly stripped like strcmp by hvdijk on Saturday October 10, 2020 @08:36AM (#24738530)
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.
Re:Memcmp being wrongly stripped like strcmp by nurettin on Saturday October 10, 2020 @12:10PM (#24739887)
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.