From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30174 invoked by alias); 13 May 2014 19:02:42 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 30108 invoked by uid 48); 13 May 2014 19:02:38 -0000 From: "jmichae3 at yahoo dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61121] -ftree-parallelize-loops=n (n as value) not accepted in 4.9.0 Date: Tue, 13 May 2014 19:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jmichae3 at yahoo dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-05/txt/msg01227.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61121 --- Comment #4 from Jim Michaels --- which means to me it takes only a constant. it should be able to take the equivalent of "auto" (however the gcc folk want to write that), again due to the wide difference between processors. for targeting public machines, you can't assume they are all the same (can't assume they all have 4 threads - some machines are dual-core). I *think* the value 0 does the equivalent of auto, but still testing this. if this is working, it should be documented as such. -ftree-parallelize-loops=@var{n} is not in the manual. alsdo, according to the HTML documentation at https://gcc.gnu.org/onlinedocs/gcc-4.9.0/gcc/Optimize-Options.html#Optimize-Options n is not in a different font.