public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hutchinsonandy at aim dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/32871] [avr] Bad optimisation - gcc is pushing too many registers
Date: Mon, 28 Apr 2008 00:59:00 -0000	[thread overview]
Message-ID: <20080428005915.358.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32871-14897@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from hutchinsonandy at aim dot com  2008-04-28 00:59 -------
Attached is INCOMPLETE attempt to fix this issue.

Register saves appear to be ok. But same function is required for Argument
pointer elimination offset. It would appear DF chain info is not maintained,
when global.c  uses this. So offset used to access arguments on stack does not
reflect final value required and will fail.


-- 


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


  parent reply	other threads:[~2008-04-28  0:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 19:22 [Bug c/32871] New: Bad optimasation - Gcc is pushing to " info at umfragen-service dot de
2007-07-29 16:12 ` [Bug target/32871] " info at umfragen-service dot de
2008-02-19  2:45 ` [Bug target/32871] [avr] Bad optimisation - gcc is pushing too " eric dot weddington at atmel dot com
2008-03-02 17:22 ` hutchinsonandy at aim dot com
2008-03-02 23:33 ` hutchinsonandy at aim dot com
2008-04-23 22:55 ` eric dot weddington at atmel dot com
2008-04-28  0:59 ` hutchinsonandy at aim dot com [this message]
2008-04-28  0:59 ` hutchinsonandy at aim dot com
2008-05-05  1:16 ` hutchinsonandy at gcc dot gnu dot org
2008-05-28  0:46 ` hutchinsonandy at gcc dot gnu dot org
2010-01-29 17:02 ` 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=20080428005915.358.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).