gcc-10-20220114 is now available

2022-01-14 Thread GCC Administrator via Gcc
Snapshot gcc-10-20220114 is now available on https://gcc.gnu.org/pub/gcc/snapshots/10-20220114/ 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: reordering of trapping operations and volatile

2022-01-14 Thread Jonathan Wakely via Gcc
On Fri, 14 Jan 2022, 14:17 Michael Matz via Gcc, wrote: > Hello, > > On Thu, 13 Jan 2022, Martin Uecker wrote: > > > > > > Handling all volatile accesses in the very same way would be > > > > > possible but quite some work I don't see much value in. > > > > > > > > I see some value. > > > > > >

Re: GSoC: Working on the static analyzer

2022-01-14 Thread Mir Immad via Gcc
HI David, I've been tinkering with the static analyzer for the last few days. I find the project of adding SARIF output to the analyzer intresting. I'm writing this to let you know that I'm trying to learn the codebase. Thank you. On Tue, Jan 11, 2022, 7:09 PM David Malcolm wrote: > On Tue, 2022

Re: git hooks: too strict check

2022-01-14 Thread Eric Gallager via Gcc
On Fri, Jan 14, 2022 at 11:14 AM Michael Matz via Gcc wrote: > > Hello, > > On Fri, 14 Jan 2022, Martin Liška wrote: > > > Hello. > > > > I'm working on a testsuite clean-up where some of the files are wrongly > > named. > > More precisely, so files have .cc extension and should use .C. However

Re: git hooks: too strict check

2022-01-14 Thread Michael Matz via Gcc
Hello, On Fri, 14 Jan 2022, Martin Liška wrote: > Hello. > > I'm working on a testsuite clean-up where some of the files are wrongly named. > More precisely, so files have .cc extension and should use .C. However there's > existing C test-case and it leads to: > > marxin@marxinbox:~/Programming

Re: reordering of trapping operations and volatile

2022-01-14 Thread Martin Uecker via Gcc
Am Freitag, den 14.01.2022, 14:15 + schrieb Michael Matz: > Hello, > > On Thu, 13 Jan 2022, Martin Uecker wrote: ... > > > I think to define this > > > all rigorously seems futile (you need a new > > > category between observable and UB), so it comes > > > down to compiler QoI on a case b

Re: [PATCH] git-backport: support renamed .cc files in commit message.

2022-01-14 Thread Martin Liška
On 1/14/22 08:44, Bernhard Reutner-Fischer wrote: On Wed, 12 Jan 2022 16:54:46 +0100 Martin Liška wrote: +def replace_file_in_changelog(lines, filename): +if not filename.endswith('.cc'): +return + +# consider all componenets of a path: gcc/ipa-icf.cc +while filename: +

Re: reordering of trapping operations and volatile

2022-01-14 Thread Paul Koning via Gcc
> On Jan 14, 2022, at 9:15 AM, Michael Matz via Gcc wrote: > > Hello, > > On Thu, 13 Jan 2022, Martin Uecker wrote: > > Handling all volatile accesses in the very same way would be > possible but quite some work I don't see much value in. I see some value. But

Re: reordering of trapping operations and volatile

2022-01-14 Thread Michael Matz via Gcc
Hello, On Thu, 13 Jan 2022, Martin Uecker wrote: > > > > Handling all volatile accesses in the very same way would be > > > > possible but quite some work I don't see much value in. > > > > > > I see some value. > > > > > > But an alternative could be to remove volatile > > > from the observ

git hooks: too strict check

2022-01-14 Thread Martin Liška
Hello. I'm working on a testsuite clean-up where some of the files are wrongly named. More precisely, so files have .cc extension and should use .C. However there's existing C test-case and it leads to: marxin@marxinbox:~/Programming/gcc/gcc/testsuite> find . -name test-asm.* ./jit.dg/test-asm.C