public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/45962] [4.6 Regression]: many c/c++ failures on cris-elf, in r165236:165242
Date: Tue, 19 Oct 2010 15:49:00 -0000 [thread overview]
Message-ID: <20101019154900.w9mB3hhVpowHym5Yr_e8wTNCWl3WZLskDrgHFFjdODM@z> (raw)
In-Reply-To: <bug-45962-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45962
Richard Henderson <rth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |NEW
--- Comment #16 from Richard Henderson <rth at gcc dot gnu.org> 2010-10-19 15:49:02 UTC ---
(In reply to comment #15)
> ... though the vector alignment is neither explicit nor mandatory.
It's implicit in the DImode mode of the type. If you'd like to reduce
the alignment of local variables, use the MINIMUM_ALIGNMENT macro; see
the i386 port for an example.
> No such dynamic allocation at r165239.
Yes, that's the whole point of the patch, to honor alignment as given.
> When doing so, it feels it needs to save the stack-pointer. That's
> redundant; it's already saved when a frame-pointer is needed.
The cris port fails to define EXIT_IGNORE_STACK to indicate this.
Without that, the middle-end thinks it must save/restore sp around
the function. Frankly, there's nothing otherwise unusual about this
new alloca from any other. I guess you've just never noticed this
extra save previously?
> It so emits "move.d $sp,[$r8-8]" ... Where it gets the -8 from, I don't
> know, I'll look further.
I assume that's a stack slot for a spilled pseudo?
next prev parent reply other threads:[~2010-10-19 15:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 3:26 [Bug rtl-optimization/45962] New: " hp at gcc dot gnu.org
2010-10-11 17:27 ` [Bug rtl-optimization/45962] " rth at gcc dot gnu.org
2010-10-11 17:38 ` hp at gcc dot gnu.org
2010-10-11 17:38 ` hp at gcc dot gnu.org
2010-10-11 18:12 ` rth at gcc dot gnu.org
2010-10-11 22:46 ` [Bug middle-end/45962] " rth at gcc dot gnu.org
2010-10-12 2:31 ` hp at gcc dot gnu.org
2010-10-12 15:53 ` rth at gcc dot gnu.org
2010-10-12 15:55 ` rth at gcc dot gnu.org
2010-10-12 19:30 ` hp at gcc dot gnu.org
2010-10-12 20:23 ` hp at gcc dot gnu.org
2010-10-12 21:31 ` rth at gcc dot gnu.org
2010-10-12 21:55 ` hp at gcc dot gnu.org
2010-10-12 22:06 ` rth at gcc dot gnu.org
2010-10-12 22:16 ` hp at gcc dot gnu.org
2010-10-12 22:49 ` hp at gcc dot gnu.org
2010-10-19 2:38 ` hp at gcc dot gnu.org
2010-10-19 15:49 ` rth at gcc dot gnu.org [this message]
2010-10-19 22:22 ` hp at gcc dot gnu.org
2010-10-19 23:21 ` rth at gcc dot gnu.org
2010-11-03 15:39 ` rguenth at gcc dot gnu.org
2010-11-15 11:34 ` rguenth at gcc dot gnu.org
2011-03-11 4:42 ` hp 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=20101019154900.w9mB3hhVpowHym5Yr_e8wTNCWl3WZLskDrgHFFjdODM@z \
--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).