This bugzilla service is closed. All entries have been migrated to

Bug 1221

Summary: I get tons of error since my distribution upgraded to GCC 6.1.1
Product: Eigen Reporter: Alessio Elmi <alessio_elmi>
Component: GeneralAssignee: Nobody <eigen.nobody>
Severity: Compilation Problem CC: chtz, gael.guennebaud, jacob.benoit.1
Priority: Normal    
Version: 3.3 (current stable)   
Hardware: All   
OS: All   
Bug Depends on:    
Bug Blocks: 814    
Description Flags
Disable -Wignored-attributes none

Description Alessio Elmi 2016-05-10 00:00:02 UTC
What I experience is that my little program stopped building since the upgrade of gcc to 6.1.1 (now the standard with Archlinux).
I get a lot of "-Wignored-attributes", which turn into breaking the compiling process. However,  turning off any warning "-w" lets me go further, even though I am not sure if it is totally safe.
I also tried latest git sources, with the same results.
The culprit line which always occurs is the following:
/usr/include/eigen3/Eigen/src/Core/DenseCoeffsBase.h:56:30: warning: ignoring attributes on template argument 'Eigen::internal::packet_traits<double>::type {aka __vector(2) double}' [-Wignored-attributes]
Comment 1 Christoph Hertzberg 2016-05-11 07:18:39 UTC
If I see it correctly, these are "only" warnings? Still they must be fixed, but perhaps it is sufficient to fix them for 3.3
I assume they essentially warn for the issue fixed here:

I locally made a fix based on meta-packets (see Bug 692 Comment 10), which appeared to work. I unfortunately seem to have lost it while messing with mercurial ... but it weren't too many changes and I can make a more clean re-implementation -- be a bit patient, though.
Comment 2 Gael Guennebaud 2016-05-18 13:51:04 UTC
Created attachment 708 [details]
Disable -Wignored-attributes

What about simply disabling this warning within Eigen as in the attached patch?
Comment 3 Gael Guennebaud 2016-05-19 13:24:43 UTC
I applied the attached changes to make gcc 6 usable: (3.2)

good enough for 3.3 (IMO)
Comment 4 Gael Guennebaud 2019-01-16 15:43:26 UTC
I consider it as fixed as there is no other solution than disabling the warning (as currently done) or encapsulating the __mXXX type in a struct, but we won't do that only for a stupid warning (there might be other good reasons though).
Comment 5 Nobody 2019-12-04 15:47:45 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: