Testing of libstdc++ with an installed toolchain was broken by
2006-06-06 Benjamin Kosnik <[EMAIL PROTECTED]>
* testsuite/util: New directory.
[...]
g++ -g -O2 -D_GLIBCXX_ASSERT -fmessage-length=0 -DLOCALEDIR="."
-I/scratch/gcc/nightly-2006-06-10-mainline/src/gcc-mainline/libstdc++-v3/
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27984
--- Comment #1 from patchapp at dberlin dot org 2006-06-10 14:10 ---
Subject: Bug number PR c++/27952
A patch for this bug has been added to the patch tracker.
The mailing list url for the patch is
http://gcc.gnu.org/ml/gcc-patches/2006-06/msg00536.html
--
http://gcc.gnu.org/bugzil
--- Comment #2 from patrik dot hagglund at bredband dot net 2006-06-10
14:45 ---
(In reply to comment #1)
> Why is this that bad of a warning,
I didn't said it was a bad warning per se (did I?). What I want to do is to be
able to prioritize between warnings to be able to cope with the
--- Comment #34 from arno at heho dot snv dot jussieu dot fr 2006-06-10
18:00 ---
(In reply to comment #30)
This patch works great for me.
Tested on i386-freebsd6 and i386-linux-2.6.15-gentoo by calling CNI in threads
created by an absolute non-CNI aware c++ Corba library.
--
http
--- Comment #3 from digitale at digitaleric dot net 2006-06-10 18:01
---
Subject: Re: gcc emits (undefined) ffreep opcode which
is not understood by Solaris' /usr/ccs/bin/as when tuning for Athlon or
Opteron CPUs
> --- Comment #1 from pinskia at gcc dot gnu dot org
It's got something to do with two occurances of the object "Action" in the
attached test vis:
[EMAIL PROTECTED] gcj -d . -I . -C one/ExitNotificationObserver.java
one/AddTaskObserverAction.java one/TaskAction.java
one/ExitNotificationObserver.java: In class 'one.ExitNotificationObserver':
one/Exit
--- Comment #1 from cagney at redhat dot com 2006-06-10 18:53 ---
Created an attachment (id=11649)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11649&action=view)
source code for compile
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27985
--- Comment #2 from kargl at gcc dot gnu dot org 2006-06-10 20:27 ---
I have a tentative patch for this problem that I'm testing now.
--
kargl at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #56 from pinskia at gcc dot gnu dot org 2006-06-10 22:22
---
complit1.C has an internal error now on powerpc-darwin:
Foo::Foo(int, int)
complit1.C:14: error: ISO C++ forbids assignment of arrays
Foo::Foo(int, int) Foo::Foo(int, int)
Analyzing compilation unitPerforming int
in the following code gcc choses the registers in such a way that it causes
itself an extra copy for every loop iteration and has to jump past the copy to
start the loop... it's probably easiest to describe just by looking at the
code:
% cat jmp-over.c
void foo(int *v, int *d, int g)
{
int s = v
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-06-10 22:32 ---
PPC gives:
_foo:
lwz r2,4(r3)
b L2
L7:
mr r2,r0
L2:
lwz r0,0(r4)
addi r4,r4,4
add r0,r2,r0
cmpw cr7,r0,r5
blt+ cr7,L7
stw r2,0(r3)
blr
12 matches
Mail list logo