Re: [ANNOUNCEMENT] Mass rename of C++ .c files to .cc suffix is going to happen on Jan 17 evening UTC TZ

2022-01-17 Thread Martin Liška
On 1/13/22 12:01, Martin Liška wrote: Hello. Based on the discussion with release managers, the change is going to happen after stage4 begins. Martin Hi. The renaming patches have been just installed and I've built a few target compilers so far. I'll be online in ~10 hours from now so I can

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

2022-01-17 Thread Martin Liška
On 1/12/22 16:54, Martin Liška wrote: There's a patch that enhances git-backport so that it updates commit messages for files which name ends now with .cc and is still .c on a branch. The patch has been installed as I've made the renaming now. Cheers, Martin

Re: Accessing const parameter of GIMPLE_CALL

2022-01-17 Thread Martin Sebor via Gcc
On 1/17/22 12:18, Shubham Narlawar via Gcc wrote: On Mon, Jan 17, 2022 at 1:55 PM Richard Biener wrote: On Mon, Jan 17, 2022 at 12:54 AM David Malcolm via Gcc wrote: On Sun, 2022-01-16 at 18:52 +0530, Shubham Narlawar via Gcc wrote: Hello, Hi; various notes inline below... My aim is t

Re: Accessing const parameter of GIMPLE_CALL

2022-01-17 Thread Shubham Narlawar via Gcc
On Mon, Jan 17, 2022 at 1:55 PM Richard Biener wrote: > > On Mon, Jan 17, 2022 at 12:54 AM David Malcolm via Gcc > wrote: > > > > On Sun, 2022-01-16 at 18:52 +0530, Shubham Narlawar via Gcc wrote: > > > Hello, > > > > Hi; various notes inline below... > > > > > > > > My aim is to iterate over gi

Re: Accessing const parameter of GIMPLE_CALL

2022-01-17 Thread Shubham Narlawar via Gcc
On Mon, Jan 17, 2022 at 5:23 AM David Malcolm wrote: > > On Sun, 2022-01-16 at 18:52 +0530, Shubham Narlawar via Gcc wrote: > > Hello, > > Hi; various notes inline below... > > > > > My aim is to iterate over gimple call stmt parameters and check > > whether it is constant or constant expression a

Re: [Exception Handling] Why does frame unwind label have static alignment 4?

2022-01-17 Thread H.J. Lu via Gcc
On Mon, Jan 17, 2022 at 9:24 AM Joseph Faulls wrote: > > Hello all, > > Small disclaimer of being new to EH, but I have come across a problem that > seems quite fundamental to EH frame registry. I am targeting riscv64, but I > believe the problem to be entirely platform agnostic. > > When using

I am looking to buy a sponsored article on your website , http://www.gnu.org/

2022-01-17 Thread irsia jonas via Gcc
HI i hope you are well I am looking to buy a sponsored article on your website , http://www.gnu.org/ What is the cost per article ? Dofollow links permanent ? Can you add a link in your existing article? it could be a new article or an insertion in an already published article .? If you have m

[Exception Handling] Why does frame unwind label have static alignment 4?

2022-01-17 Thread Joseph Faulls
Hello all, Small disclaimer of being new to EH, but I have come across a problem that seems quite fundamental to EH frame registry. I am targeting riscv64, but I believe the problem to be entirely platform agnostic. When using EH frame registry, a label is put at the beginning of the frame unw

Re: reordering of trapping operations and volatile

2022-01-17 Thread Michael Matz via Gcc
Hello, On Sat, 15 Jan 2022, Martin Uecker wrote: > > Because it interferes with existing optimisations. An explicit > > checkpoint has a clear meaning. Using every volatile access that way > > will hurt performance of code that doesn't require that behaviour for > > correctness. > > This is w

GCC 12.0.1 Status Report (2022-01-17), Stage 4 starts now

2022-01-17 Thread Richard Biener via Gcc
Status == The GCC master branch is now in regression and documentation fixing mode (Stage 4) in preparation for the release of GCC 13. Re-opening of general development will happen once we reach zero P1 regressions which is when we branch for the release. Time wise history projects that to

Re: git hooks: too strict check

2022-01-17 Thread Martin Liška
On 1/14/22 17:10, Michael Matz wrote: You can't have that, the check is correct. There are filesystems (NTFS for instance) that are case-preserving but case-insensitive, on those you really can't have two files that differ only in casing. You need to find a different solution, either consistent

Re: Accessing const parameter of GIMPLE_CALL

2022-01-17 Thread Richard Biener via Gcc
On Mon, Jan 17, 2022 at 12:54 AM David Malcolm via Gcc wrote: > > On Sun, 2022-01-16 at 18:52 +0530, Shubham Narlawar via Gcc wrote: > > Hello, > > Hi; various notes inline below... > > > > > My aim is to iterate over gimple call stmt parameters and check > > whether it is constant or constant exp