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 tree-optimization/53273] test-cases suffer from cross-function optimizations with no way to mark limits
Date: Sun, 17 Mar 2024 04:43:10 +0000 [thread overview]
Message-ID: <bug-53273-4-mv7L0tp3TI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53273-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53273
--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Hans-Peter Nilsson from comment #8)
> There it is! I *knew* I had a PR entered for this, and was a bit surprised
> when the ipa attribute was introduced, that this PR wasn't cross-referenced.
>
> Then again I guess most people don't check in bugzilla for possible entries
> when they fix something, and this one maybe hasn't got any good terms to
> look for.
I think part of it is also finding it independently and fixing it without
looking to see if someone has filed a bug report. I have found a few like this
over the last few years as I try to clean up bugzilla for quality reports.
prev parent reply other threads:[~2024-03-17 4:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 3:07 [Bug tree-optimization/53273] New: " hp at gcc dot gnu.org
2012-05-08 23:42 ` [Bug tree-optimization/53273] " hp at gcc dot gnu.org
2012-05-08 23:48 ` hp at gcc dot gnu.org
2012-05-09 0:02 ` hp at gcc dot gnu.org
2012-05-09 0:02 ` hubicka at gcc dot gnu.org
2012-05-09 0:14 ` hp at gcc dot gnu.org
2012-05-09 3:13 ` hp at gcc dot gnu.org
2024-03-16 20:58 ` pinskia at gcc dot gnu.org
2024-03-16 23:59 ` hp at gcc dot gnu.org
2024-03-17 4:43 ` 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-53273-4-mv7L0tp3TI@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).