public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sb-sf at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/39287]  New: corrupted prologue generated
Date: Tue, 24 Feb 2009 10:14:00 -0000	[thread overview]
Message-ID: <bug-39287-17356@http.gcc.gnu.org/bugzilla/> (raw)

int a(int *);

int b()
{
  int Tmp[2];
  d(Tmp);
}

produces bad prologue:
        .text
.global b
        .type   b, @function
b:
        push r29
        push r28
        rcall .
        rcall .
        rcall .
        in r28,__SP_L__
        in r29,__SP_H__
/* prologue: function */
/* frame size = 6 */
        movw r24,r28
        adiw r24,1
        rcall d
/* epilogue start */
        adiw r28,6
        in __tmp_reg__,__SREG__
        cli
        out __SP_H__,r29
        out __SREG__,__tmp_reg__
        out __SP_L__,r28
        pop r28
        pop r29
        ret
        .size   b, .-b


-- 
           Summary: corrupted prologue generated
           Product: gcc
           Version: 4.3.2
            Status: UNCONFIRMED
          Severity: critical
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sb-sf at users dot sourceforge dot net
GCC target triplet: avr


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


             reply	other threads:[~2009-02-24 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24 10:14 sb-sf at users dot sourceforge dot net [this message]
2009-02-24 10:16 ` [Bug c/39287] " sb-sf at users dot sourceforge dot net
2009-02-24 13:53 ` [Bug target/39287] " eric dot weddington at atmel dot com
2009-02-24 17:52 ` eric dot weddington at atmel dot com
2009-02-24 20:57 ` sb-sf at users dot sourceforge dot net
2009-02-25  1:29 ` eric dot weddington at atmel 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=bug-39287-17356@http.gcc.gnu.org/bugzilla/ \
    --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).