From: n90p <nop144d@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: GCC assembling with scheduling
Date: Fri, 25 Mar 2011 11:27:00 -0000 [thread overview]
Message-ID: <31236872.post@talk.nabble.com> (raw)
In-Reply-To: <mcrbp10gmb5.fsf@google.com>
Ian Lance Taylor-3 wrote:
>
> n90p <nop144d@gmail.com> writes:
>
>> Hi all, is there any method to re-schedule instructions while compiling
>> asm
>> file? For example, i'm assembling a C file and then making changes there
>> (removing some instrucions) and then i want to re-schedule instructions.
>
> Not using gcc, no. You may want to look at the micro-architectural
> optimizer: http://code.google.com/p/mao .
>
> Ian
>
>
Thanks for your quick answer! I forgot to say that i need that kind of tool
for ARM platform (cortex-a8), but MAO, as i see is for Intel only. Anyway,
thanks :)
Vahan
--
View this message in context: http://old.nabble.com/GCC-assembling-with-scheduling-tp31230841p31236872.html
Sent from the gcc - Help mailing list archive at Nabble.com.
prev parent reply other threads:[~2011-03-25 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 16:57 n90p
2011-03-24 22:56 ` Ian Lance Taylor
2011-03-25 11:27 ` n90p [this message]
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=31236872.post@talk.nabble.com \
--to=nop144d@gmail.com \
--cc=gcc-help@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).