This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Mention -freport-bug on GCC wiki
- From: Maxim Ostapenko <m dot ostapenko at partner dot samsung dot com>
- To: gcc at gcc dot gnu dot org
- Cc: Yury Gribov <y dot gribov at samsung dot com>, Slava Garbuzov <v dot garbuzov at samsung dot com>
- Date: Fri, 28 Aug 2015 16:25:38 +0300
- Subject: Mention -freport-bug on GCC wiki
- Authentication-results: sourceware.org; auth=none
Hi, community!
To simplify generating a preprocessed file if ICE is occurred, GCC
(since 5.0 version) introduces a special -freport-bug option. Looking to
GCC bug reporting guide (https://gcc.gnu.org/bugs/#detailed), it may be
useful to mention -freport-bug on this page. Does this make sense? If
so, could someone help me with publishing such information on GCC wiki
page? Here a draft text to be published:
How to generate preprocessed source file if ICE (internal compiler
error) occurred on your code.
To help you generate a preprocessed file from your ICE reprocase, GCC
(since 5.0 version) introduces a special -freport-bug option. You can
add it into your CFLAGS and expect the preprocessed code to be generated:
gcc all-your-options -freport-bug source-file
.....
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
*Preprocessed source stored into /tmp/cclPPsxk.out file, please attach
this to your bugreport*.
The .out file would contain preprocessed code itself, as well as gcc -v
output and full compilation line to reproduce the issue. This
information would help GCC developers to fix the bug faster and would
make their life a bit easier.
-Thanks,
Maxim