public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/6039: [ARM] interrupt attribute generats wrong code
Date: Sat, 17 May 2003 02:56:00 -0000	[thread overview]
Message-ID: <20030517025601.26819.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/6039; it has been noted by GNATS.

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: tori@unhappy.mine.nu, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: target/6039: [ARM] interrupt attribute generats wrong code
Date: Fri, 16 May 2003 19:48:47 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=6039
 
 Hello,
 
 gcc 3.0.4 and 3.1 cvs are rather ancient at this point. Would it be  
 possible for you to check whether this problem is still present. I  
 don't know much about arm assembly, but this is what 3.3 produces:
          .file   "junk.c"
          .text
          .align  2
          .global foo
          .type   foo, %function
 foo:
          @ Interrupt Service Routine.
          @ args = 0, pretend = 0, frame = 12
          @ frame_needed = 1, uses_anonymous_args = 0
          str     ip, [sp, #-4]!
          mov     ip, sp
          sub     lr, lr, #4
          stmfd   sp!, {r0, r1, r2, r3, fp, ip, lr, pc}
          sub     fp, ip, #4
          sub     sp, sp, #12
          mov     r3, #0
          str     r3, [fp, #-40]
          mov     r3, #0
          str     r3, [fp, #-44]
          ldr     r2, [fp, #-40]
          ldr     r3, [fp, #-44]
          add     r3, r2, r3
          str     r3, [fp, #-48]
          bl      bar
          ldmea   fp, {r0, r1, r2, r3, fp, ip, pc}^
          .size   foo, .-foo
          .ident  "GCC: (GNU) 3.3 20030508 (prerelease)"
 
 gcc mainline produces:
          .file   "junk.c"
          .text
          .align  2
          .global foo
          .type   foo, %function
 foo:
          @ Interrupt Service Routine.
          @ args = 0, pretend = 0, frame = 12
          @ frame_needed = 1, uses_anonymous_args = 0
          str     ip, [sp, #-4]!
          mov     ip, sp
          stmfd   sp!, {r0, r1, r2, r3, fp, ip, lr, pc}
          sub     fp, ip, #4
          sub     sp, sp, #12
          mov     r3, #0
          str     r3, [fp, #-40]
          mov     r3, #0
          str     r3, [fp, #-44]
          ldr     r2, [fp, #-40]
          ldr     r3, [fp, #-44]
          add     r3, r2, r3
          str     r3, [fp, #-48]
          bl      bar
          ldmea   fp, {r0, r1, r2, r3, fp, sp, lr}
          ldmfd   sp!, {ip}
          subs    pc, lr, #4
          .size   foo, .-foo
          .ident  "GCC: (GNU) 3.4 20030508 (experimental)"
 
 
 Can you confirm if these are correct? Thanks,
 
 Dara
 


             reply	other threads:[~2003-05-17  2:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17  2:56 Dara Hazeghi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-17  6:58 giovannibajo
2002-04-18  9:03 target/6039: ARM " mmitchel
2002-03-22  7:56 tori

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=20030517025601.26819.qmail@sources.redhat.com \
    --to=dhazeghi@yahoo.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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: link
Be 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).