public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103295] constexpr std::string does not work for clang
Date: Thu, 18 Nov 2021 00:23:25 +0000	[thread overview]
Message-ID: <bug-103295-4-RgSc5Ypctz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103295-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #16 from cqwrteur <unlvsur at live dot com> ---
(In reply to Jonathan Wakely from comment #15)
> Reopened :-(
> 
> I have a patch to make clang happy, but I think what we really want is a
> language change.

hi jwakely. i am trying to add a new patch to ignore copying DLLs to
../$(libdir)/bin if we are build gcc with multilibs (since 32 bits dlls
overrides 64 bits dlls). libgcc does not copy dlls either. do you think that is
appropriate?

  parent reply	other threads:[~2021-11-18  0:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  0:31 [Bug libstdc++/103295] New: " unlvsur at live dot com
2021-11-17  0:31 ` [Bug libstdc++/103295] " unlvsur at live dot com
2021-11-17  0:46 ` unlvsur at live dot com
2021-11-17  0:55 ` pinskia at gcc dot gnu.org
2021-11-17  0:57 ` unlvsur at live dot com
2021-11-17  1:13 ` unlvsur at live dot com
2021-11-17  1:14 ` redi at gcc dot gnu.org
2021-11-17  1:17 ` redi at gcc dot gnu.org
2021-11-17  9:53 ` redi at gcc dot gnu.org
2021-11-17  9:57 ` redi at gcc dot gnu.org
2021-11-17  9:58 ` unlvsur at live dot com
2021-11-17 10:00 ` redi at gcc dot gnu.org
2021-11-17 12:02 ` redi at gcc dot gnu.org
2021-11-17 14:48 ` redi at gcc dot gnu.org
2021-11-17 17:23 ` cvs-commit at gcc dot gnu.org
2021-11-17 17:41 ` redi at gcc dot gnu.org
2021-11-18  0:21 ` redi at gcc dot gnu.org
2021-11-18  0:23 ` unlvsur at live dot com [this message]
2021-11-18  7:43 ` rguenth at gcc dot gnu.org
2021-11-19 18:16 ` cvs-commit at gcc dot gnu.org
2021-11-19 18:50 ` redi at gcc dot gnu.org
2021-11-19 20:19 ` cvs-commit at gcc dot gnu.org
2021-11-19 20:21 ` redi at gcc dot gnu.org
2022-11-11 17:59 ` cvs-commit at gcc dot gnu.org
2022-11-14 18:34 ` cvs-commit 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-103295-4-RgSc5Ypctz@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).