This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [GSoC] Question about the implementation of vec.h
- From: Diego Novillo <dnovillo at google dot com>
- To: Roman Gareev <gareevroman at gmail dot com>
- Cc: gcc <gcc at gcc dot gnu dot org>, Tobias Grosser <tobias at grosser dot es>, Mircea Namolaru <mircea dot namolaru at inria dot fr>
- Date: Mon, 21 Jul 2014 09:11:08 -0400
- Subject: Re: [GSoC] Question about the implementation of vec.h
- Authentication-results: sourceware.org; auth=none
- References: <CABGF_gdF+aoh9svftNGBin2+30KV4Oifh60ZxatgRfran7S=EQ at mail dot gmail dot com>
On Mon, Jul 21, 2014 at 5:22 AM, Roman Gareev <gareevroman@gmail.com> wrote:
> Dear gcc contributors,
>
> could you please answer a few questions about the implementation of
> vec.h? Should we always use âcreateâ to initialize, for example,
> vec<tree_node*> or is it possible to do it using âsafe_grow_clearedâ
> or a similar function? There is "vec_safe_grow_cleared", which works
> with vec<T, A, vl_embed>. Is there a way to use it with
> vec<tree_node*>?
Yes, you need to use .create() to initialize vec instances.
Diego.