From: Matthias Klose [EMAIL PROTECTED]
Date: Wed, 21 May 2008 11:25:43 +0200
thanks for the update, tested with the 4.3 branch 20080509 with no
regressions.
Thanks for testing, I've checked the bug fix into mainline.
could this patch be considered for the 4.3 branch as
well?
I'm personally
David Miller writes:
From: Matthias Klose [EMAIL PROTECTED]
Date: Sun, 18 May 2008 13:33:23 +0200
Building GCC-4.3 with this patch (compared to the patch previously
used by debian [1]), I get differing symbol versions for the Debian build
on sparc in libgcc1. Both builds are configured
On Tue, May 20, 2008 at 11:26:40PM +0200, Andreas Barth wrote:
how do we continue here? Is the issue just that the headers are being
moved twice? This bug blocks testing migration of python2.5 and epiphany
which is a precondition for getting gcc-4.3 and gcc-defaults moved.
The fix in the easy
* Matthias Klose ([EMAIL PROTECTED]) [080521 12:13]:
that looks ok for now, we can work on the unification of the headers
later.
In case Thiemo agrees (or doesn't disagree) - do you plan to upload it?
Should I NMU it? ...?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To
--- Comment #6 from rguenth at gcc dot gnu dot org 2008-05-21 10:39 ---
Mark, you made this P5, but ia64-linux is a secondary platform. P3 again to
get it on the radar. But not higher priority because we don't have exactly
what
I would call a testcase.
--
rguenth at gcc dot gnu
that looks ok for now, we can work on the unification of the headers
later.
Matthias
Arthur Loiret writes:
On Tue, May 20, 2008 at 11:26:40PM +0200, Andreas Barth wrote:
how do we continue here? Is the issue just that the headers are being
moved twice? This bug blocks testing migration of
Andreas Barth wrote:
* Matthias Klose ([EMAIL PROTECTED]) [080521 12:13]:
that looks ok for now, we can work on the unification of the headers
later.
In case Thiemo agrees (or doesn't disagree) - do you plan to upload it?
Should I NMU it? ...?
I disagree, because I was confused about the
--- Comment #2 from rguenth at gcc dot gnu dot org 2008-05-21 14:18 ---
*** This bug has been marked as a duplicate of 30052 ***
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #55 from rguenth at gcc dot gnu dot org 2008-05-21 14:18
---
*** Bug 36290 has been marked as a duplicate of this bug. ***
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #4 from sje at cup dot hp dot com 2008-05-21 15:30 ---
Now I can reproduce it. I don't know if you intended this or not but the clean
target in the Makefile removed the good objects but left the bad one so that
when I rebuilt I still had the old bad object around.
--
--
giovannibajo at libero dot it changed:
What|Removed |Added
CC||giovannibajo at libero dot
|
--- Comment #56 from giovannibajo at libero dot it 2008-05-21 15:49 ---
What is the workaround for this bug? It looks like not even -O1 fixes the
compile-time hog.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30052
--- You are receiving this mail because: ---
You are on
--- Comment #57 from rguenth at gcc dot gnu dot org 2008-05-21 15:51
---
Fixed since 4.3.0, WONTFIX on earlier branches.
There is no workaround.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30052
--- You are receiving this mail because: ---
You are on the CC list for
--- Comment #58 from rguenth at gcc dot gnu dot org 2008-05-21 16:05
---
Note that for 4.3 the testcases are still slow and memory-hungry but not
because
of PTA but because of memory partitioning (we have a PR for that) and because
of call clobber analysis.
tree find ref. vars :
--- Comment #59 from rguenth at gcc dot gnu dot org 2008-05-21 16:07
---
- PR36291.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30052
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.
--
To UNSUBSCRIBE,
libffi_3.0.5-3_i386.changes uploaded successfully to localhost
along with the files:
libffi_3.0.5-3.dsc
libffi_3.0.5-3.diff.gz
libffi-dev_3.0.5-3_i386.deb
lib64ffi-dev_3.0.5-3_i386.deb
libffi5_3.0.5-3_i386.deb
lib64ffi5_3.0.5-3_i386.deb
libffi5-dbg_3.0.5-3_i386.deb
Greetings,
gcc-4.2_4.2.4-1_sparc.changes uploaded successfully to localhost
along with the files:
gcc-4.2_4.2.4-1.dsc
gcc-4.2_4.2.4.orig.tar.gz
gcc-4.2_4.2.4-1.diff.gz
gcc-4.2-source_4.2.4-1_all.deb
libstdc++6-4.2-doc_4.2.4-1_all.deb
gcc-4.2-locales_4.2.4-1_all.deb
Accepted:
cpp-4.2_4.2.4-1_sparc.deb
to pool/main/g/gcc-4.2/cpp-4.2_4.2.4-1_sparc.deb
g++-4.2-multilib_4.2.4-1_sparc.deb
to pool/main/g/gcc-4.2/g++-4.2-multilib_4.2.4-1_sparc.deb
g++-4.2_4.2.4-1_sparc.deb
to pool/main/g/gcc-4.2/g++-4.2_4.2.4-1_sparc.deb
gcc-4.2-base_4.2.4-1_sparc.deb
to
Accepted:
lib64ffi-dev_3.0.5-3_i386.deb
to pool/main/libf/libffi/lib64ffi-dev_3.0.5-3_i386.deb
lib64ffi5_3.0.5-3_i386.deb
to pool/main/libf/libffi/lib64ffi5_3.0.5-3_i386.deb
libffi-dev_3.0.5-3_i386.deb
to pool/main/libf/libffi/libffi-dev_3.0.5-3_i386.deb
libffi5-dbg_3.0.5-3_i386.deb
to
Your message dated Wed, 21 May 2008 19:47:14 +
with message-id [EMAIL PROTECTED]
and subject line Bug#481628: fixed in libffi 3.0.5-3
has caused the Debian Bug report #481628,
regarding FTBFS on mips/mipsel
to be marked as done.
This means that you claim that the problem has been dealt with.
gcc-4.2_4.2.4-1_i386.changes uploaded successfully to localhost
along with the files:
gcc-4.2-base_4.2.4-1_i386.deb
cpp-4.2_4.2.4-1_i386.deb
gobjc++-4.2-multilib_4.2.4-1_i386.deb
gobjc++-4.2_4.2.4-1_i386.deb
gobjc-4.2-multilib_4.2.4-1_i386.deb
gobjc-4.2_4.2.4-1_i386.deb
Accepted:
cpp-4.2_4.2.4-1_powerpc.deb
to pool/main/g/gcc-4.2/cpp-4.2_4.2.4-1_powerpc.deb
g++-4.2-multilib_4.2.4-1_powerpc.deb
to pool/main/g/gcc-4.2/g++-4.2-multilib_4.2.4-1_powerpc.deb
g++-4.2_4.2.4-1_powerpc.deb
to pool/main/g/gcc-4.2/g++-4.2_4.2.4-1_powerpc.deb
22 matches
Mail list logo
