Accepted:
cpp-3.3_3.3.4-11_arm.deb
to pool/main/g/gcc-3.3/cpp-3.3_3.3.4-11_arm.deb
fixincludes_3.3.4-11_arm.deb
to pool/main/g/gcc-3.3/fixincludes_3.3.4-11_arm.deb
g++-3.3_3.3.4-11_arm.deb
to pool/main/g/gcc-3.3/g++-3.3_3.3.4-11_arm.deb
g77-3.3_3.3.4-11_arm.deb
to pool/main/g/gcc-3.3/g77-3
Your message dated Thu, 02 Sep 2004 20:32:13 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#267426: fixed in gcc-3.3 1:3.3.4-11
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
Accepted:
cpp-3.3-doc_3.3.4-11_all.deb
to pool/main/g/gcc-3.3/cpp-3.3-doc_3.3.4-11_all.deb
cpp-3.3_3.3.4-11_i386.deb
to pool/main/g/gcc-3.3/cpp-3.3_3.3.4-11_i386.deb
fixincludes_3.3.4-11_i386.deb
to pool/main/g/gcc-3.3/fixincludes_3.3.4-11_i386.deb
g++-3.3_3.3.4-11_i386.deb
to pool/main/g/
Your message dated Thu, 02 Sep 2004 20:32:13 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#268929: fixed in gcc-3.3 1:3.3.4-11
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 message dated Thu, 02 Sep 2004 20:32:13 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#267656: fixed in gcc-3.3 1:3.3.4-11
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 message dated Thu, 02 Sep 2004 20:32:13 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#269522: fixed in gcc-3.3 1:3.3.4-11
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
gcc-3.3_3.3.4-11_arm.changes uploaded successfully to localhost
along with the files:
gcc-3.3-base_3.3.4-11_arm.deb
cpp-3.3_3.3.4-11_arm.deb
protoize_3.3.4-11_arm.deb
fixincludes_3.3.4-11_arm.deb
gobjc-3.3_3.3.4-11_arm.deb
libobjc1_3.3.4-11_arm.deb
gij-3.3_3.3.4-11_arm.deb
libgcj4_3
gcc-3.3_3.3.4-11_i386.changes uploaded successfully to localhost
along with the files:
gcc-3.3_3.3.4-11.dsc
gcc-3.3_3.3.4-11.diff.gz
cpp-3.3-doc_3.3.4-11_all.deb
libgcj4-common_3.3.4-11_all.deb
libgcj-common_3.3.4-11_all.deb
libstdc++5-3.3-doc_3.3.4-11_all.deb
g77-3.3-doc_3.3.4-11_all
--- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-09-02
16:06 ---
Hopefully correctly fixed this time.
--
What|Removed |Added
Status|REOPENED
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-09-02
16:04 ---
Subject: Bug 17180
CVSROOT:/cvs/gcc
Module name:gcc
Branch: gcc-3_4-branch
Changes by: [EMAIL PROTECTED] 2004-09-02 16:04:44
Modified files:
gcc/f : Change
--- Additional Comments From mark at codesourcery dot com 2004-09-02 07:48
---
Subject: Re: [3.4 Regression] nearly all g77 tests fail
ebotcazou at gcc dot gnu dot org wrote:
>--- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-09-02
>06:08 ---
>I think the pa
--- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-09-02
06:08 ---
I think the patch is not really correct because the pool is used on the host,
not on the target. We probably need something like:
struct max_alignment {
char c;
union {
HOST_WIDEST_INT i;
#ifdef
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-09-02
05:12 ---
Subject: Bug 16121
CVSROOT:/cvs/gcc
Module name:gcc
Changes by: [EMAIL PROTECTED] 2004-09-02 05:10:34
Modified files:
libjava: ChangeLog Makefile.am Makefile.in
13 matches
Mail list logo