Re: GCC 4.8.4 Status Report (2014-12-12)

2014-12-12 Thread David Edelsohn
On Fri, Dec 12, 2014 at 7:17 PM, Jakub Jelinek wrote: > On Fri, Dec 12, 2014 at 04:51:21PM -0500, David Edelsohn wrote: >> GCC 4.8 branch has degraded from 14 libstdc++ failures to 153. This > > On which target, when it has been reported, are the libstdc++ folks aware of > that? > I see zero regr

Re: GCC 4.8.4 Status Report (2014-12-12)

2014-12-12 Thread Jakub Jelinek
On Fri, Dec 12, 2014 at 04:51:21PM -0500, David Edelsohn wrote: > GCC 4.8 branch has degraded from 14 libstdc++ failures to 153. This On which target, when it has been reported, are the libstdc++ folks aware of that? I see zero regressions on x86_64-linux and i686-linux from a build 14 days ago,

Re: Idea for improvement to g++ - warning

2014-12-12 Thread Jonathan Wakely
On 12 December 2014 at 23:38, Kendrick Hamilton wrote: > Hello, > > I had an idea of a warning g++ might be able to add. The purpose of the > warning is to help prevent bugs. The warning is to occur when you might > destroy an inherited class using the base classes pointer. To illustrate > conside

Idea for improvement to g++ - warning

2014-12-12 Thread Kendrick Hamilton
Hello, I had an idea of a warning g++ might be able to add. The purpose of the warning is to help prevent bugs. The warning is to occur when you might destroy an inherited class using the base classes pointer. To illustrate consider class base { public: base(); ~base(); }

Re: GCC 4.8.4 Status Report (2014-12-12)

2014-12-12 Thread David Edelsohn
On Fri, Dec 12, 2014 at 7:35 AM, Jakub Jelinek wrote: > Status > == > > The GCC 4.8.4-rc1 release candidate has been released. > The branch is frozen now, all changes require release manager approval > until the final release of GCC 4.8.4 which should happen roughly > one week after the releas

RE: Vector modes and the corresponding width integer mode

2014-12-12 Thread Matthew Fortune
Hi Bingfeng, Thanks for commenting. It's reassuring to know that at least some ports do not have the corresponding integer modes. I have now also understood some of the background to the extra integer modes in ARM NEON and as far as I can tell the integer modes represent an opaque view of the regi

GCC 4.8.4 Status Report (2014-12-12)

2014-12-12 Thread Jakub Jelinek
Status == The GCC 4.8.4-rc1 release candidate has been released. The branch is frozen now, all changes require release manager approval until the final release of GCC 4.8.4 which should happen roughly one week after the release candidate. Quality Data Priority # Chan

GCC 4.8.4 Release Candidate available from gcc.gnu.org

2014-12-12 Thread Jakub Jelinek
The first release candidate for GCC 4.8.4 is available from ftp://gcc.gnu.org/pub/gcc/snapshots/4.8.4-RC-20141212 and shortly its mirrors. It has been generated from SVN revision 218649. I have so far bootstrapped and tested the release candidate on x86_64-linux and i686-linux. Please test

Re: [RFC] GCC vector extension: binary operators vs. differing signedness

2014-12-12 Thread Ulrich Weigand
Richard Biener wrote: > On Thu, Dec 11, 2014 at 4:04 PM, Ulrich Weigand wrote: > > However, if we make that change, there will be some cases that regress: the > > problem is that an expression "x + y" has *one* result type, and some things > > you do with the result will require that type to match

RE: Vector modes and the corresponding width integer mode

2014-12-12 Thread Bingfeng Mei
I don't think it is required. For example, PowerPC port supports V8SImode, but I don't see OImode. Just sometimes it could come handy to have the equal size scalar mode. Cheers, Bingfeng > -Original Message- > From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of > Matt

Re: [RFC] GCC vector extension: binary operators vs. differing signedness

2014-12-12 Thread Richard Biener
On Thu, Dec 11, 2014 at 4:04 PM, Ulrich Weigand wrote: > Richard Biener wrote: >> On Wed, Dec 10, 2014 at 10:09 PM, Ulrich Weigand wrote: >> > So at the very least, we should bring the documentation in line with the >> > actual behavior. However, as seen above, that actual behavior is probably >