Re: bug in gcc/cp/coroutines.cc line 4688

2025-01-18 Thread Lee Brown via Gcc
In my view  it is a bug.  It gives an error that it can't find std::throw,  but that is gcc's problem,  not the problem according to the standard.  According to the standard, the problem is that ::operator new(size_t, nothrow_t)  has not been declared.   In fact,  the relevant paragraph of the sta

Re: bug in gcc/cp/coroutines.cc line 4688

2025-01-18 Thread Lee Brown via Gcc
Just to be clear,   the appended 17 lines of very simple code breaks gcc on every platform where header does not have in its include hierarchywhich I assume to be every platform. 1) place code below in main.cpp 2) g++ -std=c++20 main.cpp and you get main.cxx: In function 'my_co do_co()':

Re: bug in gcc/cp/coroutines.cc line 4688

2025-01-18 Thread Andrew Pinski via Gcc
On Sat, Jan 18, 2025 at 2:12 PM Lee Brown via Gcc wrote: > > Just to be clear, the appended 17 lines of very simple code breaks gcc > on every platform where header does not have in its > include hierarchywhich I assume to be every platform. See the discussion in the bug report: https://g

Re: Question about optimizing dynamic_cast call in C++ at GIMPLE Level

2025-01-18 Thread Hanke Zhang via Gcc
Hi Florian, Thank you very much for your reply. This is not related to ELF. What I am trying to do is simply obtain the 'Derived' type node from the parameter that is retrieved via the '__dynamic_cast' call. I believe this should be a relatively simple coding problem. However, I am not very fami

gcc-14-20250118 is now available

2025-01-18 Thread GCC Administrator via Gcc
Snapshot gcc-14-20250118 is now available on https://gcc.gnu.org/pub/gcc/snapshots/14-20250118/ and on various mirrors, see https://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 14 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Question about optimizing dynamic_cast call in C++ at GIMPLE Level

2025-01-18 Thread Hanke Zhang via Gcc
Hi, I have recently been delving into optimizing dynamic_cast calls in C++ within the context of GIMPLE code. In particular, for scenarios involving single inheritance, I'm aiming to convert the following code: _1 = __dynamic_cast (obj_1(D), &_ZTI7Base, &_ZTI10Derived, 0); if (_1!= 0B) into a mo

Re: Question about optimizing dynamic_cast call in C++ at GIMPLE Level

2025-01-18 Thread Florian Weimer via Gcc
* Hanke Zhang via Gcc: > I have recently been delving into optimizing dynamic_cast calls in C++ > within the context of GIMPLE code. In particular, for scenarios > involving single inheritance, I'm aiming to convert the following > code: > > _1 = __dynamic_cast (obj_1(D), &_ZTI7Base, &_ZTI10Derive

[SPARC] Fix PR target/118512

2025-01-18 Thread Eric Botcazou via Gcc
This is a regression present on the mainline only, but the underlying issue has been latent for years: the compiler and the assembler disagree on the support of the VIS 3B SIMD ISA, the former bundling it with VIS 3 but not the latter. IMO the documentation is not very clear, so this patch just