From a17570cda55df3224cb671f410d0986b2f565ac5 Mon Sep 17 00:00:00 2001 From: Ivan Maidanski Date: Sun, 23 Feb 2014 16:56:54 +0400 Subject: [PATCH] Update emails/links due to project site and ML transition (www.hpl.hp.com/personal/Hans_Boehm -> www.hboehm.info; gc@linux.hpl.hp.com -> bdwgc@lists.opendylan.org) * AUTHORS: Update email. * doc/gc.man: Likewise. * README.QUICK: Change external link to gcinterface.html to local one (pointing to the file in "doc" folder). * README.md: Replace BDWGC site URL (www.hpl.hp.com/personal/Hans_Boehm to www.hboehm.info). * doc/gc.man: Likewise. * doc/gcdescr.html: Likewise. * doc/gcinterface.html: Likewise. * doc/overview.html: Likewise. * doc/scale.html: Likewise. * README.md: Update mailing list info (gc@linux.hpl.hp.com to bdwgc@lists.opendylan.org, gc-announce@linux.hpl.hp.com to bdwgc-announce@lists.opendylan.org). * configure.ac: Likewise. * doc/gcdescr.html: Likewise. * doc/overview.html: Likewise. * doc/tree.html: Remove unnecessary external link. --- AUTHORS | 2 +- README.QUICK | 5 +- README.md | 18 +++--- configure.ac | 2 +- doc/gc.man | 6 +- doc/gcdescr.html | 12 ++-- doc/gcinterface.html | 2 +- doc/overview.html | 130 +++++++++++++++++++++---------------------- doc/scale.html | 3 +- doc/tree.html | 4 +- 10 files changed, 86 insertions(+), 98 deletions(-) diff --git a/AUTHORS b/AUTHORS index 0b106818..198d0296 100644 --- a/AUTHORS +++ b/AUTHORS @@ -131,7 +131,7 @@ Grzegorz Jakacki Gustavo Rodriguez-Rivera H.J. Lu Hanno Boeck -Hans Boehm +Hans Boehm Hans-Peter Nilsson Harris NightHawk Henning Makholm diff --git a/README.QUICK b/README.QUICK index 1f419cfd..ee8f4a11 100644 --- a/README.QUICK +++ b/README.QUICK @@ -69,9 +69,8 @@ instead of GC_MALLOC. Define GC_DEBUG before including gc.h for additional checking. -More documentation on the collector interface can be found at -http://www.hpl.hp.com/personal/Hans_Boehm/gc/gcinterface.html, -in README.md and other files in the doc directory, and in include/gc.h file. +More documentation on the collector interface can be found in README.md, +doc/gcinterface.html, include/gc.h, and other files in the doc directory. WARNINGS: diff --git a/README.md b/README.md index 2867013c..d5919fce 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,8 @@ This is version 7.5.0 (next release development) of a conservative garbage collector for C and C++. You might find a more recent version -[here](http://www.hpl.hp.com/personal/Hans_Boehm/gc). +[here](http://www.hboehm.info/gc/), or +[here](https://github.com/ivmai/bdwgc). ## Overview @@ -36,9 +37,6 @@ and * Boehm H., "Simple GC-safe Compilation", Proceedings of the ACM SIGPLAN '96 Conference on Programming Language Design and Implementation. -(Some of these are also available from -[here](http://www.hpl.hp.com/personal/Hans_Boehm/papers/), among other places.) - Unlike the collector described in the second reference, this collector operates either with the mutator stopped during the entire collection (default) or incrementally during allocations. (The latter is supported @@ -55,8 +53,8 @@ CSL 84-7). Doug McIlroy wrote a simpler fully conservative collector that was part of version 8 UNIX (tm), but appears to not have received widespread use. -Rudimentary tools for use of the collector as a leak detector are included -([link](http://www.hpl.hp.com/personal/Hans_Boehm/gc/leak.html)), +Rudimentary tools for use of the collector as a +[leak detector](http://www.hboehm.info/gc/leak.html) are included, as is a fairly sophisticated string package "cord" that makes use of the collector. (See doc/README.cords and H.-J. Boehm, R. Atkinson, and M. Plass, "Ropes: An Alternative to Strings", Software Practice and Experience 25, 12 @@ -64,7 +62,7 @@ collector. (See doc/README.cords and H.-J. Boehm, R. Atkinson, and M. Plass, in Xerox Cedar, or the "rope" package in the SGI STL or the g++ distribution.) Further collector documentation can be found -[here](http://www.hpl.hp.com/personal/Hans_Boehm/gc). +[here](http://www.hboehm.info/gc/). ## General Description @@ -516,9 +514,9 @@ per MB of accessible memory that needs to be scanned and processor. Your mileage may vary.) The incremental/generational collection facility may help in some cases. -Please address bug reports [here](mailto:gc@linux.hpl.hp.com). If you are -contemplating a major addition, you might also send mail to ask whether -it's already been done (or whether we tried and discarded it). +Please address bug reports [here](mailto:bdwgc@lists.opendylan.org). +If you are contemplating a major addition, you might also send mail to ask +whether it's already been done (or whether we tried and discarded it). ## Copyright & Warranty diff --git a/configure.ac b/configure.ac index 7458008a..6e6ea7cf 100644 --- a/configure.ac +++ b/configure.ac @@ -12,7 +12,7 @@ dnl Process this file with autoconf to produce configure. # Initialization -AC_INIT(gc,7.5.0,gc@linux.hpl.hp.com) +AC_INIT(gc,7.5.0,bdwgc@lists.opendylan.org) ## version must conform to [0-9]+[.][0-9]+[.][0-9]+ AC_CONFIG_SRCDIR(gcj_mlc.c) AC_CONFIG_MACRO_DIR([m4]) diff --git a/doc/gc.man b/doc/gc.man index ef159289..45537376 100644 --- a/doc/gc.man +++ b/doc/gc.man @@ -91,13 +91,13 @@ Other facilities not discussed here include limited facilities to support increm .SH "SEE ALSO" The README and gc.h files in the distribution. More detailed definitions of the functions exported by the collector are given there. (The above list is not complete.) .LP -The web site at http://www.hpl.hp.com/personal/Hans_Boehm/gc . +The web site at http://www.hboehm.info/gc/ . .LP Boehm, H., and M. Weiser, "Garbage Collection in an Uncooperative Environment", -\fISoftware Practice & Experience\fP, September 1988, pp. 807-820. +"Software Practice & Experience", September 1988, pp. 807-820. .LP The malloc(3) man page. .LP .SH AUTHOR -Hans-J. Boehm (Hans.Boehm@hp.com). +Hans-J. Boehm (boehm@acm.org). Some of the code was written by others, most notably Alan Demers. diff --git a/doc/gcdescr.html b/doc/gcdescr.html index 8a1dae06..07afd7cc 100644 --- a/doc/gcdescr.html +++ b/doc/gcdescr.html @@ -425,7 +425,7 @@ Java-style unordered finalization, and to ignore certain kinds of cycles,

Generational Collection and Dirty Bits

We basically use the concurrent and generational GC algorithm described in -"Mostly Parallel Garbage Collection", +"Mostly Parallel Garbage Collection", by Boehm, Demers, and Shenker.

The most significant modification is that @@ -616,17 +616,13 @@ GC versions before 7 do not invoke the thread-local allocator by default. For some more details see here, and the technical report entitled -``Fast Multiprocessor Memory Allocation and Garbage Collection'' - +"Fast Multiprocessor Memory Allocation and Garbage Collection"

Comments are appreciated. Please send mail to -gc@linux.hpl.hp.com +bdwgc@lists.opendylan.org (GC mailing list) or -Hans.Boehm@hp.com -

-This is a modified copy of a page written while the author was at SGI. -The original was here. +boehm@acm.org diff --git a/doc/gcinterface.html b/doc/gcinterface.html index 31a41fcd..c315af88 100644 --- a/doc/gcinterface.html +++ b/doc/gcinterface.html @@ -249,7 +249,7 @@ memory, while the second two allocate collectible memory. The single_client versions are not safe for concurrent access by multiple threads, but are faster.

-For an example, click here. +For an example, click here.

Class inheritance based interface for new-based allocation
Users may include gc_cpp.h and then cause members of classes to diff --git a/doc/overview.html b/doc/overview.html index 833c63a0..00d5d4f4 100644 --- a/doc/overview.html +++ b/doc/overview.html @@ -4,11 +4,11 @@ - - + + - - + +
Interface OverviewTutorial SlidesFAQTutorial SlidesFAQ ExampleDownloadLicenseDownloadLicense

A garbage collector for C and C++

@@ -23,11 +23,13 @@
  • Contacts and Mailing List
    • [ This is an updated version of the page formerly at +www.hpl.hp.com/personal/Hans_Boehm/gc/, +before that at http://reality.sgi.com/boehm/gc.html and before that at ftp://parcftp.xerox.com/pub/gc/gc.html. ]

    -The Boehm-Demers-Weiser +The Boehm-Demers-Weiser conservative garbage collector can be used as a garbage collecting replacement for C malloc or C++ new. @@ -51,11 +53,11 @@ for C or C++ programs, though that is not its primary goal.

    Typically several versions will be available. Usually you should first try to use -gc_source/gc.tar.gz, +gc_source/gc.tar.gz, which is normally an older, more stable version.

    If that fails, try the latest explicitly numbered version -in +in gc_source/. Later versions may contain additional features, platform support, or bug fixes, but are likely to be less well tested. @@ -70,19 +72,20 @@ code for that version is available for browsing The arguments for and against conservative garbage collection in C and C++ are briefly discussed in -issues.html. The beginnings of -a frequently-asked-questions list are here. +issues.html. +The beginnings of a frequently-asked-questions list are +here.

    The garbage collector code is copyrighted by -Hans-J. Boehm, +Hans-J. Boehm, Alan J. Demers, Xerox Corporation, Silicon Graphics, and Hewlett-Packard Company. It may be used and copied without payment of a fee under minimal restrictions. -See the README file in the distribution or the -license for more details. +See the README file in the distribution or the +license for more details. IT IS PROVIDED AS IS, WITH ABSOLUTELY NO WARRANTY EXPRESSED OR IMPLIED. ANY USE IS AT YOUR OWN RISK.

    @@ -91,7 +94,7 @@ simply by replacing malloc with GC_malloc calls, replacing realloc with GC_realloc calls, and removing free calls. Exceptions are discussed -in issues.html. +in issues.html.

    Platforms

    The collector is not completely portable, but the distribution includes ports to most standard PC and UNIX/Linux platforms. @@ -127,7 +130,7 @@ we also do this, though with more modest processor scalability goals. Our approach is discussed briefly in scale.html.

    Some Collector Details

    -The collector uses a mark-sweep algorithm. +The collector uses a mark-sweep algorithm. It provides incremental and generational collection under operating systems which provide the right kind of virtual memory support. (Currently this includes SunOS[45], IRIX, @@ -166,7 +169,7 @@ if programs are written and tuned for garbage collection.

    Further Reading:

    The beginnings of a frequently asked questions list for this -collector are here. +collector are here.

    The following provide information on garbage collection in general:

    @@ -202,16 +205,16 @@ from those in the implementation. There is a related letter to the editor and a correction in the next issue.

    Boehm, H., and M. Weiser, -"Garbage Collection in an Uncooperative Environment", +"Garbage Collection in an Uncooperative Environment", Software Practice & Experience, September 1988, pp. 807-820.

    -Boehm, H., A. Demers, and S. Shenker, "Mostly Parallel Garbage Collection", Proceedings -of the ACM SIGPLAN '91 Conference on Programming Language Design and Implementation, +Boehm, H., A. Demers, and S. Shenker, "Mostly Parallel Garbage Collection", +Proceedings of the ACM SIGPLAN '91 Conference on Programming Language Design and Implementation, SIGPLAN Notices 26, 6 (June 1991), pp. 157-164.

    -Boehm, H., "Space Efficient Conservative Garbage Collection", Proceedings of the ACM -SIGPLAN '93 Conference on Programming Language Design and Implementation, SIGPLAN -Notices 28, 6 (June 1993), pp. 197-206. +Boehm, H., "Space Efficient Conservative Garbage Collection", +Proceedings of the ACM SIGPLAN '93 Conference on Programming Language Design +and Implementation, SIGPLAN Notices 28, 6 (June 1993), pp. 197-206.

    Boehm, H., "Reducing Garbage Collector Cache Misses", Proceedings of the 2000 International Symposium on Memory Management . @@ -256,13 +259,11 @@ We thank John Levine and JCLT for allowing us to make the second paper available electronically, and providing PostScript for the final version.

    -Boehm, H., ``Simple -Garbage-Collector-Safety'', Proceedings -of the ACM SIGPLAN '96 Conference on Programming Language Design +Boehm, H., "Simple Garbage-Collector-Safety", +Proceedings of the ACM SIGPLAN '96 Conference on Programming Language Design and Implementation.

    -Boehm, H., and D. Chase, -``A Proposal for Garbage-Collector-Safe C Compilation'', +Boehm, H., and D. Chase, "A Proposal for Garbage-Collector-Safe C Compilation", Journal of C Language Translation 4, 2 (Decemeber 1992), pp. 126-141.

    Other related information: @@ -277,7 +278,7 @@ John Ellis and David Detlef's paper collection.

    -Slides for Hans Boehm's Allocation and GC Myths talk. +Slides for Hans Boehm's Allocation and GC Myths talk.

    Current users:

    Known current users of some variant of this collector include:

    @@ -344,9 +345,9 @@ use the collector. Description of alternate interfaces to the garbage collector.

    -Slides from an ISMM 2004 tutorial about the GC. +Slides from an ISMM 2004 tutorial about the GC.

    -A FAQ (frequently asked questions) list. +A FAQ (frequently asked questions) list.

    How to use the garbage collector as a leak detector.

    @@ -360,67 +361,64 @@ garbage collector.

    Scalability of the collector to multiprocessors.

    -Directory containing garbage collector source. - +Directory containing garbage collector source.

    More background information at this site

    -An attempt to establish a bound on space usage of -conservative garbage collectors. +An attempt to establish a bound on space usage of +conservative garbage collectors.

    -Mark-sweep versus copying garbage collectors -and their complexity. +Mark-sweep versus copying garbage collectors +and their complexity.

    -Pros and cons of conservative garbage collectors, -in comparison to other collectors. - +Pros and cons of conservative garbage collectors, +in comparison to other collectors.

    -Issues related to garbage collection vs. -manual memory management in C/C++. +Issues related to garbage collection vs. +manual memory management in C/C++.

    -An example of a case in which garbage collection -results in a much faster implementation as a result of reduced -synchronization. +An example of a case in which garbage collection +results in a much faster implementation as a result of reduced synchronization.

    -Slide set discussing performance of nonmoving -garbage collectors. +Slide set discussing performance of nonmoving +garbage collectors.

    - + Slide set discussing Destructors, Finalizers, and Synchronization -(POPL 2003). +(POPL 2003).

    -Paper corresponding to above slide set. +Paper corresponding to above slide set ( -Technical Report version.) +Technical Report version).

    -A Java/Scheme/C/C++ garbage collection benchmark. +A Java/Scheme/C/C++ garbage collection benchmark.

    -Slides for talk on memory allocation myths. +Slides for talk on memory allocation myths.

    -Slides for OOPSLA 98 garbage collection talk. +Slides for OOPSLA 98 garbage collection talk.

    -Related papers. -

    Contacts and Mailing List

    +Related papers. +

    Contacts and Mailing List

    We have recently set up two mailing list for collector announcements and discussions: -To subscribe to these lists, send a mail message containing the -word "subscribe" to -gc-announce-request@linux.hpl.hp.com -or to -gc-request@linux.hpl.hp.com. -(Please ignore the instructions about web-based subscription. -The listed web site is behind the HP firewall.) +To subscribe to these lists, please visit +lists.opendylan.org/mailman/listinfo/bdwgc-announce +and +lists.opendylan.org/mailman/listinfo/bdwgc, +respectively.

    The archives for these lists appear -here. +here and +here, +respectively. The gc list archive may also be read at gmane.org.

    @@ -430,8 +428,6 @@ java mailing list, whose archives appear gclist@iecc.com.

    Comments and bug reports may also be sent to -(Hans.Boehm@hp.com) or (boehm@acm.org), but the gc mailing list is usually preferred. -

    diff --git a/doc/scale.html b/doc/scale.html index feb14f13..9faff6cb 100644 --- a/doc/scale.html +++ b/doc/scale.html @@ -132,7 +132,8 @@ simultaneously runnable threads, this may have disastrous performance consequences (e.g. a factor of 10 slowdown).

    Performance

    We conducted some simple experiments with a version of -our GC benchmark that was slightly modified to +our GC benchmark +that was slightly modified to run multiple concurrent client threads in the same address space. Each client thread does the same work as the original benchmark, but they share a heap. diff --git a/doc/tree.html b/doc/tree.html index 429ae19d..f1c6e269 100644 --- a/doc/tree.html +++ b/doc/tree.html @@ -6,9 +6,7 @@

    Two-Level Tree Structure for Fast Pointer Lookup

    -The conservative garbage collector described -here -uses a 2-level tree +The BDWGC conservative garbage collector uses a 2-level tree data structure to aid in fast pointer identification. This data structure is described in a bit more detail here, since

      -- 2.40.0