This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/66007] [5/6 Regression] Narrowing conversion inside { } results in all zero elements in C++11 mode with -Wno-error=narrowing
- From: "paolo.carlini at oracle dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 04 May 2015 17:09:58 +0000
- Subject: [Bug c++/66007] [5/6 Regression] Narrowing conversion inside { } results in all zero elements in C++11 mode with -Wno-error=narrowing
- Auto-submitted: auto-generated
- References: <bug-66007-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66007
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|paolo.carlini at oracle dot com |jason at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |paolo.carlini at oracle dot com
--- Comment #10 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Right Jakub. To my taste, fiddling directly with those counters isn't that
nice, but I know we do it in a few other places. In any case this code is
rather hackish anyway, we try to do something we don't do anywhere else,
effectively suppressing an hard error via -Wno-*. Also, as I already said, I
was thinking that normally elsewhere in the code, we do not handle pedwarns as
errors, we don't consider that -pedantic-errors may be in effect (in the
pedwarn right before too). What can I say, maybe we can ask Jason, which
solution he prefers in principle? In the meanwhile I do some testing.