News for hackers. Stuff that matters.
Re:C’s Biggest Mistake by throwawaymaths on Sunday July 02, 2023 @08:18PM (#36567229)
Not only that, but some have solved it while maintaining compatibility with null terminated strings. Null terminated strings, after all, are sometimes more efficient.
Re:C’s Biggest Mistake by zerodensity on Sunday July 02, 2023 @09:40PM (#36567703)
Can't think of a single case where null terminated strings are more efficient. Could you give some examples?
Re:C’s Biggest Mistake by umanwizard on Sunday July 02, 2023 @09:49PM (#36567755)
If you have to walk the string anyway, the null terminator has no downside.
Re:C’s Biggest Mistake by zerodensity on Sunday July 02, 2023 @10:58PM (#36568214)
According to the bible (https://www.agner.org/optimize/) it's faster to use a loop with length than walking though a pointer so not having a length will make it slower to walk the string whole also making things like simd optimizations harder for the compiler to do.
Re:C’s Biggest Mistake by throwawaymaths on Monday July 03, 2023 @01:54AM (#36569374)
That doesn't make sense. If you have loop with length you have to check both the content of the byte and the index; if you have null terminated strings you only check the content of the byte.
Re:C’s Biggest Mistake by yakubin on Monday July 03, 2023 @04:15AM (#36570207)
When you have the length, you can unroll the loop, so that you e.g. do 4 iterations at a time. With NUL you can’t do that. Moreover, loop iteration can be done in parallel (instruction-level parallelism) with processing the content of the string, since there is no data dependency between the two. With NUL you introduce a data dependency.
Re:C’s Biggest Mistake by throwawaymaths on Monday July 03, 2023 @09:39AM (#36572723)
You can't always do those things. Yes, pointer length is almost always faster. But it's not always faster.

https://lemire.me/blog/2020/09/03/sentinels-can-be-faster/?a...

Re:C’s Biggest Mistake by yakubin on Monday July 03, 2023 @12:46PM (#36575509)
You can. Here is my version: <https://godbolt.org/z/91KecEfbM>

Results:

   N = 10000
  range 1218.1
  sentinel 937.258
  mine 672.227
  ratio 1.29964
(ratio is range/sentinel, not mine/whatever)

You can get even more crazy with SIMD. But for all that you need to know the length beforehand.

Edit: The b4 variable should actually be called b8. That's a remnant of a previous version, where I used 32-bit chunks.

Re:C’s Biggest Mistake by throwawaymaths on Monday July 03, 2023 @01:24PM (#36576135)
Read the blog post. Dan lemire isn't exactly a slouch.
Re:C’s Biggest Mistake by yakubin on Monday July 03, 2023 @01:33PM (#36576286)
I read it. I don't see your point. Sentinel values simply give you a very low performance ceiling that you can't optimise past. What I wrote only took me a couple minutes. It's far from optimal (but it already takes 2/3 the time the sentinel version takes, and 1/2 the time Lemire's range version takes). With thorough effort I bet you could get at least 10 times faster than that, provided you are given the length. With sentinels, you're just left with the original performance levels you can't improve.
Re:C’s Biggest Mistake by kevin_thibedeau on Sunday July 02, 2023 @09:59PM (#36567814)
You can modify the length of NUL strings in place by inserting a new NUL or overwriting past the end without any other bookkeeping. You can split a string on delimiters simply by overwriting them with NULs.
Re:C’s Biggest Mistake by jrpelkonen on Sunday July 02, 2023 @10:31PM (#36568023)
I find these arguments rather weak. I don’t see how writing a NUL is any more efficient compared to updating a length. Furthermore, having the terminators in-band prevent the character data to be used for multiple substrings. E.g. in the split example the original string is no longer available.
Re:C’s Biggest Mistake by slaymaker1907 on Sunday July 02, 2023 @09:59PM (#36567815)
It takes 4-8 bytes to represent the size of the string versus 1 byte for a null terminator. That doubles the size of the string when you embed it in a struct or pass it as an argument on the stack. In particular, remember that even today cache lines are only 64 bytes for x86-64 and while that seems like a lot, going from 64 bytes to 68 means you go from 1 cache miss to load some struct to 2 cache misses.
Re:C’s Biggest Mistake by yakubin on Monday July 03, 2023 @04:09AM (#36570163)
Same as going from 64 to 65.
Re:C’s Biggest Mistake by throwawaymaths on Sunday July 02, 2023 @11:16PM (#36568339)
> Can't think of a single case where null terminated strings are more efficient

https://lemire.me/blog/2020/09/03/sentinels-can-be-faster/?a...

Re:C’s Biggest Mistake by 2h on Sunday July 02, 2023 @11:35PM (#36568442)
this ignores the fact that strings can contain a null character. for example, this is a valid Go program:

    package main
    
    import "fmt"
    
    func main() {
       fmt.Printf("%q\n", "hello \x00 world")
    }
Re:C’s Biggest Mistake by throwawaymaths on Sunday July 02, 2023 @11:43PM (#36568499)
I'm not sure what your point is. We're talking about c null terminated strings, not go.