Snapshot gcc-6-20160428 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160428/
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
On 04/28/2016 03:54 PM, Andrew Pinski wrote:
On Thu, Apr 28, 2016 at 2:49 PM, Martin Sebor wrote:
Many GCC tests for constexpr rely on static_assert to verify things
work correctly. While testing some changes of my own, I was surprised
to find the static_asserts pass even though my changes did
On Thu, Apr 28, 2016 at 2:49 PM, Martin Sebor wrote:
> Many GCC tests for constexpr rely on static_assert to verify things
> work correctly. While testing some changes of my own, I was surprised
> to find the static_asserts pass even though my changes did not (see
> below). It took me a while to
Many GCC tests for constexpr rely on static_assert to verify things
work correctly. While testing some changes of my own, I was surprised
to find the static_asserts pass even though my changes did not (see
below). It took me a while to realize that, and it took printing
the computed constant val
On Thu, Apr 28, 2016 at 12:35 AM, David Wohlferd
wrote:
> As part of the work I've done on inline asm, I've been looking thru the bugs
> for it. There appear to be a number that have been fixed or overtaken by
> events over the years, but the bug is still open.
>
> Is closing some of these old b
On 04/28/2016 01:35 AM, David Wohlferd wrote:
As part of the work I've done on inline asm, I've been looking thru the
bugs for it. There appear to be a number that have been fixed or
overtaken by events over the years, but the bug is still open.
Is closing some of these old bugs of any value?
Hi, Andrew
On 2016/4/28 5:15, Andrew Pinski wrote:
On Wed, Apr 27, 2016 at 12:30 AM, Andrew Pinski wrote:
On Fri, Apr 22, 2016 at 8:37 PM, Zhangjian (Bamvor)
wrote:
Hi, Yury
On 2016/4/6 6:44, Yury Norov wrote:
There are about 20 failing tests of 782 in lite scenario.
float_bessel
float_e
On Thu, Apr 28, 2016 at 9:35 AM, David Wohlferd wrote:
> As part of the work I've done on inline asm, I've been looking thru the bugs
> for it. There appear to be a number that have been fixed or overtaken by
> events over the years, but the bug is still open.
>
> Is closing some of these old bug
As part of the work I've done on inline asm, I've been looking thru the
bugs for it. There appear to be a number that have been fixed or
overtaken by events over the years, but the bug is still open.
Is closing some of these old bugs of any value?
If so, how do I pursue this?
dw
