This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Bug reduction instructions, draft 2
- From: Wolfgang Bangerth <bangerth at ticam dot utexas dot edu>
- To: tm_gccmail at mail dot kloo dot net
- Cc: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, <gcc-patches at gcc dot gnu dot org>, Janis Johnson <janis187 at us dot ibm dot com>
- Date: Tue, 14 Jan 2003 14:07:09 -0600 (CST)
- Subject: Re: Bug reduction instructions, draft 2
On Tue, 14 Jan 2003 tm_gccmail@mail.kloo.net wrote:
> [...]
Thanks for your suggestions. Janis also has had a lot of changes, which
I'll use for a next draft.
> > +<h2>Brute force approach</h2>
>
> This whole "Brute force approach" section should be completely rewritten.
> It is excessively wordy. You should merely describe it as an iterative
> process of removing various pieces of code and retesting to verify the
> original behavior is replicated.
I think that we should explain _why_ some steps should be done. The
document is not for people who frequently do this anyway, they know all
this. The intention was to have something that a bug reporter wants to
read if he wants to help more with his report.
> If you use "gcc -E -P" there will be no preprocessor directives
> in the generated uotput file.
True, but our bug reporting instructions say that people should generate
preprocessed output with -save-temps, so I did not want to deviate from
this path.
Thanks
Wolfgang
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ticam.utexas.edu
www: http://www.ticam.utexas.edu/~bangerth/