
Previously the libgo Makefile explicitly listed the set of files to compile for each package. For packages that use build tags, this required a lot of awkward automake conditionals in the Makefile. This CL changes the build to look at the build tags in the files. The new shell script libgo/match.sh does the matching. This required adjusting a lot of build tags, and removing some files that are never used. I verified that the exact same sets of files are compiled on amd64 GNU/Linux. I also tested the build on i386 Solaris. Writing match.sh revealed some bugs in the build tag handling that already exists, in a slightly different form, in the gotest shell script. This CL fixes those problems as well. The old code used automake conditionals to handle systems that were missing strerror_r and wait4. Rather than deal with those in Go, those functions are now implemented in runtime/go-nosys.c when necessary, so the Go code can simply assume that they exist. The os testsuite looked for dir_unix.go, which was never built for gccgo and has now been removed. I changed the testsuite to look for dir.go instead. Reviewed-on: https://go-review.googlesource.com/25546 From-SVN: r239189
26 lines
724 B
Go
26 lines
724 B
Go
// Copyright 2012 The Go Authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style
|
|
// license that can be found in the LICENSE file.
|
|
|
|
// -build !amd64,!s390x
|
|
|
|
package aes
|
|
|
|
import (
|
|
"crypto/cipher"
|
|
)
|
|
|
|
// newCipher calls the newCipherGeneric function
|
|
// directly. Platforms with hardware accelerated
|
|
// implementations of AES should implement their
|
|
// own version of newCipher (which may then call
|
|
// newCipherGeneric if needed).
|
|
func newCipher(key []byte) (cipher.Block, error) {
|
|
return newCipherGeneric(key)
|
|
}
|
|
|
|
// expandKey is used by BenchmarkExpand and should
|
|
// call an assembly implementation if one is available.
|
|
func expandKey(key []byte, enc, dec []uint32) {
|
|
expandKeyGo(key, enc, dec)
|
|
}
|