stackoverflow May 4, 2026 Rep: 81

Why is a call to `copy_n` ambiguous between `std::copy_n` and `__gnu_cxx::copy_n` in GCC 9, but not in GCC 13?

Score

Answers

176

Views

34.2

Trend Score

Question Details

No question body available.

Answers (1)

May 4, 2026 Score: 9 Rep: 45,494 Quality: Medium Completeness: 70%

GCC11 and below:
std::vector -> std::allocator inherits from gnucxx::newallocator (from ), so gnucxx is an associated namespace.

GCC12:
libstdc++ patched to change gnucxx::newallocator -> std::newallocator (In commit fe9571a), so gnu_cxx is no longer an associated namespace for anything with std::allocator.

Export Question Data

Export this question and its answers for further analysis or reporting.

Back to Questions

Why is a call to `copy_n` ambiguous between `std::copy_n` and `__gnu_cxx::copy_n` in GCC 9, but not in GCC 13?

Question Details

Tags

Answers (1)

Analysis Metrics

Question Information

Actions

Related Questions

Export Question Data