[Bug c++/110380] [feature request] "-pg-constexpr=coverage-output" emit coverage metrics for constexpr code evaluated at compile time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110380 Anthony Williams changed: What|Removed |Added CC||anthony.ajw at gmail dot com ---

[Bug c++/110380] [feature request] "-pg-constexpr=coverage-output" emit coverage metrics for constexpr code evaluated at compile time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110380 --- Comment #4 from Gašper Ažman --- John McFarlane noted that pre-initializing coverage datastructures with the results of the constexpr-evaluated traces would also be a possible direction. It does mean the linker needs to then correctly merge

[Bug c++/110380] [feature request] "-pg-constexpr=coverage-output" emit coverage metrics for constexpr code evaluated at compile time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110380 Hana Dusíková changed: What|Removed |Added CC||hanicka at hanicka dot net --- Comment

[Bug c++/110380] [feature request] "-pg-constexpr=coverage-output" emit coverage metrics for constexpr code evaluated at compile time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110380 --- Comment #2 from Gašper Ažman --- -fprofile-constexpr is perfectly fine :), as long as it gets a filename argument for the output; build automation will be thankful.

[Bug c++/110380] [feature request] "-pg-constexpr=coverage-output" emit coverage metrics for constexpr code evaluated at compile time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110380 Andrew Pinski changed: What|Removed |Added Severity|normal |enhancement

[Bug c++/110380] [feature request] "-pg-constexpr=coverage-output" emit coverage metrics for constexpr code evaluated at compile time

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110380 --- Comment #1 from Andrew Pinski --- pg is not the correct option here as that is about using the Gprof profiling which is different from gcov. More likely the option will be named -fprofile-constexpr