diff options
| author | Thomas Schwinge <thomas@schwinge.name> | 2012-03-17 12:33:45 +0100 |
|---|---|---|
| committer | Thomas Schwinge <thomas@schwinge.name> | 2012-03-17 12:33:45 +0100 |
| commit | 966b2bb2380a6b104b742bc7fe214e9fdf09921d (patch) | |
| tree | 8f3117209d6ffc6b78b391d80edc209800163263 /open_issues/glibc_madvise_vs_static_linking.mdwn | |
| parent | 98b9d2122329f35477594a6161dbbe3b26b59b63 (diff) | |
| parent | 3bf27c93ac4de57623809b71517116d51465f0e1 (diff) | |
| download | web-966b2bb2380a6b104b742bc7fe214e9fdf09921d.tar.gz web-966b2bb2380a6b104b742bc7fe214e9fdf09921d.tar.bz2 web-966b2bb2380a6b104b742bc7fe214e9fdf09921d.zip | |
Merge remote-tracking branch 'fp/master'
Conflicts:
open_issues/glibc_madvise_vs_static_linking.mdwn
Diffstat (limited to 'open_issues/glibc_madvise_vs_static_linking.mdwn')
| -rw-r--r-- | open_issues/glibc_madvise_vs_static_linking.mdwn | 18 |
1 files changed, 15 insertions, 3 deletions
diff --git a/open_issues/glibc_madvise_vs_static_linking.mdwn b/open_issues/glibc_madvise_vs_static_linking.mdwn index 43b8314f..1f766428 100644 --- a/open_issues/glibc_madvise_vs_static_linking.mdwn +++ b/open_issues/glibc_madvise_vs_static_linking.mdwn @@ -26,10 +26,22 @@ case of MADV_DONTNEED), but may influence its performance. The kernel is free to ignore the advice.* (`man madvise`), so we may simply want to turn it into a no-op in glibc, avoiding the link-time warning. -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). - 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. + +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). + + +# IRC, freenode, #hurd, 2012-02-16 + + <tschwinge> youpi: With Roland's fix the situation will be that just using + gcc -static doesn't emit the stub warning, but still will do so in case + that the source code itself links in madvise. Is this acceptable for + you/Debian/...? + <youpi> packages with -Werror will still bug out + <youpi> not that I consider -Werror to be a good idea, though :) + <tschwinge> youpi: Indeed. Compiler warnings can be caused by all kinds of + things. -Werror is good for development, but not for releases. |