Lines Matching full:obstack
1728 on an obstack, and all the psymbols themselves are allocated in a pair
1729 of large arrays on an obstack, so there is little to be gained by
1933 Because this data lives on the objfile's obstack, it is automatically
4377 the input options parser `getopt', the `obstack' extension, and other
4383 The obstack mechanism provides a convenient way to allocate and free
4384 chunks of memory. Each obstack is a pool of memory that is managed
4386 allocated and freed in a LIFO fashion on an obstack (see `libiberty''s
4390 There is an obstack associated with each internal representation of an
4408 free only a top portion of the obstack. There are a few instances in
4410 some local data is allocated to the obstack. Only the local data is
4411 deleted from the obstack. Of course this assumes that nothing between
4413 the same obstack. For this reason it is best and safest to use
4416 Releasing the whole obstack is also not safe per se. It is safe only
4722 per-architecture data-pointer using the architecture's obstack
4766 nozel_pre_init (struct obstack *obstack)
4768 struct nozel *data = OBSTACK_ZALLOC (obstack, struct nozel);
