public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108096] [13 regression] libreoffice build failure #2 since r13-4564
Date: Wed, 14 Dec 2022 11:25:08 +0000	[thread overview]
Message-ID: <bug-108096-4-GXVkKlVkgr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108096-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Similar problem to PR 108071. The OUString type can only be constructed from
char(&)[N] and const char(&)[N], not from const char*. The original code
constructs initializer_list<OUString> and so each element is initialized
directly from an array. The new code decays the arrays to
initializer_list<const char*> and then fails to construct OUString objects from
const char* const values.

  parent reply	other threads:[~2022-12-14 11:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 10:56 [Bug c++/108096] New: [13 regression] libreoffice build failure #2 manuel.lauss at googlemail dot com
2022-12-14 11:18 ` [Bug c++/108096] [13 regression] libreoffice build failure #2 since r13-4564 jakub at gcc dot gnu.org
2022-12-14 11:25 ` redi at gcc dot gnu.org [this message]
2022-12-14 11:32 ` redi at gcc dot gnu.org
2022-12-14 12:36 ` jason at gcc dot gnu.org
2022-12-15  5:27 ` jason 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-108096-4-GXVkKlVkgr@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).