Comment # 4
on bug 93687
from Francisco Jerez
(In reply to Timothy Pearson from comment #3) > Since this is marked NOTOURBUG, is there somewhere I should be submitting a > bug report to get this fixed? I'd really like to see OpenCL on the > OpenPOWER hardware without having to manually patch / build, and without > having to get a downstream patch into Debian / RHEL. > > Thanks! Either GCC or Khronos -- I'd be inclined to blame GCC for this, since the altivec.h header is unusable from standard C++ code (assuming you don't hack around it by undef'ing "vector" and "bool" after inclusion or by preventing it from defining them in the first place somehow), however last time somebody reported this [1] the bug was closed as invalid, so apparently some people from the GCC community think that this is the (unfortunate) expected behaviour -- Assuming they're right, cl_platform.h should stop including altivec.h (or hack around it somehow) because it makes cl.h unusable from standard C++ code on PPC platforms. [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58241
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel