public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43829] Scalarization of reductions
Date: Mon, 10 Oct 2011 09:06:00 -0000	[thread overview]
Message-ID: <bug-43829-4-uRvKFOBbb5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43829-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43829

--- Comment #47 from rguenther at suse dot de <rguenther at suse dot de> 2011-10-10 09:05:29 UTC ---
On Sat, 8 Oct 2011, mikael at gcc dot gnu.org wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43829
> 
> --- Comment #43 from Mikael Morin <mikael at gcc dot gnu.org> 2011-10-08 17:57:43 UTC ---
> (In reply to comment #39)
> > Thanks. One comment: I think you will increase the binary size by inlining the
> > reduction. Could you consider keeping the current libgfortran version and
> > protecting the scalarization by
> >   if (!optimize_size)
> > 
> This is included in the patch in comment #41. Unfortunately, it makes the test
> (comment #42) fail with -Os in the testsuite. I don't know yet how I will
> handle it. I would like to avoid forcing one optimization level if possible.
> Any idea?

/* { dg-skip-if "" { *-*-* } { "-Os" } { "" } } */


  parent reply	other threads:[~2011-10-10  9:06 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-43829-4@http.gcc.gnu.org/bugzilla/>
2011-02-07 18:53 ` mikael at gcc dot gnu.org
2011-02-07 18:58 ` mikael at gcc dot gnu.org
2011-03-01 15:41 ` dominiq at lps dot ens.fr
2011-03-04 23:15 ` mikael at gcc dot gnu.org
2011-10-04 13:18 ` matz at gcc dot gnu.org
2011-10-04 16:05 ` paul.richard.thomas at gmail dot com
2011-10-04 21:57 ` mikael at gcc dot gnu.org
2011-10-05  6:41 ` paul.richard.thomas at gmail dot com
2011-10-05 14:11 ` burnus at gcc dot gnu.org
2011-10-05 18:12 ` mikael at gcc dot gnu.org
2011-10-08 16:28 ` mikael at gcc dot gnu.org
2011-10-08 16:31 ` mikael at gcc dot gnu.org
2011-10-08 17:58 ` mikael at gcc dot gnu.org
2011-10-09  9:48 ` paul.richard.thomas at gmail dot com
2011-10-09 16:02 ` dominiq at lps dot ens.fr
2011-10-09 16:45 ` mikael at gcc dot gnu.org
2011-10-10  9:06 ` rguenther at suse dot de [this message]
2011-11-04  0:31 ` mikael at gcc dot gnu.org
2011-11-04  0:46 ` mikael at gcc dot gnu.org
2011-11-04  1:08 ` mikael at gcc dot gnu.org
2011-11-04  1:11 ` mikael at gcc dot gnu.org
2011-11-26  6:51 ` mikael at gcc dot gnu.org
2012-03-04 19:14 ` mikael at gcc dot gnu.org
2010-04-21 12:24 [Bug fortran/43829] New: " rguenth at gcc dot gnu dot org
2010-04-21 13:08 ` [Bug fortran/43829] " rguenth at gcc dot gnu dot org
2010-04-21 14:27 ` rguenth at gcc dot gnu dot org
2010-04-22  8:35 ` rguenth at gcc dot gnu dot org
2010-04-22 14:00 ` rguenth at gcc dot gnu dot org
2010-04-22 15:40 ` rguenth at gcc dot gnu dot org
2010-04-23 16:09 ` rguenth at gcc dot gnu dot org
2010-05-04 23:08 ` mikael at gcc dot gnu dot org
2010-05-05  5:08 ` pault at gcc dot gnu dot org
2010-05-05 15:44 ` rguenth at gcc dot gnu dot org
2010-05-22 19:36 ` mikael at gcc dot gnu dot org
2010-06-25  9:28 ` mikael at gcc dot gnu dot org
2010-06-25  9:34 ` mikael at gcc dot gnu dot org
2010-06-25  9:37 ` mikael at gcc dot gnu dot org
2010-06-25  9:42 ` mikael at gcc dot gnu dot org
2010-06-25  9:45 ` rguenther at suse dot de
2010-06-25 22:09 ` dominiq at lps dot ens dot fr
2010-06-26  9:06 ` mikael at gcc dot gnu dot org
2010-06-27 12:42 ` mikael at gcc dot gnu dot org
2010-06-27 12:50 ` mikael at gcc dot gnu dot org
2010-06-27 19:20 ` dominiq at lps dot ens dot fr
2010-06-27 19:45 ` burnus at gcc dot gnu dot org
2010-06-27 20:05 ` dominiq at lps dot ens dot fr
2010-06-27 21:30 ` dominiq at lps dot ens dot fr
2010-06-28  4:28 ` paul dot richard dot thomas at gmail dot com
2010-06-28  9:36 ` rguenth at gcc dot gnu dot org
2010-09-08 11:29 ` dominiq at lps dot ens dot fr
2010-09-08 17:21 ` mikael at gcc dot gnu dot org
2010-09-13  9:09 ` dominiq at lps dot ens dot fr
2010-09-13 17:10 ` mikael 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-43829-4-uRvKFOBbb5@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).