On Sun, Jan 10, 2016 at 11:32 PM, H.J. Lu wrote:
> Since *mov_internal and _(load|store)_mask patterns
> can handle unaligned load and store, we can remove UNSPEC_LOADU and
> UNSPEC_STOREU. We use function prototypes with pointer to scalar for
> unaligned load/store builtin functions so that memo
On 08/01/16 14:13, Andrew Burgess wrote:
* config/arc/arc.opt (mdiv-rem): Add period to the end.
(mcode-density): Likewise.
Thanks, I have applied this patch.
On 01/05/2016 08:47 AM, James Norris wrote:
Hi!
I've updated the original patch after some very helpful
comments from Sandra (thank you, thank you).
OK to commit to trunk?
I'm assuming this is now waiting for technical review? I can give it
another read-through for tech-writing issues but I
On Mon, Jan 4, 2016 at 1:35 PM, Jeff Law wrote:
> On 01/02/2016 04:26 PM, Patrick Palka wrote:
>>
>> On Sat, Jan 2, 2016 at 3:21 AM, Jakub Jelinek wrote:
>>>
>>> On Fri, Jan 01, 2016 at 10:06:34PM -0700, Jeff Law wrote:
>
> gcc/cp/ChangeLog:
>
> * cp-array-notation.c (cp_expa
On Thu, Dec 31, 2015 at 10:40 AM, Patrick Palka wrote:
> This patch makes it so that a gimplification failure is considered to be
> an internal error under normal circumstances, so that we otherwise avoid
> silently generating wrong code if e.g. a buggy frontend fed us a
> malformed tree.
>
> The
On Mon, Dec 21, 2015 at 6:07 PM, Patrick Palka wrote:
> We are currently failing to fold equality comparisons involving
> PTRMEM_CSTs since (I think) r229018 thus making this a GCC 6 regression.
> This regression shows up in the boost testsuite.
>
> Fixed in a straightforward way. OK to commit af
On Sun, Dec 27, 2015 at 12:14 PM, Patrick Palka wrote:
> In try_one_overload(), it should not be a deduction failure if we
> deduced more arguments of an argument pack than were explicitly
> specified (as long as the arguments are otherwise equivalent).
>
> This patch makes try_one_overload() manu
On Sun, Jan 3, 2016 at 3:14 PM, Martin Sebor wrote:
> On 12/31/2015 08:40 AM, Patrick Palka wrote:
>>
>> If we do create such an initializer, we end up with an error_mark_node
>> during gimplification, because in cp-gimplify.c we pass this
>> VEC_INIT_EXPR of the flexible array member to build_vec
I am about to start a project to incrementally move chunks of
invoke.texi around to better organize this very long chapter of the
manual. For reference, the current top-level structure looks like this:
@chapter GCC Command Options
@section Option Summary
@section Options Controlling the Kind o
On Sun, 2016-01-10 at 19:28 +, Bernd Edlinger wrote:
> Hi Peter,
>
> > @@ -4167,6 +4167,7 @@
> > -d "/opt/$with_advance_toolchain/bin/." -a \
> > -d "/opt/$with_advance_toolchain/include/.";
> > then
> >
> > + target_header_dir=`find
>
Since *mov_internal and _(load|store)_mask patterns
can handle unaligned load and store, we can remove UNSPEC_LOADU and
UNSPEC_STOREU. We use function prototypes with pointer to scalar for
unaligned load/store builtin functions so that memory passed to
*mov_internal is unaligned.
Tested on x86-64
This patch removes snprintf from _(load|store)_mask
patterns. Tested on x86-64. OK for trunk?
H.J.
---
* config/i386/sse.md (_load_mask): Remove
snprintf.
(_store_mask): Likewise.
---
gcc/config/i386/sse.md | 52 --
1 file
Hi Peter,
> @@ -4167,6 +4167,7 @@
> -d "/opt/$with_advance_toolchain/bin/." -a \
> -d "/opt/$with_advance_toolchain/include/."; then
>
>+ target_header_dir=`find /opt/$with_advance_toolchain/
>-path '*/include/features.h' | sed -e
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 Chinese (simplified) team of translators. The file is available at:
http://translationproject.org/latest/gcc/zh_CN.po
(This file, 'gcc-5.2.0.
While testing a configure fragment change for an upcoming patch, I noticed
that --with-advance-toolchain=... wasn't correctly setting $target_header_dir
to point to the Advance Toolchain's headers and instead was pointing at
the system headers. This patch arranges for configure.ac to allow
config.
Hi,
when compiling the testcase in the patch (reduced from ira-color.c) with
-O2 -ftree-parallelize-loops=2, we run into an ICE:
...
prephitmp_39 = PHI <_40(16), &conflicting_regs(7)>
ira-color.c:69:8: internal compiler error: verify_gimple failed
...
The variable conflicting_regs is a local a
Hi,
In the GCC Internals documentation the loop depth is documented
incorrectly. From git commit 9e3536f4f it is accessed through a
function, not a field.
Please install this patch to reflect this.
Best,
Nicklas
2017-01-10 Nicklas Bo Jensen
* doc/loop.texi (Loop Analysis and Repres
Hi!
Committed to gomp-4_0-branch in r232198:
commit bec521e294ddf37d52860bfa0724a5e6a2bc2225
Merge: 1d481a9 0f8f48d
Author: tschwinge
Date: Sun Jan 10 12:27:25 2016 +
svn merge -r 231690:232189 svn+ssh://gcc.gnu.org/svn/gcc/trunk
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc
Dear All,
The patch applies cleanly to 5-branch and fixes the problem. I will
commit it later on today, at the same time as the first batch of
deferred character fixes unless there are any objections.
Cheers
Paul
On 10 January 2016 at 14:02, Paul Richard Thomas
wrote:
> Dear All,
>
> I had alr
Dear All,
I had already posted a patch for the above, which sets the offset
correctly in the caller to gfc_conv_expr_descriptor. However, I was so
concerned that the latter was not doing the job properly that I
decided to investigate further. The result was that I found a
completely trivial omissi
Hi Thomas,
Thanks for changing the testcase to demonstrate that in_where does not
get left as true.
OK for trunk.
That's one regression down!
Thanks for the patch
Paul
On 10 January 2016 at 13:38, Thomas Koenig wrote:
> Am 10.01.2016 um 12:55 schrieb Thomas Koenig:
>>
>> Hello world,
>>
>> t
Am 10.01.2016 um 12:55 schrieb Thomas Koenig:
Hello world,
the attached patch fixes the regression. Before this, front-end
optimization would have tried to put a DO loop inside a WHERE construct,
leading to an ICE.
The updated test case demonstrates that matmul inlining is done even
after not
Hi,
Consider this test-case (reduced from ira-color.c):
...
unsigned int b;
unsigned int
fn1 (unsigned int d)
{
int i;
for (i = 0; i < 1000; i++)
b |= d;
return b;
}
...
When compiling with -O2 -ftree-parallelize-loops=2, we run into a segfault.
Before parloops, we have reduction
Hi!
On Fri, 8 Jan 2016 11:30:16 +, Alan Lawrence wrote:
> Here's an alternative patch, [...]
> +/* { dg-final { scan-tree-dump "note: Built SLP cancelled: can use
> load/store-lanes" { target { vect_perm && vect_load_lanes } } } } */
For all these, you're missing to provide the "suffix" i
Hello world,
the attached patch fixes the regression. Before this, front-end
optimization would have tried to put a DO loop inside a WHERE construct,
leading to an ICE.
Regression-tested. OK for trunk?
Thomas
2016-01-10 Thomas Koenig
PR fortran/69154
* frontend-pas
25 matches
Mail list logo