From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-455949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 28858 invoked by alias); 9 Jul 2014 11:40:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 28705 invoked by uid 48); 9 Jul 2014 11:39:58 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/61758] std::chrono::steady_clock::now() no longer exported
Date: Wed, 09 Jul 2014 11:40: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: 4.8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: <bug-61758-4-pjdCWpScUn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61758-4@http.gcc.gnu.org/bugzilla/>
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: 2014-07/txt/msg00540.txt.bz2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61758

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
It is totally unsupported (and unlikely to work) to mix C++11 code built with
GCC 4.x and 4.y, for any x!=y

Mixing code built with 4.8.x and 4.8.y should work, and does with the default
configuration.

You didn't actually provide the information required by http://gcc.gnu.org/bugs
such as the output of 'gcc -v' but I assume you're building GCC with
--enable-libstdcxx-time, in which case there are fewer guarantees. If Gentoo is
using that option (which should not be necessary with GCC 4.8 anyway) then you
need to rebuild all the libraries that depend on the <chrono> types.

We could potentially export a steady_clock::now() compatibility symbol for the
--enable-libstdcxx-time config, but I'd prefer to see that option go away
rather than keep it on life support.