public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tori@unhappy.mine.nu To: gcc-gnats@gcc.gnu.org Subject: target/6040: ARM interrupt attribute generats wrong code (3.1-cvs) Date: Fri, 22 Mar 2002 08:06:00 -0000 [thread overview] Message-ID: <20020322160505.5375.qmail@sources.redhat.com> (raw) >Number: 6040 >Category: target >Synopsis: ARM interrupt attribute generats wrong code (3.1-cvs) >Confidential: no >Severity: critical >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Mar 22 08:06:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Tobias Ringstrom >Release: gcc version 3.1 20020321 (prerelease) >Organization: >Environment: Crosscompiler for arm-elf >Description: Compile the following code with "arm-elf-gcc -S" void foo(void) __attribute__((__interrupt__)); void foo() { int a=0; } gives the following assembler code: .file "tmp2.c" .text .align 2 .global foo .type foo,function foo: @ Interrupt Service Routine. @ args = 0, pretend = 0, frame = 4 @ frame_needed = 1, uses_anonymous_args = 0 str ip, [sp, #-4]! mov ip, sp sub lr, lr, #4 stmfd sp!, {r3, fp, ip, lr, pc} sub fp, ip, #4 sub sp, sp, #4 mov r3, #0 str r3, [fp, #-24] ldmea fp, {r3, fp, ip, pc}^ .Lfe1: .size foo,.Lfe1-foo .ident "GCC: (GNU) 3.1 20020321 (prerelease)" Major problem: The stack pointer (sp) is never restored! Comment/question: There are four lost bytes, but that might be due to alignment of the stack. Is it? /Tobias >How-To-Repeat: See Description above! >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-03-22 16:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-22 8:06 tori [this message] 2002-04-18 9:04 mmitchel 2003-05-17 3:06 target/6040: [ARM] " Dara Hazeghi
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=20020322160505.5375.qmail@sources.redhat.com \ --to=tori@unhappy.mine.nu \ --cc=gcc-gnats@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).