diff options
| author | ian <ian@138bc75d-0d04-0410-961f-82ee72b054a4> | 2014-04-25 04:28:48 +0000 |
|---|---|---|
| committer | ian <ian@138bc75d-0d04-0410-961f-82ee72b054a4> | 2014-04-25 04:28:48 +0000 |
| commit | 0102c4b77f669b203fc196114a02226c5f93f96e (patch) | |
| tree | 2d74bb623091af0ae7f23a44fd44fff2edcb0c2d /libjava/classpath/gnu/java/security/util/FormatUtil.java | |
| parent | d124bef37aa1891f556e93a77411f0136c526439 (diff) | |
| download | ppe42-gcc-0102c4b77f669b203fc196114a02226c5f93f96e.tar.gz ppe42-gcc-0102c4b77f669b203fc196114a02226c5f93f96e.zip | |
PR go/60931
runtime: Fix garbage collector issue with non 4kB system page size
The go garbage collector tracks memory in terms of 4kB pages.
Most of the code checks getpagesize() at runtime and does the
right thing.
On a 64kB ppc64 box I see SEGVs in long running processes
which has been diagnosed as a bug in scavengelist.
scavengelist does a madvise(MADV_DONTNEED) without rounding
the arguments to the system page size. A strace of one of the
failures shows the problem:
madvise(0xc211030000, 4096, MADV_DONTNEED) = 0
The kernel rounds the length up to 64kB and we mark 60kB of
valid data as no longer needed.
Round start up to a system page and end down before calling
madvise.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/gcc-4_9-branch@209776 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'libjava/classpath/gnu/java/security/util/FormatUtil.java')
0 files changed, 0 insertions, 0 deletions
