-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilation problem on GCC 14.1 (Linux) #429
Comments
I see that with gcc 14.1 in the tests. I doubt it is your code. Looking into it |
Interesting that with the same libstdc++, gcc 14.1 fails this and clang does not. But the type definitely is complete as it is checking |
I found this : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100381 does it
help?
…On Mon, Jul 1, 2024 at 7:16 AM Darrell Wright ***@***.***> wrote:
Interesting that with the same libstdc++, gcc 14.1 fails this and clang
does not. But the type definitely is complete as it is checking std::is_nothrow_copy_constructible<char
const *>::value
—
Reply to this email directly, view it on GitHub
<#429 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB4N35BWXI4XO5RHZDDXSDZKDQ3XAVCNFSM6AAAAABKD74RH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJZGI2TIOBTGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Same thing catching, but how can a |
I have a fix in the utf-range repo that will work around this. I am thinking it is a compiler issue but could not replicate a small example. changing the |
Workaround for gcc14.1 issue in daw_json_link beached/daw_json_link#429
This should be fixed now |
Thanks! |
Hey after upgrade to GCC 14.1 I get:
If I change (remove stuff after noexcept) in
build/_deps/daw_utf_range-src/include/daw/utf8/unchecked.h
:to:
then everything gets back to normal. Dunno if that's something on my side or on library's - any ideas? Thanks!
The text was updated successfully, but these errors were encountered: