Skip to content
Snippets Groups Projects
  1. Mar 27, 2020
  2. Mar 26, 2020
  3. Mar 25, 2020
    • Anchor's avatar
      32f1dfa5
    • Nat Goodspeed's avatar
      SL-793: Use Boost.Fiber instead of the "dcoroutine" library. · 66981fab
      Nat Goodspeed authored
      Longtime fans will remember that the "dcoroutine" library is a Google Summer
      of Code project by Giovanni P. Deretta. He originally called it
      "Boost.Coroutine," and we originally added it to our 3p-boost autobuild
      package as such. But when the official Boost.Coroutine library came along
      (with a very different API), and we still needed the API of the GSoC project,
      we renamed the unofficial one "dcoroutine" to allow coexistence.
      
      The "dcoroutine" library had an internal low-level API more or less analogous
      to Boost.Context. We later introduced an implementation of that internal API
      based on Boost.Context, a step towards eliminating the GSoC code in favor of
      official, supported Boost code.
      
      However, recent versions of Boost.Context no longer support the API on which
      we built the shim for "dcoroutine." We started down the path of reimplementing
      that shim using the current Boost.Context API -- then realized that it's time
      to bite the bullet and replace the "dcoroutine" API with the Boost.Fiber API,
      which we've been itching to do for literally years now.
      
      Naturally, most of the heavy lifting is in llcoros.{h,cpp} and
      lleventcoro.{h,cpp} -- which is good: the LLCoros layer abstracts away most of
      the differences between "dcoroutine" and Boost.Fiber.
      
      The one feature Boost.Fiber does not provide is the ability to forcibly
      terminate some other fiber. Accordingly, disable LLCoros::kill() and
      LLCoprocedureManager::shutdown(). The only known shutdown() call was in
      LLCoprocedurePool's destructor.
      
      We also took the opportunity to remove postAndSuspend2() and its associated
      machinery: FutureListener2, LLErrorEvent, errorException(), errorLog(),
      LLCoroEventPumps. All that dual-LLEventPump stuff was introduced at a time
      when the Responder pattern was king, and we assumed we'd want to listen on one
      LLEventPump with the success handler and on another with the error handler. We
      have never actually used that in practice. Remove associated tests, of course.
      
      There is one other semantic difference that necessitates patching a number of
      tests: with "dcoroutine," fulfilling a future IMMEDIATELY resumes the waiting
      coroutine. With Boost.Fiber, fulfilling a future merely marks the fiber as
      ready to resume next time the scheduler gets around to it. To observe the test
      side effects, we've inserted a number of llcoro::suspend() calls -- also in
      the main loop.
      
      For a long time we retained a single unit test exercising the raw "dcoroutine"
      API. Remove that.
      
      Eliminate llcoro_get_id.{h,cpp}, which provided llcoro::get_id(), which was a
      hack to emulate fiber-local variables. Since Boost.Fiber has an actual API for
      that, remove the hack.
      
      In fact, use (new alias) LLCoros::local_ptr for LLSingleton's dependency
      tracking in place of llcoro::get_id().
      
      In CMake land, replace BOOST_COROUTINE_LIBRARY with BOOST_FIBER_LIBRARY. We
      don't actually use the Boost.Coroutine for anything (though there exist
      plausible use cases).
      66981fab
  4. Aug 05, 2019
  5. Jul 24, 2019
  6. Mar 29, 2019
    • Geenz's avatar
      Tweaked naming a bit, also white space. · 0272c47e
      Geenz authored
      Will wait for a response from @graham_linden regarding moving the sRGB conversion functions in llmath.h to llrender.
      0272c47e
    • Geenz's avatar
      Gamma correction pass 2: · 57d88a8a
      Geenz authored
      Make sure lights are in the correct color space.
      Bonus: cache the sRGB color in setLightColor on point and spot lights.  Frees up a pow and some multiplies on the CPU every frame.
      57d88a8a
  7. Dec 24, 2018
  8. Nov 29, 2018
  9. Sep 07, 2018
  10. Sep 05, 2018
  11. Aug 15, 2018
  12. Aug 08, 2018
  13. Jul 30, 2018
    • Graham Linden's avatar
      MAINT-8915 · 60d256e8
      Graham Linden authored
      Fix sync of material rotation and offset values when using aligned planar faces.
      
      Make it possible to set a specific TE's normal/spec offset/rotation values.
      
      Eliminate redundant conversions in LLSD -> struct handler.
      60d256e8
  14. Jul 20, 2018
  15. Jul 13, 2018
  16. Jun 29, 2018
  17. Jun 28, 2018
  18. Jun 19, 2018
  19. Jun 13, 2018
  20. Jun 12, 2018
  21. Jun 08, 2018
  22. Jun 01, 2018
  23. May 24, 2018
  24. Feb 21, 2018
  25. Feb 14, 2018
  26. Jan 22, 2018
  27. Jan 03, 2018
  28. Dec 20, 2017
  29. Dec 14, 2017
  30. Oct 31, 2017
  31. Nov 13, 2017
  32. May 30, 2017
  33. May 25, 2017
  34. Apr 14, 2017
  35. Mar 28, 2017
  36. Jan 24, 2017
    • ruslantproductengine's avatar
      MAINT-6645 - Improvement - Agents that render as jelly dolls should have their... · 6770c273
      ruslantproductengine authored
      MAINT-6645 - Improvement - Agents that render as jelly dolls should have their attachments render at 0 LoD to prevent loading higher LoD complexity in memory thus deterring crashes.
      Comments:
      - Fix based on "RenderAutoMuteByteLimit" setting.
      - File indra/llxml/llcontrol.h - add all signals to 0 group.
        It garanty that handlers (in indra/newview/llviewercontrol.cpp) will be called last.
      6770c273
  37. Dec 23, 2016
Loading