From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 53FA03858D28; Tue, 14 Dec 2021 14:46:33 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 53FA03858D28
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103687] [12 regression] several time/date failures
 after r12-5898
Date: Tue, 14 Dec 2021 14:46:32 +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: 12.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
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: <bug-103687-4-DJbXhPUBeG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-103687-4@http.gcc.gnu.org/bugzilla/>
References: <bug-103687-4@http.gcc.gnu.org/bugzilla/>
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 <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Dec 2021 14:46:33 -0000

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

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #7)
> Yet another option would be a new dg- directive (ideally something usable=
 in
> effective target expressions) that would invoke (ideally remote)
> LC_ALL=3D$second_arg locale -k $first_arg
> and try to match it against the third argument (regex).  So one could ver=
ify
> the assumptions the test is making,
> [dg-locale-test LC_TIME "en_HK" "^t_fmt=3D\"%I:%M:%S %p %Z\""]
> or so.

That sounds great, although if the test changes from PASS to UNSUPPORTED we=
're
unlikely to notice, and then we just stop testing the code.

I think custom locales are the ideal solution, so we can control exactly wh=
at
they contain, but I haven't found time to do it.=