[Octave-bug-tracker] [bug #61472] AddressSanitizer crash in MEX tests

[Markus Mützel]

Follow-up Comment #48, bug #61472 (project octave):

> But is that necessary for our Windows builds since we are building with GCC
11 now?  Can't we just build everything with the (now default) C++17 mode and
use the std::pmr::... allocator code?

I was thinking about this, too. See the last question in comment #38.
But in general we don't know whether it is ok to ignore/override if a package
is setting a specific standard version (e.g. `-std=c++11`) in their build
rules. That could be because they'd like to use features that weren't
available in prior versions. But it could also be because their code wouldn't
compile in C++ versions newer than the set one...
So, if we'd want to compile everything with C++17, we'd need to raise the
minimum C++ version for packages to C++17. (Or I didn't understand your
proposition.)
If we'd like to do that, we should probably give package developers a prior
note and the chance to adapt their package to the new requirements.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61472>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/