Bug#202762: gcc-3.3: fails to compile kernel 2.4.22-pre8 on alpha

2003-07-25 Thread Matthias Klose
root writes: Package: gcc-3.3 Version: 1:3.3.1-0rc1 Severity: normal trying to compile kernel 2.4.22-pre8 on alpha i get: fork.c: In function `dup_mmap': fork.c:144: error: unrecognizable insn: (insn 59 52 61 0 0x2ce7760 (set (reg/f:DI 82) (symbol_ref:DI (@Smmlist_nr))) -1

Bug#202774: marked as done (g++-3.3: Doesn't link default compiler)

2003-07-25 Thread Debian Bug Tracking System
Your message dated Fri, 25 Jul 2003 08:25:42 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#202774: g++-3.3: Doesn't link default compiler has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#202859: [mips] branch out of range when building fold-const.c

2003-07-25 Thread Guido Guenther
Subject: gcc-3.3: [mips] branch out of range when building mips64-linux gcc Package: gcc-3.3 Version: 1:3.3.1-0rc1 Severity: normal Hi, when building a mips-linux - mips64-linux crosscompiler current gcc creates assembler code as can't handle (Branch out of range) The miscompiled file is

Bug#202746: gcc: -O2 causes bogutil to segfault

2003-07-25 Thread Clint Adams
[this message only refers to testing that was only done on hppa] - does it work with gcc-3.2? - does it work with gcc-snapshot? No, with -O2 it breaks on gcc-3.23.2.3-6 gcc-3.33.3.1-0rc1 gcc-snapshot 20030722-1 - can you identify the file beeing miscompiled? No, I don't

Bug#202746: gcc: -O2 causes bogutil to segfault

2003-07-25 Thread Clint Adams
- can you identify the file beeing miscompiled? No, I don't seem to be able to do that. If I compile with -O1, it works. If I compile with -O2, it segfaults. If I compile all objects -O2 except the ones that seem to be relevant in the backtrace, it still segfaults. (Also tried with

Bug#200619: [parisc-linux] Re: Bug#200619: gcc: parisc: compiling dietlibc-dev with -Os caus

2003-07-25 Thread John David Anglin
This doesn't appear to be a gcc problem. The register %r3 is saved on the stack in __stdio_init_file_nothreads. The stack location is clobbered by the fstat syscall. + { +struct stat st; +fstat(fd,st); At the fstat call we have the following values: Breakpoint 11,