On Tue, 30 Dec 2008 18:50:01 +0300 Andrey Semashev <andrey.semashev@gmail.com> wrote:
Dmitry V. Krivenok wrote:
Hello!
As you can see the example compiled using gcc-4.1.2 compiles without any warnings regardless of optimization level. However, gcc-4.3.2 produces a lot of strange warnings if optimization is enabled.
I don't really know is it gcc or boost issue. Is it safe to use boost::date_time with gcc-4.3.2 and -O3 optimization level?
Which Boost version do you use? I believe I fixed this warning in trunk and release branch.
PS: It was a spurious warning, the variable was not actually used before being initialized. And I have no idea why it only occurs with O1 or higher.
Dmitry is not alone on this one I'm afraid. A week prior to his report I filed a Trac issue (2612) against this too. Running against gcc-4.3, with -O3 I get the same, using boost version 1.37 (release). Would be real happy if this has been seen to in the trunk.. Cheers, -- Manfred 31 December, 2008