Skip to content

Conversation

mborland
Copy link
Member

Got a report on the mailing list that a user hit this configuration error. Checked our links again, and it looks like the bug has finally been fixed in 10/24

@ckormanyos
Copy link
Member

ckormanyos commented Aug 22, 2025

Hi Matt (@mborland)

I think the CI failures are the same ones we just handled in #1306, which has just now been merged to develop

Cc: @NAThompson

@ckormanyos
Copy link
Member

I hopefully just merged the relevant changes in and fired up CI. Let's see if it goes green

@ckormanyos
Copy link
Member

it looks like the bug has finally been fixed in 10/24

Now I see what you mean. That fix took a while. Right on, it's getting better.

@mborland
Copy link
Member Author

@jzmaddock Any chance you can locally test this? There's no runners in CI that have a high enough version of GCC yet.

@ckormanyos
Copy link
Member

image

It looks like pacman for UCRT64 offers GCC 13 at the moment. That's too old right?

I wonder if we could set up a run on Godbolt?

@mborland
Copy link
Member Author

mborland commented Aug 25, 2025

It looks like pacman for UCRT64 offers GCC 13 at the moment. That's too old right?

Yes. We have GCC 14 in CI where this was still an issue. Since the bug was patched in 10/24 it should have shipped with GCC 15 in 4/25

I wonder if we could set up a run on Godbolt?

Godbolt only has up to GCC 13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants