Bug#133574: other/9081: gcc doesn't diagnose, that the compiler exceeds a compiler limit

2003-01-26 Thread rth
Synopsis: gcc doesn't diagnose, that the compiler exceeds a compiler limit State-Changed-From-To: open-closed State-Changed-By: rth State-Changed-When: Sun Jan 26 09:39:58 2003 State-Changed-Why: This isn't a compiler problem. There is no compiler limit that has been exceeded. Indeed,

Bug#85468: target/9082: [alpha,ia64] memcpy makes unaligned access

2003-01-26 Thread rth
Synopsis: [alpha,ia64] memcpy makes unaligned access State-Changed-From-To: open-closed State-Changed-By: rth State-Changed-When: Sun Jan 26 10:22:31 2003 State-Changed-Why: When submitting bugs to gcc, one must include the test case, not reference it in some package elsewhere. This

Bug#136659: target/9080: optimisation on sparc leads to unalligned access in memcpy

2003-01-26 Thread rth
Synopsis: optimisation on sparc leads to unalligned access in memcpy Responsible-Changed-From-To: unassigned-rth Responsible-Changed-By: rth Responsible-Changed-When: Sun Jan 26 10:13:38 2003 Responsible-Changed-Why: . State-Changed-From-To: open-closed State-Changed-By: rth

Bug#169004: target/9082: [alpha,ia64] memcpy makes unaligned access

2003-01-26 Thread Herbert Xu
On Sun, Jan 26, 2003 at 10:22:31AM -, [EMAIL PROTECTED] wrote: Synopsis: [alpha,ia64] memcpy makes unaligned access State-Changed-From-To: open-closed State-Changed-By: rth State-Changed-When: Sun Jan 26 10:22:31 2003 State-Changed-Why: When submitting bugs to gcc, one must include

Bug#136659: target/9080: optimisation on sparc leads to unalligned access in memcpy

2003-01-26 Thread Bernd Eckenfels
On Sun, Jan 26, 2003 at 10:13:38AM -, [EMAIL PROTECTED] wrote: Synopsis: optimisation on sparc leads to unalligned access in memcpy I'm fairly sure this has been discussed before, but I can't find the reference right away. The problem is known, and I consider the input

Bug#133574: other/9081: gcc doesn't diagnose, that the compiler exceeds a compiler limit

2003-01-26 Thread Pavel Machek
Hi! Synopsis: gcc doesn't diagnose, that the compiler exceeds a compiler limit State-Changed-From-To: open-closed State-Changed-By: rth State-Changed-When: Sun Jan 26 09:39:58 2003 State-Changed-Why: This isn't a compiler problem. There is no compiler limit that has been

Processed: reassigning issue in kernel

2003-01-26 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: reassign 133574 kernel-source-2.4.20 Bug#133574: [PR other/9081] gcc doesn't diagnose, that the compiler exceeds a compiler limit Bug reassigned from package `gcc' to `kernel-source-2.4.20'. thanks Stopping processing here. Please contact me if you

Bug#178561: gcc-3.2-doc: stream::attach(int fd) porting entry out-of-date

2003-01-26 Thread herbert
Package: gcc-3.2-doc Version: 1:3.2.2ds5-0pre6 Severity: normal The stream::attach entry in porting-howto.html does not mention the stdio_filebuf as an alternative. -- System Information Debian Release: testing/unstable Kernel Version: Linux gondolin 2.4.20-686-smp #1 SMP Mon Jan 13 23:06:41 EST