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 rtl-optimization/37516] ~(-2 - a) is not being optimized into a + 1
Date: Thu, 23 Feb 2012 22:16:00 -0000 [thread overview]
Message-ID: <bug-37516-4-aL48NtTo93@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-37516-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37516
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-02-23 22:15:05 UTC ---
> Maybe get away with these old-stylish names ('tree' and 'fold') and
> make it match reality, gimple-ssa-combine.c ;)
That sounds like a good idea. I have done that.
>
> Still have to have a look at your branch - do you have a brief
> overview documentation, for example on the wiki? What I'd like
> to do is have an interface that I can re-use for VN combining,
> basically replace its simplify_*_expression functions.
I don't have one yet. But I hope to create one this weekend.
Right now replacing the VN combining with this new functionality will not work
as it scans the defs itself. Though I am moving all the def scanning to its
own function which should allow for the code to be more modular and allow for
the VN combining to work with it.
next prev parent reply other threads:[~2012-02-23 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-37516-4@http.gcc.gnu.org/bugzilla/>
2012-02-23 8:48 ` pinskia at gcc dot gnu.org
2012-02-23 9:17 ` rguenther at suse dot de
2012-02-23 22:16 ` pinskia at gcc dot gnu.org [this message]
2012-02-24 9:03 ` rguenther at suse dot de
2012-02-26 1:43 ` pinskia at gcc dot gnu.org
2021-08-03 23:03 ` pinskia at gcc dot gnu.org
2008-09-14 3:37 [Bug rtl-optimization/37516] New: " pinskia at gcc dot gnu dot org
2008-09-14 3:37 ` [Bug rtl-optimization/37516] " pinskia at gcc dot gnu dot org
2008-09-14 4:57 ` pinskia at gcc dot gnu dot 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-37516-4-aL48NtTo93@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).