Re: Using __gnu_lto_slim to detect -fno-fat-lto-objects

On 2/22/23 09:28, Florian Weimer via Gcc wrote: > * Richard Biener: > >> On Wed, Feb 22, 2023 at 9:19 AM Florian Weimer via Gcc >> wrote: >>> >>> Can we use the COMMON symbol __gnu_lto_slim to detect >>> -fno-fat-lto-objects on contemporary GNU/Linux (with the LTO linker >>> plugin)? >> >> Yes.

RISC-V V C Intrinsic API v1.0 release meeting reminder (February 23rd, 2022)

Hi all, A reminder that the next open meeting to discuss on the RISC-V V C Intrinsic API v1.0 is going to be held later on 2022/02/23 6AM (GMT -7) / 11PM (GMT +8). The agenda can be found in the second page of the meeting slides (link

Willing to contribute to the project Idea "Fortran – DO CONCURRENT"

Hi, My name is Satyanarayana Varma. I am willing to contribute to the project idea "Fortran – DO CONCURRENT". Please suggest some resources to me so that I can learn your technologies. Could you please assign me some good first issues for the starting. Thank you, Regards. Satyanarayana Datla

Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on

On Wed, 22 Feb 2023 14:03:36 + Jonathan Wakely via Gcc wrote: > I think GCC trunk won't even build on M2, you need Iain Sandoe's > out-of-tree patches. https://gitlab.cobolworx.com/COBOLworx/gcc-cobol/-/jobs/2822 We've been building on aarch64 based on GCC trunk since December. --jkl

Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on

On Thu, 23 Feb 2023 at 15:57, James K. Lowden wrote: > > On Wed, 22 Feb 2023 14:03:36 + > Jonathan Wakely via Gcc wrote: > > > I think GCC trunk won't even build on M2, you need Iain Sandoe's > > out-of-tree patches. > > https://gitlab.cobolworx.com/COBOLworx/gcc-cobol/-/jobs/2822 > > We've be

GCC has been accepted as a GSoC mentoring org

Hello, I'm happy to announce that GCC has been accepted as a mentoring organization in Google Summer of Code 2023! The program is now in a phase that is called "Potential GSoC contributors discuss application ideas with mentoring organizations" and so let's do just that. Contributors will

Re: Missed warning (-Wuse-after-free)

Hi Martin, On 2/17/23 14:48, Martin Uecker wrote: This new wording doesn't even allow one to use memcmp(3); just reading the pointer value, however you do it, is UB. memcmp would not use the pointer value but work on the representation bytes and is still allowed. Hmm, interesting. It's rath

Re: Missed warning (-Wuse-after-free)

Am Donnerstag, dem 23.02.2023 um 20:23 +0100 schrieb Alex Colomar: > Hi Martin, > > On 2/17/23 14:48, Martin Uecker wrote: > > > This new wording doesn't even allow one to use memcmp(3); > > > just reading the pointer value, however you do it, is UB. > > > > memcmp would not use the pointer value

gcc-10-20230223 is now available

Snapshot gcc-10-20230223 is now available on https://gcc.gnu.org/pub/gcc/snapshots/10-20230223/ 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: Missed warning (-Wuse-after-free)

Hi Martin, On 2/23/23 20:57, Martin Uecker wrote: Am Donnerstag, dem 23.02.2023 um 20:23 +0100 schrieb Alex Colomar: Hi Martin, On 2/17/23 14:48, Martin Uecker wrote: This new wording doesn't even allow one to use memcmp(3); just reading the pointer value, however you do it, is UB. memcmp w

Re: Missed warning (-Wuse-after-free)

On Fri, Feb 24, 2023 at 01:02:54AM +0100, Alex Colomar wrote: > Hi Martin, > > On 2/23/23 20:57, Martin Uecker wrote: > > Am Donnerstag, dem 23.02.2023 um 20:23 +0100 schrieb Alex Colomar: > > > Hi Martin, > > > > > > On 2/17/23 14:48, Martin Uecker wrote: > > > > > This new wording doesn't even

Re: Missed warning (-Wuse-after-free)

Hi Serge, Martin, On 2/24/23 02:21, Serge E. Hallyn wrote: Does all this imply that the following is well defined behavior (and shall print what one would expect)? free(p); (void) &p; // take the address // or maybe we should (void) memcmp(&p, &p, sizeof(p)); ? printf("%p\n", p);

Re: Missed warning (-Wuse-after-free)

If I may add my thoughts here, On Thursday, February 23rd, 2023 at 20:42, Alex Colomar wrote: > I'll try to show why this feels weird to me (even in C89): > > > alx@dell7760:~/tmp$ cat pointers.c > #include > > #include > > > > int > main(void) > { > char *p, *q; > > p = malloc(42); > if (p == N