Compiler options as string?

[Tobias Burnus]

  Joseph S. Myers wrote:
>> The bare strings are only available in toplev.c: toplev_main directly gets
> They are only available in gcc.c.  If you want what the user used then you
> need to get it from gcc.c; if you want canonical forms after specs
> processing, removal of overridden options etc. then use the canonical
> forms of the decoded options to produce such a string as you wish

I decided that the latter produces good output. Joseph, do you think 
that following patch basically OK? I export the decoded arguments via 
toplev.{c,o} - or should this be handled differently?

Tobias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: options.diff
Type: text/x-patch
Size: 5617 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20100928/cc42967b/attachment.bin>