Announcement

Collapse
No announcement yet.

GCC 11 Compiler Could End Up Removing Support For The Motorola m68k, Other Old CPUs

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • GCC 11 Compiler Could End Up Removing Support For The Motorola m68k, Other Old CPUs

    Phoronix: GCC 11 Compiler Could End Up Removing Support For The Motorola m68k, Other Old CPUs

    Deprecated for the upcoming GCC 10 compiler release and set for removal in GCC 11 one year later is the CC0 representation code that is being used for handle condition codes in GCC back-ends. That in turn means a number of older CPU targets will be removed in GCC 11 should they not receive some development attention to transition them to the modern MODE_CC representation...

    http://www.phoronix.com/scan.php?pag...1-Dropping-CC0

  • #2
    Did they just deprecate the AVR backend used by popular hobbyist boards?
    Last edited by GrayShade; 10-30-2019, 07:53 AM.

    Comment


    • #3
      So they are saying that support for compiling on the Atari ST, Amiga and first gen Macs will be removed? This is a outrage!!!!!!1!


      /S
      Last edited by [email protected]; 10-30-2019, 09:51 AM. Reason: whoooooosh

      Comment


      • #4
        Originally posted by [email protected] View Post
        So they are saying that support for compiling on the Atari ST, Amiga and first gen Macs will be removed? This is a outrage!!!!!!1!
        If nobody maintains that code path to keep it up to modern standards, not doing so would be silly. If nobody steps up to keep m68k support code up to current requirements, they should remove it, as it's nothing but legacy baggage. Feel free to use an older version, fork it, or try to ensure m68k is properly supported.

        Comment


        • #5
          Originally posted by [email protected] View Post
          So they are saying that support for compiling on the Atari ST, Amiga and first gen Macs will be removed? This is a outrage!!!!!!1!
          If you had bothered reading the mailing list discussion, you would have seen that Jeff Law - one of the GCC main developers - has already said that he is going to pick up the task together with his son next year.

          Comment


          • #6
            Originally posted by DoMiNeLa10 View Post

            If nobody maintains that code path to keep it up to modern standards, not doing so would be silly. If nobody steps up to keep m68k support code up to current requirements, they should remove it, as it's nothing but legacy baggage. Feel free to use an older version, fork it, or try to ensure m68k is properly supported.
            Read the mailing list discussion. People are actually stepping up to do that. Jeff Law has announced he would do it next year and he is basically the one who has the last word on this.

            Comment


            • #7
              Originally posted by DoMiNeLa10 View Post

              If nobody maintains that code path to keep it up to modern standards, not doing so would be silly. If nobody steps up to keep m68k support code up to current requirements, they should remove it, as it's nothing but legacy baggage. Feel free to use an older version, fork it, or try to ensure m68k is properly supported.
              you don't do sarcasm, do you

              Comment


              • #8
                Originally posted by GrayShade View Post
                Did they just deprecate the AVR backend used by popular hobbyist boards?
                I guess GCC doesn't want to be used. They've been removing support for a lot of stuff recently. First Cell SPU, now AVR, and next m68k.

                Comment


                • #9
                  Originally posted by rmoog View Post
                  I guess GCC doesn't want to be used. They've been removing support for a lot of stuff recently. First Cell SPU, now AVR, and next m68k.
                  TBH, nobody is going to upgrade to GCC 11 for their XBox 360 or whatever. Most embedded projects use known-good toolchains from ages ago. Arduino has what, GCC 5.4? On SPARC platforms, GCC 3.4 is still going strong.

                  Comment


                  • #10
                    I bet that Microchip will step up and update that AVR backend as the MCU manufacturer. Just give them time to react. Unless they want to drop AVRs (they did drop a lot of MCUs when acquiring Atmel). Or the community will do it themselves.

                    Comment

                    Working...
                    X