[Bug c++/42743] Inexplicable error message with constructing SIMD values

[pinskia at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42743

Andrew Pinski  changed:

   What|Removed |Added

   Target Milestone|--- |4.7.0
   Keywords||rejects-valid
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Andrew Pinski  ---
Been fixed since GCC 4.7.0.

[Bug c++/42743] Inexplicable error message with constructing SIMD values

[paolo.carlini at oracle dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42743

Paolo Carlini paolo.carlini at oracle dot com changed:

   What|Removed |Added

 CC||jsm28 at gcc dot gnu.org

--- Comment #2 from Paolo Carlini paolo.carlini at oracle dot com 2011-10-15 
21:26:19 UTC ---
The first part of this I also noticed some time ago (and mentioned in another
PR): roughly speaking, __m128 doesn't seem default-constructible. Is there
something we can do about that? Seems rather weird, naively.

[Bug c++/42743] Inexplicable error message with constructing SIMD values

[jwakely dot gcc at gmail dot com]

--- Comment #1 from jwakely dot gcc at gmail dot com  2010-01-14 12:36 
---
(In reply to comment #0)

 vec_t tmp2 = {};  // Causes warnings about uninitialized members in
 myvec

The warning doesn't smean it's uninitialized, just that there are not
initializers present for all members:

   -Wmissing-field-initializers
   Warn if a structure's initializer has some fields missing.  For
example, the following code would cause such a warning, because x.h is
implicitly
   zero:

   struct s { int f, g, h; };
   struct s x = { 3, 4 };

You can disable that with -Wno-missing-field-initializers (but that doesn't
help for cases where vec_t cannot be aggregate initialized)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42743