Assembler problem(?) when compiling SysVinit.

Assembler problem(?) when compiling SysVinit.

[Øystein Johansen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]

Hi!

(I'm not sure if this is the right mailinglist to ask this question,
but I don't know any other place to ask. As a matter of fact, I'm not
even sure the assembler is the problem..)

I've builded native Linux binutils an native linux gcc-2.95 from a
Cygwin cross-compiler. When I'm tring to compile SysVinit-2.77, 
I get this message:

$ make
gcc -c -Wall -O2 -D_GNU_SOURCE init.c
init.c: In function `console_open':
init.c:478: warning: `fd' might be used uninitialized in this function
init.c: In function `check_pipe':
init.c:1757: Invalid `asm' statement:
init.c:1757: fixed or forbidden register 2 (cx) was spilled for class
CREG.
init.c: In function `check_init_fifo':
init.c:1964: Invalid `asm' statement:
init.c:1964: fixed or forbidden register 2 (cx) was spilled for class
CREG.
make: *** [init.o] Error 1

At this lines (1757 and 1964) the program calls a macro called FD_SET.

Is this a bug in the assembler or gcc-2.95? A error in my setup?
An error in SysVinit?

I also get the same kind of error message when I'm trying to cross-
compile the SysVinit on the Cygwin computer.

Thanks,
-Øystein

BTW: I'm using glibc-2.0

Re: Assembler problem(?) when compiling SysVinit.

[Ian Lance Taylor]

   Date: Fri, 27 Aug 1999 21:44:34 +0200
   From: =?iso-8859-1?Q?=D8ystein?= Johansen <oeysteij@online.no>

   (I'm not sure if this is the right mailinglist to ask this question,
   but I don't know any other place to ask. As a matter of fact, I'm not
   even sure the assembler is the problem..)

The assembler is not the problem.

   gcc -c -Wall -O2 -D_GNU_SOURCE init.c
   init.c: In function `console_open':
   init.c:478: warning: `fd' might be used uninitialized in this function
   init.c: In function `check_pipe':
   init.c:1757: Invalid `asm' statement:
   init.c:1757: fixed or forbidden register 2 (cx) was spilled for class
   CREG.
   init.c: In function `check_init_fifo':
   init.c:1964: Invalid `asm' statement:
   init.c:1964: fixed or forbidden register 2 (cx) was spilled for class
   CREG.
   make: *** [init.o] Error 1

   At this lines (1757 and 1964) the program calls a macro called FD_SET.

   Is this a bug in the assembler or gcc-2.95? A error in my setup?
   An error in SysVinit?

The bug is either in gcc or (more likely) in the inline assembler code
in question.  The bug is not in the assembler; the assembler is not
even being run.

Ian

Re: Assembler problem(?) when compiling SysVinit.

[Jeffrey A Law]

  In message < 19990829210912.4377.qmail@daffy.airs.com >you write:
  >    Date: Fri, 27 Aug 1999 21:44:34 +0200
  >    From: =?iso-8859-1?Q?=D8ystein?= Johansen <oeysteij@online.no>
  > 
  >    (I'm not sure if this is the right mailinglist to ask this question,
  >    but I don't know any other place to ask. As a matter of fact, I'm not
  >    even sure the assembler is the problem..)
  > 
  > The assembler is not the problem.
  > 
  >    gcc -c -Wall -O2 -D_GNU_SOURCE init.c
  >    init.c: In function `console_open':
  >    init.c:478: warning: `fd' might be used uninitialized in this function
  >    init.c: In function `check_pipe':
  >    init.c:1757: Invalid `asm' statement:
  >    init.c:1757: fixed or forbidden register 2 (cx) was spilled for class
  >    CREG.
  >    init.c: In function `check_init_fifo':
  >    init.c:1964: Invalid `asm' statement:
  >    init.c:1964: fixed or forbidden register 2 (cx) was spilled for class
  >    CREG.
  >    make: *** [init.o] Error 1
  > 
  >    At this lines (1757 and 1964) the program calls a macro called FD_SET.
  > 
  >    Is this a bug in the assembler or gcc-2.95? A error in my setup?
  >    An error in SysVinit?
  > 
  > The bug is either in gcc or (more likely) in the inline assembler code
  > in question.  The bug is not in the assembler; the assembler is not
  > even being run.
It's a bogus asm statement.  This is covered in the gcc/egcs FAQ.

jeff