WM_NCOMPPROCS and full optimization

From OpenFOAMWiki

Hi Bruno!

Don't want to add noise to your tip about WM_NCOMPPROCS=4 for compilation. But that may be problematic for some people: certain compilers (for instance CLang) use HUGE amounts of memory when doing full optimiziation. The files generated by the grammars are very large and the problem is that three grammars from the base library get compiled at approximately the same time. I've seen cases where this forces machines with medium amount of memory (8Gig to be precise) into swapping and making them almost non-responsive. So I don't endorse this tip. I'd rather have people go "took me long to compile" than "compilation frooze my machine" (and I think I remember at least one such instance on the MessageBoard)


Bgschaid (talk)14:21, 5 October 2013

Hi Bernhard,

Mmm... and I thought that .NET was annoying enough... I've never used CLang myself, so I had no idea it could be such a memory hog :(

Then how about an if and only if indication that one can only use this option if using GCC or ICC? Something like:

If you are using a GCC or ICC compiler, then before running one of the commands above, you can run this command:

... and so on.

Best regards, Bruno

Wyldckat (talk)01:01, 6 October 2013

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.
  • Your username or IP address has been blocked. The block was made by DNSBL. The reason given is Your IP address is listed as an open proxy in the DNSBL used by OpenFOAMWiki..
    • Start of block: 10:16, 25 September 2020
    • Expiry of block: 10:16, 25 September 2020
    • Intended blockee:
    You can contact DNSBL or another administrator to discuss the block. You cannot use the "email this user" feature unless a valid email address is specified in your account preferences and you have not been blocked from using it. Your current IP address is, and the block ID is #. Please include all above details in any queries you make.

You can view and copy the source of this page:

Return to Thread:Talk:Contrib/swak4Foam/WM NCOMPPROCS and full optimization/reply (2).

Nice! I already knew that CLang provides a better warning/error messages, as well as helping find some issues without the need of some other lint software, but I had no idea that it tried to optimize the output from bison et al!

OK, I'll update the note with this in mind.

Wyldckat (talk)13:41, 6 October 2013

The problem is that optimizing the parser for swak is futile: the time spent doing the actual parsing is small compard to the actual "OF-work": calculations on the fields. That's why I added the special optimiziation switch for the parsers.

PS: and this "tries to optimize goto-stained code" is only a theory (I haven't looked at the source. But its behaviour - certain CLang versions freeze a 8 Gig machine when compiling FieldParser with O3 - make me pretty sure that this is the case)

Bgschaid (talk)14:11, 6 October 2013