Lines Matching full:obstack
2031 on an obstack, and all the psymbols themselves are allocated in a pair
2032 of large arrays on an obstack, so there is little to be gained by
2254 Because this data lives on the objfile's obstack, it is automatically
5017 the input options parser `getopt', the `obstack' extension, and other
5023 The obstack mechanism provides a convenient way to allocate and free
5024 chunks of memory. Each obstack is a pool of memory that is managed
5026 allocated and freed in a LIFO fashion on an obstack (see `libiberty''s
5030 There is an obstack associated with each internal representation of an
5048 free only a top portion of the obstack. There are a few instances in
5050 some local data is allocated to the obstack. Only the local data is
5051 deleted from the obstack. Of course this assumes that nothing between
5053 the same obstack. For this reason it is best and safest to use
5056 Releasing the whole obstack is also not safe per se. It is safe only
5583 per-architecture data-pointer using the architecture's obstack
5628 nozel_pre_init (struct obstack *obstack)
5630 struct nozel *data = OBSTACK_ZALLOC (obstack, struct nozel);
