This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the EGCS project.
Re: Updating bug reporting request error messages and docs to gcc.gnu.org
On Jul 17, 1999, Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> wrote:
> I am afraid that specifying --best and -9 might confuse some users
> (Which option for which compressor?). Perhaps simply asking for maximum
> compression is sufficient?
Since all listed compressors accept `-9' except `compress', I've
rephrased it like this:
<p>Typically the CPP output (extension <code>.i</code> for C or
<code>.ii</code> for C++) will be large, so please compress the
resulting file with one of the popular compression programs such as
<tt>bzip2</tt>, <tt>gzip</tt>, <tt>zip</tt>, <tt>pkzip</tt> or
<tt>compress</tt> (in decreasing order of preference). Use maximum
compression (<code>-9</code>) if available. Please include the
compressed CPP output in your bug report.
> +<code>.s</code>), you don't usually have to include it in the bug
> "usually don't" instead?
Yup
> +bug report in order to tell who should take care of it. A meaningful
> +subject, indicating the language and platform in which the bug
> +occurred, also helps.
> I stumbled over "in which the bug occurred", but I am not a native speaker
> either. ;-)
A meaningful subject indicating language and platform also helps.
> +<p>If you fail to supply information enough information for a bug
> ^^^^^^^^^^^ ^^^^^^^^^^^
Thanks, installing.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{dcc.unicamp.br,guarana.{org,com}} aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them