From: ddmetro <puzzlesdj@gmail.com>
To: gcc@gcc.gnu.org
Subject: help on - how to specify architecture information to gcc
Date: Mon, 21 Sep 2009 11:52:00 -0000 [thread overview]
Message-ID: <25530300.post@talk.nabble.com> (raw)
Hi All,
Our project is to optimize instruction scheduling in gcc. It
requires us to specify architecture information
(basically number of cycles per instruction, stall and branch delays)
to gcc, to optimize structural hazard detection.
Problem: Is there any specific format in which we can specify this
information to gcc? Is it possible to embed this additional
architecture specific detail, in .md files?
Target language for which optimization is being done: C
Target machine architecture: i686
GCC version: 4.4.1
If none of the above options work, we were planning to put
the information manually in a file and make gcc read it each time it
loads. Any suggestions/comments on this approach?
Couldn't find a related thread. Hence a new one.
Thanking All,
- Dhiraj.
--
View this message in context: http://www.nabble.com/help-on---how-to-specify-architecture-information-to-gcc-tp25530300p25530300.html
Sent from the gcc - Dev mailing list archive at Nabble.com.
next reply other threads:[~2009-09-21 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 11:52 ddmetro [this message]
2009-09-21 12:18 ` Bingfeng Mei
2009-09-29 23:15 ` help on - how to get the .dfa output file in gcc ddmetro
2009-10-03 18:35 ` got " ddmetro
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=25530300.post@talk.nabble.com \
--to=puzzlesdj@gmail.com \
--cc=gcc@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).