gcc-6-20160908 is now available

2016-09-08 Thread gccadmin
Snapshot gcc-6-20160908 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160908/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6

Re: why do we need xtensa-config.h?

2016-09-08 Thread Oleksij Rempel
Am 08.09.2016 um 18:10 schrieb augustine.sterl...@gmail.com: > On Thu, Sep 8, 2016 at 8:14 AM, Oleksij Rempel wrote: >> Am 07.09.2016 um 18:21 schrieb augustine.sterl...@gmail.com: >>> On Tue, Sep 6, 2016 at 11:55 PM, Thomas Schwinge >>> wrote: Hi! Neither do I really know anything

Re: why do we need xtensa-config.h?

2016-09-08 Thread augustine.sterl...@gmail.com
On Thu, Sep 8, 2016 at 8:14 AM, Oleksij Rempel wrote: > Am 07.09.2016 um 18:21 schrieb augustine.sterl...@gmail.com: >> On Tue, Sep 6, 2016 at 11:55 PM, Thomas Schwinge >> wrote: >>> Hi! >>> >>> Neither do I really know anything about Xtensa, nor do I have a lot of >>> experience in these parts o

Re: why do we need xtensa-config.h?

2016-09-08 Thread Oleksij Rempel
Am 07.09.2016 um 18:21 schrieb augustine.sterl...@gmail.com: > On Tue, Sep 6, 2016 at 11:55 PM, Thomas Schwinge > wrote: >> Hi! >> >> Neither do I really know anything about Xtensa, nor do I have a lot of >> experience in these parts of GCC back ends, but: > > There is a lot of background to know

Re: Advice sought for debugging a lto1 ICE (was: Implement C _FloatN, _FloatNx types [version 6])

2016-09-08 Thread Thomas Schwinge
Hi! On Wed, 7 Sep 2016 14:23:18 +0200, Richard Biener wrote: > On Wed, Sep 7, 2016 at 1:52 PM, Thomas Schwinge > wrote: > > I trimmed the CC list -- I'm looking for advice about debugging a lto1 > > ICE. > > > > On Fri, 19 Aug 2016 11:05:59 +, Joseph Myers > > wrote: > >> On Fri, 19 Aug

[PATCH, testsuite]: Test compat _Complex varargs passing

2016-09-08 Thread Uros Bizjak
On Mon, Sep 5, 2016 at 1:45 PM, Joseph Myers wrote: > 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 arg