about summary refs log tree commit diff
path: root/src/rt/jemalloc/ChangeLog
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2013-06-12 20:25:17 -0700
committerbors <bors@rust-lang.org>2013-06-12 20:25:17 -0700
commit996301331e2d8ac7611d15ca82cc3ebc1abb632d (patch)
tree032c91b56939850145b16ede2a5bfa35e4620f92 /src/rt/jemalloc/ChangeLog
parent6c45160f19cff60e8956491eabe9e4704735c0eb (diff)
parent0685c657f0b29f6372bd4b031753ff92fc3b53ba (diff)
downloadrust-996301331e2d8ac7611d15ca82cc3ebc1abb632d.tar.gz
rust-996301331e2d8ac7611d15ca82cc3ebc1abb632d.zip
auto merge of #7079 : thestinger/rust/jemalloc, r=graydon
Minor release, the ChangeLog is included in the update.
Diffstat (limited to 'src/rt/jemalloc/ChangeLog')
-rw-r--r--src/rt/jemalloc/ChangeLog15
1 files changed, 14 insertions, 1 deletions
diff --git a/src/rt/jemalloc/ChangeLog b/src/rt/jemalloc/ChangeLog
index fc096d8f42f..8ab884875b0 100644
--- a/src/rt/jemalloc/ChangeLog
+++ b/src/rt/jemalloc/ChangeLog
@@ -6,6 +6,19 @@ found in the git revision history:
     http://www.canonware.com/cgi-bin/gitweb.cgi?p=jemalloc.git
     git://canonware.com/jemalloc.git
 
+* 3.4.0 (June 2, 2013)
+
+  This version is essentially a small bugfix release, but the addition of
+  aarch64 support requires that the minor version be incremented.
+
+  Bug fixes:
+  - Fix race-triggered deadlocks in chunk_record().  These deadlocks were
+    typically triggered by multiple threads concurrently deallocating huge
+    objects.
+
+  New features:
+  - Add support for the aarch64 architecture.
+
 * 3.3.1 (March 6, 2013)
 
   This version fixes bugs that are typically encountered only when utilizing
@@ -15,7 +28,7 @@ found in the git revision history:
   - Fix a locking order bug that could cause deadlock during fork if heap
     profiling were enabled.
   - Fix a chunk recycling bug that could cause the allocator to lose track of
-    whether a chunk was zeroed.   On FreeBSD, NetBSD, and OS X, it could cause
+    whether a chunk was zeroed.  On FreeBSD, NetBSD, and OS X, it could cause
     corruption if allocating via sbrk(2) (unlikely unless running with the
     "dss:primary" option specified).  This was completely harmless on Linux
     unless using mlockall(2) (and unlikely even then, unless the