hnes/libaco

Issues

• A full-featured, high-performance and lightweight scheduler for libaco is needed

  #22 opened 6 years ago by nishantd01
  12

• is aco_exit necessary?

  #61 opened 6 months ago by mttbx
  0

• Few questions about proper usage

  #60 opened 7 months ago by zukonake
  0

• whether this description is incorrect

  #59 opened 9 months ago by free-wind-0
  0

• `aco_amd64_inline_short_aligned_memcpy_test_ok` size alignment

  #58 opened a year ago by the-die
  0

• add arm32/aarch64 support for android and ios

  #57 opened 2 years ago by calvin2021y
  1

• Integrate into our io engine?

  #56 opened 2 years ago by beef9999
  1

• resume multiple coroutines in parallel

  #55 opened 2 years ago by tickox
  1

• Question: which is faster, creating new coroutines or reusing old coroutines

  #53 opened 3 years ago by ibogosavljevic
  3

• is it worth to create coroutine inside coroutine?

  #42 opened 3 years ago by ReiiSky
  0

• which one better to pass argument to co function

  #43 opened 3 years ago by ReiiSky
  0

• Do libaco coroutines run on different CPUs at the same time. i.e. does the program performance benefit from having multiple CPUs

  #52 opened 3 years ago by poetaman
  2

• Windows/MSVC support

  #6 opened 6 years ago by ddengster
  4

• is 120byte the lowest we can have? possible to lower this?

  #50 opened 3 years ago by superdolt
  1

• Feature Request: aco_get_co() return NULL when the caller is main co

  #48 opened 3 years ago by PunchShadow
  4

• Thread local storage support

  #46 opened 4 years ago by vluttine
  1

• Feature request: Ability to return a value from aco_yield()

  #47 opened 3 years ago by mrakh
  1

• arm & arm64 support

  #20 opened 6 years ago by lshamis
  5

• can libaco support yield/resume between threads?

  #40 opened 4 years ago by etorth
  3

• Addition of a build system generator

  #5 opened 6 years ago by elfring
  12

• 关于libco bug的疑问

  #44 opened 4 years ago by DGuco
  0

• Provide way to return error to caller instead of calling `abort()` on failed assertions

  #41 opened 5 years ago by adsr
  1

• 不再活跃维护/更新/开发了吗?

  #35 opened 5 years ago by echoface
  2

• Status and Future Plans of libaco

  #39 opened 5 years ago by hnes
  0

• Document c standard library dependencies

  #36 opened 5 years ago by moon-chilled
  0

• 为什么使用自行编写的acosw.S汇编来切换上下文，而不是使用现成的setjmp？

  #34 opened 5 years ago by liuziangexit
  1

• Request: having a version of aco_yield() that receives the coroutine to where to yield

  #31 opened 5 years ago by AltraMayor
  0

• Improvement: support a common entry for every non-main coroutine

  #30 opened 5 years ago by Light-of-Hers
  0

• Question: benchamrk about tcmalloc and memcpy

  #28 opened 6 years ago by guangqianpeng
  5

• Proposal: stack size of benchmark coroutines co_fp_stksz_xx() is optmized by compiler

  #27 opened 6 years ago by guangqianpeng
  1

• improvements to documentation

  #25 opened 6 years ago by ioquatix
  9

• build failed from the latest release

  #26 opened 6 years ago by yunfan
  2

• Question: Would there be some problem if one signal handler is triggered during the call of `acosw`?

  #24 opened 6 years ago by willmafh
  2

• Fail to build libaco

  #18 opened 6 years ago by xiaozongyang
  2

• Question: Does libaco only have the implementation of shared stack mode?

  #19 opened 6 years ago by lancewz
  6

• asm hints in aco.h aren't c99?

  #16 opened 6 years ago by postwait
  1

• Proposal: Add the MacOS support

  #11 opened 6 years ago by hnes
  1

• Question: Differences with my coroutine library?

  #12 opened 6 years ago by abbycin
  6

• Adjust code around memory allocations

  #3 opened 6 years ago by elfring
  1

• Improve cooperation with C++ environments

  #4 opened 6 years ago by elfring
  2

• reserved identifier violation

  #1 opened 6 years ago by elfring
  8

• Make an include guard unique

  #2 opened 6 years ago by elfring
  10