[Bug target/13722] [3.4/3.5 regression] [ia64] ICE in push_secondary_reload
--- Additional Comments From wilson at specifixinc dot com 2004-01-25 07:40 --- Subject: Re: PR 13722 candidate fix My latest bootstrap succeeded. I didn't run the testsuite, and I still had some debug code in there just to be safe, but I don't think either of those issues should matter. With the following patch on top of your patches, the IA-64 gcc port bootstrap again including Ada. This patch adds the REG_INC notes for auto-inc addresses in the IN operands. There is also the potential problem I pointed out earlier where we use INTVAL without checking to see if we have a CONST_INT. That isn't in this patch, but I think it should go in also. At this point, I would like to ask a favor. I have 3 IA-64 binutils bugs which need to be fixed, two of which are over a week old now, and 2 IA-64 gcc bugs that I need to respond to. I was hoping to work on them this week and/or weekend, but I ended up spending a lot of time helping you with your patch. I would appreciate being given some time to work on these problems without having to worry about the IA-64 compiler breaking. So what I am asking here is that if you check in a patch that breaks the IA-64 compiler, and you are not able to solve the problem yourself, that you revert the patch until I am able to help you. I am willing to help you with these kinds of things, but it isn't fair to others to let you monopolize my time, and it isn't fair to others to leave the IA-64 compiler broken for long periods of time. If you want to be really helpful, you could try looking at some of the IA-64 gcc bug reports in bugzilla. PR 7198 is on my list, and is one that you could handle. --- Additional Comments From wilson at specifixinc dot com 2004-01-25 07:40 --- Created an attachment (id=5570) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=5570&action=view) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13722 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
Processed: Re: Bug#218710: It seems this issue is fixed?
Processing commands for [EMAIL PROTECTED]: > tags 218710 - wontfix confirmed Bug#218710: gnumeric: FTBFS with gcc 2.95 Tags were: wontfix confirmed Tags removed: wontfix, confirmed > reassign 218710 gcc-2.95 Bug#218710: gnumeric: FTBFS with gcc 2.95 Bug reassigned from package `gnumeric' to `gcc-2.95'. > retitle 218710 [Regression from 2.95.3?] Fails to build gnumeric 1.2.5 with > "initializer element is not computable at load time" error on translatable > constant strings Bug#218710: gnumeric: FTBFS with gcc 2.95 Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#229567: gcc-3.3: Miscompile with -O -funroll-loops on powerpc
Package: gcc-3.3 Version: 1:3.3.3-0pre2 Severity: normal When complied with -O -funroll-loops on powerpc, the attached test.i produces the following output: Bytes in main: 0 1 Bytes in: 0 1 0 1 0 1 ( 0 10 15 254) x = 282 Bytes in: 0 1 0 1 0 1 ( 94 52 15 254) x = 418 Bytes in: 0 1 0 1 0 1 ( 7 208 15 254) x = 487 The reported x's should be the sum of the first six numbers on the line above. Instead, it is the sum of _all_ the numbers on the line above. Changing -O to -O2, or removing -funroll-loops generates the following (correct) result: Bytes in main: 0 1 Bytes in: 0 1 0 1 0 1 ( 70 148 15 234) x = 3 Bytes in: 0 1 0 1 0 1 ( 0 10 15 254) x = 3 Bytes in: 0 1 0 1 0 1 ( 7 76 15 234) x = 3 On 386, this problem does not occur. Note that this could be the same bug as PR13222, in which case this would be a nice, small, test case. I have not actually looked at the test case in PR13222 however, since it is rather large. The result of gcc -v --save-temps -O -funroll-loops test.c 2> ~/output.txt is below: *** output.txt Reading specs from /usr/lib/gcc-lib/powerpc-linux/3.3.3/specs Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc --disable-multilib powerpc-linux Thread model: posix gcc version 3.3.3 20040110 (prerelease) (Debian) /usr/lib/gcc-lib/powerpc-linux/3.3.3/cc1 -E -quiet -v -D__GNUC__=3 -D__GNUC_MINOR__=3 -D__GNUC_PATCHLEVEL__=3 -D__unix__ -D__gnu_linux__ -D__linux__ -Dunix -D__unix -Dlinux -D__linux -Asystem=unix -Asystem=posix test.c -funroll-loops -O test.i ignoring nonexistent directory "/usr/powerpc-linux/include" #include "..." search starts here: #include <...> search starts here: /usr/local/include /usr/lib/gcc-lib/powerpc-linux/3.3.3/include /usr/include End of search list. /usr/lib/gcc-lib/powerpc-linux/3.3.3/cc1 -fpreprocessed test.i -quiet -dumpbase test.c -auxbase test -O -version -funroll-loops -o test.s GNU C version 3.3.3 20040110 (prerelease) (Debian) (powerpc-linux) compiled by GNU C version 3.3.3 20040110 (prerelease) (Debian). GGC heuristics: --param ggc-min-expand=72 --param ggc-min-heapsize=80371 as -mppc -V -Qy -o test.o test.s GNU assembler version 2.14.90.0.7 (powerpc-linux) using BFD version 2.14.90.0.7 20031029 Debian GNU/Linux /usr/lib/gcc-lib/powerpc-linux/3.3.3/collect2 --eh-frame-hdr -V -Qy -m elf32ppclinux -dynamic-linker /lib/ld.so.1 /usr/lib/gcc-lib/powerpc-linux/3.3.3/../../../crt1.o /usr/lib/gcc-lib/powerpc-linux/3.3.3/../../../crti.o /usr/lib/gcc-lib/powerpc-linux/3.3.3/crtbegin.o -L/usr/lib/gcc-lib/powerpc-linux/3.3.3 -L/usr/lib/gcc-lib/powerpc-linux/3.3.3/../../.. test.o -lgcc -lgcc_eh -lc -lgcc -lgcc_eh /usr/lib/gcc-lib/powerpc-linux/3.3.3/crtsavres.o /usr/lib/gcc-lib/powerpc-linux/3.3.3/crtend.o /usr/lib/gcc-lib/powerpc-linux/3.3.3/../../../crtn.o GNU ld version 2.14.90.0.7 20031029 Debian GNU/Linux Supported emulations: elf32ppclinux elf32ppc elf32ppcsim elf64ppc -- System Information: Debian Release: testing/unstable Architecture: powerpc Kernel: Linux pomme 2.4.23-ben1-mvz1 #3 Mon Jan 5 19:04:27 CET 2004 ppc Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 Versions of packages gcc-3.3 depends on: ii binutils 2.14.90.0.7-3 The GNU assembler, linker and bina ii cpp-3.31:3.3.3-0pre2 The GNU C preprocessor ii gcc-3.3-base 1:3.3.3-0pre2 The GNU Compiler Collection (base ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an ii libgcc11:3.3.3-0pre2 GCC support library -- no debconf information # 1 "test.c" # 1 "" # 1 "" # 1 "test.c" # 24 "test.c" # 1 "/usr/include/stdio.h" 1 3 4 # 28 "/usr/include/stdio.h" 3 4 # 1 "/usr/include/features.h" 1 3 4 # 295 "/usr/include/features.h" 3 4 # 1 "/usr/include/sys/cdefs.h" 1 3 4 # 296 "/usr/include/features.h" 2 3 4 # 318 "/usr/include/features.h" 3 4 # 1 "/usr/include/gnu/stubs.h" 1 3 4 # 319 "/usr/include/features.h" 2 3 4 # 29 "/usr/include/stdio.h" 2 3 4 # 1 "/usr/lib/gcc-lib/powerpc-linux/3.3.3/include/stddef.h" 1 3 4 # 213 "/usr/lib/gcc-lib/powerpc-linux/3.3.3/include/stddef.h" 3 4 typedef unsigned int size_t; # 35 "/usr/include/stdio.h" 2 3 4 # 1 "/usr/include/bits/types.h" 1 3 4 # 28 "/usr/include/bits/types.h" 3 4 # 1 "/usr/include/bits/wordsize.h" 1 3 4 # 29 "/usr/include/bits/types.h" 2 3 4 # 1 "/usr/lib/gcc-lib/powerpc-linux/3.3.3/include/stddef.h" 1 3 4 # 32 "/usr/include/bits/types.h" 2 3 4 typedef unsigned char __u_char; typedef unsigned short int __u_short; typedef unsigned int __u_int; typedef unsigned long int __u_long; typedef signed char __int8_t; typedef unsigned char __uint8_t; typedef signed short int __int16_t; type
Bug#229567: gcc-3.3: Miscompile with -O -funroll-loops on powerpc
Matijs van Zuijlen writes: > Package: gcc-3.3 > Version: 1:3.3.3-0pre2 > Severity: normal > > When complied with -O -funroll-loops on powerpc, the attached test.i > produces the following output: > > Bytes in main: 0 1 > Bytes in: 0 1 0 1 0 1 ( 0 10 15 254) > x = 282 > Bytes in: 0 1 0 1 0 1 ( 94 52 15 254) > x = 418 > Bytes in: 0 1 0 1 0 1 ( 7 208 15 254) > x = 487 > > The reported x's should be the sum of the first six numbers on the line > above. Instead, it is the sum of _all_ the numbers on the line above. > Changing -O to -O2, or removing -funroll-loops generates the following > (correct) result: > > Bytes in main: 0 1 > Bytes in: 0 1 0 1 0 1 ( 70 148 15 234) > x = 3 > Bytes in: 0 1 0 1 0 1 ( 0 10 15 254) > x = 3 > Bytes in: 0 1 0 1 0 1 ( 7 76 15 234) > x = 3 > > On 386, this problem does not occur. > > Note that this could be the same bug as PR13222, in which case this would > be a nice, small, test case. I have not actually looked at the test case > in PR13222 however, since it is rather large. please could you recheck with other compiler versions, i.e. gcc-snapshot (if it's fixed upstream), gcc-3.2, gcc-2.95 (to check if the bug is a regression) Thanks, Matthias
Bug#227894: No error when using older kernel
reassign 227894 kernel-tree-2.6.0 thanks I'm sure Herbert will properly reassign this or close the report ... Gunther Laure writes: > I just booted an older kernel 2.4.22. > At this version everything works as expected! Valgrind reports no > errors! This error now maybe has to be transferred to the valgrind or > kernel 2.6 bug page. > > Bye Gunther
Re: arm cross-compiler ICE report
Nikita V. Youshchenko writes: > Hello. > > Some time ago I posted a patch for gcc-3.3 source package that enables > cross-compiler build. > > Using that patch, I built cross-compilers for arm-linux and started to use > them to build software for my Ipaq. > > Today I've got an ICE. > > I was able to cut down the problematic file and to create somewhat minimal > example that reproceses ICE. It even contains no #include's :) > > However, I don't know how to report such bugs correctly. > It seems to be incorrect to report the bug to upstream gcc, because the > cross-compiler it is bult from Debain package and contains Debian patches. > It seems to be incorrect to report the bug to Debain BTS, because Debian > curently does not support gcc cross-compilers. The best thing to report upstream would be to comment out arm specific and maybe some other patches in debian/rules.patch. I'm unsure about who is interested on reports on the Debian side ... maybe the arm maintainers?
Processed: gcc: submitted Debian report #229088 to gcc-gnats as PR 13857
Processing commands for [EMAIL PROTECTED]: > # submitted Debian report #229088 to gcc-gnats as PR 13857 > # http://gcc.gnu.org/PR13857 > forwarded 229088 http://gcc.gnu.org/PR13857 Bug#229088: g++-3.3: nested namespaces error msg Noted your statement that Bug has been forwarded to http://gcc.gnu.org/PR13857. > retitle 229088 [PR 13857] nested namespaces error msg Bug#229088: g++-3.3: nested namespaces error msg Changed Bug title. > tags 229088 + upstream Bug#229088: [PR 13857] nested namespaces error msg There were no tags set. Tags added: upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
[Bug c++/13857] nested namespaces error msg
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-01-25 15:55 --- Confirmed but not a regression. -- What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed||1 Keywords||diagnostic Last reconfirmed|-00-00 00:00:00 |2004-01-25 15:55:10 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13857 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter.
[Bug c++/13857] nested namespaces error msg
--- Additional Comments From gdr at integrable-solutions dot net
2004-01-25 15:55 ---
Subject: Re: New: nested namespaces error msg
"debian-gcc at lists dot debian dot org" <[EMAIL PROTECTED]> writes:
| [forwarded from http://bugs.debian.org/229088]
|
| seen in 3.3.3 and 3.4 CVS
|
| In this example the error message mentions the wrong namespace:
|
|
| namespace outer { namespace inner { void foo(); } }
|
| void outer::foo()
| {
| // error: `void outer::foo()' should have been declared inside `outer'
| }
I don't understand this report. As far as I can tell, the error
message is correct. You cannot define something as being part of a
namespace (using a qualified-id) if it wasn't previously declared
there. You can perfectly have outer::foo and outer::inner::foo.
The compiler is not telepathic.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13857
--- You are receiving this mail because: ---
You reported the bug, or are watching the reporter.
[Bug c++/13857] nested namespaces error msg
--- Additional Comments From gdr at integrable-solutions dot net 2004-01-25 16:00 --- Subject: Re: nested namespaces error msg "pinskia at gcc dot gnu dot org" <[EMAIL PROTECTED]> writes: | Confirmed but not a regression. It is not even a bug. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13857 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter.
Processed: Re: Bug#227894: No error when using older kernel
Processing commands for [EMAIL PROTECTED]: > reassign 227894 kernel-tree-2.6.0 Bug#227894: g++ exceptions thrown -> valgrind signals invalid read Bug reassigned from package `g++' to `kernel-tree-2.6.0'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
[Bug c++/13857] nested namespaces error msg
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-01-25 16:04 --- I had to reread the report but I now agree with Gaby that the error is right and there is no way for GCC to read your mind. -- What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13857 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter.
Re: News on bug # 225621 (invalid assembly on m68k) against g77-3.3?
Kevin B. McCarty writes: > Hi all, > I am just wondering if bug # 225621 (g77-3.3: sometimes generates invalid > assembly code on m68k) has been noticed, since I haven't seen it mentioned > anywhere on these mailing lists. Apologies if I'm being redundant. it needs to be rechecked using gcc-snapshot and forwarded upstream. any volunteers?
Processed: Re: Bug#192135: [Bug ada/10889] Convention Fortran matrices mishandled in generics
Processing commands for [EMAIL PROTECTED]: > retitle 192135 [fixed in 3.5] [Bug ada/10889] Convention Fortran matrices > mishandled in generics Bug#192135: [PR 10889] Convention Fortran matrices mishandled in generics Changed Bug title. > tags 192135 + fixed-upstream Bug#192135: [fixed in 3.5] [Bug ada/10889] Convention Fortran matrices mishandled in generics Tags were: upstream Tags added: fixed-upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#228421: gcc 3.0.4 generates bad code on Debian 3.0/PARISC
tags 228421 + woody
tags 228421 + fixed-upstream
thanks
Well, maybe a recompilation and binary NMU for apache would suffice?
Should the report be reassignd to apache?
Willy Tarreau writes:
> Package: gcc
> Version: 2:3.0.4-5
>
> Kernel: Linux hp 2.4.24-pa0 #1 Sun Jan 11 18:48:21 CET 2004 parisc unknown
> glibc: Version: 2.2.5-11.5
>
> GCC 3.0.4 included in Debian 3.0 generates bad code on PARISC platform. The
> original apache 1.3.26 distributed in this port returns lines full of zeroes
> in the size field of the files between 1 and 100 MB :
>
> linux-2.4.20-wt17.tar.bz2 08-Jun-2003 11:05
> 0.M
>
> patch-2.4.20-to-2.4.20-wt17.bz2 08-Jun-2003 11:04
> -0.0M
>
>
> CONTENTS-2.4.20-wt1708-Jun-2003 10:5218k
>
> ... and so on.
>
> So I have recompiled 1.3.29 from sources with gcc-3.0.4, and the problem was
> exactly the same. Digging through the code, I discovered that for exactly
> these files, apache uses a floating point representation for the size, and it
> calls ap_rprintf() which is sort of an sprintf(), with (size/1048576.0) as an
> argument, and "%4.1fM" as the format string.
>
> Replacing the format with "%4eM" gave me something interesting :
>
> linux-2.4.20-wt17.tar.bz2 08-Jun-2003 11:05 8.417643e-53M
> patch-2.4.20-to-2.4.20-wt17.bz2 08-Jun-2003 11:04 1.284430e-57M
> CONTENTS-2.4.20-wt1708-Jun-2003 10:5218k
>
> I've read the complete implementation of ap_rprintf(), and it seems correct
> to me. But some double arguments are passed as va_args at several places. So
> I thought that it could be possible that gcc does not handle this very well.
> Then I recompiled only util_script.c and ap_snprintf.c with gcc-3.3.2, not
> changing anything else, and apache now reports correct sizes :
>
> linux-2.4.20-wt17.tar.bz2 08-Jun-2003 11:05 30.1M
> patch-2.4.20-to-2.4.20-wt17.bz2 08-Jun-2003 11:04 7.2M
> CONTENTS-2.4.20-wt1708-Jun-2003 10:5218k
>
> Now I've found that it's very easy to reproduce. Consider this trivial
> program :
>
> #include
> #include
> main() {
>printf("%4.1f\n", 1.23456);
> }
>
> Now, test it :
>
> # gcc -O2 -o fp-test fp-test.c
> # ./fp-test
> 0.0
> # gcc -O1 -o fp-test fp-test.c
> # ./fp-test
> 1.2
> # gcc-3.3.2-parisc -O2 -o fp-test fp-test.c
> # ./fp-test
> 1.2
>
> # gcc -v
> Reading specs from /usr/lib/gcc-lib/hppa-linux/3.0.4/specs
> Configured with: ../src/configure -v --enable-languages=c,c++,f77,proto,objc
> --prefix=/usr --infodir=/share/info --mandir=/share/man --enable-shared
> --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long
> --enable-nls --without-included-gettext --disable-checking
> --enable-threads=posix --with-cpp-install-dir=bin hppa-linux
> Thread model: posix
> gcc version 3.0.4
>
> # gcc-3.3.2-parisc -v
> Reading specs from /usr/lib/gcc-lib/hppa1.1-hp-linux-gnu/3.3.2/specs
> Configured with: ../gcc-3.3.2/configure --prefix=/usr --with-gnu-ld
> --with-gnu-as --host=hppa1.1-hp-linux-gnu --target=hppa1.1-hp-linux-gnu
> --with-cpu=7100LC --enable-languages=c,c++ --disable-nls --disable-locale
> --enable-shared --enable-target-optspace
> --enable-version-specific-runtime-libs --program-suffix=-3.3.2-parisc
> --enable-threads
> Thread model: posix
> gcc version 3.3.2
>
> So it seems that the work-around simply is to switch back to -O1.
> Unfortunately, I tried about 20 -fno-XXX with -O2 to find the culprit,
> but I couldn't. And I don't remember how I can dump the -O1 and -O2
> equivalents.
>
> I hope I didn't forget anything. At the moment, I don't know if there are
> packages other than apache which have been affected by this bug.
>
> Regards,
> Willy
>
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: News on bug # 225621 (invalid assembly on m68k) against g77-3.3?
> > I am just wondering if bug # 225621 (g77-3.3: sometimes generates invalid > > assembly code on m68k) has been noticed, since I haven't seen it mentioned > > anywhere on these mailing lists. Apologies if I'm being redundant. > > it needs to be rechecked using gcc-snapshot and forwarded > upstream. any volunteers? Is there a recent enough build of gcc-snapshot that can be used? The build tree for cernlib is still on kullervo, so I could use that to verify the bug. Michael
Bug#228099: g++-3.3: exception in constructor of a class to be thrown is not caught
Alexander Motzkau writes:
> Package: g++-3.3
> Version: 1:3.3.2-4
> Severity: normal
>
> Hi there,
>
> Running the following code compiled with 'g++-3.3 testex.cc'
> results in a SIGABRT. I see no reason why this should happen.
> With g++ 3.2 it works, i.e. the exception 1 in A() is caught
> by the try-block.
>
>
> # 1 "testex.cc"
> # 1 ""
> # 1 ""
> # 1 "testex.cc"
> class A
> {
> public:
> A() {throw(1);}
> };
>
> int main(int argc, char *argv)
> {
> try
> {
> throw A();
> }
> catch(...)
> {
> }
> }
is this actually a bug?
gcc-3.4 (CVS 20040113) and 3.5 (CVS 20040113 tree-ssa) are more verbose:
$ /usr/lib/gcc-snapshot/bin/g++ bug-228099.cc &&
LD_LIBRARY_PATH=/usr/lib/gcc-snapshot/lib ./a.out
terminate called after throwing an instance of 'i'
Aborted
$ /usr/lib/gcc-experimental/bin/g++ bug-228099.cc &&
LD_LIBRARY_PATH=/usr/lib/gcc-experimental/lib ./a.out
terminate called without an active exception
Aborted
Bug#228421: gcc 3.0.4 generates bad code on Debian 3.0/PARISC
On Sun, Jan 25, 2004 at 05:36:10PM +0100, Matthias Klose wrote: > tags 228421 + woody > tags 228421 + fixed-upstream > thanks > > Well, maybe a recompilation and binary NMU for apache would suffice? recompiling apache with -O1 is enough, that's what I did here and it works. > Should the report be reassignd to apache? They should be informed of the problem, as well as any other project which uses floating point and which is compiled with -O2 on parisc. But the root of the problem lies in gcc 3.0.4 since it is OK in 3.3.2. So wouldn't it be easier to identify and backport the fix from 3.3.2 to 3.0.4 and inform all projects that they must recompile everything on parisc ? Thanks, Willy
Processed: Re: Bug#228421: gcc 3.0.4 generates bad code on Debian 3.0/PARISC
Processing commands for [EMAIL PROTECTED]: > tags 228421 + woody Bug#228421: gcc 3.0.4 generates bad code on Debian 3.0/PARISC There were no tags set. Tags added: woody > tags 228421 + fixed-upstream Bug#228421: gcc 3.0.4 generates bad code on Debian 3.0/PARISC Tags were: woody Tags added: fixed-upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: tag gcc report
Processing commands for [EMAIL PROTECTED]: > tags 228018 + fixed-upstream Bug#228018: gcc-3.3: [alpha] cc1 Internal error when building fceu-0.97.5 Tags were: upstream Tags added: fixed-upstream > retitle 228018 [fixed in 3.4] [alpha] cc1 Internal error when building > fceu-0.97.5 Bug#228018: gcc-3.3: [alpha] cc1 Internal error when building fceu-0.97.5 Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: Re: [Bug optimization/11635] [3.3/3.4 regression] Unnecessary store onto stack
Processing commands for [EMAIL PROTECTED]: > tags 202016 + fixed-upstream Bug#202016: [PR 11635] [3.3/3.4 regression] Unnecessary store onto stack Tags were: upstream Tags added: fixed-upstream > retitle 202016 [fixed in 3.4] [PR 11635] [3.3/3.4 regression] Unnecessary > store onto stack Bug#202016: [PR 11635] [3.3/3.4 regression] Unnecessary store onto stack Changed Bug title. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#229088: marked as done ([PR 13857] nested namespaces error msg)
Your message dated Sun, 25 Jan 2004 18:26:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line [Bug c++/13857] nested namespaces error msg
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 it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
Received: (at submit) by bugs.debian.org; 22 Jan 2004 22:40:09 +
>From [EMAIL PROTECTED] Thu Jan 22 14:40:09 2004
Return-path: <[EMAIL PROTECTED]>
Received: from roura.ac.upc.es [147.83.33.10]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AjnUf-0005ju-00; Thu, 22 Jan 2004 14:40:09 -0800
Received: from localhost (dync-34-225.ac.upc.es [147.83.34.225])
by roura.ac.upc.es (8.12.8/8.12.8) with ESMTP id i0MMdZ7J004963;
Thu, 22 Jan 2004 23:39:36 +0100 (MET)
Received: from jtv by localhost with local (Exim 3.36 #1 (Debian))
id 1AjnU2-00076o-00; Thu, 22 Jan 2004 23:39:30 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Jeroen T. Vermeulen" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: g++-3.3: nested namespaces error msg
X-Mailer: reportbug 2.37
Date: Thu, 22 Jan 2004 23:39:30 +0100
Message-Id: <[EMAIL PROTECTED]>
Sender: "Jeroen T. Vermeulen" <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_01_20
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no
version=2.60-bugs.debian.org_2004_01_20
X-Spam-Level:
Package: g++-3.3
Version: 1:3.3.3-0pre2
Severity: minor
In this example the error message mentions the wrong namespace:
namespace outer { namespace inner { void foo(); } }
void outer::foo()
{
// error: `void outer::foo()' should have been declared inside `outer'
}
-- System Information:
Debian Release: testing/unstable
Architecture: powerpc
Kernel: Linux bulletproof 2.6.1-ben1-jtv1 #1 Fri Jan 16 01:54:06 CET 2004 ppc
Locale: LANG=en_IN, LC_CTYPE=en_IN
Versions of packages g++-3.3 depends on:
ii gcc-3.31:3.3.3-0pre2 The GNU C compiler
ii gcc-3.3-base 1:3.3.3-0pre2 The GNU Compiler Collection (base
ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an
ii libstdc++5-3.3-dev 1:3.3.3-0pre2 The GNU Standard C++ Library v3 (d
-- no debconf information
---
Received: (at 229088-done) by bugs.debian.org; 25 Jan 2004 17:26:14 +
>From [EMAIL PROTECTED] Sun Jan 25 09:26:14 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Ako1V-00015y-00; Sun, 25 Jan 2004 09:26:14 -0800
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id SAA25952
for <[EMAIL PROTECTED]>; Sun, 25 Jan 2004 18:26:01 +0100 (MET)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id i0PHQ1Ys008551;
Sun, 25 Jan 2004 18:26:01 +0100 (MET)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 25 Jan 2004 18:26:01 +0100
To: [EMAIL PROTECTED]
Subject: Re: [Bug c++/13857] nested namespaces error msg
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_01_24
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=0.0 required=4.0 tests=none autolearn=no
version=2.60-bugs.debian.org_2004_01_24
X-Spam-Level:
gdr at integrable-solutions dot net writes:
>
> --- Additional Comments From gdr at integrable-solutions dot net
> 2004-01-25 16:00 ---
> Subject: Re: nested namespaces error msg
>
> "pinskia at gcc dot gnu dot org" <[EMAIL PROTECTED]> writes:
>
> | Confirmed but not a regression.
>
> It is not even a bug.
pinskia at gcc dot gnu dot org writes:
>
> --- Additional Comments From pinskia at gcc dot gnu dot org 2004-01-25
> 16:04 ---
> I had to reread the report but I now agree with Gaby that the error is right
> and there is no way for
> GCC to read your mind.
Bug#228421: gcc 3.0.4 generates bad code on Debian 3.0/PARISC
On Sun, Jan 25, 2004 at 06:05:17PM +0100, Willy Tarreau wrote: > But the root of the problem lies in gcc 3.0.4 since it is OK in 3.3.2. So > wouldn't it be easier to identify and backport the fix from 3.3.2 to 3.0.4 > and inform all projects that they must recompile everything on parisc ? "recompile everything" == "new release". AFAICT, the "debian way" is to recompile the packages that have bugs filed against them and binNMU (Non-Maintainer-Upload) just those packages. thanks, grant
Bug#222357: tagging gcc woody report
tags 222357 + woody upstream fixed-upstream wontfix thanks maybe you want to build a recent compiler from the current testing distribution? gcc-2.96 has never been tested/used on the alpha on Debian.
Processed: tagging gcc woody report
Processing commands for [EMAIL PROTECTED]: > tags 222357 + woody upstream fixed-upstream wontfix Bug#222357: gcc bug pr9164 present in stable/Alpha There were no tags set. Tags added: woody, upstream, fixed-upstream, wontfix > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#229642: libstdc++5-3.3-doc: no whatis info in some manpages
Package: libstdc++5-3.3-doc Version: 1:3.3.3-0pre2 Severity: normal Hi, here is the problem: $ man -k std:: | grep unknown std::__debug_alloc (3) - (unknown subject) std::__debug_alloc - (3) [std::__debug_alloc] - (unknown subject) std::__default_alloc_template (3) - (unknown subject) std::__default_alloc_template - (3) [std::__default_alloc_template] - (unknown subject) std::__malloc_alloc_template (3) - (unknown subject) std::__malloc_alloc_template - (3) [std::__malloc_alloc_template] - (unknown subject) std::Alloc_traits (3) - (unknown subject) std::Alloc_traits - (3) [std::Alloc_traits] - (unknown subject) std::auto_ptr_ref (3) - (unknown subject) std::auto_ptr_ref - (3) [std::auto_ptr_ref] - (unknown subject) std::bad_exception (3) - (unknown subject) std::bad_exception - (3) [std::bad_exception] - (unknown subject) std::bad_typeid (3) - (unknown subject) std::bad_typeid - (3) [std::bad_typeid] - (unknown subject) std::binary_function (3) - (unknown subject) std::binary_function - (3) [std::binary_function] - (unknown subject) std::bitset::reference - (3) [std::bitset_reference] - (unknown subject) std::bitset_reference (3) - (unknown subject) std::domain_error (3) - (unknown subject) std::domain_error - (3) [std::domain_error] - (unknown subject) std::fpos (3)- (unknown subject) std::fpos - (3) [std::fpos] - (unknown subject) std::invalid_argument (3) - (unknown subject) std::invalid_argument - (3) [std::invalid_argument] - (unknown subject) std::iterator_traits (3) - (unknown subject) std::iterator_traits - (3) [std::iterator_traits] - (unknown subject) std::length_error (3) - (unknown subject) std::length_error - (3) [std::length_error] - (unknown subject) std::new_alloc (3) - (unknown subject) std::new_alloc - (3) [std::new_alloc] - (unknown subject) std::out_of_range (3) - (unknown subject) std::out_of_range - (3) [std::out_of_range] - (unknown subject) std::overflow_error (3) - (unknown subject) std::overflow_error - (3) [std::overflow_error] - (unknown subject) std::range_error (3) - (unknown subject) std::range_error - (3) [std::range_error] - (unknown subject) std::raw_storage_iterator (3) - (unknown subject) std::raw_storage_iterator - (3) [std::raw_storage_iterator] - (unknown subject) std::reverse_iterator (3) - (unknown subject) std::reverse_iterator - (3) [std::reverse_iterator] - (unknown subject) std::simple_alloc (3) - (unknown subject) std::simple_alloc - (3) [std::simple_alloc] - (unknown subject) std::unary_function (3) - (unknown subject) std::unary_function - (3) [std::unary_function] - (unknown subject) std::underflow_error (3) - (unknown subject) std::underflow_error - (3) [std::underflow_error] - (unknown subject) Each manpage should only appear once. It would be even better if it could contain a description. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux jophur 2.6.0-1-686 #2 Sun Jan 11 16:59:17 EST 2004 i686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] Versions of packages libstdc++5-3.3-doc depends on: ii gcc-3.3-base 1:3.3.3-0pre2 The GNU Compiler Collection (base -- no debconf information
Bug#228421: gcc 3.0.4 generates bad code on Debian 3.0/PARISC
On Sun, Jan 25, 2004 at 11:03:53AM -0700, Grant Grundler wrote: > On Sun, Jan 25, 2004 at 06:05:17PM +0100, Willy Tarreau wrote: > > But the root of the problem lies in gcc 3.0.4 since it is OK in 3.3.2. So > > wouldn't it be easier to identify and backport the fix from 3.3.2 to 3.0.4 > > and inform all projects that they must recompile everything on parisc ? > > "recompile everything" == "new release". > AFAICT, the "debian way" is to recompile the packages that have bugs > filed against them and binNMU (Non-Maintainer-Upload) just those packages. Yes, but this is stuff already in stable. Almost everything in sarge should be compiled with gcc 3.2 or 3.3. There are some exceptions, such as old-KDE and some other old libs (C++ ABI changes). It might be worth someone tracking down the va_args patch for 3.0, but I'm certainly not going to do it. -- "Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception." -- Mark Twain
Processing of gcc-3.3_3.3.3ds3-0pre3_hppa.changes
gcc-3.3_3.3.3ds3-0pre3_hppa.changes uploaded successfully to localhost along with the files: gcc-3.3-base_3.3.3-0pre3_hppa.deb libgcc1_3.3.3-0pre3_hppa.deb cpp-3.3_3.3.3-0pre3_hppa.deb protoize_3.3.3-0pre3_hppa.deb fixincludes_3.3.3-0pre3_hppa.deb gobjc-3.3_3.3.3-0pre3_hppa.deb libobjc1_3.3.3-0pre3_hppa.deb fastjar_3.3.3-0pre3_hppa.deb g++-3.3_3.3.3-0pre3_hppa.deb libstdc++5_3.3.3-0pre3_hppa.deb libstdc++5-3.3-dev_3.3.3-0pre3_hppa.deb libstdc++5-3.3-pic_3.3.3-0pre3_hppa.deb libstdc++5-3.3-dbg_3.3.3-0pre3_hppa.deb libg2c0_3.3.3-0pre3_hppa.deb g77-3.3_3.3.3-0pre3_hppa.deb gnat-3.3_3.3.3-0pre3_hppa.deb treelang-3.3_3.3.3-0pre3_hppa.deb gpc-2.1-3.3_3.3.3.20030830-0pre3_hppa.deb gcc-3.3_3.3.3-0pre3_hppa.deb gcc-3.3-hppa64_3.3.3-0pre3_hppa.deb Greetings, Your Debian queue daemon
Incomplete upload found in Debian upload queue
Probably you are the uploader of the following file(s) in the Debian upload queue directory: gcc-3.3_3.3.3ds3-0pre3.diff.gz gcc-3.3_3.3.3ds3-0pre3.dsc This looks like an upload, but a .changes file is missing, so the job cannot be processed. If no .changes file arrives within 23:24:08, the files will be deleted. If you didn't upload those files, please just ignore this message. Greetings, Your Debian queue daemon
gcc-3.3_3.3.3ds3-0pre3_hppa.changes REJECTED
Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (gnat-3.3_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (gcc-3.3-hppa64_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (gpc-2.1-3.3_3.3.3.20030830-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (g++-3.3_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (libgcc1_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (fastjar_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (gcc-3.3_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (gobjc-3.3_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (protoize_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (gcc-3.3-base_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (treelang-3.3_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (libobjc1_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (libstdc++5-3.3-dev_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (libstdc++5-3.3-pic_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (cpp-3.3_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (libg2c0_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (libstdc++5-3.3-dbg_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (fixincludes_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (libstdc++5_3.3.3-0pre3_hppa.deb). Rejected: no source found for gcc-3.3 1:3.3.3ds3-0pre3 (g77-3.3_3.3.3-0pre3_hppa.deb). === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email.
[Bug target/13722] [3.4/3.5 regression] [ia64] ICE in push_secondary_reload
--- Additional Comments From zack at codesourcery dot com 2004-01-25 22:33 --- Subject: Re: PR 13722 candidate fix Jim Wilson <[EMAIL PROTECTED]> writes: > My latest bootstrap succeeded. I didn't run the testsuite, and I still > had some debug code in there just to be safe, but I don't think either > of those issues should matter. With the following patch on top of your > patches, the IA-64 gcc port bootstrap again including Ada. This patch > adds the REG_INC notes for auto-inc addresses in the IN operands. There > is also the potential problem I pointed out earlier where we use INTVAL > without checking to see if we have a CONST_INT. That isn't in this > patch, but I think it should go in also. Okay. I have incorporated your changes into my patch, added the CONST_INT check, and am running a bootstrap on ia64-hpux; if it succeeds I'll repost the combined patch. [...] > So what I am asking here is that if you check in a patch that > breaks the IA-64 compiler, and you are not able to solve the problem > yourself, that you revert the patch until I am able to help you. I am > willing to help you with these kinds of things, but it isn't fair to > others to let you monopolize my time, and it isn't fair to others to > leave the IA-64 compiler broken for long periods of time. I am willing to do this for most breaks. However, it is my understanding that breaks that affect only Ada are *not* considered critical, and in fact that there is no obligation for anyone to attempt to build the Ada front end. I normally do not bother building it even on platforms that can handle it (ia64-hpux cannot, as the runtime has not been ported). This is why I did not respond very fast to this bug report. I am willing to change my habits if the policy has changed, but not otherwise. > If you want to be really helpful, you could try looking at some of the > IA-64 gcc bug reports in bugzilla. PR 7198 is on my list, and is one > that you could handle. Sure, I'll look at that. zw -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13722 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Bug debug/11983] [3.4/3.5 Regression] ICE in dwarf-2 on code using altivec
-- What|Removed |Added List of versions||3.3 known to work|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11983 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Bug bootstrap/12371] [3.4/3.5 regression] [m68k-linux] bootstrap error in make compare
-- What|Removed |Added List of versions||3.3 known to work|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12371 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter.
[Bug ada/13670] [3.4/3.5 Regression] xnmake gets miscompiled during bootstrap with ada enabled
-- What|Removed |Added Severity|normal |minor List of versions||3.3 known to work|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13670 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Bug c++/11295] [3.4/3.5 regression] ICE in cp_expr_size, at cp/cp-lang.c:314 when using a non-trivial object in a compound statement expression
-- What|Removed |Added List of versions||3.3 known to work|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11295 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Bug target/13722] [3.4/3.5 regression] [ia64] ICE in push_secondary_reload
-- What|Removed |Added List of versions||3.3 known to work|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13722 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
Processing of gcc-3.3_3.3.3ds3-0pre3_i386.changes
gcc-3.3_3.3.3ds3.orig.tar.gz has incorrect size; deleting it cpp-3.3_3.3.3-0pre3_i386.deb has incorrect size; deleting it libgcj4_3.3.3-0pre3_i386.deb has incorrect size; deleting it Due to the errors above, the .changes file couldn't be processed. Please fix the problems for the upload to happen. Greetings, Your Debian queue daemon
[Bug c/13072] Bogus warning with VLA in switch
-- What|Removed |Added Known to work||tree-ssa http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13072 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
Processing of gcc-3.3_3.3.3ds0-0pre0_i386.changes
cpp-3.3-doc_3.3.3-0pre0_all.deb doesn't exist libgcj-common_3.3.3-0pre0_all.deb doesn't exist libstdc++5-3.3-doc_3.3.3-0pre0_all.deb doesn't exist g77-3.3-doc_3.3.3-0pre0_all.deb doesn't exist gnat-3.3-doc_3.3.3-0pre0_all.deb doesn't exist gpc-2.1-3.3-doc_3.3.3.20030830-0pre0_all.deb doesn't exist gcc-3.3-doc_3.3.3-0pre0_all.deb doesn't exist gcc-3.3-base_3.3.3-0pre0_i386.deb doesn't exist libgcc1_3.3.3-0pre0_i386.deb doesn't exist cpp-3.3_3.3.3-0pre0_i386.deb doesn't exist protoize_3.3.3-0pre0_i386.deb doesn't exist fixincludes_3.3.3-0pre0_i386.deb doesn't exist gobjc-3.3_3.3.3-0pre0_i386.deb doesn't exist libobjc1_3.3.3-0pre0_i386.deb doesn't exist gij-3.3_3.3.3-0pre0_i386.deb doesn't exist libgcj4_3.3.3-0pre0_i386.deb doesn't exist gcj-3.3_3.3.3-0pre0_i386.deb doesn't exist libgcj4-dev_3.3.3-0pre0_i386.deb doesn't exist fastjar_3.3.3-0pre0_i386.deb doesn't exist libffi2_3.3.3-0pre0_i386.deb doesn't exist libffi2-dev_3.3.3-0pre0_i386.deb doesn't exist g++-3.3_3.3.3-0pre0_i386.deb doesn't exist libstdc++5_3.3.3-0pre0_i386.deb doesn't exist libstdc++5-3.3-dev_3.3.3-0pre0_i386.deb doesn't exist libstdc++5-3.3-pic_3.3.3-0pre0_i386.deb doesn't exist libstdc++5-3.3-dbg_3.3.3-0pre0_i386.deb doesn't exist libg2c0_3.3.3-0pre0_i386.deb doesn't exist g77-3.3_3.3.3-0pre0_i386.deb doesn't exist gnat-3.3_3.3.3-0pre0_i386.deb doesn't exist treelang-3.3_3.3.3-0pre0_i386.deb doesn't exist gpc-2.1-3.3_3.3.3.20030830-0pre0_i386.deb doesn't exist gcc-3.3_3.3.3-0pre0_i386.deb doesn't exist Due to the errors above, the .changes file couldn't be processed. Please fix the problems for the upload to happen. Greetings, Your Debian queue daemon
Incomplete upload found in Debian upload queue
Probably you are the uploader of the following file(s) in the Debian upload queue directory: gcc-3.3_3.3.3ds1-0pre2.diff.gz gcc-3.3_3.3.3ds1-0pre2.dsc This looks like an upload, but a .changes file is missing, so the job cannot be processed. If no .changes file arrives within 23:26:12, the files will be deleted. If you didn't upload those files, please just ignore this message. Greetings, Your Debian queue daemon
Bug#67206: [Bug optimization/9363] unused struct literal constants remain
-- What|Removed |Added Known to work||tree-ssa http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9363 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
Re: Processed: Re: Bug#227894: No error when using older kernel
reassign 227894 valgrind
quit
On Sun, Jan 25, 2004 at 08:03:09AM -0800, Debian Bug Tracking System wrote:
> Processing commands for [EMAIL PROTECTED]:
>
> > reassign 227894 kernel-tree-2.6.0
> Bug#227894: g++ exceptions thrown -> valgrind signals invalid read
> Bug reassigned from package `g++' to `kernel-tree-2.6.0'.
valgrind needs to learn about the vsyscall page @ 0xe000.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
