[ruby-core:88571] [Ruby trunk Misc#15012] Testing on latest version gcc on Travis CI

[ruby-core:88571] [Ruby trunk Misc#15012] Testing on latest version gcc on Travis CI

[jaruga]

Issue #15012 has been reported by jaruga (Jun Aruga).

----------------------------------------
Misc #15012: Testing on latest version gcc on Travis CI
https://bugs.ruby-lang.org/issues/15012

* Author: jaruga (Jun Aruga)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Ruby's Travis CI [1] is running on gcc 4.8.4 as the default behavior of Travis gcc setting.
Right now gcc's latest version is 8.
Though it is important to test on the old version gcc-4.8, also it is meaningful to test on the latest version gcc, knowing we have RubyCI. [2]

The benefit to run on gcc-8 is
* We can care the issue on the latest version of gcc easier, such as visualizing the build warnings on the log.
* We can show contributors or developers how ruby could be built on the latest version gcc.

I sent the pull-request [3] to show the code as a proposal.

[1] https://travis-ci.org/ruby/ruby
[2] https://rubyci.org/
[3] https://github.com/ruby/ruby/pull/1937




-- 
https://bugs.ruby-lang.org/

[ruby-core:88572] [Ruby trunk Misc#15012] Testing on latest version gcc on Travis CI

[jaruga]

Issue #15012 has been updated by jaruga (Jun Aruga).


The demerit is 

* The Travis test running time could be longer than current one. But maybe not so long time because those test cases are run in parallel.
* I am not sure whether the "ppa:ubuntu-toolchain-r/test" repository [1] shown on the Travis document [2] is stable.

[1] https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test
[2] https://docs.travis-ci.com/user/installing-dependencies/#installing-packages-from-a-custom-apt-repository

----------------------------------------
Misc #15012: Testing on latest version gcc on Travis CI
https://bugs.ruby-lang.org/issues/15012#change-73628

* Author: jaruga (Jun Aruga)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Ruby's Travis CI [1] is running on gcc 4.8.4 as the default behavior of Travis gcc setting.
Right now gcc's latest version is 8.
Though it is important to test on the old version gcc-4.8, also it is meaningful to test on the latest version gcc, knowing we have RubyCI. [2]

The benefit to run on gcc-8 is
* We can care the issue on the latest version of gcc easier, such as visualizing the build warnings on the log.
* We can show contributors or developers how ruby could be built on the latest version gcc.

I sent the pull-request [3] to show the code as a proposal.

[1] https://travis-ci.org/ruby/ruby
[2] https://rubyci.org/
[3] https://github.com/ruby/ruby/pull/1937




-- 
https://bugs.ruby-lang.org/

[ruby-core:88573] [Ruby trunk Misc#15012] Testing on latest version gcc on Travis CI

[jaruga]

Issue #15012 has been updated by jaruga (Jun Aruga).


If you want to imagine how gcc-N and clang test cases work on both linux and osx of Travis CI, I can share this project's case.

https://travis-ci.org/trinityrnaseq/trinityrnaseq
https://github.com/trinityrnaseq/trinityrnaseq/blob/master/.travis.yml


----------------------------------------
Misc #15012: Testing on latest version gcc on Travis CI
https://bugs.ruby-lang.org/issues/15012#change-73629

* Author: jaruga (Jun Aruga)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Ruby's Travis CI [1] is running on gcc 4.8.4 as the default behavior of Travis gcc setting.
Right now gcc's latest version is 8.
Though it is important to test on the old version gcc-4.8, also it is meaningful to test on the latest version gcc, knowing we have RubyCI. [2]

The benefit to run on gcc-8 is
* We can care the issue on the latest version of gcc easier, such as visualizing the build warnings on the log.
* We can show contributors or developers how ruby could be built on the latest version gcc.

I sent the pull-request [3] to show the code as a proposal.

[1] https://travis-ci.org/ruby/ruby
[2] https://rubyci.org/
[3] https://github.com/ruby/ruby/pull/1937




-- 
https://bugs.ruby-lang.org/

[ruby-core:88583] [Ruby trunk Misc#15012] Testing on latest version gcc on Travis CI

[Greg.mpls]

Issue #15012 has been updated by MSP-Greg (Greg L).


Given that Appveyor/Windows MSYS2/MinGW also has gcc 8.2.0 available (ruby-loco uses it), seems like a good idea to me.  One would hope that newer gcc releases are also better optimized for JIT...

Off topic - about Appveyor testing - MSYS2/MinGW - `mingw-w64-x86_64-toolchain` is gcc.  There is also a `base-devel` group.  ruby-loco updates both, but toolchain is probably all that is required...

----------------------------------------
Misc #15012: Testing on latest version gcc on Travis CI
https://bugs.ruby-lang.org/issues/15012#change-73639

* Author: jaruga (Jun Aruga)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Ruby's Travis CI [1] is running on gcc 4.8.4 as the default behavior of Travis gcc setting.
Right now gcc's latest version is 8.
Though it is important to test on the old version gcc-4.8, also it is meaningful to test on the latest version gcc, knowing we have RubyCI. [2]

The benefit to run on gcc-8 is
* We can care the issue on the latest version of gcc easier, such as visualizing the build warnings on the log.
* We can show contributors or developers how ruby could be built on the latest version gcc.

I sent the pull-request [3] to show the code as a proposal.

[1] https://travis-ci.org/ruby/ruby
[2] https://rubyci.org/
[3] https://github.com/ruby/ruby/pull/1937




-- 
https://bugs.ruby-lang.org/

[ruby-core:88590] [Ruby trunk Misc#15012] Testing on latest version gcc on Travis CI

[jaruga]

Issue #15012 has been updated by jaruga (Jun Aruga).


> Given that Appveyor/Windows MSYS2/MinGW also has gcc 8.2.0 available (ruby-loco uses it), seems like a good idea to me. One would hope that newer gcc releases are also better optimized for JIT...

It looks good idea to add gcc 8 on the Windows environment too.
But I need someone's help for that, as I am not familiar with it.
I can work for Travis osx case if it is needed.


----------------------------------------
Misc #15012: Testing on latest version gcc on Travis CI
https://bugs.ruby-lang.org/issues/15012#change-73648

* Author: jaruga (Jun Aruga)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Ruby's Travis CI [1] is running on gcc 4.8.4 as the default behavior of Travis gcc setting.
Right now gcc's latest version is 8.
Though it is important to test on the old version gcc-4.8, also it is meaningful to test on the latest version gcc, knowing we have RubyCI. [2]

The benefit to run on gcc-8 is
* We can care the issue on the latest version of gcc easier, such as visualizing the build warnings on the log.
* We can show contributors or developers how ruby could be built on the latest version gcc.

I sent the pull-request [3] to show the code as a proposal.

[1] https://travis-ci.org/ruby/ruby
[2] https://rubyci.org/
[3] https://github.com/ruby/ruby/pull/1937




-- 
https://bugs.ruby-lang.org/

[ruby-core:88595] [Ruby trunk Misc#15012] Testing on latest version gcc on Travis CI

[Greg.mpls]

Issue #15012 has been updated by MSP-Greg (Greg L).


@jaruga,

Sorry I my message was unclear.  For quite some time, Ruby trunk has been built on Appveyor using the MSFT VC compiler (mswin).  Sometime last year, full testing was added to that build.

In the wild, most Windows Ruby users make use of builds based on MinGW based compilers.  Older builds used MSYS/MinGW, newer builds use MSYS2/MinGW.  These are often referred to as RubyInstaller buils (the newer ones are technically RubyInstaller2).


----------------------------------------
Misc #15012: Testing on latest version gcc on Travis CI
https://bugs.ruby-lang.org/issues/15012#change-73651

* Author: jaruga (Jun Aruga)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Ruby's Travis CI [1] is running on gcc 4.8.4 as the default behavior of Travis gcc setting.
Right now gcc's latest version is 8.
Though it is important to test on the old version gcc-4.8, also it is meaningful to test on the latest version gcc, knowing we have RubyCI. [2]

The benefit to run on gcc-8 is
* We can care the issue on the latest version of gcc easier, such as visualizing the build warnings on the log.
* We can show contributors or developers how ruby could be built on the latest version gcc.

I sent the pull-request [3] to show the code as a proposal.

[1] https://travis-ci.org/ruby/ruby
[2] https://rubyci.org/
[3] https://github.com/ruby/ruby/pull/1937




-- 
https://bugs.ruby-lang.org/

[ruby-core:88607] [Ruby trunk Misc#15012] Testing on latest version gcc on Travis CI

[jaruga]

Issue #15012 has been updated by jaruga (Jun Aruga).


Hi Greg,

> Sorry, my message was unclear. 

No problem at all. Thanks for the explanation to be cleared.

> the CI is now testing both mswin and mingw builds.

So, adding gcc-8 to the both environments makes sense for me.


What I want to share as one of the benefits is

* It is beneficial for people who are maintaining the Debian or RPM package of Ruby or gem packages on Debian or Fedora project like me. :) The latest version gcc is actively used as a main compiler on Fedora project.



----------------------------------------
Misc #15012: Testing on latest version gcc on Travis CI
https://bugs.ruby-lang.org/issues/15012#change-73663

* Author: jaruga (Jun Aruga)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Ruby's Travis CI [1] is running on gcc 4.8.4 as the default behavior of Travis gcc setting.
Right now gcc's latest version is 8.
Though it is important to test on the old version gcc-4.8, also it is meaningful to test on the latest version gcc, knowing we have RubyCI. [2]

The benefit to run on gcc-8 is
* We can care the issue on the latest version of gcc easier, such as visualizing the build warnings on the log.
* We can show contributors or developers how ruby could be built on the latest version gcc.

I sent the pull-request [3] to show the code as a proposal.

[1] https://travis-ci.org/ruby/ruby
[2] https://rubyci.org/
[3] https://github.com/ruby/ruby/pull/1937




-- 
https://bugs.ruby-lang.org/

[ruby-core:89034] [Ruby trunk Misc#15012] Testing on latest version gcc on Travis CI

[happy]

Issue #15012 has been updated by junaruga (Jun Aruga).


I just noticed the environment variables line for gcc-8 test case on `.travis.yml` are removed by the great hack in `configure.ac`.

That's amazing!
Thank you for the improvement.

https://github.com/ruby/ruby/commit/f677ba8

```
$ git show f677ba887158758c48b4f8e1df092c6aacfe6621
...
-      env:
-        - CC=gcc-8 AR=gcc-ar-8 NM=gcc-nm-8 RANLIB=gcc-ranlib-8
...
```


----------------------------------------
Misc #15012: Testing on latest version gcc on Travis CI
https://bugs.ruby-lang.org/issues/15012#change-74058

* Author: jaruga (Jun Aruga)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Ruby's Travis CI [1] is running on gcc 4.8.4 as the default behavior of Travis gcc setting.
Right now gcc's latest version is 8.
Though it is important to test on the old version gcc-4.8, also it is meaningful to test on the latest version gcc, knowing we have RubyCI. [2]

The benefit to run on gcc-8 is
* We can care the issue on the latest version of gcc easier, such as visualizing the build warnings on the log.
* We can show contributors or developers how ruby could be built on the latest version gcc.

I sent the pull-request [3] to show the code as a proposal.

[1] https://travis-ci.org/ruby/ruby
[2] https://rubyci.org/
[3] https://github.com/ruby/ruby/pull/1937




-- 
https://bugs.ruby-lang.org/