GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    sabik (sabik@rants.au)'s status on Monday, 01-Apr-2024 19:16:13 JST sabik sabik
    • owo what's chris
    • Hailey

    @chrisisgr8 @hailey
    Infinite loop without side-effects is UB; that said, you'd expect potential fall-through, not calling an unrelated function

    In conversation about a year ago from rants.au permalink
    • Embed this notice
      sabik (sabik@rants.au)'s status on Monday, 01-Apr-2024 19:16:04 JST sabik sabik
      in reply to
      • owo what's chris
      • Hailey
      • immibis
      • 💬

      @rfc6919 @immibis @hailey @chrisisgr8
      What a language!

      In conversation about a year ago permalink

      Attachments


      1. https://cache.rants.au/media_attachments/files/112/153/638/373/052/750/original/764705f331433202.png
    • Embed this notice
      💬 (rfc6919@aus.social)'s status on Monday, 01-Apr-2024 19:16:11 JST 💬 💬
      in reply to
      • owo what's chris
      • Hailey
      • immibis

      @immibis @hailey @sabik @chrisisgr8 iirc the behaviour is because the entire main() is optimised out thanks to the UB loop, then at runtime _start() jumps to where it expects main() to be

      In conversation about a year ago permalink
      GreenSkyOverMe (Monika) repeated this.
    • Embed this notice
      immibis (immibis@social.immibis.com)'s status on Monday, 01-Apr-2024 19:16:12 JST immibis immibis
      in reply to
      • owo what's chris
      • Hailey
      @sabik @chrisisgr8 @hailey in this case it looks like one part of the optimiser has noticed there's an infinite loop and removed the return instruction; another part of the optimiser has noticed there's an infinite loop and removed the infinite loop. This is allowed because C++ has some stupid rules.

      I believe the intention of infinite loops being UB was to allow the compiler to remove or merge loops in general without proving they halt.
      In conversation about a year ago permalink
    • Embed this notice
      huxley(fur) (huxley@furry.engineer)'s status on Monday, 01-Apr-2024 19:19:35 JST huxley(fur) huxley(fur)
      in reply to
      • owo what's chris
      • Hailey

      @sabik @chrisisgr8 @hailey

      This blog post goes into why the "unreachable" function is getting called -- the compiler creates assembly that falls through: https://carette.xyz/posts/the_unreachable_code_bug/

      So I think the idea is, they are defining this behavior so that this no longer happens?

      In conversation about a year ago permalink

      Attachments


      GreenSkyOverMe (Monika) repeated this.
    • Embed this notice
      Peter Bindels (dascandy42@mastodon.social)'s status on Monday, 01-Apr-2024 19:19:35 JST Peter Bindels Peter Bindels
      in reply to
      • owo what's chris
      • Hailey
      • huxley(fur)

      @huxley @sabik @chrisisgr8 @hailey I think the paper on this is proposing to make it crash reliably on that point of entering UB land, and not allowing yolo behavior.

      In conversation about a year ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.