Thread

1. adzm · 1789744548 · focus · HN ↗

   i have never before thought that a function could 'fall through' to another function. why does this behavior even exist?

   1. echoangle · 1789746042 · focus · HN ↗

      I'm also confused that an uncalled function is even compiled and linked, wouldn't it make sense to remove it entirely if the compiler can detect that it's never called?

      1. rcxdude · 1789746235 · focus · HN ↗

         If it's declared as static, maybe (well, usually, in my experience. You'll also usually get an unused warning). Otherwise the compiler can't assume some other compilation unit won't want it. Linkers can perform a garbage collection pass but they don't often do it by default and they often need finer grained information from the compiler (see the gcc arguments --ffunction-sections and -Wl,--gc-sections)

         1. lou1306 · 1789746758 · focus · HN ↗

            I can understand adding the 'unreachable' function to the object file, I can even understand plugging it into the final executable, what I (and most other people) object to is making it the de-facto entry point.

            This is literally the opposite behaviour compared to what is written in the source code, even when you "assume the infinite loop terminates".

            1. echoangle · 1789747077 · focus · HN ↗

               That's the problem with UB, once you hit it (or even have it in your code), you can't really trust anything about the execution anymore. That the function is called isn't something the compiler does on purpose, it's just that the main function is compiled empty due to the UB and the function directly behind it is executed because the CPU just keeps looking for the next instruction.

Unofficial Hacker News client; not affiliated with Y Combinator.