blaze-lib / blaze / issues / #315 - Name conflict with preprocessor macro — Bitbucket

Issue #315 resolved

Hartmut Kaiser created an issue 2020-01-20

We are running into an issue on Power9 systems, where the symbol VT1 (possibly others) are defined as a macro. This causes compilation of code that includes certain Blaze headers to fails as this symbol is used all over the place as a template argument name. Please see https://github.com/STEllAR-GROUP/phylanx/issues/1088 for details.

Comments (5)

Klaus Iglberger
- assigned issue to
  
  Klaus Iglberger
- 2020-01-25T10:36:43+00:00
Klaus Iglberger
- changed status to open
- 2020-01-25T10:36:52+00:00
Hartmut Kaiser reporter
FWIW, we have decided to fix our particular issue by adding #undef directives to HPX. This appeared to be the least intrusive fix. Please see here for more details: https://github.com/STEllAR-GROUP/hpx/pull/4322. Thanks!
- 2020-01-25T13:45:38+00:00
Klaus Iglberger
- changed status to resolved
Commit 7850cb4 prevents all naming conflicts with the preprocessor symbols VT1 and VT2. The fix is immediately available via cloning the Blaze repository and will be officially released in Blaze 3.7.
- 2020-01-25T16:16:45+00:00
Hartmut Kaiser reporter
Thanks Klaus! Much appreciated.
- 2020-01-25T16:17:46+00:00
Log in to comment

Assignee: Klaus Iglberger

Type: bug

Priority: major

Status: resolved

Votes: 0

Watchers: 1

Jira: the preferred issue tracker for Bitbucket. Join the team!