https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Target Milest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
--- Comment #5 from Martin Sebor ---
I don't consider this a regression. The warnings are justified and it wasn't a
design goal to let casts suppress them. I agree it would be useful for
compatibility with Clang (that's why I raised the bug), b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
--- Comment #6 from Ville Voutilainen ---
As stated in the other comments, this breaks *users* of existing Qt versions.
Any fix would apply to newer versions only. QVector bit-blasts an object of a
type with a virtual table over an object of that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
--- Comment #8 from Ville Voutilainen ---
I can confirm that this fixes the woes in building and using Qt as far as
QVector is concerned. Now that we have this fix, I see that there are other
bit-blasts that don't use casts. Would it be possible
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
--- Comment #9 from Jakub Jelinek ---
Author: jakub
Date: Wed Jan 10 16:59:09 2018
New Revision: 256440
URL: https://gcc.gnu.org/viewcvs?rev=256440&root=gcc&view=rev
Log:
PR c++/81327
* call.c (maybe_warn_class_memaccess): Add fo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
--- Comment #11 from Ville Voutilainen ---
The issue is again that users of existing Qt versions will see the warnings,
and they also turn to errors. I can fix the non-casting uses, but I would
recommend removing this warning from -Wall as well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
--- Comment #12 from Jakub Jelinek ---
Every GCC release comes with a http://gcc.gnu.org/gcc-7/porting_to.html
(similarly for other releases and we'll have one for gcc-8 too), and especially
with -Werror people need to adjust their codes not just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
--- Comment #13 from Ville Voutilainen ---
I understand that, but considering that I plan to convince the committee that
the bit-blasts like Qt does should be well-defined, the warning is a bit eager,
cast or no cast. And since it does break exis
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
Jakub Jelinek changed:
What|Removed |Added
CC||jason at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
--- Comment #15 from Ville Voutilainen ---
I would like to have the change be a DR. Anyway, I looked at the cast-less
cases, they are in qtransform.h, which is included by at least QImage and
QtGui, so there will be a fair amount of code that wil
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
--- Comment #16 from Martin Sebor ---
The GCC warning detects several distinct kinds of undefined behavior, most of
which cannot very well be made well-defined. Making changes to the checker
just because a subset of the undefined cases are viewe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327
--- Comment #17 from Martin Sebor ---
Author: msebor
Date: Sun Jan 14 21:54:25 2018
New Revision: 256677
URL: https://gcc.gnu.org/viewcvs?rev=256677&root=gcc&view=rev
Log:
PR c++/81327 - cast to void* does not suppress -Wclass-memaccess
gcc/Cha
15 matches
Mail list logo
