summaryrefslogtreecommitdiffstats
path: root/llgo
Commit message (Collapse)AuthorAgeFilesLines
...
* Use the object's package to mangle method names, rather than the receiver's ↵Peter Collingbourne2014-12-164-8/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Update to new bindings.Peter Collingbourne2014-12-132-55/+49
| | | | llvm-svn: 224180
* Optimize comparisons to empty string.Peter Collingbourne2014-12-091-0/+16
| | | | | | | | Geo-mean performance improvement of 0.2% (-0.3% - 0.9% @ 95% CI). Differential Revision: http://reviews.llvm.org/D6569 llvm-svn: 223728
* Add .arcconfig file.Peter Collingbourne2014-12-081-0/+4
| | | | llvm-svn: 223689
* Roll gofrontend to 2a85649c19e1.Peter Collingbourne2014-12-049-37/+61
| | | | llvm-svn: 223385
* Initial commit of llgo third_party.Peter Collingbourne2014-11-272568-0/+675343
| | | | llvm-svn: 222858
* Initial commit of llgo.Peter Collingbourne2014-11-27148-0/+15789
llvm-svn: 222857
OpenPOWER on IntegriCloud