On Thu, Mar 2, 2017 at 11:31 PM, Jakub Jelinek wrote:
> Hi!
>
> On Wed, Mar 01, 2017 at 08:26:36PM +0100, Uros Bizjak wrote:
>> 2017-03-01 Uros Bizjak
>>
>> * config/i386/i386.c (print_reg): Warn for values of
>> unsupported size in integer register.
>>
>> testsuite/ChangeLog:
>>
>> 201
On Thu, Mar 2, 2017 at 3:26 PM, Jason Merrill wrote:
> On Wed, Mar 1, 2017 at 3:58 PM, Jason Merrill wrote:
>> On Tue, Feb 28, 2017 at 1:56 PM, Jason Merrill wrote:
>>> This patch implements some proposed resolutions to open issues with
>>> C++17 class template argument deduction.
>>
>> And some
OK.
On Thu, Mar 2, 2017 at 8:31 AM, Marek Polacek wrote:
> This PR complains that the -Wpedantic -Werror=write-strings combination
> doesn't
> result in an error but in a pedwarn, which I think is a valid point. The
> principle is that more specific options take precedence over less specific
>
On Wed, Mar 1, 2017 at 3:58 PM, Jason Merrill wrote:
> On Tue, Feb 28, 2017 at 1:56 PM, Jason Merrill wrote:
>> This patch implements some proposed resolutions to open issues with
>> C++17 class template argument deduction.
>
> And some more:
This patch handles the issues of references to member
On 03/02/2017 12:58 AM, Richard Biener wrote:
On Wed, 1 Mar 2017, Martin Sebor wrote:
On 02/28/2017 11:41 PM, Richard Biener wrote:
On March 1, 2017 3:34:46 AM GMT+01:00, Martin Sebor
wrote:
On 02/28/2017 01:41 PM, Richard Biener wrote:
On February 28, 2017 7:00:39 PM GMT+01:00, Jeff Law
Hi!
On Wed, Mar 01, 2017 at 08:26:36PM +0100, Uros Bizjak wrote:
> 2017-03-01 Uros Bizjak
>
> * config/i386/i386.c (print_reg): Warn for values of
> unsupported size in integer register.
>
> testsuite/ChangeLog:
>
> 2017-03-01 Uros Bizjak
>
> * gcc.target/i386/invsize-2.c: Ne
On 03/02/2017 02:40 PM, Andrew Pinski wrote:
On Thu, Mar 2, 2017 at 1:33 PM, Martin Sebor wrote:
On 03/02/2017 01:08 AM, Richard Biener wrote:
On Thu, Mar 2, 2017 at 2:01 AM, Joseph Myers
wrote:
On Wed, 1 Mar 2017, Martin Sebor wrote:
Joseph, since you commented on the bug, do you have a
Hi!
For -O1 and above, we force all operands and targets of x86 builtins into
registers during expansion, because we expect combiner will do its job.
But for -O0, we try to keep them in MEM if the predicate allows it, we just
make sure that at most one input operand is a MEM. We still allow
MEM d
On Thu, Mar 2, 2017 at 1:33 PM, Martin Sebor wrote:
> On 03/02/2017 01:08 AM, Richard Biener wrote:
>>
>> On Thu, Mar 2, 2017 at 2:01 AM, Joseph Myers
>> wrote:
>>>
>>> On Wed, 1 Mar 2017, Martin Sebor wrote:
>>>
Joseph, since you commented on the bug, do you have a suggestion
for a dif
Hi!
The __atomic/__sync builtins have nothrow conditional on
-fnon-call-exceptions, but internal fns have right now only constant flags.
As per discussions on IRC, this patch removes ECF_NOTHROW from those 4 ifns
and instead calls gimple_call_set_nothrow when creating those to say
if it can or can
On 03/02/2017 01:08 AM, Richard Biener wrote:
On Thu, Mar 2, 2017 at 2:01 AM, Joseph Myers wrote:
On Wed, 1 Mar 2017, Martin Sebor wrote:
Joseph, since you commented on the bug, do you have a suggestion
for a different site for it or a guard? The only other call to
the function is in the For
Toma Tabacu writes:
> pr68273.c currently fails when targeting MIPS64 with the n64 ABI.
> This is because it is checking for some registers in SImode, but, because of
> n64, they will actually be in DImode.
>
> This patch restricts matching for SImode registers to ilp32 targets and adds
> matchin
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Danish team of translators. The file is available at:
http://translationproject.org/latest/gcc/da.po
(This file, 'gcc-7.1-b20170226.da.po', h
On 03/02/2017 06:50 PM, Martin Liška wrote:
Hello.
This is second part of fixes needed to not trigger integer overflow in gcse
pass.
So, how is this intended to work? The min/max stored in the param is an
int, and by using a HOST_WIDE_INT here, we expect that it is a larger
type and therefo
On 03/02/2017 06:35 PM, Marek Polacek wrote:
While at it, I fixed wrong formatting in the nearby code. Also use NULL_TREE
instead of 0 where appropriate. I really dislike those zeros-as-trees; one
day I'll just go and turn them into NULL_TREEs.
I sympathize, but it makes it harder to see whic
On Thu, Mar 2, 2017 at 10:10 AM, Richard Biener wrote:
> On Thu, 2 Mar 2017, Uros Bizjak wrote:
>
>> > Annoying me for quite some time, fixed as follows.
>> >
>> > Tested on x86_64-unknown-linux-gnu, applied to trunk.
>>
>> Index: gcc/testsuite/gcc.dg/rtl/x86_64/dfinit.c
>> ===
Fixed as r245849. Thanks...
-- Bill
Bill Schmidt, Ph.D.
GCC for Linux on Power
Linux on Power Toolchain
IBM Linux Technology Center
wschm...@linux.vnet.ibm.com
> On Mar 2, 2017, at 11:33 AM, Bill Schmidt wrote:
>
> Hi Andreas,
>
> We discovered the problem this morning in-house and are worki
Hi,
The expanded warnings for uninitialized memory caught a couple of
problems in the rs6000 back end, causing bootstrap to fail. Some
of them were just introduced yesterday, while others are a bit
older. These are just misnumbering of operands, skipping over
one and causing it to be uninitializ
On 2 March 2017 at 05:25, Jonathan Wakely wrote:
> Some of these are years old, most are more recent. The new testcase
> should help prevent us trying to use these names again.
>
> PR libstdc++/79789
> * include/bits/hashtable_policy.h (__clp2): Use reserved names for
> para
Hello!
Attached patch adds new insn_and_split pattern to handle pre_modify
XFmode push variant. -m96bit-long-double option sets XFmode size to 12
bytes that is not divisible with push size (8 bytes), resulting in
pre_modify push variant.
2017-03-02 Uros Bizjak
PR target/79514
* config
This PR complains that the -Wpedantic -Werror=write-strings combination doesn't
result in an error but in a pedwarn, which I think is a valid point. The
principle is that more specific options take precedence over less specific
options, so e.g. -Wpedantic -Wno-write-strings shouldn't give a -Wwrit
Hello.
This is second part of fixes needed to not trigger integer overflow in gcse
pass.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ready to be installed?
Martin
>From a3e8ca75be55bd6d707f54ae3972e30285b64566 Mon Sep 17 00:00:00 2001
From: marxin
Date: Thu, 2 Ma
Hello.
It can happen with inlining and -fno-tree-dce that VAR_DECL for a SSA
NAME was removed and thus the poisoning should not have any usage.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ready to be installed?
Martin
>From d8aa72dc1d696f5500c00b6c2f532f2a87cf58d2
Hello.
I've just followed Richi's advises in the PR.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ready to be installed?
Martin
>From 9a850909d00e2b63961167665d48f7ebbb99ac84 Mon Sep 17 00:00:00 2001
From: marxin
Date: Thu, 2 Mar 2017 13:34:55 +0100
Subject: [PATCH
This patch fixes an ICE-on-invalid where we redefine a function whose prototype
parameter list contains error_mark_node, which then causes a crash in
store_parm_decls_oldstyle. Fixed by adding yet another error_mark_node check.
While at it, I fixed wrong formatting in the nearby code. Also use N
Hi Andreas,
We discovered the problem this morning in-house and are working on a patch.
-- Bill
Bill Schmidt, Ph.D.
GCC for Linux on Power
Linux on Power Toolchain
IBM Linux Technology Center
wschm...@linux.vnet.ibm.com
> On Mar 2, 2017, at 11:25 AM, Andreas Schwab wrote:
>
> ../../gcc/config
../../gcc/config/rs6000/vector.md:721:14: error: 'operands[3]' is used
uninitialized in this function [-Werror=uninitialized]
UNSPEC_PREDICATE))
~^
../../gcc/config/rs6000/vector.md: In function 'rtx_def*
gen_vector_ne_v8hi_p(rtx, rtx, rtx)':
../../gcc/config/rs6000
Hi,
pr68273.c currently fails when targeting MIPS64 with the n64 ABI.
This is because it is checking for some registers in SImode, but, because of
n64, they will actually be in DImode.
This patch restricts matching for SImode registers to ilp32 targets and adds
matching for DImode registers for l
On 27/02/17 05:48, NightStrike wrote:
On Feb 22, 2017 10:06 AM, "Thomas Preudhomme" mailto:thomas.preudho...@foss.arm.com>> wrote:
Oh great thanks!
Best regards,
Thomas
On 17/02/17 22:52, JonY wrote:
On 02/17/2017 11:31 AM, Thomas Preudhomme wrote:
Her
> -Original Message-
> From: Toma Tabacu [mailto:toma.tab...@imgtec.com]
> Sent: Thursday, March 2, 2017 11:47 AM
> To: Rainer Orth
> Cc: Moore, Catherine ; gcc-
> patc...@gcc.gnu.org; Matthew Fortune
>
> Subject: RE: [PATCH,testsuite] Skip gcc.dg/lto/pr60449_0.c for mips*-*-
> elf* tar
Hi,
> From: Rainer Orth
> >
> > gcc/testsuite/
> >
> > * gcc.dg/lto/pr60449_0.c: Add dg-require-effective-target for
> > gettimeofday. Remove dg-skip-if for AVR.
>
> Two spaces after period.
>
Fixed.
> > * lib/target-supports.exp (check_effective_target_gettimeofday): New.
>
> Bet
Hi Toma,
>> that's not what I suggested (or at least meant to suggest): having
>> gettimeofday as an effective-target keyword (like setrlimit, mmap, and
>> others) is the way to go, just your previous implementation of
>> check_effective_target_gettimeofday was problematic/unreliable.
>>
>> If yo
Hi,
the following patch defines the PARAM_MIN_VECT_LOOP_BOUND parameter in
the s390 backend. It helps with the vectorization epilogue problem
described here [1].
I see an overall performance increase of > 1% in SPECfp2006, yet some
cases like cactusADM regress. This seems to be caused by the vec
Hi,
This patch fixes an assert failure when linking one LTOed object file
having a weak alias with a regular object file containing a strong
definition for that same symbol. The patch is twofold:
+ do not add an alias to a partition if it is external
+ do not declare (.globl) an alias if it is e
Looks like I broke $subject, thus the following. The issue is similar
as the fixed-value.c case I fixed with the Wuninit patch.
Bootstrap on x86_64-unknown-linux-gnu with release checking in stage3,
will commit soonish.
Richard.
2017-03-02 Richard Biener
* fold-const.c (const_binop
On 03/02/2017 10:23 AM, Jakub Jelinek wrote:
2017-03-02 Jakub Jelinek
PR rtl-optimization/79780
* cprop.c (one_cprop_pass): When second and further conditional trap
in a single basic block is turned into an unconditional trap, turn it
into a deleted note to avo
On Thu, 2 Mar 2017, Richard Biener wrote:
> On Thu, 2 Mar 2017, Jakub Jelinek wrote:
>
> > On Wed, Mar 01, 2017 at 03:03:29PM +0100, Richard Biener wrote:
> > > One issue with the patch is duplicate warnings as TREE_NO_WARNING
> > > doesn't work very well on tcc_reference trees which are not
> >
Am 02.03.2017 um 13:02 schrieb Jakub Jelinek:
And this needs to use *matmul_fn instead of *matmul_p too.
The whole point is that matmul_p is only loaded using __atomic_load_n
and only optionally stored using __atomic_store_n.
Ok with those changes.
Thanks! Committed as
https://gcc.gnu.org/vie
On 03/02/2017 01:32 PM, Marek Polacek wrote:
> It's probably too late to change opt-functions.awk now, so the following
> is a badn aid fix.
Thanks for the patch, I've written this to my TODO list for new stage1.
It's bit connected to IntegerRange attribute which I would like to append
to options.
As demonstrated by this test, we can crash on the assert in alloca_call_type:
gcc_assert (is_vla || warn_alloca_limit > 0);
when -Walloca-larger-than= receives an argument greater than INT_MAX. Even
though warn_vla_limit is marked as UInteger in c.opt, those are still
represented as ints; opt-func
On Wed, 1 Mar 2017, Richard Sandiford wrote:
> Richard Biener writes:
> > On Wed, 1 Mar 2017, Richard Sandiford wrote:
> >
> >> Richard Biener writes:
> >> > On Wed, 1 Mar 2017, Richard Sandiford wrote:
> >> >
> >> >> Richard Biener writes:
> >> >> > On Wed, 1 Mar 2017, Richard Sandiford wrote:
On Thu, Mar 02, 2017 at 12:57:05PM +0100, Thomas Koenig wrote:
> --- m4/matmul.m4 (Revision 245836)
> +++ m4/matmul.m4 (Arbeitskopie)
> @@ -123,9 +123,14 @@ void matmul_'rtype_code` ('rtype` * const restrict
> 'rtype` * const restrict a, 'rtype` * const restrict b, int try_blas,
>
Hi Jakub,
Actually, I see a problem, but not related to this patch.
I bet e.g. tsan would complain heavily on the wrappers, because the code
is racy:
Here is a patch implementing your suggestion. Tested at least so
far that all matmul test cases pass on my machine.
OK for trunk?
Regards
On Thu, 2 Mar 2017, Jakub Jelinek wrote:
> On Wed, Mar 01, 2017 at 03:03:29PM +0100, Richard Biener wrote:
> > One issue with the patch is duplicate warnings as TREE_NO_WARNING
> > doesn't work very well on tcc_reference trees which are not
> > shared. A followup could use some sort of hash table
Applied to trunk, tested with x86_64-w64-mingw32.
Changelog:
2017-03-02 Jonathan Yong <10wa...@gmail.com>
* config/i386/gthr-win32.h: Define NOGDI before
windows.h include to prevent w32api CC_NONE macro
clash with libgfortran.
--- trunk/libgcc/config/i386/gthr
On 03/01/2017 11:36 AM, JonY wrote:
> Patch OK?
>
> ChangeLog:
> * unwind-seh.c: Suppress warnings for RtlUnwindEx() calls.
>
Applied, tested with x86_64-w64-mingw32 to trunk.
signature.asc
Description: OpenPGP digital signature
On Thu, Mar 02, 2017 at 11:45:59AM +0100, Thomas Koenig wrote:
> Here's the updated version, which just uses FMA for AVX2.
>
> OK for trunk?
>
> Regards
>
> Thomas
>
> 2017-03-01 Thomas Koenig
>
> PR fortran/78379
> * m4/matmul.m4: (matmul_'rtype_code`_avx2): Also gene
On Thu, Mar 02, 2017 at 11:45:59AM +0100, Thomas Koenig wrote:
> Here's the updated version, which just uses FMA for AVX2.
>
> OK for trunk?
>
> Regards
>
> Thomas
>
> 2017-03-01 Thomas Koenig
>
> PR fortran/78379
> * m4/matmul.m4: (matmul_'rtype_code`_avx2): Also gene
Here's the updated version, which just uses FMA for AVX2.
OK for trunk?
Regards
Thomas
2017-03-01 Thomas Koenig
PR fortran/78379
* m4/matmul.m4: (matmul_'rtype_code`_avx2): Also generate for
reals. Add fma to target options.
(matmul_'rtype_code`):
On Wed, Mar 01, 2017 at 03:03:29PM +0100, Richard Biener wrote:
> One issue with the patch is duplicate warnings as TREE_NO_WARNING
> doesn't work very well on tcc_reference trees which are not
> shared. A followup could use some sort of hash table to mitigate
Can't we use TREE_NO_WARNING on get_
Hi,
> From: Rainer Orth
>
> that's not what I suggested (or at least meant to suggest): having
> gettimeofday as an effective-target keyword (like setrlimit, mmap, and
> others) is the way to go, just your previous implementation of
> check_effective_target_gettimeofday was problematic/unreliable
On Thu, Mar 02, 2017 at 10:52:08AM +0100, Richard Biener wrote:
>
> Another case of missed TREE_ADDRESSABLE on vector indexing.
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu.
>
> Ok for trunk?
Ok (given what Joseph wrote in the PR and that c_fully_fold_internal
handles VIEW_CONVERT_EX
Hi,
On Thu, 2017-03-02 at 10:36 +0100, Markus Trippelsdorf wrote:
> The following patch from Mark Wielaard fixes many (all?) open demangler
> bugs that happen because we overflow the stack due to infinite
> recursion.
>
> I'm not sure why Mark didn't post the patch himself.
> Anyway here it is.
>
Another case of missed TREE_ADDRESSABLE on vector indexing.
Bootstrapped and tested on x86_64-unknown-linux-gnu.
Ok for trunk?
2017-03-02 Richard Biener
PR c/79756
* c-common.c (c_common_mark_addressable_vec): Look through
C_MAYBE_CONST_EXPR.
* gcc.dg/vector
The following patch from Mark Wielaard fixes many (all?) open demangler
bugs that happen because we overflow the stack due to infinite
recursion.
I'm not sure why Mark didn't post the patch himself.
Anyway here it is.
Any comments?
Thanks.
diff --git a/include/demangle.h b/include/demangle.h
inde
Hi!
As the testcase shows, if more than one conditional trap is turned into
non-conditional during one_cprop_pass in a single bb, we only split the
bb after the first one (because the rest is going to be removed as
unreachable), but before that happens, we trigger RTL verification that
complains t
On Thu, Mar 2, 2017 at 10:10 AM, Richard Biener wrote:
> On Thu, 2 Mar 2017, Uros Bizjak wrote:
>
>> > Annoying me for quite some time, fixed as follows.
>> >
>> > Tested on x86_64-unknown-linux-gnu, applied to trunk.
>>
>> Index: gcc/testsuite/gcc.dg/rtl/x86_64/dfinit.c
>> ===
On Thu, 2 Mar 2017, Uros Bizjak wrote:
> > Annoying me for quite some time, fixed as follows.
> >
> > Tested on x86_64-unknown-linux-gnu, applied to trunk.
>
> Index: gcc/testsuite/gcc.dg/rtl/x86_64/dfinit.c
> ===
> --- gcc/testsuite
On Thu, Mar 02, 2017 at 10:03:28AM +0100, Thomas Koenig wrote:
> Am 02.03.2017 um 09:43 schrieb Jakub Jelinek:
> > On Wed, Mar 01, 2017 at 10:00:08PM +0100, Thomas Koenig wrote:
> > > @@ -101,7 +93,7 @@
> > > `static void
> > > 'matmul_name` ('rtype` * const restrict retarray,
> > > 'rtype` * c
Am 02.03.2017 um 09:43 schrieb Jakub Jelinek:
On Wed, Mar 01, 2017 at 10:00:08PM +0100, Thomas Koenig wrote:
@@ -101,7 +93,7 @@
`static void
'matmul_name` ('rtype` * const restrict retarray,
'rtype` * const restrict a, 'rtype` * const restrict b, int try_blas,
- int blas_limit, b
> Annoying me for quite some time, fixed as follows.
>
> Tested on x86_64-unknown-linux-gnu, applied to trunk.
Index: gcc/testsuite/gcc.dg/rtl/x86_64/dfinit.c
===
--- gcc/testsuite/gcc.dg/rtl/x86_64/dfinit.c (revision 245830)
+++ gcc/
Hi Toma,
> As you suggested, I have added a check_gettimeofday_available proc in
> target-supports.exp and a dg-require-gettimeofday proc in
> target-supports-dg.exp
> which check for gettimeofday using the existing check_function_available proc.
that's not what I suggested (or at least meant to
On Wed, Mar 01, 2017 at 10:00:08PM +0100, Thomas Koenig wrote:
> @@ -101,7 +93,7 @@
> `static void
> 'matmul_name` ('rtype` * const restrict retarray,
> 'rtype` * const restrict a, 'rtype` * const restrict b, int try_blas,
> - int blas_limit, blas_call gemm) __attribute__((__target__("
Annoying me for quite some time, fixed as follows.
Tested on x86_64-unknown-linux-gnu, applied to trunk.
Richard.
2017-03-02 Richard Biener
* gcc.dg/rtl/x86_64/dfinit.c: Only run for lp64.
* gcc.dg/rtl/x86_64/final.c: Likewise.
* gcc.dg/rtl/x86_64/into-cfglayout.c: L
On Thu, Mar 02, 2017 at 10:09:31AM +0200, Janne Blomqvist wrote:
> > Here's something from the new matmul_r8_avx2:
> >
> > 156c: c4 62 e5 b8 fd vfmadd231pd %ymm5,%ymm3,%ymm15
> > 1571: c4 c1 79 10 04 06 vmovupd (%r14,%rax,1),%xmm0
> > 1577: c4 62 dd b8 d
On Thu, Mar 2, 2017 at 9:09 AM, Janne Blomqvist
wrote:
> On Thu, Mar 2, 2017 at 9:50 AM, Thomas Koenig wrote:
>> Am 02.03.2017 um 08:32 schrieb Janne Blomqvist:
>>>
>>> On Wed, Mar 1, 2017 at 11:00 PM, Thomas Koenig
>>> wrote:
Hello world,
the attached patch enables FMA for t
On Thu, Mar 2, 2017 at 9:50 AM, Thomas Koenig wrote:
> Am 02.03.2017 um 08:32 schrieb Janne Blomqvist:
>>
>> On Wed, Mar 1, 2017 at 11:00 PM, Thomas Koenig
>> wrote:
>>>
>>> Hello world,
>>>
>>> the attached patch enables FMA for the AVX2 and AVX512F variants of
>>> matmul. This should bring a v
On Thu, Mar 2, 2017 at 2:01 AM, Joseph Myers wrote:
> On Wed, 1 Mar 2017, Martin Sebor wrote:
>
>> Joseph, since you commented on the bug, do you have a suggestion
>> for a different site for it or a guard? The only other call to
>> the function is in the Fortran FE and it's neither guarded nor
>
On Wed, 1 Mar 2017, Jakub Jelinek wrote:
> On Wed, Mar 01, 2017 at 03:03:29PM +0100, Richard Biener wrote:
> > The patch adds better limiting to that interface and fixes one
> > false positive in fixed-value.c. Two other false positives are
> > fixed by the wide-int.h patch posted a few hours ago
69 matches
Mail list logo
