| Age | Commit message (Collapse) | Author |
|
R=bradfitzgo
CC=golang-dev
https://golang.org/cl/3989052
|
|
This code implements bzip2 decompression only.
R=bradfitzgo, r2, nigeltao, rsc
CC=golang-dev
https://golang.org/cl/4176051
|
|
R=rsc
CC=bsiegert, golang-dev, mpl
https://golang.org/cl/4182081
|
|
Using make -C $* rather than (cd $* ; make) results in a small,
but measurable improvement in build times where compilation is
not the major component. eg.
before - ~/go/src/pkg$ time make
real 0m1.176s
user 0m0.639s
sys 0m0.399s
after - ~/go/src/pkg$ time make
real 0m0.916s
user 0m0.571s
sys 0m0.243s
There are other places in the distribution src/make.common for example
that could also benefit from this change.
R=adg
CC=golang-dev, rsc
https://golang.org/cl/4174055
|
|
Even if local, it requires communication with a daemon
which may not be available. This is creating problems
for getting an Ubuntu package going in Launchpad's PPA.
R=golang-dev, rsc
CC=golang-dev
https://golang.org/cl/3989062
|
|
Must be invoked as ./clean.bash --gomake make
(or --gomake gmake, depending on the name of
GNU make).
R=niemeyer
CC=golang-dev
https://golang.org/cl/4023065
|
|
The crypto package is added as a common place to store identifiers for
hash functions. At the moment, the rsa package has an enumeration of
hash functions and knowledge of their digest lengths. This is an
unfortunate coupling and other high level crypto packages tend to need
to duplicate this enumeration and knowledge (i.e. openpgp).
crypto pulls this code out into a common location.
It would also make sense to add similar support for ciphers to crypto,
but the problem there isn't as acute that isn't done in this change.
R=bradfitzgo, r, rsc
CC=golang-dev
https://golang.org/cl/4080046
|
|
R=bradfitzgo, r, bradfitzwork, nsz, rsc
CC=golang-dev
https://golang.org/cl/3990043
|
|
R=rsc
CC=Miek Gieben, golang-dev
https://golang.org/cl/3926041
|
|
R=rsc, peterGo, brainman
CC=golang-dev
https://golang.org/cl/3733046
|
|
Facilities for printing stack traces from within a running goroutine.
R=rsc
CC=golang-dev
https://golang.org/cl/4031041
|
|
The code was (as annotated in the source code) adopted from Tom's
LibCrypt (public domain code, [1]). It was neither optimised for speed
nor were any security features added.
[1] http://libtom.org/?page=features&newsitems=5&whatfile=crypt
R=rsc, berengarlehr, albert.strasheim, agl1
CC=golang-dev, schulze
https://golang.org/cl/2687042
|
|
I needed a way to read lines without worrying about \n and \r\n.
R=r, rsc
CC=golang-dev
https://golang.org/cl/2859041
|
|
This is largely based on ality's CL 2747042.
crypto/rc4: API break in order to conform to crypto/cipher's
Stream interface
cipher/cipher: promote to the default build
Since CBC differs between TLS 1.0 and 1.1, we downgrade and
support only 1.0 at the current time. 1.0 is what most of the
world uses.
Given this CL, it would be trival to add support for AES 256,
SHA 256 etc, but I haven't in order to keep the change smaller.
R=rsc
CC=ality, golang-dev
https://golang.org/cl/3659041
|
|
The recent linker changes broke NaCl support
a month ago, and there are no known users of it.
The NaCl code can always be recovered from the
repository history.
R=adg, r
CC=golang-dev
https://golang.org/cl/3671042
|
|
R=brainman, rsc
CC=golang-dev
https://golang.org/cl/3533041
|
|
This patch adds a new package: os/inotify, which
provides a Go wrapper to the Linux inotify system.
R=rsc, albert.strasheim, rog, jacek.masiulaniec
CC=golang-dev
https://golang.org/cl/2049043
|
|
At the moment, and for the forseeable future, it only checks arguments to print calls.
R=rsc, gri, niemeyer, iant2, rog, lstoakes, jacek.masiulaniec, cw
CC=golang-dev
https://golang.org/cl/3522041
|
|
Move unported files (freebsd*, windows*, nacl*) to runtime/cgo.
Step toward fixing FreeBSD build.
R=r
TBR=r
CC=golang-dev
https://golang.org/cl/3497042
|
|
Formerly known as libcgo.
Almost no code here is changing; the diffs
are shown relative to the originals in libcgo.
R=r
CC=golang-dev
https://golang.org/cl/3420043
|
|
Fixes #1104.
R=golang-dev, mattn, r
CC=Joe Poirier, golang-dev
https://golang.org/cl/3051041
|
|
elliptic implements several standard elliptic curves over prime fields.
R=r, r2
CC=golang-dev
https://golang.org/cl/3065041
|
|
CAST5 is the default OpenPGP cipher.
(This won't make Rob any happier about the size of crypto/, of course.)
It already has dst, src in that order but it doesn't have any users yet so I figure it's better than changing it later.
R=rsc, gri, r
CC=golang-dev
https://golang.org/cl/2762042
|
|
R=rsc, mattn
CC=golang-dev
https://golang.org/cl/1976045
|
|
Rather than updating the stripped-down regexp implementation embedded
in testing, delete it by passing the one function we need from the package
main file created by gotest.
R=rsc
CC=golang-dev
https://golang.org/cl/2761043
|
|
Adds softfloat64 to generic runtime
(will be discarded by linker when unused)
and adds test for it. I used the test to check
the software code against amd64 hardware
and then check the software code against
the arm and its simulation of hardware.
The latter should have been a no-op (testing
against itself) but turned up a bug in 5c causing
the vlrt.c routines to miscompile.
These changes make the cmath, math,
and strconv tests pass without any special
accommodations for arm.
R=ken2
CC=golang-dev
https://golang.org/cl/2713042
|
|
R=ken2
CC=golang-dev
https://golang.org/cl/2670042
|
|
R=ken2
CC=golang-dev
https://golang.org/cl/2666041
|
|
Just enough to make mov instructions work,
which in turn is enough to make strconv work
when it avoids any floating point calculations.
That makes a bunch of other packages pass
their tests.
Should suffice until hardware floating point
is available.
Enable package tests that now pass
(some due to earlier fixes).
Looks like there is a new integer math bug
exposed in the fmt and json tests.
R=ken2
CC=golang-dev
https://golang.org/cl/2638041
|
|
R=ken2
CC=golang-dev
https://golang.org/cl/2606041
|
|
R=adg
CC=golang-dev
https://golang.org/cl/2470045
|
|
R=ken2
CC=golang-dev
https://golang.org/cl/2520042
|
|
R=rsc, iant, agl
CC=golang-dev
https://golang.org/cl/2052042
|
|
The remaining failures include:
* something about bit operations?
crypto/block
encoding/binary
* something about file I/O?
archive/tar
archive/zip
debug/dwarf
debug/elf
debug/macho
image/png
* floating point
cmath
expvar
flag
fmt
gob
json
math
strconv
template
xml
* network (maybe fixed by a pending CL)
http
netchan
rpc
rpc/jsonrpc
syslog
websocket
* line numbers
log
* haven't bothered / not sure
exp/datafmt
exp/eval
go/printer
os
os/signal
testing/quick
R=ken2
CC=golang-dev
https://golang.org/cl/2496041
|
|
Package iterable has outlived its utility.
It is an interesting demonstration, but it encourages
people to use iteration over channels where simple
iteration over array indices or a linked list would be
cheaper, simpler, and have fewer races.
R=dsymonds, r
CC=golang-dev
https://golang.org/cl/2436041
|
|
An exercise in reflection and an unusual tool.
From the usage message:
usage: gotry [packagedirectory] expression ...
Given one expression, gotry attempts to evaluate that expression.
Given multiple expressions, gotry treats them as a list of arguments
and result values and attempts to find a function in the package
that, given the first few expressions as arguments, evaluates to
the remaining expressions as results. If the first expression has
methods, it will also search for applicable methods.
If there are multiple expressions, a package directory must be
specified. If there is a package argument, the expressions are
evaluated in an environment that includes
import . "packagedirectory"
Examples:
gotry 3+4
# evaluates to 7
gotry strings '"abc"' '"c"' 7-5
# finds strings.Index etc.
gotry regexp 'MustCompile("^[0-9]+")' '"12345"' true
# finds Regexp.MatchString
R=rsc, PeterGo, r2
CC=golang-dev
https://golang.org/cl/2352043
|
|
TBR=adg
CC=golang-dev
https://golang.org/cl/2290045
|
|
Fixes #1110.
R=golang-dev, adg
CC=Joe Poirier, golang-dev
https://golang.org/cl/2367041
|
|
Fixes #1105.
R=golang-dev, r
CC=Joe Poirier, golang-dev
https://golang.org/cl/2343043
|
|
R=ken2
CC=golang-dev
https://golang.org/cl/2345041
|
|
R=adg
TBR=adg
CC=golang-dev
https://golang.org/cl/2326041
|
|
R=rsc
CC=golang-dev
https://golang.org/cl/2125042
|
|
R=ken2
CC=golang-dev
https://golang.org/cl/2298041
|
|
This is a replacement for pending CL 2219042. It only contains
the raw suffixarray functionality with two methods:
- New create a new index from some data
- Lookup lookup occurences of a bytes slice in the data
Any other functionality (dealing with multiple data sets and
the corresponding position lists) is generic and doesn't have
to be part of this package.
Known performance bug: This implementation works fine for data sets
up to several megabytes as long as it doesn't contain very long
contiguous sequences of equal bytes. For instance, index creation for
all .go files under GOROOT (250KLOCs, approx. 9MB) takes ~50s on
2.66 GHz Intel Xeon as long as test/fixedbugs/257.go is excluded.
With that file, index creation times takes several days. 257.go contains
a string of 1M smiley faces.
There are more sophisticated suffixarray creation algorithms which
can handle very long common prefixes. The implementation can be
updated w/o the need to change the interface.
R=rsc, r, PeterGo
CC=golang-dev
https://golang.org/cl/2265041
|
|
Sent from my phone.
R=adg
CC=golang-dev
https://golang.org/cl/2192049
|
|
Re-enable the test on Windows.
R=brainman, alex.brainman
CC=golang-dev
https://golang.org/cl/2244041
|
|
R=r
CC=golang-dev
https://golang.org/cl/2225042
|
|
gc records full, '/' delimited, filenames now.
R=rsc
CC=golang-dev
https://golang.org/cl/1962042
|
|
R=r, Joe Poirier, rsc
CC=golang-dev
https://golang.org/cl/2123044
|
|
Add windows NOTEST list to pkg make file.
5a make file. the change removes a space
character that was included when appending
an extension to TARG.
R=brainman, rsc
CC=golang-dev
https://golang.org/cl/2140046
|