-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
"-fno-inline" may cause miscompile / segmentation fault #2743
Comments
I think we'll need a repro for this. |
I will keep trying to create one but up until now I can only get this in non-public production code. But I have a gut feeling this may be somewhere / somehow related to #2357. |
The effects are similar to that of an ODR violation but I'm not sure why it would be caused by |
BTW #2357 has been fixed so if you think this is related you might want to check the latest master. |
Hm... that may take some time b/c master breaks constructs like If that is intentional, then I will have to tackle that problem before the next fmt-version is released anyway... |
Closing as this is not actionable right now but feel free to reopen with repro details.
It is. |
I am currently debugging a segmentation fault seemingly caused by passing "-fno-inline" to gcc. At the moment I am not able to give a minimal working example which is able to show the phenomenon and I cannot post the original code which causes the problem in question, so I will try to give as much information as possible.
The crashing code is question is a code block like
This results in a segmentation fault with a backtrace (sanitized):
gcc-11.2.0 with fmt-8.0.1 and fmt-8.1.1 were tested (header-only).
gcc options used: -std=c++17 -ggdb3 -Og -fvar-tracking-assignments
The text was updated successfully, but these errors were encountered: