Searched refs:garbage (Results 1 – 12 of 12) sorted by relevance
251 volatile int garbage[ECACHE_PAGE_BYTE_MAX - sizeof (page_t)]; in prefetch_page_w() local273 volatile int garbage[ECACHE_PAGE_BYTE_MAX - sizeof (page_t)]; in prefetch_page_r() local
81 volatile int garbage[ECACHE_PAGE_BYTE_MAX - sizeof (page_t)]; in prefetch_page_w() local103 volatile int garbage[ECACHE_PAGE_BYTE_MAX - sizeof (page_t)]; in prefetch_page_r() local
136 void garbage(char *s);
2129 garbage("salloc"); in salloc()2151 garbage("morehd"); in morehd()2181 garbage("copy"); in copy()2232 garbage("seekc"); in seekc()2274 garbage("more"); in more()2297 garbage(char *s) in garbage() function
172 27.*when tmp file becomes too big, line of garbage no longer added to568 A bug that caused garbage to be in the buffer if the temp file1000 A bug that caused garbage to be in the buffer if the temp file
427 # Need cleanup here to avoid garbage dir left.
4320 is to be ignored, and therefore some BIOSs leave garbage values in the 12523 Fixed a problem in AcpiTbGetTablePtr() where a garbage pointer12883 text concerning reference count object management versus garbage14255 contained some garbage data caused by an internal buffer overrun.
9491 garbage
9489 garbage
4102 # 256 colors "works", but when running xterm's test-scripts, some garbage is8088 # but garbage may be left on the screen when you switch from12337 # The sb3 puts garbage on the bottom of the screen when you scroll with12521 # to work ok. There is one problem though if one types a lot of garbage
4695 # 256 colors "works", but when running xterm's test-scripts, some garbage is9049 # but garbage may be left on the screen when you switch from13906 # The sb3 puts garbage on the bottom of the screen when you scroll with14104 # to work ok. There is one problem though if one types a lot of garbage
2858 DRP, because the BIOS of Thinkpad X20 write a garbage beyond the