public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "samuel.beer at gmx dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109122] New: std::ranges::find segfaults with gcc (trunk but not 12.2) on godbolt
Date: Tue, 14 Mar 2023 09:10:47 +0000	[thread overview]
Message-ID: <bug-109122-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109122
           Summary: std::ranges::find segfaults with gcc (trunk but not
                    12.2) on godbolt
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: samuel.beer at gmx dot ch
  Target Milestone: ---

std::ranges::find segfaults in gcc on godbolt. Happens only with gcc trunk but
not with latest 12.2...

https://godbolt.org/#z:OYLghAFBqd5QCxAYwPYBMCmBRdBLAF1QCcAaPECAMzwBtMA7AQwFtMQByARg9KtQYEAysib0QXACx8BBAKoBnTAAUAHpwAMvAFYTStJg1DIApACYAQuYukl9ZATwDKjdAGFUtAK4sGe1wAyeAyYAHI%2BAEaYxCAAHKQADqgKhE4MHt6%2BekkpjgJBIeEsUTHxdpgOaUIETMQEGT5%2BXLaY9nkM1bUEBWGR0XG2NXUNWc0KQ93BvcX9sQCUtqhexMjsHOYAzMHI3lgA1CYbbsjj%2BKiH2CYaAIKb27uYB0fEhsCYChdXt2ZbDDte%2B0ObgAbhUiMRPjc7n8Hk9jgJVgkCB8NpcoT97gDHkCTgRiMFgJDbjdmGwFAkmKs9sQjE8ACJ7U4gEAvIzvQ5WKE3cbELwOPaMRwEACeXxMAHZOdc9jKBYJCMKIMECHsGMQ5l9ZVq9iBZWqAPoSiyq4gHcV0zWyo0Si1c6WypheIh7N4EfVqiBzPYAWgue2VZuNxEwBGWDBlBo5ZttxPtMoDkY2UptHLFNy1AHoM/6GLQpns0AxxphVAlTY7nTz9WXMDRVJ6fX6mSAeQT9cC8JgAO6B6khsMHMxmYNiRxscxmKMppNp2NfAMsJjBT1iyWWmWF8aMgjoZmghwkIGChV%2B/f03vNMykDbT5Pph1O1D%2BlWHBk00AgGgMdAQfekPZXoOABsx4isyrruuqqb3jKWZ7BWT6EOe77Ml%2B6D6ngVC/hU/4mAArFYeF0kqggChqkp9qGNICvSr4AVO5q4WYIHymBIAQWqGozjB/pUAWAjFqWpoQM2CisJg%2BpMCibhYDsIoJJgSoEAs267iA%2B7gkerGiqizKbm6hDREwmmol61o8VqZbKlhE4eEWKqGS84J7F2UkFggySMGAYD4W4DATlxUpajaAq0EovH8fZJZlnsIk7syYlsJJ0mybQ8mKYQKnNhph5HKBOnYMyjnGbl2BmWuFmylZgg2UOoQkIutDPkZzmuQo7meQw3m%2Bf5Q6Beu0YDZhsVId1GwMvuAB0rieuVQXajK1UELVZj8F4357GerSYGwpHmHh6A9RO/6EL6qIGv1PEplC5ocAstCcHhvB%2BBwWikKgnBuNY1iMksKzYj8PCkAQmh3QsADWIB4Ro%2BicJIz2g%2B9nC8AoIAwyDr13aQcCwDAiAoKgLAJHQ0TkJQaBEyTMTAAozAJAoHkEKQWAdqsABqnZdgA8gpL1AzQaXRKjEARIjETBLUwqcED4vMMQwpcxE2hgtLvAU7tBBc7mUuY8zO2vOIuv4MGlSgqjuslhUTprG9yqtIjeYRC88seFgiN4ngLCqwsVAGDTHPdjzjCqzIggiGI7BSKH8hKGoiO6M0BhGCg32WPoeARKjkALKgSJpOb3qnK%2BpiWNYZgaD6ADqYhNd6XPtd6SIICO6Ao9tlTOBArgjE0pCBFMRQlNkySpAIPfD7kaQ9IP/RjO37SdMMniNHo5Qdx0EzT30MRjBM4%2B710W8zDvCwKH9qwSPdj0I7rH0cHsqixEB3pAZILrIMgsV4ut4NehAuCEBIIODYXA5i8AxloOYEMoYwwehweGpAvbQ1IC9N6d8UZo2BqDBYON8ZLAIAkJ0ZMIAU2JvQYgoRxKcEfs/V%2B79P5cDMJNMwvBMD4HBHgXczR%2BBh1EOIKOPCY4qHULrBOpAuwvASN7WGHAnooMRnfLmTpCEqlQHxGhL837AA/l/XkDBf6xQ8JTchwDQHgOwQsBAmAmBYBiJ6GRCCkEw1QbwdBthMEQLBqQSGyC4EbBvmg5GWDMZQJkSw%2BRt8gmeNCaCYgKRnCSCAA%3D%3D%3D

             reply	other threads:[~2023-03-14  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14  9:10 samuel.beer at gmx dot ch [this message]
2023-03-14 10:12 ` [Bug c++/109122] " redi at gcc dot gnu.org
2023-03-14 10:15 ` redi at gcc dot gnu.org
2023-03-14 14:33 ` mpolacek at gcc dot gnu.org
2023-03-14 14:42 ` mpolacek at gcc dot gnu.org
2023-11-10 19:45 ` pinskia at gcc dot gnu.org
2023-11-10 21:22 ` ppalka 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-109122-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).