This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PATCH RFC: Implement and use VEC(T,stack)

From: Ian Lance Taylor <iant at google dot com>
From: Ian Lance Taylor <ian at airs dot com>
To: Alexandre Oliva <aoliva at redhat dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Wed, 10 Jun 2009 06:06:36 -0700
Subject: Re: PATCH RFC: Implement and use VEC(T,stack)
References: <m3ab4gomh5.fsf@pepe.airs.com> <or4ouotz8o.fsf@free.oliva.athome.lsd.ic.unicamp.br>

Alexandre Oliva <aoliva@redhat.com> writes:

> I wonder if it would make sense to introduce an attribute with a cleanup
> that could be used to verify or even automate (GCC-only) the release of
> the vector in case it gets reallocated.  Considering that it is supposed
> to most often not be reallocated into the heap, this would probably work
> well even in stage1, when the attribute may be unavailable.  This would
> help catch (at run time) mistakes such as returning the alloca()ed
> array.

We do already have the cleanup attribute for types.  I'm agnostic as
to whether we want to start using it in the gcc sources.

Ian

References:
- PATCH RFC: Implement and use VEC(T,stack)
  - From: Ian Lance Taylor
- Re: PATCH RFC: Implement and use VEC(T,stack)
  - From: Alexandre Oliva

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]