public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110394] Lambda capture receives wrong value
Date: Sat, 24 Jun 2023 21:24:52 +0000	[thread overview]
Message-ID: <bug-110394-4-LSpjodGubR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110394-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to jackyguo18 from comment #6)
> @Andrew Pinski - Thanks, just confirmed that that was the issue.
> 
> Why doesn't GCC choose to delete the function (thus causing the weird
> behaviour) early at lower optimization levels?
> 
> Seems kinda strange it would work at -O2.

Most likely inlining more and being more agressive of doing some optimizations.
Since it is undefined behavior if you use the object after the lifetime ends,
it is just happened to work at different levels of optimization really.

      parent reply	other threads:[~2023-06-24 21:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 15:51 [Bug other/110394] New: " jackyguo18 at hotmail dot com
2023-06-24 15:53 ` [Bug c++/110394] " jackyguo18 at hotmail dot com
2023-06-24 16:15 ` pinskia at gcc dot gnu.org
2023-06-24 16:25 ` pinskia at gcc dot gnu.org
2023-06-24 16:33 ` xry111 at gcc dot gnu.org
2023-06-24 21:21 ` jackyguo18 at hotmail dot com
2023-06-24 21:22 ` jackyguo18 at hotmail dot com
2023-06-24 21:24 ` pinskia at gcc dot gnu.org [this message]

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-110394-4-LSpjodGubR@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).