Closed coppolachan closed 7 years ago
Updating Eigen would be best, clearly. As you know I hate warning suppression and would rather just have legal code, even though this is strictly a deprecated warning and GCC is being a bit naughty (in the sense that verbose warning on constructs still supported but planned for deprecation is a pain in the ass pedant thing to do).
I agree, especially that Eigen has been going through several versions since. New versions does support AVX512. In principle just the URL in the Eigen script should be changed.
On 9 May 2017, at 12:03, Peter Boyle notifications@github.com wrote:
Updating Eigen would be best, clearly. As you know I hate warning suppression and would rather just have legal code, even though this is strictly a deprecated warning and GCC is being a bit naughty (in the sense that verbose warning on constructs still supported but planned for deprecation is a pain in the ass pedant thing to do).
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
updated to 3.3.3
is the problem solved with the update?
Was on my laptop; I'm waiting for travis to verify and close.
Compiled clean closing.
GCC throws a lot of the following harmless warnings, coming from the Eigen lib
should we suppress them or look for a newer version of the Eigen that solves this?