public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49881] [AVR] Inefficient stack manipulation around calls
Date: Thu, 28 Jul 2011 16:12:00 -0000 [thread overview]
Message-ID: <bug-49881-4-iYdCuVtcAg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49881-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49881
Georg-Johann Lay <gjl at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |49864
--- Comment #5 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2011-07-28 16:10:35 UTC ---
(In reply to comment #4)
> Created attachment 24857 [details]
> patch to generate pushes
>
> [...]
>
> Would one of you be so kind as to do a full test run?
> I don't have avr-libc et al set up on this machine...
Regenerating avr-libc (with your patch atop r176818) fails with PR49864 and the
exact line number from there. Do you need more food, or is the test case in
PR49864 sufficient to fix that PR?
next prev parent reply other threads:[~2011-07-28 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 22:40 [Bug target/49881] New: " rth at gcc dot gnu.org
2011-07-27 23:14 ` [Bug target/49881] " eric.weddington at atmel dot com
2011-07-28 0:05 ` rth at gcc dot gnu.org
2011-07-28 9:29 ` gjl at gcc dot gnu.org
2011-07-28 15:44 ` rth at gcc dot gnu.org
2011-07-28 16:12 ` gjl at gcc dot gnu.org [this message]
2011-07-28 16:15 ` rth at gcc dot gnu.org
2011-07-29 14:40 ` gjl at gcc dot gnu.org
2011-08-01 19:36 ` rth at gcc dot gnu.org
2011-08-02 17:38 ` rth at gcc dot gnu.org
2011-08-02 22:24 ` rth at gcc dot gnu.org
2011-08-02 22:24 ` rth at gcc dot gnu.org
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-49881-4-iYdCuVtcAg@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).