This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Ping Re: Move flag_stack_check and flag_compare_debug to?gcc_options structure


On Dec  1, 2010, Arnaud Charlet <charlet@adacore.com> wrote:

>> > Any idea on how to get rid of it?
>> 
>> I presume we would need a compilation mode that doesn't write the ALI file but
>> does everything else as usual.  Or do we already have such a thing?

> I don't think we have that. Any hope in modifying the driver that uses
> -fcompare-debug to ignore these files?

The concern IIRC is that we would overwrite the .ali files generated by
the non-debug compilation.  If compare succeeds, this shouldn't be much
of a problem, but if it fails, the file might be different, and it might
then affect other compilations.

I support the idea of adding another command-line flag that disables
writing of .ali files, and have it passed to gnat during the second
-fcompare-debug compilation (-fcompare-debug-second).

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist      Red Hat Brazil Compiler Engineer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]