On 9/19/20 11:22 PM, Martin Sebor wrote:
On 9/18/20 12:29 AM, Aldy Hernandez wrote:
On 9/17/20 10:18 PM, Martin Sebor wrote:
On 9/17/20 12:39 PM, Andrew MacLeod wrote:
On 9/17/20 12:08 PM, Martin Sebor via Gcc-patches wrote:
On 9/16/20 9:23 PM, Jeff Law wrote:
On 9/15/20 1:47 PM, Marti
Hi,
this is patch I am using to fix the assumed_alias_type.f90 failure by
simply arranging alias set 0 for the problematic array descriptor.
I am not sure this is the best option, but I suppose it is better than
setting all array descritors to have same canonical type (as done by
LTO)?
Honza
On Linux/x86_64,
6450f07388f9fe575a489c9309c36012b17b88b0 is the first bad commit
commit 6450f07388f9fe575a489c9309c36012b17b88b0
Author: Martin Sebor
Date: Sat Sep 19 17:21:52 2020 -0600
Infrastructure & C front end changes for array parameter checking (PR
c/50584).
caused
FAIL: gcc.dg
On Linux/x86_64,
6450f07388f9fe575a489c9309c36012b17b88b0 is the first bad commit
commit 6450f07388f9fe575a489c9309c36012b17b88b0
Author: Martin Sebor
Date: Sat Sep 19 17:21:52 2020 -0600
Infrastructure & C front end changes for array parameter checking (PR
c/50584).
caused
FAIL: gcc.dg
On Linux/x86_64,
6450f07388f9fe575a489c9309c36012b17b88b0 is the first bad commit
commit 6450f07388f9fe575a489c9309c36012b17b88b0
Author: Martin Sebor
Date: Sat Sep 19 17:21:52 2020 -0600
Infrastructure & C front end changes for array parameter checking (PR
c/50584).
caused
FAIL: gcc.dg
On Linux/x86_64,
6450f07388f9fe575a489c9309c36012b17b88b0 is the first bad commit
commit 6450f07388f9fe575a489c9309c36012b17b88b0
Author: Martin Sebor
Date: Sat Sep 19 17:21:52 2020 -0600
Infrastructure & C front end changes for array parameter checking (PR
c/50584).
caused
FAIL: gcc.dg
On Linux/x86_64,
6450f07388f9fe575a489c9309c36012b17b88b0 is the first bad commit
commit 6450f07388f9fe575a489c9309c36012b17b88b0
Author: Martin Sebor
Date: Sat Sep 19 17:21:52 2020 -0600
Infrastructure & C front end changes for array parameter checking (PR
c/50584).
caused
FAIL: gcc.dg
On Linux/x86_64,
3f9a497d1b0dd9da87908a11b59bf364ad40ddca is the first bad commit
commit 3f9a497d1b0dd9da87908a11b59bf364ad40ddca
Author: Martin Sebor
Date: Sat Sep 19 17:47:29 2020 -0600
Extend -Warray-bounds to detect out-of-bounds accesses to array parameters.
caused
FAIL: gcc.dg/Warr
On Linux/x86_64,
6450f07388f9fe575a489c9309c36012b17b88b0 is the first bad commit
commit 6450f07388f9fe575a489c9309c36012b17b88b0
Author: Martin Sebor
Date: Sat Sep 19 17:21:52 2020 -0600
Infrastructure & C front end changes for array parameter checking (PR
c/50584).
caused
FAIL: gcc.dg
On Linux/x86_64,
6450f07388f9fe575a489c9309c36012b17b88b0 is the first bad commit
commit 6450f07388f9fe575a489c9309c36012b17b88b0
Author: Martin Sebor
Date: Sat Sep 19 17:21:52 2020 -0600
Infrastructure & C front end changes for array parameter checking (PR
c/50584).
caused
FAIL: gcc.dg
On Linux/x86_64,
6450f07388f9fe575a489c9309c36012b17b88b0 is the first bad commit
commit 6450f07388f9fe575a489c9309c36012b17b88b0
Author: Martin Sebor
Date: Sat Sep 19 17:21:52 2020 -0600
Infrastructure & C front end changes for array parameter checking (PR
c/50584).
caused
FAIL: gcc.dg
On Linux/x86_64,
6450f07388f9fe575a489c9309c36012b17b88b0 is the first bad commit
commit 6450f07388f9fe575a489c9309c36012b17b88b0
Author: Martin Sebor
Date: Sat Sep 19 17:21:52 2020 -0600
Infrastructure & C front end changes for array parameter checking (PR
c/50584).
caused
FAIL: gcc.dg
On Linux/x86_64,
6450f07388f9fe575a489c9309c36012b17b88b0 is the first bad commit
commit 6450f07388f9fe575a489c9309c36012b17b88b0
Author: Martin Sebor
Date: Sat Sep 19 17:21:52 2020 -0600
Infrastructure & C front end changes for array parameter checking (PR
c/50584).
caused
FAIL: gcc.dg
On Linux/x86_64,
3f9a497d1b0dd9da87908a11b59bf364ad40ddca is the first bad commit
commit 3f9a497d1b0dd9da87908a11b59bf364ad40ddca
Author: Martin Sebor
Date: Sat Sep 19 17:47:29 2020 -0600
Extend -Warray-bounds to detect out-of-bounds accesses to array parameters.
caused
FAIL: gcc.dg/Warr
On 9/19/20 4:32 PM, Martin Sebor wrote:
On 9/18/20 3:09 PM, Andrew MacLeod wrote:
O
What I meant by proxy is a substitute class each of whose objects
stands in for a single instance of int_range where N is
a runtime value. There's no class like that.
[Just to be clear, I don't meant for th
On 9/17/20 4:38 PM, Joseph Myers wrote:
On Wed, 16 Sep 2020, Martin Sebor via Gcc-patches wrote:
Attached is an updated revision of the patch. Besides the tweaks
above it also contains a cosmetic change to the warning issued
for mismatches in unspecified VLA bounds: it points at the decl
with
Hi,
this is cleaned up version of the patch. I removed unfinished bits, fixed
propagation, cleaned it up and fixed fallout.
At present modref does bare minimum of what it can do and only collects
base/ref alias sets of accesses to disambiguate uding them. I have followup
patches adding more feat
[temp.deduct.guide]p3: Two deduction guide declarations in the same
translation unit for the same class template shall not have equivalent
parameter-declaration-clauses.
So let's detect that.
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
gcc/cp/ChangeLog:
PR c++/97099
This PR points out that we accept
template struct tuple { tuple(T); }; // #1
template explicit tuple(T t) -> tuple; // #2
tuple t = { 1 };
despite the 'explicit' deduction guide in a copy-list-initialization
context. That's because in deduction_guides_for we first find the
user-defined ded
I noticed that clang++ has this CTAD warning and thought that it might
be useful to have it. From clang++: "Some style guides want to allow
using CTAD only on types that "opt-in"; i.e. on types that are designed
to support it and not just types that *happen* to work with it."
So this warning warn
On 9/18/20 12:29 AM, Aldy Hernandez wrote:
On 9/17/20 10:18 PM, Martin Sebor wrote:
On 9/17/20 12:39 PM, Andrew MacLeod wrote:
On 9/17/20 12:08 PM, Martin Sebor via Gcc-patches wrote:
On 9/16/20 9:23 PM, Jeff Law wrote:
On 9/15/20 1:47 PM, Martin Sebor wrote:
Overflowing the size of a dyn
On 9/18/20 3:09 PM, Andrew MacLeod wrote:
On 9/18/20 4:35 PM, Martin Sebor wrote:
On 9/18/20 11:36 AM, Andrew MacLeod wrote:
On
it works exactly like one would expect a simple allocator to work..
as long as the allcoator is "live", its allocations are live. once
it is destructed, all the me
In the testcase below, the dependent specializations iter_reference_t
and iter_reference_t share the same tree due to specialization
caching. So when find_template_parameters walks through the
requires-expression (as part of normalization), it sees and includes the
out-of-scope template parameter
On 18/09/2020 12:25, Andrew Stubbs wrote:
This patch fixes a problem in which nested OpenMP parallel regions cause
errors if the number of inner teams is not balanced (i.e. the number of
loop iterations is not divisible by the number of physical threads). A
testcase is included.
This updated
On Thu, Sep 17, 2020 at 11:11 PM Hongtao Liu wrote:
>
> On Thu, Sep 17, 2020 at 12:10 PM Jeff Law wrote:
> >
> >
> > On 9/15/20 9:20 PM, Hongtao Liu via Gcc-patches wrote:
> > > Hi:
> > > Rtx cost of sse_to_integer would be used by pass_stv as a
> > > measurement for the scalar-to-vector transf
On 29/05/20 07:17 +0100, Mike Crowe via Libstdc++ wrote:
> > > diff --git a/libstdc++-v3/include/bits/atomic_futex.h
> > > b/libstdc++-v3/include/bits/atomic_futex.h
> > > index 5f95ade..aa137a7 100644
> > > --- a/libstdc++-v3/include/bits/atomic_futex.h
> > > +++ b/libstdc++-v3/include/bits/atomi
On Friday 11 September 2020 at 19:59:36 +0100, Jonathan Wakely wrote:
> commit 53ad6b1979f4bd7121e977c4a44151b14d8a0147
> Author: Jonathan Wakely
> Date: Fri Sep 11 19:59:11 2020
>
> libstdc++: Fix chrono::__detail::ceil to work with C++11
>
> In C++11 constexpr functions can only
> -Original Message-
> From: Richard Sandiford [mailto:richard.sandif...@arm.com]
> Sent: Saturday, August 29, 2020 2:31 AM
> To: duanbo (C)
> Cc: GCC Patches ; rguent...@suse.de
> Subject: Re: [PATCH PR96757] aarch64: ICE during GIMPLE pass: vect
>
> "duanbo (C)" writes:
> > @@ -4395,
28 matches
Mail list logo
