public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pavel.kryukov at phystech dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103853] New: std::forward_list::merge should check if __list != this
Date: Tue, 28 Dec 2021 20:43:50 +0000 [thread overview]
Message-ID: <bug-103853-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103853
Bug ID: 103853
Summary: std::forward_list::merge should check if __list !=
this
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: pavel.kryukov at phystech dot edu
Target Milestone: ---
Created attachment 52080
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52080&action=edit
check if __list==this in std::forward_list::merge
C++ standard does not require 'do nothing' if std::forward_list::merge argument
equals to 'this', however it does not say 'undefined behavior' or 'infinite
loop' too.
I've attached my patch to fix and test it, but since I'm not an experienced GCC
contributor, I don't know how to run the tests. Following instructions on
CONTRIBUTING page builds whole GCC ending with some problems with my machine. I
would be grateful if you tell how I can test only libstdc++.
next reply other threads:[~2021-12-28 20:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 20:43 pavel.kryukov at phystech dot edu [this message]
2021-12-29 10:12 ` [Bug libstdc++/103853] " redi at gcc dot gnu.org
2021-12-29 10:22 ` redi at gcc dot gnu.org
2022-01-05 10:06 ` redi at gcc dot gnu.org
2022-01-05 10:48 ` redi at gcc dot gnu.org
2022-01-05 14:40 ` pavel.kryukov at phystech dot edu
2022-01-05 14:47 ` redi at gcc dot gnu.org
2022-01-06 10:50 ` pavel.kryukov at phystech dot edu
2022-01-06 15:00 ` cvs-commit at gcc dot gnu.org
2022-01-06 15:39 ` redi at gcc dot gnu.org
2022-01-06 19:02 ` pavel.kryukov at phystech dot edu
2022-04-21 12:33 ` cvs-commit at gcc dot gnu.org
2022-04-26 13:11 ` cvs-commit at gcc dot gnu.org
2022-05-09 16:40 ` cvs-commit at gcc dot gnu.org
2022-05-09 19:45 ` redi 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-103853-4@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).