--- Additional Comments From woodzltc at sources dot redhat dot com
2005-08-09 07:04 ---
(In reply to comment #15)
[snip]
> Please add an issue on dwarf.freestandards.org and i'll take it from
> there.
I had added an public comment titiled "add a new entry to identify the main
functi
gcc-4.0_4.0.1-4_hurd-i386.changes uploaded successfully to localhost
along with the files:
gcc-4.0-base_4.0.1-4_hurd-i386.deb
libgcc1_4.0.1-4_hurd-i386.deb
cpp-4.0_4.0.1-4_hurd-i386.deb
protoize_4.0.1-4_hurd-i386.deb
fixincludes_4.0.1-4_hurd-i386.deb
libmudflap0_4.0.1-4_hurd-i386.deb
Accepted:
cpp-4.0_4.0.1-4_hurd-i386.deb
to pool/main/g/gcc-4.0/cpp-4.0_4.0.1-4_hurd-i386.deb
fastjar_4.0.1-4_hurd-i386.deb
to pool/main/g/gcc-4.0/fastjar_4.0.1-4_hurd-i386.deb
fixincludes_4.0.1-4_hurd-i386.deb
to pool/main/g/gcc-4.0/fixincludes_4.0.1-4_hurd-i386.deb
g++-4.0_4.0.1-4_hurd-i386
Your message dated Tue, 9 Aug 2005 10:52:23 +0200
with message-id <[EMAIL PROTECTED]>
and subject line [fixed in 3.4] Segfault with C++ inheritance
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
Your message dated Tue, 9 Aug 2005 10:50:54 +0200
with message-id <[EMAIL PROTECTED]>
and subject line [fixed in 4.0] libgcj4 and libsablevm1-dev both include
/usr/include/jni.h
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with
Processing commands for [EMAIL PROTECTED]:
> reopen 223226
Bug#223226: [fixed in 3.4] Segfault with C++ inheritance
Bug reopened, originator not changed.
> tags 223226 + pending
Bug#223226: [fixed in 3.4] Segfault with C++ inheritance
Tags were: fixed-upstream upstream
Tags added: pending
> than
Processing commands for [EMAIL PROTECTED]:
> forwarded 321395 [EMAIL PROTECTED]
Bug#321395: gpc-2.1-3.3-doc: Broken links to standards.html
Noted your statement that Bug has been forwarded to [EMAIL PROTECTED]
> tags 321395 + upstream
Bug#321395: gpc-2.1-3.3-doc: Broken links to standards.html
Th
gcc-defaults_1.28_hppa.changes uploaded successfully to localhost
along with the files:
cpp_4.0.1-3_hppa.deb
cpp-doc_4.0.1-3_hppa.deb
gcc_4.0.1-3_hppa.deb
gcc-doc_4.0.1-3_hppa.deb
g++_4.0.1-3_hppa.deb
gobjc_4.0.1-3_hppa.deb
g77_3.4.4-5_hppa.deb
g77-doc_3.4.4-5_hppa.deb
gfortran_4.
Accepted:
cpp-doc_4.0.1-3_hppa.deb
to pool/main/g/gcc-defaults/cpp-doc_4.0.1-3_hppa.deb
cpp_4.0.1-3_hppa.deb
to pool/main/g/gcc-defaults/cpp_4.0.1-3_hppa.deb
g++_4.0.1-3_hppa.deb
to pool/main/g/gcc-defaults/g++_4.0.1-3_hppa.deb
g77-doc_3.4.4-5_hppa.deb
to pool/main/g/gcc-defaults/g77-doc_3
Package: libstdc++6
Version: 4.0.1-2
Severity: normal
Tags: patch
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-1-686
Locale: LANG=C,
gcc-4.0_4.0.1-4_hppa.changes uploaded successfully to localhost
along with the files:
gcc-4.0-base_4.0.1-4_hppa.deb
libgcc2_4.0.1-4_hppa.deb
cpp-4.0_4.0.1-4_hppa.deb
protoize_4.0.1-4_hppa.deb
fixincludes_4.0.1-4_hppa.deb
libmudflap0_4.0.1-4_hppa.deb
libmudflap0-dev_4.0.1-4_hppa.deb
Accepted:
cpp-4.0_4.0.1-4_hppa.deb
to pool/main/g/gcc-4.0/cpp-4.0_4.0.1-4_hppa.deb
fastjar_4.0.1-4_hppa.deb
to pool/main/g/gcc-4.0/fastjar_4.0.1-4_hppa.deb
fixincludes_4.0.1-4_hppa.deb
to pool/main/g/gcc-4.0/fixincludes_4.0.1-4_hppa.deb
g++-4.0_4.0.1-4_hppa.deb
to pool/main/g/gcc-4.0/g++-4
Your message dated Tue, 09 Aug 2005 08:17:04 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#317475: fixed in ragel 4.1-3
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 r
why do you close a bug report for gcc-4.0, if nothing changed in
gcc-4.0? Please reopen, unless the bug is fixed in gcc-4.0.
Matthias
Debian Bug Tracking System writes:
> Your message dated Tue, 09 Aug 2005 08:17:04 -0700
> with message-id <[EMAIL PROTECTED]>
> and subject line Bug#317475: fix
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-09
15:59 ---
*** Bug 23298 has been marked as a duplicate of this bug. ***
--
What|Removed |Added
Processing commands for [EMAIL PROTECTED]:
> reopen 317475
Bug#317475: [m68k] ICE: Segmentation fault
Bug reopened, originator not changed.
> close 321250
Bug#321250: ragel_4.1-2(m68k/unstable/zeus): FTBFS on m68k
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed
> AFAICS the document isn't included in the gpc sources.
>
> /usr/share/doc/gcc-3.3-base/pascal/gpcs.html has links to standards.html
> (examle: 'Mmap (standards)')
> but there is no standards.html in gpc-2.1-3.3-doc and no
> /usr/share/doc/gcc-3.3-base/pascal/standards.html in Debian:
Yes, Texinf
--
What|Removed |Added
CC|rth at gcc dot gnu dot org |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=323
--- You are receiving this mail because: ---
You are
Package: gcc
Version: 3.3.5-3
When compiled with -O2, the appended test program goes into an
infinite loop at run-time. When compiled with -O or with no
optimization, it runs correctly, exiting immediately and
generating no output.
I am using Debian GNU/Linux 3.1, with a 2.4.28 kernel and
libc6-2
Your message dated Wed, 10 Aug 2005 00:40:08 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322218: gcc -O2 optimization bug
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 yo
LAST_UPDATED: Sat Aug 6 23:06:35 UTC 2005
=== acats tests ===
FAIL: cxf3a01
FAIL: cxf3a02
=== acats Summary ===
# of expected passes2318
# of unexpected failures2
Native configuration is i486-pc-linux-gnu
=== g++ tests ===
LAST_UPDATED: Sat Aug 6 23:06:35 UTC 2005
Native configuration is powerpc-unknown-linux-gnu
=== g++ tests ===
Running target unix
=== g++ Summary ===
# of expected passes11060
# of expected failures 69
# of unsupported tests 76
/b
LAST_UPDATED: Sat Aug 6 23:06:35 UTC 2005
=== acats tests ===
FAIL: c36204d
FAIL: c9a009a
FAIL: c9a009c
FAIL: c9a009h
FAIL: c9a010a
FAIL: cb1005a
FAIL: cb4009a
FAIL: cd5014e
=== acats Summary ===
# of expected passes2312
# of unexpected
LAST_UPDATED: Sat Aug 6 23:06:35 UTC 2005
=== acats tests ===
FAIL: c954025
FAIL: c954026
=== acats Summary ===
# of expected passes2318
# of unexpected failures2
Native configuration is s390-ibm-linux-gnu
=== g++ tests ===
LAST_UPDATED: Tue Jul 26 07:57:20 UTC 2005
Native configuration is arm-unknown-linux-gnu
=== libffi tests ===
Running target unix
FAIL: libffi.call/closure_fn0.c (test for excess errors)
WARNING: libffi.call/closure_fn0.c compilation failed to produce executable
FAIL: libffi.cal
LAST_UPDATED: Sat Aug 6 23:06:35 UTC 2005
=== acats tests ===
=== acats Summary ===
# of expected passes2320
# of unexpected failures0
Native configuration is sparc-unknown-linux-gnu
=== g++ tests ===
Running target unix
XPAS
LAST_UPDATED: Sat Aug 6 23:06:35 UTC 2005
Native configuration is alpha-unknown-linux-gnu
=== libffi tests ===
Running target unix
=== libffi Summary ===
# of expected passes219
# of unsupported tests 2
=== libjava tests ==
LAST_UPDATED: Sat Aug 6 23:06:35 UTC 2005
=== acats tests ===
FAIL: c93001a
FAIL: c95021a
FAIL: cb41002
FAIL: cxg1005
=== acats Summary ===
# of expected passes2316
# of unexpected failures4
Native configuration is hppa-unknown-linux-gn
28 matches
Mail list logo
