On Thu, 16 Jun 2016 08:50:19 -0700 (PDT) ⚛ <0xe2.0x9a.0...@gmail.com> wrote:
> > > The current beta will work not too badly with amd64 code but > > > still doesn't use registers efficiently enough to support x86 > > > code as it uses too many register. optimized C/C++ code only > > > uses six or at most 7 registers, which the x86 architecture has, > > > but not the nine registers that the above requires. > > > > > > So for this tight loop, golang is still slower than optimized C/C+ > > > + code, but not by very much if array bounds checks are disabled. > > > > It appears you're well versed in the x86 process instruction set > > and code generation. Could you may be offer help to the folks > > working on improving the code generation backend of the gc > > compiler? > > Will golang or google pay money for such a work? IANAG [*] but I beleive it will not. ;-) My line of reasoning resulted in the friently nudge you're discussing was something like: "the person appears to be well-versed in this subject", "he is also interested in making Go programs go faster", "therefore, it would be good to contribute directly to where the speed is a concern". [*] I Am Not At Google. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
