9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Kenny Lasse Hoff Levinsen <kennylevinsen@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans]  Go: FP in note handler
Date: Mon, 22 Feb 2016 22:56:56 +0100	[thread overview]
Message-ID: <B2464B4F-FDD2-417A-8545-9456631B1F3D@gmail.com> (raw)
In-Reply-To: <fb16aa69c6b73a2e8f0260b4e6ee025c@hamnavoe.com>

For those interested in the matter, I have opened https://github.com/golang/go/issues/14471

I mention potentially reenabling duffcopy by writing some magic note handler code that avoid the regular copy and zero optimizations, but I’m not entirely sure if that’s a plausible path. If it is, I think it would bring benefit, both in the performance gained by duffcopy/duffzero, as well as the chances of this happening again. It is, however, slightly annoying to do, as you cannot use copy(), make() or even strings or byte array literals, as these will trip duffcopy and duffzero. Any comments to my silly idea?

Best regards,
Kenny Levinsen

> On 22 Feb 2016, at 18:16, Richard Miller <miller@hamnavoe.com> wrote:
> 
>> The trace of goexitsall still contain FP register access (XORPS and duffzero which contains MOVUPS)
> 
> Sorry, in that case I think my patch is not relevant for your issue
> (but it does prevent a deadlock on multiprocessors which you might
> also run into...)
> 




       reply	other threads:[~2016-02-22 21:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fb16aa69c6b73a2e8f0260b4e6ee025c@hamnavoe.com>
2016-02-22 21:56 ` Kenny Lasse Hoff Levinsen [this message]
     [not found] <83031ee52a34de15facd95dcbcabbad9@proxima.alt.za>
2016-02-23  8:26 ` Kenny Lasse Hoff Levinsen
     [not found] <e115154c5bab8971d7b88f64ba5d4402@proxima.alt.za>
2016-02-23 10:17 ` Kenny Lasse Hoff Levinsen
2016-02-23 15:27   ` erik quanstrom
2016-02-23 15:52     ` Kenny Lasse Hoff Levinsen
2016-02-23 17:02       ` erik quanstrom
2016-02-23 17:14         ` Kenny Lasse Hoff Levinsen
2016-02-23 17:31           ` lucio
2016-02-23 17:56             ` Kenny Lasse Hoff Levinsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B2464B4F-FDD2-417A-8545-9456631B1F3D@gmail.com \
    --to=kennylevinsen@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).