diff options
author | https://me.yahoo.com/a/g3Ccalpj0NhN566pHbUl6i9QF0QEkrhlfPM-#b1c14 <diana@web> | 2015-02-16 20:11:20 +0100 |
---|---|---|
committer | GNU Hurd web pages engine <web-hurd@gnu.org> | 2015-02-16 20:11:20 +0100 |
commit | d6d0960528e261acb11689d9d4283fea7363d42b (patch) | |
tree | cf1b83ba86f7d2cdd481ab93e83748789b524c5c | |
parent | 52f8b208805f9890bd6f539555465d21ab59a3d2 (diff) |
update for rename of open_issues/glibc.mdwn to service_solahart_jakarta_selatan__082122541663/glibc.mdwn
-rw-r--r-- | service_solahart_jakarta_selatan__082122541663/boehm_gc.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/service_solahart_jakarta_selatan__082122541663/boehm_gc.mdwn b/service_solahart_jakarta_selatan__082122541663/boehm_gc.mdwn index d728dea0..3c010ce2 100644 --- a/service_solahart_jakarta_selatan__082122541663/boehm_gc.mdwn +++ b/service_solahart_jakarta_selatan__082122541663/boehm_gc.mdwn @@ -193,7 +193,7 @@ sources, and for `libatomic_ops` to the /* We tried ... */ #endif - Being on [[glibc]], we could perhaps do similar as `USE_LIBC_PRIVATES` + Being on [[service_solahart_jakarta_selatan__082122541663/glibc]], we could perhaps do similar as `USE_LIBC_PRIVATES` instead of `HEURISTIC2`. Pro: avoid `SIGSEGV` (and general fragility) during probing at startup (if I'm understanding this correctly). Con: rely on glibc internals. Or we instead add support to parse @@ -232,7 +232,7 @@ sources, and for `libatomic_ops` to the * `read` - Sure that it doesn't internally (in [[glibc]]) use `malloc`. Probably + Sure that it doesn't internally (in [[service_solahart_jakarta_selatan__082122541663/glibc]]) use `malloc`. Probably only / mostly (?) a problem for `--enable-redirect-malloc` configurations? Linux with threads uses `readv`. |