public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/81323] IPA-VRP doesn't handle return values
Date: Wed, 15 Mar 2023 17:11:04 +0000 [thread overview]
Message-ID: <bug-81323-4-UFWJSgAZc0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-81323-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81323
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aldyh at gcc dot gnu.org,
| |amacleod at redhat dot com
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> We do not have "return functions" but all IPA propagations just work on the
> acyclic graph call arg -> callee.
Well, we don't need to propagate that immediately again, then I agree we'd need
to propagate the ranges through the whole program then. All that would be
sufficient for start would be to remember the global ranges of the return
values and copy those to the callers.
next prev parent reply other threads:[~2023-03-15 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-81323-4@http.gcc.gnu.org/bugzilla/>
2023-03-15 17:06 ` jakub at gcc dot gnu.org
2023-03-15 17:11 ` jakub at gcc dot gnu.org [this message]
2023-03-15 17:14 ` jakub at gcc dot gnu.org
2023-03-15 17:16 ` jakub at gcc dot gnu.org
2023-03-16 21:05 ` amacleod at redhat dot com
2023-03-21 11:27 ` aldyh at gcc dot gnu.org
2023-12-06 18:57 ` pinskia at gcc dot gnu.org
2023-12-06 21:59 ` hubicka 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-81323-4-UFWJSgAZc0@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).