[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-11-07 Thread ppalka at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 Patrick Palka changed: What|Removed |Added Status|ASSIGNED|RESOLVED Target Milestone|---

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-07-07 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #19 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:ad6135e261ced29972e5aa33404e45bcdd99440f commit r13-1561-gad6135e261ced29972e5aa33404e45bcdd99440f Author: Jonathan Wakely Date:

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-02-06 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #18 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:f9e900ce9b17dc7d3a3809d0b0648ebe529a87c5 commit r12-7075-gf9e900ce9b17dc7d3a3809d0b0648ebe529a87c5 Author: Jakub Jelinek Date: S

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-01-19 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #17 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:b834435c8fa4cb9424787fe3044a49fef7992de8 commit r12-6726-gb834435c8fa4cb9424787fe3044a49fef7992de8 Author: Jakub Jelinek Date: W

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-01-14 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #16 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:d686d5d85c23451c03799dc55e456b73065f7333 commit r12-6578-gd686d5d85c23451c03799dc55e456b73065f7333 Author: Jakub Jelinek Date: F

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-01-08 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #15 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:51d464b608b38b9e2007948d10b1e0f1dcec142c commit r12-6382-g51d464b608b38b9e2007948d10b1e0f1dcec142c Author: Jakub Jelinek Date: S

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-01-06 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 Jakub Jelinek changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned a

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-01-05 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #13 from CVS Commits --- The releases/gcc-11 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:226210894e53259940a8e1453125e37c65299ba4 commit r11-9441-g226210894e53259940a8e1453125e37c65299ba4 Author: Jonathan Wake

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-01-05 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #12 from CVS Commits --- The releases/gcc-10 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:0d566335a31722f8044852d9a24f492830ae5789 commit r10-10381-g0d566335a31722f8044852d9a24f492830ae5789 Author: Jonathan Wak

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-01-05 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #11 from Jakub Jelinek --- There are some further questions though. E.g. address_compare has a smart code to assume that static vars will never be adjacent to automatic vars or vice versa (the implementation guarantees that): /* Ass

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-01-05 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #10 from Jakub Jelinek --- So, for #c5, if (&a[1] == &b[0]) instead of if (a+1 == b+0) works right, that is handled by the match.pd (cmp (convert1?@2 addr@0) (convert2? addr@1)) address_compare simplification. And it also works f

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-01-05 Thread ppalka at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #9 from Patrick Palka --- (In reply to Jakub Jelinek from comment #8) > At least when not constant evaluating that, a + 2 can be equal to b + 0 or > can be different, shouldn't we reject at least that? I think so, according to https:

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-01-05 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #8 from Jakub Jelinek --- At least when not constant evaluating that, a + 2 can be equal to b + 0 or can be different, shouldn't we reject at least that? It is true that for automatic variables if at least one of the pointers is into

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2022-01-05 Thread ppalka at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 Patrick Palka changed: What|Removed |Added CC||ppalka at gcc dot gnu.org --- Comment #7

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2021-11-18 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #6 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:ca243ada71656651a8753e88164a1f0f019be1c3 commit r12-5376-gca243ada71656651a8753e88164a1f0f019be1c3 Author: Jonathan Wakely Date:

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2021-11-18 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 --- Comment #5 from Jonathan Wakely --- I think this is another case of the same bug: constexpr bool test() { int a[] = { 1, 2 }; int b[] = { 3, 4 }; if (a+0 == b+0) // OK return false; if (a+1 == b+0) // ERROR retu

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2021-07-27 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 Andrew Pinski changed: What|Removed |Added CC||bobk-off at yandex dot ru --- Comment #4

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2019-03-13 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #3

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2019-03-10 Thread jbassett271 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 Justin Bassett changed: What|Removed |Added CC||jbassett271 at gmail dot com --- Commen

[Bug c++/89074] valid pointer equality constexpr comparison rejected

2019-02-07 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|