Re: A couple GIMPLE questions

2020-09-06 Thread Gary Oblock via Gcc
>That's not a question? Are you asking why PHIs exist at all? >They are the standard way to represent merging in SSA >representations. You can iterate on the PHIs of a basic block, etc. Marc, I first worked with the SSA form twenty years ago so yes I am aware of what a phi is... I've just never s

Re: A couple GIMPLE questions

2020-09-06 Thread Gary Oblock via Gcc
>Could you please get rid of this when posting on public mailing lists? No, I have no control over that but I'll give the email of our corporate IT if you want to complain to them... From: Marc Glisse Sent: Saturday, September 5, 2020 11:29 PM To: Gary Oblock C

Function signatures in extern "C".

2020-09-06 Thread Iain Sandoe
Hi g++.dg/abi/guard3.C has: extern "C" int __cxa_guard_acquire(); Which might not be a suitable declaration, depending on how the ‘extern “C”’ is supposed to affect the function signature generated. IF, the extern C should make this parse as a “K&R” style function - then the TYPE_ARG_TYP

Re: A couple GIMPLE questions

2020-09-06 Thread Richard Biener via Gcc
On September 6, 2020 9:38:45 AM GMT+02:00, Gary Oblock via Gcc wrote: >>That's not a question? Are you asking why PHIs exist at all? >>They are the standard way to represent merging in SSA >>representations. You can iterate on the PHIs of a basic block, etc. > >Marc, > >I first worked with the SS

Re: Function signatures in extern "C".

2020-09-06 Thread Jonathan Wakely via Gcc
On Sun, 6 Sep 2020 at 16:23, Iain Sandoe wrote: > > Hi > > g++.dg/abi/guard3.C > > has: > > extern "C" int __cxa_guard_acquire(); > > Which might not be a suitable declaration, depending on how the ‘extern > “C”’ is supposed to affect the function signature generated. > > IF, the extern C should m

Re: Function signatures in extern "C".

2020-09-06 Thread Iain Sandoe
Jonathan Wakely via Gcc wrote: On Sun, 6 Sep 2020 at 16:23, Iain Sandoe wrote: g++.dg/abi/guard3.C has: extern "C" int __cxa_guard_acquire(); Which might not be a suitable declaration, depending on how the ‘extern “C”’ is supposed to affect the function signature generated. IF, the exte

gcc-11-20200906 is now available

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

Re: Function signatures in extern "C".

2020-09-06 Thread Nathan Sidwell
GCC has an extension on machaines with cxx_implicit_extern_c (what used to be !NO_IMPLICIT_EXTERN_C). On such targets we'll treat 'extern "C" void Foo ()' as-if the argument list is variadic. (or something approximating that) perhaps that is confusing things? nathan On 9/6/20 4:43 PM, Iain

Re: about souce code location

2020-09-06 Thread Martin Sebor via Gcc
On 9/4/20 6:26 AM, 易会战 via Gcc wrote: how to check the location corresponding to a gimple statement? My instrument stmt include some memory access, I wish get right source code line. By context it is possible get wrong line. The gimple_location() function returns the location of the GIMPLE st

A problem with one instruction multiple latencies and pipelines

2020-09-06 Thread Qian, Jianhua
Hi I'm adding a new machine model. I have a problem when writing the "define_insn_reservation" for instruction scheduling. How to write the "define_insn_reservation" for one instruction that there are different latencies and pipelines according to parameter. For example, the ADD (shifted regist