From: ddmetro <puzzlesdj@gmail.com>
To: gcc@gcc.gnu.org
Subject: RE: got the .dfa output file in gcc
Date: Sat, 03 Oct 2009 18:35:00 -0000 [thread overview]
Message-ID: <25731469.post@talk.nabble.com> (raw)
In-Reply-To: <25672458.post@talk.nabble.com>
Hi All,
Got the output i386.dfa file in the location -
{$gcc_home}/host-i686-pc-linux-gnu/gcc.
Followed 2 steps:
1. In the initiate_automaton_gen() function of 'genautomata.c', initialize
the v_flag variable to 1 i.e., v_flag = 1;
2. Build target 'insn-automata.c'.
-Dhiraj
--
View this message in context: http://www.nabble.com/help-on---how-to-specify-architecture-information-to-gcc-tp25530300p25731469.html
Sent from the gcc - Dev mailing list archive at Nabble.com.
prev parent reply other threads:[~2009-10-03 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 11:52 help on - how to specify architecture information to gcc ddmetro
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 ` ddmetro [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=25731469.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).