public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/58250] -fprofile-use causes: "warning: -fprefetch-loop-arrays is not supported with -Os"
Date: Wed, 28 Aug 2013 09:28:00 -0000 [thread overview]
Message-ID: <bug-58250-4-Ia0zGLHg6N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58250-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58250
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Markus Trippelsdorf from comment #0)
> Just noticed this issue during a PGO/LTO Firefox build.
> During the -fprofile-use phase I always get the following warning:
> warning: -fprefetch-loop-arrays is not supported with -Os [enabled by
> default]
>
> This is caused by rev.193135:
> /* Enable sw prefetching at -O3 for CPUS that prefetching is helpful. */
> if (flag_prefetch_loop_arrays < 0
> && HAVE_prefetch
> - && optimize >= 3
> + && (optimize >= 3 || flag_profile_use)
> && TARGET_SOFTWARE_PREFETCHING_BENEFICIAL)
> flag_prefetch_loop_arrays = 1;
>
>
> Does the following patch look OK?
>
> diff --git a/gcc/toplev.c b/gcc/toplev.c
> index 53f53fd..9955ed4 100644
> --- a/gcc/toplev.c
> +++ b/gcc/toplev.c
> @@ -1506,7 +1506,7 @@ process_options (void)
>
> /* This combination of options isn't handled for i386 targets and doesn't
> make much sense anyway, so don't allow it. */
> - if (flag_prefetch_loop_arrays > 0 && optimize_size)
> + if (flag_prefetch_loop_arrays > 0 && optimize_size && !flag_profile_use)
> {
> warning (0, "-fprefetch-loop-arrays is not supported with -Os");
> flag_prefetch_loop_arrays = 0;
Hmm, I rather question this hunk - where does it come from? Why is
prefetching "unsupported" at -Os?
next prev parent reply other threads:[~2013-08-28 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 9:33 [Bug gcov-profile/58250] New: " markus at trippelsdorf dot de
2013-08-28 9:28 ` rguenth at gcc dot gnu.org [this message]
2013-08-28 9:51 ` [Bug gcov-profile/58250] " jakub at gcc dot gnu.org
2013-09-05 19:36 ` hubicka at ucw dot cz
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-58250-4-Ia0zGLHg6N@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).