public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/31862] Loop IM and other optimizations harmful for -fopenmp
Date: Wed, 25 Feb 2009 18:43:00 -0000 [thread overview]
Message-ID: <20090225184304.24362.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31862-87@http.gcc.gnu.org/bugzilla/>
------- Comment #24 from bonzini at gnu dot org 2009-02-25 18:43 -------
Andrew, your comments #6 #8 #9 clearly show that you haven't understood the
issue and are just talking past others.
The other hand the transformation has been shown to be an optimization on
single-thread cases; if it is bad for multiprocessors, it means it probably
should be guarded by a flag (but what if the load is not necessary? should it
use the same flag, a separate flag, or be always enabled?). But the IM code
should be modified to use the flag as suggested by the C++ standard (and to
avoid the load if it is not necessary, as it is in this case but not in the
case explained by N2238).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31862
next prev parent reply other threads:[~2009-02-25 18:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-31862-87@http.gcc.gnu.org/bugzilla/>
2007-05-08 13:10 ` [Bug tree-optimization/31862] " dnovillo at acm dot org
2007-05-08 14:31 ` pinskia at gcc dot gnu dot org
2007-05-08 14:37 ` rguenth at gcc dot gnu dot org
2007-05-08 14:39 ` dnovillo at acm dot org
2007-05-08 14:44 ` dnovillo at acm dot org
2007-05-08 14:59 ` Andrew Pinski
2007-05-08 14:59 ` pinskia at gmail dot com
2007-05-08 18:08 ` jakub at gcc dot gnu dot org
2007-05-08 18:46 ` pinskia at gmail dot com
2007-05-09 2:19 ` [Bug middle-end/31862] " pinskia at gcc dot gnu dot org
2007-05-09 6:30 ` jakub at gcc dot gnu dot org
2007-06-04 18:12 ` theodore dot papadopoulo at sophia dot inria dot fr
2007-10-14 14:16 ` tomash dot brechko at gmail dot com
2007-10-22 23:17 ` amylaar at gcc dot gnu dot org
2007-11-01 3:15 ` matz at gcc dot gnu dot org
2007-11-12 19:11 ` jakub at gcc dot gnu dot org
2009-02-25 12:18 ` bonzini at gnu dot org
2009-02-25 13:26 ` rguenth at gcc dot gnu dot org
2009-02-25 16:07 ` davids at webmaster dot com
2009-02-25 16:13 ` dnovillo at google dot com
2009-02-25 17:54 ` davids at webmaster dot com
2009-02-25 18:04 ` matz at gcc dot gnu dot org
2009-02-25 18:07 ` pinskia at gcc dot gnu dot org
2009-02-25 18:35 ` davids at webmaster dot com
2009-02-25 18:43 ` bonzini at gnu dot org [this message]
2009-02-26 8:26 ` ebotcazou 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=20090225184304.24362.qmail@sourceware.org \
--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).