This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/69908] recognizing idioms that check for a buffer of all-zeros could make *much* better code
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 23 Feb 2016 00:21:47 +0000
- Subject: [Bug tree-optimization/69908] recognizing idioms that check for a buffer of all-zeros could make *much* better code
- Auto-submitted: auto-generated
- References: <bug-69908-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69908
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #1 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> ---
There is a lot of work still to do in the vectorizer. Perhaps some of your
suggestions are already in this list:
http://gcc.gnu.org/bugzilla/buglist.cgi?keywords=missed-optimization,%20&keywords_type=allwords&list_id=7719&short_desc=vectori%20SLP&cf_known_to_fail_type=allwords&cf_known_to_work_type=allwords&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&short_desc_type=anywordssubstr&component=tree-optimization&product=gcc
Problems are more likely to be fixed if they are 1) minimally described 2)
causes are identified 3) possible solutions are proposed.
Looking at what GCC is doing internally
(https://gcc.gnu.org/onlinedocs/gcc/Developer-Options.html) may help to
pin-point causes.