Duraid,
How about collecting some profiles (e.g., with qprof or q-syscollect)?
That might be a quick way to get some idea as to what's causing the
regression.
--david
> On Sun, 3 Apr 2005 16:04:48 +0200, Matthias Klose <[EMAIL PROTECTED]>
> said:
Matthias> according to the ch
> On Thu, 30 Dec 2004 00:06:24 +0300, "Nikita V. Youshchenko" <[EMAIL
> PROTECTED]> said:
Nikita> Unfortunately, I'm having technical problems here.
Nikita> First, libunwind build procedure first creates two tools,
Nikita> mk_Gcursor_i and mk_Lcursor_i, that are executed to produce
>>>>> On Wed, 15 Dec 2004 13:55:45 -0800, David Mosberger <[EMAIL PROTECTED]>
>>>>> said:
David> I just checked and with the current packaging, I'm still
David> getting failures during the libunwind build.
After fixing these problems in li
>>>>> On Tue, 14 Dec 2004 11:58:07 +0100, Matthias Klose <[EMAIL PROTECTED]>
>>>>> said:
Matthias> David Mosberger writes:
>> >>>>> On Mon, 13 Dec 2004 20:47:41 +0100, Matthias Klose
>> <[EMAIL PROTECTED]> sa
> On Mon, 13 Dec 2004 20:47:41 +0100, Matthias Klose <[EMAIL PROTECTED]>
> said:
Matthias> please get the libgcc1 package from the unstable
Matthias> distribution.
I think I've got that one already (libgcc1 v3.4.3-2).
Matthias> It's currently built by the gcc-3.4 sources and inclu
Hi Matthias,
> On Sun, 12 Dec 2004 17:55:57 +0100, Matthias Klose <[EMAIL PROTECTED]>
> said:
Matthias> with the patch attached and an updated gcc-3.3 package,
Matthias> libunwind support for ia64 seems to work for me. I
Matthias> couldn't install any of the built packages. I'd lik
> On Wed, 24 Nov 2004 00:26:01 +0100, Matthias Klose <[EMAIL PROTECTED]>
> said:
Matthias> From my point of view we can get around with it by
Matthias> including the libunwind shared library in libgcc1 for the
Matthias> sarge release. I'm worried about the version skew of the
Matt
> On Tue, 23 Nov 2004 09:27:52 +0100, Matthias Klose <[EMAIL PROTECTED]>
> said:
Matthias> Is the patch in #278836 a prerequisite for the above
Matthias> changes, or can it be done without it?
If the gas-patch isn't applied, you run the risk of getting wrong
unwind-info into object-f
> On Wed, 22 Sep 2004 09:40:13 +0200, Matthias Klose <[EMAIL PROTECTED]>
> said:
Matthias> current 3.4.3 CVS has a change to add libunwind support to
Matthias> libgcc. * config.gcc (ia64*-*-linux*): Always add
Matthias> t-libunwind to tmake_file. Add t-libunwind-elf and
Matthias>
Package: gcc-3.3
Version: 1:3.3.3-0pre0
Severity: important
Tags: sid
It appears that the behavior of Debian gcc-3.3 is inconsistent with
that of Red Hat's gcc-3.2 when -fexceptions is specified. Example:
On Debian/testing:
$ cat t.c
int main (int argc, char **argv) {
printf ("hello\n
n/unstable).
Thanks,
--david
----
From: David Mosberger <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject: patch for GCC v3.3.3
Date: Tue, 2 Dec 2003 10:45:26 -0800
Reply-To: [EMAIL PROTECTED]
X-URL: http:
Package: gcc-3.3
Version: 1:3.3.2-3
Severity: important
Tags: sid
It appears that the gcc-3.3 package fails to install the header-file
unwind.h. Newer versions of glibc check for the presence of this file
and will behave differently if it is missing. The file should be
installed in /usr/lib/gcc-
12 matches
Mail list logo
