Targetting p0847 for GCC14 (explicit object parameter)

2023-06-07 Thread waffl3x via Gcc
I would like to boldly suggest implementing P0847 should be targeted at GCC14. In my anecdotal experiences, this feature is very important to people, and very important to myself, I believe it should be a priority. I am not suggesting this without offering to contribute, however because of my inex

Re: On inform diagnostics in plugins, support scripts for gdb and modeling creation of PyObjects for static analysis

2023-06-07 Thread Eric Feng via Gcc
Hi Dave, > If that's the code, does it work if you get rid of the "if (0)" > conditional, or change it to "if (1)"? As written, that guard is > false, so that call to "inform" will never be executed. Woops! Somehow I missed that but yes, it works now. Thanks! > Are you invoking gcc from an ins

Re: Followup on PR/109279: large constants on RISCV

2023-06-07 Thread Jeff Law via Gcc
On 6/1/23 20:38, Vineet Gupta wrote: Hi Jeff, I finally got around to collecting various observations on PR/109279 - more importantly the state of large constants in RV backend, apologies in advance for the long email. It seems the various commits in area have improved the original test

gcc-10-20230607 is now available

2023-06-07 Thread GCC Administrator via Gcc
Snapshot gcc-10-20230607 is now available on https://gcc.gnu.org/pub/gcc/snapshots/10-20230607/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 10 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: An overview of the analyzer support of the operator new

2023-06-07 Thread David Malcolm via Gcc
On Wed, 2023-06-07 at 19:19 +0200, Benjamin Priour wrote: > Hi, > > I've been mapping where the analyzer is lacking support of the > operator new > different variants. > I've written a bunch of test cases already to demonstrate it, you can > find > them below. > They are not yet formatted for a pa

Re: On inform diagnostics in plugins, support scripts for gdb and modeling creation of PyObjects for static analysis

2023-06-07 Thread David Malcolm via Gcc
On Wed, 2023-06-07 at 16:21 -0400, Eric Feng wrote: > Hi everyone, > > I am one of the GSoC participants this year — in particular, I am > working on a static analyzer plugin for CPython extension module > code. > I'm encountering a few challenges and would appreciate any guidance > on > the follo

On inform diagnostics in plugins, support scripts for gdb and modeling creation of PyObjects for static analysis

2023-06-07 Thread Eric Feng via Gcc
Hi everyone, I am one of the GSoC participants this year — in particular, I am working on a static analyzer plugin for CPython extension module code. I'm encountering a few challenges and would appreciate any guidance on the following issues: 1) Issue with "inform" diagnostics in the plugin: I am

Re: When do I need -fnon-call-exceptions?

2023-06-07 Thread Eric Botcazou via Gcc
> On x864 Linux -fasynchronous-unwind-tables is the default. That is > probably sufficient to make your test case work. The testcase g++.dg/torture/except-1.C you recently added to the testsuite does not pass at all if -fnon-call-exceptions is not specified (and does not pass with optimization

Re: When do I need -fnon-call-exceptions?

2023-06-07 Thread Ian Lance Taylor via Gcc
On Wed, Jun 7, 2023 at 10:09 AM Helmut Zeisel via Gcc wrote: > > I wrote some simple program that set a signal handler for SIGFPE, throws a > C++ exception in the signal handler > and catches the exception. > I compiled with and without -fnon-call-exceptions (on x64 Linux). > In both cases, the r

An overview of the analyzer support of the operator new

2023-06-07 Thread Benjamin Priour via Gcc
Hi, I've been mapping where the analyzer is lacking support of the operator new different variants. I've written a bunch of test cases already to demonstrate it, you can find them below. They are not yet formatted for a patch submission, and as some of them may require new warnings, I didn't use d

When do I need -fnon-call-exceptions?

2023-06-07 Thread Helmut Zeisel via Gcc
I wrote some simple program that set a signal handler for SIGFPE, throws a C++ exception in the signal handler and catches the exception. I compiled with and without -fnon-call-exceptions (on x64 Linux). In both cases, the result was the same: the exception was caught and the destructors were cal

About addition of .symtab and .strtab sections in simple-object-elf.c

2023-06-07 Thread Rishi Raj via Gcc
Hi Everyone, I am working on the GSOC project "Bypass Assembler when generating LTO object files." My mentors and I have decided to work on the ELF files first, so I will add .symtab along with the symbol __gnu_lto_slim to the ELF file as a first step. When I was going through the simple-object-elf

[OpenACC] cheking the status of AMD GPU offloading performance

2023-06-07 Thread Chang Liu via Gcc
Hi everyone, I have a general question regarding the GPU offloading support on AMD GPUs using OpenACC or OpenMP. I am doing some tests by compiling the new version of GCC (13 and 14), following the instructions online (https://gcc.gnu.org/wiki/Offloading#How_to_try_offloading_enabled_GCC). I

Re: Passing the complex args in the GPR's

2023-06-07 Thread Michael Matz via Gcc
Hey, On Tue, 6 Jun 2023, Umesh Kalappa via Gcc wrote: > Question is : Why does GCC choose to use GPR's here and have any > reference to support this decision ? You explicitely used -m32 ppc, so https://www.polyomino.org.uk/publications/2011/Power-Arch-32-bit-ABI-supp-1.0-Unified.pdf applies.