You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When compiling with gcc 13.1 (and other version) and using GOOGLE_STRIP_LOG the output gets optimized away as expected.
However, the constructor and deconstruction calls of NullStream() are left over in the compiled program.
I copied together from 3a0d4d2 with a cmake -DCMAKE_BUILD_TYPE=Release .. generated output.
The text was updated successfully, but these errors were encountered:
JensHuthmann
changed the title
NullStream constructor and deconstruction not optimized away with GOOGLE_STRIP_LOG
NullStream constructor and deconstructor not optimized away with GOOGLE_STRIP_LOG
Jun 22, 2023
After looking into the issue, I believe something like this could work. NullStream should probably not derive from LogMessage::LogStream to allow the compiler to optimize the corresponding symbols away.
When compiling with gcc 13.1 (and other version) and using GOOGLE_STRIP_LOG the output gets optimized away as expected.
However, the constructor and deconstruction calls of NullStream() are left over in the compiled program.
I copied together from 3a0d4d2 with a
cmake -DCMAKE_BUILD_TYPE=Release ..
generated output.Link to compiler explorer See line 518 in compiler output
The text was updated successfully, but these errors were encountered: