You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is something we should be worried about or not, but when linking the current GIT version (and for a few weeks now) on Manjaro (Stable branch) I get a lot of warnings similar to this:
In member function ‘InitSize’,
inlined from ‘__ct_base .constprop’ at /data/software/AUR/gnudatalanguage-git/src/gnudatalanguage-git/src/envt.cpp:321:23:
/data/software/AUR/gnudatalanguage-git/src/gnudatalanguage-git/src/envt.hpp:408:12: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size 9223372036854775807 [-Walloc-size-larger-than=]
408 | eArr = new T[ s]; // constructor called
| ^
/usr/include/c++/14.2.1/new: In member function ‘__ct_base .constprop’:
/usr/include/c++/14.2.1/new:133:26: note: in a call to allocation function ‘operator new []’ declared here
133 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
|
while I haven't seen any adverse consequences, I thought it might be worth raising a flag.
The text was updated successfully, but these errors were encountered:
I'm not sure if this is something we should be worried about or not, but when linking the current GIT version (and for a few weeks now) on Manjaro (Stable branch) I get a lot of warnings similar to this:
while I haven't seen any adverse consequences, I thought it might be worth raising a flag.
The text was updated successfully, but these errors were encountered: