https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644
--- Comment #24 from Alberto Luaces ---
Hi, I am not a gfortran developer nor I am asking for a minimal working example
whatsoever.
I was just stating that the problem could have disappeared, and I tried just
building your whole software (succe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644
--- Comment #22 from Alberto Luaces ---
Kyle, can you try again on your side?
Following your instructions on 2024/03/08, I checked out tuv-x version from
2024/03/04 and compiled it without problems, using gfortran 14.2.0.
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: aluaces at udc dot es
Target Milestone: ---
This happens either with functions or subroutines. Both minimal cases are
attached:
--Example 1
PROGRAM MAIN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644
--- Comment #12 from Alberto Luaces ---
It seems to be slightly different:
(gdb) p expr->ts.type
$7 = BT_PROCEDURE
(gdb) p expr->symtree->name
$8 = 0x770244e8 "@1179"
(gdb) p expr->where
$9 = {nextc = 0x0, lb = 0x0}
Maybe it will be clear
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644
--- Comment #10 from Alberto Luaces ---
Ok, indeed they were some warnings. I had to use &gfc_current_locus, as you
suggested, so now all of them are pointed at the end of the file.
Yes, I am using OOP: we have a "states" class that has its as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644
--- Comment #8 from Alberto Luaces ---
No, I meant building *gcc* with those flags, but alas each gcc compilation
stage was still building with "-O2" so almost all of the compiler structures
are still optimized.
Nevertheless I did what you sugg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644
--- Comment #6 from Alberto Luaces ---
Thanks a lot for the guidance. This is the backtrace of the last call to
gcc_assert() that makes it crash.
It says something about a non-recursive function likely calling itself. I will
inspect my source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644
Alberto Luaces changed:
What|Removed |Added
CC||aluaces at udc dot es
--- Comment #4
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: aluaces at udc dot es
Target Milestone: ---
Created attachment 49289
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49289&action=edit
Minimal
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: aluaces at udc dot es
Target Milestone: ---
The submodule
module Foo_mod
interface
module subroutine runFoo4C(ndim) bind(C, name="runFoo")
use, intrinsic :: iso_c_binding
imp
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: aluaces at udc dot es
Target Milestone: ---
I get the error
test_bug.f90:19:16:
INTENT(IN) b
1
Error: INTENT (IN) conflicts with INTENT(IN
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: aluaces at udc dot es
Target Milestone: ---
Created attachment 42504
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42504&action=edit
Minimal test example with Makefile
The attached test example trig
12 matches
Mail list logo
