On Fri, Mar 18, 2016 at 10:44 AM, Kirill Yukhin wrote:
> Hello,
> Intel spec [1] states that there're almost all broadcasting
> intructions variants available, except for (p. 2-4)
> vbroadcastsd %xmm, %xmm
> It is safe to emit
> vpbroadcastq %xmm, %xmm
> instead.
>
> I was uable to
On Fri, Mar 18, 2016 at 4:33 PM, Uros Bizjak wrote:
> On Mon, Mar 7, 2016 at 2:34 PM, Marek Polacek wrote:
>> On Fri, Mar 04, 2016 at 07:17:46PM +0100, Uros Bizjak wrote:
>>> Hello!
>>>
>>> > This is not a regression but I thought I'd post this anyway. Martin
>>> > reported
>>> > that we genera
This patch adds support for two new Power9 instructions, xxpermr and
vpermr, providing more efficient vector permutation operations on
little-endian configurations. These new instructions are described in
the Power ISA 3.0 document. Selection of the new instructions is
conditioned upon TARGET_
On Wed, 16 Mar 2016, H.J. Lu wrote:
> On Wed, Mar 16, 2016 at 9:41 AM, H.J. Lu wrote:
> > On Wed, Mar 16, 2016 at 9:35 AM, Tom de Vries
> > wrote:
> >> On 16/03/16 17:15, H.J. Lu wrote:
> >>>
> >>> On Wed, Mar 16, 2016 at 9:12 AM, H.J. Lu wrote:
> >>
> >>
> Any particular reason why this
On 03/14/2016 07:08 PM, Trevor Saunders wrote:
To work around the narrow API in the comparison function we have to either
store additional data in each node or have them available in globals. The
former would be horribly wasteful, the latter is just ugly. I choose the
latter in the lazy evalua
The following fixes excessive compile-time and memory-usage needed to
build the testcases which is caused by severe mis-calculation of
size-after-unrolling because it simply assumes that conditionals
with is_gimple_min_invariant ops can be folded to a constant.
This is not always true, like for
On 02/03/16 13:46, Evandro Menezes wrote:
On 01/08/16 16:55, Evandro Menezes wrote:
On 12/16/2015 02:11 PM, Evandro Menezes wrote:
On 12/16/2015 05:24 AM, Richard Earnshaw (lists) wrote:
On 15/12/15 23:34, Evandro Menezes wrote:
On 12/14/2015 05:26 AM, James Greenhalgh wrote:
On Thu, Dec 03,
On Wed, Mar 16, 2016 at 02:47:09PM -0400, Jason Merrill wrote:
> The constructor for an empty class can't do the -flifetime-dse clobber
> because when the class is used as a base it might be assigned the same
> offset as a real base, so the clobber would mess with real data.
Isn't this needed also
On 03/18/2016 01:16 PM, Bernd Schmidt wrote:
On 03/18/2016 08:14 PM, Jeff Law wrote:
I also added a blurb to the dump file when we create these equivalences
and included a test to verify the code fires. I verified it fired on
x86 and x86-64. It may or may not fire on other targets, so I left t
On Thu, 2016-03-17 at 12:16 +0100, Jakub Jelinek wrote:
> Thus, I've reverted the patch (kept the testcase), and after some
> discussions on IRC bootstrapped/regtested on x86_64-linux and i686
> -linux following version, which right now should change behavior just
> for the i?86 case and nothing
Hi!
I'd like to ping 2 patches, one mine:
P2 PR70001 http://gcc.gnu.org/ml/gcc-patches/2016-03/msg00710.html
and one from Alex, which hasn't been pinged for quite a while, but is P1:
P1 PR69315 https://gcc.gnu.org/ml/gcc-patches/2016-01/msg02010.html
Thanks.
Jakub
On 03/18/16 17:20, Wilco Dijkstra wrote:
Evandro Menezes wrote:
On 03/18/16 10:21, Wilco Dijkstra wrote:
Hi Evandro,
For example, though this approximation is improves the performance
noticeably for DF on A57, for SF, not so much, if at all.
I'm still skeptical that you ever can get any gai
Hello,
I have committed the following patches to amonakov/gomp-nvptx branch to fix a
few bugs uncovered in recent testing (including testing on a 32-bit ARM
platform). Patch 1 fixes an odd mispaste in bar.c, patches 2,5,6,7 address
32-bit portability issues, patch 3 works around a deadlock on err
Evandro Menezes wrote:
> On 03/18/16 10:21, Wilco Dijkstra wrote:
> > Hi Evandro,
> >
> >> For example, though this approximation is improves the performance
> >> noticeably for DF on A57, for SF, not so much, if at all.
> > I'm still skeptical that you ever can get any gain on scalars. I bet the
On Wed, Mar 16, 2016 at 10:02 AM, H.J. Lu wrote:
> On Wed, Mar 16, 2016 at 9:58 AM, Jason Merrill wrote:
>> On 03/16/2016 08:38 AM, H.J. Lu wrote:
>>>
>>> FAIL: g++.dg/abi/pr60336-1.C scan-assembler jmp[\t
>>> ]+[^$]*?_Z3xxx9true_type
>>> FAIL: g++.dg/abi/pr60336-5.C scan-assembler jmp[\t
>>>
On Fri, Mar 18, 2016 at 11:14 AM, Jason Merrill wrote:
> On 03/10/2016 05:58 PM, Patrick Palka wrote:
>>
>> This patch reverses the behavior of process_outer_var_ref, so that we
>> always implicitly capture a const variable if it's capturable, instead
>> of always trying to first fold it to a cons
gcc.target/i386/pr61599-1.c currently FAILs on 64-bit Solaris/x86 with
the native assembler:
FAIL: gcc.target/i386/pr61599-1.c (test for excess errors)
WARNING: gcc.target/i386/pr61599-1.c compilation failed to produce executable
Assembler: pr61599-1.c
"pr61599-1.s", line 2 : Illegal mnem
* config/nvptx/bar.c: Remove wrong invocation of
gomp_barrier_wait_end from gomp_team_barrier_wait_end.
---
libgomp/ChangeLog.gomp-nvptx | 5 +
libgomp/config/nvptx/bar.c | 2 --
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/libgomp/config/nvptx/bar.c b/libgo
On Wed, Mar 16, 2016 at 10:47 PM, H.J. Lu wrote:
> Since PIE implies PIC, we should set flag_pic to flag_pie for PIE in
> LTO.
>
> Tested on x86-64. OK for trunk?
Ok. I wonder if we need to do sth to flag_shlib here as well?
Richard.
> H.J.
> ---
> PR lto/70258
> * lto-lang.c
On 09/06/15 14:07, James Greenhalgh wrote:
>
> Hi,
>
> g++.dg/ext/pr57735.C is failing for test runs which explicitly pass
> -mfloat-abi=hard. Looking at the test, it seems the best fix would be
> to check before adding -mfloat-abi=soft that we are not testing some other
> float-abi. We also fail
* config/nvptx/crt0.c (__nvptx_stacks): Define in C. Use it...
(__nvptx_uni): Ditto.
(__main): ...here instead of inline asm.
* config/nvptx/stacks.c (__nvptx_stacks): Define in C.
(__nvptx_uni): Ditto.
---
libgcc/ChangeLog.gomp-nvptx | 8
libgcc
Discussion of empty class parameter passing ABI led me to notice that
r162402 broke sibcalls with arguments of size 0 in some cases. Before
that commit, the code read
else if ((partial == 0 || args[i].pass_on_stack)
&& size != 0)
{
rtx mem = validize_mem (args[i].value);
/* Chec
On 03/17/2016 06:23 AM, David Wohlferd wrote:
On 3/14/2016 8:28 AM, Bernd Schmidt wrote:
The example is not good, as discussed previously, and IMO the best
option is to remove it. Otherwise I have no objections to the latest
variant.
Despite the problems I have with the existing sample, adding
On Fri, 18 Mar 2016, Kirill Yukhin wrote:
> Hello,
> Intel spec [1] states that there're almost all broadcasting
> intructions variants available, except for (p. 2-4)
> vbroadcastsd %xmm, %xmm
> It is safe to emit
> vpbroadcastq %xmm, %xmm
> instead.
>
> I was uable to extract a testc
On 03/17/2016 06:23 AM, David Wohlferd wrote:
2016-03-16 David Wohlferd
Bernd Schmidt
* doc/extend.texi: Doc basic asm behavior re clobbers.
Any objections from the release managers if I install this for David at
this stage?
Bernd
On 03/15/2016 04:31 PM, Richard Henderson wrote:
On 03/10/2016 08:20 PM, DJ Delorie wrote:
I'm moving on to Plan C but I put a copy of the file on
.../dj/foo.c.gz (195Mb) if anyone wants to find out
why there's a 16Gb limit compiling it...
With just the following, we successfully compile your
@@ -3974,6 +3974,38 @@ build_vec_cmp (tree_code code, tree type,
return build3 (VEC_COND_EXPR, type, cmp, minus_one_vec, zero_vec);
}
+/* Possibly warn about an address never being NULL. */
+
+static void
+warn_for_null_address (location_t location, tree op, tsubst_flags_t complain)
+{
..
On 03/10/16 19:06, Wilco Dijkstra wrote:
Evandro Menezes wrote:
That's what I had in mind too, but around the approximation for x^-1/2
and using masks for vector cases thusly:
fcmne v3.4s, v0.4s, #0.0
frsqrte v1.4s, v0.4s
fmulv2.4s, v1.4s, v1.4s
frsqrts
On 16/03/16 12:34, Richard Biener wrote:
On Wed, Mar 16, 2016 at 11:57 AM, Tom de Vries wrote:
Hi,
Atm, using fdump-tree-all-graph produces invalid dot files:
...
$ rm *.c.* ; gcc test.c -O2 -S -fdump-tree-all-graph
$ for f in *.dot; do dot -Tpdf $f -o dot.pdf; done
Warning: test.c.006t.omplow
Changed in V3:
- Rebase to latest master (efc86c4c627b82364f118a29b5d9d58cad8b8c76)
- Fix bad formatting (missing space before '(').
- Use of @code{} around literal source code text.
//Hongxu
>From 7fe014845596f547d735324c466799d8207d282d Mon Sep 17 00:00:00 2001
From: Hongxu Jia
Date: Wed,
Tweak the pipeline model for Exynos M1
* gcc/config/aarch64/aarch64.c
(exynosm1_tunings): Enable the weak prefetching model.
Committed as r234307.
--
Evandro Menezes
>From a75d875a3c64180c9d6c368e2d87036d70f66036 Mon Sep 17 00:00:00 2001
From: evandro
Date: Thu
The attach patch fixes a problem causing block/blk-merge.c in the linux kernel
to be miscompiled. As a result,
block segments were not properly split and boot failed since linux 4.3.
The problem was found by a regression search. The patch reverts a change in
the handling of the Q and T
constra
On 03/17/2016 03:35 PM, Jakub Jelinek wrote:
_Jv_AllocObject returns a pointer, and as the testcase below shows,
we easily ICE if a wrong prototype is provided for it instead.
There is already other diagnostics (e.g. when it is missing, or when
it is overloaded function), so this ensures at least
On Thu, Mar 17, 2016 at 12:27 PM, Jeff Law wrote:
> On 03/16/2016 06:43 PM, Martin Sebor wrote:
>>>
>>> @@ -3974,6 +3974,38 @@ build_vec_cmp (tree_code code, tree type,
>>> return build3 (VEC_COND_EXPR, type, cmp, minus_one_vec, zero_vec);
>>> }
>>>
>>> +/* Possibly warn about an address nev
On Wed, Mar 16, 2016 at 10:59 AM, Bin Cheng wrote:
> Hi,
> One issue revealed in tree ifcvt is the pass stores/tracks DRs against its
> memory references in IR. This causes difficulty in identifying same memory
> references appearing in different forms. Given below example:
>
> void foo (int a
Jeff Law writes:
> PR rtl-optimization/70024
That's probably a typo.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
On Thu, Mar 17, 2016 at 03:34:09PM +0100, Thomas Schwinge wrote:
> That's simple enouch; OK to commit? (I'm also including the related
> change, to rename the Fortran OMP_MAP_FORCE_DEALLOC to OMP_MAP_DELETE,
> because I think that's what you'd do, once starting the OpenMP 4.5
> Fortran front end w
Hi,
This trivial patch skips gcc.c-torture/compile/20151204.c for the avr
target - the test allocates ~64K on the stack, which is too big
for the avr target. Right now, the test errors out with "total
size of local objects too large".
If this is ok, could someone commit please? I don't have
On Thu, Mar 17, 2016 at 8:55 AM, Bernd Schmidt wrote:
> On 03/17/2016 04:26 PM, H.J. Lu wrote:
>>
>> On Thu, Mar 17, 2016 at 8:23 AM, Bernd Schmidt
>> wrote:
>>>
>>> On 03/17/2016 04:13 PM, H.J. Lu wrote:
We can add an effective target, something like ignore_pic_pie, and
use it ins
On 03/18/16 10:21, Wilco Dijkstra wrote:
Hi Evandro,
For example, though this approximation is improves the performance
noticeably for DF on A57, for SF, not so much, if at all.
I'm still skeptical that you ever can get any gain on scalars. I bet the only
gain is on
4x vectorized floats.
I
On Tue, Mar 15, 2016 at 03:41:52PM -0400, Jason Merrill wrote:
> Let's factor out that duplicated code into a separate function.
Sure. It also allowed me to hoist the cheap tests for both warnings, and
while at it, I used 'location' for the first warning.
Bootstrapped/regtested on x86_64-linux,
41 matches
Mail list logo
