[Bug c++/120377] ICE with fmtlib and modules

2025-05-22 Thread cjangus at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120377

--- Comment #4 from Cameron Angus  ---
Managed to build from source, and indeed the reduced repro is fine, and my own
code is also no longer giving the original ICE that it was. So seems the
underlying issue must have been addressed in the last few days.

I have some other ICEs but they'll need separate reduction so will file new
issues. Feel free to close this, thanks.

[Bug c++/120377] ICE with fmtlib and modules

2025-05-21 Thread cjangus at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120377

--- Comment #3 from Cameron Angus  ---
Just updated to version 16.0.0 20250518 which just came through, but still
seeing the same ICE (error routines re-entered). So will have to wait for the
next one, or if I can work out how maybe I'll try to build from source, since
it seems that would be the best way to avoid wasting time on things that are
already fixed.

[Bug c++/120377] ICE with fmtlib and modules

2025-05-21 Thread cjangus at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120377

--- Comment #2 from Cameron Angus  ---
(In reply to Nathaniel Shead from comment #1)
> Having preprocessed sources makes it a lot easier for me, and I understand
> that there's some concerns about making sure that bugzilla remains as a
> source of truth for the issue even if say godbolt goes down or any of the
> other links rot.  But if you can't do that I'd still prefer having a bug
> over nothing at all :)

Understood, yeah that makes sense. Sometimes those extra couple of steps just
end up being the difference between me posting a bug or it sitting around for a
couple of weeks, that's all. 

> Your attached sources don't reproduce for me on my current build of trunk;
> on GCC15 I get an "error reporting routines re-entered", so it looks like
> something we've possibly already fixed for GCC16.

Hmm, interesting. I'm on the latest build I have access to, but it is a little
over a week old now. I expect a new one will come through soon and I'll test
again. I'm fairly sure I went through at least two distinct issues in the
process of reducing though, so I may just need to tweak things again. The
original ICE I was getting was a segmentation fault, and it changed to the
"error reporting routines re-entered" issue somewhere mid-reduction.

[Bug c++/120377] ICE with fmtlib and modules

2025-05-21 Thread nshead at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120377

Nathaniel Shead  changed:

   What|Removed |Added

 CC||nshead at gcc dot gnu.org

--- Comment #1 from Nathaniel Shead  ---
Thanks for the report!

(In reply to Cameron Angus from comment #0)
> I also created a reproduction on Compiler Explorer, though the precise ICE
> seems to be slightly different due to a difference in GCC and/or fmtlib
> version: https://godbolt.org/z/j1as93bvv

The godbolt is showing a different error due to the flags that CMake has added
for scanning dependencies; I've created PR120379 for this.  (It looks like
there might have been some accidental copy/pasting of module definitions into
the same file, perhaps?)

Your attached sources don't reproduce for me on my current build of trunk; on
GCC15 I get an "error reporting routines re-entered", so it looks like
something we've possibly already fixed for GCC16.

> I'd also like to ask, in future is logging a bug report with a Compiler
> Explorer reproduction only (no preprocessed sources) an option? I'm not a
> regular user of GCC or Linux systems so the process of recreating on CE is
> simpler for me if that is acceptable.

Having preprocessed sources makes it a lot easier for me, and I understand that
there's some concerns about making sure that bugzilla remains as a source of
truth for the issue even if say godbolt goes down or any of the other links
rot.  But if you can't do that I'd still prefer having a bug over nothing at
all :)