This is the mail archive of the
mailing list for the GCC project.
Re: GCC Dump
- To: Daqing Hou <daqing at cs dot ualberta dot ca>
- Subject: Re: GCC Dump
- From: Nathan Sidwell <nathan at codesourcery dot com>
- Date: Fri, 14 Sep 2001 10:43:44 +0100
- CC: mark at codesourcery dot com, gcc at gcc dot gnu dot org
- Organization: Codesourcery LLC
- References: <3BA003DB.E7C8E762@cs.ualberta.ca>
Daqing Hou wrote:
> We are doing a research project on dumping the tree into an intermediate
> format. Ideally, we hope to reuse the options of the front end of gcc.
> Previously, the option to switch on the dump function is
> ``--fdump-translation-unit-the_dump_file_name'' but we found that gcc
> 3.0.1 has removed this option. Instead, a new option --``dumpbase
> <file>'' seemingly works for the purpose, is it? Could you please
> explain to us how the options are managed; what is the relation between
> gcc.c and toplev.c etc so that we can do the right `surgery'?
dumpbase appears to be undocumented. oops. It's been there for a long time
to specify the name of various RTL debugging dumps - it defaults to the name
of the source file.
Unfortunately there seem to be a number of defects in this. cc1 fails to
recognise -fdump-translation-unit (this is fixed in CVS). There's also
no way to override dumpbase from gcc. (I thought -Wc,thing should do that, but
we don't have it.)
Oh dear, bit of a mess really.
Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
'But that's a lie.' - 'Yes it is. What's your point?'
email@example.com : http://www.cs.bris.ac.uk/~nathan/ : firstname.lastname@example.org