EoM’s code path functionality

The new renderer code has support for multiple, dynamic code paths. It works by selecting the optimal render technique at runtime, and then using a vtable to call those functions.


  • Less conditionals to handle corner-cases
  • Better instruction cache performance
  • Better compiler optimization


  • Impossible to inline vtable (this can be worked around by reducing vtable calls by using wrapper functions)
  • Messier/obfuscated code (and stupid c++ syntax makes it near impossible to do code paths for template classes)
  • Larger executable size (in theory, although it really is the same instructions, just executed in different order)
This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s