https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68281
Josh Stone changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68281
--- Comment #4 from Jonathan Wakely ---
See C++14 8.5 [dcl.init] p12:
If an indeterminate value is produced by an evaluation, the behavior is
undefined except in the following cases:
[... various cases involving unsigned char ...]
so you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68281
--- Comment #3 from Jonathan Wakely ---
(In reply to Josh Stone from comment #2)
> This may also be significant:
>
> bool
> base_query::get_number_param(literal_map_t const & params,
>interned_string k, long & v)
> {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68281
--- Comment #2 from Josh Stone ---
This may also be significant:
bool
base_query::get_number_param(literal_map_t const & params,
interned_string k, long & v)
{
int64_t value;
bool present = derived_probe_builder:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68281
--- Comment #1 from Josh Stone ---
I suspect this may actually be acceptable, NOTABUG, because I can't think of
any uninitialized data that would make the effective behavior different than if
it had been checked in the proper order. Both conditi
