[ruby-core:116117] [Ruby master Misc#20170] Drop support for GCC < 11
Issue #20170 has been reported by kddnewton (Kevin Newton). ---------------------------------------- Misc #20170: Drop support for GCC < 11 https://bugs.ruby-lang.org/issues/20170 * Author: kddnewton (Kevin Newton) * Status: Open * Priority: Normal ---------------------------------------- Right now, CI compiles everything from GCC 7+. However, GCC 7-10 are all end-of-life and no longer supported. We should drop support for the end-of-life compilers. -- https://bugs.ruby-lang.org/
Issue #20170 has been updated by kddnewton (Kevin Newton). (For added context: https://gcc.gnu.org/gcc-10/) ---------------------------------------- Misc #20170: Drop support for GCC < 11 https://bugs.ruby-lang.org/issues/20170#change-106116 * Author: kddnewton (Kevin Newton) * Status: Open * Priority: Normal ---------------------------------------- Right now, CI compiles everything from GCC 7+. However, GCC 7-10 are all end-of-life and no longer supported. We should drop support for the end-of-life compilers. -- https://bugs.ruby-lang.org/
Issue #20170 has been updated by jeremyevans0 (Jeremy Evans). OpenBSD/sparc64 (and maybe some other OpenBSD arches) build Ruby using GCC 8.4 (as Clang/LLVM sparc64 support isn't mature enough yet). So if possible, I would prefer to not drop support for GCC 8.4 yet. ---------------------------------------- Misc #20170: Drop support for GCC < 11 https://bugs.ruby-lang.org/issues/20170#change-106121 * Author: kddnewton (Kevin Newton) * Status: Open * Priority: Normal ---------------------------------------- Right now, CI compiles everything from GCC 7+. However, GCC 7-10 are all end-of-life and no longer supported. We should drop support for the end-of-life compilers. -- https://bugs.ruby-lang.org/
Issue #20170 has been updated by mame (Yusuke Endoh). In regard of compilers, we should look at not only the maintenance status of the upstream but also the one of major package distributions. I have investigated some distributions with long maintenance periods: * RHEL8 (maintenance support until May 31, 2029) provides gcc 8.5 * Amazon Linux 2 (maintenance support until Jun 30, 2025) provides gcc 7.3 Of course we are not obliged to support them until they stop supporting them. However, it is also true that it can be troublesome for users of those distributions. I think we need a good reason to drop them. Could you share a context in which you want to drop support? You want to use a new GCC feature, or you are facing on some actual maintenance issue? ---------------------------------------- Misc #20170: Drop support for GCC < 11 https://bugs.ruby-lang.org/issues/20170#change-106132 * Author: kddnewton (Kevin Newton) * Status: Open * Priority: Normal ---------------------------------------- Right now, CI compiles everything from GCC 7+. However, GCC 7-10 are all end-of-life and no longer supported. We should drop support for the end-of-life compilers. -- https://bugs.ruby-lang.org/
Issue #20170 has been updated by rubyFeedback (robert heiler). As jeremy pointed out, one potential drawback for dropping support for older GCC may be that ruby could not be compiled on certain platforms anymore. Personally I think the more platforms (and compilers) for ruby to run on, the better, if the maintenance burden does not outweigh support for such platforms. Even if the actual user base is rather small, I agree with jeremy from a principle point of view. (I myself compile everything from source on my Linux system, with the help of ruby scripts, so I am running GCC 13.2.0 just fine, but I remember having had issues in the past with an old CentOS system in a restricted university-campus setting, and I also once wanted to have HaikuOS work with ruby but eventually gave up on it. So I think I can relate to jeremy's point of view.) ---------------------------------------- Misc #20170: Drop support for GCC < 11 https://bugs.ruby-lang.org/issues/20170#change-106137 * Author: kddnewton (Kevin Newton) * Status: Open * Priority: Normal ---------------------------------------- Right now, CI compiles everything from GCC 7+. However, GCC 7-10 are all end-of-life and no longer supported. We should drop support for the end-of-life compilers. -- https://bugs.ruby-lang.org/
Issue #20170 has been updated by kddnewton (Kevin Newton). Status changed from Open to Closed I'm okay to wait on this. My main reason is one day I would love to use C11 features, particularly _Generic, aligned_alloc, and static_assert. I assume/hope we will get there someday. ---------------------------------------- Misc #20170: Drop support for GCC < 11 https://bugs.ruby-lang.org/issues/20170#change-108734 * Author: kddnewton (Kevin Newton) * Status: Closed ---------------------------------------- Right now, CI compiles everything from GCC 7+. However, GCC 7-10 are all end-of-life and no longer supported. We should drop support for the end-of-life compilers. -- https://bugs.ruby-lang.org/
participants (4)
-
jeremyevans0 (Jeremy Evans) -
kddnewton (Kevin Newton)
-
mame (Yusuke Endoh)
-
rubyFeedback (robert heiler)