public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46208] TARGET_PROMOTE_PROTOTYPES for SPARC V8
Date: Thu, 28 Oct 2010 10:57:00 -0000 [thread overview]
Message-ID: <20101028105700.yuoVu8Qm3ZPhRfvRrR5jkeesakrQbP7C1rtmmr9MlUs@z> (raw)
In-Reply-To: <bug-46208-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46208
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebotcazou at gcc dot
| |gnu.org
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2010-10-28 10:57:12 UTC ---
> we modified the function *TARGET_PROMOTE_PROTOTYPES
> *(http://goo.gl/2pQQ) and set it to the default value which is FALSE.
>
> static bool
> sparc_promote_prototypes (const_tree fntype ATTRIBUTE_UNUSED)
> {
> return TARGET_ARCH32 ? true : false;
> }
>
> was replaced by
>
> static bool
> sparc_promote_prototypes (const_tree fntype ATTRIBUTE_UNUSED)
> {
> return false;
> }
This will result in violations of the ABI without further changes (garbage in
the upper part of the argument registers). You need the patch I'm about to
attach as a minimum, but it cannot eliminate the extensions in the caller
alone, more work is required in the back-end. At which point changing
TARGET_PROMOTE_PROTOTYPES will probably have only a marginal effect.
next prev parent reply other threads:[~2010-10-28 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 8:11 [Bug target/46208] New: " jorge.perez at invia dot fr
2010-10-28 10:57 ` ebotcazou at gcc dot gnu.org [this message]
2010-10-28 10:59 ` [Bug target/46208] redundant extensions of argument registers ebotcazou at gcc dot gnu.org
2010-10-28 11:03 ` ebotcazou at gcc dot gnu.org
2010-11-03 0:19 ` ebotcazou at gcc dot gnu.org
2010-11-08 12:15 ` ebotcazou at gcc dot gnu.org
2010-11-08 16:04 ` pinskia at gcc dot gnu.org
2010-11-08 17:46 ` ebotcazou at gcc dot gnu.org
2010-11-15 12:35 ` jorge.perez at invia dot fr
2010-11-19 8:18 ` ebotcazou 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=20101028105700.yuoVu8Qm3ZPhRfvRrR5jkeesakrQbP7C1rtmmr9MlUs@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).