Could someone with write access please commit the patch?
The paperwork with the FSF has gone through. If something else is missing,
please tell me.
I won't be available next week.
Best regards,
Jan
Am Tuesday 24 November 2015, 08:47:49 schrieb Jan Sommer:
> It has gone through.
> That was
On 11/27/2015 10:02 AM, Bernd Schmidt wrote:
This is a patch for PRs 68471 and 68472, which show problems with the
ROP mitigation:
* reg-stack doesn't call df_insn_update when it makes changes, and
if df checking is enabled, any subsequent df_analyze call will
abort
* Using
On Mon, Nov 30, 2015 at 10:38 PM, Bernd Schmidt wrote:
> On 11/27/2015 10:02 AM, Bernd Schmidt wrote:
>>
>> This is a patch for PRs 68471 and 68472, which show problems with the
>> ROP mitigation:
>> * reg-stack doesn't call df_insn_update when it makes changes, and
>>
On Fri, 27 Nov 2015, Alan Lawrence wrote:
> On 27/11/15 15:07, Alan Lawrence wrote:
> > On 23/11/15 09:43, Richard Biener wrote:
> > > On Fri, 20 Nov 2015, Alan Lawrence wrote:
> > >
> > > > ...the asserts
> > > > you suggested in
> > > >
On Sat, Nov 28, 2015 at 6:50 AM, Bin.Cheng wrote:
> On Fri, Nov 27, 2015 at 8:51 PM, Richard Biener
> wrote:
>> On Fri, Nov 27, 2015 at 12:44 PM, Bin Cheng wrote:
>>> Hi,
>>> This patch is to fix PR68529. In my previous
Hi,
this patch fixes PR46032.
It handles a call:
...
__builtin_GOMP_parallel (fn, data, num_threads, flags)
...
as:
...
fn (data)
...
in ipa-pta.
This improves ipa-pta alias analysis in the parallelized function fn,
and allows vectorization in the testcase without a runtime alias test.
On 11/29/2015 08:32 PM, Andreas Tobler wrote:
Hi all,
the attached patch prepares the testsuite, c and c++, for the upcoming
ASAN support for FreeBSD (x86_64 first).
I tested the patch on CentOS7.1 x86_64 and on FreeBSD x86_64.
Results can be seen on the list.
Is this ok for trunk?
-/* {
On Mon, Nov 30, 2015 at 05:17:29PM +0100, Bernd Schmidt wrote:
> On 11/30/2015 01:12 PM, Andreas Tobler wrote:
> >On 30.11.15 11:28, Bernd Schmidt wrote:
> >>On 11/29/2015 08:32 PM, Andreas Tobler wrote:
> >>>-/* { dg-do run { target { *-*-linux* } } } */
> >>>+/* { dg-do run { target { *-*-linux*
On 11/30/2015 01:12 PM, Andreas Tobler wrote:
On 30.11.15 11:28, Bernd Schmidt wrote:
On 11/29/2015 08:32 PM, Andreas Tobler wrote:
-/* { dg-do run { target { *-*-linux* } } } */
+/* { dg-do run { target { *-*-linux* *-*-freebsd* } } } */
I see a patch from you to add asan support to x86
Ping. This patch is stalling for two weeks.
Thanks,
Claudiu
On Mon, Nov 16, 2015 at 11:18 AM, Claudiu Zissulescu
wrote:
> This patch adds support for atomic memory built-in for ARCHS and ARC700.
> Tested with dg.exp.
>
> OK to apply?
>
> Thanks,
> Claudiu
>
>
OK.
Jason
>
> I think you are doing too many things in one patch. I'm fine with
> dropping the zero-alias-set streaming (but I'd rather not assert
> as FE get_alias_set langhook may assign zero to random tree nodes).
Ok, the assert was there mostly to double check that all zero alias
sets rematerialize
On 30/11/15 14:24, Richard Biener wrote:
On Mon, 30 Nov 2015, Tom de Vries wrote:
On 30/11/15 10:16, Richard Biener wrote:
On Mon, 30 Nov 2015, Tom de Vries wrote:
Hi,
this patch fixes PR46032.
It handles a call:
...
__builtin_GOMP_parallel (fn, data, num_threads, flags)
...
as:
...
SVN commit r230979 always associates a loop's back-jump with the start
of the loop body. This caused a regression for gcov with conditional
loops, because then the loop body appears to be covered twice per
iteration.
gcc/cp/ChangeLog:
PR gcov-profile/68603
* cp-gimplify.c
> FYI, the function should test recog_memoized (dep_insn) also.
I don't think that's needed as it doesn't call get_attr_type on dep_insn.
--
Eric Botcazou
On 11/30/2015 01:42 AM, Richard Biener wrote:
Yeah. I've pondered with clearing the hashmap after each pass
(and hope no IPA pass would redirect edges). Or even more aggressive,
clear the hashmap as well when we do set_cfun ().
Maybe you can try that?
And no, I don't think any pass expects
Andreas Krebbel wrote:
> On 11/30/2015 04:11 PM, Dominik Vogt wrote:
> > The attached patch fixes some warnings generated by the setmem...
> > patterns in s390.md during build and add test cases for the
> > patterns. The patch is to be added on to p of the movstr patch:
> >
On Mon, Nov 30, 2015 at 05:36:25PM +0100, Tom de Vries wrote:
> +int
> +main (void)
> +{
> + unsigned results[nEvents];
> + unsigned pData[nEvents];
> + unsigned coeff = 2;
> +
> + init ([0], [0]);
> +
> +#pragma omp parallel for
> + for (int idx = 0; idx < (int)nEvents; idx++)
> +
Applied to trunk as r231077.
On 26 November 2015 at 09:43, James Greenhalgh wrote:
> On Thu, Nov 26, 2015 at 09:41:15AM +, Charles Baylis wrote:
>> Hi James,
>>
>> Ping. This needs an ack from an AArch64 reviewer/maintainer
>
> Fine by me, it will considerably clean
Richard,
Thanks a lot for your detailed comments!
Few words about 436.cactusADM gain. The loop which was transformed for
avx2 is very huge and this is the last inner-most loop in routine
Bench_StaggeredLeapfrog2 (StaggeredLeapfrog2.F #366). If you don't
have sources, let me know.
Yuri.
The attached patch fixes some warnings generated by the setmem...
patterns in s390.md during build and add test cases for the
patterns. The patch is to be added on to p of the movstr patch:
https://gcc.gnu.org/ml/gcc-patches/2015-11/msg03485.html
The test cases validate that the patterns are
On Sat, Nov 28, 2015 at 04:05:30PM +, Joseph Myers wrote:
> On Sat, 28 Nov 2015, Richard Biener wrote:
>
> > Different approach: after the FE folds (unexpectedly?), scan the result
> > for SAVE_EXPRs and if found, drop the folding.
>
> Or, if conversions are going to fold from
On Mon, 30 Nov 2015, Richard Biener wrote:
> On Mon, 30 Nov 2015, Marek Polacek wrote:
>
> > On Sat, Nov 28, 2015 at 08:50:12AM +0100, Richard Biener wrote:
> > > Different approach: after the FE folds (unexpectedly?), scan the result
> > > for
> > > SAVE_EXPRs and if found, drop the folding.
>
On Wed, Nov 11, 2015 at 17:56:15 +0300, Aleksander Ivanyushenko wrote:
> On Mon, Aug 24, 2015 at 10:45:03 +0200, Jakub Jelinek wrote:
> > On Thu, Aug 06, 2015 at 05:34:56PM +0300, Maxim Blumental wrote:
> > > Applied the idea with python script alternative. Review, please.
> >
> > > 2015-07-28
On Mon, 30 Nov 2015, Marek Polacek wrote:
> On Sat, Nov 28, 2015 at 08:50:12AM +0100, Richard Biener wrote:
> > Different approach: after the FE folds (unexpectedly?), scan the result for
> > SAVE_EXPRs and if found, drop the folding.
>
> Neither this fixes this problem completely, because we
On Mon, 30 Nov 2015, Jakub Jelinek wrote:
> On Mon, Nov 30, 2015 at 02:30:04PM +, Richard Sandiford wrote:
> > > keep the builtin_reciprocal hook (perhaps renamed to builtin_rsqrt)
> > > for the purpose of this condition and nothing else (i.e. return a
> > > boolean) and let the rest be
On Wed, Nov 11, 2015 at 05:56:15PM +0300, Aleksander Ivanyushenko wrote:
> diff --git a/configure.ac b/configure.ac
> index 9241261..b997646 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -494,6 +494,18 @@ else
> fi])
> AC_SUBST(extra_liboffloadmic_configure_flags)
>
> +# Intelmic and
On Sat, Nov 28, 2015 at 08:50:12AM +0100, Richard Biener wrote:
> Different approach: after the FE folds (unexpectedly?), scan the result for
> SAVE_EXPRs and if found, drop the folding.
Neither this fixes this problem completely, because we simply don't know where
those SAVE_EXPRs might be
On Fri, Nov 27, 2015 at 12:24 AM, Kumar, Venkataramanan
wrote:
> Hi Richard,
>
>> -Original Message-
>> From: Richard Biener [mailto:richard.guent...@gmail.com]
>> Sent: Tuesday, November 24, 2015 9:07 PM
>> To: Kumar, Venkataramanan
>> Cc: Jakub Jelinek
On 11/30/2015 04:11 PM, Dominik Vogt wrote:
> The attached patch fixes some warnings generated by the setmem...
> patterns in s390.md during build and add test cases for the
> patterns. The patch is to be added on to p of the movstr patch:
>
On 11/30/2015 06:11 PM, Ulrich Weigand wrote:
...
> However, I agree that UNSPEC_P_TO_BLK really should also get the length
> as input, to make it have precisely defined semantics. Also, I'd rather
> use a more descriptive name, like UNSPEC_REPLICATE_BYTE or the like.
>
> What would you think
Hi!
On Wed, 25 Nov 2015 11:43:14 +0100 (CET), Richard Biener
wrote:
> On Tue, 24 Nov 2015, Tom de Vries wrote:
> > > [...]
> >
> > Reposting using the in_loop_pipeline style in pass_lim.
>
> Ok.
I merged trunk r230907 into gomp-4_0-branch in a very simplistic way,
On 30/11/15 17:48, Jakub Jelinek wrote:
On Mon, Nov 30, 2015 at 05:36:25PM +0100, Tom de Vries wrote:
+int
+main (void)
+{
+ unsigned results[nEvents];
+ unsigned pData[nEvents];
+ unsigned coeff = 2;
+
+ init ([0], [0]);
+
+#pragma omp parallel for
+ for (int idx = 0; idx < (int)nEvents;
This patch contains the following bug fixes:
* Teaches gfortran to accept both num and static gang arguments inside
same clause. E.g. gang(num:10, static:30). Currently, gfortran only
allows one of those arguments to appear in a gang clause.
* Make the diagnostics reported by
On Thu, 19 Nov 2015 16:57:23 +0100
Jakub Jelinek wrote:
> If it is unclear, I think disallowing acc {parallel,kernels} inside of
> acc host_data might be too big hammer, but perhaps just erroring out
> or warning during gimplification that if you (explicitly or
> implicitly)
On 11/27/2015 06:55 PM, Eric Botcazou wrote:
> There is no official ABI for Ada so I guess that's not really a problem as
> long as it's documented on https://gcc.gnu.org/gcc-5/changes.html.
It's still surprising to make such a far-reaching change in a minor
release, I think.
Florian
---
gcc/graphite-isl-ast-to-gimple.c | 4 ++--
gcc/graphite-scop-detection.c | 31 ---
gcc/graphite-sese-to-poly.c | 16 +++-
gcc/testsuite/gcc.dg/graphite/pr35356-1.c | 2 +-
4 files changed, 22 insertions(+), 31
On 30.11.15 17:22, Jakub Jelinek wrote:
On Mon, Nov 30, 2015 at 05:17:29PM +0100, Bernd Schmidt wrote:
On 11/30/2015 01:12 PM, Andreas Tobler wrote:
On 30.11.15 11:28, Bernd Schmidt wrote:
On 11/29/2015 08:32 PM, Andreas Tobler wrote:
-/* { dg-do run { target { *-*-linux* } } } */
+/* {
we used to generate modulo and division by zero because ISL uses big numbers
which translate to zero in modulo arithmetic. The patch also improves error
handling
and bails out early in case of wrong code gen.
---
gcc/graphite-isl-ast-to-gimple.c | 85 +++-
1
On Mon, Nov 30, 2015 at 13:04:59 +0100, Jakub Jelinek wrote:
> On Fri, Nov 27, 2015 at 07:50:09PM +0300, Ilya Verbin wrote:
> > + /* Most significant bit of the size marks such vars. */
> > + unsigned HOST_WIDE_INT isize = tree_to_uhwi (size);
> > + isize |= 1ULL << (int_size_in_bytes
On 11/30/2015 02:00 AM, Ajit Kumar Agarwal wrote:
This patch made correction in the comment for SLP profitable vectorization case.
Correction in the comment for vectorizable profitable case. The comment is
contradicting the condition vec_outside_cost + vec_inside_cost > scalar_cost.
ChangeLog:
>
> FAIL: obj-c++.dg/property/dotsyntax-11.mm -fgnu-runtime (test for errors,
> line 51)
> FAIL: obj-c++.dg/property/dotsyntax-11.mm -fgnu-runtime (test for errors,
> line 56)
> FAIL: obj-c++.dg/property/dotsyntax-11.mm -fgnu-runtime (test for errors,
> line 59)
>
> Andreas.
Here is the
On Mon, Nov 30, 2015 at 11:29:34PM +0300, Ilya Verbin wrote:
> > This looks wrong, both of these clearly could affect anything with
> > DECL_HAS_VALUE_EXPR_P, not just the link vars.
> > So, if you need to handle the "omp declare target link" vars specially,
> > you should only handle those
On Mon, Nov 30, 2015 at 21:49:02 +0100, Jakub Jelinek wrote:
> On Mon, Nov 30, 2015 at 11:29:34PM +0300, Ilya Verbin wrote:
> > You're right, it doesn't deallocate memory on the device if DSO leaves
> > nonzero
> > refcount. And currently host compiler doesn't set MSB in host_var_table,
> >
On 11/29/2015 03:10 PM, Andreas Tobler wrote:
All,
this patch adds support for asan for i?86/x86_64-*freebsd*.
Test results can be found on the list.
These modifications belong only to gcc. There is one modification to
asan/asan_linux.cc, this one is sent upstream. Until this one is in, my
On 11/26/2015 11:49 AM, Andreas Tobler wrote:
Hi all,
the attached patch fixes the build issue from this ticket if bootstrap
is disabled.
Tested on x86_64-*-linux* and on x86_64-*-freebsd* with gcc and clang.
Ok for trunk?
And 5.3?
Thanks,
Andreas
2015-11-26 Andreas Tobler
Hi,
when looking at the attempt_target_gridification function I realized I
forgot to to replace some of the early code with proper gimple
statement access function calls. This patch addresses that.
Committed to the branch.
Thanks,
Martin
2015-11-30 Martin Jambor
On 11/30/2015 03:06 PM, Jan Sommer wrote:
Could someone with write access please commit the patch?
The paperwork with the FSF has gone through. If something else is missing,
please tell me.
I won't be available next week.
I'm not sure what you built your patches again, but I can't apply them
> Hi,
> this is polished version of the patch to implement IL level incremental
> inking.
> -flinker-output is now documented and can be specified to the GCC driver.
> In this case plugin gets option -linker-output-known and it stops from
> attempts to detect it from info passed down by linker. I
On Tue, Nov 24, 2015 at 6:18 PM, Richard Earnshaw
wrote:
> On 24/11/15 09:56, Richard Earnshaw wrote:
>> On 24/11/15 02:51, Bin.Cheng wrote:
> The aarch64's problem is we don't define addptr3 pattern, and we don't
>>> have direct insn pattern describing the
On 11/29/2015 09:24 AM, Ajit Kumar Agarwal wrote:
I agree with the above. To add up on the above, we only require to calculate
the set of objects ( SSA_NAMES) that are live at the birth or the header of the
loop.
We don't need to calculate the live through the Loop considering Live in and
This patch backports the recent fortran routine support changes I've
made in trunk to gomp-4_0-branch. Nothing changed in the fortran front
end, but I corrected a couple of problems with the way that gang, worker
and vector were handled in tree-nested.c. And there's a new test case to
exercise
Hi,
this is first patch in the broken up series. It adds the logic into
ipa-inline-transform to drop the flag when inlining. I do it always until
we find a way to make early optimizations safe WRT this transform.
The testcase triggers with GCC 5.0/4.9 too, older compilers passes if
On 11/26/2015 05:37 AM, Bernd Schmidt wrote:
On 11/25/2015 11:47 PM, David Malcolm wrote:
FWIW, the reason I special-cased the linked list was to avoid any
dynamic memory allocation: the ctors run before main, so I wanted to
keep them as simple as possible.
Is there any particular reason for
Hi,
this is polished version of the patch to implement IL level incremental inking.
-flinker-output is now documented and can be specified to the GCC driver.
In this case plugin gets option -linker-output-known and it stops from
attempts to detect it from info passed down by linker. I also added
Hi,
Jakub requested that I remove the grid description from new fields of
the classes representing gimple omp statement and put them into
special artificial clauses instead. This patch implement that, with
one target clause per dimension (so up to three clauses) and each one
describing both the
On Mon, 30 Nov 2015, Marek Polacek wrote:
> On Sat, Nov 28, 2015 at 08:50:12AM +0100, Richard Biener wrote:
> > Different approach: after the FE folds (unexpectedly?), scan the result for
> > SAVE_EXPRs and if found, drop the folding.
>
> Neither this fixes this problem completely, because we
Hi,
doing some more testing of the branch and combining two of my
testcases I came accross a bug where temporaries created by
force_gimple_operand_gsi were not added to the proper bind and thus
were subsequently re-mapped to error_mark when the target construct
was within some other omp
Hi,
this is third part which enables us to change -fstrict-aliasing using
optimize attribute. This ought to work safely now because inliner
propagate the flag.
Bootstrapped/regtested x86_64-linux.
Honza
* gcc.c-torture/execute/alias-1.c: New testcase.
* c-common.c: Do not
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Hi,
this patch disables the streaming of alias 0 flag and adds a comment why.
Bootstrapped/regtested x86_64-linux, OK?
Honza
* lto-streamer-out.c (hash_tree): Do not stream TYPE_ALIAS_SET.
* tree-streamer-out.c (pack_ts_type_common_value_fields): Do not
stream
PR 68477 observes that gccgo crashes when using -flto1 because a type
variant has TYPE_STRING_FLAG set. So, don't do that.
TYPE_STRING_FLAG doesn't really do anything, as far as I can tell,
since all the relevant tests in dwarf2out.c also test isfortran().
But, it seems like the right thing to
On Sat, Nov 28, 2015 at 3:40 AM, Jakub Jelinek wrote:
> Hi!
>
> The recent changes where vector sqrt is represented in the IL using
> IFN_SQRT instead of target specific builtins broke the discovery
> of vector rsqrt, as targetm.builtin_reciprocal is called only
> on builtin
Some time ago, we submitted an RFC for the introduction of
UPC support into GCC. During the intervening time period,
we have continued to keep the 'gupc' (GNU UPC) branch in sync
with the GCC trunk and have incorporated feedback and contributions from
various GCC developers (Joseph Myers, Tom
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
The UPC-related source code differences are summarized here:
Hi!
Committed to gomp-4_0-branch in r231099:
commit 4f88f92b308151aa2c2592102da20c417df69c27
Merge: 24e5942 851c1b0
Author: tschwinge
Date: Tue Dec 1 07:44:27 2015 +
svn merge -r 230907:231075 svn+ssh://gcc.gnu.org/svn/gcc/trunk
[NOTE: Due to email list size limits, this patch is broken into 9 parts.]
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
[NOTE: Due to email list size limits, this patch is broken into 9 parts.]
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
Hi,
memory attributes are currently optimized and attached to RTL even when not
optimizing. This is obviously just a wasted effort.
Bootstrapped/regtested x86_64-linux, OK?
Honza
* emit-rtl.c (set_mem_attrs, set_mem_attributes_minus_bitpos):
Do not compute memory attributes when
[NOTE: Due to email list size limits, this patch is broken into 9 parts.]
Background
--
An overview email, describing the UPC-related changes is here:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg5.html
The GUPC branch is described here:
http://gcc.gnu.org/projects/gupc.html
Hi!
On Fri, 27 Nov 2015 11:51:11 -0500, David Edelsohn wrote:
> On Fri, Nov 27, 2015 at 11:24 AM, Thomas Schwinge
> wrote:
> > On Tue, 24 Nov 2015 10:32:12 +, Alan Lawrence
> > wrote:
> >> I note doc/install.texi says that
The GCC 5 branch is now frozen for creating a first release candidate
for GCC 5.3. All changes from now on require release manager approval.
Thanks,
Richard.
On Thu, Nov 12, 2015 at 04:58:21PM +0300, Alexander Monakov wrote:
> I'm proposing the following patch as a step towards resolving the issue with
> inaccessibility of stack storage (.local memory) in PTX to other threads than
> the one using that stack. The idea is to have preallocated stacks,
On 11/29/2015 06:14 PM, H.J. Lu wrote:
Is this safe for stage 3?
Is there a reason to do it now? This doesn't include a testcase.
* function.c (assign_parm_setup_stack): Force source into a
register if needed.
* target.def (function_incoming_arg): Update documentation
Hello Jakub,
On 11/24/2015 06:10 PM, Jakub Jelinek wrote:
The new pass is IMNSHO completely useless and undesirable, both for compile
time (another whole IL traversal) reasons and for the unnecessary creation
of memory allocations.
[…]
Thank you for your detailed answer! This is just to say
On Mon, 30 Nov 2015, Jakub Jelinek wrote:
> Does your patch affect all the stack allocations within certain function
> (i.e. no way to select on a per-variable bases what stack to allocate it
> to)? Without any detailed analysis at least e.g. spilled (non-addressable)
> vars could at least go to
Self-explanatory, tested on x86_64-suse-linux, applied on the mainline.
2015-11-30 Eric Botcazou
* gcc-interface/utils2.c (gnat_invariant_expr): Add type conversions.
2015-11-30 Eric Botcazou
*
On Mon, 30 Nov 2015, Jakub Jelinek wrote:
> Does it really have to be a full multilib? I mean, the only precondition is
> that something sets up the var, right? Would the OpenACC folks be willing
> to set it up too? For stuff like libc, functions that are ECF_LEAF builtins
> IMHO really don't
This fixes the simple C interfacing issues recently reported by Jan (the
signedness issue of char will probably be fixed for GCC 6, the duality
pointer/System.Address probably _not_ unfortunately).
Tested on x86_64-suse-linux, applied on the mainline.
2015-11-30 Eric Botcazou
On Fri, Nov 27, 2015 at 07:50:09PM +0300, Ilya Verbin wrote:
> On Thu, Nov 19, 2015 at 16:31:15 +0100, Jakub Jelinek wrote:
> > On Mon, Nov 16, 2015 at 06:40:43PM +0300, Ilya Verbin wrote:
> > > @@ -2009,7 +2010,8 @@ scan_sharing_clauses (tree clauses, omp_context
> > > *ctx)
> > > decl =
On 11/30/2015 01:00 AM, Matthias Klose wrote:
link libgccjit using LDFLAGS (which is empty by default), but could be
used to pass hardening options like -Wlz,relro.
Ok when stage 1 opens.
Bernd
On 30.11.15 11:28, Bernd Schmidt wrote:
On 11/29/2015 08:32 PM, Andreas Tobler wrote:
Hi all,
the attached patch prepares the testsuite, c and c++, for the upcoming
ASAN support for FreeBSD (x86_64 first).
I tested the patch on CentOS7.1 x86_64 and on FreeBSD x86_64.
Results can be seen on
On 30/11/15 10:16, Richard Biener wrote:
On Mon, 30 Nov 2015, Tom de Vries wrote:
Hi,
this patch fixes PR46032.
It handles a call:
...
__builtin_GOMP_parallel (fn, data, num_threads, flags)
...
as:
...
fn (data)
...
in ipa-pta.
This improves ipa-pta alias analysis in the parallelized
This fixes an ordering issue in the Ada code generated by the -fdump-ada-spec
option with the C++ compiler on structures/unions with nested anonymous arrays
of structures/unions.
Given that this only affects the Ada code generated by -fdump-ada-spec and has
no effect whatsoever on the C and
1 - 100 of 123 matches
Mail list logo