Date: Mon, 23 Mar 2020 18:34:40 +0000 From: bugzilla-noreply@freebsd.org To: standards@FreeBSD.org Subject: [Bug 245006] toolchain: clang issues bogus "warning: multi-line // comment [-Wcomment]" Message-ID: <bug-245006-99-29V51DrrHX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-245006-99@https.bugs.freebsd.org/bugzilla/> References: <bug-245006-99@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D245006 Dimitry Andric <dim@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dim@FreeBSD.org Status|New |Open --- Comment #3 from Dimitry Andric <dim@FreeBSD.org> --- Apparently gcc thinks the same, you just have to add -Wcomment: $ gcc -v Using built-in specs. COLLECT_GCC=3Dgcc COLLECT_LTO_WRAPPER=3D/usr/local/libexec/gcc9/gcc/x86_64-portbld-freebsd13.= 0/9.2.0/lto-wrapper Target: x86_64-portbld-freebsd13.0 Configured with: /wrkdirs/share/dim/ports/lang/gcc9/work/gcc-9.2.0/configure --enable-multilib --enable-plugin --disable-bootstrap --disable-nls --enable-gnu-indirect-function --libdir=3D/usr/local/lib/gcc9 --libexecdir=3D/usr/local/libexec/gcc9 --program-suffix=3D9 --with-as=3D/usr/local/bin/as --with-gmp=3D/usr/local --with-gxx-include-dir=3D/usr/local/lib/gcc9/include/c++/ --with-ld=3D/usr/local/bin/ld --with-pkgversion=3D'FreeBSD Ports Collection' --with-system-zlib --with-isl=3D/usr/local --enable-languages=3Dc,c++,objc,= fortran --prefix=3D/usr/local --localstatedir=3D/var --mandir=3D/usr/local/man --infodir=3D/usr/local/share/info/gcc9 --build=3Dx86_64-portbld-freebsd13.0 Thread model: posix gcc version 9.2.0 (FreeBSD Ports Collection) $ gcc -Wcomment -c multiline.c multiline.c:1:1: warning: multi-line comment [-Wcomment] 1 | // \ | ^ And similar for gcc 4.8, 7.5 and 8.3. I am unsure about the interpretation of the various standards though, as th= ey do not say much, if anything, about warnings. The construct is completely legal, so it causes no errors unless you insist on making all warnings erro= rs. Maybe you can report this upstream with gcc and clang, to see what their opinion is? I am hesitant to make changes to our versions unless there is a pressing need to do so. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-245006-99-29V51DrrHX>