summaryrefslogtreecommitdiff
path: root/open_issues/glibc_madvise_vs_static_linking.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues/glibc_madvise_vs_static_linking.mdwn')
-rw-r--r--open_issues/glibc_madvise_vs_static_linking.mdwn5
1 files changed, 3 insertions, 2 deletions
diff --git a/open_issues/glibc_madvise_vs_static_linking.mdwn b/open_issues/glibc_madvise_vs_static_linking.mdwn
index ab633b0f..4af41931 100644
--- a/open_issues/glibc_madvise_vs_static_linking.mdwn
+++ b/open_issues/glibc_madvise_vs_static_linking.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2010, 2011, 2012 Free Software Foundation,
+[[!meta copyright="Copyright © 2010, 2011, 2012, 2013 Free Software Foundation,
Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
@@ -29,7 +29,8 @@ no-op in glibc, avoiding the link-time warning.
GCC c5db973fdab3db3e13db575e5650c0bcfd3630f4 (2011-10-17) makes use of this.
As we now export the symbol (and `MADV_DONTNEED`, too), GCC will no longer
`munmap` pages, but will keep them mapped for later re-use. This may increase
-memory usage.
+memory usage. The discussion in [[!message-id
+"20120720162519.734e02eb@spoyarek"]] touches related topics.
2011-07: This is what Samuel has [done for Debian
glibc](http://anonscm.debian.org/viewvc/pkg-glibc/glibc-package/trunk/debian/patches/hurd-i386/local-madvise_warn.diff).