public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/104739] gdc.test/runnable/mangle.d etc. FAIL with Solaris as
Date: Fri, 02 Feb 2024 15:48:20 +0000 [thread overview]
Message-ID: <bug-104739-4-ZhNfevN6tO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104739-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104739
--- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #4 from Rainer Orth <ro at gcc dot gnu.org> ---
> I wonder how to handle this: while DejaGnu has an ucn effective-target keyword,
> the gdc.test testsuite doesn't use those at all.
What I think could be done is
* Add "//UTF-8 chars" comments to testmodule.d and ufcs.d; mangle.d
already has one.
* Make gdc-utils.exp (gdc-convert-test) check for those annotations,
adding
// { dg-require-effective-target ucn}
if found.
The new annotations would have to go upstream, I believe. WDYT?
next prev parent reply other threads:[~2024-02-02 15:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 12:23 [Bug d/104739] New: " ro at gcc dot gnu.org
2022-03-01 12:24 ` [Bug d/104739] " ro at gcc dot gnu.org
2022-05-06 8:32 ` jakub at gcc dot gnu.org
2023-05-08 12:24 ` rguenth at gcc dot gnu.org
2024-02-02 13:35 ` ro at gcc dot gnu.org
2024-02-02 15:48 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2024-02-02 21:23 ` ibuclaw at gdcproject dot org
2024-02-05 12:52 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-02-05 12:54 ` ro at gcc dot gnu.org
2024-02-14 10:52 ` ro at gcc dot gnu.org
2024-02-14 13:53 ` cvs-commit at gcc dot gnu.org
2024-02-14 13:55 ` ro at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-104739-4-ZhNfevN6tO@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).