> Which revision of gcc is this? Using built-in specs. COLLECT_GCC=/opt/gcc-10.0-20191208/bin/gcc-10.0-20191208 COLLECT_LTO_WRAPPER=/opt/gcc-10.0-20191208/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc-10-20191208/configure --prefix=/usr/local --sysconfdir=/etc --localstatedir=/var --libexecdir='/usr/local/lib' --enable-version-specific-runtime-libs --disable-rpath --with-system-zlib --enable-gnu-unique-object --enable-languages=c,c++,objc,obj-c++,fortran,lto --enable-plugin --enable-initfini-array --enable-gnu-indirect-function --program-suffix=-10.0-20191208 Thread model: posix Supported LTO compression algorithms: zlib gcc version 10.0.0 20191208 (experimental) (GCC)
> Which terminal are you using, and what version? libvte 2.90. Also tested on MATE Terminal 1.16.3 and Terminator 1.90, showing garbled outputs on warning lines and beeps. Tested on xfce4-terminal 0.8.3, it produces no beep but garbled outputs; however I think this is due to broken terminal bell support of xfce4-terminal in my system. 2019-12-15 23:09 GMT+08:00, David Malcolm <dmalc...@redhat.com>: > On Sun, 2019-12-15 at 19:38 +0800, 王昊然 wrote: >> This patch has made my terminal beeps on every warning message, which >> is so noisy. > > Sorry about this. > >> May be this feature should be disabled by default, unless enabled by >> configure time option, runtime option or runtime environment >> variables. > > Which revision of gcc is this? > > Which terminal are you using, and what version? > > > Thanks > David > >
