4 Commits

Author	SHA1	Message	Date
Peter Collingbourne	56109b78c7	Roll gotools to 47f2109c. ... At the same time, perform a number of simplifications: - Rename go.tools directory to gotools. - Import only the go directory; all required Go analysis code and its dependencies have now been moved to this directory. llvm-svn: 225825	2015-01-13 20:45:08 +00:00
Peter Collingbourne	82a260eaaf	irgen: introduce ManglePackagePath function ... This is useful for clients that need to use llgo's mangling of the package path to look up a specific function within a given package. Differential Revision: http://reviews.llvm.org/D6801 llvm-svn: 225027	2014-12-31 00:25:34 +00:00
Peter Collingbourne	545e7276a8	Use the object's package to mangle method names, rather than the receiver's package ... If we use the receiver's package, we can end up with identical manglings for different functions. Consider: package p type U struct{} func (U) f() package q import "p" type T struct { p.U } func (T) f() The method set of *T has two synthetic methods named (*T).f(); one forwards to (T).f(), and the other to (U).f(). Previously, we were distinguishing them by the receiver's package, and in this case because both methods have the same receiver, they received the same name. The methods are correctly distinguished by the package owning the identifier "f", which is available via f.Object().Pkg(). Differential Revision: http://reviews.llvm.org/D6673 llvm-svn: 224357	2014-12-16 20:04:55 +00:00
Peter Collingbourne	ad9841e8ac	Initial commit of llgo. ... llvm-svn: 222857	2014-11-27 00:06:42 +00:00