public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/65502] pure-const should play well with clobbers.
Date: Tue, 24 Mar 2015 06:33:00 -0000 [thread overview]
Message-ID: <bug-65502-4-ab8df4ZaUD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65502-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65502
--- Comment #5 from Jan Hubicka <hubicka at ucw dot cz> ---
> I think we can safely ignore clobbers when scanning functions for
> pure/constness.
Yes (it is what the patch does), but doing so may cause worse code in the
function calling these destructors. DCE will remove the destructor call and we
will lose information about memory location being dead.
I think we may want to output the clobber after destructors calls in this case.
prev parent reply other threads:[~2015-03-24 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 10:47 [Bug ipa/65502] New: " hubicka at gcc dot gnu.org
2015-03-22 9:54 ` [Bug ipa/65502] " hubicka at gcc dot gnu.org
2015-03-23 0:16 ` hubicka at gcc dot gnu.org
2015-03-23 9:57 ` rguenth at gcc dot gnu.org
2015-03-24 6:33 ` hubicka at ucw dot cz [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-65502-4-ab8df4ZaUD@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).