https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109684
--- Comment #22 from Tomáš Trnka <trnka at scm dot com> --- (In reply to Steve Kargl from comment #21) > I missed your comment #7 as simply grabbed the "slightly > more simplified" attachment and started a bug hunt from there. > Do either of the other testcase attachments exhibit the issue? Unfortunately, none of the testcases attached to this bug happen to trigger that particular issue. It seems to pop up in many different modules in our codebase, but they are all modules with quite complicated dependency trees, so isolating a small testcase from them is not straigtforward (I need to start from several tens of thousands of SLOC worth of stuff and manually try to reduce it from there, which is tedious at best). That's why I was hoping one of you GCC devs might have an idea of what could possibly be wrong (and some suggestions on what to look at in the gfortran internals or which pieces of code to start playing with). The bad part is that what should just be a warning ends up bringing the compiler down because it hits an assert in the diagnostic printing code. Does expr->where being completely blank sound suspicious? Perhaps something to do with the artificially generated code? The warning is triggered by defined assignment routines, not (directly) by the finalizer. However, it does not occur on GCC 12 or on GCC 13 with the change in comment 4 reverted. It is thus either a preexisting bug uncovered by the fix for this bug or a new one caused by the fix, dunno. That's why I haven't posted it as a separate issue (yet), should I?
