This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/70552] __builtin_constant_p fails to reflect the constness of constexpr calls


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70552

--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Yes, thanks for pointing that out.  I think the change is r233671.  I certainly
agree that it's useful to be able to step through constexpr functions in
non-constexpr contexts.  In the test case below, however, the definition of
foo() isn't emitted into the object file so it cannot be stepped into.  The
builtin simply returns the wrong result.  I hope we can make it so that it
returns the useful result I described in comment #0 while still maintaining the
useful debuggability outside of constexpr contexts.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]