From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1E24E395A41B; Fri, 12 Jun 2020 12:48:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1E24E395A41B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1591966085; bh=Y3fyItYsKXxOYkqUsime1mMoRmIEAgB054iD50kJjXg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hOeVtvn5i6pFJdZK7pwl4lc0EhscNaroL91ckVUdPJ2ZERpIghT5BpVbTJPV/TvDc zijLn2hwmKL1QAv/w79fKHRYzpgOZ5kznFPI/DoFEo45GeMy6ZGudneLUZJk+JmzM3 gAzod2GSxT6q4N8+gACjJ51qz/XsG8qj9cWL0/34= From: "maxim.yegorushkin at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f; Date: Fri, 12 Jun 2020 12:48:04 +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: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: maxim.yegorushkin at gmail dot com X-Bugzilla-Status: SUSPENDED X-Bugzilla-Resolution: 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: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jun 2020 12:48:05 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D81122 --- Comment #19 from Maxim Egorushkin = --- (In reply to Jonathan Wakely from comment #17) > At this time LWG 2381 is still open. Until the proposed fix (or some other > fix) is resolved by making a change to the draft standard, I do not want = to > change libstdc++. May be enable hexfloat round-trip if a user defines a macro? The standards often follow existing practice, waiting on the standard may l= ead to a deadlock.=