Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
RhodiumToad's profile
RhodiumToad
RhodiumToad
RhodiumToad
@RhodiumToad

Tweets

RhodiumToad

@RhodiumToad

Find me on IRC: #postgresql or #freebsd on http://freenode.net . (he/him)

Joined February 2019

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Frank Leonhardt‏ @extremecompute 15 Dec 2019
      • Report Tweet
      • Report NetzDG Violation

      What is it with clang/llvm on #FreeBSD not compiling? I'm using 12.1-RELEASE and the 12.1-RELEASE source and still it goes nuts, eating all of RAM before getting a kill. Compile the same file a couple of times more and suddenly it works. It's always CLANG! What am I missing?

      2 replies 1 retweet 0 likes
    2. RhodiumToad‏ @RhodiumToad 15 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @extremecompute

      If you're using poudriere, then consider disabling or reducing tmpfs use - llvm uses both lots of disk space (and therefore mem/swap if tmpfs is used) and lots of working RAM for compile/link.

      1 reply 0 retweets 0 likes
    3. RhodiumToad‏ @RhodiumToad 15 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RhodiumToad @extremecompute

      If you have sufficient swap space but still get OOM kills that DON'T have a "swap_pager_getswapspace" error, also try increasing vm.pageout_oom_seq a lot. (OOM kills can be triggered not by lack of swap space but by slowness in pageouts)

      1 reply 0 retweets 0 likes
    4. Frank Leonhardt‏ @extremecompute 16 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @RhodiumToad

      Thanks for the thoughts. I isolated the problem part of the build and ran the compiler directly from the shell. After a while it starts eating core at 50MB/second until its all gone. It's pretty obviously a leak in the compiler somewhere.

      1 reply 0 retweets 0 likes
    5. Frank Leonhardt‏ @extremecompute 16 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @extremecompute @RhodiumToad

      Worth mentioning this is a clean CD install of 12.1-R -> check out 12.1-R -> source -> buildworld. Only oddness is /usr/src and /usr/obj on ZFS datasets.

      1 reply 0 retweets 0 likes
    6. Frank Leonhardt‏ @extremecompute 16 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @extremecompute @RhodiumToad

      c++ -target x86_64-unknown-freebsd12.1 [...] -c /usr/src/contrib/llvm/tools/clang/lib/ASTMatchers/Dynamic/Registry.cpp -o ASTMatchers/Dynamic/Registry.o

      1 reply 0 retweets 0 likes
      RhodiumToad‏ @RhodiumToad 17 Dec 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @extremecompute

      Can't reproduce. Installed a 12.1 system with zfs in a 3GB bhyve vm, and tried a buildworld at -j4; it's still running (maybe ~45 min to go), but it compiled that file ok

      2:34 AM - 17 Dec 2019
      • 1 Like
      • Frank Leonhardt
      1 reply 0 retweets 1 like
        1. New conversation
        2. Frank Leonhardt‏ @extremecompute 17 Dec 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @RhodiumToad

          Thanks for the experiment. The totally weird thing about this is that it passed that file and then broke on another one later. And repeat. Its like an uninitialised variable is making the results random. Always with llvm/clang though.

          2 replies 0 retweets 0 likes
        3. Frank Leonhardt‏ @extremecompute 17 Dec 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @extremecompute @RhodiumToad

          FWIW I'm using 1Gb of core and 2Gb of swap (which is hardly touched until it goes bananas). High water mark on c++ is ~300Mb normally (size, not res); only sshd running and built using default(?) -j1.

          2 replies 0 retweets 0 likes
        4. 7 more replies

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info