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 tree-optimization/114206] recursive function call vs local variable addresses
Date: Sat, 02 Mar 2024 11:06:38 +0000 [thread overview]
Message-ID: <bug-114206-4-bSamnrMNUL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114206-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114206
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
CC| |xry111 at gcc dot gnu.org
--- Comment #4 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> I think both 0 and 1 are correct here.
>
> The question becomes does the address of b need to be different between
> different calls of f. I am not 100% convinced it needs to be different.
It looks like they needs to be different as they refer different objects and
the lifetime of both object has still not ended when comparing them.
next prev parent reply other threads:[~2024-03-02 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 9:06 [Bug c/114206] New: GCC generates wrong-code congli at smail dot nju.edu.cn
2024-03-02 9:13 ` [Bug tree-optimization/114206] " pinskia at gcc dot gnu.org
2024-03-02 9:27 ` [Bug tree-optimization/114206] recursive function call vs local variable addresses congli at smail dot nju.edu.cn
2024-03-02 9:36 ` congli at smail dot nju.edu.cn
2024-03-02 11:06 ` xry111 at gcc dot gnu.org [this message]
2024-03-02 15:15 ` arsen at gcc dot gnu.org
2024-03-04 9:54 ` rguenth at gcc dot gnu.org
2024-03-04 17:31 ` [Bug tree-optimization/114206] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2024-03-05 12:14 ` jakub 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-114206-4-bSamnrMNUL@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).