public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/111685] Segfault while sorting on array element address
Date: Wed, 04 Oct 2023 01:35:00 +0000	[thread overview]
Message-ID: <bug-111685-4-6AWdP1XlJ8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111685-4@http.gcc.gnu.org/bugzilla/>

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

Xi Ruoyao <xry111 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xry111 at gcc dot gnu.org

--- Comment #7 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
[alg.sorting] p3:

For algorithms other than those described in 28.7.3, comp shall
induce a strict weak ordering on the values.

Note the terminology "values".  I cannot find the definition of "value" in the
standard, but I'm pretty sure the "values" must be independent to "their
addresses" or the entire standard would become completely unreasonable (note
that rvalues has no addresses at all).

  parent reply	other threads:[~2023-10-04  1:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 18:57 [Bug c++/111685] New: " knoepfel at fnal dot gov
2023-10-03 19:06 ` [Bug libstdc++/111685] " pinskia at gcc dot gnu.org
2023-10-03 19:10 ` pinskia at gcc dot gnu.org
2023-10-03 19:14 ` knoepfel at fnal dot gov
2023-10-03 19:19 ` knoepfel at fnal dot gov
2023-10-03 21:24 ` pinskia at gcc dot gnu.org
2023-10-03 21:37 ` pinskia at gcc dot gnu.org
2023-10-04  1:35 ` xry111 at gcc dot gnu.org [this message]
2023-10-04  9:48 ` redi at gcc dot gnu.org
2023-10-04 10:06 ` redi at gcc dot gnu.org
2023-10-04 17:46 ` fchelnokov at gmail dot com
2023-10-05 19:27 ` knoepfel at fnal dot gov
2023-10-06 10:10 ` fchelnokov at gmail dot com

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-111685-4-6AWdP1XlJ8@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).