octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #61472] AddressSanitizer crash in MEX tests
Date: Wed, 22 Dec 2021 10:10:06 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.110 Safari/537.36 Edg/96.0.1054.62

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

IIUC, the issue that prevented packages to compile with C++11 if Octave was
compiled with the new C++17 feature is the following:

If Octave was compiled with the new feature,
OCTAVE_DISABLE_STD_PMR_POLYMORPHIC_ALLOCATOR is defined to 1. In that case,
the headers use the new C++17 feature.
If a package sets compiler flags to use (only) C++11 features and includes
those headers, the compiler complains (rightfully so).

I'm not sure if your proposed solution will work. 
If Octave was compiled with the new feature, it will export functions that
expect Array<T, std::pmr::polymorphic_allocator<T>> types as arguments. 
If a packages sets e.g. `-std=c++11`, the headers will define functions that
expect Array<T, std::allocator<T>> types as arguments. 
Will that work without issues? It might be worth a try...

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]