This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
How to migrate ggc_alloc_XXX for GCC v8.x (git-20170816)?
- From: Leslie Zhai <lesliezhai at llvm dot org dot cn>
- To: tbsaunde at tbsaunde dot org
- Cc: dmalcolm at redhat dot com, GCC Development <gcc at gcc dot gnu dot org>
- Date: Wed, 16 Aug 2017 17:32:10 +0800
- Subject: How to migrate ggc_alloc_XXX for GCC v8.x (git-20170816)?
- Authentication-results: sourceware.org; auth=none
- Feedback-id: bizesmtp:llvm.org.cn:qybgforeign:qybgforeign1
Hi GCC developers,
GCC v4.6's gengtype will auto-generate Allocators for known structs and
unions, for example: ggc_alloc_tree2WeakVH for tree2WeakVH
https://github.com/xiangzhai/dragonegg/blob/master/include/dragonegg/gt-cache-4.6.inc#L24
but gengtype will not auto-generate ggc_alloc_XXX for GCC v6.x or v8.x
(git-20170816), for example: struct GTY((for_user)) tree2WeakVH
https://github.com/xiangzhai/dragonegg/blob/master/include/dragonegg/gt-cache-8.0.inc#L1284
As ChangeLog-2014 mentioned:
2014-05-17 Trevor Saunders <tsaunders@mozilla.com>
...
(ggc_alloc): Install the type's destructor as the finalizer if it
might do something.
Please give me some hint about ggc_alloc migration, thanks a lot!
--
Regards,
Leslie Zhai - a LLVM developer https://reviews.llvm.org/p/xiangzhai/