silently, as what the compiler does to unused variables.
David
On Friday, July 19, 2013 2:34:05 AM UTC+8, Nick Craig-Wood wrote:
That doesn't fix it unfortunately.
Also there are examples of exactly that style in the go source, eg
http://golang.org/src/pkg/bytes/bytes_decl.go
function
the
assembler. That
the stack
<mailto:ni...@craig-wood.com <javascript:>>> --http://www.craig-wood.com/nick
Google Groups "golang-nuts" group.
it, send an email to golang-nuts...@googlegroups.com <javascript:>
<mailto:golang-nuts%2bunsubscribe@googlegroups.com <javascript:>>.
https://groups.google.com/groups/opt_out.
--
Nick Craig-Wood <ni...@craig-wood.com <javascript:><mailto:ni...@craig-wood.com <javascript:>>> --
http://www.craig-wood.com/nick
--
Nick Craig-Wood <ni...@craig-wood.com <javascript:> <mailto:
ni...@craig-wood.com <javascript:>>>
-- http://www.craig-wood.com/nick
--
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...@googlegroups.com <javascript:>
<mailto:golang-nuts%2bunsubscribe@googlegroups.com <javascript:>>.
For more options, visit https://groups.google.com/groups/opt_out.
--
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...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
Nick Craig-Wood <ni...@craig-wood.com <javascript:>> --
http://www.craig-wood.com/nick
--That doesn't fix it unfortunately.
Also there are examples of exactly that style in the go source, eg
http://golang.org/src/pkg/bytes/bytes_decl.go
On 18/07/13 19:25, minux wrote:
please don't leave any empty lines between the annotation and the
declaration.
search for the annotation in the go tree for examples.
On Jul 19, 2013 2:00 AM, "Nick Craig-Wood" <ni...@craig-wood.com<javascript:>
<mailto:ni...@craig-wood.com <javascript:>>> wrote:
http://golang.org/cmd/gc/ - compiler directives ;-)
I can't seem to make it work though :-(
I made a before and after test here to demonstrate. I hope I'm just
doing something stupid!
https://github.com/ncw/go-noescape-test
Thanks in advance for any help!
<ni...@craig-wood.com <javascript:> wrote:
disable
allocateplease don't leave any empty lines between the annotation and the
declaration.
search for the annotation in the go tree for examples.
On Jul 19, 2013 2:00 AM, "Nick Craig-Wood" <ni...@craig-wood.com<javascript:>
<mailto:ni...@craig-wood.com <javascript:>>> wrote:
On 17/07/13 23:14, Dave Cheney wrote:
It's an undocumented secret annotation that only the gc compilers
support. Don't tell anyone.It's an undocumented secret annotation that only the gc compilers
http://golang.org/cmd/gc/ - compiler directives ;-)
I can't seem to make it work though :-(
I made a before and after test here to demonstrate. I hope I'm just
doing something stupid!
https://github.com/ncw/go-noescape-test
Thanks in advance for any help!
On 18/07/2013, at 8:08, Nick Craig-Wood <ni...@craig-wood.com<javascript:>
<mailto:ni...@craig-wood.com <javascript:>>> wrote:Exactly what I was looking for - thanks!
It didn't work immediately - I'll try some more in the morning.
It didn't work immediately - I'll try some more in the morning.
On 17/07/13 22:47, Dave Cheney wrote:
Grep for //go:noescape
On Thu, Jul 18, 2013 at 7:45 AM, Nick Craig-Wood
Grep for //go:noescape
On Thu, Jul 18, 2013 at 7:45 AM, Nick Craig-Wood
I've noticed that re-writing functions in assembler seems to
Go's escape analysis.
In the particular example I'm working on that causes go to
In the particular example I'm working on that causes go to
objects on the heap rather than the stack in the calling Go
which for some test cases outweighs the goodness of converting
called function to assembler!
To be specific in the below g() has been converted to
To be specific in the below g() has been converted to
seems to force f() to allocate `data` on the heap rather than
like it used to when g() was in Go.
func f() {
var data [64]byte
g(data)
}
Any ideas on how to get round this?
Thanks
Nick
--
Nick Craig-Wood <ni...@craig-wood.com <javascript:>
func f() {
var data [64]byte
g(data)
}
Any ideas on how to get round this?
Thanks
Nick
--
Nick Craig-Wood <ni...@craig-wood.com <javascript:>
--
You received this message because you are subscribed to the
You received this message because you are subscribed to the
To unsubscribe from this group and stop receiving emails from
<mailto:golang-nuts%2bunsubscribe@googlegroups.com <javascript:>>.
For more options, visit
--
Nick Craig-Wood <ni...@craig-wood.com <javascript:>
http://www.craig-wood.com/nick
--
Nick Craig-Wood <ni...@craig-wood.com <javascript:> <mailto:
ni...@craig-wood.com <javascript:>>>
-- http://www.craig-wood.com/nick
--
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...@googlegroups.com <javascript:>
<mailto:golang-nuts%2bunsubscribe@googlegroups.com <javascript:>>.
For more options, visit https://groups.google.com/groups/opt_out.
--
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...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
--
Nick Craig-Wood <ni...@craig-wood.com <javascript:>> --
http://www.craig-wood.com/nick
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
