public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eweddington at cso dot atmel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/16563] The compiler doesnt the necessary push/restore of  r18/r19
Date: Wed, 14 Feb 2007 16:48:00 -0000	[thread overview]
Message-ID: <20070214164811.17725.qmail@sourceware.org> (raw)
In-Reply-To: <bug-16563-8949@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from eweddington at cso dot atmel dot com  2007-02-14 16:48 -------
Same results with GCC 4.1.1:

00000000 <testfunc>:
   0:   af 92           push    r10
   2:   bf 92           push    r11
   4:   cf 92           push    r12
   6:   df 92           push    r13
   8:   ef 92           push    r14
   a:   ff 92           push    r15
   c:   0f 93           push    r16
   e:   1f 93           push    r17
  10:   f6 2e           mov     r15, r22
  12:   e4 2e           mov     r14, r20
  14:   a0 2e           mov     r10, r16
  16:   b1 2e           mov     r11, r17
  18:   c2 2e           mov     r12, r18
  1a:   d3 2e           mov     r13, r19
  1c:   00 d0           rcall   .+0             ; 0x1e <testfunc+0x1e>
  1e:   8a e0           ldi     r24, 0x0A       ; 10
  20:   00 d0           rcall   .+0             ; 0x22 <testfunc+0x22>
  22:   8f 2d           mov     r24, r15
  24:   00 d0           rcall   .+0             ; 0x26 <testfunc+0x26>
  26:   8b e0           ldi     r24, 0x0B       ; 11
  28:   90 e0           ldi     r25, 0x00       ; 0
  2a:   00 d0           rcall   .+0             ; 0x2c <testfunc+0x2c>
  2c:   8e 2d           mov     r24, r14
  2e:   00 d0           rcall   .+0             ; 0x30 <testfunc+0x30>
  30:   86 e0           ldi     r24, 0x06       ; 6
  32:   00 d0           rcall   .+0             ; 0x34 <testfunc+0x34>
  34:   9d 2d           mov     r25, r13
  36:   8c 2d           mov     r24, r12
  38:   7b 2d           mov     r23, r11
  3a:   6a 2d           mov     r22, r10
  3c:   00 d0           rcall   .+0             ; 0x3e <testfunc+0x3e>
  3e:   1f 91           pop     r17
  40:   0f 91           pop     r16
  42:   ff 90           pop     r15
  44:   ef 90           pop     r14
  46:   df 90           pop     r13
  48:   cf 90           pop     r12
  4a:   bf 90           pop     r11
  4c:   af 90           pop     r10
  4e:   08 95           ret


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16563


       reply	other threads:[~2007-02-14 16:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16563-8949@http.gcc.gnu.org/bugzilla/>
2007-02-14 16:48 ` eweddington at cso dot atmel dot com [this message]
2008-06-04 13:07 ` eric dot weddington at atmel dot com
     [not found] <bug-16563-4@http.gcc.gnu.org/bugzilla/>
2014-02-16 13:16 ` jackie.rosen at hushmail dot com
2004-07-15 10:30 [Bug c/16563] New: " baphomed at lycos dot de
2004-07-15 11:57 ` [Bug target/16563] " bangerth at dealii dot org
2004-07-15 20:23 ` ericw at evcohs dot com
2004-07-15 20:41 ` j dot gnu at uriah dot heep dot sax dot de
2004-08-31 18:35 ` denisc at overta dot ru
2004-09-08 13:57 ` em at la dot mine dot nu
2004-10-06 16:48 ` berndtrog at yahoo 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=20070214164811.17725.qmail@sourceware.org \
    --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: 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).