Attached is an updated/enhanced patch with many more tests
and the suggested documentation tweak. It also restores
the handling of empty attributes that the first revision
inadvertently removed from the C parser.
The tests are much more comprehensive now but still not
exhaustive. I have added w
> Le 14 oct. 2018 à 00:43, Tobias Burnus a écrit :
>
> Hi Dominique,
>
> Dominique d'Humières wrote:
>> UNRESOLVED: gfortran.dg/inline_matmul_24.f90 -O0 scan-tree-dump-times
>> optimized "gamma5[__var_1_do * 4 + __var_2_do]" 1
>>
>> ! { dg-final { scan-tree-dump-times "gamma5\[_
Hi Dominique,
Dominique d'Humières wrote:
UNRESOLVED: gfortran.dg/inline_matmul_24.f90 -O0 scan-tree-dump-times optimized
"gamma5[__var_1_do * 4 + __var_2_do]" 1
! { dg-final { scan-tree-dump-times "gamma5\[__var_1_do \\* 4 \\+ __var_2_do\]" 1
"optimized" } }
Shouldn’t -fdump-tre
On Sat, 13 Oct 2018, H.J. Lu wrote:
> Add register source to movddup so that IRA will allow register source
> for *vec_dupv2di when SSE3 is enabled.
>
> gcc/
>
> PR target/87599
> * config/i386/sse.md (*vec_dupv2di): Add register source to
> movddup.
>
> gcc/testsuite/
>
>
Also disable AVX512IFMA, AVX5124FMAPS and AVX5124VNNIW when disabling
AVX512F.
gcc/
PR target/87572
* common/config/i386/i386-common.c (OPTION_MASK_ISA_AVX512F_UNSET):
Add OPTION_MASK_ISA_AVX512IFMA_UNSET,
OPTION_MASK_ISA_AVX5124FMAPS_UNSET and
OPTION_MASK_
Add register source to movddup so that IRA will allow register source
for *vec_dupv2di when SSE3 is enabled.
gcc/
PR target/87599
* config/i386/sse.md (*vec_dupv2di): Add register source to
movddup.
gcc/testsuite/
PR target/87599
* gcc.target/i386/pr87599
On 13 October 2018 12:56:14 CEST, Jonathan Wakely wrote:
>Yes, of course. We don't even look for usleep unless nanosleep isn't
>available, so I mean systems with no nanosleep *and* no usleep.
Right. Wasn't obvious to me from just the patch. Sorry for the noise..
This fixes an assertion failure compiling the Ada Web Server package (soap/
soap-message-xml.adb to be precise) at -O2 -gnatn -fPIC on x86/Linux:
+===GNAT BUG DETECTED==+
| Pro 20.0w (20181010-90) (i686-pc-linux-gnu) GCC error:
On Sat, 13 Oct 2018, Jonathan Wakely wrote:
On 13/10/18 11:07 +0200, Marc Glisse wrote:
--- libstdc++-v3/include/bits/alloc_traits.h(revision 265131)
+++ libstdc++-v3/include/bits/alloc_traits.h(working copy)
@@ -233,38 +233,43 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
using type =
On Fri, 2018-10-12 at 14:17 -0400, David Malcolm wrote:
> On Fri, 2018-10-12 at 14:45 -0400, David Malcolm wrote:
> > [re this thread "ToT build failure?":
> > https://gcc.gnu.org/ml/gcc-patches/2017-07/msg00344.html ]
> >
> > On Thu, 2017-07-06 at 20:58 +0200, Jakub Jelinek wrote:
> > > On Thu,
On 13/10/18 11:07 +0200, Marc Glisse wrote:
--- libstdc++-v3/include/bits/alloc_traits.h(revision 265131)
+++ libstdc++-v3/include/bits/alloc_traits.h(working copy)
@@ -233,38 +233,43 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
using type = decltype(__test<_Alloc>(0));
};
Hi Tobias,
UNRESOLVED: gfortran.dg/inline_matmul_24.f90 -O0 scan-tree-dump-times
optimized "gamma5[__var_1_do * 4 + __var_2_do]" 1
UNRESOLVED: gfortran.dg/inline_matmul_24.f90 -O1 scan-tree-dump-times
optimized "gamma5[__var_1_do * 4 + __var_2_do]" 1
UNRESOLVED: gfortran.
On Tue, 9 Oct 2018 at 14:48, Paolo Carlini wrote:
>
> Hi,
>
> On 09/10/18 15:33, Jonathan Wakely wrote:
> > On Tue, 9 Oct 2018 at 14:30, Paul Koning wrote:
> >> I'm trying to build the current code on Linux with GCC 4.3.2 (stock
> >> compiler in Fedora 10 which is my old test system). It fails
On Sat, 13 Oct 2018 at 08:49, Bernhard Reutner-Fischer
wrote:
>
> On 11 October 2018 23:36:15 CEST, Jonathan Wakely wrote:
>
> >But I'm assuming that systems with no usleep are probably rare, and
> >can live with rounding up to sleep for a full second.
>
> Well conforming implementations usually
On Sun, 2 Sep 2018, Jonathan Wakely wrote:
On 01/09/18 21:56 +0200, Marc Glisse wrote:
On Sat, 1 Sep 2018, Marc Glisse wrote:
this patch passed bootstrap+regtest on powerpc64le-unknown-linux-gnu.
I realized afterwards that for a C++17-only feature, that's not testing
much... So I changed i
On 11 October 2018 23:36:15 CEST, Jonathan Wakely wrote:
>But I'm assuming that systems with no usleep are probably rare, and
>can live with rounding up to sleep for a full second.
Well conforming implementations usually won't have usleep which was
obscolencent in SUSv3 and removed from SUSv4.
16 matches
Mail list logo