[Bug c++/77742] Warning about placement new for over-aligned type

2016-11-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77742

Jonathan Wakely  changed:

   What|Removed |Added

 CC||marc.mutz at kdab dot com

--- Comment #4 from Jonathan Wakely  ---
*** Bug 78434 has been marked as a duplicate of this bug. ***

[Bug c++/77742] Warning about placement new for over-aligned type

2016-10-12 Thread jason at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77742

Jason Merrill  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED
   Assignee|unassigned at gcc dot gnu.org  |jason at gcc dot gnu.org
   Target Milestone|--- |7.0

--- Comment #3 from Jason Merrill  ---
Fixed.

[Bug c++/77742] Warning about placement new for over-aligned type

2016-10-12 Thread jason at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77742

--- Comment #2 from Jason Merrill  ---
Author: jason
Date: Wed Oct 12 18:04:51 2016
New Revision: 241073

URL: https://gcc.gnu.org/viewcvs?rev=241073&root=gcc&view=rev
Log:
PR c++/77742 - -Waligned-new and placement new.
* init.c (build_new_1): Don't -Waligned-new about placement new.
(malloc_alignment): New.  Consider MALLOC_ABI_ALIGNMENT.
* decl.c (cxx_init_decl_processing): New.

Added:
trunk/gcc/testsuite/g++.dg/cpp1z/aligned-new7.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/decl.c
trunk/gcc/cp/init.c

[Bug c++/77742] Warning about placement new for over-aligned type

2016-09-27 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77742

Jonathan Wakely  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2016-09-27
 Blocks||65122
 Ever confirmed|0   |1


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65122
[Bug 65122] std::vector doesn't honor element alignment

[Bug c++/77742] Warning about placement new for over-aligned type

2016-09-26 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77742

--- Comment #1 from Richard Biener  ---
As placement new has no control over the memory alignment the warning looks
useless to me.  In this particular case we even know statically the memory is
well-aligned.