[Bug driver/64690] New: -freport-bug issue with comments

["jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64690

            Bug ID: 64690
           Summary: -freport-bug issue with comments
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jakub at gcc dot gnu.org
                CC: chefmax at gcc dot gnu.org

As -freport-bug dumps also the error output into the file as /* ... */
comment, there is a problem if that text includes /* or */ character sequences.
E.g. take PR64688 testcase, add /* */  before last line, so it reads:
/* */ void performance_testtest_method() { test_fill<K<int>, Q<unsigned,
int>>(0); }

./xg++ -B ./ -S -O3 -march=westmere pr64688.C -std=c++11 -freport-bug
gives err file that contains
/* ...
 /* */ void performance_testtest_method() { test_fill<K<int>, Q<unsigned,
int>>(0); }
...
*/

Perhaps /* and */ in the output should be replaced by something that won't be
parsed as comment beginning or end, like //^H* and **^H/ ? ^H meaning literal
backspace (\x08) char, so that at least when you cat it to terminal you won't
notice the difference.