public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ysrumyan at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/55970] [x86] Avoid reverse order of function argument gimplifying
Date: Fri, 01 Feb 2013 13:34:00 -0000	[thread overview]
Message-ID: <bug-55970-4-NfiJHIce7h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55970-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #5 from Yuri Rumyantsev <ysrumyan at gmail dot com> 2013-02-01 13:34:20 UTC ---
I sent for review a simple fix that can be considered as workaround for this
issue - I simply change macros

#define PUSH_ARGS_REVERSED TARGET_PUSH_ARGS

that allows user to preserve an order of function arguments evaluation if
"-mno-push-args" option was added to compile.

I also checked that adding that option will not affect on performance for
Corei7 and Atom platforms.

With modified gcc attached test is passed:

gcc -O2 t.c t_main.c -mno-push-args
./a.out
Test Passed


  parent reply	other threads:[~2013-02-01 13:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 14:44 [Bug tree-optimization/55970] New: " ysrumyan at gmail dot com
2013-01-14 14:47 ` [Bug tree-optimization/55970] " ysrumyan at gmail dot com
2013-01-14 14:56 ` rguenth at gcc dot gnu.org
2013-01-14 15:16 ` ysrumyan at gmail dot com
2013-01-14 17:34 ` pinskia at gcc dot gnu.org
2013-02-01 13:34 ` ysrumyan at gmail dot com [this message]
2013-02-04 11:15 ` manu 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-55970-4-NfiJHIce7h@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).