Are hardcoded conditions optimized by JVM in Android?

Question

Due to debugging reason most parts of the code in my application has this recurrent portion of code:

public static final boolean DEBUG = true; // just created once in a "Utility" class if (Utility.DEBUG) Log.d("TIMER", /*string message that is strictly related to context*/);

Now, if the boolean values turn to false this becomes dead code. My question is if in this case the Android compiler would do basics optimizations such as constant folding and dead code remotion?

If the answer is no, what is the best way to whip out in release phase the debugging logs?

If Utility.DEBUGis a constant as indicated by your code, the dead code should already be removed by the java compiler. — MrSmith42
– MrSmith42, Commented Feb 15, 2018 at 14:57

Elliott Frisch · Accepted Answer · 2018-02-15 14:59:28Z

5

Yes; in the case of static final fields the compiler can and will remove the unreachable section. If you examine the byte-code you can validate this yourself.

answered Feb 15, 2018 at 14:59

Elliott Frisch

202k20 gold badges166 silver badges265 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Ralf Kleberhoff Over a year ago

To make that point clear: It's not the JVM, it's the Java compiler eliminating the dead code, before any Android-specific software comes into play.

Collectives™ on Stack Overflow

Are hardcoded conditions optimized by JVM in Android?

1 Answer 1

1 Comment

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Related