From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-455947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 32022 invoked by alias); 9 Jul 2014 10:16:59 -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 31971 invoked by uid 48); 9 Jul 2014 10:16:54 -0000
From: "Martin.vGagern at gmx dot net" <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 10:16: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: Martin.vGagern at gmx dot net
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-Z0FfUdzYyK@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/msg00538.txt.bz2

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

--- Comment #1 from Martin von Gagern <Martin.vGagern at gmx dot net> ---
I just read https://gcc.gnu.org/ml/gcc-patches/2013-05/msg01553.html indicating
that this is likely a deliberate ABI breakage for an experimental API. If that
is your official position, feel free to close WONTFIX. Too bad that this kind
of information contained in the email isn't included in the commit message.
Would have saved me a lot of time.