public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bernie at develer dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/13312] [m68k] C++ produces stack frame damaging code for Coldfire Date: Mon, 19 Jan 2004 05:05:00 -0000 [thread overview] Message-ID: <20040119050537.21741.qmail@sources.redhat.com> (raw) In-Reply-To: <20031205063124.13312.Steve@Zook.com> ------- Additional Comments From bernie at develer dot com 2004-01-19 05:05 ------- I've tried to reproduce this problem with: - GCC 3.4 (20040114) + Andreas cc0 patch - GCC 3.3.3 (20031222) + my ColdFire/uClinux patch set In both cases, the generated code seems to be correct, assuming I'm looking at the same variable: GCC 3.4: move.w %d0,-2(%a6) [...] clr.l %d0 move.w -2(%a6),%d0 add.l %d0,88(%a5) move.w 94(%a5),%d0 GCC 3.3.3: move.w %d0,-6(%a6) [...] clr.l %d0 move.w -6(%a6),%d0 add.l %d0,88(%a4) move.w 94(%a4),%d0 Please test with the latest 3_3-branch snapshot. If you still see the problem, try applying all these patches in the given order: http://www.develer.com/uclinux/uclinux-tools-20031230/gcc-3.3.2-coldfire-targets.patch http://www.develer.com/uclinux/uclinux-tools-20031230/gcc-3.3.2-coldfire-frame.patch http://www.develer.com/uclinux/uclinux-tools-20031230/gcc-3.3.2-uclinux-idshlib.patch http://www.develer.com/uclinux/uclinux-tools-20031230/gcc-3.3.2-uclinux-thunk.patch http://www.develer.com/uclinux/uclinux-tools-20031230/gcc-3.3.2-uclinux-specs.patch http://www.develer.com/uclinux/uclinux-tools-20031230/gcc-3.3.2-coldfire-omitfrmptr.patch The uClinux patches are not relevant to you, but you need them in order to apply dependent ColdFire patches. If any of these patches fixes the problem for you, I'll prepare a standalone version that applies to 3_3-branch and submit it for this PR. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13312
next prev parent reply other threads:[~2004-01-19 5:05 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-12-05 6:31 [Bug c++/13312] New: " Steve at Zook dot com 2003-12-05 6:34 ` [Bug c++/13312] " Steve at Zook dot com 2003-12-05 6:39 ` [Bug target/13312] " pinskia at gcc dot gnu dot org 2004-01-18 17:55 ` [Bug target/13312] [m68k] " dhazeghi at yahoo dot com 2004-01-19 5:05 ` bernie at develer dot com [this message] 2004-01-21 17:00 ` dhazeghi at yahoo dot com 2004-01-24 7:08 ` Steve at Zook dot com 2004-01-25 5:01 ` Steve at Zook dot com 2004-01-25 9:59 ` bernie at develer dot com 2004-01-29 3:31 ` dhazeghi at yahoo dot com 2004-01-29 13:38 ` bernie at develer dot com 2004-06-10 8:03 ` bernie at develer dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040119050537.21741.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).