LAST_UPDATED: Sat Oct 15 18:47:36 UTC 2005
Native configuration is m68k-linux-gnu (a4000t)
=== gpc tests ===
Running target any
FAIL: fjf328.pas
FAIL: fjf347.pas
FAIL: marco1.pas
FAIL: tsmul.pas
=== gpc Summary ===
# of tests4947
# of expected p
On Tue, Nov 08, 2005 at 04:01:11PM +0100, Matthias Klose wrote:
> libstdc++6 is currently configured to use the mt allocator based on
> discussions in April 2004 with upstream libstdc++ developers. This
> configuration turned out to be a mistake (memory leaks and the
> allocator is still buggy), ot
* Matthias Klose:
> The change does not have an effect on symbols exported from
> libstdc++, but it does have an effect on symbols exported by
> libraries which use containers (using an allocator) from the
> template headers.
Does it change the internal representation of std::string, or some
othe
* Matthias Klose ([EMAIL PROTECTED]) [051108 16:28]:
> The change will break some libraries, as seen in #336114, which can be
> fixed by rebuilding these libraries against a reconfigured libstdc++.
>
> * Identify all library packages depending on libstdc++ and
>exporting *mt_alloc* symbols.
>
Nathanael Nerode writes:
> tags 336114 +upstream
> forwarded 336114 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24712
> thanks
>
> Forwarded upstream as GCC bug number 24712.
I think, that's not upstream. both changes were made between the 4.0.1
and the 4.0.2 release.
Matthias
--
To UNSUB
Your message dated Tue, 8 Nov 2005 11:36:58 -0600
with message-id <[EMAIL PROTECTED]>
and subject line fixed in or before gcc-4.0_4.0.2-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
Your message dated Tue, 8 Nov 2005 11:36:58 -0600
with message-id <[EMAIL PROTECTED]>
and subject line fixed in or before gcc-4.0_4.0.2-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
Your message dated Tue, 8 Nov 2005 11:36:58 -0600
with message-id <[EMAIL PROTECTED]>
and subject line fixed in or before gcc-4.0_4.0.2-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
Processing commands for [EMAIL PROTECTED]:
> tags 333100 + pending
Bug#333100: [PR 21123] [4.0 regression] [hppa] Fails to build kdebluetooth
Tags were: upstream
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administr
libstdc++6 is currently configured to use the mt allocator based on
discussions in April 2004 with upstream libstdc++ developers. This
configuration turned out to be a mistake (memory leaks and the
allocator is still buggy), other distributions did change back to the
new allocator (the default one)
Processing commands for [EMAIL PROTECTED]:
> tags 323133 + fixed-upstream
Bug#323133: [PR 21123, 4.0 regression, fixed in 4.1] ICE on arm & m68k when
compiling arts (in cp_expr_size, at cp/cp-objcp-common.c:101)
Tags were: help upstream
Bug#323686: [PR 21123] ICE in cp_expr_size, compiling orbit2
--- Comment #26 from pinskia at gcc dot gnu dot org 2005-11-08 12:54
---
Fixed at least on the mainline.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
On 9/20/05, LI Daobing <[EMAIL PROTECTED]> wrote:
> package g++-4.0
> retitle 328939 [PR 21089]g++-4.0: do not optimize for a 'const double'
> thanks
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21089
>
This bug disappear in version 4.0.2-3. I think now you can close it.
$ dpkg -l g++-4.0 | gr
Hi,
Please subscribe me for this mailing list
Thanks.
Rama
--- Comment #25 from jason at gcc dot gnu dot org 2005-11-08 08:32 ---
Subject: Bug 21123
Author: jason
Date: Tue Nov 8 08:32:26 2005
New Revision: 106634
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106634
Log:
PR c++/21123
* cp/method.c (use_thunk): Use buil
15 matches
Mail list logo
