Re:Inter-Procedural Optimization and Derefinement
by dkarapetyan on Sunday July 17, 2016 @06:04PM
(#12112090)
I don't understand the example
Shouldn't it be optimized to
instead of
[ Parent
| on HN ]
Re:Inter-Procedural Optimization and Derefinement
by legulere on Sunday July 17, 2016 @08:32PM
(#12112609)
int unused = 1 / 0;
is undefined behaviour. The compiler can replace it with anything it wants. Like for instance a return true. Compilers usually (ab-)use this to remove branches.
Re:Inter-Procedural Optimization and Derefinement
by adrianratnapala on Monday July 18, 2016 @12:30AM
(#12113225)
No need to for parentheses around "ab" in abuse. This is just bad behaviour from compilers trying to optimise for benchmarks.
The right thing to do is to issue an error or warning, and then not make absurd assumptions about other variables. A good explanation of all this can be found here: http://c9x.me/compile/bib/ubc.pdf
Re:Inter-Procedural Optimization and Derefinement
by legulere on Monday July 18, 2016 @06:01AM
(#12114121)
I guess the problem with issuing warnings is that dead code can also contain undefined behaviour, so the compiler would probably produce lots of false positives.
Re:Inter-Procedural Optimization and Derefinement
by nikic on Sunday July 17, 2016 @06:09PM
(#12112105)
Division by zero is undefined behavior, so the compiler is free to assume that the b==false branch is unreachable.
Re:Inter-Procedural Optimization and Derefinement
by choosername on Sunday July 17, 2016 @07:22PM
(#12112399)
It would also be reasonable to remove the declaration as the variable is "unused".
Re:Inter-Procedural Optimization and Derefinement
by dkarapetyan on Sunday July 17, 2016 @06:13PM
(#12112120)
I see.