This is the mail archive of the 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: [trunk<-vta] Re: [vta, 4.4] make df-scan df_collection_rec arrays overflow-safe

On Wed, Jun 3, 2009 at 2:49 PM, Alexandre Oliva<> wrote:
> On Jun ?1, 2009, Ian Lance Taylor <> wrote:
>> I like the idea but (sorry) I would rather see this as a more general
>> data structure which can be used in other places. ?I don't like the ##
>> stuff you are using. ?Perhaps if you defined a new type of VEC:
>> VEC(TYPE, alloca).
> Make that a *big* sorry :-(
> I've been trying to figure out how to make that fit in the current VEC
> API, but I don't see a pleasant way to introduce it.

This patch is the kind of thing I mean.  It has an ugly aspect but it
does the job (maybe somebody can suggest a way around the ugliness).
I've bootstrapped but haven't run the testsuite.  The numbers passed
to VEC_alloc are guesses.  They should be large enough to be
sufficient for most cases, but not so large as to waste stack memory.
I'd like to hear suggestions for what the values should be.


Attachment: foo.txt
Description: Text document

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