https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
Martin Sebor changed:
What|Removed |Added
Assignee|msebor at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
Florian Weimer changed:
What|Removed |Added
See Also||https://sourceware.org/bugz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
--- Comment #18 from Martin Sebor ---
The link works for me. An older version of the paper is here:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3396.htm
If that doesn't work for you either try searching for the paper titled Dynamic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
--- Comment #17 from Marios Hadjieleftheriou ---
(In reply to Martin Sebor from comment #12)
> Confirmed. As noted in bug 67911, the solution proposed for the next
> version of C++ is the following:
> http://www.open-std.org/jtc1/sc22/wg21/docs/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
Martin Sebor changed:
What|Removed |Added
CC||mhadji at gmail dot com
--- Comment #16 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
Martin Sebor changed:
What|Removed |Added
CC||b7.10110111 at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
Martin Sebor changed:
What|Removed |Added
CC||ilja.honkonen at helsinki dot
fi
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
H.J. Lu changed:
What|Removed |Added
CC||tkoenig at gcc dot gnu.org
--- Comment #13 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #11
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
H.J. Lu changed:
What|Removed |Added
CC||hayim at post dot tau.ac.il
--- Comment #10 fro
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
H.J. Lu changed:
What|Removed |Added
CC||sergey.v.maslov at intel
|
--- Comment #8 from hjl dot tools at gmail dot com 2010-04-24 02:42 ---
*** Bug 43874 has been marked as a duplicate of this bug. ***
--
hjl dot tools at gmail dot com changed:
What|Removed |Added
---
--- Comment #7 from hjl dot tools at gmail dot com 2009-01-09 01:09 ---
We can solve it with
1. A target should define MALLOC_ABI_ALIGNMENT properly.
2. g++ should issue an error when the default new operator
is used on a type whose alignment is greater than
MALLOC_ABI_ALIGNMENT.
3. It
--- Comment #6 from joseph at codesourcery dot com 2008-05-07 11:25 ---
Subject: Re: C++ compiler should issue a warning with missing
new operator
On Wed, 7 May 2008, pinskia at gcc dot gnu dot org wrote:
> aligned memory. PPC LV2 returns 16byte aligned memory. PPC Linux should be
--- Comment #5 from pinskia at gcc dot gnu dot org 2008-05-07 05:00 ---
(In reply to comment #4)
> The default new operator is implemented within gcc. It should be
> possible to let g++ know the alignment returned by the new operator.
The default one is but the user can override it as d
--- Comment #4 from hjl dot tools at gmail dot com 2008-05-07 04:56 ---
The default new operator is implemented within gcc. It should be
possible to let g++ know the alignment returned by the new operator.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36159
--- Comment #3 from bangerth at dealii dot org 2008-05-07 04:21 ---
How is the compiler supposed to know about what alignment malloc can
produce? How can it know that ::operator new doesn't increase the
alignment automatically?
W.
--
bangerth at dealii dot org changed:
W
--- Comment #2 from hjl dot tools at gmail dot com 2008-05-06 16:28 ---
Trevor, can you scale down your original proposal just to issue an
error when there is no class-specific operator new for a type with
an alignment greater than what malloc() guarantees? It will be
programmer's respon
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-05-06 16:11 ---
Actually we (Sony) have come up with a solution but not much as come about with
it though.
If you read Trevor's proposal, you would have found we did come up with one.
--
http://gcc.gnu.org/bugzilla/show_bug.cg
21 matches
Mail list logo