Go to file
Joseph Myers 3d525fce70 c: Allow bool and enum null pointer constants [PR112556]
As reported in bug 112556, GCC wrongly rejects conversion of null
pointer constants with bool or enum type to pointers in
convert_for_assignment (assignment, initialization, argument passing,
return).  Fix the code there to allow BOOLEAN_TYPE and ENUMERAL_TYPE;
it already allowed INTEGER_TYPE and BITINT_TYPE.

This bug (together with -std=gnu23 meaning false has type bool rather
than int) has in turn resulted in people thinking they need to fix
code using false as a null pointer constant for C23 compatibility.
While such a usage is certainly questionable, it has nothing to do
with C23 compatibility and the right place for warnings about such
usage is -Wzero-as-null-pointer-constant.  I think it would be
appropriate to extend -Wzero-as-null-pointer-constant to cover
BOOLEAN_TYPE, ENUMERAL_TYPE and BITINT_TYPE (in all the various
contexts in which that option generates warnings), though this patch
doesn't do anything about that option.

Bootstrapped with no regressions for x86-64-pc-linux-gnu.

	PR c/112556

gcc/c/
	* c-typeck.cc (convert_for_assignment): Allow conversion of
	ENUMERAL_TYPE and BOOLEAN_TYPE null pointer constants to pointers.

gcc/testsuite/
	* gcc.dg/c11-null-pointer-constant-1.c,
	gcc.dg/c23-null-pointer-constant-1.c: New tests.
2024-11-18 22:26:21 +00:00
.forgejo
.github
c++tools
config
contrib libdiagnostics: add a "sarif-replay" command-line tool [PR96032] 2024-11-18 17:08:37 -05:00
fixincludes
gcc c: Allow bool and enum null pointer constants [PR112556] 2024-11-18 22:26:21 +00:00
gnattools
gotools
include
INSTALL
libada
libatomic testsuite: move dg-test cleanup code from gcc-dg.exp to its own file 2024-11-18 16:49:04 -05:00
libbacktrace
libcc1
libcody
libcpp libcpp: add .c++-header-unit target 2024-11-18 09:18:17 +01:00
libdecnumber
libffi
libgcc Fix more c23 bool fallout 2024-11-18 10:11:01 -07:00
libgfortran
libgm2
libgo
libgomp testsuite: move dg-test cleanup code from gcc-dg.exp to its own file 2024-11-18 16:49:04 -05:00
libgrust
libiberty Daily bump. 2024-11-17 00:21:19 +00:00
libitm testsuite: move dg-test cleanup code from gcc-dg.exp to its own file 2024-11-18 16:49:04 -05:00
libobjc
libphobos testsuite: move dg-test cleanup code from gcc-dg.exp to its own file 2024-11-18 16:49:04 -05:00
libquadmath
libsanitizer
libssp
libstdc++-v3 testsuite: move dg-test cleanup code from gcc-dg.exp to its own file 2024-11-18 16:49:04 -05:00
libvtv testsuite: move dg-test cleanup code from gcc-dg.exp to its own file 2024-11-18 16:49:04 -05:00
lto-plugin
maintainer-scripts
zlib
.b4-config
.dir-locals.el
.gitattributes
.gitignore
ABOUT-NLS
ar-lib
ChangeLog
ChangeLog.jit
ChangeLog.tree-ssa
compile
config-ml.in
config.guess
config.rpath
config.sub
configure Add libdiagnostics (v4) 2024-11-18 17:08:36 -05:00
configure.ac Add libdiagnostics (v4) 2024-11-18 17:08:36 -05:00
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.RUNTIME
depcomp
install-sh
libtool-ldflags
libtool.m4
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
missing
mkdep
mkinstalldirs
move-if-change
multilib.am
README
SECURITY.txt
symlink-tree
test-driver
ylwrap

This directory contains the GNU Compiler Collection (GCC).

The GNU Compiler Collection is free software.  See the files whose
names start with COPYING for copying permission.  The manuals, and
some of the runtime libraries, are under different terms; see the
individual source files for details.

The directory INSTALL contains copies of the installation information
as HTML and plain text.  The source of this information is
gcc/doc/install.texi.  The installation information includes details
of what is included in the GCC sources and what files GCC installs.

See the file gcc/doc/gcc.texi (together with other files that it
includes) for usage and porting information.  An online readable
version of the manual is in the files gcc/doc/gcc.info*.

See http://gcc.gnu.org/bugs/ for how to report bugs usefully.

Copyright years on GCC source files may be listed using range
notation, e.g., 1987-2012, indicating that every year in the range,
inclusive, is a copyrightable year that could otherwise be listed
individually.