Menu

#146 Any plans for support for latest GCC version 9, released 3 May 2019?

v1.0 (example)
open
nobody
None
5
2020-02-10
2019-06-03
No

Any plans for support for GCC 9, released 3 May 2019?

It would be very useful to have the latest and greatest GCC C/C++ compiler supported.

Is there any impediment to producing this?

Thank you.

Related

Support Requests: #146

Discussion

  • Zufu Liu

    Zufu Liu - 2019-06-03

    GCC 9.1 is already in MYSY2:

    pacman -S[w] mingw-w64-x86_64-gcc mingw-w64-x86_64-gdb mingw-w64-x86_64-make mingw-w64-x86_64-tools-git mingw-w64-x86_64-gcc-fortran mingw-w64-x86_64-gcc-libs
    
     
    • Sergey Lebedkin

      Sergey Lebedkin - 2019-06-05

      Thanx! But when we will see standalone builds?

       
      • Brecht Sanders

        Brecht Sanders - 2019-11-11

        I just released my personal build of MinGW-w64 7.0.0 with GCC 9.2 here: http://winlibs.com/

         
        • Pavlos Gkesos

          Pavlos Gkesos - 2020-02-10

          I love you.
          I remove all of these links from my bookmarks and I place yours.

           

          Last edit: Pavlos Gkesos 2020-02-10
  • Paul A Bristow

    Paul A Bristow - 2019-11-29

    I have now got to load this and confirm that it works as promised with current Codeblocks release on Windows 10.

    Brilliant - meets my needs for the most uptodate versions tracking the C++2a/20 standards, with constexpr additions. Many thanks Brecht Sanders. I ho e you will be able to release other versions as they become available. (I'm sure that the compiler writers are working on version 10!)

     
    • Brecht Sanders

      Brecht Sanders - 2019-11-29

      That's great news.
      I use it myself in Code::Blocks on Windows.
      GCC development on version 10 is in progress, and I'm constantly keeping an eye out for new releases.

       
      • Paul A Bristow

        Paul A Bristow - 2019-12-04

        I note that this version is posix-dwarf

        GNU C++17 (MinGW-W64 x86_64-posix-dwarf, built by Brecht Sanders) version 9.2.0
        (x86_64-w64-mingw32)

        compiled by GNU C version 9.2.0, GMP version 6.1.2, MPFR version 4.0.2, MPC
        version 1.1.0, isl version isl-0.22-GMP

        Previously I have used the version that is at

        "C:\Program Files\mingw-w64\x86_64-8.1.0-win32-seh-rt_v6-rev0\mingw64"

        On that release there is an installer that gives you options for which variant
        you want.

        For Arch: x86_64, Threads: win32 and Exceptions: she

        I'm not sure of the implications of this being different, but I'd prefer not to
        have another variable if possible.

        Thanks.

        PS I have many projects rebuilding, but some failures at runtime failing dynamic
        link to the basic_stringstream traits. Are these related?

        From: Brecht Sanders brechtsanders@users.sourceforge.net
        Sent: 29 November 2019 12:21
        To: [mingw-w64:support-requests]
        146@support-requests.mingw-w64.p.re.sourceforge.net
        Subject: [mingw-w64:support-requests] Re: #146 Any plans for support for latest
        GCC version 9, released 3 May 2019?

        That's great news.
        I use it myself in Code::Blocks on Windows.
        GCC development on version 10 is in progress, and I'm constantly keeping an eye
        out for new releases.


        [support-requests:#146]
        https://sourceforge.net/p/mingw-w64/support-requests/146/ Any plans for
        support for latest GCC version 9, released 3 May 2019?

        Status: open
        Group: v1.0 (example)
        Created: Mon Jun 03, 2019 01:47 PM UTC by Paul A Bristow
        Last Updated: Fri Nov 29, 2019 12:03 PM UTC
        Owner: nobody

        Any plans for support for GCC 9, released 3 May 2019?

        It would be very useful to have the latest and greatest GCC C/C++ compiler
        supported.

        Is there any impediment to producing this?

        Thank you.


        Sent from sourceforge.net because you indicated interest in
        https://sourceforge.net/p/mingw-w64/support-requests/146/

        To unsubscribe from further messages, please visit
        https://sourceforge.net/auth/subscriptions/

         

        Related

        Support Requests: #146

        • Brecht Sanders

          Brecht Sanders - 2019-12-08

          I chose to avoid SEH on the basis that it imposes a larger performance overhead.

          The POSIX threading was chosen over WIN32 because the C++ thread implementation is less compatible with and causes certain packages not to build properly.

          My goal was to have te most optimal and portable solution, so I didn't built the alternatives.

          About your basic_stringstream errors: note that the ABI changed, so linking stuff compiled with different GCC versions is likely to cause such problems.
          Personally I rebuild my entire collection of libraries whenever a new compiler is released.

           

Log in to post a comment.