public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112652] g++.dg/cpp26/literals2.C FAILs
Date: Wed, 13 Mar 2024 13:46:14 +0000	[thread overview]
Message-ID: <bug-112652-4-lBBSy83K8e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112652-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #6)
> > --- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
> > Uni-Bielefeld.DE> ---
> >> --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> >> Given that C++ says e.g. in https://eel.is/c++draft/lex.ccon#3.1
> >> that program is ill-formed if some character lacks encoding in the execution
> >> character set, I'm afraid the Solaris iconv behavior results in violation of
> 
> Although I can barely wrap my head around the standardese there, I had a
> look at n4928 (the last? C++23 draft), which has a different wording
> here (p.25, 5.13.3):

The testcase is for a C++26 feature, which made those ill-formed.

> The current Solaris iconv behaviour certainly isn't particularly
> intuitive and I'll ask the Solaris engineers about it.  However, there's
> the question what to do about the testcase?  Just xfail it on Solaris or
> omit just the two affected subtests there?

xfailing is one possibility, but then on Solaris we'll never support C++26
properly.
Or require using GNU libiconv rather than Solaris iconv if it can't deal with
that?

  parent reply	other threads:[~2024-03-13 13:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 15:04 [Bug c++/112652] New: " ro at gcc dot gnu.org
2023-11-21 15:05 ` [Bug c++/112652] " ro at gcc dot gnu.org
2023-11-21 18:32 ` jakub at gcc dot gnu.org
2023-11-22 15:09 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-11-22 15:26 ` jakub at gcc dot gnu.org
2023-11-24  9:05 ` jakub at gcc dot gnu.org
2024-03-12 15:51 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-03-13 13:22 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-03-13 13:46 ` jakub at gcc dot gnu.org [this message]
2024-03-13 14:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-03-13 15:45 ` jakub at gcc dot gnu.org
2024-03-22 13:52 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-07  7:42 ` rguenth 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-112652-4-lBBSy83K8e@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).