public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jmichae3 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61121] -O2 -ftree-parallelize-loops=0 for maximum not accepted in 4.9.0
Date: Fri, 20 Jun 2014 13:24:00 -0000	[thread overview]
Message-ID: <bug-61121-4-ERGkjtLjcw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61121-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61121

Jim Michaels <jmichae3 at yahoo dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|-ftree-parallelize-loops=n  |-O2
                   |(n as value) not accepted   |-ftree-parallelize-loops=0
                   |in 4.9.0                    |for maximum not accepted in
                   |                            |4.9.0

--- Comment #6 from Jim Michaels <jmichae3 at yahoo dot com> ---
changed title to something more appropriate since value is always numeric. so
give 0 a special meaning. really, there is always a minimum of 1 thread. so the
value 0 could be used for the max number of threads on the system or ther max
number of threads on the system -1 (1 for the OS to use as a NICE factor).


  parent reply	other threads:[~2014-06-20 13:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 23:47 [Bug c++/61121] New: -ftree-parallelize-loops=n (n as value) " jmichae3 at yahoo dot com
2014-05-08 23:52 ` [Bug c++/61121] " jmichae3 at yahoo dot com
2014-05-08 23:59 ` jmichae3 at yahoo dot com
2014-05-09  7:08 ` jakub at gcc dot gnu.org
2014-05-13 19:02 ` jmichae3 at yahoo dot com
2014-06-20 13:21 ` jmichae3 at yahoo dot com
2014-06-20 13:24 ` jmichae3 at yahoo dot com [this message]
2014-06-20 13:57 ` [Bug c++/61121] -O2 -ftree-parallelize-loops=0 for maximum " jmichae3 at yahoo dot com
2014-07-10 20:56 ` jmichae3 at yahoo dot com

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-61121-4-ERGkjtLjcw@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).