--
What|Removed |Added
Summary|ACATS FAIL cxaa017 character|[4.1 regression] ACATS FAIL
|processing wrong code |cxaa017 character processing
--
What|Removed |Added
CC||pinskia at gcc dot gnu dot
||org
http://gcc.gnu.org/bugzilla/sh
--- Additional Comments From ian at airs dot com 2005-07-29 22:38 ---
I haven't checked g++ 3.3.x, but I have no reason to doubt you. I think you
grasp the situation fine: at least for a while, g++ did not follow the ABI. Now
it does. It's a problem. Any time you don't follow the ABI,
--
Bug 16989 depends on bug 21720, which changed state.
Bug 21720 Summary: GCC incorrectly rounds hex floats
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21720
What|Old Value |New Value
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-29
23:24 ---
Fixed.
--
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
The new C parser lost a call to mark_forward_parm_decls, thereby completely
breaking the GNU extension of forward parameter declarations. I'm testing a
patch. Testcases:
int f1(int a; int a);
should be accepted (rather than complaining about a duplicate parameter name),
int h1(int a; int b);
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-29
23:30 ---
Confirmed. I did not even know of this extension. I don't even see it as
being a documented one
either, unless I missed something obvious.
--
What|Removed |Added
GCC 4.0 fails to diagnose cases of parameter forward declarations followed by no
normal parameter declarations, such as
int g1(int a;);
int g2(int a; __attribute__((unused)));
int g3(int;);
int g4(int, long;);
The same applies to 4.1 once I've fixed bug 23143. 3.4 diagnoses these cases.
--
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-29
23:34 ---
Confirmed, this has been failing since at least 20040909.
--
What|Removed |Added
--- Additional Comments From joseph at codesourcery dot com 2005-07-29
23:34 ---
Subject: Re: [4.1 Regression] parameter forward declarations
broken
On Fri, 29 Jul 2005, pinskia at gcc dot gnu dot org wrote:
> Confirmed. I did not even know of this extension. I don't even see it
>
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-07-29
23:58 ---
Subject: Bug 529
CVSROOT:/cvs/gcc
Module name:gcc
Changes by: [EMAIL PROTECTED] 2005-07-29 23:58:37
Modified files:
gcc: ChangeLog c-decl.c
gcc/testsui
--- Additional Comments From wilson at gcc dot gnu dot org 2005-07-30
01:02 ---
The problem is the compile-classes rule in the libjava/classpath/lib/Makefile.am
file. This rule contains a line $(JAVAC) that has a recursive make hidden
inside it. make -j requires that all lines that per
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-07-30
01:35 ---
Subject: Bug 23143
CVSROOT:/cvs/gcc
Module name:gcc
Changes by: [EMAIL PROTECTED] 2005-07-30 01:34:58
Modified files:
gcc: ChangeLog c-decl.c c-parser.c
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-07-30
02:12 ---
Subject: Bug 22582
CVSROOT:/cvs/gcc
Module name:gcc
Changes by: [EMAIL PROTECTED] 2005-07-30 02:12:26
Modified files:
gcc: ChangeLog
gcc/doc: i
--
Bug 5362 depends on bug 22582, which changed state.
Bug 22582 Summary: -rdynamic is undocumented
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22582
What|Old Value |New Value
--- Additional Comments From wilson at gcc dot gnu dot org 2005-07-30
02:16 ---
Fixed on mainline.
--
What|Removed |Added
Status|NEW |RES
--
What|Removed |Added
BugsThisDependsOn||23145
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22368
The C front-end says that struct {int i;} is compatiable with struct {int i,j}
which is wrong.
The following testcase should be rejected but it is not:
file1.c
struct op {
int i;
};
void a (struct op* o);
end -
file2.c -
struct listop {
int i, j;
};
void a(struct li
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-30
03:05 ---
Hmm, Apple's 3.3-fast does not have this bug.
sv.i:4: warning: conflicting types for `a'
op.i:4: warning: previous declaration of `a'
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23145
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-30
03:09 ---
Fixed.
--
What|Removed |Added
Status|NEW |RESOLVED
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-30
03:10 ---
Fixed.
--
What|Removed |Added
Status|NEW |RESOLVED
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-07-30
05:33 ---
Subject: Bug 22570
CVSROOT:/cvs/gcc
Module name:gcc
Changes by: [EMAIL PROTECTED] 2005-07-30 05:33:40
Modified files:
libgfortran: ChangeLog
libgfortran/io : t
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-07-30
06:18 ---
Subject: Bug 22570
CVSROOT:/cvs/gcc
Module name:gcc
Branch: gcc-4_0-branch
Changes by: [EMAIL PROTECTED] 2005-07-30 06:18:35
Modified files:
libgfortran: Change
--- Additional Comments From jvdelisle at gcc dot gnu dot org 2005-07-30
06:29 ---
Can or will this patch be put into mainline? Seems to be falling in a crack.
It is needed to help with moving forward on pr23138. I will apply the patch
given here. My first attempts failed, maybe I ha
--- Additional Comments From jvdelisle at gcc dot gnu dot org 2005-07-30
06:31 ---
I have confirmed this bug on cygwin. We can't get current builds on cygwin,
perhaps patch to pr21275 is needed?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23138
101 - 125 of 125 matches
Mail list logo
