[Bug driver/31350] gcc -v --help puts some output on std. out, and some on std. error.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31350 Andrew Pinski changed: What|Removed |Added CC||josh at joshtriplett dot org --- Comment #7 from Andrew Pinski --- *** Bug 93284 has been marked as a duplicate of this bug. ***
[Bug driver/31350] gcc -v --help puts some output on std. out, and some on std. error.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31350 --- Comment #6 from Manuel López-Ibáñez --- This is exactly the same case as: $ gcc --help --invalid 1> /dev/null gcc: error: unrecognized command line option ‘--invalid’ One should not expect the error output to go to stdout just because --help was provided.
[Bug driver/31350] gcc -v --help puts some output on std. out, and some on std. error.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31350 Manuel López-Ibáñez changed: What|Removed |Added Status|NEW |RESOLVED CC||manu at gcc dot gnu.org Resolution|--- |INVALID --- Comment #5 from Manuel López-Ibáñez --- (In reply to Andrew Pinski from comment #1) > Some of this is not a GCC bug but a binutils one I think or maybe not a bug > at all. At least all the GNU tools should follow the GNU Coding Guidelines: https://www.gnu.org/prep/standards/html_node/_002d_002dhelp.html#g_t_002d_002dhelp Thus, the correct behavior is to use stdout for --help. However, the output of "-v" is not "verbose help". You get the same output independently of --help. It is simply verbose diagnostics about what GCC is doing and they should go to stderr. Thus, this is not a bug. If you find something in the output of --help= or --version that is printed to stderr, please re-open.
[Bug driver/31350] gcc -v --help puts some output on std. out, and some on std. error.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31350 Eric Gallager changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed||2017-10-05 Ever confirmed|0 |1 --- Comment #4 from Eric Gallager --- (In reply to Ladislas de Toldi from comment #3) > I confirm this is also the case for avr-gcc > > This is what I get to stderr: > > --- > > Using built-in specs. > Reading specs from > /usr/local/Cellar/avr-gcc/7.2.0/lib/gcc/avr/7.2.0/device-specs/specs-avr2 > COLLECT_GCC=avr-gcc > COLLECT_LTO_WRAPPER=/usr/local/Cellar/avr-gcc/7.2.0/libexec/gcc/avr/7.2.0/ > lto-wrapper > Target: avr > Configured with: ../configure --target=avr > --prefix=/usr/local/Cellar/avr-gcc/7.2.0 --enable-languages=c,c++ > --with-ld=/usr/local/opt/avr-binutils/bin/avr-ld > --with-as=/usr/local/opt/avr-binutils/bin/avr-as --disable-nls > --disable-libssp --disable-shared --disable-threads --disable-libgomp > --with-dwarf2 > Thread model: single > gcc version 7.2.0 (GCC) OK, changing status to NEW. This isn't necessarily confirmation that this is a bug with gcc, just that it happens.
[Bug driver/31350] gcc -v --help puts some output on std. out, and some on std. error.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31350 Ladislas de Toldi changed: What|Removed |Added CC||ladislas at leka dot io --- Comment #3 from Ladislas de Toldi --- I confirm this is also the case for avr-gcc This is what I get to stderr: --- Using built-in specs. Reading specs from /usr/local/Cellar/avr-gcc/7.2.0/lib/gcc/avr/7.2.0/device-specs/specs-avr2 COLLECT_GCC=avr-gcc COLLECT_LTO_WRAPPER=/usr/local/Cellar/avr-gcc/7.2.0/libexec/gcc/avr/7.2.0/lto-wrapper Target: avr Configured with: ../configure --target=avr --prefix=/usr/local/Cellar/avr-gcc/7.2.0 --enable-languages=c,c++ --with-ld=/usr/local/opt/avr-binutils/bin/avr-ld --with-as=/usr/local/opt/avr-binutils/bin/avr-as --disable-nls --disable-libssp --disable-shared --disable-threads --disable-libgomp --with-dwarf2 Thread model: single gcc version 7.2.0 (GCC)
[Bug driver/31350] gcc -v --help puts some output on std. out, and some on std. error.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31350 Eric Gallager changed: What|Removed |Added Target|i686-pc-linux-gnu | CC||egallager at gcc dot gnu.org Host|i686-pc-linux-gnu | Build|i686-pc-linux-gnu | --- Comment #2 from Eric Gallager --- (In reply to Andrew Pinski from comment #1) > Some of this is not a GCC bug but a binutils one I think or maybe not a bug > at all. Or a cctools bug or a bug for wherever you get your assembler from. For me the stuff that goes to stderr is: Using built-in specs. COLLECT_GCC=/usr/local/bin/gcc COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/i386-apple-darwin9.8.0/8.0.0/lto-wrapper Target: i386-apple-darwin9.8.0 Configured with: ../configure --disable-werror --disable-werror-always --enable-languages=c,c++,lto,objc,obj-c++ --enable-stage1-checking=release,rtl -C --with-system-libunwind --enable-secureplt --enable-frame-pointer --enable-debug --with-isl --disable-host-shared --enable-maintainer-mode --disable-default-pie --with-ld64 --without-pic --enable-target-optspace --enable-libstdcxx-debug CC=/usr/local/bin/gcc CXX=/usr/local/bin/g++ AUTOCONF=/usr/local/bin/autoconf AUTOHEADER=/usr/local/bin/autoheader AUTORECONF=/usr/local/bin/autoreconf AUTOM4TE=/usr/local/bin/autom4te AUTOSCAN=/usr/local/bin/autoscan AUTOUPDATE=/usr/local/bin/autoupdate IFNAMES=/usr/local/bin/ifnames Thread model: posix gcc version 8.0.0 20170905 (experimental) (GCC) COLLECT_GCC_OPTIONS='-v' '--help' '-mmacosx-version-min=10.5.8' '-asm_macosx_version_min=10.5' '-mtune=core2' /usr/local/libexec/gcc/i386-apple-darwin9.8.0/8.0.0/cc1 -quiet -v -D__DYNAMIC__ help-dummy -fPIC -quiet -dumpbase help-dummy -mmacosx-version-min=10.5.8 -mtune=core2 -auxbase help-dummy -version --help -o /var/tmp//cczaoGRD.s GNU C11 (GCC) version 8.0.0 20170905 (experimental) (i386-apple-darwin9.8.0) compiled by GNU C version 8.0.0 20170905 (experimental), GMP version 6.1.0, MPFR version 3.1.4, MPC version 1.0.3, isl version isl-0.16.1-GMP GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 COLLECT_GCC_OPTIONS='-v' '--help' '-mmacosx-version-min=10.5.8' '-mtune=core2' as -arch i386 -v -force_cpusubtype_ALL --help -o /var/tmp//ccltZ0N3.o /var/tmp//cczaoGRD.s Apple Inc version cctools-698.1~1, GNU assembler version 1.38 FATAL:/usr/bin/../libexec/gcc/darwin/i386/as: I don't understand '-' flag!
