Increased binary size with statically-linked libomp.a

I reported increased binary statically-linked libomp.a (vs. gcc + libgomp) at Can you all share your thoughts on the issue - in particular, if the runtime can be better organized for static linking.


Binary size is one of the best arguments for dynamic linking.


Is it now easy to build a static library in trunk?