From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Cc: hiraditya@gmail.com, sebpop@gmail.com
Subject: Re: [PATCH] RFC: Enable graphite at -O3 -fprofile_use
Date: Fri, 13 Nov 2015 10:30:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.11.1511131124050.4884@t29.fhfr.qr> (raw)
Sorry for not replying earlier, it seems gmail eats messages sometimes
(thus also not replying to the mail directly).
You write
> Since graphite will not modify the CFG when it does not do any
optimization,
> we would like to propose that graphite's polyhedral optimizer be enabled
at
> -O3 -fprofile-use where, compile time is of lesser concern.
I think this is generally a good idea. Note that for this we should
raise the minimum supported ISL version to one supporting the
timeout thingy and of course we need to make ISL a required
prerequesite for building GCC. Which means making sure ISL builds
on all our primary and secondary host platforms (I think it does).
I'd also like to see runtime / compile-time (and code-size?) figures
for, say, SPEC CPU 2006 (with FDO of course). Maybe also some
information on whether GRAPHITE did anything for any benchmark
in that suite (I notice GRAPHITE doesn't use the -fopt-info
machinery, aka dump_printf and friends with MSG_OPTIMIZED_LOCATIONS
or MSG_MISSED_OPTIMIZATIONS).
So please work on the above list of items.
Thanks,
Richard.
next reply other threads:[~2015-11-13 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 10:30 Richard Biener [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-13 11:19 VandeVondele Joost
2015-11-13 11:32 ` Richard Biener
2015-11-13 13:25 ` aditya kumar
2015-11-09 5:16 hiraditya
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=alpine.LSU.2.11.1511131124050.4884@t29.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=hiraditya@gmail.com \
--cc=sebpop@gmail.com \
/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).