How to generate a call inst. sequence?

2022-01-18 Thread Andras Tantos
All, I'm working on porting GCC to a processor architecture that doesn't have a (HW) stack nor a call instruction. This means that for calls, I need to generate the following instruction sequence:     // move stack-pointer:     $sp <- $sp-4     // load return address:     $r3 <- return_label

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

2022-01-18 Thread Harald Anlauf via Gcc
Am 17.01.22 um 22:26 schrieb 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. Chee

Re: Accessing const parameter of GIMPLE_CALL

2022-01-18 Thread Shubham Narlawar via Gcc
On Tue, Jan 18, 2022 at 2:20 PM Richard Biener wrote: > > On Mon, Jan 17, 2022 at 8:19 PM Shubham Narlawar > 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

Re: Accessing const parameter of GIMPLE_CALL

2022-01-18 Thread Shubham Narlawar via Gcc
On Tue, Jan 18, 2022 at 2:19 AM Martin Sebor wrote: > > 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, Shu

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

2022-01-18 Thread Martin Liška
On 1/18/22 14:10, Richard Earnshaw wrote: Is that worth adding to contrib/gcc-git-customization.sh ? Yes, can you please do that? Thanks, Martin

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

2022-01-18 Thread Richard Earnshaw via Gcc
On 17/01/2022 21:41, Martin Liška wrote: 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

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

2022-01-18 Thread Martin Liška
LGTM. I've just installed that, the Ada testsuite should work now. Martin

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

2022-01-18 Thread Jakub Jelinek via Gcc
On Tue, Jan 18, 2022 at 10:08:20AM +0100, Martin Liška wrote: > On 1/18/22 09:53, Richard Biener wrote: > > Technically all release managers are also global reviewers, but I > > agree the speciality > > of the Ada setup (esp. the runtime being in gcc/) could have been > > anticipated. > > Yeah, I

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

2022-01-18 Thread Martin Liška
On 1/18/22 09:53, Richard Biener wrote: Technically all release managers are also global reviewers, but I agree the speciality of the Ada setup (esp. the runtime being in gcc/) could have been anticipated. Yeah, I thought that building Ada FE is enough for testing effort, sorry. I would like t

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

2022-01-18 Thread Richard Biener via Gcc
On Tue, Jan 18, 2022 at 9:46 AM Eric Botcazou via Gcc-patches wrote: > > > Release managers. > > They certainly have authority on the timing, but not on the contents. Technically all release managers are also global reviewers, but I agree the speciality of the Ada setup (esp. the runtime being in

Re: Accessing const parameter of GIMPLE_CALL

2022-01-18 Thread Richard Biener via Gcc
On Mon, Jan 17, 2022 at 8:19 PM Shubham Narlawar 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, > > > > > >

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

2022-01-18 Thread Eric Botcazou via Gcc
> Release managers. They certainly have authority on the timing, but not on the contents. > Working on that right now, sorry.. OK, thanks in advance. -- Eric Botcazou

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

2022-01-18 Thread Martin Liška
On 1/18/22 09:36, Eric Botcazou wrote: Martin, 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 address potential issues caused by the patch. Who approved it though? Release managers. The renaming of

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

2022-01-18 Thread Eric Botcazou via Gcc
Martin, > 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 address > potential issues caused by the patch. Who approved it though? The renaming of the C files in the ada/ directory is wrong and should be

Re: reordering of trapping operations and volatile

2022-01-18 Thread Richard Biener via Gcc
On Mon, Jan 17, 2022 at 3:11 PM Michael Matz via Gcc wrote: > > 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