On Thu, 2 Jul 2015, Jason Merrill wrote:
On 07/02/2015 12:10 AM, Jim Wilson wrote:
This is a known gmp problem, documented in PR56019 and in
https://gcc.gnu.org/gcc-4.9/porting_to.html
near the bottom where it discusses cstddef.h changes.
This document also says that "A workaround until
On Wed, Jul 1, 2015 at 10:21 PM, Jason Merrill wrote:
> This document also says that "A workaround until libraries get updated is to
> include or before any headers from that library."
> Can you try modifying the graphite* files accordingly?
Right. I forgot to try that. Trying it now, I see t
On 07/02/2015 12:10 AM, Jim Wilson wrote:
This is a known gmp problem, documented in PR56019 and in
https://gcc.gnu.org/gcc-4.9/porting_to.html
near the bottom where it discusses cstddef.h changes.
This document also says that "A workaround until libraries get updated
is to include or b
On Thu, Jun 18, 2015 at 3:16 AM, Ilya Enkovich wrote:
> Hi,
>
> Currently return statement with no bounds in instrumented function causes
> ICE. This patch uses zero bounds in such cases instead. Bootstrapped and
> regtested for x86_64-unknown-linux-gnu. Applied to trunk. Is it OK for
> gcc
On 07/01/2015 11:26 AM, Jason Merrill wrote:
> I've been threatening to do this for a couple of months, and now that
> the regressions are under control I think it's time. This patch changes
> the default C++ dialect to C++14.
>
> Tested x86_64-pc-linux-gnu, applying to trunk.
This causes a buil
-Original Message-
From: Joseph Myers [mailto:jos...@codesourcery.com]
Sent: Wednesday, July 01, 2015 3:48 AM
To: Ajit Kumar Agarwal
Cc: l...@redhat.com; GCC Patches; Vinod Kathail; Shail Aditya Gupta; Vidhumouli
Hunsigida; Nagaraju Mekala
Subject: Re: [Patch,tree-optimization]: Add new
On 07/01/2015 10:53 AM, Steve Kargl wrote:
> The attached patch special cases unary minus/plus when
> gfotran tries to match a function keyword in a mangled
> statement. The testcase contains examples, but for
> context consider 'c = exp(-a) )' where the final ')'
> is erronous. gfortran is tryin
On 07/01/2015 02:25 PM, James Norris wrote:
> This patch allows parameter declarations to be used as
> arguments to deviceptr for C and C++.
Does this fix an existing failure? If not, can you please add a new test
case?
Thanks,
Cesar
On Wed, Jul 01, 2015 at 11:39:09PM +0200, Gerald Pfeifer wrote:
> On Wed, 1 Jul 2015, Thomas Koenig wrote:
> > I just committed the following patch to the WWW docs.
>
> Thanks. In the description, are the integers constants truncated
> or (the result of) the division?
>
The result is truncated.
On Wed, 1 Jul 2015, Thomas Koenig wrote:
> I just committed the following patch to the WWW docs.
Thanks. In the description, are the integers constants truncated
or (the result of) the division?
> An error was reported by Gerald's script, but that seems to have
> been spurious. At least, there
Hans-Peter Nilsson writes:
>> From: Richard Sandiford
>> Date: Tue, 30 Jun 2015 22:55:24 +0200
>
>> Bootstrapped & regression-tested on x86_64-linux-gnu and aarch64-linux-gnu.
>> Also tested via config-list.mk. Committed as preapproved.
>>
>> Thanks,
>> Richard
>>
>>
>> gcc/
>> * defa
Hi,
This patch allows parameter declarations to be used as
arguments to deviceptr for C and C++.
Committed to gomp-4_0-branch.
Jim
diff --git a/gcc/c/c-parser.c b/gcc/c/c-parser.c
index 88e68ae..dc244ce 100644
--- a/gcc/c/c-parser.c
+++ b/gcc/c/c-parser.c
@@ -10749,7 +10749,7 @@ c_parser_oacc_d
Hi again,
On 07/01/2015 10:54 PM, Paolo Carlini wrote:
Hi,
On 07/01/2015 10:45 PM, Andreas Schwab wrote:
Paolo Carlini writes:
@@ -972,21 +972,20 @@ ucn_valid_in_identifier (cpp_reader *pfile,
cppcha
or 0060 (`), nor one in the range D800 through DFFF inclusive.
*PSTR must be p
Hi Steve,
> The attached patch avoid the dereference of a NULL pointer,
> and thereby avoids an ICE. Regression tested on trunk.
> OK to commit?
OK.
Thanks for the patch!
Thomas
On Tue, Jun 30, 2015 at 18:10:44 +0200, Jakub Jelinek wrote:
> The thing is whether it is actually a good idea to allocate the enter data
> allocated objects together.
> In OpenMP 4.0, generally objects would be allocated and deallocated at the
> same times, except for multiple host threads trying
Hi,
On 07/01/2015 10:45 PM, Andreas Schwab wrote:
Paolo Carlini writes:
@@ -972,21 +972,20 @@ ucn_valid_in_identifier (cpp_reader *pfile, cppcha
or 0060 (`), nor one in the range D800 through DFFF inclusive.
*PSTR must be preceded by "\u" or "\U"; it is assumed that the
- buff
On Wed, 2015-07-01 at 15:52 -0500, Yaakov Selkowitz wrote:
> On Wed, 2015-07-01 at 15:46 -0500, Yaakov Selkowitz wrote:
> > On Fri, 2015-05-29 at 16:25 -0500, Yaakov Selkowitz wrote:
> > > This is the second in a series of patches to make a build with an
> > > in-tree GNU libiconv work as designed.
On Wed, 2015-07-01 at 15:46 -0500, Yaakov Selkowitz wrote:
> On Fri, 2015-05-29 at 16:25 -0500, Yaakov Selkowitz wrote:
> > This is the second in a series of patches to make a build with an
> > in-tree GNU libiconv work as designed.
> >
> > Currently GDB is the only toolchain component which actua
The attached patch avoid the dereference of a NULL pointer,
and thereby avoids an ICE. Regression tested on trunk.
OK to commit?
2015-07-01 Steven g. Kargl
PR fortran/66545
* primary.c (match_sym_complex_part): Do not dereference NULL pointer.
2015-07-01 Steven g. Kargl
On Wed, 2015-07-01 at 15:46 -0500, Yaakov Selkowitz wrote:
> On Fri, 2015-05-29 at 16:25 -0500, Yaakov Selkowitz wrote:
> > This is the second in a series of patches to make a build with an
> > in-tree GNU libiconv work as designed.
> >
> > Currently GDB is the only toolchain component which actua
On Fri, 2015-05-29 at 16:25 -0500, Yaakov Selkowitz wrote:
> This is the second in a series of patches to make a build with an
> in-tree GNU libiconv work as designed.
>
> Currently GDB is the only toolchain component which actually uses an
> in-tree libiconv. This patch modifies the common AM_IC
Paolo Carlini writes:
> @@ -972,21 +972,20 @@ ucn_valid_in_identifier (cpp_reader *pfile, cppcha
> or 0060 (`), nor one in the range D800 through DFFF inclusive.
>
> *PSTR must be preceded by "\u" or "\U"; it is assumed that the
> - buffer end is delimited by a non-hex digit. Returns
On Fri, 2015-05-29 at 16:14 -0500, Yaakov Selkowitz wrote:
> This is the first in a series of patches to make a build with an in-tree
> GNU libiconv work as designed.
>
> This patch fixes dependencies for parallel make, and avoids failures
> with make targets not supported by GNU libiconv.
Thanks
On Fri, 2015-05-29 at 16:14 -0500, Yaakov Selkowitz wrote:
> This is the first in a series of patches to make a build with an in-tree
> GNU libiconv work as designed.
>
> This patch fixes dependencies for parallel make, and avoids failures
> with make targets not supported by GNU libiconv.
Thanks
Hi,
this issue isn't a regression but it's getting a lot of attention and
duplicates. Essentially, due to the lines at the very end of _cpp_valid_ucn:
if (result == 0)
result = 1;
return result;
}
we can't possibly get the encoding of \U right in C++, that is
zero, even afte
Ping?
https://gcc.gnu.org/ml/gcc-patches/2015-06/msg00149.html
> This patch updates gthr-tpf.h to the current gthr.h API and TPF API. Ok?
>
> * gthr-tpf.h (__GTHREADS_CXX0X): Define.
> (__gthread_t): Define.
> (__gthread_cond_t): Define.
> (__gthread_time_t): Define.
>
> Ah, then approved.
Thanks, committed.
Hi,
The attached patch fixes a syntax error in one of
the OpenACC runtime tests.
Committed to gomp-4_0-branch
Jim
diff --git a/libgomp/testsuite/libgomp.oacc-fortran/if-1.f90 b/libgomp/testsuite/libgomp.oacc-fortran/if-1.f90
index 3ea9681..1729a3b 100644
--- a/libgomp/testsuite/libgomp.oacc-for
> From: Richard Sandiford
> Date: Tue, 30 Jun 2015 22:55:24 +0200
> Bootstrapped & regression-tested on x86_64-linux-gnu and aarch64-linux-gnu.
> Also tested via config-list.mk. Committed as preapproved.
>
> Thanks,
> Richard
>
>
> gcc/
> * defaults.h (HAVE_epilogue, gen_epilogue): De
On Wed, Jul 01, 2015 at 02:26:59PM -0400, Jason Merrill wrote:
> I've been threatening to do this for a couple of months, and now that the
> regressions are under control I think it's time. This patch changes the
> default C++ dialect to C++14.
Great!
It seems that our cppopts.texi is very outda
I've been threatening to do this for a couple of months, and now that
the regressions are under control I think it's time. This patch changes
the default C++ dialect to C++14.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 6f2b3941ffb3734cecc05507dd8ed46f6a6d4f2d
Author: Jason Merrill
The attached change revises the argument order of the __kernel_cmpxchg and
__kernel_cmpxchg2
calls so that they now match the argument order of the light-weight syscalls.
All callers were updated.
The clobbers and written arguments of the asms in these two functions were
reviewed and updated
t
The attached patch special cases unary minus/plus when
gfotran tries to match a function keyword in a mangled
statement. The testcase contains examples, but for
context consider 'c = exp(-a) )' where the final ')'
is erronous. gfortran is trying to match a keyword
such as 'c = exp(x=-a)' so it ex
Hi,
I've committed this patch, which rewrites the scan lines in test-case
i386/vararg-loc.c from scan-assembler to scan-rtl-dump, to fix PR66723.
Thanks,
- Tom
Use scan-rtl-dump in i386/vararg-loc.c
2015-07-01 Tom de Vries
PR testsuite/66723
* gcc.target/i386/vararg-loc.c: Use scan-rtl-
On 06/29/2015 11:36 AM, David Malcolm wrote:
On Thu, 2015-06-25 at 13:18 -0600, Jeff Law wrote:
On 06/25/2015 01:13 PM, David Malcolm wrote:
I found when implementing switch statements for the jit that it
was much easier to work with libiberty's splay-tree.h by first
wrapping it in a C++ wrappe
On 06/30/2015 01:45 AM, Richard Biener wrote:
On Mon, Jun 29, 2015 at 7:51 PM, Jeff Law wrote:
So do we want to restrict the new pattern on GENERIC, then rely on
phiopt to get smarter and catch this stuff for GIMPLE? Or drop the
pattern totally and do everything in phiopt on GIMPLE?
Note th
On 01/07/15 13:58, Richard Biener wrote:
On Wed, Jul 1, 2015 at 1:43 PM, Tom de Vries wrote:
Hi,
I.
When running test libgomp.c/appendix-a/a.29.1.c with '--target_board
unix/-O2/-g', we run into this failure:
...
FAIL: libgomp.c/appendix-a/a.29.1.c (test for excess errors)
Excess errors:
src/
It's trivial to fix the alignment of nullptr_t, but I was concerned
about ABI impact. On further research it seems that it won't cause any
trouble with argument alignment, since that doesn't seem to rely on
TYPE_ALIGN at all; I think the only ABI breakage would come from
unaligned nullptr_t fi
On 06/30/2015 10:04 AM, Alan Lawrence wrote:
Jeff Law wrote:
Thanks. Does running the phi-only propagator after the loop header
copying help? At first glance it would seem that it ought to
propagate the values of those degenerate PHIs then eliminate those PHIs.
It was written to cleanup after
On 06/30/2015 02:58 PM, Richard Sandiford wrote:
This patch uses target-insns.def to define casesi and tablejump.
It's the first point in the series at which we need access to the
instruction code, so the patch adds that to targetm as well.
Bootstrapped & regression-tested on x86_64-linux-gnu an
Hello world,
I just committed the following patch to the WWW docs.
An error was reported by Gerald's script, but that seems to
have been spurious. At least, there was no error on
revalidation.
Regards
Thomas
2015-07-01 Thomas Koenig
* gcc-6/changes.html: Document -Win
On 06/28/2015 03:08 PM, Sandra Loosemore wrote:
Re the testcase, this fixed 16 FAILs on existing tests in the gcc
testsuite with the forthcoming nios2 load/store multiple instruction
support, all assembler errors due to the bad instructions being
generated. There's nothing I can do on nios2 for
On 07/01/2015 09:25 AM, Richard Sandiford wrote:
Richard Biener writes:
On Wed, Jul 1, 2015 at 10:27 AM, Richard Sandiford
wrote:
This patch should restore bootstrap on hppa (and probably other targets
besides). The change to use target-insns.def put more stress on the
emit()/classify_insn()
Hi,
when compiling libgomp.oacc-c-c++-common/kernels-loop at -O2 -g, we run
into:
...
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/kernels-loop.c
-DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 (internal compiler error)
...
The ICE in more detail:
...
src/libgomp/testsuite/libgomp.oacc-c/..
On 7/1/15 21:52, Bernd Schmidt wrote:
> On 07/01/2015 03:04 AM, Chen Gang wrote:
>
>> For me, the more details are:
>>
>> - The insns have 2 loops which can be lsetup optimized.
>>
>> - After hwloop_optimize finishes 1st lsetup optimization, it generates
>> new lsetup insn which appends to
Richard Biener writes:
> On Wed, Jul 1, 2015 at 10:27 AM, Richard Sandiford
> wrote:
>> This patch should restore bootstrap on hppa (and probably other targets
>> besides). The change to use target-insns.def put more stress on the
>> emit()/classify_insn() group of functions, which were missing
On Tue, 2015-06-30 at 09:01 -0400, David Malcolm wrote:
> On Tue, 2015-06-30 at 08:43 +0200, Basile Starynkevitch wrote:
> > On Mon, Jun 29, 2015 at 11:44:31AM -0400, David Malcolm wrote:
> > > I've gone over the changes to the gcc/jit and gcc/testsuite/jit.dg
> > > directories in trunk since gcc 5
I've gone over the changes to the gcc/jit and gcc/testsuite/jit.dg
directories in trunk since the last backports to gcc 5 [1] and
backported the following 8 changes from trunk to the gcc-5-branch:
gcc-5-branch's r225251:
* trunk's r225203 (9bd7a189c372465fb757ecd67336379779f4ea60,
"jit: fix some
This patch "notices" the index variable of an acc loop (internally an OMP_FOR)
inside an OpenACC construct, and completes the implicit firstprivate
behavior as described in the spec. The firstprivate clauses and FIXME in
libgomp.oacc-c-c++-common/parallel-loop-2.h has also been removed together
in
"Lynn A. Boger" writes:
> It's not clear to me what distro/gcc/glibc versions and type of build
> causes the error. I have not been able to reproduce the
> original problem.
The failure mode is quite obvious: go_langhook_init_options_struct is
called before the options are parsed, so -m32 hasn'
If further testing is needed on this patch I can do it, but I need more
information what variations need to be tested?
It's not clear to me what distro/gcc/glibc versions and type of build
causes the error. I have not been able to reproduce the
original problem.
On 06/15/2015 01:58 PM, Andre
On 07/01/2015 03:04 AM, Chen Gang wrote:
For me, the more details are:
- The insns have 2 loops which can be lsetup optimized.
- After hwloop_optimize finishes 1st lsetup optimization, it generates
new lsetup insn which appends to jump insn in the basic block (which
causes the insn
On 06/30/2015 11:01 AM, Cesar Philippidis wrote:
> This patch has been applied to gomp-4_0-branch.
It was brought to my attention that I forgot to attach the patch.
Cesar
2015-06-30 Cesar Philippidis
gcc/
* omp-low.c (oacc_get_reduction_array_id): Remove.
(oacc_parallel_max_reduction_arra
I intend to commit this to trunk and the gcc-5-branch either today or
tomorrow.
I made a mistake in using "c++98" and "c++11" as the valid arguments
for the ABI configure option, because it confuses people into thinking
that it is affected by, or affects, the -std=c++11 option. In fact
the ABI m
I've just noticed that DOM doesn't handle
if (x >= y)
return 1;
if (y == x)
abort ();
in that it records y != x on the else edge but not !(y == x).
The following fixes that.
Bootstrap & regtest running on x86_64-unknown-linux-gnu.
Richard.
2015-07-01 Richard Biener
*
This merges the complete comparison patterns from the match-and-simplify
branch, leaving incomplete implementations of fold-const.c code alone.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2015-07-01 Richard Biener
* fold-const.c (fold_comparison): Move X -
Hi,
The independent clause is not available for use
with device_type clauses associated with loop
directives. This patch removes the usage.
Committed to gomp-4_0-branch
Jim
diff --git a/gcc/c/c-parser.c b/gcc/c/c-parser.c
index bcbd163..88e68ae 100644
--- a/gcc/c/c-parser.c
+++ b/gcc/c/c-parser
Tested by visual inspection of gimple dump of reproducer
supplied by bug reporter [1], and via "make check-jit"; takes jit.sum
from 8234 to 8289 passes.
Committed to trunk as r225248.
[1] https://gcc.gnu.org/ml/jit/2015-q2/msg00134.html
gcc/jit/ChangeLog:
PR jit/66700
* jit-playb
Committed to trunk as r225246.
gcc/jit/ChangeLog:
* docs/topics/types.rst (gcc_jit_context_new_union_type): Add
documentation.
* docs/_build/texinfo/libgccjit.texi: Regenerate.
gcc/testsuite/ChangeLog:
* jit.dg/test-accessing-union.c: Add comments for use by
On Wed, Jul 01, 2015 at 02:31:41PM +0200, Bernd Edlinger wrote:
> the bogus offsets-issue is now entered in bugzilla, see PR66614.
>
> It is however only a very minor issue, and does probably have
> no impact on the generated code at all.
>
>
> How should I continue with the rtx_addr_can_trap-pa
Committed to trunk as r225245.
gcc/jit/ChangeLog:
* docs/topics/contexts.rst (gcc_jit_context_set_bool_option):
Clarify lack of lifetime requirements on (const char *) parameter.
* docs/topics/expressions.rst
(gcc_jit_context_new_string_literal): Likewise.
(
Hi,
the bogus offsets-issue is now entered in bugzilla, see PR66614.
It is however only a very minor issue, and does probably have
no impact on the generated code at all.
How should I continue with the rtx_addr_can_trap-patch?
Is it OK to commit?
Thanks
Bernd.
-
On 01/07/15 13:25 +0100, Jonathan Wakely wrote:
On 01/07/15 13:23 +0100, Jonathan Wakely wrote:
This adds the "detection idiom" API from N4502
http://open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4502.pdf
I've added the low-level parts to , with public aliases
in , so that I can use them elsew
On 01/07/15 13:23 +0100, Jonathan Wakely wrote:
This adds the "detection idiom" API from N4502
http://open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4502.pdf
I've added the low-level parts to , with public aliases
in , so that I can use them elsewhere in the
library.
For example this uses the
Hello!
We have to enable OS extensions (GNU_SOURCE) to use asprintf.
2015-07-01 Uros Bizjak
* configure.ac: Add AC_USE_SYSTEM_EXTENSIONS.
* configure: Regenerate.
* config.h.in: Ditto.
Bootstrapped on x86_64-linux-gnu.
OK for mainline?
Uros.
Index: configure.ac
===
This adds the "detection idiom" API from N4502
http://open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4502.pdf
I've added the low-level parts to , with public aliases
in , so that I can use them elsewhere in the
library.
Tested powerpc64le-linux, committed to trunk.
commit 280016fc93e2c62e1c07f25
Normally, with PIE, GCC accesses globals that are extern to the module
using GOT. This is two instructions, one to get the address of the global
from GOT and the other to get the value. Examples:
---
extern int a_glob;
int
main ()
{
return a_glob;
}
---
With PIE, the generated code accesses g
On Wed, Jul 1, 2015 at 12:32 PM, Matthew Wahab
wrote:
> Hello,
>
> Tests I recently added for the code generated by the ARM backend for the
> __sync
> builtins had
>
> - 'do-require-effective-target', instead of the directive
> 'dg-require-effective-target' and
> - 'stlex' instead of 'strex' in
On Wed, Jul 1, 2015 at 1:43 PM, Tom de Vries wrote:
> Hi,
>
> I.
>
> When running test libgomp.c/appendix-a/a.29.1.c with '--target_board
> unix/-O2/-g', we run into this failure:
> ...
> FAIL: libgomp.c/appendix-a/a.29.1.c (test for excess errors)
> Excess errors:
> src/libgomp/testsuite/libgomp.
Hi,
I.
When running test libgomp.c/appendix-a/a.29.1.c with '--target_board
unix/-O2/-g', we run into this failure:
...
FAIL: libgomp.c/appendix-a/a.29.1.c (test for excess errors)
Excess errors:
src/libgomp/testsuite/libgomp.c/appendix-a/a.29.1.c:6:1: error: type
mismatch between an SSA_NAME
On 01/07/15 12:22 +0200, Uros Bizjak wrote:
Hello!
2015-07-01 Uros Bizjak
* libsupc++/guard.cc (__test_and_acquire): Use __p after __atomic_load
to avoid unused variable warning.
(__set_and_release): Use __p after __atomic_store to avoid unused
variable warning.
Bootstrapped and
Hi Guys,
I am applying the patch below to fix a problem with the MSP430's
zero_extendhipsi2 pattern. When the destination is memory, four bytes
must be written, even though only a 20-bit value is being stored, as
otherwise the top nibble will be lost.
Cheers
Nick
gcc/ChangeLog
2015-07
Hello,
Tests I recently added for the code generated by the ARM backend for the __sync
builtins had
- 'do-require-effective-target', instead of the directive
'dg-require-effective-target' and
- 'stlex' instead of 'strex' in the expected output for armv8-sync-op-acquire.c
This meant the tests
On Wed, Jul 1, 2015 at 1:24 PM, Richard Biener
wrote:
> On Mon, Jun 29, 2015 at 3:41 PM, Jason Merrill wrote:
>> On 06/27/2015 08:14 PM, Ed Smith-Rowland wrote:
>>>
>>> In c-ada-specs.c/print_ada_macros() I just write these as a char
>>> constant rather than spelling the token.
>>> We could do th
On Wed, Jul 01, 2015 at 10:59:15AM +0100, Richard Sandiford wrote:
> Trevor Saunders writes:
> > On Tue, Jun 16, 2015 at 09:45:56AM +0100, Richard Sandiford wrote:
> >> I couldn't tell whether the unusual name of the function
> >> ("gt_cleare_cache") is deliberate or not, but I left it be.
> >
> >
On Mon, Jun 29, 2015 at 3:41 PM, Jason Merrill wrote:
> On 06/27/2015 08:14 PM, Ed Smith-Rowland wrote:
>>
>> In c-ada-specs.c/print_ada_macros() I just write these as a char
>> constant rather than spelling the token.
>> We could do the latter. You'd see the "u8" then I think. I couldn't
>> fin
Hi,
testcase libgomp.oacc-c-c++-common/lib-3.c is supposed to fail.
It fails currently in two ways:
- no device found, if there is no nonhost device type supported, so
just host and host_nonshm
- no device initialized, if there is a nonhost device type supported,
f.i. nvidia
The reason for
Hi,
I noticed on gomp-4_0-branch that lib-62.c was failing with a sigsegv:
...
Program received signal SIGSEGV, Segmentation fault.
acc_init_1 (d=acc_device_nvidia) at src/libgomp/oacc-init.c:179
179 ndevs = base_dev->get_num_devices_func ();
(gdb) p base_dev
$1 = (struct gomp_device_descr
Hi!
I've committed following patch, which per the new ABI additions
mangles and handles the various new linear clause modifiers in
declare simd functions. The vectorizer side is not done yet,
for now we'll never use SIMD_CLONE_ARG_TYPE_LINEAR_*_CONSTANT_STEP
in vectorized routines, that waits fir
This adds a #pragma scalar_storage_order directive to the C family of
languages that makes it possible to specify a default SSO.
Tested on x86_64-suse-linux. applied on the branch.
* doc/extend.texi (Structure-Packing Pragmas): Rename into...
( Structure-Layout Pragmas): ...this
Hello!
2015-07-01 Uros Bizjak
* libsupc++/guard.cc (__test_and_acquire): Use __p after __atomic_load
to avoid unused variable warning.
(__set_and_release): Use __p after __atomic_store to avoid unused
variable warning.
Bootstrapped and regression tested on x86_64-linux-gnu.
O
Richard Sandiford writes:
> Richard Biener writes:
>> On Wed, Jul 1, 2015 at 11:39 AM, Trevor Saunders
>> wrote:
>>> On Tue, Jun 23, 2015 at 07:41:42PM +0100, Richard Sandiford wrote:
[A fair bit later than promised, sorry...]
Mikhail posted a patch to make genflags generate the d
Richard Biener writes:
> On Wed, Jul 1, 2015 at 11:39 AM, Trevor Saunders
> wrote:
>> On Tue, Jun 23, 2015 at 07:41:42PM +0100, Richard Sandiford wrote:
>>> [A fair bit later than promised, sorry...]
>>>
>>> Mikhail posted a patch to make genflags generate the default HAVE_foo
>>> and gen_foo de
On 19/06/15 09:50, Thomas Schwinge wrote:
Hi!
On Tue, 5 May 2015 16:09:18 +0200, I wrote:
I don't know why libgomp.oacc-c-c++-common/lib-62.c contains this
explicit acc_init call with acc_device_nvidia -- generally, the test
cases should not contain such unconditional statements. So, let's the
Hello!
This patch avoids "enum conversion when passing argument 1 of
‘getrusage’ is invalid in C++" warning when compiling getruntime.c.
The condition is copied from sys/resource.h.
2015-07-01 Uros Bizjak
* getruntime.c (get_run_time) [__USE_GNU]: Use RUSAGE_SELF as
argument 1 of getr
Trevor Saunders writes:
> On Tue, Jun 16, 2015 at 09:45:56AM +0100, Richard Sandiford wrote:
>> I couldn't tell whether the unusual name of the function
>> ("gt_cleare_cache") is deliberate or not, but I left it be.
>
> I'm not sure what's particularly unusual about it?
"cleare" rather than "clea
On Wed, Jul 1, 2015 at 11:39 AM, Trevor Saunders wrote:
> On Tue, Jun 23, 2015 at 07:41:42PM +0100, Richard Sandiford wrote:
>> [A fair bit later than promised, sorry...]
>>
>> Mikhail posted a patch to make genflags generate the default HAVE_foo
>> and gen_foo definitions that have recently been
On Tue, Jun 16, 2015 at 09:45:56AM +0100, Richard Sandiford wrote:
> As described in the covering note, this patch replaces handle_cache_entry
> with a new function keep_cache_entry. It also ensures that elements are
> deleted using the proper function, so that m_n_deleted is updated.
Thanks for
On Tue, Jun 23, 2015 at 07:41:42PM +0100, Richard Sandiford wrote:
> [A fair bit later than promised, sorry...]
>
> Mikhail posted a patch to make genflags generate the default HAVE_foo
> and gen_foo definitions that have recently been added to defaults.h:
>
> https://gcc.gnu.org/ml/gcc-patches
committed as 225233.
2015-07-01 Jiong Wang
gcc/
* doc/sourcebuild.texi (AArch64-specific attributes): Document
"aarch64_tiny", "aarch64_small", "aarch64_large",
"aarch64_little_endian", "aarch64_big_endian".
Index: gcc/ChangeLog
==
James Greenhalgh writes:
> On Tue, Jun 30, 2015 at 03:17:00PM +0100, Jiong Wang wrote:
>>
>> As discussed here
>>
>> https://gcc.gnu.org/ml/gcc-patches/2015-06/msg02151.html,
>>
>> Since have enabled binutils feature detection when configuring gcc,
>> -fpic will not be enabled if there is no
James Greenhalgh writes:
> On Mon, Jun 29, 2015 at 01:42:13PM +0100, Jiong Wang wrote:
>>
>> This patch fix the breakage caused by
>>
>> https://gcc.gnu.org/ml/gcc-patches/2015-06/msg01913.html
>>
>> We fall back to -fPIC if there is no assembler support on those new
>> relocation modifiers
On Tue, Jun 30, 2015 at 03:17:00PM +0100, Jiong Wang wrote:
>
> As discussed here
>
> https://gcc.gnu.org/ml/gcc-patches/2015-06/msg02151.html,
>
> Since have enabled binutils feature detection when configuring gcc,
> -fpic will not be enabled if there is no binutils support on those new
> rel
On Wed, Jul 1, 2015 at 10:27 AM, Richard Sandiford
wrote:
> This patch should restore bootstrap on hppa (and probably other targets
> besides). The change to use target-insns.def put more stress on the
> emit()/classify_insn() group of functions, which were missing a case
> for parallel returns.
On Mon, Jun 29, 2015 at 01:42:13PM +0100, Jiong Wang wrote:
>
> This patch fix the breakage caused by
>
> https://gcc.gnu.org/ml/gcc-patches/2015-06/msg01913.html
>
> We fall back to -fPIC if there is no assembler support on those new
> relocation modifiers for -fpic.
>
> OK for trunk?
>
> g
This patch should restore bootstrap on hppa (and probably other targets
besides). The change to use target-insns.def put more stress on the
emit()/classify_insn() group of functions, which were missing a case
for parallel returns.
Tested with a cross-compiler that it fixes the hppa problem. Boot
On Wed, Jul 01, 2015 at 09:52:04AM +0200, Eric Botcazou wrote:
> Jakub,
>
> > 2015-06-29 Eric Botcazou
> >
> > PR middle-end/66633
> > * tree-nested.c (convert_nonlocal_omp_clauses): Initialize need_chain
> > to true if the function is nested and if not optimizing.
> > (convert
Jakub,
> 2015-06-29 Eric Botcazou
>
> PR middle-end/66633
> * tree-nested.c (convert_nonlocal_omp_clauses): Initialize need_chain
> to true if the function is nested and if not optimizing.
> (convert_local_omp_clauses): Initialize need_frame to true if the
> funct
> Given there is no PR to track this I'll count on you remembering to
> backport it then ;)
OK.
> If you'd want it in 5.2 then you'd need to backport it by this Friday
> morning.
No thanks. :-)
--
Eric Botcazou
On Tue, Jun 30, 2015 at 11:03 PM, Eric Botcazou wrote:
>> Ok (I suppose this also affects the GCC 5 branch?)
>
> Thanks. Yes, it does, but I'm not sure if we need to backport it immediately.
Given there is no PR to track this I'll count on you remembering to
backport it then ;)
If you'd want it
1 - 100 of 102 matches
Mail list logo
