public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: doko@debian.org
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: target/9074: [alpha-linux] gcc fails to compile kernel on wildfire
Date: Fri, 27 Dec 2002 15:56:00 -0000	[thread overview]
Message-ID: <E18S4Gt-0003rJ-00@tango.net.local> (raw)


>Number:         9074
>Category:       target
>Synopsis:       [alpha-linux] gcc fails to compile kernel on wildfire
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Fri Dec 27 15:56:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     herbert@gondor.apana.org.au
>Release:        3.2.2 CVS 021212 (Debian) (Debian unstable)
>Organization:
The Debian Project
>Environment:
System: Debian GNU/Linux (unstable)
Architecture: alpha
host: alpha-linux
Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,proto,pascal,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm --enable-objc-gc alpha-linux
Thread model: posix
gcc version 3.2.2 20021212 (Debian prerelease)
>Description:
[ Reported to the Debian BTS as report #172090.
  Please CC 172090@bugs.debian.org on replies.
  Log of report can be found at http://bugs.debian.org/172090 ]
	

Compiling the kernel for the Wildfire fails with:

herbert@cardolan:/mnt/home/herbert/src/debian/work/kernel/build/2.4/kernel-image-alpha-2.4/build-wildfire/drivers/char$ /usr/lib/gcc-lib/alpha-linux/3.2.2/cc1 -lang-c -nostdinc -v -I/mnt/big/herbert/build/kernel/2.4/kernel-image-alpha-2.4/build-wildfire/include -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=0 -D__GXX_ABI_VERSION=102 -D__gnu_linux__ -Dlinux -Dunix -D_LONGLONG -D__alpha__ -D__ELF__ -D__gnu_linux__ -D__linux__ -D__unix__ -D_LONGLONG -D__alpha__ -D__ELF__ -D__linux -D__unix -Asystem=linux -D__OPTIMIZE__ -D__STDC_HOSTED__=1 -D__LANGUAGE_C__ -D__LANGUAGE_C -DLANGUAGE_C -Acpu=alpha -Amachine=alpha -D__alpha -D__alpha__ -D__alpha_ev6__ -Acpu=ev6 -D__alpha_bwx__ -Acpu=bwx -D__alpha_max__ -Acpu=max -D__alpha_fix__ -Acpu=fix -D__alpha_cix__ -Acpu=cix -D__KERNEL__ -DMODULE -DMODVERSIONS -DKBUILD_BASENAME=istallion -include /mnt/big/herbert/build/kernel/2.4/kernel-image-alpha-2.4/build-wildfire/include/linux/modversions.h -iwithprefix include istallion.c -quiet -d!
umpbase istallion.c -mno-fp-regs -mcpu=ev67 -O2 -Wall -Wstrict-prototypes -Wno-trigraphs -version -fno-strict-aliasing -fno-common -fomit-frame-pointer -ffixed-8
GNU CPP version 3.2.2 20021202 (Debian prerelease) (cpplib) (Alpha GNU/Linux for ELF)
GNU C version 3.2.2 20021202 (Debian prerelease) (alpha-linux)
        compiled by GNU C version 3.2.2 20021202 (Debian prerelease).
#include "..." search starts here:
#include <...> search starts here:
 /mnt/big/herbert/build/kernel/2.4/kernel-image-alpha-2.4/build-wildfire/include
 /usr/lib/gcc-lib/alpha-linux/3.2.2/include
End of search list.
istallion.c: In function `stli_allocbrd':
istallion.c:4738: warning: int format, different type arg (arg 2)
istallion.c: In function `stli_memread':
istallion.c:4895: unable to find a register to spill in class `R27_REG'
istallion.c:4895: this is the insn:
(insn 191 423 192 (parallel[
            (set (reg:DI 2 $2 [123])
                (umod:DI (reg:DI 24 $24 [122])
                    (reg:DI 25 $25 [117])))
            (clobber (reg:DI 23 $23))
            (clobber (reg:DI 28 $28))
        ] ) 37 {*divmoddi_internal_er} (insn_list 189 (insn_list 184 (insn_list:REG_DEP_ANTI 180 (nil))))
    (expr_list:REG_DEAD (reg:DI 24 $24 [122])
        (expr_list:REG_UNUSED (reg:DI 23 $23)
            (expr_list:REG_UNUSED (reg:DI 28 $28)
                (nil)))))
istallion.c:4895: confused by earlier errors, bailing out

The compile works if the kernel is configured as generic as opposed to Wildfire.

[attaching the preprocessed source in a followup mail]

>How-To-Repeat:
	
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-12-27 23:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-27 15:56 doko [this message]
2003-02-10  1:56 Falk Hueffner

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=E18S4Gt-0003rJ-00@tango.net.local \
    --to=doko@debian.org \
    --cc=172090@bugs.debian.org \
    --cc=debian-gcc@lists.debian.org \
    --cc=gcc-gnats@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).