ARC's pending patches
Hi, Until GCC steering committee will take a decision about ARC's maintainer, please can any of the global reviewer review my pending ARC's patches: https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01100.html https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01101.html https://gcc.gnu.org/ml/gcc-patches/2016-05/msg02327.html https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01290.html https://gcc.gnu.org/ml/gcc-patches/2016-06/msg02041.html https://gcc.gnu.org/ml/gcc-patches/2016-06/msg02042.html https://gcc.gnu.org/ml/gcc-patches/2016-06/msg02044.html https://gcc.gnu.org/ml/gcc-patches/2016-07/msg00386.html https://gcc.gnu.org/ml/gcc-patches/2016-07/msg00389.html Any help is highly appreciated, Claudiu
Re: Testing _Complex varargs passing [was: Alpha, ABI change: pass SFmode and SCmode varargs by reference]
On Sun, 4 Sep 2016, Uros Bizjak wrote: > It looks that different handling of _Complex char, _Complex short and > _Complex float is there on purpose. Is (was?) there a limitation in a > c language standard that prevents passing of these arguments as > varargs? Well, ISO C doesn't define complex integers at all. But it's deliberate (see DR#206) that _Complex float doesn't promote to _Complex double in variable arguments. And there is nothing in ISO C to stop _Complex float being passed in variable arguments. For all these types including the complex integer ones: given that the front end doesn't promote them, they should be usable in variable arguments. -- Joseph S. Myers jos...@codesourcery.com
Re: ARC's pending patches
Hi Claudiu, On Mon, 5 Sep 2016, Claudiu Zissulescu wrote: > Until GCC steering committee will take a decision about ARC's > maintainer can you please share some more background on this? I do not recall any conversation around this at the steering committee. The GCC MAINTAINERS file still lists arc portJoern Rennecke and I am copying Jörn on this. In my experience, the best way to get additional maintainers or have a replacement is for the (or a) current maintainer to nominate her. > https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01100.html > https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01101.html > https://gcc.gnu.org/ml/gcc-patches/2016-05/msg02327.html > https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01290.html > https://gcc.gnu.org/ml/gcc-patches/2016-06/msg02041.html > https://gcc.gnu.org/ml/gcc-patches/2016-06/msg02042.html > https://gcc.gnu.org/ml/gcc-patches/2016-06/msg02044.html > https://gcc.gnu.org/ml/gcc-patches/2016-07/msg00386.html > https://gcc.gnu.org/ml/gcc-patches/2016-07/msg00389.html Gerald
RE: ARC's pending patches
Hi, On the last GNU Cauldron, Joern notify us he want to stand off as an ARC maintainer, not giving a particular date though. He did review a number of patches in the beginning of this year, and after that he went silent. I tried to contact him directly on the subject, without success. Hence, I wrote an email to Richard Earnshaw expressing my concerns about ARC backend, as his name is in top of the global reviewers. He declined competency on the topic, and forwarded my email to GNU steering committee to solve the issue. Please let me know if you need more info, Claudiu > -Original Message- > From: Gerald Pfeifer [mailto:ger...@pfeifer.com] > Sent: Monday, September 05, 2016 4:13 PM > To: Claudiu Zissulescu ; Joern Rennecke > > Cc: Francois Bedard ; gcc@gcc.gnu.org > Subject: Re: ARC's pending patches > > Hi Claudiu, > > On Mon, 5 Sep 2016, Claudiu Zissulescu wrote: > > Until GCC steering committee will take a decision about ARC's > > maintainer > > can you please share some more background on this? I do not > recall any conversation around this at the steering committee. > > > The GCC MAINTAINERS file still lists > > arc portJoern Rennecke > > and I am copying Jörn on this. In my experience, the best > way to get additional maintainers or have a replacement is > for the (or a) current maintainer to nominate her. > > > https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01100.html > > https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01101.html > > https://gcc.gnu.org/ml/gcc-patches/2016-05/msg02327.html > > https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01290.html > > https://gcc.gnu.org/ml/gcc-patches/2016-06/msg02041.html > > https://gcc.gnu.org/ml/gcc-patches/2016-06/msg02042.html > > https://gcc.gnu.org/ml/gcc-patches/2016-06/msg02044.html > > https://gcc.gnu.org/ml/gcc-patches/2016-07/msg00386.html > > https://gcc.gnu.org/ml/gcc-patches/2016-07/msg00389.html > > Gerald
