Skip to content

ObjexxFCL Update for Visual C++ 2015 and Intel C++ 2016 Compatibility#5204

Merged
Myoldmopar merged 2 commits intodevelopfrom
ObjexxFCL_Update
Sep 17, 2015
Merged

ObjexxFCL Update for Visual C++ 2015 and Intel C++ 2016 Compatibility#5204
Myoldmopar merged 2 commits intodevelopfrom
ObjexxFCL_Update

Conversation

@DeadParrot
Copy link
Contributor

This adds support for these two new Windows compiler releases. In my quick testing so far, with these changes those compilers seem to work for EnergyPlus. Merging this for the upcoming 8.4 release depends on whether we expect users who do their own builds from release sources will want to use these compilers before the following release.

Visual C++ 2015:

  • Format of INF floating point values changed requiring an adjustment to a Print unit test

Intel C++ 2016 (Windows):

  • Bug (reported) with static std::locale objects and stream imbue calls worked-around in ObjexxFCL::fmt
  • Disabled warning 809 to suppress bogus messages about exception specs for virtual destructors (Intel knows about this and will fix it)

General:

  • Dropped the Array::to_default() methods (not used in EnergyPlus) to eliminate issue with builtin type members that aren't initialized in the default constructor (sanitizers would complain about the assignment of an uninitialized value)

CMake:

  • A few minor tweaks/fixups in the sanitizer setup

@DeadParrot DeadParrot added the DoNotPublish Includes changes that shouldn't be reported in the changelog label Sep 15, 2015
Myoldmopar added a commit that referenced this pull request Sep 17, 2015
ObjexxFCL Update for Visual C++ 2015 and Intel C++ 2016 Compatibility
@Myoldmopar Myoldmopar merged commit 988cb91 into develop Sep 17, 2015
@Myoldmopar Myoldmopar deleted the ObjexxFCL_Update branch September 17, 2015 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

DoNotPublish Includes changes that shouldn't be reported in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants