From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7660 invoked by alias); 3 Sep 2015 11:55:40 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 7190 invoked by uid 48); 3 Sep 2015 11:55:37 -0000 From: "sthlm58 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/67434] std::chrono::duration acts like static even if instantiated every time Date: Thu, 03 Sep 2015 11:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 5.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sthlm58 at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-09/txt/msg00262.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67434 --- Comment #2 from sthlm58 at gmail dot com --- (In reply to Jonathan Wakely from comment #1) > (In reply to Michal Kucharski from comment #0) > > std::chrono::duration benchmark( ) > > { > > std::random_device rd; > > > > std::chrono::duration total; > > You have not initialized this variable. > > > > > for (int i = 0; i < 100; i++) > > { > > auto t1 = std::chrono::high_resolution_clock::now(); > > auto t2 = std::chrono::high_resolution_clock::now(); > > total += std::chrono::duration_cast>(t2 - > > t1); > > This has undefined behaviour because you are performing addition on an > uninitialized value. You could have found this with valgrind. In other words, here 'total' was default-initialized (hence unspecified) thus causing undefined behavior. It it were value-initialized e.g. with '{}' the problem would not happen.