Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#58394 - [gcc-fortran] Internal error in gnu fortran
Attached to Project:
Arch Linux
Opened by Daniel Bershatsky (daskol) - Sunday, 29 April 2018, 16:56 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Friday, 01 June 2018, 09:08 GMT
Opened by Daniel Bershatsky (daskol) - Sunday, 29 April 2018, 16:56 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Friday, 01 June 2018, 09:08 GMT
|
DetailsGNU Fortran fails to compile source. I am trying to compile tt-fort project. Actually this issue repeats in several last releases. It forces me to use ifort instead of gfortran that is not desired.
Additional info: * core/gcc 7.3.1+20180406-1 * core/gcc-libs 7.3.1+20180406-1 * core/gcc-fortran 7.3.1+20180406-1 * verbose gfortran output in attachment Steps to reproduce: 1. Clone https://github.com/oseledets/tt-fort 2. Setup Makefile.cpu 3. Run make 4. In my case fortran fails on dispmodule.f90 |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Friday, 01 June 2018, 09:08 GMT
Reason for closing: Upstream
Friday, 01 June 2018, 09:08 GMT
Reason for closing: Upstream
Comment by Daniel Bershatsky (daskol) -
Thursday, 10 May 2018, 17:06 GMT
The issue is reproducible with GNU Fortran (GCC) 8.1.0.
Comment by Bartłomiej Piotrowski (Barthalion) -
Friday, 01 June 2018, 09:08 GMT
Seems to be upstream issue. I don't see any similar report so please bring it there. (Or ping me somewhere if you want me to do it.)
gfortran.log