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/51345] [avr] Devices with 8-bit SP need their own multilib(s)
Date: Sat, 24 Mar 2012 21:09:00 -0000 [thread overview]
Message-ID: <bug-51345-4-qnYyYfvHZR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51345-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51345
Georg-Johann Lay <gjl at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
Target Milestone|4.7.0 |4.7.1
--- Comment #6 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2012-03-24 21:06:42 UTC ---
Reopened:
The current (4.7.0) behaviour is:
-mtiny-stack acts as multilib-option for 16-bit SP targets in avr2 and avr25,
i.e. with that switch will trigger multi-lib from ./tiny-stack resp.
./avr25/tiny-stack
The problem is that the tiny-stack multilibs mix 16-bit SP targets that are
treated as 8-bit SP, and targets with 8-bit SP.
The currect implementation assumes SP.H = 0 in tiny-stack mlibs in order to
properly initialize the frame pointer, e.g. in __prologue_saves.
This is no good for 16-bit SP targets.
Solution:
Restore the behaviour for the 16-bit SP targets as was, i.e. -mtiny-stack does
not affect multilib selection for these targets, but if specified on the
command line, the resulting code will only change SP.L and assume SP.H never
changes.
For the 8-bit SP targets, -mtiny-stack should remain as in 4.7.0, i.e. used
internally to trigger tiny-stack multilibs. Specifying -mtiny-stack on the
command line will be redundant for these targets and have no effect.
next prev parent reply other threads:[~2012-03-24 21:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 14:35 [Bug target/51345] New: " gjl at gcc dot gnu.org
2011-11-29 14:44 ` [Bug target/51345] " gjl at gcc dot gnu.org
2011-12-02 19:15 ` gjl at gcc dot gnu.org
2011-12-06 15:06 ` gjl at gcc dot gnu.org
2011-12-28 12:27 ` gjl at gcc dot gnu.org
2012-01-02 12:52 ` gjl at gcc dot gnu.org
2012-01-04 15:29 ` gjl at gcc dot gnu.org
2012-03-24 21:09 ` gjl at gcc dot gnu.org [this message]
2012-03-28 10:32 ` gjl at gcc dot gnu.org
2012-03-28 11:05 ` gjl at gcc dot gnu.org
2012-05-31 17:42 ` gjl 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-51345-4-qnYyYfvHZR@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).