- Dec 24, 2024
- Dec 23, 2024
- Dec 22, 2024
-
-
rdubner authored
Ordinary .cc files have their prerequisite .h files calculated and stored in build/gcc/cobol/.deps as part of the ordinary build. But those three oddball source files only had a few .h files specified, and the ones specified were incomplete. Rather than fuss with it, I just made them dependent on all libgcobol/*.h and gcc/cobol/*.h files.
-
rdubner authored
-
rdubner authored
-
rdubner authored
-
rdubner authored
-
rdubner authored
-
rdubner authored
-
- Dec 21, 2024
- Dec 19, 2024
-
-
James K. Lowden authored
-
rdubner authored
-
rdubner authored
It was interfering with GDB-COBOL's ability to set a breakpoint at the called routine
-
James K. Lowden authored
- Dec 18, 2024
-
-
rdubner authored
-
rdubner authored
-
James K. Lowden authored
- Dec 17, 2024
-
-
James K. Lowden authored
-
James K. Lowden authored
-
rdubner authored
-
James K. Lowden authored
-
rdubner authored
-
Jonathan Wakely authored
libstdc++-v3/ChangeLog: * include/debug/safe_local_iterator.h (_GLIBCXX_DEBUG_VERIFY_OPERANDS): Add parentheses to avoid -Wparentheses warning.
-
Jonathan Wakely authored
Inserting an empty range into a std::deque results in undefined calls to either std::copy, std::copy_backward, std::move, or std::move_backward. We call those algos with invalid arguments where the output range is the same as the input range, e.g. std::copy(first, last, first) which violates the preconditions for the algorithms. This fix simply returns early if there's nothing to insert. Most callers already ensure that we don't even call _M_range_insert_aux with an empty range, but some callers don't. Rather than checking for n == 0 in each of the callers, this just does the check once and uses __builtin_expect to treat empty insertions as unlikely. libstdc++-v3/ChangeLog: PR libstdc++/118035 * include/bits/deque.tcc (_M_range_insert_aux): Return immediately if inserting an empty range. * testsuite/23_containers/deque/modifiers/insert/118035.cc: New test.