From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3E2723858434; Sat, 7 Jan 2023 08:29:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3E2723858434 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1673080150; bh=uMdqkdeI63+YWTMceyjMpjrSR/4oLTJUeBzPO84qaKw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=jyEHH1nkxoQ3gGhGwhk1SvTYsVRIEVLZ5p0AnWyODy6DVsgmpPIRcSWbSX5XuXosi RkKhW0d5vlFej4RaMBlsJ86CWlxyPSmU5bqlHiTM/9MeaU+sDAp1Cknoh9NhwmbcrQ a3lWiz+GxjfTfzcAHODmJx1/z+S1tdsQEufVw4aA= From: "jdx at o2 dot pl" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/108221] Building cross compiler for H8 family fails at libstdc++-v3/src/c++20/tzdb.cc Date: Sat, 07 Jan 2023 08:29:07 +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: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jdx at o2 dot pl X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108221 --- Comment #11 from Jan Dubiec --- (In reply to Jonathan Wakely from comment #8) > (In reply to Jan Dubiec from comment #6) > > Please note -mn -mint32 options =E2=80=93 > > normal mode (aka 16-bit mode) with 32-bit integers. >=20 > Has this bizarre mode ever been able to build libstdc++? Yes, it was possible to build libstdc++ in this mode before introduction of= all that C++20 time zone stuff in 9fc61d45. E.g. I am able to build 907c84cb wh= ich is parent of 9fc61d45. That being said, the normal mode is indeed "bizzare" and I can't imagine my= self why one would want to use it these days, when the original 16-bit H8/300 di= ed a long time ago and its descendants are just dying. Perhaps support for normal mode should be removed just like support for H8/300 was in mid-2020 (as far= as I remember).=