We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
crunch/inc/crn_defs.h: warning #175: subscript out of range
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
I get this when building the Damon engine with ICC:
crunch/inc/crn_defs.h(236): warning #175: subscript out of range return (m_buf[0] << 24U) | (m_buf[1] << 16U) | (m_buf[2] << 8U) | (m_buf[3]); ^ detected during instantiation of "crnd::crn_packed_uint<N>::operator unsigned int() const [with N=3U]" at line 2242 of "crunch/inc/crn_decomp.h" crunch/inc/crn_defs.h(234): warning #175: subscript out of range return (m_buf[0] << 16U) | (m_buf[1] << 8U) | (m_buf[2]); ^ detected during instantiation of "crnd::crn_packed_uint<N>::operator unsigned int() const [with N=2U]" at line 2198 of "crunch/inc/crn_decomp.h" crunch/inc/crn_defs.h(236): warning #175: subscript out of range return (m_buf[0] << 24U) | (m_buf[1] << 16U) | (m_buf[2] << 8U) | (m_buf[3]); ^ detected during instantiation of "crnd::crn_packed_uint<N>::operator unsigned int() const [with N=2U]" at line 2198 of "crunch/inc/crn_decomp.h" crunch/inc/crn_defs.h(236): warning #175: subscript out of range return (m_buf[0] << 24U) | (m_buf[1] << 16U) | (m_buf[2] << 8U) | (m_buf[3]); ^ detected during instantiation of "crnd::crn_packed_uint<N>::operator unsigned int() const [with N=2U]" at line 2198 of "crunch/inc/crn_decomp.h"
The text was updated successfully, but these errors were encountered:
It looks to be the same problem CodeQL was reporting:
The following cpp/static-buffer-overflow critical error is dismissed as it is a false positive: Potential buffer-overflow: 'm_buf' has size 2 but 'm_buf[3]' may be accessed here. It is a false positive because the tool fails to understand that the value tested for the switch case is the array size itself.
The following cpp/static-buffer-overflow critical error is dismissed as it is a false positive:
Potential buffer-overflow: 'm_buf' has size 2 but 'm_buf[3]' may be accessed here.
It is a false positive because the tool fails to understand that the value tested for the switch case is the array size itself.
See: #60 (comment)
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
I get this when building the Damon engine with ICC:
The text was updated successfully, but these errors were encountered: