Re:What Every C Programmer Should Know About Undefined Behav...
by calrogman on Tuesday January 13, 2015 @10:43AM
(#8880482)
In that case the machine code generated doesn't dereference NULL, so the answer "it segfaults" isn't wrong.
Re:What Every C Programmer Should Know About Undefined Behav...
by heinrich5991 on Tuesday January 13, 2015 @11:28AM
(#8880788)
In the C code, a null pointer is dereferenced. A segfault is not happening in the executable. Arguing about intermediate steps is kinda moot IMO.
Re:What Every C Programmer Should Know About Undefined Behav...
by mikeash on Tuesday January 13, 2015 @11:46AM
(#8880911)
The very concept of dereferencing doesn't exist at that level.
Re:What Every C Programmer Should Know About Undefined Behav...
by mikeash on Wednesday January 14, 2015 @10:53AM
(#8886974)
I'll take the downvote as a request for elaboration. In C, you dereference a pointer. This typically translates to machine code that loads memory at an address. The translation is so direct that we tend to think of them as identical, i.e. dereferencing a pointer is loading memory at an address. But this is not so; first of all, nothing says pointers have to be implemented as memory addresses in the first place, and even if you do implement them that way (as virtually every C implementation does), not every pointer dereference has to generate a load instruction. That's not just the case for optimizing out NULL dereferences. Optimizations mean that in general, an expression p can have the memory load optimized away if the value at that location is already known from a previous computation (say, because you just assigned a value there, or you read the value a bit earlier and it's still available in a register).
In C, you deference a pointer. In assembly or machine code, you load memory at an address. The two don't have to happen at the same time, though, and just because you don't end up loading memory at an address doesn't mean you didn't dereference a pointer.
In short:
*(char *)NULL
This always dereferences NULL, even if the compiler optimizes out the statement entirely.
Edit: some NULL dereferences.