-std=gnu++17 triggering debug-mode failures

[Avi Kivity]

I traced the debug mode failures we have (memory leaks on utf8_type's
managed object) to -std=gnu++17. Moving to the commit that switched to
C++17, and forcing C++14 instead, fixes the bug.


It could be the same problem that Raphael discovered, but in another
place. We could verify it by applying the proposed gcc fix and
rebuilding, and retesting.


Any other ideas?

[Duarte Nunes]

We could also try clang, but IIRC, building with clang isn't working at the moment.

--
You received this message because you are subscribed to the Google Groups "ScyllaDB development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-dev...@googlegroups.com.
To post to this group, send email to scylla...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-dev/f483647e-f71b-ad02-e556-870021c2ddf0%40scylladb.com.
For more options, visit https://groups.google.com/d/optout.

[Paweł Dziepak]

This is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82560

Supposedly, fixed in GCC 7.3.

--
You received this message because you are subscribed to the Google Groups "ScyllaDB development" group.

To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-dev+unsubscribe@googlegroups.com.

[Avi Kivity]

Then no problem, I'll verify.

[Avi Kivity]

You were right. Office and remote distcc updated with gcc-7.3.

Fedora users can update with 'dnf --enablerepo updates-testing update gcc'.

Takuya, please prepare a gcc 7.3 package for 3rdparty.

[Takuya ASADA]

2018年2月1日(木) 19:26 Avi Kivity <a...@scylladb.com>:

You were right. Office and remote distcc updated with gcc-7.3.

Fedora users can update with 'dnf --enablerepo updates-testing update gcc'.

Takuya, please prepare a gcc 7.3 package for 3rdparty.

Okay, will update the package.

On 02/01/2018 11:33 AM, Avi Kivity wrote:

Then no problem, I'll verify.

On 02/01/2018 11:31 AM, Paweł Dziepak wrote:

This is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82560

Supposedly, fixed in GCC 7.3.

On 31 January 2018 at 18:43, Avi Kivity <a...@scylladb.com> wrote:

I traced the debug mode failures we have (memory leaks on utf8_type's managed object) to -std=gnu++17. Moving to the commit that switched to C++17, and forcing C++14 instead, fixes the bug.


It could be the same problem that Raphael discovered, but in another place. We could verify it by applying the proposed gcc fix and rebuilding, and retesting.


Any other ideas?

--
You received this message because you are subscribed to the Google Groups "ScyllaDB development" group.

To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-dev...@googlegroups.com.