Live data from Hacker News

Viewing profile — aykevl

aykevl

HN member
Joined
Sat, Aug 18, 2018, 1:45 PM UTC
HN karma
47
Public activity
18 items

About aykevl

No profile information was provided.

Recent public activity

  1. comment
    Comment #41808488

    M3 and M4 haven't been supported yet because they weren't a priority (looks like they've been focusing on gaming support for the last year or so). Alyssa said in her talk that they…

  2. comment
    Comment #33609924

    I believe the video decoder (h264 etc) is actually separate from the GPU.

  3. comment
    Comment #31695136

    Right now we don't have any support for Android and iOS in particular, but we do support Linux/ARM (regular Linux). It's an interesting use case however. > In my understanding it s…

  4. comment
    Comment #31132917

    Supporting GC on WebAssembly has been a _major_ pain for TinyGo because WebAssembly doesn't allow access to the stack. It's really slow and I'm still not confident it's bug free. H…

  5. comment
    Comment #20482527

    Not on the heap, but it can certainly have uninitialized variables on the stack. These cannot be created in normal Go code but the optimizer may decide to leave some values uniniti…

  6. comment
    Comment #20478697

    Oops, those docs need updating. The GC now works on all platforms (including RISC-V and WebAssembly!) except for AVR because the AVR backend is just too unreliable at the moment an…

  7. comment
    Comment #20478655

    That should be possible: there is also experimental AVR support. Experimental because the LLVM backend is unfortunately too buggy to be used in real programs (but is improving!). T…

  8. comment
    Comment #20478615

    Hehe, LLVM takes about an hour to compile on my laptop. The compiler itself is not tiny in any way. It really refers to the size of the binaries produced which is usually very smal…

  9. comment
    Comment #20478565

    The conservative mark-sweep implementation was the easiest to write: I don't think there is any real GC that is simpler. In the long term, the plan is to add other GCs that are pre…

  10. comment
    Comment #20478501

    There are 3 LLVM-based Go compilers that I'm aware of: gollvm, llgo, and tinygo. Of those, only TinyGo reimplements the runtime that causes lots of (code size) overhead in the othe…

  11. comment
    Comment #20478437

    https://tinygo.org/usage/important-options/ Take a look at the `-gc` flag. The values have changed in the latest version (need to update the docs!) but it does provide an option to…

  12. comment
    Comment #20318610

    I once asked this a cryptographer. His response was that he would do the following things (if I remember correctly): * Discuss the result with a few cryptographers he trusts, to ch…

  13. comment
    Comment #19828014

    Yes, there is a fair bit of documentation. But it is nowhere near any popular general purposes language. Also, most documentation isn't very accessible if you're not a compiler dev…

  14. comment
    Comment #17789406

    I'm certainly open to PRs :) Good catch on the LICENSE file, I totally forgot about it. I've added it now.

  15. comment
    Comment #17788855

    That's pretty cool! If you want something now, I've also written and abandoned this: https://github.com/aykevl/tinygo-gccgo It actually worked fairly well, but the code was way too…

  16. comment
    Comment #17788627

    Yeah the heavyweight standard library is a big problem. I'm trying to solve it (in part) with smart analysis that tries much harder to remove dead code and dead global data. Maybe …

  17. comment
    Comment #17788549

    I'm using this exactly. It's not the nicest interface but it supports almost everything that LLVM does. https://github.com/llir/llvm looks nice but I don't think you can interface …

  18. comment
    Comment #17788502

    Hi, I'm the author of the compiler. All backends supported by LLVM should be fairly easily supported by TinyGo. In fact, I've had the blinky example running on an Arduino a while b…