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
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 _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
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
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644
Alberto Luaces changed:
What|Removed |Added
CC||aluaces at udc dot es
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97245
Bug ID: 97245
Summary: ASSOCIATE intrinsic does not recognize a ponter
variable the second time it is used
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
