Hi! The -freport-bug changes added an undesirable empty line at the end of gcc -v . That extra line is desirable just in the -freport-bug dumps, so moved there.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2015-01-23 Jakub Jelinek <ja...@redhat.com> PR driver/64737 * gcc.c (print_configuration): Don't print a blank line at the end here... (run_attempt): ... but here unstead. --- gcc/gcc.c.jj 2015-01-23 09:50:16.000000000 +0100 +++ gcc/gcc.c 2015-01-23 11:28:24.311695091 +0100 @@ -6331,10 +6331,10 @@ print_configuration (FILE *file) if (! strncmp (version_string, compiler_version, n) && compiler_version[n] == 0) - fnotice (file, "gcc version %s %s\n\n", version_string, + fnotice (file, "gcc version %s %s\n", version_string, pkgversion_string); else - fnotice (file, "gcc driver version %s %sexecuting gcc version %s\n\n", + fnotice (file, "gcc driver version %s %sexecuting gcc version %s\n", version_string, pkgversion_string, compiler_version); } @@ -6438,6 +6438,7 @@ run_attempt (const char **new_argv, cons { FILE *file_out = fopen (err_temp, "a"); print_configuration (file_out); + fputs ("\n", file_out); fclose (file_out); } Jakub