This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
for the C language, c-parse.in : the grammar definition c-parse.gperf: terminal symbols, or tokens tree.def : TREE nodes definitions tree.h : TREE nodes accessing macros and other for the C++ language If you want to make simple extensions you _probably_ just have to modify c-parse.in. It's a bi tmore complicated if you need more terminal symbols (you have to hack c-parse.gperf). To add completely new language constructs you must not only extend the grammar, you also must handle these new constructs through the whole compiler flow. That's not so easy, but not impossible. Hope this could be enough to start, feel free to ask more. benedetto Dynamic One > Hi all, > > What are all the files have to be modified or what is the procedure have to > be followed to make the GCC compiler to accept the extended input language > specifications at its front end. > > Any suggestion in this regard higly appreciated. > > Thanks for your time and consideration. > Manikandan.V > ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |