Bug 125025 – Finally remove those DFG_ENABLE things

• Status: RESOLVED
• Resolution: FIXED
• Component: JavaScriptCore

[Filip Pizlo]

Using C preprocessor macros to control the internal debugging functionality of a compiler is insane.  It means that the debug support isn't tested all the time, it isn't even built all the time, and it makes it challenging to read the code because of a bunch of #if's littered in the most complex places (after all it's the most complex algorithms that need debug prints).

We now have Options::verboseCompilation and friends, which doesn't suffer as many of those problems.

We should get rid of the old DFG_ENABLE preprocessor flags, because this will cleanse the codebase of the insanity and it will guide would-be DFG hackers towards the right way of getting debug dumps (i.e. the commandline options).

[Filip Pizlo]

Created attachment 218085 [details]
the patch

[Sam Weinig]

rs=me

[EFL EWS Bot]

Comment on attachment 218085 [details]
the patch

Attachment 218085 [details] did not pass efl-ews (efl):
Output: http://webkit-queues.appspot.com/results/39978148

[Build Bot]

Comment on attachment 218085 [details]
the patch

Attachment 218085 [details] did not pass mac-wk2-ews (mac-wk2):
Output: http://webkit-queues.appspot.com/results/39918130

[Filip Pizlo]

The build fails are because I forgot to give this release build love; the fixes are all trivial.

[Filip Pizlo]

Created attachment 218087 [details]
patch for landing

This one should work.

[Filip Pizlo]

Landed in http://trac.webkit.org/changeset/159886