[Bug c/112556] Null pointer constants with enumeration type are not accepted

2025-04-25 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112556 Jakub Jelinek changed: What|Removed |Added Target Milestone|15.0|15.2 --- Comment #10 from Jakub Jelinek

[Bug c/112556] Null pointer constants with enumeration type are not accepted

2024-11-19 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112556 Sam James changed: What|Removed |Added Status|REOPENED|ASSIGNED

[Bug c/112556] Null pointer constants with enumeration type are not accepted

2024-11-19 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112556 Sam James changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |sjames at gcc dot gnu.org R

[Bug c/112556] Null pointer constants with enumeration type are not accepted

2024-11-18 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112556 --- Comment #8 from Sam James --- Thanks. I'll take a look.

[Bug c/112556] Null pointer constants with enumeration type are not accepted

2024-11-18 Thread jsm28 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112556 --- Comment #7 from Joseph S. Myers --- I don't object to a backport if someone wishes to backport it. (Technically this is a regression between GCC 10 where false in had type int and GCC 11 where it had type _Bool in C2X mode, so resulting in

[Bug c/112556] Null pointer constants with enumeration type are not accepted

2024-11-18 Thread sjames at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112556 --- Comment #6 from Sam James --- This needs backporting to GCC 14 too, no? We have a lot of upstream maintainers using GCC 14 with -std=gnu23 or -std=c23 to reproduce and fix problems. If they can only reproduce "real" C23 problems with unrelea

[Bug c/112556] Null pointer constants with enumeration type are not accepted

2024-11-18 Thread jsm28 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112556 Joseph S. Myers changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---

[Bug c/112556] Null pointer constants with enumeration type are not accepted

2024-11-18 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112556 --- Comment #4 from GCC Commits --- The master branch has been updated by Joseph Myers : https://gcc.gnu.org/g:3d525fce70fa0ffa0b22af6e213643e1ceca5ab5 commit r15-5431-g3d525fce70fa0ffa0b22af6e213643e1ceca5ab5 Author: Joseph Myers Date: Mon

[Bug c/112556] Null pointer constants with enumeration type are not accepted

2024-06-27 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112556 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2024-06-27 Ever confirmed|0

[Bug c/112556] Null pointer constants with enumeration type are not accepted

2023-11-16 Thread joseph at codesourcery dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112556 --- Comment #2 from joseph at codesourcery dot com --- Yes, this is a bug; null_pointer_constant_p gets this right, but convert_for_assignment fails to handle enumerations and booleans as possible null pointer constants. Other contexts such a

[Bug c/112556] Null pointer constants with enumeration type are not accepted

2023-11-15 Thread luigighiron at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112556 --- Comment #1 from Halalaluyafail3 --- This bug also seems to happen with boolean types: void*p=(_Bool)0; Furthermore, this bug only seems to happen when the type of the null pointer constant is an enumeration or boolean type: void*p1=+(_Boo