Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.compilers    |    Compiler construction, theory, etc. (Mod    |    2,753 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,312 of 2,753    |
|    Sreekumar to All    |
|    Parsing the gcc assembly output    |
|    20 Apr 08 00:34:18    |
      From: vksreekumar@gmail.com              Hi All,              I would like to parse the assembly output of gcc (the *.s file that we       get when we compile the file with -s flag) to identify function calls,       function definitions and loops. I was wondering if there is a grammar       file for the assembly format printed out by gcc. Any suggestions that       might be a cleaner way to parse the assembly file would be very       helpful.              Thanks in advance              Sreekumar       [The assembler syntax is of course specific to the architecture of       your computer, but since most gcc output is assembled by the GNU       assembler gas, that's one place to start. Some architectures use .y       files, some hand coded parsers. On the other hand, for this sort of       analysis I suspect that some perl or python adhockery would work just       as well and be a lot easier. -John]              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca