https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
--- Comment #6 from Jakub Jelinek ---
Author: jakub
Date: Wed Sep 21 15:13:46 2016
New Revision: 240317
URL: https://gcc.gnu.org/viewcvs?rev=240317&root=gcc&view=rev
Log:
PR c++/77651
c-family/
* c.opt (Waligned-new=): Add Reject
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
Richard Biener changed:
What|Removed |Added
Version|unknown |7.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
--- Comment #4 from Guille ---
For what it's worth, any call to 'c++ -Waligned-new=none ...' will also ICE.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
--- Comment #3 from Guille ---
Excuses, I take that back.
I use placement new on a properly aligned piece of memory, gcc complains
(warning) that:
* 'note: uses ‘void* operator new(std::size_t, void*)’, which does not have an
alignment paramet
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
--- Comment #2 from Guille ---
Correction: There is no issue with '-faligned-new', only with
'-Wno-aligned-new'.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77651
Markus Trippelsdorf changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
