home.social

Search

1000 results for “sourceware”

  1. I'm a bit sad today. Yesterday I pushed forge.sourceware.org/gcc/gcc-m, which makes a simple `x + 1` ill-formed: compiler-explorer.com/z/4rYx87. Now, in generic code, you write `+ std::cw<1>` instead. If you know the value-type (`float` in this case), just use the appropriate literal (if it exists): `x + 1.f`.

    #stdsimd #cpp26

  2. I'm a bit sad today. Yesterday I pushed forge.sourceware.org/gcc/gcc-m, which makes a simple `x + 1` ill-formed: compiler-explorer.com/z/4rYx87. Now, in generic code, you write `+ std::cw<1>` instead. If you know the value-type (`float` in this case), just use the appropriate literal (if it exists): `x + 1.f`.

    #stdsimd #cpp26

  3. I'm a bit sad today. Yesterday I pushed forge.sourceware.org/gcc/gcc-m, which makes a simple `x + 1` ill-formed: compiler-explorer.com/z/4rYx87. Now, in generic code, you write `+ std::cw<1>` instead. If you know the value-type (`float` in this case), just use the appropriate literal (if it exists): `x + 1.f`.

    #stdsimd #cpp26

  4. I'm a bit sad today. Yesterday I pushed forge.sourceware.org/gcc/gcc-m, which makes a simple `x + 1` ill-formed: compiler-explorer.com/z/4rYx87. Now, in generic code, you write `+ std::cw<1>` instead. If you know the value-type (`float` in this case), just use the appropriate literal (if it exists): `x + 1.f`.

    #stdsimd #cpp26

  5. Valgrind 3.27 RC1 is out

    An RC1 tarball for 3.27.0 is now available at
    sourceware.org/pub/valgrind/va
    (md5sum = bd95111c1a9f81f136c5e4e2c62b493e)
    (sha1sum = 0eefb3a7d86a3bd0154480db3d2173bb8bd6d7c1)
    sourceware.org/pub/valgrind/va
    Public keys can be found at klomp.org/mark/gnupg-pub.txt

    Please give it a try in configurations that are important for you and
    report any problems you have, either on the developer/user mailing list, or
    (preferably) via our bug tracker at
    bugs.kde.org/enter_bug.cgi?pro

    An RC2 should be available Fri Apr 17
    The final 3.27.0 release is scheduled for Mon Apr 20.

    #valgrind

  6. Note that someone created various CVEs for #elfutils based on (fixed and closed) bug reports without following our SECURITY policy: sourceware.org/cgit/elfutils/t

    These are NOT security issues according to our policy.

    We request that people who report suspected security vulnerabilities report them through the contacts in our SECURITY policy and not through non-affiliated CNAs.

    Creating random CVEs without coordinating with the upstream project and designated CNA just causes lots of make work.

  7. Queriendo sacar una traza de ejecución de un proceso con #GDB [1] no puedo porque "Process record and replay target doesn't support ioctl request".

    [1] sourceware.org/gdb/current/onl

  8. What I've been doing the last 3 days:
    - Working on a `./bootstrap` for ...

    What I'm doing today:
    - ...finished and sent it! sourceware.org/pipermail/binut
    - Finally responding to feedback on other changes I've sent off.

  9. Oh boy, they gave me further responsibilities in GCC: "Thomas Schwinge appointed co-maintainer of the nvptx backend", <inbox.sourceware.org/37d6cd4e->. 😳 🤖
    (That's the Nvidia GPU support in the @gnutools, used for and code offloading.)

  10. Oh boy, they gave me further responsibilities in GCC: "Thomas Schwinge appointed co-maintainer of the nvptx backend", <inbox.sourceware.org/37d6cd4e->. 😳 🤖
    (That's the Nvidia GPU support in the @gnutools, used for #OpenACC and #OpenMP code offloading.)

  11. Oh boy, they gave me further responsibilities in GCC: "Thomas Schwinge appointed co-maintainer of the nvptx backend", <inbox.sourceware.org/37d6cd4e->. 😳 🤖
    (That's the Nvidia GPU support in the @gnutools, used for #OpenACC and #OpenMP code offloading.)

  12. Oh boy, they gave me further responsibilities in GCC: "Thomas Schwinge appointed co-maintainer of the nvptx backend", <inbox.sourceware.org/37d6cd4e->. 😳 🤖
    (That's the Nvidia GPU support in the @gnutools, used for #OpenACC and #OpenMP code offloading.)

  13. Had a chance to debug `openjdk` build failure related to `make-4.4.1` update (`make-4.4` was fine): github.com/NixOS/nixpkgs/issue

    The result is a one-liner fix: github.com/openjdk/jdk/pull/12

    The fix is very similar to the `glibc` one needed for `make-4.4`: sourceware.org/PR29564

  14. Anticipating #valgrind 3.27.0.

    Andreas also showed there are still meaningful optimizations to be made on how memcheck tracks undefinedness bits as outlined in the original "Using Valgrind to detect undefined value errors with bit-precision" valgrind.org/docs/memcheck2005 paper.

    His optimization of memcheck instrumenting a bitwise AND/OR with a constant is clever and simplifies the generated code: sourceware.org/cgit/valgrind/c

  15. #Valgrind valgrind.org not only tweaks your instruction stream it also wraps all your system calls so it knows all (memory) manipulation that goes on in your program (and to hide itself from the program it is running inside).

    We integrated the #LTP linux-test-project.readthedocs syscalls testsuite with make ltpchecks

    We are now down to ~50 failures builder.sourceware.org/testrun

    All tracked in the meta bug dependency tree bugs.kde.org/showdependencytre

    Lets bring that count down to zarro boogs!

  16. Oh dear, #GCC is having its decennial existential crisis again, pondering the earth-shattering decision to switch to #C++20. 😱😴 Next they’ll be considering adding emojis to the compiler output for extra clarity. 😂🚀
    inbox.sourceware.org/gcc/aQj1t #existentialcrisis #compilerhumor #technews #HackerNews #ngated

  17. Today's one of these days when reading a mailing list discussion convinces me that I was right.

    So, do people agree with me? No, not at all. In fact, I can't even start to comprehend how lightly #Debian folks are treating such issues as a sudden #ABI change. I'm talking about changing `#time_t` from 32 bits to 64 bits, on 32-bit platforms. They're like: YOLO, let's just change it and see what happens…

    And what will happen? Well, if we have any program compiled with 32-bit time_t, that happens to link to a system library that now exposes 64-bit time_t in its ABI, then suddenly stuff's going to misalign. Like, we get all the fun C vulnerabilities — here function parameters will be misinterpreted, there we will be reading or writing to the wrong memory addresses…

    Ok, I guess Debian has it easier than #Gentoo. They're using binary packages, so at least as far as the system packages are concerned, they can do the upgrade in a reasonably reliable way, in a short time. In Gentoo, we're talking about hours or even days of rebuilding. And during this time *production systems* will be starting program with a risk of ABI incompatibility, or in other words — we'd be running one huge vulnerability of a system. Not to mention that some rebuild could fail, and suddenly we'd be left with a half-rebuilt system…

    inbox.sourceware.org/libc-alph

    #32bit #y2k38 #security

  18. Dziś jest kolejny z tych dni, w których czytanie dyskusji na temat przekonuje mnie, że miałem rację.

    Znaczy uczestnicy się zgadzają ze mną? Nie, wręcz przeciwnie. Wręcz niepojęte jest dla mnie, jak lekkomyślnie ludzie od Debiana traktuje takie problemy jak nagłą zmianę #ABI. A mowa tu o zmianie wielkości typu `#time_t` z 32 bitów na 64 bity, na 32-bitowych platformach. Po prostu YOLO i zmieniamy, co będzie to będzie…

    A co będzie? Otóż to, że jeżeli mamy jakikolwiek program skompilowany z 32-bitowym time_t, który dowiązany jest do biblioteki eksponującej 64-bitowe time_t w swoim ABI, to nagle cichaczem wszystko się rozjedzie. Znaczy, dostaniemy wszystkie nasze ulubione problemy bezpieczeństwa znane z C — tu się rozjadą argumenty do funkcji, tam będziemy czytać albo pisać po niewłaściwych adresach w pamięci…

    No dobra, #Debian niewątpliwie ma łatwiej niż #Gentoo. Jadą na paczkach binarnych, więc przynajmniej wszystkie systemowe paczki mogą w miarę pewnie zaktualizować w krótkim czasie. W Gentoo z kolei mówimy o godzinach, może nawet dniach, kompilacji. A w tym czasie *systemy produkcyjne* uruchamiałyby programy z potencjalną niezgodnością ABI, a więc praktycznie rzecz biorąc, system stanowiłby jedną wielką dziurę bezpieczeństwa. Nie wspominając o ryzyku, że kompilacja którejś paczki się posypie i nagle zostaniemy z na wpół przebudowanym systemem…

    inbox.sourceware.org/libc-alph

    #32bit #y2k38 #bezpieczeństwo

  19. RE: hostux.social/@fsfstatus/11659

    Note this does not include @gcc.gnu.org but we might consider the same SPF policy if this trail is successful.

  20. @iank As an inanimate infrastructure project for distributed communities I don't live in a specific time zone. All my servers use Coordinated Universal Time (UTC). See you in an hour!

    web.libera.chat/?channel=#over

  21. @iank As an inanimate infrastructure project for distributed communities I don't live in a specific time zone. All my servers use Coordinated Universal Time (UTC). See you in an hour!

    web.libera.chat/?channel=#over

  22. @iank As an inanimate infrastructure project for distributed communities I don't live in a specific time zone. All my servers use Coordinated Universal Time (UTC). See you in an hour!

    web.libera.chat/?channel=#over