public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamesl at appliedminds dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/12084] New: 3.3.1 emitting strange stack handling code for ARM interrupts Date: Thu, 28 Aug 2003 01:12:00 -0000 [thread overview] Message-ID: <20030828011206.12084.jamesl@appliedminds.com> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12084 Summary: 3.3.1 emitting strange stack handling code for ARM interrupts Product: gcc Version: 3.3.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jamesl at appliedminds dot com CC: gcc-bugs at gcc dot gnu dot org The following was compiled with arm-elf-gcc -S -g -O2 -Wall -mcpu=arm7tdmi void int_handler(void) __attribute__((interrupt("IRQ"))); void foo(void) { } void int_handler(void) { foo(); } It emitted this assembly for int_handler: int_handler: .LFB5: .loc 1 8 0 @ Interrupt Service Routine. @ args = 0, pretend = 0, frame = 0 @ frame_needed = 1, uses_anonymous_args = 0 str ip, [sp, #-4]! mov ip, sp .LCFI0: stmfd sp!, {r0, r1, r2, r3, fp, ip, lr, pc} .LCFI1: sub fp, ip, #4 .LCFI2: .loc 1 9 0 bl foo ldmea fp, {r0, r1, r2, r3, fp, sp, lr} ldmfd sp!, {ip} subs pc, lr, #4 1) The stack pointer is not being reset to its original location. 2) One of those ldm** needs a ^ after it to restore the correct CPSR. This seems to be the same bug as in 3.2
next reply other threads:[~2003-08-28 1:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-08-28 1:12 jamesl at appliedminds dot com [this message] 2003-08-28 1:12 ` [Bug c/12084] " jamesl at appliedminds dot com 2003-08-28 1:13 ` jamesl at appliedminds dot com 2003-08-29 16:22 ` [Bug target/12084] " pinskia at gcc dot gnu dot org 2003-09-01 9:20 ` rearnsha at gcc dot gnu dot org
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=20030828011206.12084.jamesl@appliedminds.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).