[Bug rtl-optimization/34845] [4.3.0 20080111] mips16 : branch in branch delay slot

2008-01-17 Thread armcc2000 at yahoo dot com
--- Comment #1 from armcc2000 at yahoo dot com 2008-01-18 03:57 --- Bug is invalid: branches in mips16 don't have delay slots. The cause of the problems I was seeing was found elsewhere. Sorry for the noise... -- armcc2000 at yahoo dot com changed: What|Re

[Bug c/34845] New: [4.3.0 20080111] mips16 : branch in branch delay slot

2008-01-17 Thread armcc2000 at yahoo dot com
Summary: [4.3.0 20080111] mips16 : branch in branch delay slot Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: armcc20

[Bug target/25281] [3.4/4.0 only] Request fix for Bug #23150 (aka Bug #24675) in gcc 3.4.x and gcc 4.0.x for arm arch.

2006-01-18 Thread armcc2000 at yahoo dot com
--- Comment #3 from armcc2000 at yahoo dot com 2006-01-18 19:28 --- (In reply to comment #2) > > Kazu, does your patch for PR 23150 apply to 4.0? If so, would you please > test that change? I think we've tried that already. Patch applies to 4.0.2 without problems, but i

[Bug target/24675] Stack corruption in ARM arch. if 64bit variable is passed to a function of which the low 32 use the register and the up 32 use the stack

2005-11-09 Thread armcc2000 at yahoo dot com
--- Comment #9 from armcc2000 at yahoo dot com 2005-11-10 01:25 --- (In reply to comment #8) > > Yes then this is a dup of that bug then. The problem is that the middle-end > did not know what the target was doing so it rejected sib calling in this > case. > Any ide

[Bug target/24675] Stack corruption in ARM arch. if 64bit variable is passed to a function of which the low 32 use the register and the up 32 use the stack

2005-11-09 Thread armcc2000 at yahoo dot com
--- Comment #7 from armcc2000 at yahoo dot com 2005-11-09 23:32 --- (In reply to comment #4) > > I think this is a dup of bug 23150 which was fixed in 4.1.0. > Something has certainly changed in 4.1 - the stack corruption is gone. With -Os, the good() and bad() testcases c

[Bug target/24675] Stack corruption in ARM arch. if 64bit variable is passed to a function of which the low 32 use the register and the up 32 use the stack

2005-11-08 Thread armcc2000 at yahoo dot com
--- Comment #5 from armcc2000 at yahoo dot com 2005-11-09 06:21 --- (In reply to comment #4) > I think this is a dup of bug 23150 which was fixed in 4.1.0. > I don't think so. I rebuilt 4.0.2 after applying the patch given for bug 23150. The patched version of 4.0.2 giv

[Bug inline-asm/24751] ARM : poor register allocation around inline assembler

2005-11-08 Thread armcc2000 at yahoo dot com
--- Comment #3 from armcc2000 at yahoo dot com 2005-11-09 05:56 --- Yes, I think you're absolutely correct. You've also just explained a bug I've been staring at all day ;-) Reading action->dev_id was causing a segfault and I couldn't understand why r0 and r7 in

[Bug inline-asm/24751] New: ARM : poor register allocation around inline assembler

2005-11-08 Thread armcc2000 at yahoo dot com
Component: inline-asm AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: armcc2000 at yahoo dot com GCC host triplet: i686-host_pc-linux-gnu GCC target triplet: arm-9tdmi-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24751

[Bug target/24675] Stack corruption in ARM arch. if 64bit variable is passed to a function of which the low 32 use the register and the up 32 use the stack

2005-11-08 Thread armcc2000 at yahoo dot com
--- Comment #3 from armcc2000 at yahoo dot com 2005-11-09 04:21 --- A few more results... 1) gcc 4.0.2 _is_ also buggy 2) Bug seems to be associated with -foptimize-sibling-calls ie previous code compiled with: arm-linux-gcc-4.0.2 -O1 -foptimize-sibling-calls gives: .align

[Bug target/24675] Stack corruption in ARM arch. if 64bit variable is passed to a function of which the low 32 use the register and the up 32 use the stack

2005-11-08 Thread armcc2000 at yahoo dot com
--- Comment #2 from armcc2000 at yahoo dot com 2005-11-09 02:11 --- Here's a slightly smaller test case: extern void foo (int f1, int f2, int f3, int f4, int f5, int f6); void good (int g1, int g2, int g3, int g4, i