[Bug libstdc++/103162] overconstrained std::pmr::memory_resource allocate/deallocate methods

2021-11-10 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103162 --- Comment #13 from Florin Iucha --- (In reply to Jonathan Wakely from comment #11) > I'm going to get the standard clarified instead (and then cppreference will > probably follow suit). That will be great!

[Bug libstdc++/103162] overconstrained std::pmr::memory_resource allocate/deallocate methods

2021-11-10 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103162 --- Comment #12 from Florin Iucha --- (In reply to Jonathan Wakely from comment #9) > (In reply to Florin Iucha from comment #2) > > It indicates that it reports errors via exceptions. > > Yes, but that doesn't mean 0 is a valid return value. T

[Bug libstdc++/103162] overconstrained std::pmr::memory_resource allocate/deallocate methods

2021-11-10 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103162 --- Comment #10 from Florin Iucha --- (In reply to Jonathan Wakely from comment #8) > > There are uses for the memory_resources pattern, outside of its current > > application in the standard library - for example allocating ranges in a > > file

[Bug libstdc++/103162] overconstrained std::pmr::memory_resource allocate/deallocate methods

2021-11-10 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103162 --- Comment #7 from Florin Iucha --- That is most unfortunate because it will force us to duplicate the library used for resource management. Not only that, but if I were to implement the pmr::memory_resource interface in terms of the other libr

[Bug libstdc++/103162] overconstrained std::pmr::memory_resource allocate/deallocate methods

2021-11-09 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103162 Florin Iucha changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/103162] New: overconstrained std::pmr::memory_resource allocate/deallocate methods

2021-11-09 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103162 Bug ID: 103162 Summary: overconstrained std::pmr::memory_resource allocate/deallocate methods Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/102077] null-pointer dereference in std::thread::detach()

2021-08-26 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102077 Florin Iucha changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[Bug libstdc++/102077] New: null-pointer dereference in std::thread::detach()

2021-08-26 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102077 Bug ID: 102077 Summary: null-pointer dereference in std::thread::detach() Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Compone

[Bug sanitizer/100439] stack overflow running ubsan

2021-07-06 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100439 --- Comment #14 from Florin Iucha --- Bisecting the configure flags, I think I narrowed it down to: it fails when "--enable-gnu-indirect-function" is present.

[Bug sanitizer/100439] stack overflow running ubsan

2021-07-06 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100439 --- Comment #13 from Florin Iucha --- With GCC 11-20210703 snapshot I can reproduce the observation on Ubuntu 20.04 but can not reproduce the observation on Debian testing.

[Bug sanitizer/100439] stack overflow running ubsan

2021-07-02 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100439 --- Comment #12 from Florin Iucha --- Actually, it gets even better - no clang needed. Just build GCC 11-20210626 Snapshot and build the example using the Google test recipe: # # Makefile # ALL: bin/test_hello .PHONY: clean CXX=/opt/gcc11-for

[Bug sanitizer/100439] stack overflow running ubsan

2021-07-02 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100439 --- Comment #11 from Florin Iucha --- Updated Makefile for clang12: #--- ALL: bin/test_hello .PHONY: clean CXX=/opt/clang12-for-tng/bin/clang++ CXXFLAGS=-m64 -g -std=c++20 --gcc-toolchain=/opt/gcc11-for-tng -fsanitize=un

[Bug sanitizer/100439] stack overflow running ubsan

2021-07-02 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100439 --- Comment #10 from Florin Iucha --- I am able to reproduce something similar by building GCC11 from snapshot 11-20210626 (96358cbbe6e6447519a155301b6acb1624c0) and then using Clang12 (12.0.1-rc4) ubsan: #234 0x7f9769d39670 in __cxxabi

[Bug sanitizer/100439] stack overflow running ubsan

2021-05-14 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100439 --- Comment #9 from Florin Iucha --- I was not able to reproduce the observation using the native compiler and system glibc.

[Bug sanitizer/100439] stack overflow running ubsan

2021-05-13 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100439 --- Comment #7 from Florin Iucha --- Created attachment 50809 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50809&action=edit crosstool-ng configuration file

[Bug sanitizer/100439] stack overflow running ubsan

2021-05-13 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100439 --- Comment #6 from Florin Iucha --- With the test file above, and this Makefile: --8< --8< --8< --8< --8< --8< --8< --8< --8< --8< --8< --8< ALL: bin/test_hello .PHONY: clean CXX=/opt/tng-gcc11-glibc-linux5.4/bin/x86_64-tng-linux-gnu-g++

[Bug sanitizer/100439] stack overflow running ubsan

2021-05-13 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100439 --- Comment #5 from Florin Iucha --- It is a "CMake object library" - not a static library. I will prepare a more self-contained test case shortly.

[Bug sanitizer/100439] stack overflow running ubsan

2021-05-06 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100439 --- Comment #3 from Florin Iucha --- Tried it with current HEAD of https://github.com/google/googletest (f5e592d8ee5ffb1d9af5be7f715ce3576b8bf9c4), with the cmake patched to add "-fsanitize=undefined -fno-omit-frame-pointer -std=c++2a" and the b

[Bug sanitizer/100439] stack overflow running ubsan

2021-05-06 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100439 --- Comment #2 from Florin Iucha --- This is for regular x86-64; we're using a cross-compiler sysroot to avoid dependency on system libraries and be able to run the binary on different Linux distributions. I can't reproduce the problem on a "he

[Bug sanitizer/100439] New: stack overflow running ubsan

2021-05-05 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100439 Bug ID: 100439 Summary: stack overflow running ubsan Product: gcc Version: 11.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer

[Bug c++/97899] [11 Regression] internal compiler error: in split_nonconstant_init_1, at cp/typeck2.c:626

2020-11-18 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97899 --- Comment #7 from Florin Iucha --- Cool, thank you!

[Bug c++/97899] [11 Regression] internal compiler error: in split_nonconstant_init_1, at cp/typeck2.c:626

2020-11-18 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97899 --- Comment #5 from Florin Iucha --- Curious, were you able to reduce it further, or just bisected it?

[Bug c++/97899] [11 Regression] internal compiler error: in split_nonconstant_init_1, at cp/typeck2.c:626

2020-11-18 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97899 --- Comment #3 from Florin Iucha --- gcc version 11.0.0 20201108 (previous snapshot) is compiling fine.

[Bug c++/97899] internal compiler error: in split_nonconstant_init_1, at cp/typeck2.c:626

2020-11-18 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97899 --- Comment #1 from Florin Iucha --- Created attachment 49590 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49590&action=edit pre-processed source file

[Bug c++/97899] New: internal compiler error: in split_nonconstant_init_1, at cp/typeck2.c:626

2020-11-18 Thread florin.iucha at amd dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97899 Bug ID: 97899 Summary: internal compiler error: in split_nonconstant_init_1, at cp/typeck2.c:626 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal