public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bingfeng Mei" <bmei@broadcom.com>
To: ddmetro <puzzlesdj@gmail.com>, 	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: RE: help on - how to specify architecture information to gcc
Date: Mon, 21 Sep 2009 12:18:00 -0000	[thread overview]
Message-ID: <7FB04A5C213E9943A72EE127DB74F0AD93CCB63038@SJEXCHCCR02.corp.ad.broadcom.com> (raw)
In-Reply-To: <25530300.post@talk.nabble.com>

You should check how to construct DFA for your target architecture.
Look at "Specifying processor pipeline description" in GCC internal
manual and checked out how other architectures do it.


-Bingfeng 

> -----Original Message-----
> From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] On 
> Behalf Of ddmetro
> Sent: 21 September 2009 12:52
> To: gcc@gcc.gnu.org
> Subject: help on - how to specify architecture information to gcc
> 
> 
> 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-in
> formation-to-gcc-tp25530300p25530300.html
> Sent from the gcc - Dev mailing list archive at Nabble.com.
> 
> 
> 

  reply	other threads:[~2009-09-21 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 11:52 ddmetro
2009-09-21 12:18 ` Bingfeng Mei [this message]
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=7FB04A5C213E9943A72EE127DB74F0AD93CCB63038@SJEXCHCCR02.corp.ad.broadcom.com \
    --to=bmei@broadcom.com \
    --cc=gcc@gcc.gnu.org \
    --cc=puzzlesdj@gmail.com \
    /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).