public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/111948] subrange modifies a const size object
Date: Tue, 24 Oct 2023 20:37:38 +0000 [thread overview]
Message-ID: <bug-111948-4-JYJY7brozv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111948-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111948
--- Comment #5 from 康桓瑋 <hewillk at gmail dot com> ---
It shouldn't be. Is that a compiler bug?
Clang compiles the same libstdc++ code without problems.(In reply to Jonathan
Wakely from comment #2)
> (In reply to 康桓瑋 from comment #1)
> > _M_size._M_size in the function body is already const.
>
> It shouldn't be. Is that a compiler bug?
>
> Clang compiles the same libstdc++ code without problems.
Sorry, I didn't delve into whether this was a bug in libstdc++ or the compiler.
At the moment it seems this is a compiler problem.
https://godbolt.org/z/ronn4exhG
next prev parent reply other threads:[~2023-10-24 20:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 5:51 [Bug libstdc++/111948] New: " hewillk at gmail dot com
2023-10-24 5:55 ` [Bug libstdc++/111948] " hewillk at gmail dot com
2023-10-24 16:15 ` redi at gcc dot gnu.org
2023-10-24 16:20 ` redi at gcc dot gnu.org
2023-10-24 16:30 ` redi at gcc dot gnu.org
2023-10-24 20:37 ` hewillk at gmail dot com [this message]
2023-11-08 11:35 ` de34 at live dot cn
2023-11-08 12:01 ` redi at gcc dot gnu.org
2023-11-23 14:40 ` redi at gcc dot gnu.org
2023-12-05 23:35 ` cvs-commit at gcc dot gnu.org
2023-12-06 14:44 ` cvs-commit at gcc dot gnu.org
2023-12-06 14:46 ` redi at gcc dot gnu.org
2024-02-02 16:12 ` 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-111948-4-JYJY7brozv@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).