-
Notifications
You must be signed in to change notification settings - Fork 1k
[bug]: app_sms: Compilation failure in DEVMODE due to stringop-overflow error in GCC 15 pre-release #1088
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
Comments
Ignore gcc warning about writing 32 bytes into a region of size 6, since we check that we don't go out of bounds for each byte. Resolves: asterisk#1088
Does putting an explicit cast there work? I don't know where it is getting 32 bytes from,
|
Nope.
|
Just my 2 cents but I’d wait for gcc 15 to be released. This seems like a compiler bug. |
Ignore gcc warning about writing 32 bytes into a region of size 6, since we check that we don't go out of bounds for each byte. This is due to a vectorization bug in gcc 15. Resolves: asterisk#1088
GCC 15.1 is released and this still manifests. |
Thanks for verifying... I never got around to filing a bug but more impetus to do it now... Edit: Looks like I already did that, so should be good to go.... |
Ignore gcc warning about writing 32 bytes into a region of size 6, since we check that we don't go out of bounds for each byte. This is due to a vectorization bug in gcc 15. Resolves: asterisk#1088
Severity
Major
Versions
22.2.0-rc1
Components/Modules
app_sms
Operating Environment
Fedora 42
Frequency of Occurrence
Constant
Issue Description
gcc 15 warning about possible writing beyond bounds of a buffer.
Looks like a false positive to me since there is a check for each byte if the end of the buffer has been reached, and the bounds are correct, but it's possible I've missed something...
Relevant log output
Asterisk Issue Guidelines
The text was updated successfully, but these errors were encountered: