public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/39276]  New: [lto] - Testsuite gcc.log shows many "getconf: Invalid argument (_NPROCESSORS_ONLN)"
Date: Mon, 23 Feb 2009 16:13:00 -0000	[thread overview]
Message-ID: <bug-39276-13830@http.gcc.gnu.org/bugzilla/> (raw)

# gcc/xgcc -v
Using built-in specs.
COLLECT_GCC=gcc/xgcc
Target: i386-pc-solaris2.11
Configured with: ../lto_trunk/configure --prefix=/usr/local/lto
--enable-languages=lto,c++ --enable-shared --disable-static --enable-multilib
--with-gnu-as --with-as=/usr/local/bin/as --with-gnu-ld
--with-ld=/usr/local/bin/ld --with-gmp=/usr/local --with-mpfr=/usr/local
--without-ppl
Thread model: posix
gcc version 4.4.0 20090218 (experimental) [lto revision 144375] (lto merged
with rev 144262) 


The Testsuite gcc.log shows many "getconf: Invalid argument 
(_NPROCESSORS_ONLN)" errors. Here is one example:

PASS: gcc.c-torture/execute/builtins/20010124-1.c execution,  -O0 -flto 
Executing on host: /usr/share/src/lto_build/gcc/xgcc
-B/usr/share/src/lto_build/gcc/
/usr/share/src/lto_trunk/gcc/testsuite/gcc.c-torture/execute/builtins/20010124-1.c
/usr/share/src/lto_trunk/gcc/testsuite/gcc.c-torture/execute/builtins/20010124-1-lib.c
/usr/share/src/lto_trunk/gcc/testsuite/gcc.c-torture/execute/builtins/lib/main.c
 -w  -O0 -fwhopr   -lm   -o
/usr/share/src/lto_build/gcc/testsuite/gcc/20010124-1.x1    (timeout = 300)
getconf: Invalid argument (_NPROCESSORS_ONLN)


/usr/share/src/lto_build/gcc/ltrans-driver[99]: [: argument expected


output is:
getconf: Invalid argument (_NPROCESSORS_ONLN)


/usr/share/src/lto_build/gcc/ltrans-driver[99]: [: argument expected


FAIL: gcc.c-torture/execute/builtins/20010124-1.c compilation,  -O0 -fwhopr 
UNRESOLVED: gcc.c-torture/execute/builtins/20010124-1.c execution,  -O0 -fwhopr 


On Solaris if you execute this, you get this:

# /usr/bin/getconf _NPROCESSORS_ONLN
getconf: Invalid argument (_NPROCESSORS_ONLN)

# /usr/xpg4/bin/getconf _NPROCESSORS_ONLN 
getconf: Invalid argument (_NPROCESSORS_ONLN)


But, if you execute this, you get this:

# /bin/ksh93 -c getconf | grep NPROCESSORS_ONLN
NPROCESSORS_ONLN=1

# /bin/ksh93 -c "getconf NPROCESSORS_ONLN"
1


The last result is probably what is wanted.

Rob


-- 
           Summary: [lto] - Testsuite gcc.log shows many "getconf: Invalid
                    argument (_NPROCESSORS_ONLN)"
           Product: gcc
           Version: lto
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rob1weld at aol dot com
 GCC build triplet: i386-pc-solaris2.11
  GCC host triplet: i386-pc-solaris2.11
GCC target triplet: i386-pc-solaris2.11


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


             reply	other threads:[~2009-02-23 16:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23 16:13 rob1weld at aol dot com [this message]
2009-02-23 16:48 ` [Bug c/39276] " rob1weld at aol dot com
2009-02-23 17:05 ` rob1weld at aol dot com
2009-02-23 17:29 ` [Bug driver/39276] " pinskia at gcc dot gnu dot org
2009-02-23 17:33 ` dnovillo at google dot com
2009-02-24 16:54 ` [Bug c/39276] " rob1weld at aol dot com
2009-07-09  0:11 ` [Bug lto/39276] " bje at gcc dot gnu dot org
2009-07-09 20:50 ` ro at gcc dot gnu dot org
2009-09-16 13:39 ` rguenth at gcc dot gnu dot org
2009-09-17  9:08 ` rguenth at gcc dot gnu dot org
2009-09-22 11:28 ` rguenth at gcc dot gnu dot org
2009-09-22 11:30 ` rguenth at gcc dot gnu dot org
2009-09-25 23:58 ` rob1weld at aol 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-39276-13830@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).