re: NetBSD/vax 11.0RC1
matthew green <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.vax |
|---|---|
| Message-ID | <[email protected]> |
> don't use -pipe ah... unfortunately, this is a thing i turned on on my build machine, it isn't used my default -- my vax is cc1plus'ing to a temp.s file. .. and my netbsd-11 256mb simh completed gimple-match.cc, and has moved onto generic-match.cc. i know vax uses less memory than amd64 but i think that we now can guess that gcc12's gimple-match.cc takes a bit over 400mb to compile, not the >900mb i saw on amd64. i have also been running "vmstat 10" in a window, and the two reports either side of that cc1plus exiting are: procs memory page disks faults cpu r b avm fre flt re pi po fr sr r0 r2 in sy cs us sy id 1 0 485004 4324 13 0 1 11 17 17 1 1 105 49 15 95 5 0 3 0 79144 170812 15 0 4 0 0 0 3 2 110 56 16 66 34 0 other evidence is Ken's reports with 512mb and hangs happening with ~50MB of free ram, but that's less clear. note that "avm" above includes active ram *and* swap.. so, it seems like the hang-bug we're seeing is not 100% always reproducible :-) but maybe 90+% .. BTW, i commited a fix to vax ddb backtrace that i tripped up on a couple of times, and plan to get it into -11. .mrg.