public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/92714] [missed-optimization] aggregate initialization of an array fills the whole array with zeros first, including leading non-zero elements
[not found] <bug-92714-4@http.gcc.gnu.org/bugzilla/>
@ 2019-11-29 9:01 ` jakub at gcc dot gnu.org
2021-12-22 10:06 ` [Bug tree-optimization/92714] " pinskia at gcc dot gnu.org
1 sibling, 0 replies; 2+ messages in thread
From: jakub at gcc dot gnu.org @ 2019-11-29 9:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92714
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Or in theory store-merging could do this, although it can handle only the = {}
and not memset right now. That said, just unconditionally adjusting the
clearing store not to cover the boundaries which are overwritten is not a good
idea, it is much faster to start with an 8 or 16 byte aligned address over
skipping 3 or 7 bytes there.
>From gcc-bugs-return-661764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 09:04:02 2019
Return-Path: <gcc-bugs-return-661764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44959 invoked by alias); 29 Nov 2019 09:04:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44890 invoked by uid 55); 29 Nov 2019 09:03:57 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/91574] [10 Regression] ICE in types_same_for_odr at gcc/ipa-devirt.c:355 since r272037
Date: Fri, 29 Nov 2019 09:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91574-4-uuW7HKre0m@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03558.txt.bz2
Content-length: 728
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91574
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Fri Nov 29 09:03:25 2019
New Revision: 278829
URL: https://gcc.gnu.org/viewcvs?rev=278829&root=gcc&view=rev
Log:
Check for TYPE_NAME in type_with_linkage_p.
2019-11-29 Martin Liska <mliska@suse.cz>
PR lto/91574
* ipa-devirt.c (types_same_for_odr): Check for existence
of TYPE_NAMEs first.
2019-11-29 Martin Liska <mliska@suse.cz>
PR lto/91574
* g++.dg/lto/pr91574_0.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/lto/pr91574_0.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/ipa-devirt.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 09:08:29 2019
Return-Path: <gcc-bugs-return-661765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55759 invoked by alias); 29 Nov 2019 09:08:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55702 invoked by uid 55); 29 Nov 2019 09:08:24 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/92489] [9 regression] internal error on Invalid_Value Attribute attribute
Date: Fri, 29 Nov 2019 09:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92489-4-Y68fRrilkM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92489-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92489-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03559.txt.bz2
Content-length: 656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92489
--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Fri Nov 29 09:07:53 2019
New Revision: 278830
URL: https://gcc.gnu.org/viewcvs?rev=278830&root=gcc&view=rev
Log:
PR ada/92489
Backport from mainline
2019-07-01 Ed Schonberg <schonberg@adacore.com>
* exp_attr.adb (Expand_Attribute_Reference, case Invalid_Value):
Resolve result of call to Get_Simple_Init_Val, which may be a
conversion of a literal.
Modified:
branches/gcc-9-branch/gcc/ada/ChangeLog
branches/gcc-9-branch/gcc/ada/exp_attr.adb
>From gcc-bugs-return-661767-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 09:09:31 2019
Return-Path: <gcc-bugs-return-661767-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59693 invoked by alias); 29 Nov 2019 09:09:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58911 invoked by uid 55); 29 Nov 2019 09:09:23 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60228] ICE using lambda in #pragma omp declare reduction
Date: Fri, 29 Nov 2019 09:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60228-4-ZGLZG9J8Xl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60228-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60228-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03561.txt.bz2
Content-length: 1620
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60228
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Nov 29 09:08:46 2019
New Revision: 278831
URL: https://gcc.gnu.org/viewcvs?rev=278831&root=gcc&view=rev
Log:
PR c++/60228
* parser.c (cp_parser_omp_declare_reduction_exprs): If
processing_template_decl, wrap the combiner or initializer
into EXPR_STMT.
* decl.c (start_preparsed_function): Don't start a lambda scope
for DECL_OMP_DECLARE_REDUCTION_P functions.
(finish_function): Don't finish a lambda scope for
DECL_OMP_DECLARE_REDUCTION_P functions, nor cp_fold_function
them nor cp_genericize them.
* mangle.c (decl_mangling_context): Look through
DECL_OMP_DECLARE_REDUCTION_P functions.
* semantics.c (expand_or_defer_fn_1): For DECL_OMP_DECLARE_REDUCTION_P
functions, use tentative linkage, don't keep their bodies with
-fkeep-inline-functions and return false at the end.
* g++.dg/gomp/openmp-simd-2.C: Don't expect bodies for
DECL_OMP_DECLARE_REDUCTION_P functions.
* testsuite/libgomp.c++/udr-20.C: New test.
* testsuite/libgomp.c++/udr-21.C: New test.
Added:
trunk/libgomp/testsuite/libgomp.c++/udr-20.C
trunk/libgomp/testsuite/libgomp.c++/udr-21.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/decl.c
trunk/gcc/cp/mangle.c
trunk/gcc/cp/parser.c
trunk/gcc/cp/semantics.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/gomp/openmp-simd-2.C
trunk/libgomp/ChangeLog
>From gcc-bugs-return-661766-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 09:09:19 2019
Return-Path: <gcc-bugs-return-661766-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58460 invoked by alias); 29 Nov 2019 09:09:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57881 invoked by uid 48); 29 Nov 2019 09:09:13 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/92489] [9 regression] internal error on Invalid_Value Attribute attribute
Date: Fri, 29 Nov 2019 09:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92489-4-N30j9rQbII@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92489-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92489-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03560.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92489
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Thanks for reporting the problem.
>From gcc-bugs-return-661768-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 09:11:20 2019
Return-Path: <gcc-bugs-return-661768-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64072 invoked by alias); 29 Nov 2019 09:11:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63992 invoked by uid 55); 29 Nov 2019 09:11:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60228] ICE using lambda in #pragma omp declare reduction
Date: Fri, 29 Nov 2019 09:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60228-4-sV8DrRUl2j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60228-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60228-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03562.txt.bz2
Content-length: 1367
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60228
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Nov 29 09:10:44 2019
New Revision: 278832
URL: https://gcc.gnu.org/viewcvs?rev=278832&root=gcc&view=rev
Log:
PR c++/60228
* parser.c (cp_parser_omp_declare_reduction_exprs): If
processing_template_decl, wrap the combiner or initializer
into EXPR_STMT.
* decl.c (start_preparsed_function): Don't start a lambda scope
for DECL_OMP_DECLARE_REDUCTION_P functions.
(finish_function): Don't finish a lambda scope for
DECL_OMP_DECLARE_REDUCTION_P functions, nor cp_fold_function
them nor cp_genericize them.
* mangle.c (decl_mangling_context): Look through
DECL_OMP_DECLARE_REDUCTION_P functions.
* semantics.c (expand_or_defer_fn_1): For DECL_OMP_DECLARE_REDUCTION_P
functions, use tentative linkage, don't keep their bodies with
-fkeep-inline-functions and return false at the end.
* g++.dg/gomp/openmp-simd-2.C: Don't expect bodies for
DECL_OMP_DECLARE_REDUCTION_P functions.
* testsuite/libgomp.c++/udr-20.C: New test.
* testsuite/libgomp.c++/udr-21.C: New test.
Modified:
trunk/libgomp/testsuite/libgomp.c++/udr-20.C
trunk/libgomp/testsuite/libgomp.c++/udr-21.C
>From gcc-bugs-return-661769-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 09:14:27 2019
Return-Path: <gcc-bugs-return-661769-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74394 invoked by alias); 29 Nov 2019 09:14:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74338 invoked by uid 48); 29 Nov 2019 09:14:19 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyB0cmVlLW9wdGltaXphdGlvbi85MjcxNV0gWzEwIFJlZ3Jlc3Npb25d?= =?UTF-8?B?IGVycm9yOiBwb3NpdGlvbiBwbHVzIHNpemUgZXhjZWVkcyBzaXplIG9mIHJl?= =?UTF-8?B?ZmVyZW5jZWQgb2JqZWN0IGluICDigJhiaXRfZmllbGRfcmVm4oCZ?Date: Fri, 29 Nov 2019 09:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92715-4-4T9Br2Q0rM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92715-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92715-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03563.txt.bz2
Content-length: 3725
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92715
--- Comment #5 from David Binderman <dcb314 at hotmail dot com> ---
Reduced C++ code:
typedef double a __attribute__((__vector_size__(32)));
double b;
a c;
enum { d, e };
template <typename> struct h;
template <typename> class i;
template <typename, int g, int, int = 0, int = g, int = d> class aa;
template <typename> class j;
template <typename, typename> class ab;
template <typename> struct ae;
template <typename> struct w;
template <typename af> struct x { typedef typename ae<af>::k k; };
template <typename ah> struct y { typedef j<ah> k; };
template <typename ai> ai aj(const typename w<ai>::k &);
template <> struct ae<double> { typedef a k; };
template <> struct w<a> { typedef double k; };
template <> a aj(const double &ak) {
c = a{ak, ak, ak, ak};
return c;
}
struct z {
z(double am) : an(am) {}
template <typename ag> void ao() { aj<ag>(an); }
double an;
};
struct ap {
template <int, typename ai> void aq(double *, ai);
};
template <typename ah> class ar {
public:
typedef typename h<ah>::al al;
typedef aa<al, h<ah>::as, h<ah>::at, e, h<ah>::au, h<ah>::av> aw;
typedef ab<z, aw> ax;
const ax ay(const al &);
template <typename az> const ab<az, aw> ba(const az &);
ah &operator/=(const al &);
};
template <typename ah> class j : public ar<ah> {};
template <typename ah> struct ac { typename ah::al &bb(long); };
template <typename al, int bc, int bd, int be, int bf, int bg>
struct ac<aa<al, bc, bd, be, bf, bg>> : ac<i<aa<al, bf, bg>>> {
typedef aa<al, bc, bd> bh;
ac(bh);
};
struct bi {
template <typename af, typename bj> void ao(z bk, bj) { bk.ao<af>(); }
};
template <typename bl, typename bm> struct ac<ab<bl, bm>> {
ac(ab<bl, bm> l) : bn(l.bo()) {}
template <int, typename ag, typename bj> ag bp(bj bq) { br.ao<ag>(bn, bq); }
bl bn;
bi br;
};
template <typename bs> struct bt {
typedef typename bs::bh bu;
typedef typename x<typename bu::al>::k ag;
};
template <typename bv> struct bw {
static void bx(bv by) {
enum { bz, ca, cb };
by.template aq<ca, cb, typename bv::ag>(bz);
}
};
template <typename cc, typename cd, typename ce> class cf {
public:
typedef cc cg;
typedef cd ch;
typedef typename bt<cc>::ag ag;
cf(cg ci, ch cj, ce, cc) : ck(ci), cl(cj) {}
template <int dg, int cm, typename> void aq(long bq) {
bn.template aq<dg>(&ck.bb(bq), cl.template bp<cm, ag>(bq));
}
cg ck;
ch cl;
ce bn;
};
template <typename cn, typename co, typename ce> void cp(cn ci, co cj, ce cq) {
typedef ac<cn> cg;
typedef ac<co> ch;
ch a(cj);
cg d(ci);
typedef cf<cg, ch, ce> bv;
bv e(d, a, cq, ci);
bw<bv>::bx(e);
}
template <typename bu, typename cr, typename cs> void m(bu ci, cr cj, cs cq) {
ab<z, aa<double, 0, 1, 1, 2, 3>> n = cj;
cp(ci, n, cq);
}
template <typename ah> class i : public y<ah>::k {};
template <typename o, int g, int ad, int u, int q, int r>
struct h<aa<o, g, ad, u, q, r>> {
typedef o al;
enum { as, at, au, av };
};
template <typename o, int g, int, int, int, int>
class aa : public i<aa<o, g, d>> {};
template <typename, typename> class ab {
public:
ab(long, long, z cq) : bn(cq) {}
z bo() { return bn; }
z bn;
};
template <typename ah>
template <typename az>
const ab<az, typename ar<ah>::aw> ar<ah>::ba(const az &cq) {
return ab<az, aw>(0, 0, cq);
}
template <typename ah> const typename ar<ah>::ax ar<ah>::ay(const al &p) {
return ba(z(p));
}
template <typename ah> ah &ar<ah>::operator/=(const al &am) {
ah s;
ab<z, aa<double, 0, 1, 1, 2, 3>> t = ay(am);
m(s, t, ap());
}
void v() {
aa<double, 1, 1> f;
__attribute__((__vector_size__(2 * sizeof(double)))) double g;
b = g[0];
f /= b;
}
>From gcc-bugs-return-661771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 09:19:24 2019
Return-Path: <gcc-bugs-return-661771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84349 invoked by alias); 29 Nov 2019 09:19:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84286 invoked by uid 55); 29 Nov 2019 09:19:20 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyB0cmVlLW9wdGltaXphdGlvbi85MjcxNV0gWzEwIFJlZ3Jlc3Npb25d?= =?UTF-8?B?IGVycm9yOiBwb3NpdGlvbiBwbHVzIHNpemUgZXhjZWVkcyBzaXplIG9mIHJl?= =?UTF-8?B?ZmVyZW5jZWQgb2JqZWN0IGluICDigJhiaXRfZmllbGRfcmVm4oCZ?Date: Fri, 29 Nov 2019 09:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92715-4-39KnmAGlLc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92715-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92715-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03565.txt.bz2
Content-length: 724
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92715
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Fri Nov 29 09:18:48 2019
New Revision: 278833
URL: https://gcc.gnu.org/viewcvs?rev=278833&root=gcc&view=rev
Log:
2019-11-29 Richard Biener <rguenther@suse.de>
PR tree-optimization/92715
* tree-ssa-forwprop.c (simplify_vector_constructor): Bail
out for uniform vectors and source vectors with less elements
than the destination.
* gcc.dg/torture/pr92715.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/torture/pr92715.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-forwprop.c
>From gcc-bugs-return-661770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 09:19:12 2019
Return-Path: <gcc-bugs-return-661770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83616 invoked by alias); 29 Nov 2019 09:19:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83543 invoked by uid 48); 29 Nov 2019 09:19:08 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyB0cmVlLW9wdGltaXphdGlvbi85MjcxNV0gWzEwIFJlZ3Jlc3Npb25d?= =?UTF-8?B?IGVycm9yOiBwb3NpdGlvbiBwbHVzIHNpemUgZXhjZWVkcyBzaXplIG9mIHJl?= =?UTF-8?B?ZmVyZW5jZWQgb2JqZWN0IGluICDigJhiaXRfZmllbGRfcmVm4oCZ?Date: Fri, 29 Nov 2019 09:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status resolution
Message-ID: <bug-92715-4-KiW3dKfCzg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92715-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92715-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03564.txt.bz2
Content-length: 481
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92715
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P1 |P3
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-661772-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 10:12:12 2019
Return-Path: <gcc-bugs-return-661772-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105484 invoked by alias); 29 Nov 2019 10:12:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105415 invoked by uid 48); 29 Nov 2019 10:12:08 -0000
From: "avi@cloudius-systems.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92722] gcc considers "padding" byte of empty lambda to be uninitialized
Date: Fri, 29 Nov 2019 10:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: avi@cloudius-systems.com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92722-4-N92bXrLQPZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92722-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92722-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03566.txt.bz2
Content-length: 504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92722
Avi Kivity <avi@cloudius-systems.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |avi@cloudius-systems.com
--- Comment #2 from Avi Kivity <avi@cloudius-systems.com> ---
Maybe those 1-byte elements generated for empty structs should be considered
padding. They certainly don't correspond to any member.
>From gcc-bugs-return-661773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 10:42:55 2019
Return-Path: <gcc-bugs-return-661773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38946 invoked by alias); 29 Nov 2019 10:42:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38896 invoked by uid 48); 29 Nov 2019 10:42:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92722] gcc considers "padding" byte of empty lambda to be uninitialized
Date: Fri, 29 Nov 2019 10:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92722-4-EEJdyrX4a3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92722-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92722-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03567.txt.bz2
Content-length: 599
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92722
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
During expansion we avoid the moves when an empty struct is being copied.
But this testcase explicitly copies the underlying bytes rather than copying
the empty struct, I don't see what the compiler could do in that case.
>From gcc-bugs-return-661774-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 10:58:16 2019
Return-Path: <gcc-bugs-return-661774-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67028 invoked by alias); 29 Nov 2019 10:58:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66365 invoked by uid 48); 29 Nov 2019 10:58:09 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92510] ICE in native_encode_rtx, at simplify-rtx.c:6272
Date: Fri, 29 Nov 2019 10:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to short_desc
Message-ID: <bug-92510-4-T3JYuFCgeq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92510-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92510-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03568.txt.bz2
Content-length: 722
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92510
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Assignee|jakub at gcc dot gnu.org |unassigned at gcc dot gnu.org
Summary|[10 Regression] ICE in |ICE in native_encode_rtx,
|native_encode_rtx, at |at simplify-rtx.c:6272
|simplify-rtx.c:6272 |
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The regression is fixed. Keeping open if Segher wants to do some further
fixes.
>From gcc-bugs-return-661775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 11:08:59 2019
Return-Path: <gcc-bugs-return-661775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38936 invoked by alias); 29 Nov 2019 11:08:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38887 invoked by uid 48); 29 Nov 2019 11:08:55 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92705] [10 Regression] ICE: Segmentation fault (in build_new_op_1)
Date: Fri, 29 Nov 2019 11:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92705-4-VbWFhs6Km0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92705-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92705-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03569.txt.bz2
Content-length: 949
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92705
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|error-recovery |
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-29
CC| |jakub at gcc dot gnu.org,
| |jason at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r277864. This isn't error-recovery, there is no error printed
before it ICEs.
Slightly shortened:
struct A {};
struct B {};
struct C { operator B*(); };
struct D { operator B*(); };
struct E : C, D { operator A*(); };
void foo(E e, int B::* pmf) { int i = e->*pmf; }
>From gcc-bugs-return-661776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 11:30:55 2019
Return-Path: <gcc-bugs-return-661776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30446 invoked by alias); 29 Nov 2019 11:30:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30241 invoked by uid 48); 29 Nov 2019 11:30:45 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92685] In IPA's execute stage create_version_clone_with_body fails with non-vNULL callers
Date: Fri, 29 Nov 2019 11:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92685-4-Mpikqsllrd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92685-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92685-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03570.txt.bz2
Content-length: 883
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92685
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Hello.
Yes, for usage of create_version_clone_with_body one needs to load GIMPLE body
of both caller and callee function.
Anyway, can you please rather write to https://gcc.gnu.org/ml/gcc/ mailing
list?
Note that we use create_version_clone_with_body mainly in IPA passes that are
not part of INSERT_PASSES_AFTER (all_regular_ipa_passes). Can you please
describe what kind of IPA pass you're intending to write? Please write to the
mailing list.
>From gcc-bugs-return-661778-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 11:35:53 2019
Return-Path: <gcc-bugs-return-661778-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38213 invoked by alias); 29 Nov 2019 11:35:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37927 invoked by uid 48); 29 Nov 2019 11:35:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92720] cc1 accepts #include /dev/stdin inline
Date: Fri, 29 Nov 2019 11:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92720-4-w0SlKVk6ov@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03572.txt.bz2
Content-length: 831
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> GCC does not check the files.
>
> >echo '\042hello botfelk\\n\042'
> This one fails for me too:
> In file included from t8.c:5:0:
> /dev/stdin: In function ‘main’:
> /dev/stdin:1:1: error: stray ‘\’ in program
> /dev/stdin:1:2: error: invalid suffix "hello" on integer constant
> /dev/stdin:1:11: error: expected ‘)’ before ‘botfelk’
> /dev/stdin:1:18: error: stray ‘\’ in program
> /dev/stdin:1:19: error: stray ‘\’ in program
> /dev/stdin:1:21: error: stray ‘\’ in program
You need to use -e for GNU echo to interpret the \042 characters.
>From gcc-bugs-return-661777-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 11:35:26 2019
Return-Path: <gcc-bugs-return-661777-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37086 invoked by alias); 29 Nov 2019 11:35:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37054 invoked by uid 48); 29 Nov 2019 11:35:22 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92720] cc1 accepts #include /dev/stdin inline
Date: Fri, 29 Nov 2019 11:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92720-4-Ha5oHUNg2L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03571.txt.bz2
Content-length: 537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Dennis Clarke from comment #0)
> This may require a bit of a dive into the specifications however
> an inline include of /dev/stdin seems wrong for some definition
> of wrong.
There's no such thing as an "inline include", the preprocessor just substitutes
the content of the named file wherever a #include directive appears.
If that file happens to be /dev/stdin then it happens to be /dev/stdin.
>From gcc-bugs-return-661779-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 11:38:17 2019
Return-Path: <gcc-bugs-return-661779-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43925 invoked by alias); 29 Nov 2019 11:38:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43872 invoked by uid 48); 29 Nov 2019 11:38:12 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92705] [10 Regression] ICE: Segmentation fault (in build_new_op_1)
Date: Fri, 29 Nov 2019 11:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92705-4-Vec7jz1itU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92705-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92705-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03573.txt.bz2
Content-length: 2584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92705
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The ICE is because conv is ck_ambig with user_conv_p set.
Looking at other conv->user_conv_p tests, e.g. reference_binding does:
if (conv->user_conv_p)
{
...
for (conversion *t = conv; t; t = next_conversion (t))
if (t->kind == ck_user
&& DECL_CONV_FN_P (t->cand->fn))
{
and doesn't expect that user_conv_p implies that ck_user will appear.
The following patch restores the previous diagnostics on the testcase, but I'm
afraid I have no idea what is right. If ck_ambig with user_conv_p set is
right, then it itself isn't ck_user and next_conversion on it is NULL.
--- gcc/cp/call.c.jj 2019-11-28 18:58:55.671297387 +0100
+++ gcc/cp/call.c 2019-11-29 12:33:04.033386816 +0100
@@ -6370,8 +6370,12 @@ build_new_op_1 (const op_location_t &loc
conv = cand->convs[0];
if (conv->user_conv_p)
{
- while (conv->kind != ck_user)
- conv = next_conversion (conv);
+ for (conversion *t = conv; t; t = next_conversion (t))
+ if (t->kind == ck_user)
+ {
+ conv = t;
+ break;
+ }
arg1 = convert_like (conv, arg1, complain);
}
@@ -6380,8 +6384,12 @@ build_new_op_1 (const op_location_t &loc
conv = cand->convs[1];
if (conv->user_conv_p)
{
- while (conv->kind != ck_user)
- conv = next_conversion (conv);
+ for (conversion *t = conv; t; t = next_conversion (t))
+ if (t->kind == ck_user)
+ {
+ conv = t;
+ break;
+ }
arg2 = convert_like (conv, arg2, complain);
}
}
@@ -6391,8 +6399,12 @@ build_new_op_1 (const op_location_t &loc
conv = cand->convs[2];
if (conv->user_conv_p)
{
- while (conv->kind != ck_user)
- conv = next_conversion (conv);
+ for (conversion *t = conv; t; t = next_conversion (t))
+ if (t->kind == ck_user)
+ {
+ conv = t;
+ break;
+ }
arg3 = convert_like (conv, arg3, complain);
}
}
>From gcc-bugs-return-661780-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 11:43:33 2019
Return-Path: <gcc-bugs-return-661780-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54349 invoked by alias); 29 Nov 2019 11:43:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54295 invoked by uid 48); 29 Nov 2019 11:43:29 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/91574] [10 Regression] ICE in types_same_for_odr at gcc/ipa-devirt.c:355 since r272037
Date: Fri, 29 Nov 2019 11:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91574-4-QPvD10Ic7C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03574.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91574
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-661781-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 11:51:30 2019
Return-Path: <gcc-bugs-return-661781-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63557 invoked by alias); 29 Nov 2019 11:51:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63497 invoked by uid 48); 29 Nov 2019 11:51:25 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92719] MacOS 10.15 Catalina build fails
Date: Fri, 29 Nov 2019 11:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget cc target_milestone cf_gccbuild
Message-ID: <bug-92719-4-gAOYbYe9jp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92719-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92719-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03575.txt.bz2
Content-length: 1455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92719
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-apple-darwin19.0.0
CC| |iains at gcc dot gnu.org
Target Milestone|--- |10.0
Build| |x86_64-apple-darwin19.0.0
--- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
please could you identify the version of Xcode and the SDK in use?
(anything less than 11.3beta is known to have problems).
you have some configuration options that don't apply to 10.15:
--enable-multilib (this would just break later)
and some that are unnecessary:
--enable-bootstrap (default)
lto in the languages (default)
It is likely the --enable-host-shared option that is causing some difficulty
here, it is rarely used/tested.
(I will try to repeat that locally)
It seems that your GMP installation is in /usr/local (or somehow found
automatically)?
This could also be a problem when using a sysroot (/usr/local is not added at
present)
see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90834#c13
could you check ---
../configure --prefix=$PWD/usr --with-sysroot=$OSX_SDK_PATH
--enable-languages=c,c++,fortran --with-gmp=/path/to/gmp/prefix
>From gcc-bugs-return-661782-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 11:54:23 2019
Return-Path: <gcc-bugs-return-661782-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65991 invoked by alias); 29 Nov 2019 11:54:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65918 invoked by uid 48); 29 Nov 2019 11:54:19 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92720] cc1 accepts #include /dev/stdin inline
Date: Fri, 29 Nov 2019 11:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92720-4-C08SlRbjo7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03576.txt.bz2
Content-length: 799
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #2)
> (In reply to Dennis Clarke from comment #0)
> > This may require a bit of a dive into the specifications however
> > an inline include of /dev/stdin seems wrong for some definition
> > of wrong.
>
> There's no such thing as an "inline include", the preprocessor just
> substitutes the content of the named file wherever a #include directive
> appears.
>
> If that file happens to be /dev/stdin then it happens to be /dev/stdin.
The actual mapping from a #include directive to a physical file is
implementation defined, so it seems OK for one compiler to refuse to do include
certain paths, and OK for another to do so.
>From gcc-bugs-return-661783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 12:02:32 2019
Return-Path: <gcc-bugs-return-661783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74461 invoked by alias); 29 Nov 2019 12:02:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73799 invoked by uid 48); 29 Nov 2019 12:02:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92705] [10 Regression] ICE: Segmentation fault (in build_new_op_1)
Date: Fri, 29 Nov 2019 12:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92705-4-99xAEldBhE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92705-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92705-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03577.txt.bz2
Content-length: 357
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92705
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Though, previously the convert_like calls were done no matter what the
conversion is, so with the above patch maybe after the if (conv->user_conv_p)
... stmts, with whatever the conv is. Not sure if it makes a difference for
anything.
>From gcc-bugs-return-661784-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 12:18:48 2019
Return-Path: <gcc-bugs-return-661784-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109023 invoked by alias); 29 Nov 2019 12:18:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108874 invoked by uid 48); 29 Nov 2019 12:18:43 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/92724] New: Can't link 9.2.0 ada with latest GCC
Date: Fri, 29 Nov 2019 12:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92724-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03578.txt.bz2
Content-length: 10023
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92724
Bug ID: 92724
Summary: Can't link 9.2.0 ada with latest GCC
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: ebotcazou at gcc dot gnu.org
Target Milestone: ---
Using latest GCC master, I can't build gcc-9 branch with it. It's very likely
caused by switch to -fno-common:
$ g++ -no-pie -g -DIN_GCC -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H
-static-libstdc++ -static-libgcc -o gnatbind ada/b_gnatb.o
ada/libgnat/a-elchha.o ada/libgnat/a-except.o ada/libgnat/ada.o ada/adaint.o
ada/ali-util.o ada/ali.o ada/alloc.o ada/argv.o ada/aspects.o ada/atree.o
ada/bcheck.o ada/binde.o ada/binderr.o ada/bindgen.o ada/bindusg.o ada/butil.o
ada/casing.o ada/cio.o ada/csets.o ada/cstreams.o ada/debug.o ada/einfo.o
ada/elists.o ada/env.o ada/err_vars.o ada/errout.o ada/erroutc.o ada/exit.o
ada/final.o ada/fmap.o ada/fname-uf.o ada/fname.o ada/libgnat/g-byorma.o
ada/libgnat/g-hesora.o ada/libgnat/g-htable.o ada/libgnat/gnat.o ada/gnatbind.o
ada/gnatvsn.o ada/hostparm.o ada/init.o ada/initialize.o ada/libgnat/interfac.o
ada/krunch.o ada/lib.o ada/link.o ada/namet.o ada/nlists.o ada/opt.o
ada/osint-b.o ada/osint.o ada/output.o ada/raise.o ada/raise-gcc.o
ada/restrict.o ada/rident.o ada/rtfinal.o ada/rtinit.o ada/libgnat/s-addope.o
ada/libgnat/s-assert.o ada/libgnat/s-carun8.o ada/libgnat/s-casuti.o
ada/libgnat/s-conca2.o ada/libgnat/s-conca3.o ada/libgnat/s-conca4.o
ada/libgnat/s-conca5.o ada/libgnat/s-conca6.o ada/libgnat/s-conca7.o
ada/libgnat/s-conca8.o ada/libgnat/s-conca9.o ada/libgnat/s-crc32.o
ada/libgnat/s-crtl.o ada/libgnat/s-excdeb.o ada/libgnat/s-except.o
ada/libgnat/s-excmac.o ada/libgnat/s-exctab.o ada/libgnat/s-htable.o
ada/libgnat/s-imenne.o ada/libgnat/s-imgenu.o ada/libgnat/s-imgint.o
ada/libgnat/s-mastop.o ada/libgnat/s-memory.o ada/libgnat/s-os_lib.o
ada/libgnat/s-parame.o ada/libgnat/s-resfil.o ada/libgnat/s-restri.o
ada/libgnat/s-secsta.o ada/libgnat/s-soflin.o ada/libgnat/s-soliin.o
ada/libgnat/s-sopco3.o ada/libgnat/s-sopco4.o ada/libgnat/s-sopco5.o
ada/libgnat/s-stache.o ada/libgnat/s-stalib.o ada/libgnat/s-stoele.o
ada/libgnat/s-strhas.o ada/libgnat/s-string.o ada/libgnat/s-strops.o
ada/libgnat/s-traent.o ada/libgnat/s-traceb.o ada/libgnat/s-unstyp.o
ada/libgnat/s-utf_32.o ada/libgnat/s-wchcnv.o ada/libgnat/s-wchcon.o
ada/libgnat/s-wchjis.o ada/libgnat/s-wchstw.o ada/scans.o ada/scil_ll.o
ada/scng.o ada/sdefault.o ada/seh_init.o ada/sem_aux.o ada/sinfo.o
ada/sinput-c.o ada/sinput.o ada/snames.o ada/stand.o ada/stringt.o ada/style.o
ada/styleg.o ada/stylesw.o ada/switch-b.o ada/switch.o ada/libgnat/system.o
ada/table.o ada/targext.o ada/targparm.o ada/tree_io.o ada/types.o ada/uintp.o
ada/uname.o ada/urealp.o ada/widechar.o ggc-none.o libcommon-target.a
libcommon.a ../libcpp/libcpp.a ../libbacktrace/.libs/libbacktrace.a
../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -g
mv -f Tlto-wrapper lto-wrapper
/usr/bin/ld: ada/ali.o: in function `ali__scan_ali':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/ali.adb:2767: undefined
reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/ali.adb:2767: undefined
reference to `__gnat_end_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/ali.adb:1587: undefined
reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/ali.adb:1587: undefined
reference to `__gnat_end_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/ali.adb:2805: undefined
reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/ali.adb:2805: undefined
reference to `__gnat_end_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/ali.adb:1416: undefined
reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/ali.adb:1416: undefined
reference to `__gnat_end_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/ali.adb:1552: undefined
reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/ali.adb:1552: undefined
reference to `__gnat_end_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/ali.adb:2767: undefined
reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/gnatbind.o: in function `_ada_gnatbind':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/gnatbind.adb:899:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/gnatbind.adb:899:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/output.o: in function `output__flush_buffer':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/output.adb:163:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/output.adb:163:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/restrict.o: in function
`restrict__check_restriction__update_restrictions':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/restrict.adb:482:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/restrict.adb:482:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/libgnat/s-os_lib.o: in function `system__os_lib__gm_split':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/libgnat/s-os_lib.adb:1393:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/libgnat/s-os_lib.adb:1393:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/libgnat/s-os_lib.o: in function
`system__os_lib__create_temp_file_internal':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/libgnat/s-os_lib.adb:920:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/libgnat/s-os_lib.adb:920:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/libgnat/s-os_lib.o: in function `system__os_lib__copy_file':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/libgnat/s-os_lib.adb:600:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/libgnat/s-os_lib.adb:600:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/libgnat/s-resfil.o: in function
`system__response_file__arguments_from__recurse':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/libgnat/s-resfil.adb:486:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/libgnat/s-resfil.adb:486:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/libgnat/s-resfil.o: in function
`system__response_file__arguments_from':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/libgnat/s-resfil.adb:509:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/libgnat/s-resfil.adb:509:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/libgnat/s-secsta.o: in function
`system__secondary_stack__allocate_dynamic__allocate_new_chunk':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/libgnat/s-secsta.adb:199:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/libgnat/s-secsta.adb:199:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/switch-b.o: in function
`switch__b__scan_binder_switches__get_stack_size':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/switch-b.adb:110:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/switch-b.adb:110:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/switch-b.o: in function `switch__b__scan_binder_switches':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/switch-b.adb:530:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/switch-b.adb:530:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/targparm.o: in function `targparm__get_target_parameters':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/targparm.adb:431:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/targparm.adb:431:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/tree_io.o: in function `tree_io__tree_read_terminate':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/tree_io.adb:380:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/tree_io.adb:380:
undefined reference to `__gnat_end_handler_v1'
/usr/bin/ld: ada/widechar.o: in function `widechar__scan_wide':
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/widechar.adb:142:
undefined reference to `__gnat_begin_handler_v1'
/usr/bin/ld:
/home/marxin/Programming/gcc2/objdir/gcc/../../gcc/ada/widechar.adb:142:
undefined reference to `__gnat_end_handler_v1'
collect2: error: ld returned 1 exit status
make: *** [../../gcc/ada/gcc-interface/Make-lang.in:664: gnatbind] Error 1
make: *** Waiting for unfinished jobs....
^Cmake: *** [Makefile:1116: gimple-match.o] Interrupt
make: *** [Makefile:1116: insn-emit.o] Interrupt
make: *** [Makefile:1116: generic-match.o] Interrupt
>From gcc-bugs-return-661785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 12:19:26 2019
Return-Path: <gcc-bugs-return-661785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110119 invoked by alias); 29 Nov 2019 12:19:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110067 invoked by uid 55); 29 Nov 2019 12:19:22 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/84963] [8 Regression] ICE in get_constraint_for_ssa_var, at tree-ssa-structalias.c:2955
Date: Fri, 29 Nov 2019 12:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84963-4-O0BswwR1mM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84963-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03579.txt.bz2
Content-length: 546
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84963
--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Fri Nov 29 12:18:50 2019
New Revision: 278836
URL: https://gcc.gnu.org/viewcvs?rev=278836&root=gcc&view=rev
Log:
Fix testcase - was missing -fopenacc
PR ipa/84963
* gfortran.dg/goacc/pr84963.f90: Use dg-additional-options not
dg-options as otherwise -fopenacc is not used.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/goacc/pr84963.f90
>From gcc-bugs-return-661786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 12:20:30 2019
Return-Path: <gcc-bugs-return-661786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115616 invoked by alias); 29 Nov 2019 12:20:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115526 invoked by uid 48); 29 Nov 2019 12:20:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91825] [10 regression] Bogus -Wmaybe-uninitialized with r275744 breaks bootstrap
Date: Fri, 29 Nov 2019 12:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-91825-4-dTISnh5aDr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91825-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03580.txt.bz2
Content-length: 9841
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91825
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Slightly tweaked, so that no other warnings are reported on it with -O2 -Wall,
except this -Wmaybe-uninitialized starting with the r277864 change and nothing
before:
typedef struct rtx_def *rtx;
enum machine_mode {
E_VOIDmode, E_BLKmode, E_CCmode, E_CCFPmode, E_CCFPEmode, E_CC_SWPmode,
E_CC_NZCmode, E_CC_NZmode,
E_CC_Zmode, E_CC_Cmode, E_CC_ADCmode, E_CC_Vmode, E_BImode, E_QImode,
E_HImode, E_SImode, E_DImode,
E_TImode, E_OImode, E_CImode, E_XImode, E_QQmode, E_HQmode, E_SQmode,
E_DQmode, E_TQmode, E_UQQmode,
E_UHQmode, E_USQmode, E_UDQmode, E_UTQmode, E_HAmode, E_SAmode, E_DAmode,
E_TAmode, E_UHAmode, E_USAmode,
E_UDAmode, E_UTAmode, E_HFmode, E_SFmode, E_DFmode, E_TFmode, E_SDmode,
E_DDmode, E_TDmode, E_CQImode,
E_CHImode, E_CSImode, E_CDImode, E_CTImode, E_COImode, E_CCImode, E_CXImode,
E_HCmode, E_SCmode, E_DCmode,
E_TCmode, E_V8QImode, E_V4HImode, E_V2SImode, E_V16QImode, E_V8HImode,
E_V4SImode, E_V2DImode, E_VNx2TImode,
E_VNx3TImode, E_VNx4TImode, E_VNx2OImode, E_V2HFmode, E_V4HFmode, E_V2SFmode,
E_V2DFmode, NUM_MACHINE_MODES
};
template <int N> struct A { int coeffs[N]; };
template <int N> class C : public A<N> {
public:
template <typename C0> C(const C0 &);
};
machine_mode mode_size_inline_mode, emit_store_flag_1_target_mode;
A<2> mode_size[1];
struct B {
enum from_int {};
};
extern const char mode_class[NUM_MACHINE_MODES];
template <typename T> T as_a(machine_mode);
class scalar_int_mode {
public:
scalar_int_mode() {}
scalar_int_mode(B::from_int p1) : m_mode(machine_mode(p1)) {}
operator machine_mode() { return m_mode; }
machine_mode m_mode;
} mode_to_bytes_mode;
scalar_int_mode word_mode;
template <typename T> bool is_int_mode(machine_mode p1, T p2) {
if (mode_class[p1]) {
*p2 = B::from_int(p1);
return true;
}
return false;
}
enum insn_code {};
enum rtx_code { GE, LE, LT };
struct rtx_def {
rtx_code code;
machine_mode mode;
};
rtx const_int_rtx_63, const_int_rtx_64, emit_store_flag_1_subtarget,
emit_store_flag_1_tem, emit_store_flag_1_op00, emit_store_flag_1_op01,
emit_store_flag_1_op0h, emit_store_flag_1_target, emit_store_flag_1_op0,
emit_store_flag_1_op1;
enum tree_code { RSHIFT_EXPR };
enum optab_tag { and_optab, ior_optab, one_cmpl_optab };
enum optab_methods { OPTAB_DIRECT };
insn_code emit_store_flag_1_icode;
rtx_code emit_store_flag_1_code;
int emit_store_flag_1_unsignedp, emit_store_flag_1_normalizep;
short emit_store_flag_1___trans_tmp_24, emit_store_flag_1___trans_tmp_23;
bool iterate_p();
inline __attribute__((__always_inline__)) C<2> mode_size_inline() {
A<2> mode_size;
switch (mode_size_inline_mode) {
case E_VOIDmode: return 0;
case E_BLKmode: return 0;
case E_CCmode: return 4;
case E_CCFPmode: return 4;
case E_CCFPEmode: return 4;
case E_CC_SWPmode: return 4;
case E_CC_NZCmode: return 4;
case E_CC_NZmode: return 4;
case E_CC_Zmode: return 4;
case E_CC_Cmode: return 4;
case E_CC_ADCmode: return 4;
case E_CC_Vmode: return 4;
case E_BImode: return 1;
case E_QImode: return 1;
case E_HImode: return 2;
case E_SImode: return 4;
case E_DImode: return 8;
case E_TImode: return 6;
case E_OImode: return 2;
case E_CImode: return 8;
case E_XImode: return 4;
case E_QQmode: return 1;
case E_HQmode: return 2;
case E_SQmode: return 4;
case E_DQmode: return 8;
case E_TQmode: return 6;
case E_UQQmode: return 1;
case E_UHQmode: return 2;
case E_USQmode: return 4;
case E_UDQmode: return 8;
case E_UTQmode: return 6;
case E_HAmode: return 2;
case E_SAmode: return 4;
case E_DAmode: return 8;
case E_TAmode: return 6;
case E_UHAmode: return 2;
case E_USAmode: return 4;
case E_UDAmode: return 8;
case E_UTAmode: return 6;
case E_HFmode: return 2;
case E_SFmode: return 4;
case E_DFmode: return 8;
case E_TFmode: return 6;
case E_SDmode: return 4;
case E_DDmode: return 8;
case E_TDmode: return 6;
case E_CQImode: return 2;
case E_CHImode: return 4;
case E_CSImode: return 8;
case E_CDImode: return 6;
case E_CTImode: return 2;
case E_COImode: return 4;
case E_CCImode: return 6;
case E_CXImode: return 8;
case E_HCmode: return 4;
case E_SCmode: return 8;
case E_DCmode: return 6;
case E_TCmode: return 2;
case E_V8QImode: return 8;
case E_V4HImode: return 8;
case E_V2SImode: return 8;
case E_V16QImode: return 6;
case E_V8HImode: return 6;
case E_V4SImode: return 6;
case E_V2DImode: return 6;
case E_VNx2TImode: return 2;
case E_VNx3TImode: return 8;
case E_VNx4TImode: return 4;
case E_VNx2OImode: return 4;
case E_V2HFmode: return 4;
case E_V4HFmode: return 8;
case E_V2SFmode: return 8;
case E_V2DFmode: return 6;
default: return mode_size;
}
}
inline __attribute__((always_inline)) C<2> mode_to_bytes() {
return mode_to_bytes_mode ? mode_size_inline() : mode_size[0];
}
inline __attribute__((always_inline)) C<2> mode_to_bits() {
mode_to_bytes();
return 0;
}
inline __attribute__((always_inline)) short GET_MODE_SIZE(scalar_int_mode) {
return mode_to_bytes().coeffs[0];
}
inline __attribute__((always_inline)) short GET_MODE_BITSIZE(scalar_int_mode) {
return mode_to_bits().coeffs[0];
}
void get_wider();
void simplify_gen_subreg(machine_mode, rtx, machine_mode, C<2>);
bool val_signbit_known_set_p(machine_mode, long);
rtx emit_store_flag(rtx, rtx_code, rtx, rtx, machine_mode, int, int);
rtx expand_shift(tree_code, machine_mode, rtx, C<2>, rtx, int);
insn_code optab_handler();
void expand_binop(machine_mode, optab_tag, rtx, rtx, rtx, int, optab_methods);
rtx expand_unop(machine_mode, optab_tag, rtx, rtx, int);
void convert_move(rtx, rtx, int);
rtx convert_modes(machine_mode, machine_mode, rtx, int);
rtx emit_cstore();
rtx emit_store_flag_1(machine_mode p1) {
scalar_int_mode int_mode;
emit_store_flag_1___trans_tmp_23 = mode_to_bits().coeffs[0];
if (is_int_mode(p1, &int_mode) && (emit_store_flag_1_op0->code ||
emit_store_flag_1_op0))
if (emit_store_flag_1_code && const_int_rtx_63) {
machine_mode __trans_tmp_3 = word_mode, __trans_tmp_4 = int_mode,
__trans_tmp_5 = word_mode, __trans_tmp_6 = int_mode,
__trans_tmp_7 = word_mode;
simplify_gen_subreg(__trans_tmp_3, emit_store_flag_1_op0, __trans_tmp_4,
0);
simplify_gen_subreg(__trans_tmp_5, emit_store_flag_1_op0, __trans_tmp_6,
8);
expand_binop(__trans_tmp_7, const_int_rtx_64 ? ior_optab : and_optab,
emit_store_flag_1_op00, emit_store_flag_1_op01, 0,
emit_store_flag_1_unsignedp, OPTAB_DIRECT);
if (emit_store_flag_1_tem) {
machine_mode __trans_tmp_8 = word_mode;
emit_store_flag(0, emit_store_flag_1_code, emit_store_flag_1_tem,
emit_store_flag_1_op1, __trans_tmp_8,
emit_store_flag_1_unsignedp,
emit_store_flag_1_normalizep);
}
}
if ((emit_store_flag_1_code || emit_store_flag_1_code) && const_int_rtx_64)
;
machine_mode __trans_tmp_10 __attribute__((unused)) = int_mode;
machine_mode __trans_tmp_12 = word_mode, __trans_tmp_14 = word_mode;
emit_store_flag_1_tem = emit_store_flag(
0, emit_store_flag_1_code, emit_store_flag_1_op0h, emit_store_flag_1_op1,
__trans_tmp_12, emit_store_flag_1_unsignedp,
emit_store_flag_1_target_mode ||
emit_store_flag_1_tem->mode == emit_store_flag_1_target_mode);
bool __trans_tmp_13 = val_signbit_known_set_p(
__trans_tmp_14, emit_store_flag_1_normalizep ?: 1);
convert_move(emit_store_flag_1_target, 0, __trans_tmp_13);
if (emit_store_flag_1_op1 == const_int_rtx_64 &&
(emit_store_flag_1_code == LT || emit_store_flag_1_code == GE) &&
is_int_mode(p1, &int_mode)) {
scalar_int_mode int_target_mode =
as_a<scalar_int_mode>(emit_store_flag_1_target_mode);
emit_store_flag_1___trans_tmp_24 = mode_to_bytes().coeffs[0];
if (GET_MODE_SIZE(int_mode)) {
machine_mode __trans_tmp_15 = int_target_mode, __trans_tmp_16 = int_mode;
emit_store_flag_1_op0 = convert_modes(__trans_tmp_15, __trans_tmp_16,
emit_store_flag_1_op0, 0);
}
int_mode = int_target_mode;
if (int_mode)
emit_store_flag_1_subtarget = 0;
if (emit_store_flag_1_code) {
machine_mode __trans_tmp_17 = int_mode, __trans_tmp_18 = int_mode;
emit_store_flag_1_op0 =
expand_unop(__trans_tmp_17, one_cmpl_optab, emit_store_flag_1_op0,
emit_store_flag_1_subtarget, 0);
GET_MODE_BITSIZE(int_mode);
emit_store_flag_1_normalizep = 1;
emit_store_flag_1_op0 =
expand_shift(RSHIFT_EXPR, __trans_tmp_18, emit_store_flag_1_op0, 1,
emit_store_flag_1_subtarget, 1);
}
if ((int_mode = int_target_mode)) {
machine_mode __trans_tmp_20 = int_target_mode, __trans_tmp_21 = int_mode;
emit_store_flag_1_op0 = convert_modes(__trans_tmp_20, __trans_tmp_21,
emit_store_flag_1_op0, 0);
}
}
for (; iterate_p();)
emit_store_flag_1_icode = optab_handler();
if (emit_store_flag_1_icode)
get_wider();
rtx tem = emit_cstore();
if (tem)
if (mode_class[p1])
tem = emit_cstore();
if (tem)
return tem;
return 0;
}
>From gcc-bugs-return-661787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 12:28:10 2019
Return-Path: <gcc-bugs-return-661787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 403 invoked by alias); 29 Nov 2019 12:28:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 366 invoked by uid 55); 29 Nov 2019 12:28:05 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/84963] [8 Regression] ICE in get_constraint_for_ssa_var, at tree-ssa-structalias.c:2955
Date: Fri, 29 Nov 2019 12:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84963-4-cmvtLni6ku@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84963-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03581.txt.bz2
Content-length: 670
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84963
--- Comment #7 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Fri Nov 29 12:27:34 2019
New Revision: 278838
URL: https://gcc.gnu.org/viewcvs?rev=278838&root=gcc&view=rev
Log:
Fix testcase - was missing -fopenacc
Backport from mainline
2019-11-29 Tobias Burnus <tobias@codesourcery.com>
PR ipa/84963
* gfortran.dg/goacc/pr84963.f90: Use dg-additional-options not
dg-options as otherwise -fopenacc is not used.
Modified:
branches/gcc-9-branch/gcc/testsuite/ChangeLog
branches/gcc-9-branch/gcc/testsuite/gfortran.dg/goacc/pr84963.f90
>From gcc-bugs-return-661788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 12:32:59 2019
Return-Path: <gcc-bugs-return-661788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9808 invoked by alias); 29 Nov 2019 12:32:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9752 invoked by uid 48); 29 Nov 2019 12:32:56 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/91997] pretty printers: The __node_type type alias in _Hashtable is not available
Date: Fri, 29 Nov 2019 12:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91997-4-Fwql7TgWbT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91997-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91997-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03582.txt.bz2
Content-length: 273
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91997
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The problem is not missing debuginfo, it's a GDB bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=25234
I have a workaround for libstdc++ though.
>From gcc-bugs-return-661789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 12:40:44 2019
Return-Path: <gcc-bugs-return-661789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104178 invoked by alias); 29 Nov 2019 12:40:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104133 invoked by uid 48); 29 Nov 2019 12:40:40 -0000
From: "anbu1024.me at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92725] New: ICE: Segmentation fault during GIMPLE pass
Date: Fri, 29 Nov 2019 12:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anbu1024.me at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92725-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03583.txt.bz2
Content-length: 2210
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92725
Bug ID: 92725
Summary: ICE: Segmentation fault during GIMPLE pass
Product: gcc
Version: 8.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: anbu1024.me at gmail dot com
Target Milestone: ---
$ cat 0.c
int global ;
void foo() ;
__attribute__((returns_twice)) int bar() ;
void baz(int, int);
void main ( )
{
int x;
for ( ; ; )
foo();
baz(bar(), global);
}
--------------------------------------------------------------------------------
$ gcc-snapshot8 --version
gcc (GCC) 8.3.1 20191122
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
--------------------------------------------------------------------------------
$ gcc-snapshot8 0.c
during GIMPLE pass: *build_cgraph_edges
0.c: In function ‘main’:
0.c:10:6: internal compiler error: Segmentation fault
void main ( )
^~~~
0xa654af crash_signal
../../gcc-8-20191122/gcc/toplev.c:325
0x8275a0 useless_type_conversion_p(tree_node*, tree_node*)
../../gcc-8-20191122/gcc/gimple-expr.c:70
0x70606d types_compatible_p
../../gcc-8-20191122/gcc/gimple-expr.h:66
0x70606d gimple_check_call_args
../../gcc-8-20191122/gcc/cgraph.c:3798
0x70606d gimple_check_call_matching_types(gimple*, tree_node*, bool)
../../gcc-8-20191122/gcc/cgraph.c:3848
0x708346 symbol_table::create_edge(cgraph_node*, cgraph_node*, gcall*,
profile_count, bool)
../../gcc-8-20191122/gcc/cgraph.c:879
0x708544 cgraph_node::create_edge(cgraph_node*, gcall*, profile_count)
../../gcc-8-20191122/gcc/cgraph.c:914
0x70df6e execute
../../gcc-8-20191122/gcc/cgraphbuild.c:322
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-661790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 12:42:19 2019
Return-Path: <gcc-bugs-return-661790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106356 invoked by alias); 29 Nov 2019 12:42:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106285 invoked by uid 48); 29 Nov 2019 12:42:15 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92713] ICE in libsupc++ building an offload compiler targeting amdgcn-unknown-amdhsa
Date: Fri, 29 Nov 2019 12:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92713-4-ApSIN3C8rN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03584.txt.bz2
Content-length: 736
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92713
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Notes from the #gcc IRC:
* Workaround: --enable-languages=c,lto,fortran – i.e. do not build the C++
compiler for AMD GCN
* Note: the offload compiler doesn't need any frontends (but lto)
* Only (offloaded) code which does not need libstc++ will work.
* For C++ support on GCN itself: a few features are currently missing
such as exceptions
>From gcc-bugs-return-661791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 12:49:05 2019
Return-Path: <gcc-bugs-return-661791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116963 invoked by alias); 29 Nov 2019 12:49:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116895 invoked by uid 48); 29 Nov 2019 12:49:01 -0000
From: "charlet at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/92724] Can't link 9.2.0 ada with latest GCC
Date: Fri, 29 Nov 2019 12:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: charlet at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution target_milestone
Message-ID: <bug-92724-4-R0LE6LKGWk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92724-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92724-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03585.txt.bz2
Content-length: 737
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92724
Arnaud Charlet <charlet at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |charlet at gcc dot gnu.org
Resolution|--- |INVALID
Target Milestone|--- |10.0
--- Comment #1 from Arnaud Charlet <charlet at gcc dot gnu.org> ---
You cannot build GNAT with a more recent version of GNAT in general, as
explained in https://gcc.gnu.org/install/prerequisites.html.
This PR is an occurrence of such incompatibility.
>From gcc-bugs-return-661792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 12:57:26 2019
Return-Path: <gcc-bugs-return-661792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44043 invoked by alias); 29 Nov 2019 12:57:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43980 invoked by uid 48); 29 Nov 2019 12:57:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91825] [10 regression] Bogus -Wmaybe-uninitialized with r275744 breaks bootstrap
Date: Fri, 29 Nov 2019 12:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91825-4-01ARyjSJu0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91825-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03586.txt.bz2
Content-length: 303
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91825
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Though, I'm afraid the reduced testcases are bad, because it doesn't reproduce
without the incorrect __trans_tmp_10 that uses int_mode even outside of code
where it is initialized.
>From gcc-bugs-return-661793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 12:59:36 2019
Return-Path: <gcc-bugs-return-661793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47952 invoked by alias); 29 Nov 2019 12:59:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47913 invoked by uid 48); 29 Nov 2019 12:59:32 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92725] ICE: Segmentation fault during GIMPLE pass
Date: Fri, 29 Nov 2019 12:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work everconfirmed cf_known_to_fail
Message-ID: <bug-92725-4-XBeA2tnqxi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92725-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92725-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03587.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92725
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-29
Known to work| |10.0, 9.1.0
Ever confirmed|0 |1
Known to fail| |7.1.0, 8.1.0, 8.3.1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. I think we have a duplicate for this, it works on the GCC 9 branch.
>From gcc-bugs-return-661794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:05:32 2019
Return-Path: <gcc-bugs-return-661794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46869 invoked by alias); 29 Nov 2019 13:05:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46826 invoked by uid 55); 29 Nov 2019 13:05:27 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92710] [9/10 Regression] Vectoriser generates invalid simd call for bool arguments
Date: Fri, 29 Nov 2019 13:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92710-4-Fgv5tZA7sE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92710-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92710-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03588.txt.bz2
Content-length: 1295
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92710
--- Comment #2 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Fri Nov 29 13:04:56 2019
New Revision: 278839
URL: https://gcc.gnu.org/viewcvs?rev=278839&root=gcc&view=rev
Log:
Don't pass booleans as mask types to simd clones (PR 92710)
In this PR we assigned a vector mask type to the result of a comparison
and then tried to pass that mask type to a simd clone, which expected
a normal (non-mask) type instead.
This patch simply punts on call arguments that have a mask type.
A better fix would be to pattern-match the comparison to a COND_EXPR,
like we would if the comparison was stored to memory, but doing that
isn't gcc 9 or 10 material.
Note that this doesn't affect x86_64-linux-gnu because the ABI promotes
bool arguments to ints.
2019-11-29 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR tree-optimization/92710
* tree-vect-stmts.c (vectorizable_simd_clone_call): Reject
vector mask arguments.
gcc/testsuite/
PR tree-optimization/92710
* gcc.dg/vect/pr92710.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/vect/pr92710.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-vect-stmts.c
>From gcc-bugs-return-661795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:17:07 2019
Return-Path: <gcc-bugs-return-661795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64496 invoked by alias); 29 Nov 2019 13:17:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64451 invoked by uid 55); 29 Nov 2019 13:17:03 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/84963] [8 Regression] ICE in get_constraint_for_ssa_var, at tree-ssa-structalias.c:2955
Date: Fri, 29 Nov 2019 13:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84963-4-anTInVpHeC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84963-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03589.txt.bz2
Content-length: 670
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84963
--- Comment #8 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Fri Nov 29 13:16:31 2019
New Revision: 278840
URL: https://gcc.gnu.org/viewcvs?rev=278840&root=gcc&view=rev
Log:
Fix testcase - was missing -fopenacc
Backport from mainline
2019-11-29 Tobias Burnus <tobias@codesourcery.com>
PR ipa/84963
* gfortran.dg/goacc/pr84963.f90: Use dg-additional-options not
dg-options as otherwise -fopenacc is not used.
Modified:
branches/gcc-8-branch/gcc/testsuite/ChangeLog
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/goacc/pr84963.f90
>From gcc-bugs-return-661796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:26:50 2019
Return-Path: <gcc-bugs-return-661796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120306 invoked by alias); 29 Nov 2019 13:26:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120255 invoked by uid 48); 29 Nov 2019 13:26:45 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92726] New: OpenACC: 'NULL'-in -> no-op, and/or 'NULL'-out
Date: Fri, 29 Nov 2019 13:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92726-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03590.txt.bz2
Content-length: 652
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92726
Bug ID: 92726
Summary: OpenACC: 'NULL'-in -> no-op, and/or 'NULL'-out
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: openacc
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
OpenACC is being clarified that when you pass 'NULL' into data clauses, or
runtime API functions, that means no-op, and/or a 'NULL' return value.
>From gcc-bugs-return-661797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:29:52 2019
Return-Path: <gcc-bugs-return-661797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48251 invoked by alias); 29 Nov 2019 13:29:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48221 invoked by uid 48); 29 Nov 2019 13:29:48 -0000
From: "david at westcontrol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] New: Idea for better error messages
Date: Fri, 29 Nov 2019 13:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: david at westcontrol dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03591.txt.bz2
Content-length: 1799
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
Bug ID: 92727
Summary: Idea for better error messages
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: david at westcontrol dot com
Target Milestone: ---
Consider this code:
#include <vector>
#include <memory>
class Y {int i;};
class X {
std::unique_ptr<Y> sp;
int i;
};
int main() {
std::vector<X> v;
X x;
v.push_back(x); // Line A
// v.push_back(std::move(x)); // Line B
}
It is a simple mistake - class X has a unique_ptr and can't be copied, but the
push_back tries to copy it.
The errors generated, however, contain a lot of unhelpful information about
allocators for the vector. They hide the useful part of the messages, which
is:
note: 'X::X(const X&)' is implicitly deleted because the default definition
would be ill-formed
It is an extra note, rather than the error message, but is key for the user to
identify the problem.
Would it be possible to hide the messages concerning the allocator here? In
general, would it be possible to hide the messages that deal with template
parameters that are unchanged from the default? That would let the user see
messages that are relevant to the code /they/ have written, rather than
implementation details in the libraries and headers.
Even better, in this case, would be a hint that the user needs a std::move, as
shown in line B.
(Yes, I know I may be asking for the impossible here, or at least for the very
difficult. But it is the kind of thing that makes C++ development harder than
it should be.)
>From gcc-bugs-return-661798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:30:42 2019
Return-Path: <gcc-bugs-return-661798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49519 invoked by alias); 29 Nov 2019 13:30:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49348 invoked by uid 55); 29 Nov 2019 13:30:25 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92476] [10 regression] SEGV in cgraph_edge_brings_value_p
Date: Fri, 29 Nov 2019 13:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mjambor at suse dot cz
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92476-4-92ePX26djr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92476-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92476-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03592.txt.bz2
Content-length: 1041
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92476
--- Comment #5 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Author: jamborm
Date: Fri Nov 29 13:29:35 2019
New Revision: 278841
URL: https://gcc.gnu.org/viewcvs?rev=278841&root=gcc&view=rev
Log:
ipa-cp: Avoid ICEs when looking at expanded thunks and unoptimized functions
2019-11-29 Martin Jambor <mjambor@suse.cz>
PR ipa/92476
* ipa-cp.c (set_single_call_flag): Set node_calling_single_call in
the summary only if the summary exists.
(find_more_scalar_values_for_callers_subset): Check node_dead in
the summary only if the summary exists.
(ipcp_store_bits_results): Ignore nodes without lattices.
(ipcp_store_vr_results): Likewise.
* cgraphclones.c: Include ipa-fnsummary.h and ipa-prop.h and the
header files required by them.
(cgraph_node::expand_all_artificial_thunks): Analyze expanded thunks.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/cgraphclones.c
trunk/gcc/ipa-cp.c
>From gcc-bugs-return-661799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:34:37 2019
Return-Path: <gcc-bugs-return-661799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61173 invoked by alias); 29 Nov 2019 13:34:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61042 invoked by uid 48); 29 Nov 2019 13:34:33 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91003] [10 Regression] ICE when compiling LAPACK (CGEGV) with optimization
Date: Fri, 29 Nov 2019 13:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-91003-4-Ox1yhTD1a4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91003-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91003-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03593.txt.bz2
Content-length: 1394
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91003
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rsandifo at gcc dot gnu.org
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
So this is another "boolean" case. In vect_get_constant_vectors we run into
/* ??? SLP analysis should compute the vector type for the
constant / invariant and store it in the SLP node. */
tree op = op_node->ops[0];
/* Check if vector type is a boolean vector. */
tree stmt_vectype = STMT_VINFO_VECTYPE (stmt_vinfo);
if (VECT_SCALAR_BOOLEAN_TYPE_P (TREE_TYPE (op))
&& vect_mask_constant_operand_p (stmt_vinfo))
vector_type = truth_type_for (stmt_vectype);
else
vector_type = get_vectype_for_scalar_type (vinfo, TREE_TYPE (op), op_node);
for
h_18 = _129 ? 1 : 0;
with unsigned boolean (kind==4) typed result/then/else values (SImode).
IIRC I couldn't simply remove this and rely on get_vectype_for_scalar_type
to do the right thing (TM) in general. Plus we don't have a stmt-info
for the constant operands (but we do now have an SLP node for them).
I hope Richards patches improve things here but I don't remember them
touching this particular place.
>From gcc-bugs-return-661800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:35:38 2019
Return-Path: <gcc-bugs-return-661800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62813 invoked by alias); 29 Nov 2019 13:35:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62748 invoked by uid 48); 29 Nov 2019 13:35:34 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 13:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92712-4-7RhI0TvKbJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03594.txt.bz2
Content-length: 1078
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |law at gcc dot gnu.org,
| |uros at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I don't think the testcase is actually very good, because it uses volatile that
asks the compiler not to optimize that part.
But it can be reproduced with:
static int func_base(int t, const int v) {
int x = 0;
for (int i = 0; i < t; ++i) x += v;
return x;
}
int func_default(int t, const int v) {
return func_base(t, v);
}
int func_assumed(int t, const int v) {
if (t < 0) __builtin_unreachable();
return func_base(t, v);
}
too. The first change in func_assumed was r233207 and the -1;mul;add instead
of mul appeared with r263652.
>From gcc-bugs-return-661801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:37:22 2019
Return-Path: <gcc-bugs-return-661801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67769 invoked by alias); 29 Nov 2019 13:37:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64743 invoked by uid 55); 29 Nov 2019 13:37:18 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92476] [10 regression] SEGV in cgraph_edge_brings_value_p
Date: Fri, 29 Nov 2019 13:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mjambor at suse dot cz
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92476-4-ZanHlCfGMp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92476-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92476-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03595.txt.bz2
Content-length: 557
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92476
--- Comment #6 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Author: jamborm
Date: Fri Nov 29 13:36:47 2019
New Revision: 278842
URL: https://gcc.gnu.org/viewcvs?rev=278842&root=gcc&view=rev
Log:
Add an x86_64 test for PR 92476
2019-11-29 Martin Jambor <mjambor@suse.cz>
PR ipa/92476
* g++.dg/lto/pr92476_[01].C: New test.
Added:
trunk/gcc/testsuite/g++.dg/lto/pr92476_0.C
trunk/gcc/testsuite/g++.dg/lto/pr92476_1.C
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:42:24 2019
Return-Path: <gcc-bugs-return-661802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20265 invoked by alias); 29 Nov 2019 13:42:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20210 invoked by uid 48); 29 Nov 2019 13:42:20 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92711] GCC 10 libxul.so -fprofile-generate binary is 360MB while clang needs only 163MB.
Date: Fri, 29 Nov 2019 13:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92711-4-xntDxH17iD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03596.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92711
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
One particular change that has happened in the GCC 10 devel cycle is that we
started using TOP N counters for indirect calls and value profiling. Right now,
we track 4 key:value pairs for each counter plus one counter for total number
of executions.
>From gcc-bugs-return-661803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:43:46 2019
Return-Path: <gcc-bugs-return-661803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22512 invoked by alias); 29 Nov 2019 13:43:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22426 invoked by uid 48); 29 Nov 2019 13:43:40 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92476] [10 regression] SEGV in cgraph_edge_brings_value_p
Date: Fri, 29 Nov 2019 13:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution assigned_to
Message-ID: <bug-92476-4-OaIPvqp5rJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92476-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92476-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03597.txt.bz2
Content-length: 588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92476
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
CC| |jamborm at gcc dot gnu.org
Resolution|--- |FIXED
Assignee|mjambor at suse dot cz |jamborm at gcc dot gnu.org
--- Comment #7 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-661804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:48:57 2019
Return-Path: <gcc-bugs-return-661804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39633 invoked by alias); 29 Nov 2019 13:48:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39566 invoked by uid 48); 29 Nov 2019 13:48:53 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91003] [10 Regression] ICE when compiling LAPACK (CGEGV) with optimization
Date: Fri, 29 Nov 2019 13:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-91003-4-9TbIreAfVo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91003-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91003-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03598.txt.bz2
Content-length: 324
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91003
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 47396
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47396&action=edit
untested patch
The following fixes the testcase but possibly makes the issue just harder to
trigger.
>From gcc-bugs-return-661805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:49:40 2019
Return-Path: <gcc-bugs-return-661805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40739 invoked by alias); 29 Nov 2019 13:49:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40624 invoked by uid 55); 29 Nov 2019 13:49:32 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92711] GCC 10 libxul.so -fprofile-generate binary is 360MB while clang needs only 163MB.
Date: Fri, 29 Nov 2019 13:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92711-4-aYh2v36qQQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03599.txt.bz2
Content-length: 207
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92711
--- Comment #6 from Jan Hubicka <hubicka at ucw dot cz> ---
With GCC9 like inliner parameters I get 308MB binary, so it is still
somehwat bigger.
Honza
>From gcc-bugs-return-661806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:50:38 2019
Return-Path: <gcc-bugs-return-661806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42908 invoked by alias); 29 Nov 2019 13:50:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42845 invoked by uid 48); 29 Nov 2019 13:50:34 -0000
From: "joel.hutton at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92391] gcc.dg/vect/bb-slp-40.c FAILs
Date: Fri, 29 Nov 2019 13:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joel.hutton at arm dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92391-4-mzMvFEyIP8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92391-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92391-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03600.txt.bz2
Content-length: 211
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92391
--- Comment #13 from Joel Hutton <joel.hutton at arm dot com> ---
This appears to no longer be failing in the latest 'gcc-testresults' can this
be closed?
>From gcc-bugs-return-661807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 13:57:48 2019
Return-Path: <gcc-bugs-return-661807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91549 invoked by alias); 29 Nov 2019 13:57:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91484 invoked by uid 48); 29 Nov 2019 13:57:44 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92711] GCC 10 libxul.so -fprofile-generate binary is 360MB while clang needs only 163MB.
Date: Fri, 29 Nov 2019 13:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92711-4-MOYa5JeJUS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03601.txt.bz2
Content-length: 370
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92711
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #6)
> With GCC9 like inliner parameters I get 308MB binary, so it is still
> somehwat bigger.
>
> Honza
I would try to set:
#define GCOV_TOPN_VALUES 1
then you should see the different of TOP N counters.
>From gcc-bugs-return-661808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:03:01 2019
Return-Path: <gcc-bugs-return-661808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127251 invoked by alias); 29 Nov 2019 14:03:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127143 invoked by uid 48); 29 Nov 2019 14:02:57 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 14:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-jn0MjybyGi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03602.txt.bz2
Content-length: 1512
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Before the first revision mentioned above *.optimized dump contained just t *
v, the second one doesn't change anything in *.optimized and is a RTL costing
matter.
_4 = (unsigned int) t_1(D);
_10 = _4 + 4294967295;
_8 = (int) _10;
_13 = v_3(D) * _8;
x_5 = v_3(D) + _13;
and can be seen even on simpler:
int
foo (int t, int v)
{
t = t - 1U;
v *= t;
return v + t;
}
which we don't optimize at GIMPLE level. We don't optimize even:
int
bar (int t, int v)
{
t = t - 1;
v *= t;
return v + t;
}
Rather than hoping it is optimized during combine (the change there was that
while combining b=a-1 into c=b*d we attempted c=a*d-d we now attempt c=(a-1)*d
and similarly for the 3 insn combination with e=c+d, where we attempted and
succeeded to combine that into e=a*d while now we attempt and fail e=(a-1)*d+d:
-Successfully matched this instruction:
+Failed to match this instruction:
(parallel [
(set (reg/v:SI 91 [ <retval> ])
- (mult:SI (reg/v:SI 92 [ t ])
+ (plus:SI (mult:SI (plus:SI (reg/v:SI 92 [ t ])
+ (const_int -1 [0xffffffffffffffff]))
+ (reg/v:SI 93 [ v ]))
(reg/v:SI 93 [ v ])))
(clobber (reg:CC 17 flags))
])
), I think it would be useful to optimize this in match.pd, plus maybe teach
simplify-rtx.c to handle this.
>From gcc-bugs-return-661809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:08:03 2019
Return-Path: <gcc-bugs-return-661809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2554 invoked by alias); 29 Nov 2019 14:08:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2432 invoked by uid 55); 29 Nov 2019 14:07:58 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 14:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-sO2QyZBODw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03603.txt.bz2
Content-length: 2078
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 29 Nov 2019, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
>
> --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> Before the first revision mentioned above *.optimized dump contained just t *
> v, the second one doesn't change anything in *.optimized and is a RTL costing
> matter.
> _4 = (unsigned int) t_1(D);
> _10 = _4 + 4294967295;
> _8 = (int) _10;
> _13 = v_3(D) * _8;
> x_5 = v_3(D) + _13;
> and can be seen even on simpler:
> int
> foo (int t, int v)
> {
> t = t - 1U;
> v *= t;
> return v + t;
> }
> which we don't optimize at GIMPLE level. We don't optimize even:
> int
> bar (int t, int v)
> {
> t = t - 1;
> v *= t;
> return v + t;
> }
> Rather than hoping it is optimized during combine (the change there was that
> while combining b=a-1 into c=b*d we attempted c=a*d-d we now attempt c=(a-1)*d
> and similarly for the 3 insn combination with e=c+d, where we attempted and
> succeeded to combine that into e=a*d while now we attempt and fail e=(a-1)*d+d:
> -Successfully matched this instruction:
> +Failed to match this instruction:
> (parallel [
> (set (reg/v:SI 91 [ <retval> ])
> - (mult:SI (reg/v:SI 92 [ t ])
> + (plus:SI (mult:SI (plus:SI (reg/v:SI 92 [ t ])
> + (const_int -1 [0xffffffffffffffff]))
> + (reg/v:SI 93 [ v ]))
> (reg/v:SI 93 [ v ])))
> (clobber (reg:CC 17 flags))
> ])
> ), I think it would be useful to optimize this in match.pd, plus maybe teach
> simplify-rtx.c to handle this.
I think fold_plusminus_mult_expr does this on GENERIC, but it was dumbed
down at some point because of undefined overflow issues. Because
for (t - 1) * v + v, (t - 1) might be zero and with large v t * v
might overflow (or so, need to track down history of that function).
Richard.
>From gcc-bugs-return-661810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:13:37 2019
Return-Path: <gcc-bugs-return-661810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26723 invoked by alias); 29 Nov 2019 14:13:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26693 invoked by uid 48); 29 Nov 2019 14:13:33 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92728] New: [OpenMP][OpenACC] Common-block name clause matching issues: common block needs to be defined before + blank common not supported
Date: Fri, 29 Nov 2019 14:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: openacc, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92728-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03604.txt.bz2
Content-length: 1761
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92728
Bug ID: 92728
Summary: [OpenMP][OpenACC] Common-block name clause matching
issues: common block needs to be defined before +
blank common not supported
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: openacc, openmp
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
Target Milestone: ---
Based on the discussion at
https://gcc.gnu.org/ml/gcc-patches/2019-11/threads.html#00717
The current clause matching code in openmp.c's gfc_match_omp_variable_list
does:
m = gfc_match (" / %n /", n);
…
st = gfc_find_symtree (gfc_current_ns->common_root, n);
if (st == NULL)
{
gfc_error ("COMMON block /%s/ not found at %C", n);
Hence:
(1) This code requires the ordering
common /name/ …
!$omp … (/name/)
!$acc … (/name/)
while it would be (also) natural to use
!$omp … (/name/)
!$acc … (/name/)
common /name/ …
The Fortran standard usually permits this and at least part of the OpenXXX
specs talk only about the specification section, not imposing any ordering.
* Blank commons (i.e. common blocks without a name) cannot be matched.
Regarding blank commons: neither OpenMP nor OpenACC are clear whether they are
permitted and where. – However, in some clauses, OpenMP explicitly mentions
that blank commons are not permitted, implying that they are permitted
elsewhere. (See linked emails in the thread.)
>From gcc-bugs-return-661811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:22:11 2019
Return-Path: <gcc-bugs-return-661811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37651 invoked by alias); 29 Nov 2019 14:22:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37550 invoked by uid 48); 29 Nov 2019 14:22:07 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/79592] incomplete diagnostic "is not usable as a constexpr function because:"
Date: Fri, 29 Nov 2019 14:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_reconfirmed_on
Message-ID: <bug-79592-4-SjhnLJCSAp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79592-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79592-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03605.txt.bz2
Content-length: 638
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79592
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|accepts-invalid |
Last reconfirmed|2017-08-21 00:00:00 |2019-11-29
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #1)
> On a 32-bit target, it is always incorrectly accepted; adding -m64 is
> necessary to get the incomplete diagnostic:
That was a separate problem, fixed by r257161 for PR 68810.
>From gcc-bugs-return-661812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:23:27 2019
Return-Path: <gcc-bugs-return-661812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39095 invoked by alias); 29 Nov 2019 14:23:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39041 invoked by uid 48); 29 Nov 2019 14:23:22 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92697] IPA-SRA modifies ifunc_resolvers
Date: Fri, 29 Nov 2019 14:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92697-4-Se0DOSdWY5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92697-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92697-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03606.txt.bz2
Content-length: 427
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92697
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-661813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:25:47 2019
Return-Path: <gcc-bugs-return-661813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84141 invoked by alias); 29 Nov 2019 14:25:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83685 invoked by uid 48); 29 Nov 2019 14:25:43 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/79592] incomplete diagnostic "is not usable as a constexpr function because:"
Date: Fri, 29 Nov 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-79592-4-0VnMmq5Uix@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79592-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79592-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03607.txt.bz2
Content-length: 308
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79592
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #0)
> If the expression is (void*)1 rather than (void*)1LL then it is incorrectly
> accepted.
And that was the same problem, fixed by r257161.
>From gcc-bugs-return-661814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:25:50 2019
Return-Path: <gcc-bugs-return-661814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84462 invoked by alias); 29 Nov 2019 14:25:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84018 invoked by uid 48); 29 Nov 2019 14:25:45 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-1ZnP2RJKxd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03608.txt.bz2
Content-length: 418
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #5 from Marc Glisse <glisse at gcc dot gnu.org> ---
a*x+x -> (a+1)*x is unsafe (a=INT_MAX, x=0), but there are cases where we could
prove that it is safe, in particular when a is actually b-1 (more generally for
a*x+b*x when we can prove (with VRP?) that a+b cannot overflow).
Also, enabling -fwrapv for the last few gimple passes would help.
>From gcc-bugs-return-661815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:27:57 2019
Return-Path: <gcc-bugs-return-661815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86713 invoked by alias); 29 Nov 2019 14:27:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86655 invoked by uid 48); 29 Nov 2019 14:27:52 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92391] gcc.dg/vect/bb-slp-40.c FAILs
Date: Fri, 29 Nov 2019 14:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92391-4-TaJ2smWEbB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92391-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92391-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03609.txt.bz2
Content-length: 413
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92391
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #14 from Rainer Orth <ro at gcc dot gnu.org> ---
Sure.
>From gcc-bugs-return-661816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:35:09 2019
Return-Path: <gcc-bugs-return-661816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94676 invoked by alias); 29 Nov 2019 14:35:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94574 invoked by uid 48); 29 Nov 2019 14:35:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 14:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-3bgCxJx80s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03610.txt.bz2
Content-length: 687
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
At least from the comments it seems fold_plusminus_mult_expr only handles
(A * C) +- (B * C) -> (A +- B) * C
(A * C) +- A -> A * (C +- 1)
so for the testcases in question that is the latter and we punt because it is
not wrapping arithmetics and it doesn't match one of the special cases in
there.
The suggestion I'll try to work on is to check if C isn't a plus/minus expr
with constant second operand that doesn't go in the other direction and thus
where the transformation isn't introducing UB.
I guess it should be enough to do this in match.pd though.
>From gcc-bugs-return-661817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:35:52 2019
Return-Path: <gcc-bugs-return-661817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95733 invoked by alias); 29 Nov 2019 14:35:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95655 invoked by uid 48); 29 Nov 2019 14:35:48 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92510] ICE in native_encode_rtx, at simplify-rtx.c:6272
Date: Fri, 29 Nov 2019 14:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92510-4-eBgoOVHulA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92510-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92510-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03611.txt.bz2
Content-length: 543
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92510
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from Segher Boessenkool <segher at gcc dot gnu.org> ---
This is a bad PR to track all improvements that could be made to combine
(and RTL in general). Closing as fixed.
>From gcc-bugs-return-661818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:36:05 2019
Return-Path: <gcc-bugs-return-661818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96507 invoked by alias); 29 Nov 2019 14:36:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96424 invoked by uid 48); 29 Nov 2019 14:36:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 14:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-92712-4-AFsswhiImh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03612.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
>From gcc-bugs-return-661819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:38:05 2019
Return-Path: <gcc-bugs-return-661819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100825 invoked by alias); 29 Nov 2019 14:38:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100761 invoked by uid 48); 29 Nov 2019 14:38:01 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92729] New: [avr] Convert the backend to MODE_CC so it can be kept in future releases
Date: Fri, 29 Nov 2019 14:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-92729-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03613.txt.bz2
Content-length: 834
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729
Bug ID: 92729
Summary: [avr] Convert the backend to MODE_CC so it can be kept
in future releases
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: glaubitz at physik dot fu-berlin.de
Target Milestone: ---
Target: avr-*-*
This is a tracker bug for the convert the avr backend from CC0 to MODE_CC so it
can be kept in future releases.
See: https://gcc.gnu.org/wiki/CC0Transition
I will be using this bug report to create a bounty on BountySource.com.
We have already successfully funded such a conversion for the m68k backend, see
#91851.
>From gcc-bugs-return-661820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:39:59 2019
Return-Path: <gcc-bugs-return-661820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103882 invoked by alias); 29 Nov 2019 14:39:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103829 invoked by uid 48); 29 Nov 2019 14:39:53 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] Idea for better error messages
Date: Fri, 29 Nov 2019 14:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_severity
Message-ID: <bug-92727-4-GGjoOYr07K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03614.txt.bz2
Content-length: 2465
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Severity|normal |enhancement
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to David Brown from comment #0)
> Would it be possible to hide the messages concerning the allocator here?
I don't see how. It's the allocator that tries to use the X(const X&) copy
constructor. Why would you want to hide it?
> In
> general, would it be possible to hide the messages that deal with template
> parameters that are unchanged from the default?
Can you clarify what you mean? Nothing in this error has anything to do with
default template arguments. You'll get exactly the same error with
std::vector<X, acme::my_custom_allocator<X>>.
> That would let the user see
> messages that are relevant to the code /they/ have written, rather than
> implementation details in the libraries and headers.
While that seems a noble goal, I don't think "hide the messages concerning the
allocator" or "hide the messages that deal with template parameters that are
unchanged from the default" get anywhere near that goal.
> Even better, in this case, would be a hint that the user needs a std::move,
> as shown in line B.
Where should the compiler suggest that move? How does it know whether the
missing std::move should be in main(), or inside std::vector::push_back, or
inside allocator::construct?
A reasonable heuristic would be to assume code inside system headers is
correct, and that the code using those system headers is at fault, but it's
still going to suggest the wrong place often.
A better one would be to assume system headers are correct, and not suggest
adding it anywhere that already uses std::forward, because that's probably
generic code dealing with perfect forwarding, and the move should have been in
the caller of *that* code.
And you don't want to suggest adding std::move to a const value, because that
won't help.
The general problem is that inserting a std::move at some point in the call
graph can completely change everything after that point, and so won't
necessarily even reach the code that gave an error. Is that a "fix"? It's
impossible to know without grokking the code.
>From gcc-bugs-return-661823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:43:52 2019
Return-Path: <gcc-bugs-return-661823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121817 invoked by alias); 29 Nov 2019 14:43:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118927 invoked by uid 48); 29 Nov 2019 14:43:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] Idea for better error messages
Date: Fri, 29 Nov 2019 14:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92727-4-WkPlZoOzRs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03617.txt.bz2
Content-length: 639
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Are you suggesting that everything inside libstdc++ code should be treated as a
black box for the purposes of diagnostics, so that the location of the actual
problem:
error: use of deleted function ‘X::X(const X&)’
is shown as the "entry point" into the library code, i.e. the call to push_back
in the user's code?
That would be novel, and very unpopular with some people (who do want to be
able to examine the library headers and see how/why they got to that point and
what didn't compile).
>From gcc-bugs-return-661821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:43:50 2019
Return-Path: <gcc-bugs-return-661821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121081 invoked by alias); 29 Nov 2019 14:43:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117795 invoked by uid 48); 29 Nov 2019 14:43:46 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89280] [8 Regression] ICE: Segmentation fault (in is_gimple_reg_type)
Date: Fri, 29 Nov 2019 14:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89280-4-cR1snFSAtC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89280-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89280-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03615.txt.bz2
Content-length: 187
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89280
--- Comment #15 from Martin Liška <marxin at gcc dot gnu.org> ---
*** Bug 92725 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-661822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:43:50 2019
Return-Path: <gcc-bugs-return-661822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121430 invoked by alias); 29 Nov 2019 14:43:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117531 invoked by uid 48); 29 Nov 2019 14:43:45 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92725] ICE: Segmentation fault during GIMPLE pass
Date: Fri, 29 Nov 2019 14:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-92725-4-5WQ8fLYAvY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92725-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92725-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03616.txt.bz2
Content-length: 572
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92725
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |marxin at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Dup.
*** This bug has been marked as a duplicate of bug 89280 ***
>From gcc-bugs-return-661824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:44:26 2019
Return-Path: <gcc-bugs-return-661824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18148 invoked by alias); 29 Nov 2019 14:44:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11600 invoked by uid 48); 29 Nov 2019 14:44:21 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92379] rs6000.c:5598:13: runtime error: shift exponent 64 is too large for 64-bit type 'long int'
Date: Fri, 29 Nov 2019 14:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92379-4-yVTUdhuqVk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92379-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92379-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03618.txt.bz2
Content-length: 154
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92379
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Any update about this Segher?
>From gcc-bugs-return-661825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:47:40 2019
Return-Path: <gcc-bugs-return-661825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34320 invoked by alias); 29 Nov 2019 14:47:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33952 invoked by uid 55); 29 Nov 2019 14:47:35 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/91997] pretty printers: The __node_type type alias in _Hashtable is not available
Date: Fri, 29 Nov 2019 14:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91997-4-4LeQXDa5zE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91997-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91997-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03619.txt.bz2
Content-length: 2477
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91997
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Fri Nov 29 14:47:03 2019
New Revision: 278846
URL: https://gcc.gnu.org/viewcvs?rev=278846&root=gcc&view=rev
Log:
libstdc++:: improve how pretty printers find node types (PR 91997)
This fixes two related problems.
The iterators for node-based containers use nested typedefs such as
std::list<T>::iterator::_Node to denote their node types. As reported in
https://bugzilla.redhat.com/show_bug.cgi?id=1053438 those typedefs are
not always present in the debug info. That means the pretty printers
cannot find them using gdb.lookup_type (via the find_type helper).
Instead of looking up the nested typedefs this patch makes the printers
look up the actual class templates directly.
A related problem (and the original topic of PR 91997) is that GDB fails
to find types via gdb.lookup_type when printing a backtrace from a
non-C++ functiion: https://sourceware.org/bugzilla/show_bug.cgi?id=25234
That is also solved by not looking up the nested typedef.
PR libstdc++/91997
* python/libstdcxx/v6/printers.py (find_type): Fail more gracefully
if we run out of base classes to look at.
(llokup_templ_spec, lookup_node_type): New utilities to find node
types for node-based containers.
(StdListPrinter.children, NodeIteratorPrinter.__init__)
(NodeIteratorPrinter.to_string, StdSlistPrinter.children)
(StdSlistIteratorPrinter.to_string, StdRbtreeIteratorPrinter.__init__)
(StdMapPrinter.children, StdSetPrinter.children)
(StdForwardListPrinter.children): Use lookup_node_type instead of
find_type.
(StdListIteratorPrinter.__init__, StdFwdListIteratorPrinter.__init__):
Pass name of node type to NodeIteratorPrinter constructor.
(Tr1HashtableIterator.__init__): Rename argument.
(StdHashtableIterator.__init__): Likewise. Use lookup_templ_spec
instead of find_type.
* testsuite/libstdc++-prettyprinters/59161.cc: Remove workaround for
_Node typedef not being present in debuginfo.
* testsuite/libstdc++-prettyprinters/91997.cc: New test.
Added:
trunk/libstdc++-v3/testsuite/libstdc++-prettyprinters/91997.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/python/libstdcxx/v6/printers.py
trunk/libstdc++-v3/testsuite/libstdc++-prettyprinters/59161.cc
>From gcc-bugs-return-661826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:48:42 2019
Return-Path: <gcc-bugs-return-661826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36562 invoked by alias); 29 Nov 2019 14:48:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36126 invoked by uid 55); 29 Nov 2019 14:48:30 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92710] [9/10 Regression] Vectoriser generates invalid simd call for bool arguments
Date: Fri, 29 Nov 2019 14:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92710-4-a28ZpUEGjj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92710-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92710-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03620.txt.bz2
Content-length: 5455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92710
--- Comment #3 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Fri Nov 29 14:47:44 2019
New Revision: 278851
URL: https://gcc.gnu.org/viewcvs?rev=278851&root=gcc&view=rev
Log:
Don't defer choice of vector type for bools (PR 92596)
Now that stmt_vec_info records the choice between vector mask
types and normal nonmask types, we can use that information in
vect_get_vector_types_for_stmt instead of deferring the choice
of vector type till later.
vect_get_mask_type_for_stmt used to check whether the boolean inputs
to an operation:
(a) consistently used mask types or consistently used nonmask types; and
(b) agreed on the number of elements.
(b) shouldn't be a problem when (a) is met. If the operation
consistently uses mask types, tree-vect-patterns.c will have corrected
any mismatches in mask precision. (This is because we only use mask
types for a small well-known set of operations and tree-vect-patterns.c
knows how to handle any that could have different mask precisions.)
And if the operation consistently uses normal nonmask types, there's
no reason why booleans should need extra vector compatibility checks
compared to ordinary integers.
So the potential difficulties all seem to come from (a). Now that
we've chosen the result type ahead of time, we also have to consider
whether the outputs and inputs consistently use mask types.
Taking each vectorizable_* routine in turn:
- vectorizable_call
vect_get_vector_types_for_stmt only handled booleans specially
for gassigns, so vect_get_mask_type_for_stmt never had chance to
handle calls. I'm not sure we support any calls that operate on
booleans, but as things stand, a boolean result would always have
a nonmask type. Presumably any vector argument would also need to
use nonmask types, unless it corresponds to internal_fn_mask_index
(which is already a special case).
For safety, I've added a check for mask/nonmask combinations here
even though we didn't check this previously.
- vectorizable_simd_clone_call
Again, vect_get_mask_type_for_stmt never had chance to handle calls.
The result of the call will always be a nonmask type and the patch
for PR 92710 rejects mask arguments. So all booleans should
consistently use nonmask types here.
- vectorizable_conversion
The function already rejects any conversion between booleans in which
one type isn't a mask type.
- vectorizable_operation
This function definitely needs a consistency check, e.g. to handle
& and | in which one operand is loaded from memory and the other is
a comparison result. Ideally we'd handle this via pattern stmts
instead (like we do for the all-mask case), but that's future work.
- vectorizable_assignment
VECT_SCALAR_BOOLEAN_TYPE_P requires single-bit precision, so the
current code already rejects problematic cases.
- vectorizable_load
Loads always produce nonmask types and there are no relevant inputs
to check against.
- vectorizable_store
vect_check_store_rhs already rejects mask/nonmask combinations
via useless_type_conversion_p.
- vectorizable_reduction
- vectorizable_lc_phi
PHIs always have nonmask types. After the change above, attempts
to combine the PHI result with a mask type would be rejected by
vectorizable_operation. (Again, it would be better to handle
this using pattern stmts.)
- vectorizable_induction
We don't generate inductions for booleans.
- vectorizable_shift
The function already rejects boolean shifts via type_has_mode_precision_p.
- vectorizable_condition
The function already rejects mismatches via useless_type_conversion_p.
- vectorizable_comparison
The function already rejects comparisons between mask and nonmask types.
The result is always a mask type.
2019-11-29 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR tree-optimization/92596
* tree-vect-stmts.c (vectorizable_call): Punt on hybrid mask/nonmask
operations.
(vectorizable_operation): Likewise, instead of relying on
vect_get_mask_type_for_stmt to do this.
(vect_get_vector_types_for_stmt): Always return a vector type
immediately, rather than deferring the choice for boolean results.
Use a vector mask type instead of a normal vector if
vect_use_mask_type_p.
(vect_get_mask_type_for_stmt): Delete.
* tree-vect-loop.c (vect_determine_vf_for_stmt_1): Remove
mask_producers argument and special boolean_type_node handling.
(vect_determine_vf_for_stmt): Remove mask_producers argument and
update calls to vect_determine_vf_for_stmt_1. Remove doubled call.
(vect_determine_vectorization_factor): Update call accordingly.
* tree-vect-slp.c (vect_build_slp_tree_1): Remove special
boolean_type_node handling.
(vect_slp_analyze_node_operations_1): Likewise.
gcc/testsuite/
PR tree-optimization/92596
* gcc.dg/vect/bb-slp-pr92596.c: New test.
* gcc.dg/vect/bb-slp-43.c: Likewise.
Added:
trunk/gcc/testsuite/gcc.dg/vect/bb-slp-43.c
trunk/gcc/testsuite/gcc.dg/vect/bb-slp-pr92596.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-vect-loop.c
trunk/gcc/tree-vect-slp.c
trunk/gcc/tree-vect-stmts.c
>From gcc-bugs-return-661827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:48:42 2019
Return-Path: <gcc-bugs-return-661827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36627 invoked by alias); 29 Nov 2019 14:48:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36129 invoked by uid 55); 29 Nov 2019 14:48:30 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92596] [10 Regression] ICE in exact_div, at poly-int.h:2162 since r278406
Date: Fri, 29 Nov 2019 14:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92596-4-3A3R6yc4C7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92596-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92596-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03622.txt.bz2
Content-length: 5456
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92596
--- Comment #11 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Fri Nov 29 14:47:44 2019
New Revision: 278851
URL: https://gcc.gnu.org/viewcvs?rev=278851&root=gcc&view=rev
Log:
Don't defer choice of vector type for bools (PR 92596)
Now that stmt_vec_info records the choice between vector mask
types and normal nonmask types, we can use that information in
vect_get_vector_types_for_stmt instead of deferring the choice
of vector type till later.
vect_get_mask_type_for_stmt used to check whether the boolean inputs
to an operation:
(a) consistently used mask types or consistently used nonmask types; and
(b) agreed on the number of elements.
(b) shouldn't be a problem when (a) is met. If the operation
consistently uses mask types, tree-vect-patterns.c will have corrected
any mismatches in mask precision. (This is because we only use mask
types for a small well-known set of operations and tree-vect-patterns.c
knows how to handle any that could have different mask precisions.)
And if the operation consistently uses normal nonmask types, there's
no reason why booleans should need extra vector compatibility checks
compared to ordinary integers.
So the potential difficulties all seem to come from (a). Now that
we've chosen the result type ahead of time, we also have to consider
whether the outputs and inputs consistently use mask types.
Taking each vectorizable_* routine in turn:
- vectorizable_call
vect_get_vector_types_for_stmt only handled booleans specially
for gassigns, so vect_get_mask_type_for_stmt never had chance to
handle calls. I'm not sure we support any calls that operate on
booleans, but as things stand, a boolean result would always have
a nonmask type. Presumably any vector argument would also need to
use nonmask types, unless it corresponds to internal_fn_mask_index
(which is already a special case).
For safety, I've added a check for mask/nonmask combinations here
even though we didn't check this previously.
- vectorizable_simd_clone_call
Again, vect_get_mask_type_for_stmt never had chance to handle calls.
The result of the call will always be a nonmask type and the patch
for PR 92710 rejects mask arguments. So all booleans should
consistently use nonmask types here.
- vectorizable_conversion
The function already rejects any conversion between booleans in which
one type isn't a mask type.
- vectorizable_operation
This function definitely needs a consistency check, e.g. to handle
& and | in which one operand is loaded from memory and the other is
a comparison result. Ideally we'd handle this via pattern stmts
instead (like we do for the all-mask case), but that's future work.
- vectorizable_assignment
VECT_SCALAR_BOOLEAN_TYPE_P requires single-bit precision, so the
current code already rejects problematic cases.
- vectorizable_load
Loads always produce nonmask types and there are no relevant inputs
to check against.
- vectorizable_store
vect_check_store_rhs already rejects mask/nonmask combinations
via useless_type_conversion_p.
- vectorizable_reduction
- vectorizable_lc_phi
PHIs always have nonmask types. After the change above, attempts
to combine the PHI result with a mask type would be rejected by
vectorizable_operation. (Again, it would be better to handle
this using pattern stmts.)
- vectorizable_induction
We don't generate inductions for booleans.
- vectorizable_shift
The function already rejects boolean shifts via type_has_mode_precision_p.
- vectorizable_condition
The function already rejects mismatches via useless_type_conversion_p.
- vectorizable_comparison
The function already rejects comparisons between mask and nonmask types.
The result is always a mask type.
2019-11-29 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR tree-optimization/92596
* tree-vect-stmts.c (vectorizable_call): Punt on hybrid mask/nonmask
operations.
(vectorizable_operation): Likewise, instead of relying on
vect_get_mask_type_for_stmt to do this.
(vect_get_vector_types_for_stmt): Always return a vector type
immediately, rather than deferring the choice for boolean results.
Use a vector mask type instead of a normal vector if
vect_use_mask_type_p.
(vect_get_mask_type_for_stmt): Delete.
* tree-vect-loop.c (vect_determine_vf_for_stmt_1): Remove
mask_producers argument and special boolean_type_node handling.
(vect_determine_vf_for_stmt): Remove mask_producers argument and
update calls to vect_determine_vf_for_stmt_1. Remove doubled call.
(vect_determine_vectorization_factor): Update call accordingly.
* tree-vect-slp.c (vect_build_slp_tree_1): Remove special
boolean_type_node handling.
(vect_slp_analyze_node_operations_1): Likewise.
gcc/testsuite/
PR tree-optimization/92596
* gcc.dg/vect/bb-slp-pr92596.c: New test.
* gcc.dg/vect/bb-slp-43.c: Likewise.
Added:
trunk/gcc/testsuite/gcc.dg/vect/bb-slp-43.c
trunk/gcc/testsuite/gcc.dg/vect/bb-slp-pr92596.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-vect-loop.c
trunk/gcc/tree-vect-slp.c
trunk/gcc/tree-vect-stmts.c
>From gcc-bugs-return-661828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:48:55 2019
Return-Path: <gcc-bugs-return-661828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37649 invoked by alias); 29 Nov 2019 14:48:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37050 invoked by uid 48); 29 Nov 2019 14:48:44 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92379] rs6000.c:5598:13: runtime error: shift exponent 64 is too large for 64-bit type 'long int'
Date: Fri, 29 Nov 2019 14:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92379-4-NAV7xVFX3S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92379-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92379-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03621.txt.bz2
Content-length: 195
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92379
--- Comment #5 from Segher Boessenkool <segher at gcc dot gnu.org> ---
It's not top priority; it is fine for stage 4, too. Patches welcome.
>From gcc-bugs-return-661829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:49:08 2019
Return-Path: <gcc-bugs-return-661829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38835 invoked by alias); 29 Nov 2019 14:49:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38746 invoked by uid 55); 29 Nov 2019 14:49:04 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92677] [10 Regression] ICE in get_group_load_store_type, at tree-vect-stmts.c:2261 since r271704
Date: Fri, 29 Nov 2019 14:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92677-4-IHR9kSHbcl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03623.txt.bz2
Content-length: 935
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92677
--- Comment #2 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Fri Nov 29 14:48:30 2019
New Revision: 278852
URL: https://gcc.gnu.org/viewcvs?rev=278852&root=gcc&view=rev
Log:
Fix DR_GROUP_GAP for strided accesses (PR 92677)
When dissolving an SLP-only group of accesses, we should only set
the gap to group_size - 1 for normal non-strided groups.
2019-11-29 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR tree-optimization/92677
* tree-vect-loop.c (vect_dissolve_slp_only_groups): Set the gap
to zero when dissolving a group of strided accesses.
gcc/testsuite/
PR tree-optimization/92677
* gcc.dg/vect/pr92677.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/vect/pr92677.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-vect-loop.c
>From gcc-bugs-return-661830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:49:19 2019
Return-Path: <gcc-bugs-return-661830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39539 invoked by alias); 29 Nov 2019 14:49:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39463 invoked by uid 48); 29 Nov 2019 14:49:14 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 14:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-3wt6f9rs4r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03624.txt.bz2
Content-length: 686
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #7 from Marc Glisse <glisse at gcc dot gnu.org> ---
The first question could be why SCCP produces
(const int) ((unsigned int) t_2(D) + 4294967295) * v_3(D) + v_3(D)
and not directly t*v. Several loop passes do have this tendency to split out
the last (or first) iteration and produce strange expressions that we have
trouble cleaning up afterwards.
Anyway, in VRP2, I see
_10: int [0, 2147483646]
_14 = v_3(D) * _10;
x_6 = v_3(D) + _14;
so range info would allow to prove that _10 + 1 cannot overflow, and thus to
factor out v_3(D). I have long wanted a op_cannot_overflow(tree_code,tree,tree)
utility...
>From gcc-bugs-return-661831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:52:23 2019
Return-Path: <gcc-bugs-return-661831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46097 invoked by alias); 29 Nov 2019 14:52:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46010 invoked by uid 48); 29 Nov 2019 14:52:19 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 14:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-uTp4rBix11@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03625.txt.bz2
Content-length: 557
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #8 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #6)
> The suggestion I'll try to work on is to check if C isn't a plus/minus expr
> with constant second operand that doesn't go in the other direction and thus
> where the transformation isn't introducing UB.
In the testcase, t-1 is computed in some unsigned type and then cast back to
signed, so I don't think it will work.
> I guess it should be enough to do this in match.pd though.
Yes.
>From gcc-bugs-return-661832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:54:56 2019
Return-Path: <gcc-bugs-return-661832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15351 invoked by alias); 29 Nov 2019 14:54:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8162 invoked by uid 48); 29 Nov 2019 14:54:52 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/91997] pretty printers: The __node_type type alias in _Hashtable is not available
Date: Fri, 29 Nov 2019 14:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-91997-4-JYToTd7JrR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91997-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91997-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03626.txt.bz2
Content-length: 395
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91997
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|10.0 |8.4
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed on trunk, backports to follow.
>From gcc-bugs-return-661833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:57:37 2019
Return-Path: <gcc-bugs-return-661833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5458 invoked by alias); 29 Nov 2019 14:57:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5397 invoked by uid 55); 29 Nov 2019 14:57:33 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 14:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-pn8LSXuyyI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03627.txt.bz2
Content-length: 703
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #9 from rguenther at suse dot de <rguenther at suse dot de> ---
On November 29, 2019 3:25:45 PM GMT+01:00, "glisse at gcc dot gnu.org"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
>
>--- Comment #5 from Marc Glisse <glisse at gcc dot gnu.org> ---
>a*x+x -> (a+1)*x is unsafe (a=INT_MAX, x=0), but there are cases where
>we could
>prove that it is safe, in particular when a is actually b-1 (more
>generally for
>a*x+b*x when we can prove (with VRP?) that a+b cannot overflow).
>
>Also, enabling -fwrapv for the last few gimple passes would help.
I had a patch for that, RTL is also wrapv.
>From gcc-bugs-return-661834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 14:59:49 2019
Return-Path: <gcc-bugs-return-661834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8928 invoked by alias); 29 Nov 2019 14:59:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8845 invoked by uid 48); 29 Nov 2019 14:59:45 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 14:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-CvfYT2SUzc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03628.txt.bz2
Content-length: 803
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #8)
> (In reply to Jakub Jelinek from comment #6)
> > The suggestion I'll try to work on is to check if C isn't a plus/minus expr
> > with constant second operand that doesn't go in the other direction and thus
> > where the transformation isn't introducing UB.
>
> In the testcase, t-1 is computed in some unsigned type and then cast back to
> signed, so I don't think it will work.
I know, it will be a small complication, sure, but it can be handled.
Using range info is certainly useful, but e.g. for this case with -1U it will
not be able to do anything, as the range of (int)(t-1U) will be varying. So I
think we want both.
>From gcc-bugs-return-661835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 15:01:13 2019
Return-Path: <gcc-bugs-return-661835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10950 invoked by alias); 29 Nov 2019 15:01:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10903 invoked by uid 48); 29 Nov 2019 15:01:08 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92286] Possible improvement for -Wduplicated-cond warning
Date: Fri, 29 Nov 2019 15:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92286-4-rZlaPm2dib@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92286-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92286-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03629.txt.bz2
Content-length: 482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92286
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Based on Eric wrote, I tend to close it as won't fix.
>From gcc-bugs-return-661836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 15:05:51 2019
Return-Path: <gcc-bugs-return-661836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27993 invoked by alias); 29 Nov 2019 15:05:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27914 invoked by uid 48); 29 Nov 2019 15:05:45 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92283] [10 Regression] 454.calculix miscomparison since r276645 with -O2 -march=znver2
Date: Fri, 29 Nov 2019 15:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ra, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92283-4-6RyQrSP6wf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92283-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92283-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03630.txt.bz2
Content-length: 3347
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92283
--- Comment #26 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
I think I find the problem root. We have
********** Local #2: **********
Choosing alt 0 in insn 1804: (0) =v (1) %0 (2) vm (3) v
{*fma_fmadd_df}
Creating newreg=4707 from oldreg=1801, assigning class ALL_SSE_REGS to
r4707
Creating newreg=4708 from oldreg=1801, assigning class ALL_SSE_REGS to
r4708
Making reload reg 4708 for reg 1801 optional
1804: r4707:DF={r4707:DF*r4708:DF+r984:DF}
! REG_DEAD r1801:DF
REG_DEAD r984:DF
Inserting insn reload before:
10917: r4707:DF=r1801:DF
10919: r4708:DF=r1801:DF
Inserting insn reload after:
10918: r238:DF=r4707:DF
.........
Choosing alt 2 in insn 1814: (0) v (1) v (2) vm (3) 0
{*fma_fmadd_df}
Creating newreg=4709 from oldreg=1801, assigning class ALL_SSE_REGS to
r4709
Making reload reg 4709 for reg 1801 optional
1814: r244:DF={r1795:DF*r4709:DF+r1803:DF}
REG_DEAD r1801:DF
REG_DEAD r1803:DF
Inserting insn reload before:
10920: r4709:DF=r1801:DF
********** Inheritance #2: **********
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Use smallest class of ALL_SSE_REGS and SSE_REGS
Creating newreg=4778 from oldreg=1801, assigning class ALL_SSE_REGS to
inheritance r4778
Original reg change 1801->4778 (bb177):
10920: r4709:DF=r4778:DF
Add inheritance<-original before:
10995: r4778:DF=r1801:DF
Inheritance reuse change 1801->4778 (bb177):
10019: r3911:DF=r4778:DF
REG_DEAD r4778:DF
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Use smallest class of ALL_SSE_REGS and SSE_REGS
Creating newreg=4779 from oldreg=1801, assigning class ALL_SSE_REGS to
inheritance r4779
Original reg change 1801->4779 (bb177):
! 10919: r4708:DF=r4779:DF
Add inheritance<-original before:
10996: r4779:DF=r1801:DF
Inheritance reuse change 1801->4779 (bb177):
10995: r4778:DF=r4779:DF
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
********** Assignment #2: **********
Assigning to 4779 (cl=ALL_SSE_REGS, orig=1801, freq=18, tfirst=4707,
tfreq=36)...
Assigning to 4778 (cl=ALL_SSE_REGS, orig=1801, freq=18, tfirst=4707,
tfreq=36)...
Assigning to 4780 (cl=ALL_SSE_REGS, orig=1801, freq=18, tfirst=4707,
tfreq=36)...
Assign 26 to inheritance r4780 (freq=18)
Reassigning non-reload pseudos
Assign 4 to r237 (freq=26)
Assign 26 to inheritance r4778 (freq=18)
! Hard reg 26 is preferable by r4779 with profit 24
Assign 26 to inheritance r4779 (freq=18)
We assigned 26 for conflicting 4779 and 4707 because they have the same value
1802 (from r1801).
4707 got the same value as 1801 because LRA sees wrong (REG_DEAD r1801:DF) in
insn 1804. In most cases LRA uses live-ranges but in constraint sub-pass it
can use reg notes too.
Live ranges and reg notes should be synchronized but in this case we did not
update notes after
first inheritance sub-pass although there were some changes there too.
I working on a patch. If the tests are ok, I commit the patch today.
>From gcc-bugs-return-661837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 15:08:23 2019
Return-Path: <gcc-bugs-return-661837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31428 invoked by alias); 29 Nov 2019 15:08:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31377 invoked by uid 48); 29 Nov 2019 15:08:19 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92710] [9 Regression] Vectoriser generates invalid simd call for bool arguments
Date: Fri, 29 Nov 2019 15:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-92710-4-AMK9kyH0SR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92710-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92710-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03631.txt.bz2
Content-length: 632
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92710
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[9/10 Regression] |[9 Regression] Vectoriser
|Vectoriser generates |generates invalid simd call
|invalid simd call for bool |for bool arguments
|arguments |
--- Comment #4 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Fixed on trunk so far.
>From gcc-bugs-return-661838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 15:09:16 2019
Return-Path: <gcc-bugs-return-661838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32726 invoked by alias); 29 Nov 2019 15:09:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32619 invoked by uid 48); 29 Nov 2019 15:09:12 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92596] [10 Regression] ICE in exact_div, at poly-int.h:2162 since r278406
Date: Fri, 29 Nov 2019 15:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92596-4-oKLpT7B351@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92596-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92596-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03632.txt.bz2
Content-length: 460
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92596
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-661839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 15:10:02 2019
Return-Path: <gcc-bugs-return-661839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35315 invoked by alias); 29 Nov 2019 15:10:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35059 invoked by uid 48); 29 Nov 2019 15:09:58 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92677] [10 Regression] ICE in get_group_load_store_type, at tree-vect-stmts.c:2261 since r271704
Date: Fri, 29 Nov 2019 15:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92677-4-nQeQbUuznL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03633.txt.bz2
Content-length: 459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92677
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-661840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 15:19:55 2019
Return-Path: <gcc-bugs-return-661840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48823 invoked by alias); 29 Nov 2019 15:19:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48771 invoked by uid 48); 29 Nov 2019 15:19:51 -0000
From: "david at westcontrol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] Idea for better error messages
Date: Fri, 29 Nov 2019 15:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: david at westcontrol dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92727-4-IzzMl1Xm7t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03634.txt.bz2
Content-length: 2674
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
--- Comment #3 from David Brown <david at westcontrol dot com> ---
I may not have been very clear here. Let me try and take a step back here.
>From the user's viewpoint, the problem is that they have made a class that
can't be copied, and they have written code that tries to copy it. With the
current error messages, point comes across - but it is hidden amongst a lot of
messages about "allocators" that will be unfamiliar to many users, and
unhelpful to most users.
I fully appreciate the problem occurs when the allocator that tries to use the
copy constructor. But the user has not specified an allocator, or picked an
allocator, or mentioned allocators in their code - and perhaps does not even
know what they are. Most users are happy to accept "it goes in memory
somewhere", or "it is on the heap", without worrying about the details. What I
am hoping for here is some way to help the user get the part of the error
information that is important to them, and will help them fix their code,
without unnecessary detail.
What I meant about default template parameters is that - as you say - some
people /do/ want all the details of the messages about the allocator. These
are mostly in two groups - people using non-default allocators, and people who
want to deal with the details of the standard library. The first group can be
identified by their use of explicit allocators in the template instantiation
rather than using the defaults, and the second could perhaps use an additional
compiler switch (a little like the current "-Wsystem-headers" switch).
So yes, I /am/ suggesting that the error location should be given as the
"v.push_back(x);" line. And yes, I am aware that it would not be ideal for
experts - but I think it would be clearer to a majority of users. And that
would be novel! Part of the job of a compiler is to help people write correct
code, and clear error and warning messages are essential for that. (Let me
also say that gcc does a fine job here, and has improved enormously over the
years that I have used it - though it could still be better.)
Perhaps this could be better handled using concepts? Maybe "push_back" could
be declared to take a parameter with a concept requiring either a type that
could be copied into the vector or a type that is a compatible rvalue
reference? Or perhaps concepts and "if constexpr" in C++17 would make it
practical to make the "push_back(const T&)" overload unavailable if T is not
copyable? That would get you straight to a "no matching function call for
std::vector<X>::push_back(X&)" message on the offending line.
>From gcc-bugs-return-661841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 15:43:00 2019
Return-Path: <gcc-bugs-return-661841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111651 invoked by alias); 29 Nov 2019 15:43:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 111535 invoked by uid 48); 29 Nov 2019 15:42:56 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 15:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-vcUfl8qFPa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03635.txt.bz2
Content-length: 1029
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #11 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #10)
> I know, it will be a small complication, sure, but it can be handled.
Ah, I think I understand now. But still
x=-1
a=INT_MAX
a*x+x gives INT_MIN without overflow.
Now a could be (int)((unsigned)b-1) where b is INT_MIN. But we don't want to
generate b*x for that (INT_MIN*-1), since it overflows. So we would need to do
the multiplication in some unsigned type. If we go there (do everything
unsigned), we could do the transformation always, and restricting it is just a
heuristic for when the signed type information might be more useful than the
factorized form.
> Using range info is certainly useful, but e.g. for this case with -1U it
> will not be able to do anything, as the range of (int)(t-1U) will be
> varying. So I think we want both.
In this very particular case, it happens that we have if(t>0) dominating this
stuff, which helps VRP.
>From gcc-bugs-return-661842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 15:47:29 2019
Return-Path: <gcc-bugs-return-661842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1950 invoked by alias); 29 Nov 2019 15:47:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1930 invoked by uid 48); 29 Nov 2019 15:47:25 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] Idea for better error messages
Date: Fri, 29 Nov 2019 15:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92727-4-qre0yY98Pq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03636.txt.bz2
Content-length: 3039
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to David Brown from comment #3)
> Perhaps this could be better handled using concepts?
Yes, ideally. That stops compilation as soon as you try to call something that
fails to satisfy the constraints (in this case, that the vector's value type is
constructible from the argument to push_back).
> Maybe "push_back"
> could be declared to take a parameter with a concept requiring either a type
> that could be copied into the vector or a type that is a compatible rvalue
> reference?
We can't change the parameter type of push_back, that would not be conforming.
> Or perhaps concepts and "if constexpr" in C++17 would make it
> practical to make the "push_back(const T&)" overload unavailable if T is not
> copyable? That would get you straight to a "no matching function call for
> std::vector<X>::push_back(X&)" message on the offending line.
if-constexpr can't help, that can only be used inside the function, by which
point it's too late.
I don't think concepts are really practical either, because we're limited where
we can reasonably use them. std::vector has to be usable in C++98 still, and
implementing the whole thing twice (with and without concepts in the API) would
be a maintenance nightmare.
Also, altering the overload set as you suggest needs to be done *very*
carefuly, or what happens is you end up removing one bad function and so a
different function gets called instead. You need to consider the entire
overload set at once.
I think a much more maintainable approach is something like:
--- a/libstdc++-v3/include/bits/stl_vector.h
+++ b/libstdc++-v3/include/bits/stl_vector.h
@@ -1183,6 +1183,10 @@ _GLIBCXX_BEGIN_NAMESPACE_CONTAINER
void
push_back(const value_type& __x)
{
+#if __cplusplus >= 201703L
+ if constexpr (is_same_v<allocator_type, allocator<value_type>>)
+ static_assert(is_copy_constructible_v<value_type>);
+#endif
if (this->_M_impl._M_finish != this->_M_impl._M_end_of_storage)
{
_GLIBCXX_ASAN_ANNOTATE_GROW(1);
With that change your example prints:
In file included from /home/jwakely/gcc/10/include/c++/10.0.0/vector:67,
from up.cc:1:
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_vector.h: In instantiation of
'void std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp = X;
_Alloc = std::allocator<X>; std::vector<_Tp, _Alloc>::value_type = X]':
up.cc:14:18: required from here
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_vector.h:1188:18: error:
static assertion failed
1188 | static_assert(is_copy_constructible_v<value_type>);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I think trying to do this via "smart" diagnostics would be doomed to failure.
Enforcing preconditions via static_assert is much more reliable, and easier to
tweak to improve it. Somebody just needs to add those assertions.
>From gcc-bugs-return-661843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 15:55:31 2019
Return-Path: <gcc-bugs-return-661843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12582 invoked by alias); 29 Nov 2019 15:55:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12540 invoked by uid 48); 29 Nov 2019 15:55:26 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] Idea for better error messages
Date: Fri, 29 Nov 2019 15:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92727-4-D2cvfN3x9w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03637.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The downside of this (and your suggestion to remove push_back from the overload
set) is that you no longer get told the copy constructor is deleted and why.
That note is only printed when the copy constructor is needed, but this
approach means it never gets used, because the assertions stops it getting that
far.
>From gcc-bugs-return-661844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 15:59:39 2019
Return-Path: <gcc-bugs-return-661844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5974 invoked by alias); 29 Nov 2019 15:59:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5908 invoked by uid 48); 29 Nov 2019 15:59:35 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 15:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-krMvPm90Aq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03638.txt.bz2
Content-length: 1333
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #11)
> (In reply to Jakub Jelinek from comment #10)
> > I know, it will be a small complication, sure, but it can be handled.
>
> Ah, I think I understand now. But still
>
> x=-1
> a=INT_MAX
> a*x+x gives INT_MIN without overflow.
> Now a could be (int)((unsigned)b-1) where b is INT_MIN. But we don't want to
> generate b*x for that (INT_MIN*-1), since it overflows. So we would need to
> do the multiplication in some unsigned type. If we go there (do everything
> unsigned), we could do the transformation always, and restricting it is just
> a heuristic for when the signed type information might be more useful than
> the factorized form.
The comments at least in fold-const.c say clearly that we do not want to
perform unsigned multiplication.
I was talking about the int a, b;
((int)(a-1U))*b+b
transformation into a*b.
Even for a=0, it is -1*b+b into 0, there could be UB before, but there is none
after. a=INT_MIN used to be INT_MAX*b+b and newly INT_MIN*b, well defined for
b=0, UB for b > 0, UB for b < -1, but it is true that INT_MAX*-1+-1 is well
defined INT_MIN, but INT_MIN*-1 is UB.
So guess we need to use range info only then.
>From gcc-bugs-return-661845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 16:10:14 2019
Return-Path: <gcc-bugs-return-661845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21991 invoked by alias); 29 Nov 2019 16:10:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21890 invoked by uid 48); 29 Nov 2019 16:10:06 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92193] Poor diagnostics when a constexpr function call follows a failed static_assert
Date: Fri, 29 Nov 2019 16:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-92193-4-fpUfVEEUoF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92193-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92193-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03639.txt.bz2
Content-length: 7048
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92193
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-29
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This results in a far worse experience for users in C++20, where lots more
things become constexpr.
With the patch I suggested in Bug 92727 comment 4 the diagnostic in C++17 mode
would be:
In file included from /home/jwakely/gcc/10/include/c++/10.0.0/vector:67,
from up.cc:1:
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_vector.h: In instantiation of
'void std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp = X;
_Alloc = std::allocator<X>; std::vector<_Tp, _Alloc>::value_type = X]':
up.cc:14:18: required from here
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_vector.h:1188:18: error:
static assertion failed
1188 | static_assert(is_copy_constructible_v<value_type>);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
But compiling the exact same code with -std=gnu++2a gives:
In file included from /home/jwakely/gcc/10/include/c++/10.0.0/vector:67,
from up.cc:1:
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_vector.h: In instantiation of
'void std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp = X;
_Alloc = std::allocator<X>; std::vector<_Tp, _Alloc>::value_type = X]':
up.cc:14:18: required from here
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_vector.h:1188:18: error:
static assertion failed
1188 | static_assert(is_copy_constructible_v<value_type>);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from
/home/jwakely/gcc/10/include/c++/10.0.0/ext/alloc_traits.h:34,
from
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_uninitialized.h:67,
from /home/jwakely/gcc/10/include/c++/10.0.0/vector:66,
from up.cc:1:
/home/jwakely/gcc/10/include/c++/10.0.0/bits/alloc_traits.h: In instantiation
of 'static constexpr void std::allocator_traits<std::allocator<_Up>
>::construct(std::allocator_traits<std::allocator<_Up> >::allocator_type&,
_Up*, _Args&& ...) [with _Up = X; _Args = {const X&}; _Tp = X;
std::allocator_traits<std::allocator<_Up> >::allocator_type =
std::allocator<X>]':
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_vector.h:1193:30: required
from 'void std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp =
X; _Alloc = std::allocator<X>; std::vector<_Tp, _Alloc>::value_type = X]'
up.cc:14:18: required from here
/home/jwakely/gcc/10/include/c++/10.0.0/bits/alloc_traits.h:504:20: error: use
of deleted function 'X::X(const X&)'
504 | noexcept(noexcept(::new((void*)__p) _Up(std::declval<_Args>()...)))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
up.cc:6:7: note: 'X::X(const X&)' is implicitly deleted because the default
definition would be ill-formed:
6 | class X {
| ^
up.cc:6:7: error: use of deleted function 'std::unique_ptr<_Tp,
_Dp>::unique_ptr(const std::unique_ptr<_Tp, _Dp>&) [with _Tp = Y; _Dp =
std::default_delete<Y>]'
In file included from /home/jwakely/gcc/10/include/c++/10.0.0/memory:82,
from up.cc:2:
/home/jwakely/gcc/10/include/c++/10.0.0/bits/unique_ptr.h:456:7: note: declared
here
456 | unique_ptr(const unique_ptr&) = delete;
| ^~~~~~~~~~
In file included from
/home/jwakely/gcc/10/include/c++/10.0.0/ext/alloc_traits.h:34,
from
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_uninitialized.h:67,
from /home/jwakely/gcc/10/include/c++/10.0.0/vector:66,
from up.cc:1:
/home/jwakely/gcc/10/include/c++/10.0.0/bits/alloc_traits.h: In instantiation
of 'static constexpr void std::allocator_traits<std::allocator<_Up>
>::construct(std::allocator_traits<std::allocator<_Up> >::allocator_type&,
_Up*, _Args&& ...) [with _Up = X; _Args = {const X&}; _Tp = X;
std::allocator_traits<std::allocator<_Up> >::allocator_type =
std::allocator<X>]':
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_vector.h:1193:30: required
from 'void std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp =
X; _Alloc = std::allocator<X>; std::vector<_Tp, _Alloc>::value_type = X]'
up.cc:14:18: required from here
/home/jwakely/gcc/10/include/c++/10.0.0/bits/alloc_traits.h:509:21: error: no
matching function for call to 'construct_at(X*&, const X&)'
509 | std::construct_at(__p, std::forward<_Args>(__args)...);
| ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_tempbuf.h:60,
from
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_algo.h:62,
from /home/jwakely/gcc/10/include/c++/10.0.0/vector:62,
from up.cc:1:
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_construct.h:94:5: note:
candidate: 'template<class _Tp, class ... _Args> constexpr decltype
(::new(void*(0)) _Tp) std::construct_at(_Tp*, _Args&& ...)'
94 | construct_at(_Tp* __location, _Args&&... __args)
| ^~~~~~~~~~~~
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_construct.h:94:5: note:
template argument deduction/substitution failed:
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_construct.h: In substitution
of 'template<class _Tp, class ... _Args> constexpr decltype (::new(void*(0))
_Tp) std::construct_at(_Tp*, _Args&& ...) [with _Tp = X; _Args = {const X&}]':
/home/jwakely/gcc/10/include/c++/10.0.0/bits/alloc_traits.h:509:21: required
from 'static constexpr void std::allocator_traits<std::allocator<_Up>
>::construct(std::allocator_traits<std::allocator<_Up> >::allocator_type&,
_Up*, _Args&& ...) [with _Up = X; _Args = {const X&}; _Tp = X;
std::allocator_traits<std::allocator<_Up> >::allocator_type =
std::allocator<X>]'
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_vector.h:1193:30: required
from 'void std::vector<_Tp, _Alloc>::push_back(const value_type&) [with _Tp =
X; _Alloc = std::allocator<X>; std::vector<_Tp, _Alloc>::value_type = X]'
up.cc:14:18: required from here
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_construct.h:96:17: error: use
of deleted function 'X::X(const X&)'
96 | -> decltype(::new((void*)0) _Tp(std::declval<_Args>()...))
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
That's because in C++20 some of the code following the static assertion
involves a constexpr function, which calls another constexpr function, which
calls another ... and all of them get evaluated and barf out their errors. The
whole point of the static_assert is to stop that happening.
>From gcc-bugs-return-661846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 16:12:09 2019
Return-Path: <gcc-bugs-return-661846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23522 invoked by alias); 29 Nov 2019 16:12:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23489 invoked by uid 48); 29 Nov 2019 16:12:02 -0000
From: "david at westcontrol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] Idea for better error messages
Date: Fri, 29 Nov 2019 16:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: david at westcontrol dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92727-4-I6XygKTj6i@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03640.txt.bz2
Content-length: 690
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
--- Comment #6 from David Brown <david at westcontrol dot com> ---
I can see it is a challenge to get enough detail in the messages to be good for
the more advanced users, and still simple enough and clear enough for more
casual or inexperienced users.
The static assertion looks good to me, and is clearly the easiest way to
implement such a feature. But I appreciate that it would not be ideal for some
people, and would hide useful messages from them.
Perhaps the a better place to focus would be on IDE's, maybe especially with
parsing of the new JSON format, to help people see exactly where the problem
lies in their code.
>From gcc-bugs-return-661847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 16:14:55 2019
Return-Path: <gcc-bugs-return-661847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29113 invoked by alias); 29 Nov 2019 16:14:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29075 invoked by uid 48); 29 Nov 2019 16:14:50 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92730] New: [OpenMP] Common blocks in map() clause not accepted
Date: Fri, 29 Nov 2019 16:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92730-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03641.txt.bz2
Content-length: 2080
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92730
Bug ID: 92730
Summary: [OpenMP] Common blocks in map() clause not accepted
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: openmp
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
Target Milestone: ---
See also PR 92728 and the thread at
https://gcc.gnu.org/ml/gcc-patches/2019-11/threads.html#00717
Pre-remark, as remembered just now:
"Named common blocks of the same name shall be of the same size in all scoping
units of a program in which they appear, but blank common blocks may be of
different sizes." (Fortran 2018, 8.10.2.5)
From the thread:
> In OpenMP 5, common blocks appear twice – once [2.1, p.39, ll.11ff.] as
> general rule in the definition of "list item" (which are inherited by
> "extended list item" and "locator-list item"). [There are also some
> constraints and notes regarding common blocks)]. It does not really tell
> whether blank commons are permitted or not; some description is
> explicitly for named-common variables, leaving blank-common ones out
> (and undefined). But later sections explicitly make reference to blank
> commons, hence, one can assume they are permitted unless explicitly
> stated that they are not.
>
> And then very selectively for some items:
> * allocate – only with default allocator.
> * declare target – some restrictions and no blank commons
> * depend clause – no common permitted
> * threadprivate – some notes and explanation of the syntax (why?)
> also only here requirement regarding common blocks with bind(c)
> (why not also for declare target?)
> * linear clause – no common permitted
> * copyin – some notes
> * copyprivate – some notes
>
> As target test cases were suspiciously left out, I tries '!$omp target
> map(/name/)' which was rejected.
>From gcc-bugs-return-661848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 16:16:17 2019
Return-Path: <gcc-bugs-return-661848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30919 invoked by alias); 29 Nov 2019 16:16:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30861 invoked by uid 48); 29 Nov 2019 16:16:05 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] Idea for better error messages
Date: Fri, 29 Nov 2019 16:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92727-4-y8krMqGEHG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03642.txt.bz2
Content-length: 1386
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to David Brown from comment #6)
> I can see it is a challenge to get enough detail in the messages to be good
> for the more advanced users, and still simple enough and clear enough for
> more casual or inexperienced users.
>
> The static assertion looks good to me, and is clearly the easiest way to
> implement such a feature. But I appreciate that it would not be ideal for
> some people, and would hide useful messages from them.
I disagree. The static assert contains all you need to know, expert or not. The
benefit of seeing all the gory details is to figure out why something didn't
compile, and what (possibly implicit) requirement your code failed to meet. If
the maintainer of the library explicitly spelled out that requirement with a
static_assert, then there's no need to see any more detail, because there's no
need to infer the requirement from the code.
Unfortunately that nice diagnostic from the static_assert turns into a total
mess in C++20 mode, see Bug 92193 comment 2.
My preference for this bug would be to reassign it to libstdc++ and hope that
people pick up the baton and submit patches to add static_assert in places
where it improves the user experience. That can be done piecemeal, and improved
over time.
>From gcc-bugs-return-661849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 16:20:05 2019
Return-Path: <gcc-bugs-return-661849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33735 invoked by alias); 29 Nov 2019 16:20:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33625 invoked by uid 48); 29 Nov 2019 16:20:00 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92728] [OpenMP][OpenACC] Common-block name clause matching issues: common block needs to be defined before + blank common not supported
Date: Fri, 29 Nov 2019 16:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: openacc, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92728-4-WOMyt6HY9s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92728-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92728-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03643.txt.bz2
Content-length: 961
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92728
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
See also PR 92730 for a related issue (OpenMP's map() does not handle /common/)
Remark, as I only just remembered:
"Named common blocks of the same name shall be of the same size in all scoping
units of a program in which they appear, but blank common blocks may be of
different sizes." (Fortran 2018, 8.10.2.5)
If the common block is only on the host – and uses map(/block/), mapping single
variables is fine. If it is only on the device, it is also fine – it only
becomes interesting if the same-named common block is on both device and host.
In this case, they have to be named (= same size) and a copy(/map/) should
really copy the whole block and not only the (directly) used common-block
variables.
For OpenACC, device_resident seems to be about this feature, OpenMP seems to be
silent on this topic.
>From gcc-bugs-return-661850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 16:34:27 2019
Return-Path: <gcc-bugs-return-661850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60225 invoked by alias); 29 Nov 2019 16:34:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60192 invoked by uid 48); 29 Nov 2019 16:34:22 -0000
From: "david at westcontrol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] Idea for better error messages
Date: Fri, 29 Nov 2019 16:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: david at westcontrol dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92727-4-BgOXD9ecQK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03644.txt.bz2
Content-length: 212
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
--- Comment #8 from David Brown <david at westcontrol dot com> ---
I don't think there is anything more I can add at the moment. Thank you for
your efforts.
>From gcc-bugs-return-661851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 16:42:36 2019
Return-Path: <gcc-bugs-return-661851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115836 invoked by alias); 29 Nov 2019 16:42:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115722 invoked by uid 48); 29 Nov 2019 16:42:30 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 16:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-aotMAs9VQ3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03645.txt.bz2
Content-length: 1166
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Ok, so match.pd does the following transformations:
A*B+A -> (B+1)*A
A*B-A -> (B-1)*A
A-A*B -> (1-B)*A
A*B+A*C -> (B+C)*A
A*B-A*C -> (B-C)*A
(ignoring equivalent expressions with commutative + or *).
Let's consider for start just the simpler 3 cases.
For those, I believe the only cases where these introduce UB when it wasn't
before in two's complement world are:
A*B+A -> (B+1)*A with A==-1 && B==max
A*B+A -> (B+1)*A with A==0 && B==max
A*B-A -> (B-1)*A with A==0 && B==min
A-A*B -> (1-B)*A with A==-1 && B==-max
A-A*B -> (1-B)*A with A==0 && B==min
A-A*B -> (1-B)*A with A==0 && B==-max
Now, the current match.pd patterns disable this optimization if A might be 0 or
-1.
So, what we could do is: 1) for the A*B-A case, drop the must not be -1 check
2) add the checks for the ranges of the other operand, say for the first one it
is fine if we don't know anything about A (@0) if we know the B (@1) is not
maximum.
For the last 2, the question is if we can come up with something similar.
>From gcc-bugs-return-661852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 16:47:06 2019
Return-Path: <gcc-bugs-return-661852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125944 invoked by alias); 29 Nov 2019 16:47:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125889 invoked by uid 48); 29 Nov 2019 16:47:01 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] Idea for better error messages
Date: Fri, 29 Nov 2019 16:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92727-4-4fLDt319Oy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03646.txt.bz2
Content-length: 842
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
--- Comment #9 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #7)
> I disagree. The static assert contains all you need to know, expert or not.
> The benefit of seeing all the gory details is to figure out why something
> didn't compile, and what (possibly implicit) requirement your code failed to
> meet. If the maintainer of the library explicitly spelled out that
> requirement with a static_assert, then there's no need to see any more
> detail, because there's no need to infer the requirement from the code.
Uh? Here, we would get an error message saying only that X is not
copy-constructible. Sure, that's important to know. But it is helpful if the
compiler can point out why it isn't copy-constructible, which it currently
does.
>From gcc-bugs-return-661853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 16:59:58 2019
Return-Path: <gcc-bugs-return-661853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22221 invoked by alias); 29 Nov 2019 16:59:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22143 invoked by uid 55); 29 Nov 2019 16:59:54 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 16:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-9siz6ehYdx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03647.txt.bz2
Content-length: 1792
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #14 from rguenther at suse dot de <rguenther at suse dot de> ---
On November 29, 2019 4:59:35 PM GMT+01:00, "jakub at gcc dot gnu.org"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
>
>--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
>(In reply to Marc Glisse from comment #11)
>> (In reply to Jakub Jelinek from comment #10)
>> > I know, it will be a small complication, sure, but it can be
>handled.
>>
>> Ah, I think I understand now. But still
>>
>> x=-1
>> a=INT_MAX
>> a*x+x gives INT_MIN without overflow.
>> Now a could be (int)((unsigned)b-1) where b is INT_MIN. But we don't
>want to
>> generate b*x for that (INT_MIN*-1), since it overflows. So we would
>need to
>> do the multiplication in some unsigned type. If we go there (do
>everything
>> unsigned), we could do the transformation always, and restricting it
>is just
>> a heuristic for when the signed type information might be more useful
>than
>> the factorized form.
>
>The comments at least in fold-const.c say clearly that we do not want
>to
>perform unsigned multiplication.
Yeah, doing so early regresses things too much. Doing it late with wrapv was my
idea a while back. I've arranged it to be before the last reassoc pass but
moved(?) the last VRP before that.
>I was talking about the int a, b;
>((int)(a-1U))*b+b
>transformation into a*b.
>Even for a=0, it is -1*b+b into 0, there could be UB before, but there
>is none
>after. a=INT_MIN used to be INT_MAX*b+b and newly INT_MIN*b, well
>defined for
>b=0, UB for b > 0, UB for b < -1, but it is true that INT_MAX*-1+-1 is
>well
>defined INT_MIN, but INT_MIN*-1 is UB.
>So guess we need to use range info only then.
>From gcc-bugs-return-661854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 17:12:01 2019
Return-Path: <gcc-bugs-return-661854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38413 invoked by alias); 29 Nov 2019 17:12:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38355 invoked by uid 48); 29 Nov 2019 17:11:57 -0000
From: "rrrlasse at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92731] New: Data race on exception object thrown from std::future
Date: Fri, 29 Nov 2019 17:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rrrlasse at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03648.txt.bz2
Content-length: 2607
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92731
Bug ID: 92731
Summary: Data race on exception object thrown from std::future
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: rrrlasse at hotmail dot com
Target Milestone: ---
Created attachment 47397
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47397&action=edit
TSan output and .ii file
The source is compiled with:
g++ cpp.cpp -lpthread -fsanitize=thread -Wall -Wextra
After running for around 100 - 500 iteration in the for-loop of the main
thread, TSan reports a data race between the destructor of the exception object
and the strlen() loop.
If you omit the std::move(packaged_task) the warning disappears.
uname -a: Linux ubuntu 5.0.0-29-generic #31-Ubuntu SMP Thu Sep 12 13:05:32 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
g++ --version: g++ (Ubuntu 8.3.0-6ubuntu1) 8.3.0
Since you can apparently only add a single attachment, I've colledted the .ii
file and tsan report in a zip file.
Source code:
#include <iostream>
#include <optional>
#include <stdexcept>
#include <mutex>
#include <future>
#include <cstring>
std::condition_variable cv;
std::mutex mu;
std::function<void()> job;
bool has_job = false;
void looper() {
for (;;) {
std::unique_lock <std::mutex> ul(mu);
while (!has_job) {
cv.wait(ul);
}
has_job = false;
job();
}
}
// g++ cpp.cpp -lpthread -fsanitize=thread -Wall -Wextra
int main() {
std::thread t = std::thread(looper);
for (int c = 0; ; c++) {
try {
std::packaged_task<void()> packaged_task([]() { throw
std::runtime_error("aaaaaaaaaaaaaaaaa"); });
std::future<void> task_future =
packaged_task.get_future();
{
std::unique_lock<std::mutex> ul(mu);
job = [&]() {
#if 1
// tsan warning
std::packaged_task<void ()> tmp(std::move(packaged_task));
tmp();
#else
// no warning
packaged_task();
#endif
};
has_job = true;
cv.notify_one();
}
task_future.get();
}
catch (const std::runtime_error& e) {
for (int i = 0; i < 10; i++) {
[[maybe_unused]] int a = strlen(e.what());
}
}
}
}
>From gcc-bugs-return-661855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 17:22:26 2019
Return-Path: <gcc-bugs-return-661855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64133 invoked by alias); 29 Nov 2019 17:22:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63998 invoked by uid 48); 29 Nov 2019 17:22:20 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] Idea for better error messages
Date: Fri, 29 Nov 2019 17:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92727-4-qdkISuoSM0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03649.txt.bz2
Content-length: 689
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
For this specific call, yes. For the general case of "arguments do not meet the
function's requirements" there are no such notes from the compiler.
For example, v.emplace_back("blah") won't tell you anything more than that you
can't construct an X from "blah".
The bug in this example is that the push_back call needs to make a copy and the
type is not copyable. It's not a bug that the copy constructor is implictly
deleted. Knowing that the copy constructor is implicitly deleted and why,
doesn't actually help you figure out that you need to use std::move.
>From gcc-bugs-return-661856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 17:23:07 2019
Return-Path: <gcc-bugs-return-661856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70710 invoked by alias); 29 Nov 2019 17:23:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68629 invoked by uid 55); 29 Nov 2019 17:23:01 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/89014] Use-after-free in aarch64 -march=native
Date: Fri, 29 Nov 2019 17:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89014-4-IoziWCMHVD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89014-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89014-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03650.txt.bz2
Content-length: 1407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89014
--- Comment #9 from Wilco <wilco at gcc dot gnu.org> ---
Author: wilco
Date: Fri Nov 29 17:22:30 2019
New Revision: 278854
URL: https://gcc.gnu.org/viewcvs?rev=278854&root=gcc&view=rev
Log:
aarch64: fix use-after-free in -march=native (PR driver/89014)
Running:
$ valgrind ./xgcc -B. -c test.c -march=native
on aarch64 shows a use-after-free in host_detect_local_cpu due
to the std::string result of aarch64_get_extension_string_for_isa_flags
only living until immediately after a c_str call.
This leads to corrupt "-march=" values being passed to cc1.
This patch fixes the use-after-free, though it appears to also need
Tamar's patch here:
https://gcc.gnu.org/ml/gcc-patches/2018-12/msg01302.html
in order to generate valid values for cc1. This may have worked by
accident in the past, if the corrupt "-march=" value happened to be
0-terminated in the "right" place; with this patch it now appears
to reliably break without Tamar's patch.
Backport from mainline
2019-01-23 David Malcolm <dmalcolm@redhat.com>
PR driver/89014
* config/aarch64/driver-aarch64.c (host_detect_local_cpu): Fix
use-after-free of the result of
aarch64_get_extension_string_for_isa_flags.
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/aarch64/driver-aarch64.c
>From gcc-bugs-return-661857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 17:25:15 2019
Return-Path: <gcc-bugs-return-661857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75218 invoked by alias); 29 Nov 2019 17:25:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75188 invoked by uid 48); 29 Nov 2019 17:25:11 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92731] Data race on exception object thrown from std::future
Date: Fri, 29 Nov 2019 17:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92731-4-7NuVr4LLeL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03651.txt.bz2
Content-length: 191
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92731
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(You can add as many attachments as you like, but only one at a time.)
>From gcc-bugs-return-661858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 17:43:12 2019
Return-Path: <gcc-bugs-return-661858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115125 invoked by alias); 29 Nov 2019 17:43:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115058 invoked by uid 48); 29 Nov 2019 17:43:08 -0000
From: "klaus.doldinger64 at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92732] New: Bit-field with std::byte as member type cannot be initialized
Date: Fri, 29 Nov 2019 17:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: klaus.doldinger64 at googlemail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92732-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03652.txt.bz2
Content-length: 1015
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92732
Bug ID: 92732
Summary: Bit-field with std::byte as member type cannot be
initialized
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: klaus.doldinger64 at googlemail dot com
Target Milestone: ---
Since C++20 bit-field initializer are possible.
There seems to be a bug with std::byte an bit-fields.
struct Test {
std::byte a : 2 = std::byte{0}; // NOK
uint8_t b : 2 = 0; // OK
};
Compiling this with
g++ (GCC) 10.0.0 20191128 (experimental)
yields:
test93.cc:20:28: error: cannot convert 'std::byte' to 'unsigned char:2' in
initialization
20 | std::byte a : 2 = std::byte{0}; // NOK
| ^~~~~~~
| |
| std::byte
>From gcc-bugs-return-661859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:04:42 2019
Return-Path: <gcc-bugs-return-661859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22499 invoked by alias); 29 Nov 2019 18:04:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22336 invoked by uid 48); 29 Nov 2019 18:04:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 18:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-S52WbkZwhB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03653.txt.bz2
Content-length: 897
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
For
A*B+A*C -> (B+C)*A
the problematic cases are
A==-1 and B > 0 and C==(max-B)+1 (i.e. when B+C overflows to min)
or A==0 and B < 0 and C<min-B
or A==0 and B > 0 and C>max-B
(last two cases cover when B+C overflows)
For
A*B-A*C -> (B-C)*A
the problematic cases are
A==-1 and B > 0 and C==min+B (i.e. when B-C is min)
or A==0 and B < -1 and C>B-min
or A==0 and B >= 0 and C<B-max
(last two cases cover when B-C overflows)
Again, we perform the operation right now if A is not 0 and not -1 for certain.
I guess we could handle those cases by using something like
check_for_binary_op_overflow, except that for the case where A might be -1 and
plusminus equal to MINUS_EXPR we also need to make sure the result of B-C is
known not to be min.
>From gcc-bugs-return-661860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:11:25 2019
Return-Path: <gcc-bugs-return-661860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28719 invoked by alias); 29 Nov 2019 18:11:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28660 invoked by uid 48); 29 Nov 2019 18:11:21 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] Idea for better error messages
Date: Fri, 29 Nov 2019 18:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92727-4-mvqacs20UO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03654.txt.bz2
Content-length: 1343
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
--- Comment #11 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #10)
> The bug in this example is that the push_back call needs to make a copy and
> the type is not copyable. It's not a bug that the copy constructor is
> implictly deleted. Knowing that the copy constructor is implicitly deleted
> and why, doesn't actually help you figure out that you need to use std::move.
Indeed, there are 2 cases where you get the error:
- the type is meant to be move-only and you forgot to call std::move
- the type is meant to be copyable, but you did something that results in a
non-copyable type
In the first case, the static assertion is good and to the point. It could even
check if the type is move constructible and suggest using std::move in its
message.
In the second case, I'd love to know what I did wrong, and the extra
information is more than welcome.
As someone who is used to deciphering compiler messages, I tend to prefer
having too much, in case it might be useful, rather than too little. Anyway, I
am talking about verbosity in general, not specifically for this case, maybe
for this case the details are less important, I didn't think too hard about it,
and I am not preventing anyone from introducing the static_assert.
>From gcc-bugs-return-661861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:28:05 2019
Return-Path: <gcc-bugs-return-661861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100436 invoked by alias); 29 Nov 2019 18:28:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100294 invoked by uid 48); 29 Nov 2019 18:28:00 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 18:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-iUaQUD5LW3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03655.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #16 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #15)
> I guess we could handle those cases by using something like
> check_for_binary_op_overflow, except that for the case where A might be -1
> and plusminus equal to MINUS_EXPR we also need to make sure the result of
> B-C is known not to be min.
You may not need to worry about the multiplication overflowing. If a*b+a*c and
b+c are computed with an undefined overflow type and do not overflow, then
a*(b+c) cannot overflow either.
>From gcc-bugs-return-661862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:35:36 2019
Return-Path: <gcc-bugs-return-661862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113309 invoked by alias); 29 Nov 2019 18:35:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113270 invoked by uid 48); 29 Nov 2019 18:35:32 -0000
From: "rrrlasse at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92731] Data race on exception object thrown from std::future
Date: Fri, 29 Nov 2019 18:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rrrlasse at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92731-4-aZwUfacTUg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03656.txt.bz2
Content-length: 529
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92731
--- Comment #2 from Lasse Reinhold <rrrlasse at hotmail dot com> ---
As far as I remember I could only add a single file when I created the bug
report, and the option to add more showed up after completion.
Anyway, the c++ code isn't very idiomatic, but I can't see why it would be
illegal to let the child thread do a dummy-move (through the lambda reference
capture), compared to doing a move in the main thread. An everything is fully
synchronized through mutexes...
>From gcc-bugs-return-661863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:36:11 2019
Return-Path: <gcc-bugs-return-661863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115170 invoked by alias); 29 Nov 2019 18:36:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115097 invoked by uid 48); 29 Nov 2019 18:36:07 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 18:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-gihXfLknAO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03657.txt.bz2
Content-length: 3142
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Untested patch:
--- gcc/match.pd.jj 2019-11-05 14:59:22.546873967 +0100
+++ gcc/match.pd 2019-11-29 18:17:27.472002727 +0100
@@ -2480,18 +2480,42 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT)
(plusminus @0 (mult:c@3 @0 @2))
(if ((!ANY_INTEGRAL_TYPE_P (type)
|| TYPE_OVERFLOW_WRAPS (type)
+ /* For @0 + @0*@2 this transformation would introduce UB
+ (where there was none before) for @0 in [-1,0] and @2 max.
+ For @0 - @0*@2 this transformation would introduce UB
+ for @0 0 and @2 in [min,min+1] or @0 -1 and @2 min+1. */
|| (INTEGRAL_TYPE_P (type)
- && tree_expr_nonzero_p (@0)
- && expr_not_equal_to (@0, wi::minus_one (TYPE_PRECISION
(type)))))
+ && ((tree_expr_nonzero_p (@0)
+ && expr_not_equal_to (@0,
+ wi::minus_one (TYPE_PRECISION (type))))
+ || (plusminus == PLUS_EXPR
+ ? expr_not_equal_to (@2,
+ wi::max_value (TYPE_PRECISION (type), SIGNED))
+ /* Let's ignore the @0 -1 and @2 min case. */
+ : (expr_not_equal_to (@2,
+ wi::min_value (TYPE_PRECISION (type), SIGNED))
+ && expr_not_equal_to (@2,
+ wi::min_value (TYPE_PRECISION (type), SIGNED)
+ + 1))))))
&& single_use (@3))
(mult (plusminus { build_one_cst (type); } @2) @0)))
(simplify
(plusminus (mult:c@3 @0 @2) @0)
(if ((!ANY_INTEGRAL_TYPE_P (type)
|| TYPE_OVERFLOW_WRAPS (type)
+ /* For @0*@2 + @0 this transformation would introduce UB
+ (where there was none before) for @0 in [-1,0] and @2 max.
+ For @0*@2 - @0 this transformation would introduce UB
+ for @0 0 and @2 min. */
|| (INTEGRAL_TYPE_P (type)
- && tree_expr_nonzero_p (@0)
- && expr_not_equal_to (@0, wi::minus_one (TYPE_PRECISION
(type)))))
+ && ((tree_expr_nonzero_p (@0)
+ && (plusminus == MINUS_EXPR
+ || expr_not_equal_to (@0,
+ wi::minus_one (TYPE_PRECISION (type)))))
+ || expr_not_equal_to (@2,
+ (plusminus == PLUS_EXPR
+ ? wi::max_value (TYPE_PRECISION (type), SIGNED)
+ : wi::min_value (TYPE_PRECISION (type), SIGNED))))))
&& single_use (@3))
(mult (plusminus @2 { build_one_cst (type); }) @0))))))
This doesn't try to do anything about the A*B+A*C cases. Fixes the #c0
testcase and shows I've screwed up my simplified testcases,
the case that is fixed with this patch is e.g.
int foo (int t, int v)
{
int a = t - 1;
int b = a * v;
return b + v;
}
where we don't know anything about v (VARYING), but from a = t - 1 we know it
is not INT_MAX and can use that in the optimization.
>From gcc-bugs-return-661864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:42:37 2019
Return-Path: <gcc-bugs-return-661864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28184 invoked by alias); 29 Nov 2019 18:42:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21813 invoked by uid 48); 29 Nov 2019 18:42:32 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92733] New: linker errors for missing std::__alloc_on_move with a cross-compiler
Date: Fri, 29 Nov 2019 18:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03658.txt.bz2
Content-length: 4292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92733
Bug ID: 92733
Summary: linker errors for missing std::__alloc_on_move with a
cross-compiler
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
Building a cross-compiler (for all targets I've tried) fails with linker errors
like those below:
/build/gcc-svn/gcc/xg++ -B /build/gcc-svn/gcc -nostdinc++ -I
/build/gcc-svn/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu -I
/build/gcc-svn/x86_64-pc-linux-gnu/libstdc++-v3/include -I
/src/gcc/svn/libstdc++-v3/libsupc++ -I
/src/gcc/svn/libstdc++-v3/include/backward -L
/build/gcc-svn/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs -no-pie -O0 -g3
-DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wno-error=format-diag -Wmissing-format-attribute
-Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -fno-common -DHAVE_CONFIG_H -static-libstdc++
-static-libgcc -o cc1 c/c-lang.o c-family/stub-objc.o attribs.o c/c-errors.o
c/c-decl.o c/c-typeck.o c/c-convert.o c/c-aux-info.o c/c-objc-common.o
c/c-parser.o c/c-fold.o c/gimple-parser.o c-family/c-common.o
c-family/c-cppbuiltin.o c-family/c-dump.o c-family/c-format.o
c-family/c-gimplify.o c-family/c-indentation.o c-family/c-lex.o
c-family/c-omp.o c-family/c-opts.o c-family/c-pch.o c-family/c-ppoutput.o
c-family/c-pragma.o c-family/c-pretty-print.o c-family/c-semantics.o
c-family/c-ada-spec.o c-family/c-ubsan.o c-family/known-headers.o
c-family/c-attribs.o c-family/c-warn.o c-family/c-spellcheck.o glibc-c.o
rs6000-c.o \
cc1-checksum.o libbackend.a main.o libcommon-target.a libcommon.a
../libcpp/libcpp.a ../libdecnumber/libdecnumber.a libcommon.a
../libcpp/libcpp.a ../libbacktrace/.libs/libbacktrace.a
../libiberty/libiberty.a ../libdecnumber/libdecnumber.a
-L/ssd/build/powerpc64le-linux/gcc-svn/./isl/.libs -lisl
-L/ssd/build/powerpc64le-linux/gcc-svn/./gmp/.libs
-L/ssd/build/powerpc64le-linux/gcc-svn/./mpfr/src/.libs
-L/ssd/build/powerpc64le-linux/gcc-svn/./mpc/src/.libs -lmpc -lmpfr -lgmp
-rdynamic -ldl -L./../zlib -lz
/usr/bin/ld:
/build/gcc-svn/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a(string-inst.o):
in function `std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::operator=(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >&&)':
/ssd/build/gcc-svn/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/basic_string.h:716:
undefined reference to `void std::__alloc_on_move<std::allocator<char>
>(std::allocator<char>&, std::allocator<char>&)'
/usr/bin/ld:
/build/gcc-svn/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a(string-inst.o):
in function `std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::assign(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&)':
/ssd/build/gcc-svn/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/basic_string.h:1363:
undefined reference to `void std::__alloc_on_copy<std::allocator<char>
>(std::allocator<char>&, std::allocator<char> const&)'
/usr/bin/ld:
/build/gcc-svn/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a(string-inst.o):
in function `__gnu_cxx::__alloc_traits<std::allocator<char>,
char>::_S_on_swap(std::allocator<char>&, std::allocator<char>&)':
/ssd/build/gcc-svn/x86_64-pc-linux-gnu/libstdc++-v3/include/ext/alloc_traits.h:101:
undefined reference to `void std::__alloc_on_swap<std::allocator<char>
>(std::allocator<char>&, std::allocator<char>&)'
collect2: error: ld returned 1 exit status
make[2]: *** [/src/gcc/svn/gcc/c/Make-lang.in:85: cc1] Error 1
make[2]: Leaving directory '/ssd/build/powerpc64le-linux/gcc-svn/gcc'
make[1]: *** [Makefile:4370: all-gcc] Error 2
make[1]: Leaving directory '/ssd/build/powerpc64le-linux/gcc-svn'
make: *** [Makefile:966: all] Error 2
make: Leaving directory '/ssd/build/powerpc64le-linux/gcc-svn'
Command exited with non-zero status 2
>From gcc-bugs-return-661865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:43:55 2019
Return-Path: <gcc-bugs-return-661865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38245 invoked by alias); 29 Nov 2019 18:43:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38187 invoked by uid 48); 29 Nov 2019 18:43:51 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 18:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-bnZ0WzMF0o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03659.txt.bz2
Content-length: 916
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #16)
> (In reply to Jakub Jelinek from comment #15)
> > I guess we could handle those cases by using something like
> > check_for_binary_op_overflow, except that for the case where A might be -1
> > and plusminus equal to MINUS_EXPR we also need to make sure the result of
> > B-C is known not to be min.
>
> You may not need to worry about the multiplication overflowing. If a*b+a*c
> and b+c are computed with an undefined overflow type and do not overflow,
> then a*(b+c) cannot overflow either.
Yes, see above, for a*b+-a*c the only cases where UB would be introduced is
when b+-c overflows (but a subset of that, if we knew that a is not 0, we could
do better, as then all we care about is that (unsigned)(b+-c) didn't overflow
to INT_MIN).
>From gcc-bugs-return-661866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:46:18 2019
Return-Path: <gcc-bugs-return-661866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42323 invoked by alias); 29 Nov 2019 18:46:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42189 invoked by uid 48); 29 Nov 2019 18:46:14 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92683] [10 Regression] strncmp incorrect result with equal substrings and non-const bound
Date: Fri, 29 Nov 2019 18:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92683-4-XyEKTZfqd2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92683-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92683-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03660.txt.bz2
Content-length: 708
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92683
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Unless the problem in comment #0 persists on the targets please open new bugs
for these kinds of target-specific regressions in the test suite. I can't
build cross-compilers at the moment because of pr92733 so I can't easily verify
this but the test failure seems like a separate issue.
>From gcc-bugs-return-661867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:46:18 2019
Return-Path: <gcc-bugs-return-661867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42326 invoked by alias); 29 Nov 2019 18:46:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42201 invoked by uid 48); 29 Nov 2019 18:46:14 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83819] [meta-bug] missing strlen optimizations
Date: Fri, 29 Nov 2019 18:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-83819-4-zs7GEZcR80@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03661.txt.bz2
Content-length: 510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819
Bug 83819 depends on bug 92683, which changed state.
Bug 92683 Summary: [10 Regression] strncmp incorrect result with equal substrings and non-const bound
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92683
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-661868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:47:16 2019
Return-Path: <gcc-bugs-return-661868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45537 invoked by alias); 29 Nov 2019 18:47:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45355 invoked by uid 48); 29 Nov 2019 18:47:12 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92733] linker errors for missing std::__alloc_on_move with a cross-compiler
Date: Fri, 29 Nov 2019 18:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92733-4-B6V69sWjQA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03662.txt.bz2
Content-length: 253
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92733
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This error message does not make sense. Xgcc/xg++ should not be used to link
cc1. For a cross.
Can you provide how you configured?
>From gcc-bugs-return-661869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:52:50 2019
Return-Path: <gcc-bugs-return-661869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53995 invoked by alias); 29 Nov 2019 18:52:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53911 invoked by uid 48); 29 Nov 2019 18:52:46 -0000
From: "Theodore.Papadopoulo at inria dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92727] Idea for better error messages
Date: Fri, 29 Nov 2019 18:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: Theodore.Papadopoulo at inria dot fr
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92727-4-ublCp44SYS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03663.txt.bz2
Content-length: 2418
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92727
Theodore.Papadopoulo at inria dot fr changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Theodore.Papadopoulo@inria.
| |fr
--- Comment #12 from Theodore.Papadopoulo at inria dot fr ---
Sorry if this is message slightly diverges from the technical aspects...
While I'm used to parse the g++ messages, I must agree that sometimes it is too
much and not straight to the point... There has to be a way to make messages a
little more readable.
For one thing even finding the boundaries between two messages is not always
visually trivial. It might not be very difficult (with colors or blank lines or
...) to make this much easier to parse.
I must also say that in extreme cases (like eg some boost spirit stuff or more
generally some meta-template code), the error stack is huge and I have
appreciated what they do in boost spirit: In the code there is a comment that
states "if you have an error at the next line, this usually means you have done
that mistake".
Long before I was aware of static_assert, I considered implementing some kind
of pragma to achieve these high level messages, because this helps a lot. The
static_assert solution evoked above might be a way to implement this without
relying to extensions, which is nice... The only thing I regret slightly is the
verbiage related to the static_assert, which for me is an implementation detail
(of the way the error was generated). I understand very well that's the way
static_assert is supposed to work, but I would prefer a more normally looking
message, or maybe some visually easy to identify "hint" that would be provided
in addition to errors messages and that can help the developer at least in the
trivial cases...
I think that the quality of the error messages is very important for a compiler
and understand that this is a very difficult topic. I also know that very
important improvements were made these last two years, and I take the
opportunity to thank all those involved in that work.
Yet we should never forget that error messages must have two qualities:
- Allow to identify the cause of a problem (completeness).
- Allow to do so as quickly as possible (efficiency).
>From gcc-bugs-return-661870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 18:56:26 2019
Return-Path: <gcc-bugs-return-661870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58962 invoked by alias); 29 Nov 2019 18:56:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58877 invoked by uid 48); 29 Nov 2019 18:56:21 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92733] linker errors for missing std::__alloc_on_move with a cross-compiler
Date: Fri, 29 Nov 2019 18:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92733-4-mvuSvUuFQf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03664.txt.bz2
Content-length: 500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92733
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Thanks for the hint! It was indeed caused by a problem with my configure
script.
>From gcc-bugs-return-661871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 19:03:55 2019
Return-Path: <gcc-bugs-return-661871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69963 invoked by alias); 29 Nov 2019 19:03:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69849 invoked by uid 48); 29 Nov 2019 19:03:49 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92683] [10 Regression] strncmp incorrect result with equal substrings and non-const bound
Date: Fri, 29 Nov 2019 19:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92683-4-fU2R0bDTKO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92683-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92683-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03665.txt.bz2
Content-length: 2862
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92683
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
With pr92733 resolved I can verify that the test case from comment #0 is
compiled correctly by the sparc-sun-solaris2.11 cross:
$ cat pr92683.c && /build/sparc-sun-solaris2.11/gcc-svn/gcc/xgcc -B
/build/sparc-sun-solaris2.11/gcc-svn/gcc -O1 -S -Wall -Wextra
-fdump-tree-forwprop1=/dev/stdout pr92683.c
int f (void)
{
return __builtin_strncmp ("123", "1234", 3); // correctly folded to zero
}
int g (void)
{
int n = 3;
return __builtin_strncmp ("123", "1234", n); // incorrectly folded to -1
}
;; Function f (f, funcdef_no=0, decl_uid=1482, cgraph_uid=1, symbol_order=0)
f ()
{
<bb 2> :
return 0;
}
;; Function g (g, funcdef_no=1, decl_uid=1485, cgraph_uid=2, symbol_order=1)
g ()
{
int n;
<bb 2> :
return 0;
}
The gcc.dg/strcmpopt_8.c test also passes for me when compiled with the
sparc-sun-solaris2.11 cross:
$ nice make -C /build/sparc-sun-solaris2.11/gcc-svn/gcc check-c 'CFLAGS=-O0
-g3' 'CXXFLAGS=-O0 -g3' 'STAGE1_CFLAGS=-O0 -g3' 'STAGE1_CXXFLAGS=-O0 -g3'
RUNTESTFLAGS="dg.exp=gcc.dg/strcmpopt_8.c"
make: Entering directory '/ssd/build/sparc-sun-solaris2.11/gcc-svn/gcc'
...
Test run by msebor on Fri Nov 29 11:59:25 2019
Target is sparc-sun-solaris2.11
Host is x86_64-pc-linux-gnu
=== gcc tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /src/gcc/svn/gcc/testsuite/config/default.exp as tool-and-target-specific
interface file.
WARNING: Assuming target board is the local machine (which is probably wrong).
You may need to set your DEJAGNU environment variable.
Running /src/gcc/svn/gcc/testsuite/gcc.dg/dg.exp ...
=== gcc Summary ===
# of expected passes 4
/ssd/build/sparc-sun-solaris2.11/gcc-svn/gcc/xgcc version 10.0.0 20191129
(experimental) (GCC)
make[1]: Leaving directory '/ssd/build/sparc-sun-solaris2.11/gcc-svn/gcc'
make: Leaving directory '/ssd/build/sparc-sun-solaris2.11/gcc-svn/gcc'
The output looks as expected:
$ /build/sparc-sun-solaris2.11/gcc-svn/gcc/xgcc -B
/build/sparc-sun-solaris2.11/gcc-svn/gcc -O1 -S -Wall -Wextra
-fdump-tree-forwprop1=/dev/stdout
/src/gcc/svn/gcc/testsuite/gcc.dg/strcmpopt_8.c
;; Function test_literal (test_literal, funcdef_no=0, decl_uid=1485,
cgraph_uid=1, symbol_order=0)
test_literal ()
{
int zero;
size_t max;
<bb 2> :
return;
}
;; Function test_cst_array (test_cst_array, funcdef_no=1, decl_uid=1492,
cgraph_uid=2, symbol_order=3)
test_cst_array ()
{
int zero;
size_t max;
<bb 2> :
return;
}
>From gcc-bugs-return-661872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 19:10:53 2019
Return-Path: <gcc-bugs-return-661872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80135 invoked by alias); 29 Nov 2019 19:10:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80083 invoked by uid 48); 29 Nov 2019 19:10:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92732] Bit-field of scoped enumeration type cannot be initialized
Date: Fri, 29 Nov 2019 19:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on short_desc everconfirmed
Message-ID: <bug-92732-4-jKymFbh7W0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92732-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92732-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03666.txt.bz2
Content-length: 1304
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92732
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-29
Summary|Bit-field with std::byte as |Bit-field of scoped
|member type cannot be |enumeration type cannot be
|initialized |initialized
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is not a complete testcase, it's missing the relevant headers. I already
provided a reduced testcase on the mailing list (and explained that the problem
is not specific to std::byte).
enum class byte : unsigned char { };
using uint8_t = unsigned char;
struct Test
{
byte a : 2 = byte{0}; // NOK
uint8_t b : 2 = 0; // OK
};
bf.cc:6:18: error: cannot convert 'byte' to 'unsigned char:2' in initialization
6 | byte a : 2 = byte{0}; // NOK
| ^~~~~~~
| |
| byte
>From gcc-bugs-return-661873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 19:13:57 2019
Return-Path: <gcc-bugs-return-661873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84958 invoked by alias); 29 Nov 2019 19:13:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84887 invoked by uid 48); 29 Nov 2019 19:13:53 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92731] Data race on exception object thrown from std::future
Date: Fri, 29 Nov 2019 19:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92731-4-O2i9feLoIh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03667.txt.bz2
Content-length: 476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92731
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Lasse Reinhold from comment #2)
> As far as I remember I could only add a single file when I created the bug
> report, and the option to add more showed up after completion.
As I said, you can only add one at a time. One on the original submission, and
then you can add another one, and submit that, and add another one, and submit
that.
>From gcc-bugs-return-661874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 19:21:47 2019
Return-Path: <gcc-bugs-return-661874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98749 invoked by alias); 29 Nov 2019 19:21:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98561 invoked by uid 48); 29 Nov 2019 19:21:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 19:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92712-4-KSr2nU88Iy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03668.txt.bz2
Content-length: 262
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47398
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47398&action=edit
gcc10-pr92712.patch
Full untested patch.
>From gcc-bugs-return-661875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 19:21:59 2019
Return-Path: <gcc-bugs-return-661875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99595 invoked by alias); 29 Nov 2019 19:21:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99442 invoked by uid 48); 29 Nov 2019 19:21:55 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66773] sign-compare warning for == and != are pretty useless
Date: Fri, 29 Nov 2019 19:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.7.2
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66773-4-NrGWJ3zYO9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03669.txt.bz2
Content-length: 778
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66773
--- Comment #21 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Daniel Marjamäki from comment #20)
> Ping. Your "much better" code does not work.
I said that this is much better than an explicit cast. It is. And it behaves
identically.
If the user expects C to provide tests for "mathematically different", the
user has some learning to do.
If, as I said, the user uses explicit casts, that's not good. Much better
already is to use implicit casts, as I said; and much better than that is
to fix the problems at the root (use proper types everywhere), as I said.
There is no simple fix, so GCC cannot give good guidance.
Oh, and don't try to insult me please, I'm much too dumb for that.
>From gcc-bugs-return-661876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 19:34:01 2019
Return-Path: <gcc-bugs-return-661876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120681 invoked by alias); 29 Nov 2019 19:34:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120347 invoked by uid 48); 29 Nov 2019 19:33:57 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92734] New: Missing match.pd simplification done by fold_binary_loc on generic
Date: Fri, 29 Nov 2019 19:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03670.txt.bz2
Content-length: 913
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92734
Bug ID: 92734
Summary: Missing match.pd simplification done by
fold_binary_loc on generic
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
While working on the PR92712 testcases, I had to remove one testcase I wrote,
because we haven't simplified stuff in GIMPLE in that case (we do on RTL):
int
foo (int t)
{
return 1 - (int) (1U - t);
}
int
bar (int t)
{
int a = 1U - t;
return 1 - a;
}
The first function is optimized into return t during fold_binary_loc associate:
but there isn't anything in match.pd that handles this (or should it be some
special pass?).
>From gcc-bugs-return-661877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 19:54:14 2019
Return-Path: <gcc-bugs-return-661877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33577 invoked by alias); 29 Nov 2019 19:54:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33467 invoked by uid 48); 29 Nov 2019 19:54:10 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92718] [8/9/10 Regression] Bogus Wstringop-overflow in __builtin_memset() of an element of array of size 1 of struct
Date: Fri, 29 Nov 2019 19:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc see_also blocked
Message-ID: <bug-92718-4-vPKRH5jqeA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92718-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92718-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03671.txt.bz2
Content-length: 1021
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92718
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
CC| |msebor at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=36602
Blocks| |88443
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Replacing the memset call with the assignment '*p = (struct s){ 0 };' avoids
the warning and also results in better/optimal code. (As suggested in pr36602,
that would be a useful optimization independent of the warning.)
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443
[Bug 88443] [meta-bug] bogus/missing -Wstringop-overflow warnings
>From gcc-bugs-return-661879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 19:55:14 2019
Return-Path: <gcc-bugs-return-661879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36368 invoked by alias); 29 Nov 2019 19:55:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36249 invoked by uid 48); 29 Nov 2019 19:55:09 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91003] [10 Regression] ICE when compiling LAPACK (CGEGV) with optimization
Date: Fri, 29 Nov 2019 19:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91003-4-LNTkhOEs4G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91003-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91003-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03673.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91003
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-661878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 19:55:02 2019
Return-Path: <gcc-bugs-return-661878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35531 invoked by alias); 29 Nov 2019 19:55:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35237 invoked by uid 55); 29 Nov 2019 19:54:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91003] [10 Regression] ICE when compiling LAPACK (CGEGV) with optimization
Date: Fri, 29 Nov 2019 19:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91003-4-RCUcxlhP2K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91003-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91003-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03672.txt.bz2
Content-length: 832
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91003
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Fri Nov 29 19:54:25 2019
New Revision: 278860
URL: https://gcc.gnu.org/viewcvs?rev=278860&root=gcc&view=rev
Log:
2019-11-29 Richard Biener <rguenther@suse.de>
PR tree-optimization/91003
* tree-vect-slp.c (vect_mask_constant_operand_p): Pass in the
operand number, avoid handling the non-condition operands of
COND_EXPRs as comparisons.
(vect_get_constant_vectors): Pass down the operand number.
(vect_get_slp_defs): Likewise.
* gfortran.dg/pr91003.f90: New testcase.
Added:
trunk/gcc/testsuite/gfortran.dg/pr91003.f90
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-vect-slp.c
>From gcc-bugs-return-661880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 20:22:59 2019
Return-Path: <gcc-bugs-return-661880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89931 invoked by alias); 29 Nov 2019 20:22:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89842 invoked by uid 48); 29 Nov 2019 20:22:55 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Fri, 29 Nov 2019 20:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-dTZEMnhQzh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03674.txt.bz2
Content-length: 288
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #20 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #19)
> Created attachment 47398 [details]
> gcc10-pr92712.patch
>
> Full untested patch.
The patch looks very good to me :-)
>From gcc-bugs-return-661881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 20:35:03 2019
Return-Path: <gcc-bugs-return-661881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100560 invoked by alias); 29 Nov 2019 20:35:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100490 invoked by uid 48); 29 Nov 2019 20:34:57 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92698] Unnecessary copy in overlapping array assignment
Date: Fri, 29 Nov 2019 20:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92698-4-PQILrYM69l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03675.txt.bz2
Content-length: 2025
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92698
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to mjr19 from comment #0)
> subroutine cpy(a,src,dest,len)
> integer, intent(in) :: src,dest,len
> real(kind(1d0)), intent(inout) :: a(:)
>
> a(dest:dest+len-1)=a(src:src+len-1)
>
> end subroutine cpy
>
>
> seems to compile to malloc tmp array, inline copy to tmp, inline copy from
> tmp, free tmp in gfortran 7.4 and 8.3. Gfortran 9.2 modifies this by
> replacing the inline copies with memcpy at -O3.
>
> Fortran permits the source and destination to overlap, so a single call to
> memcpy would be wrong.
It would also be wrong for another reason: a is not known to be contiguous
at compile-time. The subroutine has to account for the fact that the
caller could pass a non-contiguous array slice, for example via
call cpy (a(1:10:2),1,2,2)
If the test case said
subroutine cpy(a,src,dest,len)
integer, intent(in) :: src,dest,len
real(kind(1d0)), intent(inout), contiguous :: a(:)
or
subroutine cpy(a,src,dest,len,n)
integer, intent(in) :: src,dest,len,n
real(kind(1d0)), intent(inout), contiguous :: a(n)
then putting in a memmove could indeed help, and the caller has to repack
the array on call, and unpack on return (which would defeat the purpose
of the optimization).
However, I am not convinced that this is something worth pursuing.
Instead of calling a subroutine, the user might as well write an
assignment statement directly into the rogram. This also has the
advantage that, if the relationship between src and dest is known,
for example via
a(n:n+len-1) = a(n+1:n+len)
the compiler will actually optimize this into a memmove (provided
it knows the array is contiguous).
>From gcc-bugs-return-661882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 20:56:47 2019
Return-Path: <gcc-bugs-return-661882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61729 invoked by alias); 29 Nov 2019 20:56:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61683 invoked by uid 55); 29 Nov 2019 20:56:42 -0000
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92629] internal compiler error: in convert_mpz_to_unsigned, at fortran/simplify.c:173
Date: Fri, 29 Nov 2019 20:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: anlauf at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92629-4-PXdK9rlzfb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92629-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92629-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03676.txt.bz2
Content-length: 772
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92629
--- Comment #5 from anlauf at gcc dot gnu.org ---
Author: anlauf
Date: Fri Nov 29 20:56:11 2019
New Revision: 278862
URL: https://gcc.gnu.org/viewcvs?rev=278862&root=gcc&view=rev
Log:
2019-11-29 Harald Anlauf <anlauf@gmx.de>
Backport from mainline
PR fortran/92629
* simplify.c (convert_mpz_to_unsigned): Skip assert for argument
range when -fno-range-check is specified.
PR fortran/92629
* gfortran.dg/pr92629.f90: New testcase.
Added:
branches/gcc-9-branch/gcc/testsuite/gfortran.dg/pr92629.f90
Modified:
branches/gcc-9-branch/gcc/fortran/ChangeLog
branches/gcc-9-branch/gcc/fortran/simplify.c
branches/gcc-9-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 20:56:59 2019
Return-Path: <gcc-bugs-return-661883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62418 invoked by alias); 29 Nov 2019 20:56:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62384 invoked by uid 48); 29 Nov 2019 20:56:55 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92732] Bit-field of scoped enumeration type cannot be initialized
Date: Fri, 29 Nov 2019 20:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-92732-4-jDllPZS7bz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92732-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92732-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03677.txt.bz2
Content-length: 579
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92732
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47399
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47399&action=edit
gcc10-pr92732.patch
Untested fix.
>From gcc-bugs-return-661884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 20:59:15 2019
Return-Path: <gcc-bugs-return-661884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66563 invoked by alias); 29 Nov 2019 20:59:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66522 invoked by uid 55); 29 Nov 2019 20:59:11 -0000
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92629] internal compiler error: in convert_mpz_to_unsigned, at fortran/simplify.c:173
Date: Fri, 29 Nov 2019 20:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: anlauf at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92629-4-nyIVeES7Ph@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92629-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92629-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03678.txt.bz2
Content-length: 772
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92629
--- Comment #6 from anlauf at gcc dot gnu.org ---
Author: anlauf
Date: Fri Nov 29 20:58:39 2019
New Revision: 278863
URL: https://gcc.gnu.org/viewcvs?rev=278863&root=gcc&view=rev
Log:
2019-11-29 Harald Anlauf <anlauf@gmx.de>
Backport from mainline
PR fortran/92629
* simplify.c (convert_mpz_to_unsigned): Skip assert for argument
range when -fno-range-check is specified.
PR fortran/92629
* gfortran.dg/pr92629.f90: New testcase.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/pr92629.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/simplify.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 21:03:04 2019
Return-Path: <gcc-bugs-return-661885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70723 invoked by alias); 29 Nov 2019 21:03:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70591 invoked by uid 48); 29 Nov 2019 21:02:59 -0000
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92629] internal compiler error: in convert_mpz_to_unsigned, at fortran/simplify.c:173
Date: Fri, 29 Nov 2019 21:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: anlauf at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-92629-4-dDw947dWvj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92629-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92629-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03679.txt.bz2
Content-length: 496
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92629
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |8.4
--- Comment #7 from anlauf at gcc dot gnu.org ---
Fixed on trunk, 9- and 8-branch.
Thanks for the report.
>From gcc-bugs-return-661886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 21:18:24 2019
Return-Path: <gcc-bugs-return-661886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124527 invoked by alias); 29 Nov 2019 21:18:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124023 invoked by uid 48); 29 Nov 2019 21:18:18 -0000
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/71196] f951: internal compiler error: in gfc_conv_string_init, at fortran/trans-const.c:149
Date: Fri, 29 Nov 2019 21:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-71196-4-f5p0ILqgv1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71196-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71196-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03680.txt.bz2
Content-length: 903
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71196
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gcc dot gnu.org
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to G. Steinmetz from comment #5)
> $ cat z8.f90
> program p
> type t
> character(3) :: c
> integer :: i
> end type
> type t2
> type(t) :: a
> end type
> type(t2) :: x
> data x%a%i / 1 /
> print *, x
> end
> # ICE, see comment above
Adding -fdump-fortran-original may give a possible hint as to the origin of the
problem:
symtree: 'x' || symbol: 'x'
type spec : (DERIVED t2)
attributes: (VARIABLE DATA)
value: t2(t(1))
This cannot be right.
>From gcc-bugs-return-661887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 21:25:29 2019
Return-Path: <gcc-bugs-return-661887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2920 invoked by alias); 29 Nov 2019 21:25:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2785 invoked by uid 48); 29 Nov 2019 21:25:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92734] Missing match.pd simplification done by fold_binary_loc on generic
Date: Fri, 29 Nov 2019 21:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92734-4-B6pqNQj3DC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03681.txt.bz2
Content-length: 306
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92734
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Of course we have reassoc, but in there we punt on the non-wrapping integral
types, because reassociation is generally unsafe for them. There are just
special cases that can be handled.
>From gcc-bugs-return-661888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 21:31:49 2019
Return-Path: <gcc-bugs-return-661888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30602 invoked by alias); 29 Nov 2019 21:31:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30558 invoked by uid 48); 29 Nov 2019 21:31:43 -0000
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/71196] f951: internal compiler error: in gfc_conv_string_init, at fortran/trans-const.c:149
Date: Fri, 29 Nov 2019 21:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-71196-4-xwQK1yhr3g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71196-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71196-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03682.txt.bz2
Content-length: 989
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71196
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
--- Comment #7 from anlauf at gcc dot gnu.org ---
More fun and confusion:
program p
type t
integer :: k
integer :: j
integer :: i
end type t
type t2
type(t) :: a
end type t2
type(t2) :: x
data x%a%k / 42 /
data x%a%i / 1 /
data x%a%j / -9 /
print *, x
end
compiles ok but prints:
-9 1 42
(should be: 42 -9 1)
-fdump-fortran-original says:
symtree: 'x' || symbol: 'x'
type spec : (DERIVED t2)
attributes: (VARIABLE DATA)
value: t2(t(-9 , 1 , 42))
How could the init data get mixed up, so that they are assigned in the
reverse order of how the appear in the code?
>From gcc-bugs-return-661889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 21:51:25 2019
Return-Path: <gcc-bugs-return-661889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47747 invoked by alias); 29 Nov 2019 21:51:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47706 invoked by uid 48); 29 Nov 2019 21:51:20 -0000
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/71196] f951: internal compiler error: in gfc_conv_string_init, at fortran/trans-const.c:149
Date: Fri, 29 Nov 2019 21:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-71196-4-NvdANRHqaY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71196-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71196-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03683.txt.bz2
Content-length: 644
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71196
--- Comment #8 from anlauf at gcc dot gnu.org ---
The issue seems to be related to the depth of DT nesting.
If there is only one level, the issue does not occur. E.g.
program p
type t
integer :: k
integer :: j
integer :: i
end type t
type(t) :: y
data y%k / 42 /
data y%i / 1 /
data y%j / -9 /
print *, y
end
prints:
42 -9 1
and we have:
symtree: 'y' || symbol: 'y'
type spec : (DERIVED t)
attributes: (VARIABLE DATA)
value: t(42 , -9 , 1)
as it should be.
>From gcc-bugs-return-661890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Nov 29 22:04:58 2019
Return-Path: <gcc-bugs-return-661890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62514 invoked by alias); 29 Nov 2019 22:04:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62421 invoked by uid 55); 29 Nov 2019 22:04:52 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92283] [10 Regression] 454.calculix miscomparison since r276645 with -O2 -march=znver2
Date: Fri, 29 Nov 2019 22:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ra, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92283-4-IqhBSddo9Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92283-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92283-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03684.txt.bz2
Content-length: 519
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92283
--- Comment #27 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
Author: vmakarov
Date: Fri Nov 29 22:04:21 2019
New Revision: 278865
URL: https://gcc.gnu.org/viewcvs?rev=278865&root=gcc&view=rev
Log:
2019-11-29 Vladimir Makarov <vmakarov@redhat.com>
PR rtl-optimization/92283
* lra.c (lra): Update reg notes after inheritance sub-pass and
before constraint sub-pass.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/lra.c
>From gcc-bugs-return-661891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 00:01:53 2019
Return-Path: <gcc-bugs-return-661891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95320 invoked by alias); 30 Nov 2019 00:01:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95256 invoked by uid 48); 30 Nov 2019 00:01:49 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66773] sign-compare warning for == and != are pretty useless
Date: Sat, 30 Nov 2019 00:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.7.2
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vincent-gcc at vinc17 dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66773-4-2u3IYWLlMK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03685.txt.bz2
Content-length: 691
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66773
--- Comment #22 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
(In reply to Segher Boessenkool from comment #21)
> If, as I said, the user uses explicit casts, that's not good. Much better
> already is to use implicit casts, as I said;
There's no such thing as implicit casts. Casts are always explicit.
> and much better than that is
> to fix the problems at the root (use proper types everywhere), as I said.
This will not necessarily solve the problem, because the size and/or the
signedness of a type may be unknown (the signedness can be detected with a
macro, but there's no way to change the sign of a type).
>From gcc-bugs-return-661892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 00:58:10 2019
Return-Path: <gcc-bugs-return-661892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127806 invoked by alias); 30 Nov 2019 00:58:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121470 invoked by uid 48); 30 Nov 2019 00:58:06 -0000
From: "marcpawl at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92735] New: unused member variable causes code to compile for member to function for undefined function
Date: Sat, 30 Nov 2019 00:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marcpawl at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92735-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03686.txt.bz2
Content-length: 1644
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92735
Bug ID: 92735
Summary: unused member variable causes code to compile for
member to function for undefined function
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: marcpawl at gmail dot com
Target Milestone: ---
Marc Pawlowsky <marcpawl@gmail.com>
Thu, Nov 28, 8:25 PM (23 hours ago)
to gcc-bugzilla-account-request
https://godbolt.org/z/SFZmZJ
In clang you get
no member names 'hello' in 'Bad'
which is the expected result.
In all GCC versions using --std=c++17 from 5.2 onwards the code compiles.
#include <type_traits>
#include <cstdio>
struct Foo {
virtual void hello(int) = 0;
};
struct Bar : public Foo {
void hello(int) override {};
};
struct Bad { };
template <typename T>
struct is_Foo {
using hello_fn_t = void (T::*)(int);
constexpr static void (T::*hello)(int) = &T::hello;
static constexpr bool value=true;
};
template <typename T>
auto say(T& t) -> std::enable_if_t<is_Foo<T>::value, void>{
//U u; // Line 22
//t.hello(4); // Line 23
puts("hello\n");
}
int main()
{
//Bar b;;
//Foo& f = b;
//say(b);
//say(f);
Bad bad;
say(bad);
}
If you change say to
template <typename T, typename U=is_Foo<T>>
void say(T& t)
{
U u; // Line 22
//t.hello(4); // Line 23
}
you get the same errors in clang, but no errors in gcc.
==
on a related not I sent to clang bug report where if value is not static the
code will compile.
>From gcc-bugs-return-661893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 03:57:26 2019
Return-Path: <gcc-bugs-return-661893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58452 invoked by alias); 30 Nov 2019 03:57:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58412 invoked by uid 48); 30 Nov 2019 03:57:21 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92688] including <regex> introduce the name index to global namespace scope
Date: Sat, 30 Nov 2019 03:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92688-4-9SAKWLGMqb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92688-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92688-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03687.txt.bz2
Content-length: 548
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92688
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #9 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> Plus GCC does not have a POSIX option.
This has come up in a few other bugs; I'll find their numbers later...
>From gcc-bugs-return-661894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 04:02:39 2019
Return-Path: <gcc-bugs-return-661894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70915 invoked by alias); 30 Nov 2019 04:02:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70847 invoked by uid 48); 30 Nov 2019 04:02:34 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/92696] #pragma GCC diagnostic ... interferes with if/else
Date: Sat, 30 Nov 2019 04:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92696-4-jyHbTx0o6q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92696-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92696-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03688.txt.bz2
Content-length: 829
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92696
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> (In reply to Andrew Pinski from comment #2)
> > Also #pragma are considered statements. There is another issue like this
> > but instead using _Pragma .
>
> I should say some Pragmas are considered statements.
>
> See PR 90400 Which shows the similar issue but with _Pragma. In this case,
> these Pragmas are considered statements.
also some of the other bugs related to it, too
>From gcc-bugs-return-661895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 04:07:41 2019
Return-Path: <gcc-bugs-return-661895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75380 invoked by alias); 30 Nov 2019 04:07:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75325 invoked by uid 48); 30 Nov 2019 04:07:36 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92700] wrong "unintialized" warning with std::optional
Date: Sat, 30 Nov 2019 04:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92700-4-lMGYOlqaYH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92700-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92700-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03689.txt.bz2
Content-length: 646
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92700
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> We at least do have other PRs complaining about std::optional
I think 2 of the Martins were working on a patch to split off warnings like
this into a separate -Wmaybe-uninitialized-aggregates to handle this
>From gcc-bugs-return-661896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 04:47:16 2019
Return-Path: <gcc-bugs-return-661896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115297 invoked by alias); 30 Nov 2019 04:47:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115149 invoked by uid 48); 30 Nov 2019 04:47:11 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/70196] inconsistent constness of inequality of weak symbol addresses
Date: Sat, 30 Nov 2019 04:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: minor
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-70196-4-teEX0OzDMS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70196-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70196-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03690.txt.bz2
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70196
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Nathan Sidwell from comment #4)
> ordering comparison of pointers is only well-defined when the two pointers
> point into the same object (including one-past-the-end). [expr.ref]/4
>
Right, there's a warning from -Wextra for that, there's a bug to split it off
into its own warning, too...
>From gcc-bugs-return-661897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 04:48:40 2019
Return-Path: <gcc-bugs-return-661897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121359 invoked by alias); 30 Nov 2019 04:48:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116868 invoked by uid 48); 30 Nov 2019 04:48:30 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90647] Warn on returning a lambda with captured local variables
Date: Sat, 30 Nov 2019 04:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90647-4-TwLGBBNVde@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90647-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90647-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03691.txt.bz2
Content-length: 449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90647
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Antony Polukhin from comment #0)
> Consider the example:
>
> auto test(int s) {
> return [&s] { return s; };
> }
>
>
> `s` is a local variable, so we return a lambda that has a dangling reference.
>
> It would be nice to have a warning for such cases.
Under -Wreturn-local-addr, or a new flag?
>From gcc-bugs-return-661898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 05:55:16 2019
Return-Path: <gcc-bugs-return-661898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77945 invoked by alias); 30 Nov 2019 05:55:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77915 invoked by uid 48); 30 Nov 2019 05:55:12 -0000
From: "chinoune.mehdi at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92736] New: Error when using a variable from a module in a submodule and its parent module.
Date: Sat, 30 Nov 2019 05:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: chinoune.mehdi at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03692.txt.bz2
Content-length: 2134
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92736
Bug ID: 92736
Summary: Error when using a variable from a module in a
submodule and its parent module.
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: chinoune.mehdi at hotmail dot com
Target Milestone: ---
gfortran recently start to reject this code :
module m1
implicit none
integer, parameter :: i = 10
end module m1
module m2
use m1, only : i
implicit none
interface
module subroutine sb1()
end subroutine sb1
end interface
end module m2
submodule(m2) s1
use m1, only : i
implicit none
contains
module subroutine sb1
print*,"hello"
end subroutine sb1
end submodule s1
gfortran-9 -c file.f90
15 | submodule(m2) s1
| 1
16 | use m1, only : i
| 2
Error:
Symbol ‘i’ at (1) conflicts with the symbol at (2)
The error message is not clear!
I can compile it using gfortran 8.3.0 and 9.2.0, but it fails with 9.2.1 and
10.0
I think this is where it started failing :
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=274609
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=274608
>From gcc-bugs-return-661899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 06:46:11 2019
Return-Path: <gcc-bugs-return-661899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96765 invoked by alias); 30 Nov 2019 06:46:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96721 invoked by uid 48); 30 Nov 2019 06:46:06 -0000
From: "rrrlasse at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92731] Data race on exception object thrown from std::future
Date: Sat, 30 Nov 2019 06:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rrrlasse at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92731-4-XZEqXWrp66@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03693.txt.bz2
Content-length: 1249
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92731
--- Comment #4 from Lasse Reinhold <rrrlasse at hotmail dot com> ---
Some simplifications, and also tried with atomics instead of mutexes, to no
avail:
#include <iostream>
#include <stdexcept>
#include <future>
#include <assert.h>
std::function<void()> job;
std::atomic<bool> has_job{ false };
int main() {
std::thread t = std::thread([]() {
for (;;) {
if (has_job.load(std::memory_order_acquire)) {
job();
has_job.store(false, std::memory_order_release);
}
}
});
for (int c = 0; ; c++) {
if (!has_job.load(std::memory_order_acquire)) {
try {
std::packaged_task<void()> packaged_task([]() { throw 1234; });
std::future<void> task_future = packaged_task.get_future();
job = [&]() {
std::packaged_task<void ()> tmp(std::move(packaged_task));
tmp();
};
has_job.store(true, std::memory_order_release);
task_future.get();
}
catch (const int& e) {
assert(e == 1234);
}
}
}
}
>From gcc-bugs-return-661900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 06:58:58 2019
Return-Path: <gcc-bugs-return-661900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103889 invoked by alias); 30 Nov 2019 06:58:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103848 invoked by uid 48); 30 Nov 2019 06:58:54 -0000
From: "daniel.marjamaki at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66773] sign-compare warning for == and != are pretty useless
Date: Sat, 30 Nov 2019 06:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.7.2
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: daniel.marjamaki at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66773-4-Vkk0zytsJ6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03694.txt.bz2
Content-length: 1126
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66773
--- Comment #23 from Daniel Marjamäki <daniel.marjamaki at gmail dot com> ---
> If the user expects C to provide tests for "mathematically different", the
user has some learning to do.
I believe most users can appreciate this. But few users fully understand the
integer conversions. I think it's dangerous. :-(
> If, as I said, the user uses explicit casts, that's not good. Much better
already is to use implicit casts, as I said; and much better than that is
to fix the problems at the root (use proper types everywhere), as I said.
You are de-facto advocating explicit casts because that is how everybody fixes
these.
The advice to use proper types is good, in my opinion everybody tries to do
that. However as far as I see it's impossible in practice to never mix signed
and unsigned types in real projects.
> There is no simple fix, so GCC cannot give good guidance.
Then people just blindly use explicit casts.. and I dislike that.
> Oh, and don't try to insult me please, I'm much too dumb for that.
I apologize! I do not want to insult people.
>From gcc-bugs-return-661901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 08:04:26 2019
Return-Path: <gcc-bugs-return-661901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32419 invoked by alias); 30 Nov 2019 08:04:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32376 invoked by uid 48); 30 Nov 2019 08:04:22 -0000
From: "antoshkka at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90647] Warn on returning a lambda with captured local variables
Date: Sat, 30 Nov 2019 08:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antoshkka at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90647-4-sFRBHjagMx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90647-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90647-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03695.txt.bz2
Content-length: 160
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90647
--- Comment #2 from Antony Polukhin <antoshkka at gmail dot com> ---
-Wreturn-local-addr looks good to me
>From gcc-bugs-return-661902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 09:25:48 2019
Return-Path: <gcc-bugs-return-661902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62919 invoked by alias); 30 Nov 2019 09:25:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62744 invoked by uid 48); 30 Nov 2019 09:25:43 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92719] MacOS 10.15 Catalina build fails
Date: Sat, 30 Nov 2019 09:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92719-4-3L8AuKz1Cj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92719-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92719-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03696.txt.bz2
Content-length: 682
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92719
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #2 from Iain Sandoe <iains at gcc dot gnu.org> ---
With configuration options as suggested, bootstrap completes (and jit build).
However, there are a significant number of issues with jit testing (but that's
a separate issue).
Test results here:
https://gcc.gnu.org/ml/gcc-testresults/2019-11/msg01649.html
>From gcc-bugs-return-661903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 09:25:48 2019
Return-Path: <gcc-bugs-return-661903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62984 invoked by alias); 30 Nov 2019 09:25:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62810 invoked by uid 48); 30 Nov 2019 09:25:45 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90835] Incompatibilities with macOS 10.15 headers
Date: Sat, 30 Nov 2019 09:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-90835-4-IrCh7Waix7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03697.txt.bz2
Content-length: 463
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835
Bug 90835 depends on bug 92719, which changed state.
Bug 92719 Summary: MacOS 10.15 Catalina build fails
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92719
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
>From gcc-bugs-return-661904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 10:53:00 2019
Return-Path: <gcc-bugs-return-661904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7365 invoked by alias); 30 Nov 2019 10:53:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7269 invoked by uid 48); 30 Nov 2019 10:52:56 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90647] Warn on returning a lambda with captured local variables
Date: Sat, 30 Nov 2019 10:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on blocked everconfirmed
Message-ID: <bug-90647-4-mSDfzbEgHo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90647-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90647-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03698.txt.bz2
Content-length: 1186
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90647
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-30
Blocks|87403 |90556, 54367
Ever confirmed|0 |1
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Antony Polukhin from comment #2)
> -Wreturn-local-addr looks good to me
Hm, I suddenly got the idea that there was another bug under the
-Wreturn-local-addr meta-bug that this might be a dup of, but after checking,
it doesn't look like it after all... confirmed as a separate bug for now, I
guess.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54367
[Bug 54367] [meta-bug] lambda expressions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403
[Bug 87403] [Meta-bug] Issues that suggest a new warning
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90556
[Bug 90556] [meta-bug] bogus/missing -Wreturn-local-addr
>From gcc-bugs-return-661905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 10:54:56 2019
Return-Path: <gcc-bugs-return-661905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8993 invoked by alias); 30 Nov 2019 10:54:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8920 invoked by uid 48); 30 Nov 2019 10:54:52 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/70196] inconsistent constness of inequality of weak symbol addresses
Date: Sat, 30 Nov 2019 10:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: minor
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also
Message-ID: <bug-70196-4-ucqYlcoaIR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70196-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70196-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03699.txt.bz2
Content-length: 853
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70196
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=81453
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #5)
> (In reply to Nathan Sidwell from comment #4)
> > ordering comparison of pointers is only well-defined when the two pointers
> > point into the same object (including one-past-the-end). [expr.ref]/4
> >
>
> Right, there's a warning from -Wextra for that, there's a bug to split it
> off into its own warning, too...
...right, bug 81453
>From gcc-bugs-return-661906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 11:07:33 2019
Return-Path: <gcc-bugs-return-661906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19406 invoked by alias); 30 Nov 2019 11:07:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19318 invoked by uid 48); 30 Nov 2019 11:07:29 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92652] function call to lambda expression that return true does not satisfy the constraint in requires-clause if using return type deduction
Date: Sat, 30 Nov 2019 11:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc blocked
Message-ID: <bug-92652-4-Nqu00ysvE3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92652-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92652-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03700.txt.bz2
Content-length: 727
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92652
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
Blocks| |54367
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
is this a "concepts" thing? (I don't know C++ very well; I mostly just triage
bugs, and the "requires" and "constraint" terms remind me of some "concepts"
bugs...)
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54367
[Bug 54367] [meta-bug] lambda expressions
>From gcc-bugs-return-661907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 11:36:13 2019
Return-Path: <gcc-bugs-return-661907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107811 invoked by alias); 30 Nov 2019 11:36:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107754 invoked by uid 48); 30 Nov 2019 11:36:09 -0000
From: "lutztonineubert at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92695] P1064R0 - virtual constexpr fails if object taken from array
Date: Sat, 30 Nov 2019 11:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lutztonineubert at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92695-4-oaT59YOuKO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03701.txt.bz2
Content-length: 196
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92695
--- Comment #11 from Toni Neubert <lutztonineubert at gmail dot com> ---
I tested all patches and it works as expected.
Thank you very much!
>From gcc-bugs-return-661908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 12:06:38 2019
Return-Path: <gcc-bugs-return-661908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9372 invoked by alias); 30 Nov 2019 12:06:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9234 invoked by uid 48); 30 Nov 2019 12:06:33 -0000
From: "mjr19 at cam dot ac.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92698] Unnecessary copy in overlapping array assignment
Date: Sat, 30 Nov 2019 12:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mjr19 at cam dot ac.uk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92698-4-ASBbxJPM7U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03702.txt.bz2
Content-length: 1439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92698
--- Comment #2 from mjr19 at cam dot ac.uk ---
Thomas is quite correct that I had failed to mark the array as contiguous, at
which point the double copy is more reasonable (although memcpy will also
expect its arguments to be contiguous).
He also correctly points out that
a(n:n+len-1) = a(n+1:n+len)
will optimise to memmove if a is known to be contiguous.
However, I still think there is scope for further improvement.
a(n:n+len-1) = a(n+offset:n+offset+len-1)
never seems to optimise, whether or not a is contiguous, presumably because the
sign of offset is unknown. However, as memmove copes with either sign of offset
(or offset=0), concerns about the value of offset seem unnecessary.
Also, I suspect that arrays in Fortran are often contiguous, even when this is
not explicitly stated, so introducing a special case for contiguous arrays at
high optimisation levels may be beneficial. The explicit "contiguous" attribute
was introduced only in F2008 (and does not require packing and unpacking by the
caller if the caller's array is already contiguous). I expect a lot of code has
not progressed further than F2003.
The example I offered was not real code. The real code in which this arose was
a Fortran implementation of Timsort in which the assignment was just one part
of a subroutine, albeit a significant part in terms of execution time.
>From gcc-bugs-return-661909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 13:01:29 2019
Return-Path: <gcc-bugs-return-661909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94183 invoked by alias); 30 Nov 2019 13:01:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93740 invoked by uid 48); 30 Nov 2019 13:01:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92723] ICE in expand_shift_1, at expmed.c:2635
Date: Sat, 30 Nov 2019 13:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: ice-on-valid-code, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92723-4-syn7o2aq9q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03703.txt.bz2
Content-length: 4308
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92723
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-30
CC| |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reduced (-std=c++17 -O3):
template <typename> struct d;
template <typename e> struct d<e &> { typedef e g; };
template <typename e> struct ac {
typedef typename d<e>::g g;
};
template <typename e> using af = typename ac<e>::g;
template <bool, typename, typename ae> using ah = ae;
struct aj {
template <typename h, typename... ak> void al(h *, ak... an) { h(an...); }
};
template <typename> using ao = aj;
template <typename> class allocator : public ao<int> {};
template <typename> struct ap;
template <typename e> struct ap<allocator<e>> {
using aq = allocator<e>;
template <typename h, typename... ak>
static void al(aq ar, h am, ak... an) {
ar.al(am, an...);
}
};
struct as {
as(allocator<int>);
};
template <typename> struct at { allocator<int> av; };
template <typename e, typename aw> struct ax {
struct ay : as {
ay(aw ar) : as(ar) {}
};
template <typename... ak> ax(aw ar, ak... an) : az(ar) {
ap<aw>::al(ar, ba(), an...);
}
e *ba();
ay az;
};
struct bb {
template <typename e, typename aw, typename... ak>
bb(e *, at<aw> ar, ak... an) {
ax<e, aw>(ar.av, an...);
}
};
template <typename e> struct au {
using bc = e;
template <typename aw, typename... ak>
au(aw bd, ak... an) : be(ba, bd, an...) {}
bc *ba;
bb be;
};
template <typename e> struct bf : au<e> {
template <typename aw, typename... ak>
bf(aw bd, ak... an) : au<e>(bd, an...) {}
template <typename bg, typename aw, typename... ak>
friend bf<bg> bh(const aw &, ak &&...);
};
template <typename e, typename aw, typename... ak>
bf<e> bh(const aw &, ak &&... an) {
bf<e>(at<aw>{}, an...);
}
template <typename e, typename... ak> void bi(ak... an) {
bh<e>(allocator<int>(), an...);
}
template <typename> constexpr bool bj = false;
class j;
struct bk {
j *operator->();
};
struct bn : public bk {
bn(decltype(nullptr));
};
class br;
template <typename> using bp = br;
template <typename bq, typename bu> bq bs(bu);
template <typename bt> bt *bx();
using bv = struct bw {
template <typename cb> void by() {
int bz;
cb::ca(bz);
}
};
struct cf {
using cc = int;
};
struct cd {
char k;
void ce();
};
struct br : public cd {
int &operator[](long l) {
int *cj = reinterpret_cast<int *>(k);
return cj[l];
}
};
struct m {
using cc = int;
};
template <typename> constexpr bool n = false;
struct j {
using cg = int;
using q = bp<cg>;
q o();
} ch;
template <typename... r, typename ci> bool cn(ci f) {
((bs<r *>(ch) ? f(*bs<r *>(ch)) : false) || ...);
return false;
}
template <typename ck> struct p {
using cl = int;
static void co(bp<int> a, int b, bp<cl> c) {
a.ce();
for (long i; i; ++i)
c[i] = ck::apply(a[i], b);
}
};
template <template <typename, typename> class ck> struct cw {
template <typename ci> bool da(ci f) { cn<cf, m>(f); return false; }
template <typename ci> bool cy(ci f) {
da([&](auto cz) { return da([&](auto dg) { return f(cz, dg); }); });
return false;
}
static bv ca(int bz) { bi<cw>(bz); return bv(); }
cw(long) {
cy([](auto &db, auto &de) {
using cx = af<decltype(db)>;
using cr = af<decltype(de)>;
using dc = int;
using cv = typename cx::cc;
using cu = typename cr::cc;
using dd = ah<bj<cv>, cv, j>;
using dl = ah<n<dc>, int, p<ck<cv, cu>>>;
bn df = nullptr;
auto di = df->o();
if (auto dh = bx<dd>())
dl::co(dh->o(), 0, di);
return false;
});
}
};
template <typename, typename> struct s {
using cl = unsigned long;
template <typename dj = cl> static dj apply(int a, int b) {
return dj(a)>> b | dj(a) <<sizeof(dj) * 8 - b;
}
};
using t = cw<s>;
bw dn;
void dm() { dn.by<t>(); }
>From gcc-bugs-return-661910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 13:07:01 2019
Return-Path: <gcc-bugs-return-661910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110582 invoked by alias); 30 Nov 2019 13:07:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110303 invoked by uid 48); 30 Nov 2019 13:06:55 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65656] __builtin_constant_p should always be constexpr
Date: Sat, 30 Nov 2019 13:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.3
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65656-4-net6rbRuNm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65656-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65656-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03704.txt.bz2
Content-length: 645
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65656
--- Comment #10 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #9)
> See also bug 54021 for a similar problem report. That bug has been resolved
> and the test case submitted here also compiles and runs to completion with
> the same output as with Clang (at both -O0 and -O2).
>
> I can reproduce the problem described in comment #6 but it seems independent
> of the bug reported here. Are there any objections to resolving this bug as
> suggested in comment #3 and opening a new one for the other issue?
No such objections from me.
>From gcc-bugs-return-661911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 13:11:11 2019
Return-Path: <gcc-bugs-return-661911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125206 invoked by alias); 30 Nov 2019 13:11:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123961 invoked by uid 48); 30 Nov 2019 13:10:57 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92723] ICE in expand_shift_1, at expmed.c:2635
Date: Sat, 30 Nov 2019 13:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: ice-on-valid-code, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92723-4-nlupl3HxTj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03705.txt.bz2
Content-length: 4038
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92723
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Slightly adjusted, so that there are no warnings on it, with -O2 -std=c++17
-Wall -W when it compiles successfully, and with s/O2/O3/ when there is the
ICE:
template <typename> struct d;
template <typename e> struct d<e &> { typedef e g; };
template <typename e> struct ac {
typedef typename d<e>::g g;
};
template <typename e> using af = typename ac<e>::g;
template <bool, typename, typename ae> using ah = ae;
struct aj {
template <typename h, typename... ak> void al(h *, ak... an) { h(an...); }
};
template <typename> using ao = aj;
template <typename> class allocator : public ao<int> {};
template <typename> struct ap;
template <typename e> struct ap<allocator<e>> {
using aq = allocator<e>;
template <typename h, typename... ak>
static void al(aq ar, h am, ak... an) {
ar.al(am, an...);
}
};
struct as {
as(allocator<int>);
};
template <typename> struct at { allocator<int> av; };
template <typename e, typename aw> struct ax {
struct ay : as {
ay(aw ar) : as(ar) {}
};
template <typename... ak> ax(aw ar, ak... an) : az(ar) {
ap<aw>::al(ar, ba(), an...);
}
e *ba();
ay az;
};
struct bb {
template <typename e, typename aw, typename... ak>
bb(e *, at<aw> ar, ak... an) {
ax<e, aw>(ar.av, an...);
}
};
template <typename e> struct au {
using bc = e;
template <typename aw, typename... ak>
au(aw bd, ak... an) : be(ba, bd, an...) {}
bc *ba = nullptr;
bb be;
};
template <typename e> struct bf : au<e> {
template <typename aw, typename... ak>
bf(aw bd, ak... an) : au<e>(bd, an...) {}
template <typename bg, typename aw, typename... ak>
friend bf<bg> bh(const aw &, ak &&...);
};
template <typename e, typename aw, typename... ak>
bf<e> bh(const aw &, ak &&... an) {
bf<e>(at<aw>{}, an...);
for (;;);
}
template <typename e, typename... ak> void bi(ak... an) {
bh<e>(allocator<int>(), an...);
}
template <typename> constexpr bool bj = false;
class j;
struct bk {
j *operator->();
};
struct bn : public bk {
bn(decltype(nullptr));
};
class br;
template <typename> using bp = br;
template <typename bq, typename bu> bq bs(bu);
template <typename bt> bt *bx();
using bv = struct bw {
template <typename cb> void by() {
int bz = 0;
cb::ca(bz);
}
};
struct cf {
using cc = int;
};
struct cd {
char k;
void ce();
};
struct br : public cd {
int &operator[](long l) {
int *cj = reinterpret_cast<int *>(k);
return cj[l];
}
};
struct m {
using cc = int;
};
template <typename> constexpr bool n = false;
struct j {
using cg = int;
using q = bp<cg>;
q o();
} ch;
template <typename... r, typename ci> bool cn(ci f) {
((bs<r *>(ch) ? f(*bs<r *>(ch)) : false) || ...);
return false;
}
template <typename ck> struct p {
using cl = int;
static void co(bp<int> a, int b, bp<cl> c) {
a.ce();
for (long i = 0; i < 8; ++i)
c[i] = ck::apply(a[i], b);
}
};
template <template <typename, typename> class ck> struct cw {
template <typename ci> bool da(ci f) { cn<cf, m>(f); return false; }
template <typename ci> bool cy(ci f) {
da([&](auto cz) { return da([&](auto dg) { return f(cz, dg); }); });
return false;
}
static bv ca(int bz) { bi<cw>(bz); return bv(); }
cw(long) {
cy([](auto &db, auto &de) {
using cx = af<decltype(db)>;
using cr = af<decltype(de)>;
using cv = typename cx::cc;
using cu = typename cr::cc;
using dd = ah<bj<cv>, cv, j>;
using dl = ah<n<int>, int, p<ck<cv, cu>>>;
bn df = nullptr;
auto di = df->o();
if (auto dh = bx<dd>())
dl::co(dh->o(), 0, di);
return false;
});
}
};
template <typename, typename> struct s {
using cl = unsigned long;
template <typename dj = cl> static dj apply(int a, int b) {
return dj(a)>> b | dj(a) <<(sizeof(dj) * 8 - b);
}
};
using t = cw<s>;
bw dn;
void dm() { dn.by<t>(); }
>From gcc-bugs-return-661912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 13:58:18 2019
Return-Path: <gcc-bugs-return-661912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20901 invoked by alias); 30 Nov 2019 13:58:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20606 invoked by uid 48); 30 Nov 2019 13:58:13 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65656] __builtin_constant_p should always be constexpr
Date: Sat, 30 Nov 2019 13:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.3
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65656-4-drdQgp9uHI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65656-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65656-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03706.txt.bz2
Content-length: 179
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65656
--- Comment #11 from Marc Glisse <glisse at gcc dot gnu.org> ---
Comment #6 looks like it was probably fixed with bug 85746.
>From gcc-bugs-return-661913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 15:03:27 2019
Return-Path: <gcc-bugs-return-661913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6376 invoked by alias); 30 Nov 2019 15:03:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6340 invoked by uid 55); 30 Nov 2019 15:03:22 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91783] [10 Regression] ICE in gfc_dep_resolver, at fortran/dependency.c:2111
Date: Sat, 30 Nov 2019 15:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91783-4-a2AoPLlL2v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03707.txt.bz2
Content-length: 786
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91783
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Sat Nov 30 15:02:50 2019
New Revision: 278873
URL: https://gcc.gnu.org/viewcvs?rev=278873&root=gcc&view=rev
Log:
Do not look at _data component in gfc_dep_resolver.
2019-11-30 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/91783
* dependency.c (gfc_dep_resolver): Do not look at _data
component if present.
2019-11-30 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/91783
* gfortran.dg/dependency_56.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/dependency_56.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/dependency.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 15:09:52 2019
Return-Path: <gcc-bugs-return-661915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13593 invoked by alias); 30 Nov 2019 15:09:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13511 invoked by uid 48); 30 Nov 2019 15:09:48 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91783] [10 Regression] ICE in gfc_dep_resolver, at fortran/dependency.c:2111
Date: Sat, 30 Nov 2019 15:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91783-4-9XohuW97eC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03709.txt.bz2
Content-length: 558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91783
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed on trunk (and testcase also committed to gcc-9).
You never know what somebody may chose to backport :-)
Thanks for the bug report!
>From gcc-bugs-return-661914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 15:09:09 2019
Return-Path: <gcc-bugs-return-661914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12644 invoked by alias); 30 Nov 2019 15:09:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12611 invoked by uid 55); 30 Nov 2019 15:09:03 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91783] [10 Regression] ICE in gfc_dep_resolver, at fortran/dependency.c:2111
Date: Sat, 30 Nov 2019 15:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91783-4-myqcChs5kP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03708.txt.bz2
Content-length: 677
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91783
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Sat Nov 30 15:08:32 2019
New Revision: 278874
URL: https://gcc.gnu.org/viewcvs?rev=278874&root=gcc&view=rev
Log:
Backport from trunk as an insurance policy.
2019-11-30 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/91783
* gfortran.dg/dependency_56.f90: New test. Backport from trunk on
the off-chance that somebody backports something that will break
this test case.
Added:
branches/gcc-9-branch/gcc/testsuite/gfortran.dg/dependency_56.f90
Modified:
branches/gcc-9-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 16:28:29 2019
Return-Path: <gcc-bugs-return-661916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59336 invoked by alias); 30 Nov 2019 16:28:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59161 invoked by uid 48); 30 Nov 2019 16:28:25 -0000
From: "rlibby at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92718] [8/9/10 Regression] Bogus Wstringop-overflow in __builtin_memset() of an element of array of size 1 of struct
Date: Sat, 30 Nov 2019 16:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rlibby at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92718-4-MFQhtZ7WqJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92718-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92718-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03710.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92718
--- Comment #3 from Ryan Libby <rlibby at gmail dot com> ---
(In reply to Martin Sebor from comment #2)
> Replacing the memset call with the assignment '*p = (struct s){ 0 };' avoids
> the warning and also results in better/optimal code. (As suggested in
> pr36602, that would be a useful optimization independent of the warning.)
In the real code that prompted the warning, the struct has some members
which are declared const, which I believe prevents using aggregate
initialization as a workaround (or at least, it produces an error).
>From gcc-bugs-return-661917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 16:31:19 2019
Return-Path: <gcc-bugs-return-661917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91343 invoked by alias); 30 Nov 2019 16:31:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91311 invoked by uid 48); 30 Nov 2019 16:31:15 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92737] New: cgraph_node and varpool_node needs explicit constructor
Date: Sat, 30 Nov 2019 16:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03711.txt.bz2
Content-length: 625
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92737
Bug ID: 92737
Summary: cgraph_node and varpool_node needs explicit
constructor
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
CC: marxin at gcc dot gnu.org
Target Milestone: ---
cgraph_node and varpool_node are non-pods, but still allocated via
alloc_cleared and we rely on various flags to be set to 0.
>From gcc-bugs-return-661918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 16:36:00 2019
Return-Path: <gcc-bugs-return-661918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96275 invoked by alias); 30 Nov 2019 16:36:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96233 invoked by uid 48); 30 Nov 2019 16:35:56 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92736] Error when using a variable from a module in a submodule and its parent module.
Date: Sat, 30 Nov 2019 16:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92736-4-Pt4ftyLR6C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03712.txt.bz2
Content-length: 666
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92736
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #1 from kargl at gcc dot gnu.org ---
Not sure the code is conforming, and don't have time to
investigate (unless someone is willing to cough up $$).
Workaround 1. Remove "use m1, only : i" in submodule(m2)
as 'i' is already available from module m2.
Workaround 2. Use Fortran's renaming scheme. Thus, change
the submodule(m2) to 'Use m1, only : j=>i'
>From gcc-bugs-return-661919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 18:25:49 2019
Return-Path: <gcc-bugs-return-661919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85897 invoked by alias); 30 Nov 2019 18:25:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85607 invoked by uid 48); 30 Nov 2019 18:25:43 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64329] Crash when returning reference from lambda with deduced type
Date: Sat, 30 Nov 2019 18:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: blocked
Message-ID: <bug-64329-4-dqNXbFfM4J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64329-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64329-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03713.txt.bz2
Content-length: 1202
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64329
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |54367
--- Comment #7 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #5)
> (In reply to Jonathan Wakely from comment #2)
> > (In reply to Michael Stahl from comment #1)
> > > i believe i've hit the same problem
> >
> > I don't think so. The original bug report is for 4.9.3, and seems to be an
> > actual compiler bug that is fixed already in GCC 5 and later.
> >
> > Your case is invalid code. While I agree a warning would be nice, it's not
> > the same as a bug in 4.9.3 that has been fixed.
>
> I've created PR 70692 for the missing warning on the invalid code, since
> it's a different problem to the one in this PR.
ah right, I think this just reminded me of a bug whose number I was trying to
remember for a different bug...
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54367
[Bug 54367] [meta-bug] lambda expressions
>From gcc-bugs-return-661920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 18:28:27 2019
Return-Path: <gcc-bugs-return-661920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87725 invoked by alias); 30 Nov 2019 18:28:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87652 invoked by uid 48); 30 Nov 2019 18:28:24 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90647] Warn on returning a lambda with captured local variables
Date: Sat, 30 Nov 2019 18:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also
Message-ID: <bug-90647-4-qNGq2T4r3k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90647-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90647-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03714.txt.bz2
Content-length: 1000
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90647
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=70692
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #3)
> (In reply to Antony Polukhin from comment #2)
> > -Wreturn-local-addr looks good to me
>
> Hm, I suddenly got the idea that there was another bug under the
> -Wreturn-local-addr meta-bug that this might be a dup of, but after
> checking, it doesn't look like it after all... confirmed as a separate bug
> for now, I guess.
I guess it might have been bug 70692 that I was thinking of? But that's a
different -Wreturn-local-addr issue; it's only related enough for the "See
Also" field...
>From gcc-bugs-return-661921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 19:12:26 2019
Return-Path: <gcc-bugs-return-661921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2052 invoked by alias); 30 Nov 2019 19:12:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2026 invoked by uid 48); 30 Nov 2019 19:12:22 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] New: [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Sat, 30 Nov 2019 19:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03715.txt.bz2
Content-length: 498
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
Bug ID: 92738
Summary: [10 regression] Large code size growth for -O2
binaries between 2019-05-19...2019-05-29
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
Target Milestone: ---
>From gcc-bugs-return-661922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 19:13:24 2019
Return-Path: <gcc-bugs-return-661922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3225 invoked by alias); 30 Nov 2019 19:13:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3185 invoked by uid 48); 30 Nov 2019 19:13:20 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Sat, 30 Nov 2019 19:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92738-4-nt8iwwHQOX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03716.txt.bz2
Content-length: 228
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
This is seen on
https://lnt.opensuse.org/db_default/v4/SPEC/graph?highlight_run=7361&plot.574=31.574.4
>From gcc-bugs-return-661923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 19:20:51 2019
Return-Path: <gcc-bugs-return-661923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8504 invoked by alias); 30 Nov 2019 19:20:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8448 invoked by uid 48); 30 Nov 2019 19:20:46 -0000
From: "lutztonineubert at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92695] P1064R0 - virtual constexpr fails if object taken from array
Date: Sat, 30 Nov 2019 19:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lutztonineubert at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92695-4-LJAL1ZRpvt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03717.txt.bz2
Content-length: 392
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92695
--- Comment #12 from Toni Neubert <lutztonineubert at gmail dot com> ---
Hello, I got another error using virtual classes:
```
struct A {
virtual constexpr ~A() = default;
};
struct B : A {};
constexpr bool test() {
B b;
return true;
}
static_assert(test());
```
-> virtual constexpr B::~B()' used before its definition
>From gcc-bugs-return-661924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 19:45:42 2019
Return-Path: <gcc-bugs-return-661924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34093 invoked by alias); 30 Nov 2019 19:45:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34071 invoked by uid 48); 30 Nov 2019 19:45:25 -0000
From: "dclarke at blastwave dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92720] cc1 accepts #include /dev/stdin inline
Date: Sat, 30 Nov 2019 19:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dclarke at blastwave dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92720-4-xxWjEiv1Ha@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03718.txt.bz2
Content-length: 399
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720
--- Comment #5 from Dennis Clarke <dclarke at blastwave dot org> ---
Glad someone looked at this. I was going to try again with LLVM/Clang
and then a few other places on a few other architectures. Why bother?
However if this is "implementation defined" then we should see a
paragraph somewhere in a standards doc regarding this. Somewhere.
>From gcc-bugs-return-661925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 20:27:09 2019
Return-Path: <gcc-bugs-return-661925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121031 invoked by alias); 30 Nov 2019 20:27:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121009 invoked by uid 55); 30 Nov 2019 20:27:05 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92720] cc1 accepts #include /dev/stdin inline
Date: Sat, 30 Nov 2019 20:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92720-4-uDjqjtBVnV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03719.txt.bz2
Content-length: 1046
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720
--- Comment #6 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
For the documentation of implementation-defined preprocessor behavior (as
required to be documented by a C implementation for anything the C
standard says is implementation-defined; in this case, where C11 6.10.2#2
and #3 refer to "How the places are specified or the header identified is
implementation-defined." and "searched for in an implementation-defined
manner"), see cpp.texi. It says:
@item Source file inclusion.
For a discussion on how the preprocessor locates header files,
@ref{Include Operation}.
In turn, that section "Include Operation" has more details. It doesn't
mention includes with an absolute path, but I think that's because the
general concept of resolving a path relative to a directory, and how that
handles absolute paths, is one for the underlying operating system, not
for any particular application running on that operating system.
>From gcc-bugs-return-661926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 20:51:14 2019
Return-Path: <gcc-bugs-return-661926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39331 invoked by alias); 30 Nov 2019 20:51:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39145 invoked by uid 48); 30 Nov 2019 20:51:09 -0000
From: "dclarke at blastwave dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92720] cc1 accepts #include /dev/stdin inline
Date: Sat, 30 Nov 2019 20:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dclarke at blastwave dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92720-4-CGT1a5bQqZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03720.txt.bz2
Content-length: 1902
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720
--- Comment #7 from Dennis Clarke <dclarke at blastwave dot org> ---
Looking at the document n1256 "ISO/IEC 9899:TC3 WG14/N125" ye C99
specifications we see section 6.10.2 Source file inclusion subsection 1
which almost seems clear :
A #include directive shall identify a header or source file
that can be processed by the implementation.
Sort of a vague idea there. Whatever "can be" means. However the file
/dev/stdin really is neither a "header" nor is it a "source" file.
As people are saying, this is all "implementation" defined perhaps. I
feel that no file shall be included if it is neither a "source" file
nor a valid "header". No idea how one would verify such a condition at
the pre-processing translation stage.
However I also see :
5.1.1.2 Translation phases
The precedence among the syntax rules of translation is
specified by the following phases.[5]
1. Physical source file multibyte characters are mapped, in
an implementation-defined manner, to the source character
set (introducing new-line characters forend-of-line
indicators) if necessary. Trigraph sequences are replaced
by corresponding single-character internal representations.
Where the footnote [5] states :
5 Implementations shall behave as if these separate phases
occur, even though many are typically folded together in
practice. Source files, translation units, and translated
translation units need not necessarily be stored as files,
nor need there be any one-to-one correspondence between these
entities and any external representation. The description
is conceptual only, and does not specify any particular
implementation.
That seems to imply I could just as easily do an include of /dev/random.
Dennis
>From gcc-bugs-return-661927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 21:17:30 2019
Return-Path: <gcc-bugs-return-661927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96668 invoked by alias); 30 Nov 2019 21:17:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96635 invoked by uid 48); 30 Nov 2019 21:17:26 -0000
From: "dclarke at blastwave dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92720] cc1 accepts #include /dev/stdin inline
Date: Sat, 30 Nov 2019 21:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dclarke at blastwave dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92720-4-nx648HIUke@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03721.txt.bz2
Content-length: 1661
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720
--- Comment #8 from Dennis Clarke <dclarke at blastwave dot org> ---
(In reply to joseph@codesourcery.com from comment #6)
.
.
.
> In turn, that section "Include Operation" has more details. It doesn't
> mention includes with an absolute path, but I think that's because the
> general concept of resolving a path relative to a directory, and how that
> handles absolute paths, is one for the underlying operating system, not
> for any particular application running on that operating system.
I hope someone agrees that this seems like black magic :
esther$
esther$ uname -a
Linux esther 5.3.0-2-686 #1 SMP Debian 5.3.9-3 (2019-11-19) i686 GNU/Linux
esther$ cat /proc/version
Linux version 5.3.0-2-686 (debian-kernel@lists.debian.org) (gcc version 9.2.1
20191109 (Debian 9.2.1-19)) #1 SMP Debian 5.3.9-3 (2019-11-19)
esther$ gcc --version
gcc (Debian 9.2.1-19) 9.2.1 20191109
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
esther$ ( /usr/bin/printf "\042"; dd if=/dev/urandom bs=16 count=1 2>/dev/null
| od -Ax -t x1 -v | tr -d '\012' | cut -c8-54 | tr -d '\012';/usr/bin/printf
"\042\n" ) | gcc -std=iso9899:1999 -pedantic -pedantic-errors -Wpedantic
-fno-builtin -O0 -D_XOPEN_SOURCE=600 -o /tmp/wtf /tmp/wtf.c
esther$ /tmp/wtf
1e e8 6e 82 6a a4 0b 66 0f d5 48 33 2a 86 21 6b
esther$
Which makes one wonder what would happen if I were to merely include
/dev/urandom directly.
Dennis
>From gcc-bugs-return-661928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 21:41:30 2019
Return-Path: <gcc-bugs-return-661928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2243 invoked by alias); 30 Nov 2019 21:41:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2191 invoked by uid 48); 30 Nov 2019 21:41:26 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Sat, 30 Nov 2019 21:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92738-4-RuX9CojT6b@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03722.txt.bz2
Content-length: 1181
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
--- Comment #2 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=10.542.4&highlight_run=7354
shows shorter range
+2019-05-24 Jakub Jelinek <jakub@redhat.com>
+
+ * tree-core.h (enum omp_clause_code): Add OMP_CLAUSE__CONDTEMP_.
+ * tree.h (OMP_CLAUSE_DECL): Use OMP_CLAUSE__CONDTEMP_ instead of
+ OMP_CLAUSE__REDUCTEMP_.
+ * tree.c (omp_clause_num_ops, omp_clause_code_name): Add
+ OMP_CLAUSE__CONDTEMP_.
....
+2019-05-19 Segher Boessenkool <segher@kernel.crashing.org>
+
+ * config/rs6000/constraints.md (define_register_constraint "wo"):
+ Delete.
+ * config/rs6000/rs6000.h (enum r6000_reg_class_enum): Delete
+ RS6000_CONSTRAINT_wo.
+ * config/rs6000/rs6000.c (rs6000_debug_reg_global): Adjust.
+ (rs6000_init_hard_regno_mode_ok): Adjust.
+ * config/rs6000/rs6000.md: Replace "wo" constraint by "wa" with "p9v".
+ * config/rs6000/altivec.md: Ditto.
+ * doc/md.texi (Machine Constraints): Adjust.
+
2019-05-18 Iain Sandoe <iain@sandoe.co.uk>
It may be easy to bisect.
>From gcc-bugs-return-661929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 30 23:44:36 2019
Return-Path: <gcc-bugs-return-661929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32235 invoked by alias); 30 Nov 2019 23:44:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32189 invoked by uid 48); 30 Nov 2019 23:44:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92720] cc1 accepts #include /dev/stdin inline
Date: Sat, 30 Nov 2019 23:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92720-4-DJLjGzEkd8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03723.txt.bz2
Content-length: 1125
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92720
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Dennis Clarke from comment #7)
> Sort of a vague idea there. Whatever "can be" means. However the file
> /dev/stdin really is neither a "header" nor is it a "source" file.
It could be. `echo "extern int i;"` would provide a valid source file to
standard input. "source file" does not mean "regular file on a physical disk".
> As people are saying, this is all "implementation" defined perhaps. I
> feel that no file shall be included if it is neither a "source" file
> nor a valid "header". No idea how one would verify such a condition at
> the pre-processing translation stage.
The compiler can't verify that. What's the difference between a header with a
syntax error (which we obviously want the compiler to *attempt* to compile, and
give a diagnostic) and a random file that isn't a header?
> That seems to imply I could just as easily do an include of /dev/random.
You can. Just don't expect it to compile.
This seems like a case of "play stupid games, win stupid prizes".
>From gcc-bugs-return-661930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 00:27:39 2019
Return-Path: <gcc-bugs-return-661930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121486 invoked by alias); 1 Dec 2019 00:27:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121327 invoked by uid 48); 1 Dec 2019 00:27:12 -0000
From: "cjdb.ns at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92739] New: [Trunk Regression] Requires clause followed by an attribute no longer compiles
Date: Sun, 01 Dec 2019 00:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cjdb.ns at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00000.txt.bz2
Content-length: 1714
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92739
Bug ID: 92739
Summary: [Trunk Regression] Requires clause followed by an
attribute no longer compiles
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: cjdb.ns at gmail dot com
Target Milestone: ---
Created attachment 47401
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47401&action=edit
Preprocessed file for broken build
The following code works in 466691493b9, but not in commits starting from Git
hash 6b42dfe4264.
```
template<typename T>
requires true
[[deprecated]] void f()
{}
```
# Diagnostic
test.cpp:2:1: error: expression must be enclosed in parentheses
2 | requires true
| ^~~~~~~~
test.cpp:2:10: error: expected unqualified-id before 'true'
2 | requires true
| ^~~~
# Built using
/usr/local/bin/g++-10 -std=c++2a test.cpp
# System type
* Ubuntu 18.04 via WSL
* Ubuntu 18.04 via a Docker image
# GCC configured with
```
export CC=/usr/local/bin/gcc-10 \
CXX=/usr/local/bin/g++-10 \
CFLAGS='-O3 -DNDEBUG -g0' \
CXXFLAGS='-O3 -DNDEBUG -g0' \
CPPFLAGS="$CXXFLAGS"
../gcc/configure --disable-multilib \
--disable-nls \
--disable-bootstrap \
--enable-languages=c,c++ \
--disable-werror \
--with-diagnostics-color=always \
--with-ld=/usr/bin/gold
```
>From gcc-bugs-return-661931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 00:28:46 2019
Return-Path: <gcc-bugs-return-661931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122625 invoked by alias); 1 Dec 2019 00:28:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122555 invoked by uid 48); 1 Dec 2019 00:28:42 -0000
From: "cjdb.ns at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92739] [Trunk Regression] Requires clause followed by an attribute no longer compiles
Date: Sun, 01 Dec 2019 00:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cjdb.ns at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92739-4-c5ktrFybNK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00001.txt.bz2
Content-length: 262
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92739
--- Comment #1 from Christopher Di Bella <cjdb.ns at gmail dot com> ---
Created attachment 47402
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47402&action=edit
Preprocessed file for working build
>From gcc-bugs-return-661932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 00:46:15 2019
Return-Path: <gcc-bugs-return-661932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4322 invoked by alias); 1 Dec 2019 00:46:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4266 invoked by uid 48); 1 Dec 2019 00:46:09 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92698] Unnecessary copy in overlapping array assignment
Date: Sun, 01 Dec 2019 00:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed bug_severity
Message-ID: <bug-92698-4-V4Hj7hQk99@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00002.txt.bz2
Content-length: 2095
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92698
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-01
Ever confirmed|0 |1
Severity|normal |enhancement
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
So, here's a C test case, also functionally equivalent to
a memmove.
#include <stdlib.h>
void foo (double *a, int n, int len, int offset)
{
int i;
double *p;
p = malloc(sizeof(*p) * len);
for (i=0; i<len; i++)
p[i] = a[n+i];
for (i=0; i<len; i++)
a[n+offset+i] = p[i];
free(p);
}
So, this is something the middle end could possibly catch, it doesn't
do so at the moment.
Regarding loop versioning wrt unity / non-unity strides: We've had that
discussion for a more general case, I cannot find the PR at the moment,
it may have been closed as WONTFIX. One problem that we saw was that
the time overhead and growth of code size could be too high, especially
with short arrays.
With the CONTIGOUS attribute and the IS_CONTIGUOUS function, the user
now can control what needs to happen. Older code, by the way, usually
has
real a(n)
style arguments, and these are always contiguous (and may need to
be converted on entry / exit).
So, what's left? We could indeed translate
a(n:n+len-1) = a(n+offset:n+offset+len-1)
into pseudo-code
if (is_contiguous(a)) then
i = n + offset + len - 1 - (n + offset) + 1
if (bounds_checking) then
if (n + len - 1 /=i) stop "out of bounds error"
end if
if (i>0) then
call memcpy (c_loc(a(n)), c_loc(a(n+offset), i*c_sizeof(a(1))
end if
else
a(n:n+len-1) = a(n+offset:n+offset+len-1)
(this is pseudo-code because we cannot use the real c_loc because
a is usually not a target).
So, confirmed as an enhancement request.
>From gcc-bugs-return-661933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 00:48:41 2019
Return-Path: <gcc-bugs-return-661933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6369 invoked by alias); 1 Dec 2019 00:48:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6268 invoked by uid 48); 1 Dec 2019 00:48:31 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91512] [10 Regression] Fortran compile time regression.
Date: Sun, 01 Dec 2019 00:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91512-4-qunh03J1dl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91512-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91512-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00003.txt.bz2
Content-length: 452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91512
--- Comment #21 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Sunil Pandey from comment #20)
> Created attachment 46851 [details]
> Compile time regression reproducer.
>
> attached reproducer show ~28X compile time regression after the commit. See
> the command line in readme.txt file.
I'm afraid the test case is no use without the source that the
*.mod files were from.
>From gcc-bugs-return-661934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 01:06:19 2019
Return-Path: <gcc-bugs-return-661934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72230 invoked by alias); 1 Dec 2019 01:06:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72191 invoked by uid 48); 1 Dec 2019 01:06:15 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92740] New: induct2 (from polyhedron) regresses 267% with -O2 -ftree-vectorize -ftree-slp-vectorize -fvect-cost-modes=dynamic compared to -O2
Date: Sun, 01 Dec 2019 01:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00004.txt.bz2
Content-length: 589
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92740
Bug ID: 92740
Summary: induct2 (from polyhedron) regresses 267% with -O2
-ftree-vectorize -ftree-slp-vectorize
-fvect-cost-modes=dynamic compared to -O2
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
Target Milestone: ---
This is on zen2 hardware.
>From gcc-bugs-return-661935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 01:08:53 2019
Return-Path: <gcc-bugs-return-661935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74416 invoked by alias); 1 Dec 2019 01:08:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74377 invoked by uid 48); 1 Dec 2019 01:08:48 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92740] induct2 (from polyhedron) regresses 267% with -O2 -ftree-vectorize -ftree-slp-vectorize -fvect-cost-modes=dynamic compared to -O2
Date: Sun, 01 Dec 2019 01:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92740-4-H6YMkjUBXK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00005.txt.bz2
Content-length: 244
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92740
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
There is also 75% regression on fft2 and 5% on rnflow2.
Induct2 reproduces on kaby lake, fft2 and rnflow seems zen specific.
>From gcc-bugs-return-661936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 04:56:21 2019
Return-Path: <gcc-bugs-return-661936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124524 invoked by alias); 1 Dec 2019 04:56:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124170 invoked by uid 48); 1 Dec 2019 04:56:15 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92741] New: [10 Regression] ICE: verify_gimple failed (error: invalid vector types in nop conversion)
Date: Sun, 01 Dec 2019 04:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00006.txt.bz2
Content-length: 2122
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92741
Bug ID: 92741
Summary: [10 Regression] ICE: verify_gimple failed (error:
invalid vector types in nop conversion)
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
Target: x86_64-unknown-linux-gnu
gcc-10.0.0-alpha20191124 snapshot (r278660) ICEs when compiling the following
testcase reduced from testsuite/gcc.target/i386/sse2-mmx-pinsrw.c w/ -O2
-fexceptions -fnon-call-exceptions -fno-inline:
typedef int vh __attribute__ ((__vector_size__ (2 * sizeof (int))));
typedef short int cq __attribute__ ((__vector_size__ (4 * sizeof (short
int))));
static void
id (int *r8, vh *tu)
{
*(vh *) r8 = *tu;
}
void
mr (void)
{
int r8;
cq he = { 0, };
id (&r8, (vh *) &he);
}
% x86_64-unknown-linux-gnu-gcc-10.0.0-alpha20191124 -O2 -fexceptions
-fnon-call-exceptions -fno-inline -c pi4vkh1k.c
pi4vkh1k.c: In function 'id.constprop':
pi4vkh1k.c:5:1: error: invalid vector types in nop conversion
5 | id (int *r8, vh *tu)
| ^~
vector(2) int
cq
_2 = (vector(2) int) { 0, 0, 0, 0 };
during GIMPLE pass: fixup_cfg
pi4vkh1k.c:5:1: internal compiler error: verify_gimple failed
0xd57c08 verify_gimple_in_cfg(function*, bool)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/tree-cfg.c:5445
0xc3af99 execute_function_todo
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/passes.c:1983
0xc3bcb7 do_per_function
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/passes.c:1638
0xc3bcb7 execute_todo
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/passes.c:2037
W/ -fopenacc the check fails during IPA pass pta instead.
>From gcc-bugs-return-661937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 05:13:13 2019
Return-Path: <gcc-bugs-return-661937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49776 invoked by alias); 1 Dec 2019 05:13:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49188 invoked by uid 48); 1 Dec 2019 05:13:09 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/66955] Bootstrap error: libcc1 compiled as shared library despite --disable-shared
Date: Sun, 01 Dec 2019 05:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66955-4-sugn3d8lRT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66955-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66955-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00007.txt.bz2
Content-length: 393
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66955
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Rainer Orth from comment #4)
> Confirmed on all of Linux/x86_64 and Solaris/x86. Recategorizing: libcc1 has
> nothing to do with libgcc. There's no category for it and the MAINTAINERS
> file lists none.
Hm, maybe a category for it should be created...
>From gcc-bugs-return-661938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 05:14:00 2019
Return-Path: <gcc-bugs-return-661938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58173 invoked by alias); 1 Dec 2019 05:13:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56600 invoked by uid 48); 1 Dec 2019 05:13:53 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92742] New: [10 Regression] ICE in info_for_reduction, at tree-vect-loop.c:4367
Date: Sun, 01 Dec 2019 05:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92742-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00008.txt.bz2
Content-length: 2799
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92742
Bug ID: 92742
Summary: [10 Regression] ICE in info_for_reduction, at
tree-vect-loop.c:4367
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
gcc-10.0.0-alpha20191124 snapshot (r278660) ICEs when compiling the following
testcase w/ -O3:
unsigned int qw;
int
rs (int iq, int wg)
{
for (qw = 0; qw < 2; ++qw)
{
}
while (iq < 1)
{
wg *= qw * 2;
++iq;
}
return wg;
}
% gcc-10.0.0-alpha20191124 -O3 -c bcr4em7v.c
during GIMPLE pass: vect
bcr4em7v.c: In function 'rs':
bcr4em7v.c:4:1: internal compiler error: in info_for_reduction, at
tree-vect-loop.c:4367
4 | rs (int iq, int wg)
| ^~
0x6d760c info_for_reduction(_stmt_vec_info*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/tree-vect-loop.c:4367
0xf5e0b4 vectorizable_reduction(_stmt_vec_info*, _slp_tree*, _slp_instance*,
vec<stmt_info_for_cost, va_heap, vl_ptr>*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/tree-vect-loop.c:5967
0xf4ed0a vect_analyze_stmt(_stmt_vec_info*, bool*, _slp_tree*, _slp_instance*,
vec<stmt_info_for_cost, va_heap, vl_ptr>*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/tree-vect-stmts.c:10849
0xf7ae0c vect_slp_analyze_node_operations_1
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/tree-vect-slp.c:2792
0xf7ae0c vect_slp_analyze_node_operations
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/tree-vect-slp.c:2898
0xf7e7b1 vect_slp_analyze_operations(vec_info*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/tree-vect-slp.c:2932
0xf66527 vect_analyze_loop_2
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/tree-vect-loop.c:2125
0xf66527 vect_analyze_loop(loop*, vec_info_shared*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/tree-vect-loop.c:2554
0xf84b90 try_vectorize_loop_1
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/tree-vectorizer.c:892
0xf8560e vectorize_loops()
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191124/work/gcc-10-20191124/gcc/tree-vectorizer.c:1125
>From gcc-bugs-return-661939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 05:41:26 2019
Return-Path: <gcc-bugs-return-661939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123464 invoked by alias); 1 Dec 2019 05:41:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123423 invoked by uid 48); 1 Dec 2019 05:41:21 -0000
From: "chinoune.mehdi at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92736] Error when using a variable from a module in a submodule and its parent module.
Date: Sun, 01 Dec 2019 05:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: chinoune.mehdi at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92736-4-DopKN4a8Lm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00009.txt.bz2
Content-length: 1610
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92736
--- Comment #2 from Chinoune <chinoune.mehdi at hotmail dot com> ---
(In reply to kargl from comment #1)
> Not sure the code is conforming, and don't have time to
> investigate (unless someone is willing to cough up $$).
>
> Workaround 1. Remove "use m1, only : i" in submodule(m2)
> as 'i' is already available from module m2.
>
> Workaround 2. Use Fortran's renaming scheme. Thus, change
> the submodule(m2) to 'Use m1, only : j=>i'
You introduced a regression and it is your duty to fix it.
At least fix the ambiguous error message which doesn't tell anything about the
problem.
15 | submodule(m2) s1
| 1
16 | use m1, only : i
| 2
Error:
Symbol ‘i’ at (1) conflicts with the symbol at (2)
does 'i' conflict with 'm2'?!
>From gcc-bugs-return-661940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 06:20:26 2019
Return-Path: <gcc-bugs-return-661940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15132 invoked by alias); 1 Dec 2019 06:20:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15089 invoked by uid 55); 1 Dec 2019 06:20:20 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92736] Error when using a variable from a module in a submodule and its parent module.
Date: Sun, 01 Dec 2019 06:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92736-4-WJdbMCQRkM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00010.txt.bz2
Content-length: 999
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92736
--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sun, Dec 01, 2019 at 05:41:21AM +0000, chinoune.mehdi at hotmail dot com
wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92736
>
> --- Comment #2 from Chinoune <chinoune.mehdi at hotmail dot com> ---
> (In reply to kargl from comment #1)
> > Not sure the code is conforming, and don't have time to
> > investigate (unless someone is willing to cough up $$).
> >
> > Workaround 1. Remove "use m1, only : i" in submodule(m2)
> > as 'i' is already available from module m2.
> >
> > Workaround 2. Use Fortran's renaming scheme. Thus, change
> > the submodule(m2) to 'Use m1, only : j=>i'
>
> You introduced a regression and it is your duty to fix it.
When it comes to gfortran, I have no duty to you or anyone else.
I have neither the time nor now the inclination to look at this
bug (unless someone coughs up $$$$ (price just went up ;)).
>From gcc-bugs-return-661941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 12:10:12 2019
Return-Path: <gcc-bugs-return-661941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6599 invoked by alias); 1 Dec 2019 12:10:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6530 invoked by uid 48); 1 Dec 2019 12:10:08 -0000
From: "chinoune.mehdi at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92736] Error when using a variable from a module in a submodule and its parent module.
Date: Sun, 01 Dec 2019 12:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: chinoune.mehdi at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92736-4-LLlv0GxNS2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00011.txt.bz2
Content-length: 1341
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92736
--- Comment #4 from Chinoune <chinoune.mehdi at hotmail dot com> ---
(In reply to Steve Kargl from comment #3)
> On Sun, Dec 01, 2019 at 05:41:21AM +0000, chinoune.mehdi at hotmail dot com
> wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92736
> >
> > --- Comment #2 from Chinoune <chinoune.mehdi at hotmail dot com> ---
> > (In reply to kargl from comment #1)
> > > Not sure the code is conforming, and don't have time to
> > > investigate (unless someone is willing to cough up $$).
> > >
> > > Workaround 1. Remove "use m1, only : i" in submodule(m2)
> > > as 'i' is already available from module m2.
> > >
> > > Workaround 2. Use Fortran's renaming scheme. Thus, change
> > > the submodule(m2) to 'Use m1, only : j=>i'
> >
> > You introduced a regression and it is your duty to fix it.
>
> When it comes to gfortran, I have no duty to you or anyone else.
> I have neither the time nor now the inclination to look at this
> bug (unless someone coughs up $$$$ (price just went up ;)).
With $$$ I can get a the best Fortran Compiler from Intel. Why should I pay you
$$$$ for just one little bug?!
And I didn't complain about the bug, I did just report it. If you don't like
people reporting bugs in open-source programs then you should better leave.
>From gcc-bugs-return-661942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 15:01:23 2019
Return-Path: <gcc-bugs-return-661942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99223 invoked by alias); 1 Dec 2019 15:01:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99188 invoked by uid 48); 1 Dec 2019 15:01:19 -0000
From: "akim.demaille at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92743] New: doc: -Wattribute-alias improperly indexed
Date: Sun, 01 Dec 2019 15:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: akim.demaille at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92743-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00012.txt.bz2
Content-length: 610
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92743
Bug ID: 92743
Summary: doc: -Wattribute-alias improperly indexed
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: akim.demaille at gmail dot com
Target Milestone: ---
The documentation indexes the option with the leading `-`, contrary to the rest
of the documentation.
See
https://gcc.gnu.org/onlinedocs/gcc-9.2.0/gcc/Option-Index.html#Option-Index.
>From gcc-bugs-return-661943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 17:56:56 2019
Return-Path: <gcc-bugs-return-661943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96563 invoked by alias); 1 Dec 2019 17:56:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96544 invoked by uid 48); 1 Dec 2019 17:56:52 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92743] doc: -Wattribute-alias improperly indexed
Date: Sun, 01 Dec 2019 17:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-92743-4-pT7rXhBzmS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92743-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92743-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00013.txt.bz2
Content-length: 656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92743
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-01
CC| |marxin at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Let me fix it.
>From gcc-bugs-return-661944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 18:00:21 2019
Return-Path: <gcc-bugs-return-661944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98377 invoked by alias); 1 Dec 2019 18:00:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98196 invoked by uid 48); 1 Dec 2019 18:00:00 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92742] [10 Regression] ICE in info_for_reduction, at tree-vect-loop.c:4367
Date: Sun, 01 Dec 2019 18:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work assigned_to target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92742-4-YPJQJW39dx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92742-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92742-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00014.txt.bz2
Content-length: 838
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92742
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-01
CC| |marxin at gcc dot gnu.org
Known to work| |9.2.0
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r277882.
>From gcc-bugs-return-661945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 18:01:34 2019
Return-Path: <gcc-bugs-return-661945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99844 invoked by alias); 1 Dec 2019 18:01:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99784 invoked by uid 48); 1 Dec 2019 18:01:26 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92744] New: [10 Regression] error: insn does not satisfy its constraints since r278439
Date: Sun, 01 Dec 2019 18:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone cf_gcchost
Message-ID: <bug-92744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00015.txt.bz2
Content-length: 2136
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92744
Bug ID: 92744
Summary: [10 Regression] error: insn does not satisfy its
constraints since r278439
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-pc-linux-gnu
I see following ICE:
$ cat return.ii
class A {
public:
typedef float __dec32 __attribute__((mode(SD)));
__dec32 __val;
};
bool operator!=(A p1, A p2) { return p1.__val != p2.__val; }
void fn1();
void fn2(A p1, A p2) {
if (p1 != p2)
fn1();
}
$ g++ return.ii -fno-tree-ccp -Os -c
return.ii: In function ‘void fn2(A, A)’:
return.ii:11:1: error: insn does not satisfy its constraints:
11 | }
| ^
(insn 43 4 9 2 (parallel [
(set (reg:SI 21 xmm1 [ p2 ])
(reg:SI 20 xmm0 [orig:84 p1 ] [84]))
(set (reg:SI 20 xmm0 [orig:84 p1 ] [84])
(reg:SI 21 xmm1 [ p2 ]))
]) "return.ii":9:3 78 {*swapsi}
(nil))
during RTL pass: cprop_hardreg
return.ii:11:1: internal compiler error: in extract_constrain_insn, at
recog.c:2195
0x7e973a _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/marxin/Programming/gcc/gcc/rtl-error.c:108
0x7e9760 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
/home/marxin/Programming/gcc/gcc/rtl-error.c:118
0x7e79e3 extract_constrain_insn(rtx_insn*)
/home/marxin/Programming/gcc/gcc/recog.c:2195
0x109c6ef copyprop_hardreg_forward_1
/home/marxin/Programming/gcc/gcc/regcprop.c:802
0x109d50e execute
/home/marxin/Programming/gcc/gcc/regcprop.c:1367
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-661946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 18:01:48 2019
Return-Path: <gcc-bugs-return-661946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100558 invoked by alias); 1 Dec 2019 18:01:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100535 invoked by uid 48); 1 Dec 2019 18:01:44 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92744] [10 Regression] error: insn does not satisfy its constraints since r278439
Date: Sun, 01 Dec 2019 18:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work version target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92744-4-WHdp76kka0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00016.txt.bz2
Content-length: 623
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92744
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-01
Known to work| |9.2.0
Version|9.0 |10.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
>From gcc-bugs-return-661947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 18:03:29 2019
Return-Path: <gcc-bugs-return-661947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103099 invoked by alias); 1 Dec 2019 18:03:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103063 invoked by uid 48); 1 Dec 2019 18:03:25 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92740] induct2 (from polyhedron) regresses 267% with -O2 -ftree-vectorize -ftree-slp-vectorize -fvect-cost-modes=dynamic compared to -O2
Date: Sun, 01 Dec 2019 18:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92740-4-fMcZbVJLAW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00017.txt.bz2
Content-length: 609
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92740
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-12-01
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Can you please point to LNT number where you see it?
>From gcc-bugs-return-661948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 18:04:41 2019
Return-Path: <gcc-bugs-return-661948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104212 invoked by alias); 1 Dec 2019 18:04:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104118 invoked by uid 48); 1 Dec 2019 18:04:37 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Sun, 01 Dec 2019 18:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work blocked target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92738-4-Tl6ujQdGk2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00018.txt.bz2
Content-length: 849
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-01
CC| |marxin at gcc dot gnu.org
Known to work| |9.2.0
Blocks| |26163
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
[Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
>From gcc-bugs-return-661949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 18:05:12 2019
Return-Path: <gcc-bugs-return-661949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104987 invoked by alias); 1 Dec 2019 18:05:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104949 invoked by uid 48); 1 Dec 2019 18:05:08 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92741] [10 Regression] ICE: verify_gimple failed (error: invalid vector types in nop conversion)
Date: Sun, 01 Dec 2019 18:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work assigned_to target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92741-4-UPAxqkzhCW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00019.txt.bz2
Content-length: 834
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92741
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-01
CC| |marxin at gcc dot gnu.org
Known to work| |9.2.0
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r278245.
>From gcc-bugs-return-661950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 18:08:22 2019
Return-Path: <gcc-bugs-return-661950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106581 invoked by alias); 1 Dec 2019 18:08:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106540 invoked by uid 48); 1 Dec 2019 18:08:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92744] [10 Regression] error: insn does not satisfy its constraints since r278439
Date: Sun, 01 Dec 2019 18:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-92744-4-Tx7CYqW4pD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00020.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92744
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Honza mentioned this too. I'll have a look.
>From gcc-bugs-return-661951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 18:29:52 2019
Return-Path: <gcc-bugs-return-661951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15353 invoked by alias); 1 Dec 2019 18:29:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14975 invoked by uid 48); 1 Dec 2019 18:29:48 -0000
From: "lutztonineubert at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91369] Implement P0784R7: constexpr new
Date: Sun, 01 Dec 2019 18:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lutztonineubert at gmail dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-91369-4-QKHJXf2F7p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00021.txt.bz2
Content-length: 694
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91369
Toni Neubert <lutztonineubert at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lutztonineubert at gmail dot com
--- Comment #21 from Toni Neubert <lutztonineubert at gmail dot com> ---
I get: 'allocated storage has not been deallocated' when using
prvalues/xvalues:
struct A {
constexpr A() : p{new int} {}
constexpr ~A() {
delete p;
}
int* p;
};
constexpr bool test() {
A{};
return true;
}
constexpr auto res = test();
static_assert(res);
>From gcc-bugs-return-661952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 18:58:43 2019
Return-Path: <gcc-bugs-return-661952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55730 invoked by alias); 1 Dec 2019 18:58:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55675 invoked by uid 48); 1 Dec 2019 18:58:39 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92743] doc: -Wattribute-alias improperly indexed
Date: Sun, 01 Dec 2019 18:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: diagnostic, documentation, easyhack
X-Bugzilla-Severity: trivial
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc bug_severity
Message-ID: <bug-92743-4-5J8oCaQMTu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92743-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92743-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00022.txt.bz2
Content-length: 512
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92743
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic, documentation,
| |easyhack
CC| |egallager at gcc dot gnu.org
Severity|normal |trivial
>From gcc-bugs-return-661953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 19:04:14 2019
Return-Path: <gcc-bugs-return-661953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69883 invoked by alias); 1 Dec 2019 19:04:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69856 invoked by uid 48); 1 Dec 2019 19:04:10 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Sun, 01 Dec 2019 19:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92738-4-9ChtAmfGCp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00023.txt.bz2
Content-length: 233
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
One of the big changes that caused that:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=21.264.4
>From gcc-bugs-return-661954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 20:16:36 2019
Return-Path: <gcc-bugs-return-661954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107635 invoked by alias); 1 Dec 2019 20:16:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107606 invoked by uid 48); 1 Dec 2019 20:16:32 -0000
From: "milasudril at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92745] New: Initializing array with vec4 results in compile error
Date: Sun, 01 Dec 2019 20:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: milasudril at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_file_loc bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00024.txt.bz2
Content-length: 1863
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92745
Bug ID: 92745
Summary: Initializing array with vec4 results in compile error
Product: gcc
Version: 8.3.0
URL: https://gcc.godbolt.org/z/sxvR3G
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: milasudril at gmail dot com
Target Milestone: ---
Target: Any
In GCC 8.3 and later the following code fails to compile:
#include <array>
template<class T>
using vec4_t __attribute__((vector_size(4*sizeof(T)))) = float;
auto transpose(std::array<vec4_t<float>, 4> col)
{
std::array<vec4_t<float>, 4> ret{vec4_t<float>{col[0][0], col[1][0],
col[2][0], col[3][0]},
vec4_t<float>{col[0][1], col[1][1],
col[2][1], col[3][1]},
vec4_t<float>{col[0][2], col[1][2],
col[2][2], col[3][2]},
vec4_t<float>{col[0][3], col[1][3],
col[2][3], col[3][3]}};
return ret;
}
x86-64 gcc 8.3
-O3
1
<Compilation failed>
x86-64 gcc 8.3 - 1240ms
<source>: In function 'auto transpose(std::array<__vector(4) float, 4>)':
<source>:11:102: error: too many initializers for 'std::array<__vector(4)
float, 4>'
vec4_t<float>{col[0][3],
col[1][3], col[2][3], col[3][3]}};
^
Compiler returned: 1
It compiles with GCC 8.2 and earlier, and also the latest version of clang.
>From gcc-bugs-return-661955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 20:29:55 2019
Return-Path: <gcc-bugs-return-661955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120057 invoked by alias); 1 Dec 2019 20:29:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119972 invoked by uid 48); 1 Dec 2019 20:29:51 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92723] [10 Regression] ICE in expand_shift_1, at expmed.c:2635
Date: Sun, 01 Dec 2019 20:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: ice-on-valid-code, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc target_milestone short_desc
Message-ID: <bug-92723-4-KDFk86EY8H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00025.txt.bz2
Content-length: 656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92723
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jamborm at gcc dot gnu.org
Target Milestone|--- |10.0
Summary|ICE in expand_shift_1, at |[10 Regression] ICE in
|expmed.c:2635 |expand_shift_1, at
| |expmed.c:2635
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
ICEs since r275982.
>From gcc-bugs-return-661956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 20:35:11 2019
Return-Path: <gcc-bugs-return-661956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124383 invoked by alias); 1 Dec 2019 20:35:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124294 invoked by uid 48); 1 Dec 2019 20:35:06 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/90374] Fortran 2018: Support d0.d, e0.d, es0.d, en0.d, g0.d and ew.d e0 edit descriptors for output
Date: Sun, 01 Dec 2019 20:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90374-4-lOJFfUYNKV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90374-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90374-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00026.txt.bz2
Content-length: 879
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90374
--- Comment #7 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to anlauf from comment #6)
> (In reply to Jerry DeLisle from comment #5)
> > Author: jvdelisle
> > Date: Thu Nov 28 18:33:20 2019
> > New Revision: 278817
>
> Jerry,
>
> your change to format.c generates a warning here:
>
> ../../../trunk/libgfortran/io/format.c: In function 'parse_format_list':
> ../../../trunk/libgfortran/io/format.c:1029:7: warning: suggest explicit
> braces to avoid am
> biguous 'else' [-Wdangling-else]
> 1029 | if (t != FMT_POSINT)
> | ^
>
> Looking at the context:
>
> t = format_lex (fmt);
> if (t != FMT_POSINT)
> if (t == FMT_ZERO)
> {
>
> this seems to make sense (to me). Do you plan to add {}?
Hi Herald, I saw that also, so plan to add the braces.
>From gcc-bugs-return-661957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 21:00:52 2019
Return-Path: <gcc-bugs-return-661957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43866 invoked by alias); 1 Dec 2019 21:00:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43184 invoked by uid 48); 1 Dec 2019 21:00:46 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92622] FAIL: gcc.dg/Warray-bounds-22.c on ILP32: missing warnings for VLA on lines 67 and 69
Date: Sun, 01 Dec 2019 21:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92622-4-42qv3jbjCu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92622-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92622-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00027.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92622
sandra at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandra at gcc dot gnu.org
--- Comment #2 from sandra at gcc dot gnu.org ---
I've been seeing this random failure on nios2-elf and nios2-linux-gnu, too.
>From gcc-bugs-return-661958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 21:47:01 2019
Return-Path: <gcc-bugs-return-661958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7581 invoked by alias); 1 Dec 2019 21:47:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7486 invoked by uid 48); 1 Dec 2019 21:46:56 -0000
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82904] [8/9/10 Regression] ICE in make_ssa_name_fn, at tree-ssanames.c:261
Date: Sun, 01 Dec 2019 21:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-82904-4-rthfyXiMNS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82904-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82904-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00028.txt.bz2
Content-length: 614
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82904
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gcc dot gnu.org
--- Comment #6 from anlauf at gcc dot gnu.org ---
Do I understand Richard's comment correctly that we should get for
character(:), allocatable, save :: x
in the dump sth. like:
static integer(kind=4) _F.x = 0;
static character(kind=1)[1:_F.x] * x = 0B;
i.e. the length should be initialized to 0?
>From gcc-bugs-return-661959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 22:30:43 2019
Return-Path: <gcc-bugs-return-661959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5343 invoked by alias); 1 Dec 2019 22:30:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5192 invoked by uid 55); 1 Dec 2019 22:30:26 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/90374] Fortran 2018: Support d0.d, e0.d, es0.d, en0.d, g0.d and ew.d e0 edit descriptors for output
Date: Sun, 01 Dec 2019 22:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90374-4-sw1HgaguLI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90374-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90374-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00029.txt.bz2
Content-length: 512
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90374
--- Comment #8 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Author: jvdelisle
Date: Sun Dec 1 22:29:43 2019
New Revision: 278886
URL: https://gcc.gnu.org/viewcvs?rev=278886&root=gcc&view=rev
Log:
2019-12-01 Jerry DeLisle <jvdelisle@gcc.ngu.org>
PR fortran/90374
* io/format.c (parse_format_list): Add braces to disambiguate
conditional.
Modified:
trunk/libgfortran/ChangeLog
trunk/libgfortran/io/format.c
>From gcc-bugs-return-661960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 01 22:32:20 2019
Return-Path: <gcc-bugs-return-661960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7487 invoked by alias); 1 Dec 2019 22:32:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7216 invoked by uid 48); 1 Dec 2019 22:32:12 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/90374] Fortran 2018: Support d0.d, e0.d, es0.d, en0.d, g0.d and ew.d e0 edit descriptors for output
Date: Sun, 01 Dec 2019 22:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90374-4-STtsSk2PVG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90374-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90374-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00030.txt.bz2
Content-length: 531
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90374
--- Comment #9 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to anlauf from comment #6)
---snip---
> Jerry,
>
> your change to format.c generates a warning here:
>
> ../../../trunk/libgfortran/io/format.c: In function 'parse_format_list':
> ../../../trunk/libgfortran/io/format.c:1029:7: warning: suggest explicit
---snip---
> {
>
> this seems to make sense (to me). Do you plan to add {}?
Hi Herald, I saw that also, so did add the braces.
>From gcc-bugs-return-661961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 03:11:07 2019
Return-Path: <gcc-bugs-return-661961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101804 invoked by alias); 2 Dec 2019 03:11:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101734 invoked by uid 48); 2 Dec 2019 03:11:03 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87403] [Meta-bug] Issues that suggest a new warning
Date: Mon, 02 Dec 2019 03:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, meta-bug
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87403-4-gJPaDzL4kB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87403-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87403-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00031.txt.bz2
Content-length: 185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
David Malcolm's new static analyzer might solve some of these
>From gcc-bugs-return-661962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 03:14:55 2019
Return-Path: <gcc-bugs-return-661962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104550 invoked by alias); 2 Dec 2019 03:14:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104456 invoked by uid 48); 2 Dec 2019 03:14:51 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/68230] Unused function parameters not reported by -Wunused-parameter when only used recursively (add -Wparameter-only-used-recursively instead?)
Date: Mon, 02 Dec 2019 03:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also
Message-ID: <bug-68230-4-y910MD1JtG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68230-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68230-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00032.txt.bz2
Content-length: 532
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68230
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=32562
--- Comment #11 from Eric Gallager <egallager at gcc dot gnu.org> ---
bug 32562 is related (that's for functions, this is for parameters)
>From gcc-bugs-return-661963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 03:17:15 2019
Return-Path: <gcc-bugs-return-661963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106572 invoked by alias); 2 Dec 2019 03:17:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106481 invoked by uid 48); 2 Dec 2019 03:17:10 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/89863] [meta-bug] Issues that static analyzers (cppcheck, clang-static-analyzer) find that gcc misses
Date: Mon, 02 Dec 2019 03:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-89863-4-hWG6azGFzq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89863-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89863-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00033.txt.bz2
Content-length: 517
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89863
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
Some of the bugs that this one depends upon might be useful inspiration for the
new analyzer that David Malcolm is working on.
>From gcc-bugs-return-661964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 03:52:57 2019
Return-Path: <gcc-bugs-return-661964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4096 invoked by alias); 2 Dec 2019 03:52:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4023 invoked by uid 55); 2 Dec 2019 03:52:50 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92499] nios2 backend needs to consider allocated object size, not C object size for gprel optimization
Date: Mon, 02 Dec 2019 03:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92499-4-UcRFdgw4VU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00034.txt.bz2
Content-length: 1617
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92499
--- Comment #9 from sandra at gcc dot gnu.org ---
Author: sandra
Date: Mon Dec 2 03:52:15 2019
New Revision: 278891
URL: https://gcc.gnu.org/viewcvs?rev=278891&root=gcc&view=rev
Log:
2019-12-01 Sandra Loosemore <sandra@codesourcery.com>
Fix bugs relating to flexibly-sized objects in nios2 backend.
PR target/92499
gcc/c/
* c-decl.c (flexible_array_type_p): Move to common code.
gcc/
* config/nios2/nios2.c (nios2_in_small_data_p): Do not consider
objects of flexible types to be small if they have internal linkage
or are declared extern.
* config/nios2/nios2.h (ASM_OUTPUT_ALIGNED_LOCAL): Replace with...
(ASM_OUTPUT_ALIGNED_DECL_LOCAL): ...this. Use targetm.in_small_data_p
instead of the size of the object initializer.
* tree.c (flexible_array_type_p): Move from C front end, and
generalize to handle fields in non-C structures.
* tree.h (flexible_array_type_p): Declare.
gcc/testsuite/
* gcc.target/nios2/pr92499-1.c: New.
* gcc.target/nios2/pr92499-2.c: New.
* gcc.target/nios2/pr92499-3.c: New.
Added:
trunk/gcc/testsuite/gcc.target/nios2/pr92499-1.c
trunk/gcc/testsuite/gcc.target/nios2/pr92499-2.c
trunk/gcc/testsuite/gcc.target/nios2/pr92499-3.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-decl.c
trunk/gcc/config/nios2/nios2.c
trunk/gcc/config/nios2/nios2.h
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree.c
trunk/gcc/tree.h
>From gcc-bugs-return-661965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 06:24:52 2019
Return-Path: <gcc-bugs-return-661965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95924 invoked by alias); 2 Dec 2019 06:24:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95766 invoked by uid 55); 2 Dec 2019 06:24:37 -0000
From: "helijia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92132] new test case gcc.dg/vect/vect-cond-reduc-4.c fails with its introduction in r277067
Date: Mon, 02 Dec 2019 06:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: helijia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92132-4-YA0I2gN8BV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92132-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92132-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00035.txt.bz2
Content-length: 1993
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92132
--- Comment #7 from Li Jia He <helijia at gcc dot gnu.org> ---
Author: helijia
Date: Mon Dec 2 06:23:56 2019
New Revision: 278892
URL: https://gcc.gnu.org/viewcvs?rev=278892&root=gcc&view=rev
Log:
[rs6000]Fix PR92098 by backporting vec_cmp and vcond_mask supports to
gcc-9-branch
As PR92132 added vec_cmp_* and vcond_mask_* supports on trunk. This is a
partial backport of vec_{cmp,cmpu}<mode><mode> interface and related expand
to gcc-9-branch to fix PR92098.
gcc/ChangeLog
2019-12-02 Li Jia He <helijia@linux.ibm.com>
Partial backport from mainline
PR target/92098
2019-11-08 Kewen Lin <linkw@gcc.gnu.org>
PR target/92132
* config/rs6000/predicates.md
(signed_or_equality_comparison_operator): New predicate.
(unsigned_or_equality_comparison_operator): Likewise.
* config/rs6000/rs6000.md (one_cmpl<mode>2): Remove expand.
(one_cmpl<mode>3_internal): Rename to one_cmpl<mode>2.
* config/rs6000/vector.md
(vcond_mask_<mode><mode> for VEC_I and VEC_I): New expand.
(vec_cmp<mode><mode> for VEC_I and VEC_I): Likewise.
(vec_cmpu<mode><mode> for VEC_I and VEC_I): Likewise.
gcc/testsuite/ChangeLog
2019-12-02 Li Jia He <helijia@linux.ibm.com>
Partial backport from trunk
PR target/92098
2019-11-08 Kewen Lin <linkw@gcc.gnu.org>
PR target/92132
* gcc.target/powerpc/pr92132-fp-1.c: New test.
* gcc.target/powerpc/pr92132-fp-2.c: New test.
Added:
branches/gcc-9-branch/gcc/testsuite/gcc.target/powerpc/pr92098-int-1.c
branches/gcc-9-branch/gcc/testsuite/gcc.target/powerpc/pr92098-int-2.c
Modified:
branches/gcc-9-branch/gcc/ChangeLog
branches/gcc-9-branch/gcc/config/rs6000/predicates.md
branches/gcc-9-branch/gcc/config/rs6000/rs6000.md
branches/gcc-9-branch/gcc/config/rs6000/vector.md
branches/gcc-9-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 06:24:52 2019
Return-Path: <gcc-bugs-return-661966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96045 invoked by alias); 2 Dec 2019 06:24:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95804 invoked by uid 55); 2 Dec 2019 06:24:46 -0000
From: "helijia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92098] [9 Regression] After r262333, the following code cannot be vectorized on powerpc64le.
Date: Mon, 02 Dec 2019 06:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: helijia at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92098-4-In4eJSSOVt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92098-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92098-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00036.txt.bz2
Content-length: 1993
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92098
--- Comment #3 from Li Jia He <helijia at gcc dot gnu.org> ---
Author: helijia
Date: Mon Dec 2 06:23:56 2019
New Revision: 278892
URL: https://gcc.gnu.org/viewcvs?rev=278892&root=gcc&view=rev
Log:
[rs6000]Fix PR92098 by backporting vec_cmp and vcond_mask supports to
gcc-9-branch
As PR92132 added vec_cmp_* and vcond_mask_* supports on trunk. This is a
partial backport of vec_{cmp,cmpu}<mode><mode> interface and related expand
to gcc-9-branch to fix PR92098.
gcc/ChangeLog
2019-12-02 Li Jia He <helijia@linux.ibm.com>
Partial backport from mainline
PR target/92098
2019-11-08 Kewen Lin <linkw@gcc.gnu.org>
PR target/92132
* config/rs6000/predicates.md
(signed_or_equality_comparison_operator): New predicate.
(unsigned_or_equality_comparison_operator): Likewise.
* config/rs6000/rs6000.md (one_cmpl<mode>2): Remove expand.
(one_cmpl<mode>3_internal): Rename to one_cmpl<mode>2.
* config/rs6000/vector.md
(vcond_mask_<mode><mode> for VEC_I and VEC_I): New expand.
(vec_cmp<mode><mode> for VEC_I and VEC_I): Likewise.
(vec_cmpu<mode><mode> for VEC_I and VEC_I): Likewise.
gcc/testsuite/ChangeLog
2019-12-02 Li Jia He <helijia@linux.ibm.com>
Partial backport from trunk
PR target/92098
2019-11-08 Kewen Lin <linkw@gcc.gnu.org>
PR target/92132
* gcc.target/powerpc/pr92132-fp-1.c: New test.
* gcc.target/powerpc/pr92132-fp-2.c: New test.
Added:
branches/gcc-9-branch/gcc/testsuite/gcc.target/powerpc/pr92098-int-1.c
branches/gcc-9-branch/gcc/testsuite/gcc.target/powerpc/pr92098-int-2.c
Modified:
branches/gcc-9-branch/gcc/ChangeLog
branches/gcc-9-branch/gcc/config/rs6000/predicates.md
branches/gcc-9-branch/gcc/config/rs6000/rs6000.md
branches/gcc-9-branch/gcc/config/rs6000/vector.md
branches/gcc-9-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 06:38:06 2019
Return-Path: <gcc-bugs-return-661967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108280 invoked by alias); 2 Dec 2019 06:38:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108212 invoked by uid 55); 2 Dec 2019 06:38:02 -0000
From: "fxue at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92133] Support multi versioning on self recursive function
Date: Mon, 02 Dec 2019 06:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fxue at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92133-4-xJLT35OXXY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92133-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92133-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00037.txt.bz2
Content-length: 1664
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92133
--- Comment #7 from fxue at gcc dot gnu.org ---
Author: fxue
Date: Mon Dec 2 06:37:30 2019
New Revision: 278893
URL: https://gcc.gnu.org/viewcvs?rev=278893&root=gcc&view=rev
Log:
Enable recursive function versioning
2019-12-02 Feng Xue <fxue@os.amperecomputing.com>
PR ipa/92133
* doc/invoke.texi (ipa-cp-max-recursive-depth): Document new option.
(ipa-cp-min-recursive-probability): Likewise.
* params.opt (ipa-cp-max-recursive-depth): New.
(ipa-cp-min-recursive-probability): Likewise.
* ipa-cp.c (ipcp_lattice<valtype>::add_value): Add two new parameters
val_p and unlimited.
(self_recursively_generated_p): New function.
(get_val_across_arith_op): Likewise.
(propagate_vals_across_arith_jfunc): Add constant propagation for
self-recursive function.
(incorporate_penalties): Do not penalize pure self-recursive function.
(good_cloning_opportunity_p): Dump node_is_self_scc flag.
(propagate_constants_topo): Set node_is_self_scc flag for cgraph node.
(get_info_about_necessary_edges): Relax hotness check for edge to
self-recursive function.
* ipa-prop.h (ipa_node_params): Add new field node_is_self_scc.
2019-12-02 Feng Xue <fxue@os.amperecomputing.com>
PR ipa/92133
* gcc.dg/ipa/ipa-clone-2.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/ipa/ipa-clone-2.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/doc/invoke.texi
trunk/gcc/ipa-cp.c
trunk/gcc/ipa-prop.h
trunk/gcc/params.opt
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 06:55:04 2019
Return-Path: <gcc-bugs-return-661968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124941 invoked by alias); 2 Dec 2019 06:55:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124699 invoked by uid 48); 2 Dec 2019 06:55:00 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92746] New: [10 Regression] ICE in check_noexcept_r, at cp/except.c:1114
Date: Mon, 02 Dec 2019 06:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00038.txt.bz2
Content-length: 3787
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92746
Bug ID: 92746
Summary: [10 Regression] ICE in check_noexcept_r, at
cp/except.c:1114
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
g++-10.0.0-alpha20191201 snapshot (r278886) ICEs when compiling the following
testcase, reduced from
test/CXX/concepts-ts/dcl.dcl/dcl.spec/dcl.spec.concept/p1.cpp from the clang
9.0.0 test suite, w/ -fconcepts:
template<typename T> concept bool C3() { return true; }
static_assert(noexcept(C3<int>()), "function concept should be treated as if
noexcept(true) specified");
% g++-10.0.0-alpha20191201 -fconcepts -c vtdkmihj.cc
vtdkmihj.cc:2:33: internal compiler error: in check_noexcept_r, at
cp/except.c:1114
2 | static_assert(noexcept(C3<int>()), "function concept should be treated
as if noexcept(true) specified");
| ^
0x5fec0a check_noexcept_r
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/cp/except.c:1114
0x11e6c1c walk_tree_1(tree_node**, tree_node* (*)(tree_node**, int*, void*),
void*, hash_set<tree_node*, false, default_hash_traits<tree_node*> >*,
tree_node* (*)(tree_node**, int*, tree_node* (*)(tree_node**, int*, void*),
void*, hash_set<tree_node*, false, default_hash_traits<tree_node*> >*))
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree.c:11957
0x11ea5eb walk_tree_without_duplicates_1(tree_node**, tree_node*
(*)(tree_node**, int*, void*), void*, tree_node* (*)(tree_node**, int*,
tree_node* (*)(tree_node**, int*, void*), void*, hash_set<tree_node*, false,
default_hash_traits<tree_node*> >*))
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree.c:12313
0x8de9ec expr_noexcept_p(tree_node*, int)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/cp/except.c:1212
0x8deb6e finish_noexcept_expr(tree_node*, int)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/cp/except.c:1197
0x95422d cp_parser_unary_expression
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/cp/parser.c:8320
0x92f774 cp_parser_binary_expression
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/cp/parser.c:9480
0x930806 cp_parser_assignment_expression
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/cp/parser.c:9780
0x930049 cp_parser_constant_expression
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/cp/parser.c:10074
0x930342 cp_parser_static_assert
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/cp/parser.c:14580
0x964d7f cp_parser_declaration
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/cp/parser.c:13322
0x9653a0 cp_parser_translation_unit
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/cp/parser.c:4721
0x9653a0 c_parse_file()
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/cp/parser.c:43048
0xa7493f c_common_parse_file()
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/c-family/c-opts.c:1185
>From gcc-bugs-return-661969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 07:34:59 2019
Return-Path: <gcc-bugs-return-661969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74093 invoked by alias); 2 Dec 2019 07:34:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74054 invoked by uid 48); 2 Dec 2019 07:34:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92734] Missing match.pd simplification done by fold_binary_loc on generic
Date: Mon, 02 Dec 2019 07:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92734-4-p3J0gRzcLR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00039.txt.bz2
Content-length: 959
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92734
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
We have a set of special-case patterns for simple associations in match.pd, one
for this case seems missing, like the group
/* Match patterns that allow contracting a plus-minus pair
irrespective of overflow issues. */
/* (A +- B) - A -> +- B */
/* (A +- B) -+ B -> A */
/* A - (A +- B) -> -+ B */
/* A +- (B -+ A) -> +- B */
closest match is
/* CST1 - (CST2 - A) -> CST3 + A */
(simplify
(minus CONSTANT_CLASS_P@1 (minus CONSTANT_CLASS_P@2 @0))
(with { tree cst = const_binop (MINUS_EXPR, type, @1, @2); }
(if (cst && !TREE_OVERFLOW (cst))
(plus { cst; } @0))))
which "just" seems to lack a (convert? ...) around the inner minus.
And yes, reassoc would be the pass to handle this, maybe in the very late
if/when
we decide to switch the IL to -fwapv semantics there.
>From gcc-bugs-return-661970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 07:40:15 2019
Return-Path: <gcc-bugs-return-661970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77743 invoked by alias); 2 Dec 2019 07:40:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77707 invoked by uid 48); 2 Dec 2019 07:40:10 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92736] [9/10 Regression] Error when using a variable from a module in a submodule and its parent module.
Date: Mon, 02 Dec 2019 07:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_known_to_work keywords cf_reconfirmed_on everconfirmed short_desc target_milestone cf_known_to_fail
Message-ID: <bug-92736-4-BK6MGEq8rX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00040.txt.bz2
Content-length: 1125
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92736
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Known to work| |7.5.0, 8.3.0, 9.2.0
Keywords| |rejects-valid
Last reconfirmed| |2019-12-02
Ever confirmed|0 |1
Summary|Error when using a variable |[9/10 Regression] Error
|from a module in a |when using a variable from
|submodule and its parent |a module in a submodule and
|module. |its parent module.
Target Milestone|--- |9.3
Known to fail| |10.0, 9.2.1
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. ifort accepts the code so I assume it is valid.
>From gcc-bugs-return-661971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 07:44:56 2019
Return-Path: <gcc-bugs-return-661971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82072 invoked by alias); 2 Dec 2019 07:44:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82025 invoked by uid 48); 2 Dec 2019 07:44:50 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Mon, 02 Dec 2019 07:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-92738-4-cG0nWdTesi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00041.txt.bz2
Content-length: 1142
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization,
| |needs-bisection
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
There is
2019-05-23 Richard Biener <rguenther@suse.de>
PR tree-optimization/88440
* opts.c (default_options_table): Enable
-ftree-loop-distribute-patterns
at -O[2s]+.
* tree-loop-distribution.c (generate_memset_builtin): Fold the
generated call.
(generate_memcpy_builtin): Likewise.
(distribute_loop): Pass in whether to only distribute patterns.
(prepare_perfect_loop_nest): Also allow size optimization.
(pass_loop_distribution::execute): When optimizing a loop
nest for size allow pattern replacement.
but that should cause code-size shrinking... (just try
-fno-tree-loop-distribute-patterns and see if fixed)
>From gcc-bugs-return-661972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 07:48:51 2019
Return-Path: <gcc-bugs-return-661972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88548 invoked by alias); 2 Dec 2019 07:48:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88440 invoked by uid 48); 2 Dec 2019 07:48:46 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92741] [10 Regression] ICE: verify_gimple failed (error: invalid vector types in nop conversion)
Date: Mon, 02 Dec 2019 07:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-92741-4-m7CTS8OImI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00042.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92741
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
_2 = (vector(2) int) { 0, 0, 0, 0 };
that's also not folded.
>From gcc-bugs-return-661973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 07:51:39 2019
Return-Path: <gcc-bugs-return-661973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91237 invoked by alias); 2 Dec 2019 07:51:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91045 invoked by uid 48); 2 Dec 2019 07:51:35 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92741] [10 Regression] ICE: verify_gimple failed (error: invalid vector types in nop conversion)
Date: Mon, 02 Dec 2019 07:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-92741-4-PX7rH6xfiq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00043.txt.bz2
Content-length: 403
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92741
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #3 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-661974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 07:51:58 2019
Return-Path: <gcc-bugs-return-661974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104838 invoked by alias); 2 Dec 2019 07:51:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99244 invoked by uid 48); 2 Dec 2019 07:51:55 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92745] [8/9/10 Regression] Initializing array with vec4 results in compile error
Date: Mon, 02 Dec 2019 07:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_known_to_work keywords cf_reconfirmed_on everconfirmed short_desc target_milestone
Message-ID: <bug-92745-4-zbhMckW563@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00044.txt.bz2
Content-length: 977
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92745
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Status|UNCONFIRMED |NEW
Known to work| |7.5.0
Keywords| |rejects-valid
Last reconfirmed| |2019-12-02
Ever confirmed|0 |1
Summary|Initializing array with |[8/9/10 Regression]
|vec4 results in compile |Initializing array with
|error |vec4 results in compile
| |error
Target Milestone|--- |8.4
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-661975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 07:52:21 2019
Return-Path: <gcc-bugs-return-661975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128757 invoked by alias); 2 Dec 2019 07:52:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124215 invoked by uid 48); 2 Dec 2019 07:52:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92746] [10 Regression] ICE in check_noexcept_r, at cp/except.c:1114
Date: Mon, 02 Dec 2019 07:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-92746-4-XxGNXsUzNY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00045.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92746
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-661976-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 08:13:05 2019
Return-Path: <gcc-bugs-return-661976-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43713 invoked by alias); 2 Dec 2019 08:13:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43646 invoked by uid 48); 2 Dec 2019 08:13:00 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82904] [8/9/10 Regression] ICE in make_ssa_name_fn, at tree-ssanames.c:261
Date: Mon, 02 Dec 2019 08:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82904-4-ZGpU6ATuO0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82904-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82904-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00046.txt.bz2
Content-length: 672
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82904
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to anlauf from comment #6)
> Do I understand Richard's comment correctly that we should get for
>
> character(:), allocatable, save :: x
>
> in the dump sth. like:
>
> static integer(kind=4) _F.x = 0;
> static character(kind=1)[1:_F.x] * x = 0B;
>
> i.e. the length should be initialized to 0?
No, the issue is the [1:_F.x], the frontend needs to place an explicit
DECL_EXPR in the IL (where the static initialization / allocation happens)
which will be the place the middle-end "evaluates" the size expression.
>From gcc-bugs-return-661977-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 08:14:44 2019
Return-Path: <gcc-bugs-return-661977-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45689 invoked by alias); 2 Dec 2019 08:14:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45535 invoked by uid 48); 2 Dec 2019 08:14:40 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92098] [9 Regression] After r262333, the following code cannot be vectorized on powerpc64le.
Date: Mon, 02 Dec 2019 08:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92098-4-bOVa9hvjvK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92098-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92098-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00047.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92098
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-661978-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 08:14:44 2019
Return-Path: <gcc-bugs-return-661978-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45806 invoked by alias); 2 Dec 2019 08:14:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45594 invoked by uid 48); 2 Dec 2019 08:14:40 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53947] [meta-bug] vectorizer missed-optimizations
Date: Mon, 02 Dec 2019 08:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-53947-4-VbmDFdi80o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53947-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00048.txt.bz2
Content-length: 513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 92098, which changed state.
Bug 92098 Summary: [9 Regression] After r262333, the following code cannot be vectorized on powerpc64le.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92098
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-661980-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 08:16:40 2019
Return-Path: <gcc-bugs-return-661980-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50352 invoked by alias); 2 Dec 2019 08:16:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50088 invoked by uid 48); 2 Dec 2019 08:16:35 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
Date: Mon, 02 Dec 2019 08:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.2.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-26163-4-keKuwah6i6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
References: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00050.txt.bz2
Content-length: 529
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 91222, which changed state.
Bug 91222 Summary: [10 Regression] 507.cactuBSSN_r build fails in warn_types_mismatch at ipa-devirt.c:1006 since r273571
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91222
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-661979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 08:16:39 2019
Return-Path: <gcc-bugs-return-661979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50218 invoked by alias); 2 Dec 2019 08:16:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50008 invoked by uid 48); 2 Dec 2019 08:16:34 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91222] [10 Regression] 507.cactuBSSN_r build fails in warn_types_mismatch at ipa-devirt.c:1006 since r273571
Date: Mon, 02 Dec 2019 08:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91222-4-SclCanuYE4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91222-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91222-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00049.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91222
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #31 from Martin Liška <marxin at gcc dot gnu.org> ---
It's fixed.
>From gcc-bugs-return-661981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 08:52:25 2019
Return-Path: <gcc-bugs-return-661981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124793 invoked by alias); 2 Dec 2019 08:52:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124667 invoked by uid 55); 2 Dec 2019 08:52:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92712] [8/9/10 Regression] Performance regression with assumed values
Date: Mon, 02 Dec 2019 08:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92712-4-OgvxibYEDr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00051.txt.bz2
Content-length: 1389
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
--- Comment #21 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Dec 2 08:51:49 2019
New Revision: 278894
URL: https://gcc.gnu.org/viewcvs?rev=278894&root=gcc&view=rev
Log:
PR tree-optimization/92712
* match.pd ((A * B) +- A -> (B +- 1) * A,
A +- (A * B) -> (1 +- B) * A): Allow optimizing signed integers
even when we don't know anything about range of A, but do know
something about range of B and the simplification won't introduce
new UB.
* gcc.dg/tree-ssa/pr92712-1.c: New test.
* gcc.dg/tree-ssa/pr92712-2.c: New test.
* gcc.dg/tree-ssa/pr92712-3.c: New test.
* gfortran.dg/loop_versioning_1.f90: Adjust expected number of
likely to be innermost dimension messages.
* gfortran.dg/loop_versioning_10.f90: Likewise.
* gfortran.dg/loop_versioning_6.f90: Likewise.
Added:
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr92712-1.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr92712-2.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr92712-3.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/match.pd
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/loop_versioning_1.f90
trunk/gcc/testsuite/gfortran.dg/loop_versioning_10.f90
trunk/gcc/testsuite/gfortran.dg/loop_versioning_6.f90
>From gcc-bugs-return-661982-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 09:13:50 2019
Return-Path: <gcc-bugs-return-661982-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27242 invoked by alias); 2 Dec 2019 09:13:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27124 invoked by uid 48); 2 Dec 2019 09:13:45 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92741] [10 Regression] ICE: verify_gimple failed (error: invalid vector types in nop conversion)
Date: Mon, 02 Dec 2019 09:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92741-4-sDEqc0O4cZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00052.txt.bz2
Content-length: 1214
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92741
--- Comment #4 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
This comes from:
if (!useless_type_conversion_p (TREE_TYPE (rhs), TREE_TYPE (v->value)))
{
if (fold_convertible_p (TREE_TYPE (rhs), v->value))
val = fold_build1 (NOP_EXPR, TREE_TYPE (rhs), v->value);
else if (TYPE_SIZE (TREE_TYPE (rhs))
== TYPE_SIZE (TREE_TYPE (v->value)))
val = fold_build1 (VIEW_CONVERT_EXPR, TREE_TYPE (rhs), v->value);
in ipcp_modif_dom_walker::before_dom_children. fold_convertible_p
is returning true for the mismatched vector types, which is clearly
a bug and I have a fix. But does anyone have any thoughts on whether
the above code is correct? It seems strange to be trusting
fold_convertible_p with the choice when this kind of type punning
always acts as a VIEW_CONVERT_EXPR-style reinterpret of the
memory contents. Earlier we have:
if (!v
|| v->by_ref != by_ref
|| maybe_ne (tree_to_poly_int64 (TYPE_SIZE (TREE_TYPE (v->value))),
size))
continue;
which I guess makes it safe in practice.
>From gcc-bugs-return-661984-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 10:27:53 2019
Return-Path: <gcc-bugs-return-661984-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19102 invoked by alias); 2 Dec 2019 10:27:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19025 invoked by uid 48); 2 Dec 2019 10:27:44 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
Date: Mon, 02 Dec 2019 10:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.2.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-26163-4-HcoZsm1Zel@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
References: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00054.txt.bz2
Content-length: 477
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 92133, which changed state.
Bug 92133 Summary: Support multi versioning on self recursive function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92133
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-661983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 10:27:19 2019
Return-Path: <gcc-bugs-return-661983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17946 invoked by alias); 2 Dec 2019 10:27:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17872 invoked by uid 48); 2 Dec 2019 10:27:15 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92747] New: x86 vector builtins throw exceptions
Date: Mon, 02 Dec 2019 10:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00053.txt.bz2
Content-length: 571
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92747
Bug ID: 92747
Summary: x86 vector builtins throw exceptions
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
Looks like all x86 vector builtins used by intrinsics throw exceptions. Seen
with the testcase for PR92645 and __builtin_ia32_packuswb128 for example.
>From gcc-bugs-return-661985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 10:27:53 2019
Return-Path: <gcc-bugs-return-661985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19176 invoked by alias); 2 Dec 2019 10:27:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18964 invoked by uid 48); 2 Dec 2019 10:27:44 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92133] Support multi versioning on self recursive function
Date: Mon, 02 Dec 2019 10:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92133-4-OajYIbL3iR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92133-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92133-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00055.txt.bz2
Content-length: 476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92133
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Martin Jambor <jamborm at gcc dot gnu.org> ---
I believe this is now implemented, so marking as fixed.
>From gcc-bugs-return-661986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 10:28:45 2019
Return-Path: <gcc-bugs-return-661986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20980 invoked by alias); 2 Dec 2019 10:28:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20906 invoked by uid 48); 2 Dec 2019 10:28:40 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92747] x86 vector builtins throw exceptions
Date: Mon, 02 Dec 2019 10:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget cc blocked
Message-ID: <bug-92747-4-s1Xo9Idejl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00056.txt.bz2
Content-length: 1857
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92747
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target| |x86_64-*-*, i?86-*-*
CC| |hjl.tools at gmail dot com,
| |hubicka at gcc dot gnu.org,
| |uros at gcc dot gnu.org
Blocks| |92645
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
11:22 < richi> that is, be careful for -ftrapping-math / -fnon-call-exceptions
(but all intrinsics certainly are not calls!)
11:23 < richi> (interesting twist I guess)
11:23 < jakub> seems leaf attribute isn't used for the intrinsics either
11:23 < richi> so FP arithmetic builtins (if we have those) need to stay
throwing but only for -fnon-call-exceptions
11:25 < jakub> not sure if there is an easy way to find out what is FP builtin
and what is not, perhaps by checking if any of the
argument/return value types have anything to do with floating
types/vectors thereof?
...
11:26 < jakub> richi: as first shot we might just mark everything NOTHROW+ if
not non-call-exceptions and add leaf attribute unconditionally
11:27 < jakub> richi: except that leaf might be wrong if we have any atomic
related intrinsics :(
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
[Bug 92645] Hand written vector code is 450 times slower when compiled with GCC
compared to Clang
>From gcc-bugs-return-661987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 10:42:00 2019
Return-Path: <gcc-bugs-return-661987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39537 invoked by alias); 2 Dec 2019 10:41:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39451 invoked by uid 48); 2 Dec 2019 10:41:55 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Mon, 02 Dec 2019 10:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92738-4-DjyjVZiPfZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00057.txt.bz2
Content-length: 349
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
Ok, I've just updated LNT filter, and one can see it better with:
https://lnt.opensuse.org/db_default/v4/SPEC/spec_report/branch?sorting=gcc-9%2Cgcc-trunk&all_elf_detail_stats=on
I'm going to bisect the WRF size bump.
>From gcc-bugs-return-661988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 10:50:47 2019
Return-Path: <gcc-bugs-return-661988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58125 invoked by alias); 2 Dec 2019 10:50:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57864 invoked by uid 48); 2 Dec 2019 10:50:43 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92737] cgraph_node and varpool_node needs explicit constructor
Date: Mon, 02 Dec 2019 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed
Message-ID: <bug-92737-4-pkC2gPxIT2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00058.txt.bz2
Content-length: 640
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92737
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-02
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
I can work on that.
>From gcc-bugs-return-661989-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 10:50:58 2019
Return-Path: <gcc-bugs-return-661989-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59035 invoked by alias); 2 Dec 2019 10:50:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58947 invoked by uid 48); 2 Dec 2019 10:50:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92742] [10 Regression] ICE in info_for_reduction, at tree-vect-loop.c:4367
Date: Mon, 02 Dec 2019 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92742-4-xxfYr1sSG1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92742-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92742-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00059.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92742
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-661990-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 10:51:21 2019
Return-Path: <gcc-bugs-return-661990-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61244 invoked by alias); 2 Dec 2019 10:51:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61191 invoked by uid 55); 2 Dec 2019 10:51:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92742] [10 Regression] ICE in info_for_reduction, at tree-vect-loop.c:4367
Date: Mon, 02 Dec 2019 10:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92742-4-5dQ0NuwT6q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92742-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92742-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00060.txt.bz2
Content-length: 703
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92742
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Mon Dec 2 10:50:45 2019
New Revision: 278896
URL: https://gcc.gnu.org/viewcvs?rev=278896&root=gcc&view=rev
Log:
2019-12-02 Richard Biener <rguenther@suse.de>
PR tree-optimization/92742
* tree-vect-loop.c (vect_fixup_reduc_chain): Do not
touch the def-type but verify it is consistent with the
original stmts.
* gcc.dg/torture/pr92742.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/torture/pr92742.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-vect-loop.c
>From gcc-bugs-return-661991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 11:15:55 2019
Return-Path: <gcc-bugs-return-661991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102629 invoked by alias); 2 Dec 2019 11:15:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90753 invoked by uid 48); 2 Dec 2019 11:15:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92739] [10 Regression] Requires clause followed by an attribute no longer compiles
Date: Mon, 02 Dec 2019 11:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-92739-4-qv11HQs9Pb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00061.txt.bz2
Content-length: 1131
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92739
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-02
CC| |asutton at gcc dot gnu.org
Target Milestone|--- |10.0
Summary|[Trunk Regression] Requires |[10 Regression] Requires
|clause followed by an |clause followed by an
|attribute no longer |attribute no longer
|compiles |compiles
Ever confirmed|0 |1
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Christopher Di Bella from comment #0)
> The following code works in 466691493b9, but not in commits starting from
> Git hash 6b42dfe4264.
Which is r278774 for the bugzilla auto-link.
>From gcc-bugs-return-661992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 11:19:51 2019
Return-Path: <gcc-bugs-return-661992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126313 invoked by alias); 2 Dec 2019 11:19:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126255 invoked by uid 48); 2 Dec 2019 11:19:47 -0000
From: "mark.eggleston at codethink dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/89100] Default widths for i, f and g format specifiers in format strings
Date: Mon, 02 Dec 2019 11:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mark.eggleston at codethink dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-89100-4-btGxHtdnyZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89100-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89100-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00062.txt.bz2
Content-length: 530
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89100
MarkEggleston <mark.eggleston at codethink dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #14 from MarkEggleston <mark.eggleston at codethink dot com> ---
Committed 22nd May 2019
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=271511
>From gcc-bugs-return-661993-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 12:03:51 2019
Return-Path: <gcc-bugs-return-661993-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13487 invoked by alias); 2 Dec 2019 12:03:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13427 invoked by uid 48); 2 Dec 2019 12:03:46 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91985] Unsupported DFP not diagnosed with constants or built-in functions
Date: Mon, 02 Dec 2019 12:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-91985-4-CK2zNnEQUQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91985-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91985-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00063.txt.bz2
Content-length: 701
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91985
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tschwinge at gcc dot gnu.org
--- Comment #5 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to jules from comment #4)
> SVN r278684 appears to cause a problem with offloading compilation in lto1
Discussed in threads at
<http://mid.mail-archive.com/87a78hm1ku.fsf@euler.schwinge.homeip.net>, and
<http://mid.mail-archive.com/20191128142402.2949931d@squid.athome>. Resolved
in r278826.
>From gcc-bugs-return-661994-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 12:07:25 2019
Return-Path: <gcc-bugs-return-661994-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15930 invoked by alias); 2 Dec 2019 12:07:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15842 invoked by uid 48); 2 Dec 2019 12:07:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92695] P1064R0 - virtual constexpr fails if object taken from array
Date: Mon, 02 Dec 2019 12:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92695-4-dnIHFVAgp3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00064.txt.bz2
Content-length: 786
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92695
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
For #c12, I think that is because of:
5615 /* Defer virtual destructors so that thunks get the right
5616 linkage. */
5617 if (DECL_VIRTUAL_P (decl) && !at_eof)
5618 {
5619 note_vague_linkage_fn (decl);
5620 return true;
5621 }
which makes mark_used not to synthesize those until end of TU.
Not really sure how to fix that, shall we if constexpr synthesize them early
anyway, but only register for constexpr evaluation and undo other effects of
the synthesize_method? Or handle specially during constexpr evaluation each
time we see those (or just first time, by remembering the body)?
>From gcc-bugs-return-661995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 12:16:54 2019
Return-Path: <gcc-bugs-return-661995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129668 invoked by alias); 2 Dec 2019 12:16:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129628 invoked by uid 48); 2 Dec 2019 12:16:45 -0000
From: "jengelh at inai dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92748] New: Two different -Wreturn-type diagnostics for essentially same code
Date: Mon, 02 Dec 2019 12:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jengelh at inai dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92748-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00065.txt.bz2
Content-length: 1062
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92748
Bug ID: 92748
Summary: Two different -Wreturn-type diagnostics for
essentially same code
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: jengelh at inai dot de
Target Milestone: ---
-- Input --
» cat x.c
static void *f() {}
void *g() {}
-- Observed output --
» gcc x.c -c -Wall -v
gcc version 9.2.1 20190903 [gcc-9-branch revision 275330] (SUSE Linux)
…
x.c:1:1: warning: no return statement in function returning non-void
[-Wreturn-type]
x.c:2:1: warning: control reaches end of non-void function [-Wreturn-type]
-- Expected output --
Emit the same diagnostic messages for both issues, e.g.
x.c:1:1: warning: no return statement in function returning non-void
[-Wreturn-type]
x.c:2:1: warning: no return statement in function returning non-void
[-Wreturn-type]
>From gcc-bugs-return-661996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 12:28:30 2019
Return-Path: <gcc-bugs-return-661996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126408 invoked by alias); 2 Dec 2019 12:28:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126353 invoked by uid 48); 2 Dec 2019 12:28:25 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92741] [10 Regression] ICE: verify_gimple failed (error: invalid vector types in nop conversion)
Date: Mon, 02 Dec 2019 12:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92741-4-rhC6UGKIRd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00066.txt.bz2
Content-length: 1613
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92741
--- Comment #5 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to rsandifo@gcc.gnu.org from comment #4)
> This comes from:
>
> if (!useless_type_conversion_p (TREE_TYPE (rhs), TREE_TYPE (v->value)))
> {
> if (fold_convertible_p (TREE_TYPE (rhs), v->value))
> val = fold_build1 (NOP_EXPR, TREE_TYPE (rhs), v->value);
> else if (TYPE_SIZE (TREE_TYPE (rhs))
> == TYPE_SIZE (TREE_TYPE (v->value)))
> val = fold_build1 (VIEW_CONVERT_EXPR, TREE_TYPE (rhs), v->value);
>
> in ipcp_modif_dom_walker::before_dom_children. fold_convertible_p
> is returning true for the mismatched vector types, which is clearly
> a bug and I have a fix. But does anyone have any thoughts on whether
> the above code is correct?
We do the same for inlining (and IPA-SRA) in force_value_to_type in
tree-inline.c which is where I guess this comes from. There it is
meant to deal with potential parameter type promotion but you are
right that with values passed in aggregates, V_C_Eing always makes
more sense.
> It seems strange to be trusting
> fold_convertible_p with the choice when this kind of type punning
> always acts as a VIEW_CONVERT_EXPR-style reinterpret of the
> memory contents. Earlier we have:
>
> if (!v
> || v->by_ref != by_ref
> || maybe_ne (tree_to_poly_int64 (TYPE_SIZE (TREE_TYPE (v->value))),
> size))
> continue;
>
> which I guess makes it safe in practice.
Yes, I guess it would.
>From gcc-bugs-return-661997-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 12:35:15 2019
Return-Path: <gcc-bugs-return-661997-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11766 invoked by alias); 2 Dec 2019 12:35:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11667 invoked by uid 48); 2 Dec 2019 12:35:10 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92747] x86 vector builtins throw exceptions
Date: Mon, 02 Dec 2019 12:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92747-4-RGaCW8YoV1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00067.txt.bz2
Content-length: 934
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92747
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The generic builtins don't care about -fnon-call-exceptions though (e.g. sin is
nothrow even with -fnon-call-exceptions), so for the start we might just use
nothrow/leaf for all x86 backend builtins for start. Though, eventually say
builtins that store something into memory (or load from memory) or might be
trapping should probably not be nothrow, though -fnon-call-exceptions is
Optimization flag and thus can differ between functions, so e.g. deciding based
on the global flag_non_call_exceptions during construction of the builtin is
problematic.
>From gcc-bugs-return-661998-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 12:54:22 2019
Return-Path: <gcc-bugs-return-661998-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61394 invoked by alias); 2 Dec 2019 12:54:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61318 invoked by uid 48); 2 Dec 2019 12:54:18 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/68230] Unused function parameters not reported by -Wunused-parameter when only used recursively (add -Wparameter-only-used-recursively instead?)
Date: Mon, 02 Dec 2019 12:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-68230-4-PVD5XyBUk1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68230-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68230-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00068.txt.bz2
Content-length: 1199
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68230
--- Comment #12 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #10)
> Martin Jambor's IPA-SRA rewrite might be relevant here; it sounded like the
> new IPA-SRA will remove parameters that are unused like this, but I didn't
> quite catch if it'd also warn about them...
IPA-SRA can remove parameters that are only used to be passed to
another function in a chain of recursive calls, it does not even have
to be a direct recursion (but it can). It does not warn but it could.
One problem is however that IPA-SRA only modifies and analyzes "local"
functions, so in non-LTO mode it only works if all of the recursive
functions were static or in an anonymous C++ namespace. With LTO,
anything not exported outside the result executable/shared object
would do but you'd only get your warnings at link-time.
Please also note that with this particular testcase, by the time IPA
passes see the function the recursion is converted to tail-call and
since IPA-CP (running just before IPA-SRA) can also remove totally
unused parameters, IPA-SRA does not do anything in this case even with
-fwhole-program.
>From gcc-bugs-return-661999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 13:08:40 2019
Return-Path: <gcc-bugs-return-661999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46216 invoked by alias); 2 Dec 2019 13:08:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45988 invoked by uid 48); 2 Dec 2019 13:08:31 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Mon, 02 Dec 2019 13:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92738-4-yGxixeVqn2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00069.txt.bz2
Content-length: 481
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
So wrf grew starting with r271377, size (w/o debug info) goes from 20164464B to
23674792.
>From gcc-bugs-return-662000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 13:39:02 2019
Return-Path: <gcc-bugs-return-662000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47132 invoked by alias); 2 Dec 2019 13:39:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47069 invoked by uid 48); 2 Dec 2019 13:38:57 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Mon, 02 Dec 2019 13:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92738-4-hvHW4ezFR4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00070.txt.bz2
Content-length: 608
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
Wilco <wilco at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilco at gcc dot gnu.org
--- Comment #7 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #6)
> So wrf grew starting with r271377, size (w/o debug info) goes from 20164464B
> to 23674792.
Also check the build time of wrf. Looking at my logs trunk takes 2x as long to
build it since June.
>From gcc-bugs-return-662001-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 13:55:33 2019
Return-Path: <gcc-bugs-return-662001-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70370 invoked by alias); 2 Dec 2019 13:55:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70316 invoked by uid 48); 2 Dec 2019 13:55:28 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Mon, 02 Dec 2019 13:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92738-4-Crgk5zYOy3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00071.txt.bz2
Content-length: 495
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Wilco from comment #7)
> (In reply to Martin Liška from comment #6)
> > So wrf grew starting with r271377, size (w/o debug info) goes from 20164464B
> > to 23674792.
>
> Also check the build time of wrf. Looking at my logs trunk takes 2x as long
> to build it since June.
Maybe related to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91509
?
>From gcc-bugs-return-662002-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 13:56:57 2019
Return-Path: <gcc-bugs-return-662002-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72459 invoked by alias); 2 Dec 2019 13:56:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72399 invoked by uid 55); 2 Dec 2019 13:56:53 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92747] x86 vector builtins throw exceptions
Date: Mon, 02 Dec 2019 13:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92747-4-69VcFg34OD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00072.txt.bz2
Content-length: 1380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92747
--- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 2 Dec 2019, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92747
>
> Jakub Jelinek <jakub at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |jakub at gcc dot gnu.org
>
> --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> The generic builtins don't care about -fnon-call-exceptions though (e.g. sin is
> nothrow even with -fnon-call-exceptions), so for the start we might just use
> nothrow/leaf for all x86 backend builtins for start. Though, eventually say
> builtins that store something into memory (or load from memory) or might be
> trapping should probably not be nothrow, though -fnon-call-exceptions is
> Optimization flag and thus can differ between functions, so e.g. deciding based
> on the global flag_non_call_exceptions during construction of the builtin is
> problematic.
One trick would be to keep the default conservative and in
ix86_gimple_fold_builtin adjust the behavior per call via
gimple_call_set_nothrow. That would happen in the gimple lowering
pass (before EH/CFG build).
>From gcc-bugs-return-662003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 14:06:43 2019
Return-Path: <gcc-bugs-return-662003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122472 invoked by alias); 2 Dec 2019 14:06:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122450 invoked by uid 48); 2 Dec 2019 14:06:39 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92746] [10 Regression] ICE in check_noexcept_r, at cp/except.c:1114
Date: Mon, 02 Dec 2019 14:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92746-4-goWRXzk8la@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00073.txt.bz2
Content-length: 561
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92746
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-02
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-662004-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 14:08:10 2019
Return-Path: <gcc-bugs-return-662004-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124364 invoked by alias); 2 Dec 2019 14:08:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124292 invoked by uid 48); 2 Dec 2019 14:08:07 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92747] x86 vector builtins throw exceptions
Date: Mon, 02 Dec 2019 14:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92747-4-jUGQqbVw7f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00074.txt.bz2
Content-length: 622
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92747
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Or add an attribute that would work as nothrow if called from
-fno-non-call-exceptions and as nothing otherwise.
Though, e.g. for C++ sin in the library is really marked throw () rather than
using nothrow attribute, so it couldn't be changed easily to some new
attribute.
It makes no sense to invent something x86 specific until the generic builtins
stuff is resolved, and whether it should be resolved or not depends on what the
Ada/Go folks or whomever uses -fnon-call-exceptions actually need.
>From gcc-bugs-return-662005-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 14:11:09 2019
Return-Path: <gcc-bugs-return-662005-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1800 invoked by alias); 2 Dec 2019 14:11:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1772 invoked by uid 48); 2 Dec 2019 14:11:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92734] Missing match.pd simplification done by fold_binary_loc on generic
Date: Mon, 02 Dec 2019 14:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: easyhack, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92734-4-MrN8Wgic9d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00075.txt.bz2
Content-length: 302
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92734
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The (A +- CST1) +- CST2 -> A + CST3 pattern already does handle casts it seems,
it is just the other two that don't.
That has been added in r249447 with a follow-up fix in r257683.
>From gcc-bugs-return-662006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 14:13:06 2019
Return-Path: <gcc-bugs-return-662006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3509 invoked by alias); 2 Dec 2019 14:13:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3473 invoked by uid 48); 2 Dec 2019 14:13:02 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92326] wrong bound in zero-length array diagnostics
Date: Mon, 02 Dec 2019 14:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: trivial
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92326-4-ya0IWDwOJX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92326-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92326-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00076.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92326
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Just for the record, I see the failure in grub2 package.
>From gcc-bugs-return-662007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 14:23:52 2019
Return-Path: <gcc-bugs-return-662007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24443 invoked by alias); 2 Dec 2019 14:23:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24141 invoked by uid 48); 2 Dec 2019 14:23:47 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBpcGEvOTI3NDldIE5ldzogd2FybmluZzogaW5saW5pbmcgZmFpbGVk?= =?UTF-8?B?IGluIGNhbGwgdG8g4oCYc2Fsc2EyMOKAmTogLS1wYXJhbSBtYXgtaW5saW5l?= =?UTF-8?B?LWluc25zLXNpbmdsZSBsaW1pdCByZWFjaGVkIGFmdGVyIHIyNzY1MTY=?Date: Mon, 02 Dec 2019 14:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone attachments.created
Message-ID: <bug-92749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00077.txt.bz2
Content-length: 2735
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92749
Bug ID: 92749
Summary: warning: inlining failed in call to ‘salsa20’: --param
max-inline-insns-single limit reached after r276516
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Created attachment 47403
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47403&action=edit
test-case
The test-case is reduced from libxcrypt package, starting from the revision I
see:
$ gcc -m32 -O2 -Winline -c xcrypt.i -Werror
alg-yescrypt-opt.c: In function ‘blockmix_salsa8’:
alg-yescrypt-opt.c:280:20: error: inlining failed in call to ‘salsa20’: --param
max-inline-insns-single limit reached [-Werror=inline]
alg-yescrypt-opt.c:383:364: note: called from here
alg-yescrypt-opt.c:280:20: error: inlining failed in call to ‘salsa20’: --param
max-inline-insns-single limit reached [-Werror=inline]
alg-yescrypt-opt.c:382:332: note: called from here
alg-yescrypt-opt.c: In function ‘blockmix_salsa8_xor’:
alg-yescrypt-opt.c:280:20: error: inlining failed in call to ‘salsa20’: --param
max-inline-insns-single limit reached [-Werror=inline]
alg-yescrypt-opt.c:408:372: note: called from here
alg-yescrypt-opt.c:280:20: error: inlining failed in call to ‘salsa20’: --param
max-inline-insns-single limit reached [-Werror=inline]
alg-yescrypt-opt.c:406:340: note: called from here
alg-yescrypt-opt.c: In function ‘blockmix’:
alg-yescrypt-opt.c:280:20: error: inlining failed in call to ‘salsa20’: --param
max-inline-insns-single limit reached [-Werror=inline]
alg-yescrypt-opt.c:674:2: note: called from here
alg-yescrypt-opt.c: In function ‘blockmix_xor_save’:
alg-yescrypt-opt.c:280:20: error: inlining failed in call to ‘salsa20’: --param
max-inline-insns-single limit reached [-Werror=inline]
alg-yescrypt-opt.c:784:2: note: called from here
alg-yescrypt-opt.c: In function ‘blockmix_xor.constprop’:
alg-yescrypt-opt.c:280:20: error: inlining failed in call to ‘salsa20’: --param
max-inline-insns-single limit reached [-Werror=inline]
alg-yescrypt-opt.c:733:2: note: called from here
@Honza: Can you please check that it's not a regression after the revision?
I need to tweak --param max-inline-insns-single to 110 to make it happy.
>From gcc-bugs-return-662008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 14:25:02 2019
Return-Path: <gcc-bugs-return-662008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29585 invoked by alias); 2 Dec 2019 14:25:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29295 invoked by uid 48); 2 Dec 2019 14:24:59 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBpcGEvOTI3NDldIHdhcm5pbmc6IGlubGluaW5nIGZhaWxlZCBpbiBj?= =?UTF-8?B?YWxsIHRvIOKAmHNhbHNhMjDigJk6IC0tcGFyYW0gbWF4LWlubGluZS1pbnNu?= =?UTF-8?B?cy1zaW5nbGUgbGltaXQgcmVhY2hlZCBhZnRlciByMjc2NTE2?Date: Mon, 02 Dec 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on cc cf_known_to_work target_milestone cf_known_to_fail
Message-ID: <bug-92749-4-PlVtTJccnT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00078.txt.bz2
Content-length: 540
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92749
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2019-12-2
CC| |hubicka at gcc dot gnu.org
Known to work| |9.2.0
Target Milestone|--- |10.0
Known to fail| |10.0
>From gcc-bugs-return-662009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 15:11:40 2019
Return-Path: <gcc-bugs-return-662009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72294 invoked by alias); 2 Dec 2019 15:11:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72199 invoked by uid 48); 2 Dec 2019 15:11:36 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Mon, 02 Dec 2019 15:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92738-4-Z1RQD93053@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00079.txt.bz2
Content-length: 649
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
--- Comment #9 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #8)
> (In reply to Wilco from comment #7)
> > (In reply to Martin Liška from comment #6)
> > > So wrf grew starting with r271377, size (w/o debug info) goes from 20164464B
> > > to 23674792.
> >
> > Also check the build time of wrf. Looking at my logs trunk takes 2x as long
> > to build it since June.
>
> Maybe related to:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91509
> ?
I think not, this is plain -Ofast, no LTO or prefetching. The same slowdown
happens with -O2.
>From gcc-bugs-return-662010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 15:16:27 2019
Return-Path: <gcc-bugs-return-662010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77649 invoked by alias); 2 Dec 2019 15:16:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77609 invoked by uid 48); 2 Dec 2019 15:16:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92750] New: DSE fails to remove all dead clobbers
Date: Mon, 02 Dec 2019 15:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00080.txt.bz2
Content-length: 1471
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92750
Bug ID: 92750
Summary: DSE fails to remove all dead clobbers
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
In PR92645 I see DSE1 doing
MEM[(struct Vec *)&s] = _74;
MEM[(struct Vec *)&a] ={v} {CLOBBER};
- MEM[(struct Vec *)&a] ={v} {CLOBBER};
- MEM[(struct Vec *)&a] ={v} {CLOBBER};
- MEM[(struct Vec *)&a] ={v} {CLOBBER};
- MEM[(struct Vec *)&a] ={v} {CLOBBER};
_73 = (unsigned char) invA_8;
MEM[(struct Vec *)&a].val = _73;
MEM[(struct Vec *)&a + 1B] ={v} {CLOBBER};
MEM[(struct Vec *)&a + 1B].val = _73;
MEM[(struct Vec *)&a + 2B] ={v} {CLOBBER};
- MEM[(struct Vec *)&a + 2B] ={v} {CLOBBER};
MEM[(struct Vec *)&a + 2B].val = _73;
MEM[(struct Vec *)&a + 3B] ={v} {CLOBBER};
MEM[(struct Vec *)&a + 3B].val = _73;
MEM[(struct Vec *)&a + 4B] ={v} {CLOBBER};
- MEM[(struct Vec *)&a + 4B] ={v} {CLOBBER};
- MEM[(struct Vec *)&a + 4B] ={v} {CLOBBER};
MEM[(struct Vec *)&a + 4B].val = _73;
MEM[(struct Vec *)&a + 5B] ={v} {CLOBBER};
...
as you can see it removes all but one clobber but there's still a real must-def
that should make the last clobber dead as well.
>From gcc-bugs-return-662011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 15:17:50 2019
Return-Path: <gcc-bugs-return-662011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129727 invoked by alias); 2 Dec 2019 15:17:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129714 invoked by uid 48); 2 Dec 2019 15:17:45 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92751] New: VN partial def support confused about clobbers
Date: Mon, 02 Dec 2019 15:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00081.txt.bz2
Content-length: 956
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92751
Bug ID: 92751
Summary: VN partial def support confused about clobbers
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
FRE doesn't optimize
MEM[(struct Vec *)&D.195309] ={v} {CLOBBER};
MEM[(struct Vec *)&D.195309].val = 128;
MEM[(struct Vec *)&D.195309 + 2B] ={v} {CLOBBER};
MEM[(struct Vec *)&D.195309 + 2B].val = 128;
...
MEM[(struct Vec *)&D.195309 + 28B].val = 128;
MEM[(struct Vec *)&D.195309 + 30B] ={v} {CLOBBER};
MEM[(struct Vec *)&D.195309 + 30B].val = 128;
_127 = MEM <vector(16) short unsigned int> [(char * {ref-all})&D.195309];
to a vector constant because it's confused by the CLOBBERs.
>From gcc-bugs-return-662012-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 15:18:07 2019
Return-Path: <gcc-bugs-return-662012-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130558 invoked by alias); 2 Dec 2019 15:18:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130506 invoked by uid 48); 2 Dec 2019 15:18:02 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92751] VN partial def support confused about clobbers
Date: Mon, 02 Dec 2019 15:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on blocked assigned_to everconfirmed
Message-ID: <bug-92751-4-mYsWN44X6E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00082.txt.bz2
Content-length: 866
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92751
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-02
Blocks| |92645
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mine.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
[Bug 92645] Hand written vector code is 450 times slower when compiled with GCC
compared to Clang
>From gcc-bugs-return-662013-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 15:34:23 2019
Return-Path: <gcc-bugs-return-662013-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14243 invoked by alias); 2 Dec 2019 15:34:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14210 invoked by uid 48); 2 Dec 2019 15:34:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92734] Missing match.pd simplification done by fold_binary_loc on generic
Date: Mon, 02 Dec 2019 15:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: easyhack, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed attachments.created
Message-ID: <bug-92734-4-qrv4rFQmC3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00083.txt.bz2
Content-length: 690
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92734
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-02
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47404
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47404&action=edit
gcc10-pr92734.patch
Untested fix.
>From gcc-bugs-return-662014-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 15:38:50 2019
Return-Path: <gcc-bugs-return-662014-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34299 invoked by alias); 2 Dec 2019 15:38:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34254 invoked by uid 48); 2 Dec 2019 15:38:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92750] DSE fails to remove all dead clobbers
Date: Mon, 02 Dec 2019 15:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92750-4-t7nW1VptKo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00084.txt.bz2
Content-length: 817
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92750
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I believe even when the whole object that is clobbered is overwritten right
after it, the clobber is still useful, as it holds information in the IL that
the old value is gone and there is a new value. E.g. if address of the var is
taken before the clobber, then there is clobber and then the whole object is
overwritten with another value, but nothing takes the address afterwards, e.g.
the tail-call optimization could be applied.
>From gcc-bugs-return-662015-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 15:43:30 2019
Return-Path: <gcc-bugs-return-662015-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47154 invoked by alias); 2 Dec 2019 15:43:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47128 invoked by uid 48); 2 Dec 2019 15:43:26 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92682] [10 Regression] maxlocval_4.f90 / minlocval_4.f90 failure on POWER9
Date: Mon, 02 Dec 2019 15:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92682-4-bQb9Q2VJYG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00085.txt.bz2
Content-length: 296
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92682
--- Comment #2 from seurer at gcc dot gnu.org ---
Looking through all the tester logs I see a handful of failures on power 7, 8,
and 9 in late October/early November but none since so if there was a problem
it appears to have cleared up.
>From gcc-bugs-return-662016-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 15:47:17 2019
Return-Path: <gcc-bugs-return-662016-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42036 invoked by alias); 2 Dec 2019 15:47:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36374 invoked by uid 48); 2 Dec 2019 15:47:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92745] [8/9/10 Regression] Initializing array with vec4 results in compile error
Date: Mon, 02 Dec 2019 15:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92745-4-wELPbUsY0S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00086.txt.bz2
Content-length: 470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92745
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r268428 on the trunk and likely with r268555 on the 8 branch.
Let me reduce it.
>From gcc-bugs-return-662017-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 15:57:54 2019
Return-Path: <gcc-bugs-return-662017-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49980 invoked by alias); 2 Dec 2019 15:57:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49928 invoked by uid 48); 2 Dec 2019 15:57:50 -0000
From: "Casey at Carter dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82380] [concepts] Error when using requires constraint with attributes
Date: Mon, 02 Dec 2019 15:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Casey at Carter dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-82380-4-T6TrZhi8I6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82380-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82380-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00087.txt.bz2
Content-length: 712
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82380
Casey Carter <Casey at Carter dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cjdb.ns at gmail dot com
--- Comment #6 from Casey Carter <Casey at Carter dot net> ---
(In reply to Jonathan Wakely from comment #5)
> I tested it with "concept" not "concept bool" i.e.
>
> template <class T>
> concept C = true;
>
> template <class T>
> requires C<T>
> [[nodiscard]] int f(T t) {
> return 22;
> }
>
> int main() {
> return 0;
> }
This seems to have regressed (https://godbolt.org/z/SmPx-y).
>From gcc-bugs-return-662018-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 15:58:03 2019
Return-Path: <gcc-bugs-return-662018-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50756 invoked by alias); 2 Dec 2019 15:58:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50613 invoked by uid 48); 2 Dec 2019 15:57:59 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92745] [8/9/10 Regression] Initializing array with vec4 results in compile error
Date: Mon, 02 Dec 2019 15:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92745-4-CzdX4ui7Bd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00088.txt.bz2
Content-length: 400
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92745
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Mine then :-(
>From gcc-bugs-return-662019-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:01:52 2019
Return-Path: <gcc-bugs-return-662019-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66613 invoked by alias); 2 Dec 2019 16:01:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66551 invoked by uid 48); 2 Dec 2019 16:01:48 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92745] [8/9/10 Regression] Initializing array with vec4 results in compile error
Date: Mon, 02 Dec 2019 16:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92745-4-TIKwiyu80I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00089.txt.bz2
Content-length: 496
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92745
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
creduce gives:
template <typename a, int b> struct c { typedef a d[b]; };
template <typename a, int b> struct h { typename c<a, b>::d e; };
template <class f> using g __attribute__((vector_size(sizeof(f)))) = float;
void i() { h<g<float>, 4>{g<float>{}, {}}; }
as something that used to be accepted and is rejected afterwards. Not sure if
that error isn't valid though.
>From gcc-bugs-return-662020-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:09:34 2019
Return-Path: <gcc-bugs-return-662020-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84063 invoked by alias); 2 Dec 2019 16:09:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83991 invoked by uid 48); 2 Dec 2019 16:09:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92745] [8/9/10 Regression] Initializing array with vec4 results in compile error
Date: Mon, 02 Dec 2019 16:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92745-4-6YJF03RAkt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00090.txt.bz2
Content-length: 730
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92745
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Better testcase:
template <typename a, int b> struct c { typedef a d[b]; };
template <typename a, int b> struct array {
typename c<a, b>::d e;
a operator[](long);
};
template<class T>
using vec4_t __attribute__((vector_size(4*sizeof(T)))) = float;
auto transpose(array<vec4_t<float>, 4> col)
{
array<vec4_t<float>, 4>
ret{vec4_t<float>{col[0][0], col[1][0], col[2][0], col[3][0]},
vec4_t<float>{col[0][1], col[1][1], col[2][1], col[3][1]},
vec4_t<float>{col[0][2], col[1][2], col[2][2], col[3][2]},
vec4_t<float>{col[0][3], col[1][3], col[2][3], col[3][3]}};
return ret;
}
>From gcc-bugs-return-662021-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:11:28 2019
Return-Path: <gcc-bugs-return-662021-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126599 invoked by alias); 2 Dec 2019 16:11:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125843 invoked by uid 48); 2 Dec 2019 16:11:23 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92718] [8/9/10 Regression] Bogus Wstringop-overflow in __builtin_memset() of an element of array of size 1 of struct
Date: Mon, 02 Dec 2019 16:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92718-4-qzXlM2YiuD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92718-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92718-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00091.txt.bz2
Content-length: 375
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92718
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Modifying const members of a struct is undefined, regardless of how it's done:
either by assignment or by overwriting it using memset. GCC doesn't diagnose
it yet but I expect it will, maybe as early as in GCC 11, similarly to how G++
diagnoses it.
>From gcc-bugs-return-662022-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:18:42 2019
Return-Path: <gcc-bugs-return-662022-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42394 invoked by alias); 2 Dec 2019 16:18:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42336 invoked by uid 48); 2 Dec 2019 16:18:38 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92712] [8/9 Regression] Performance regression with assumed values
Date: Mon, 02 Dec 2019 16:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-92712-4-hAwotp5k8A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00092.txt.bz2
Content-length: 603
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92712
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[8/9/10 Regression] |[8/9 Regression]
|Performance regression with |Performance regression with
|assumed values |assumed values
--- Comment #22 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Should be fixed on the trunk.
I don't think we want to backport to release branches though.
>From gcc-bugs-return-662025-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:23:49 2019
Return-Path: <gcc-bugs-return-662025-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52635 invoked by alias); 2 Dec 2019 16:23:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51830 invoked by uid 55); 2 Dec 2019 16:23:43 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/78237] std::timed_mutex::try_lock_for/until affected by system realtime clock
Date: Mon, 02 Dec 2019 16:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.2.1
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mac at mcrowe dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-78237-4-q7eqpKXtMD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78237-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78237-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00095.txt.bz2
Content-length: 3306
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78237
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Dec 2 16:23:10 2019
New Revision: 278903
URL: https://gcc.gnu.org/viewcvs?rev=278903&root=gcc&view=rev
Log:
libstdc++: Add full steady_clock support to shared_timed_mutex
The pthread_rwlock_clockrdlock and pthread_rwlock_clockwrlock functions
were added to glibc in v2.30. They have also been added to Android
Bionic. If these functions are available in the C library then they can
be used to implement shared_timed_mutex::try_lock_until,
shared_timed_mutex::try_lock_for,
shared_timed_mutex::try_lock_shared_until and
shared_timed_mutex::try_lock_shared_for so that they are no longer
unaffected by the system clock being warped. (This is the shared_mutex
equivalent of PR libstdc++/78237 for mutex.)
If the new functions are available then steady_clock is deemed to be the
"best" clock available which means that it is used for the relative
try_lock_for calls and absolute try_lock_until calls using steady_clock
and user-defined clocks. It's not possible to have
_GLIBCXX_USE_PTHREAD_RWLOCK_CLOCKLOCK defined without
_GLIBCXX_USE_PTHREAD_RWLOCK_T, so the requirement that the clock be the
same as condition_variable is maintained. Calls explicitly using
system_clock (aka high_resolution_clock) continue to use CLOCK_REALTIME
via the old pthread_rwlock_timedrdlock and pthread_rwlock_timedwrlock
functions.
If the new functions are not available then system_clock is deemed to be
the "best" clock available which means that the previous suboptimal
behaviour remains.
Additionally, the user-defined clock used with
shared_timed_mutex::try_lock_for and shared_mutex::try_lock_shared_for
may have higher precision than __clock_t. We may need to round the
duration up to ensure that the timeout is long enough. (See
__timed_mutex_impl::_M_try_lock_for)
2019-12-02 Mike Crowe <mac@mcrowe.com>
Add full steady_clock support to shared_timed_mutex
* acinclude.m4 (GLIBCXX_CHECK_PTHREAD_RWLOCK_CLOCKLOCK): Define
to check for the presence of both pthread_rwlock_clockrdlock and
pthread_rwlock_clockwrlock.
* config.h.in: Regenerate.
* configure.ac: Call GLIBCXX_USE_PTHREAD_RWLOCK_CLOCKLOCK.
* configure: Regenerate.
* include/std/shared_mutex (shared_timed_mutex): Define __clock_t as
the best clock to use for relative waits.
(shared_timed_mutex::try_lock_for) Round up wait duration if necessary.
(shared_timed_mutex::try_lock_shared_for): Likewise.
(shared_timed_mutex::try_lock_until): Use existing try_lock_until
implementation for system_clock (which matches __clock_t when
_GLIBCCXX_USE_PTHREAD_RWLOCK_CLOCKLOCK is not defined). Add new
overload for steady_clock that uses pthread_rwlock_clockwrlock if it
is available. Simplify overload for non-standard clock to just call
try_lock_for with a relative timeout.
(shared_timed_mutex::try_lock_shared_until): Likewise.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/acinclude.m4
trunk/libstdc++-v3/config.h.in
trunk/libstdc++-v3/configure
trunk/libstdc++-v3/configure.ac
trunk/libstdc++-v3/include/std/shared_mutex
>From gcc-bugs-return-662023-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:23:41 2019
Return-Path: <gcc-bugs-return-662023-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51566 invoked by alias); 2 Dec 2019 16:23:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51360 invoked by uid 55); 2 Dec 2019 16:23:33 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/78237] std::timed_mutex::try_lock_for/until affected by system realtime clock
Date: Mon, 02 Dec 2019 16:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.2.1
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mac at mcrowe dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-78237-4-LSJriA78L8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78237-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78237-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00093.txt.bz2
Content-length: 2592
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78237
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Dec 2 16:23:01 2019
New Revision: 278901
URL: https://gcc.gnu.org/viewcvs?rev=278901&root=gcc&view=rev
Log:
libstdc++: PR 78237 Add full steady_clock support to timed_mutex
The pthread_mutex_clocklock function is available in glibc since the
2.30 release. If this function is available in the C library it can be
used to fix PR libstdc++/78237 by supporting steady_clock properly with
timed_mutex.
This means that code using timed_mutex::try_lock_for or
timed_mutex::wait_until with steady_clock is no longer subject to timing
out early or potentially waiting for much longer if the system clock is
warped at an inopportune moment.
If pthread_mutex_clocklock is available then steady_clock is deemed to
be the "best" clock available which means that it is used for the
relative try_lock_for calls and absolute try_lock_until calls using
steady_clock and user-defined clocks. Calls explicitly using
system_clock (aka high_resolution_clock) continue to use CLOCK_REALTIME
via __gthread_cond_timedwait.
If pthread_mutex_clocklock is not available then system_clock is deemed
to be the "best" clock available which means that the previous
suboptimal behaviour remains.
2019-12-02 Mike Crowe <mac@mcrowe.com>
PR libstdc++/78237 Add full steady_clock support to timed_mutex
* acinclude.m4 (GLIBCXX_CHECK_PTHREAD_MUTEX_CLOCKLOCK): Define to
detect presence of pthread_mutex_clocklock function.
* config.h.in: Regenerate.
* configure: Regenerate.
* configure.ac: Call GLIBCXX_CHECK_PTHREAD_MUTEX_CLOCKLOCK.
* include/std/mutex (__timed_mutex_impl): Remove unnecessary __clock_t.
(__timed_mutex_impl::_M_try_lock_for): Use best clock to turn relative
timeout into absolute timeout.
(__timed_mutex_impl::_M_try_lock_until): Keep existing implementation
for system_clock. Add new implementation for steady_clock that calls
_M_clocklock. Modify overload for user-defined clock to use a relative
wait so that it automatically uses the best clock.
[_GLIBCXX_USE_PTHREAD_MUTEX_CLOCKLOCK] (timed_mutex::_M_clocklock):
New member function.
(recursive_timed_mutex::_M_clocklock): Likewise.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/acinclude.m4
trunk/libstdc++-v3/config.h.in
trunk/libstdc++-v3/configure
trunk/libstdc++-v3/configure.ac
trunk/libstdc++-v3/include/std/mutex
>From gcc-bugs-return-662024-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:23:43 2019
Return-Path: <gcc-bugs-return-662024-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51799 invoked by alias); 2 Dec 2019 16:23:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51496 invoked by uid 55); 2 Dec 2019 16:23:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/91906] std::timed_mutex::try_lock_until may not wait for timeout to expire when called with user-defined clock
Date: Mon, 02 Dec 2019 16:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mac at mcrowe dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91906-4-50FitVejVp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91906-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00094.txt.bz2
Content-length: 2635
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91906
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Dec 2 16:23:06 2019
New Revision: 278902
URL: https://gcc.gnu.org/viewcvs?rev=278902&root=gcc&view=rev
Log:
libstdc++: Fix timed_mutex::try_lock_until on arbitrary clock (PR 91906)
A non-standard clock may tick more slowly than
std::chrono::steady_clock. This means that we risk returning false
early when the specified timeout may not have expired. This can be
avoided by looping until the timeout time as reported by the
non-standard clock has been reached.
Unfortunately, we have no way to tell whether the non-standard clock
ticks more quickly that std::chrono::steady_clock. If it does then we
risk returning later than would be expected, but that is unavoidable and
permitted by the standard.
2019-12-02 Mike Crowe <mac@mcrowe.com>
PR libstdc++/91906 Fix timed_mutex::try_lock_until on arbitrary clock
* include/std/mutex (__timed_mutex_impl::_M_try_lock_until): Loop
until the absolute timeout time is reached as measured against the
appropriate clock.
* testsuite/util/slow_clock.h: New file. Move implementation of
slow_clock test class.
* testsuite/30_threads/condition_variable/members/2.cc: Include
slow_clock from header.
* testsuite/30_threads/shared_timed_mutex/try_lock/3.cc: Convert
existing test to templated function so that it can be called with
both system_clock and steady_clock.
* testsuite/30_threads/timed_mutex/try_lock_until/3.cc: Also run test
using slow_clock to test above fix.
* testsuite/30_threads/recursive_timed_mutex/try_lock_until/3.cc:
Likewise.
* testsuite/30_threads/recursive_timed_mutex/try_lock_until/4.cc: Add
new test that try_lock_until behaves as try_lock if the timeout has
already expired or exactly matches the current time.
Added:
trunk/libstdc++-v3/testsuite/30_threads/timed_mutex/try_lock_until/4.cc
- copied, changed from r278901,
trunk/libstdc++-v3/testsuite/30_threads/timed_mutex/try_lock_until/3.cc
trunk/libstdc++-v3/testsuite/util/slow_clock.h
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/std/mutex
trunk/libstdc++-v3/testsuite/30_threads/condition_variable/members/2.cc
trunk/libstdc++-v3/testsuite/30_threads/recursive_timed_mutex/try_lock_until/3.cc
trunk/libstdc++-v3/testsuite/30_threads/shared_timed_mutex/try_lock/3.cc
trunk/libstdc++-v3/testsuite/30_threads/timed_mutex/try_lock_until/3.cc
>From gcc-bugs-return-662026-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:23:56 2019
Return-Path: <gcc-bugs-return-662026-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53459 invoked by alias); 2 Dec 2019 16:23:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52724 invoked by uid 55); 2 Dec 2019 16:23:50 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/91906] std::timed_mutex::try_lock_until may not wait for timeout to expire when called with user-defined clock
Date: Mon, 02 Dec 2019 16:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mac at mcrowe dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91906-4-9ceuT4Tggd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91906-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00096.txt.bz2
Content-length: 2036
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91906
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Dec 2 16:23:14 2019
New Revision: 278904
URL: https://gcc.gnu.org/viewcvs?rev=278904&root=gcc&view=rev
Log:
libstdc++: Fix try_lock_until and try_lock_shared_until on arbitrary clock
This is the equivalent to PR libstdc++/91906, but for shared_mutex.
A non-standard clock may tick more slowly than std::chrono::steady_clock.
This means that we risk returning false early when the specified timeout
may not have expired. This can be avoided by looping until the timeout time
as reported by the non-standard clock has been reached.
Unfortunately, we have no way to tell whether the non-standard clock ticks
more quickly that std::chrono::steady_clock. If it does then we risk
returning later than would be expected, but that is unavoidable without
waking up periodically to check, which would be rather too expensive.
François Dumont pointed out[1] a flaw in an earlier version of this patch
that revealed a hole in the test coverage, so I've added a new test that
try_lock_until acts as try_lock if the timeout has already expired.
[1] https://gcc.gnu.org/ml/libstdc++/2019-10/msg00021.html
2019-12-02 Mike Crowe <mac@mcrowe.com>
Fix try_lock_until and try_lock_shared_until on arbitrary clock
* include/std/shared_mutex (shared_timed_mutex::try_lock_until)
(shared_timed_mutex::try_lock_shared_until): Loop until the absolute
timeout time is reached as measured against the appropriate clock.
* testsuite/30_threads/shared_timed_mutex/try_lock_until/1.cc: New
file. Test try_lock_until and try_lock_shared_until timeouts against
various clocks.
* testsuite/30_threads/shared_timed_mutex/try_lock_until/1.cc: New
file. Test try_lock_until and try_lock_shared_until timeouts against
various clocks.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/std/shared_mutex
>From gcc-bugs-return-662028-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:50:36 2019
Return-Path: <gcc-bugs-return-662028-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43179 invoked by alias); 2 Dec 2019 16:50:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43067 invoked by uid 48); 2 Dec 2019 16:50:31 -0000
From: "cjdb.ns at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82380] [concepts] Error when using requires constraint with attributes
Date: Mon, 02 Dec 2019 16:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cjdb.ns at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82380-4-5tp48VbF5x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82380-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82380-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00098.txt.bz2
Content-length: 188
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82380
--- Comment #7 from Christopher Di Bella <cjdb.ns at gmail dot com> ---
*** Bug 92739 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-662027-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:50:36 2019
Return-Path: <gcc-bugs-return-662027-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43176 invoked by alias); 2 Dec 2019 16:50:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43047 invoked by uid 48); 2 Dec 2019 16:50:30 -0000
From: "cjdb.ns at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92739] [10 Regression] Requires clause followed by an attribute no longer compiles
Date: Mon, 02 Dec 2019 16:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cjdb.ns at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92739-4-DnVbYxOUiX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00097.txt.bz2
Content-length: 537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92739
Christopher Di Bella <cjdb.ns at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Christopher Di Bella <cjdb.ns at gmail dot com> ---
This appears to be a duplicate of 82380.
*** This bug has been marked as a duplicate of bug 82380 ***
>From gcc-bugs-return-662029-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:52:11 2019
Return-Path: <gcc-bugs-return-662029-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45473 invoked by alias); 2 Dec 2019 16:52:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45390 invoked by uid 48); 2 Dec 2019 16:52:07 -0000
From: "cjdb.ns at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82380] [concepts] Error when using requires constraint with attributes
Date: Mon, 02 Dec 2019 16:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cjdb.ns at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82380-4-PHEKTFU6nJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82380-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82380-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00099.txt.bz2
Content-length: 256
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82380
--- Comment #8 from Christopher Di Bella <cjdb.ns at gmail dot com> ---
The above (presumably) works in 466691493b9, but not in commits starting from
Git hash 6b42dfe4264.
Bugzilla autolink: r278774
>From gcc-bugs-return-662030-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:55:39 2019
Return-Path: <gcc-bugs-return-662030-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103267 invoked by alias); 2 Dec 2019 16:55:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103233 invoked by uid 48); 2 Dec 2019 16:55:36 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/78237] std::timed_mutex::try_lock_for/until affected by system realtime clock
Date: Mon, 02 Dec 2019 16:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.2.1
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mac at mcrowe dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-78237-4-tCFhW9RnGl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78237-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78237-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00100.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78237
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for GCC 10.
>From gcc-bugs-return-662031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 16:56:05 2019
Return-Path: <gcc-bugs-return-662031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104153 invoked by alias); 2 Dec 2019 16:56:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104095 invoked by uid 48); 2 Dec 2019 16:56:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/91906] std::timed_mutex::try_lock_until may not wait for timeout to expire when called with user-defined clock
Date: Mon, 02 Dec 2019 16:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mac at mcrowe dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91906-4-K7ZRosv24d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91906-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00101.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91906
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for GCC 10.
>From gcc-bugs-return-662032-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 17:02:17 2019
Return-Path: <gcc-bugs-return-662032-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17126 invoked by alias); 2 Dec 2019 17:02:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16982 invoked by uid 48); 2 Dec 2019 17:02:13 -0000
From: "alisdairm at me dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92752] New: Bogus "ignored qualifiers" warning on const-qualified pointer-to-member-function objects
Date: Mon, 02 Dec 2019 17:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: alisdairm at me dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92752-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00102.txt.bz2
Content-length: 1761
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92752
Bug ID: 92752
Summary: Bogus "ignored qualifiers" warning on const-qualified
pointer-to-member-function objects
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: alisdairm at me dot com
Target Milestone: ---
We are seeing a bogus warning on the default constructor for a class template
that wraps a data member of the template parameter type, when that template
parameter is a const-qualified pointer-to-member-function type (note, the
pointer-to-member function type is cv-qualified, not the member function that
is pointed to). This comes up in our own library implementation for a
pair-like type used for our associative containers (pair<const Key, Value>)
Example code, should be compiled with -Wextra to show the warning:
struct X {};
using MemFn = int (X::*)();
template <class T>
struct Wrap {
T data;
Wrap() : data() {}
};
int main() {
Wrap<MemFn const> x;
}
Compiler output:
In instantiation of 'Wrap<T>::Wrap() [with T = int (X::* const)()]':
13:23: required from here
9:29: warning: type qualifiers ignored on cast result type
[-Wignored-qualifiers]
9 | Wrap() : data() {}
| ^
Compiler returned: 0
As far as we can tell, this applies only to pointer-to-member-function types,
not regular function pointers, not pointer-to-data-member, nor any other scalar
type.
Checking past compilers with the Godbolt compiler explorer, this warning seems
to first appear in gcc 8.1:
https://godbolt.org/z/8Mxpsm
>From gcc-bugs-return-662033-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 17:30:26 2019
Return-Path: <gcc-bugs-return-662033-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107813 invoked by alias); 2 Dec 2019 17:30:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107218 invoked by uid 48); 2 Dec 2019 17:30:01 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Mon, 02 Dec 2019 17:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92738-4-FtKomBKVuw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00103.txt.bz2
Content-length: 1338
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
--- Comment #10 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #6)
> So wrf grew starting with r271377, size (w/o debug info) goes from 20164464B
> to 23674792.
I think we've had this discussion before, although I cannot offhand
recall the PR number. PR91512 is closely related.
Since r271377, arguments which may be contiguous are now (conditionally)
packed and unpacked inline (see PR88821).
This was done so that the middle end can look into these conversions
and possibly eliminate them, if it can be determined via inlining
or LTO that the argument is contiguous anyway). This can lead to an
extremely large performance boost for some test cases (*10 or more),
but will, in general, lead to a size increase.
Now, wrf has an extremely strange (and rare) programming style where they pass
a ton of assumed shape arguments (where it is not clear, at compile-time,
if they need packing/unpacking) to an old-style array argument. This
causes considerable code size increase.
So, it's a tradeoff, which we discussed at the time. This is why this
is not done at -Os.
Should we "fix" this? I think not, the style of wrf is just too horrid,
and pessimizing other programs for the sake of one benchmark makes little
sense to me.
>From gcc-bugs-return-662034-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 17:46:11 2019
Return-Path: <gcc-bugs-return-662034-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7192 invoked by alias); 2 Dec 2019 17:46:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6165 invoked by uid 48); 2 Dec 2019 17:46:02 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Mon, 02 Dec 2019 17:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92738-4-E3sNJ7LAiq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00104.txt.bz2
Content-length: 1664
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
--- Comment #11 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #10)
> (In reply to Martin Liška from comment #6)
> > So wrf grew starting with r271377, size (w/o debug info) goes from 20164464B
> > to 23674792.
>
> I think we've had this discussion before, although I cannot offhand
> recall the PR number. PR91512 is closely related.
>
> Since r271377, arguments which may be contiguous are now (conditionally)
> packed and unpacked inline (see PR88821).
>
> This was done so that the middle end can look into these conversions
> and possibly eliminate them, if it can be determined via inlining
> or LTO that the argument is contiguous anyway). This can lead to an
> extremely large performance boost for some test cases (*10 or more),
> but will, in general, lead to a size increase.
>
> Now, wrf has an extremely strange (and rare) programming style where they
> pass
> a ton of assumed shape arguments (where it is not clear, at compile-time,
> if they need packing/unpacking) to an old-style array argument. This
> causes considerable code size increase.
>
> So, it's a tradeoff, which we discussed at the time. This is why this
> is not done at -Os.
>
> Should we "fix" this? I think not, the style of wrf is just too horrid,
> and pessimizing other programs for the sake of one benchmark makes little
> sense to me.
Would using -frepack-arrays solve this issue? I proposed making that the
default a while back. It would do any repacking that is necessary at call sites
rather than creating multiple copies of all loops in every function.
>From gcc-bugs-return-662035-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 17:51:25 2019
Return-Path: <gcc-bugs-return-662035-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18249 invoked by alias); 2 Dec 2019 17:51:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18181 invoked by uid 48); 2 Dec 2019 17:51:21 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66773] sign-compare warning for == and != are pretty useless
Date: Mon, 02 Dec 2019 17:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.7.2
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66773-4-1kVX70nMyv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00105.txt.bz2
Content-length: 1378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66773
--- Comment #24 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Daniel Marjamäki from comment #23)
> > If the user expects C to provide tests for "mathematically different", the
> user has some learning to do.
>
> I believe most users can appreciate this. But few users fully understand the
> integer conversions. I think it's dangerous. :-(
But deleting or disabling the sign compare warnings will not help this.
> > If, as I said, the user uses explicit casts, that's not good. Much better
> already is to use implicit casts, as I said; and much better than that is
> to fix the problems at the root (use proper types everywhere), as I said.
>
> You are de-facto advocating explicit casts because that is how everybody
> fixes these.
No, I am not; and no, not everyone uses casts to shut up these warnings.
Too many people do, certainly, but not even the majority.
> The advice to use proper types is good, in my opinion everybody tries to do
> that. However as far as I see it's impossible in practice to never mix
> signed and unsigned types in real projects.
>
> > There is no simple fix, so GCC cannot give good guidance.
>
> Then people just blindly use explicit casts.. and I dislike that.
Sure, me too. Do you see a way we can discourage people from doing that?
>From gcc-bugs-return-662036-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 17:51:46 2019
Return-Path: <gcc-bugs-return-662036-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19547 invoked by alias); 2 Dec 2019 17:51:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19385 invoked by uid 55); 2 Dec 2019 17:51:39 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92741] [10 Regression] ICE: verify_gimple failed (error: invalid vector types in nop conversion)
Date: Mon, 02 Dec 2019 17:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92741-4-7ufhsh9usx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00106.txt.bz2
Content-length: 952
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92741
--- Comment #6 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Mon Dec 2 17:51:08 2019
New Revision: 278910
URL: https://gcc.gnu.org/viewcvs?rev=278910&root=gcc&view=rev
Log:
Tighten check for vector types in fold_convertible_p (PR 92741)
In this PR, IPA-CP was misled into using NOP_EXPR rather than
VIEW_CONVERT_EXPR to reinterpret a vector of 4 shorts as a vector
of 2 ints. This tripped the tree-cfg.c assert I'd added in r278245.
2019-12-02 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR middle-end/92741
* fold-const.c (fold_convertible_p): Check vector types more
thoroughly.
gcc/testsuite/
PR middle-end/92741
* gcc.dg/pr92741.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/pr92741.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/fold-const.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662037-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 17:52:07 2019
Return-Path: <gcc-bugs-return-662037-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20370 invoked by alias); 2 Dec 2019 17:52:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20282 invoked by uid 48); 2 Dec 2019 17:52:02 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92741] [10 Regression] ICE: verify_gimple failed (error: invalid vector types in nop conversion)
Date: Mon, 02 Dec 2019 17:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92741-4-LkZqYJHv39@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00107.txt.bz2
Content-length: 459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92741
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-662038-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 18:07:58 2019
Return-Path: <gcc-bugs-return-662038-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56994 invoked by alias); 2 Dec 2019 18:07:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56926 invoked by uid 48); 2 Dec 2019 18:07:55 -0000
From: "srk31 at srcf dot ucam.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/91025] cpp man page incorrectly describes -MD option
Date: Mon, 02 Dec 2019 18:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: srk31 at srcf dot ucam.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-91025-4-sTQGR56Ggx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91025-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91025-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00108.txt.bz2
Content-length: 383
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91025
--- Comment #2 from Stephen Kell <srk31 at srcf dot ucam.org> ---
Created attachment 47405
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47405&action=edit
Patch to cpp manual page's description of -MD
It took me long enough, but I'm fairly sure this patch results in a less-wrong
cpp man page than the current one.
>From gcc-bugs-return-662039-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 18:33:21 2019
Return-Path: <gcc-bugs-return-662039-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113024 invoked by alias); 2 Dec 2019 18:33:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112967 invoked by uid 48); 2 Dec 2019 18:33:16 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/90076] Polymorphic Allocate on Assignment Memory Leak
Date: Mon, 02 Dec 2019 18:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-90076-4-OArdD52bzO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90076-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90076-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00109.txt.bz2
Content-length: 2356
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90076
G. Steinmetz <gscfq@t-online.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gscfq@t-online.de
--- Comment #2 from G. Steinmetz <gscfq@t-online.de> ---
An alternate take :
$ cat z1.f90
program p
contains
subroutine s
class(*), allocatable :: x
x = undef
end
end
$ gfortran-10-20191201 -c z1.f90
z1.f90:5:0:
5 | x = undef
|
internal compiler error: in build_function_decl, at fortran/trans-decl.c:2324
0x6f2c39 build_function_decl
../../gcc/fortran/trans-decl.c:2321
0x6fa334 gfc_get_symbol_decl(gfc_symbol*)
../../gcc/fortran/trans-decl.c:1727
0x7088e0 gfc_conv_variable
../../gcc/fortran/trans-expr.c:2624
0x704afa gfc_conv_expr(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-expr.c:8665
0x716511 gfc_conv_initializer(gfc_expr*, gfc_typespec*, tree_node*, bool, bool,
bool)
../../gcc/fortran/trans-expr.c:7660
0x7047f3 gfc_conv_structure(gfc_se*, gfc_expr*, int)
../../gcc/fortran/trans-expr.c:8553
0x7164a1 gfc_conv_initializer(gfc_expr*, gfc_typespec*, tree_node*, bool, bool,
bool)
../../gcc/fortran/trans-expr.c:7675
0x6f9e5f gfc_get_symbol_decl(gfc_symbol*)
../../gcc/fortran/trans-decl.c:1888
0x7088e0 gfc_conv_variable
../../gcc/fortran/trans-expr.c:2624
0x704afa gfc_conv_expr(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-expr.c:8665
0x71294f trans_class_vptr_len_assignment
../../gcc/fortran/trans-expr.c:8967
0x714e19 trans_class_assignment
../../gcc/fortran/trans-expr.c:10596
0x714e19 gfc_trans_assignment_1
../../gcc/fortran/trans-expr.c:11002
0x6d4617 trans_code
../../gcc/fortran/trans.c:1852
0x6fda64 gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6798
0x6fd864 gfc_generate_contained_functions
../../gcc/fortran/trans-decl.c:5793
0x6fd864 gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6730
0x686c26 translate_all_program_units
../../gcc/fortran/parse.c:6302
0x686c26 gfc_parse_file()
../../gcc/fortran/parse.c:6541
0x6d10bf gfc_be_parse_file
../../gcc/fortran/f95-lang.c:210
>From gcc-bugs-return-662040-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 18:34:15 2019
Return-Path: <gcc-bugs-return-662040-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114397 invoked by alias); 2 Dec 2019 18:34:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114355 invoked by uid 48); 2 Dec 2019 18:34:10 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/90499] ICE during polymorphic assignment
Date: Mon, 02 Dec 2019 18:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-90499-4-QhC5q3Tte2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90499-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90499-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00110.txt.bz2
Content-length: 2267
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90499
G. Steinmetz <gscfq@t-online.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gscfq@t-online.de
--- Comment #2 from G. Steinmetz <gscfq@t-online.de> ---
Update, also related to pr90076 :
$ gfortran-10-20191201 -c pr90499.f90
pr90499.f90:17:0:
17 | f = g_t()
|
internal compiler error: in build_function_decl, at fortran/trans-decl.c:2324
0x6f2c39 build_function_decl
../../gcc/fortran/trans-decl.c:2321
0x6fa334 gfc_get_symbol_decl(gfc_symbol*)
../../gcc/fortran/trans-decl.c:1727
0x7088e0 gfc_conv_variable
../../gcc/fortran/trans-expr.c:2624
0x704afa gfc_conv_expr(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-expr.c:8665
0x716511 gfc_conv_initializer(gfc_expr*, gfc_typespec*, tree_node*, bool, bool,
bool)
../../gcc/fortran/trans-expr.c:7660
0x7047f3 gfc_conv_structure(gfc_se*, gfc_expr*, int)
../../gcc/fortran/trans-expr.c:8553
0x7164a1 gfc_conv_initializer(gfc_expr*, gfc_typespec*, tree_node*, bool, bool,
bool)
../../gcc/fortran/trans-expr.c:7675
0x6f9e5f gfc_get_symbol_decl(gfc_symbol*)
../../gcc/fortran/trans-decl.c:1888
0x7088e0 gfc_conv_variable
../../gcc/fortran/trans-expr.c:2624
0x704afa gfc_conv_expr(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-expr.c:8665
0x71294f trans_class_vptr_len_assignment
../../gcc/fortran/trans-expr.c:8967
0x714e19 trans_class_assignment
../../gcc/fortran/trans-expr.c:10596
0x714e19 gfc_trans_assignment_1
../../gcc/fortran/trans-expr.c:11002
0x6d4617 trans_code
../../gcc/fortran/trans.c:1852
0x6fda64 gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6798
0x6fd864 gfc_generate_contained_functions
../../gcc/fortran/trans-decl.c:5793
0x6fd864 gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6730
0x686c26 translate_all_program_units
../../gcc/fortran/parse.c:6302
0x686c26 gfc_parse_file()
../../gcc/fortran/parse.c:6541
0x6d10bf gfc_be_parse_file
../../gcc/fortran/f95-lang.c:210
>From gcc-bugs-return-662041-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 18:35:51 2019
Return-Path: <gcc-bugs-return-662041-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116152 invoked by alias); 2 Dec 2019 18:35:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116058 invoked by uid 48); 2 Dec 2019 18:35:47 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92753] New: ICE in gfc_trans_call, at fortran/trans-stmt.c:392
Date: Mon, 02 Dec 2019 18:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00111.txt.bz2
Content-length: 1311
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92753
Bug ID: 92753
Summary: ICE in gfc_trans_call, at fortran/trans-stmt.c:392
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Started to ICE between 20181028 and 20181104 :
$ cat z1.f90
module m
type t
character(3) :: c
end type
type(t), parameter :: x = t('abc')
end
program p
use m
call s(x%c%len)
contains
subroutine s(n)
print *, n
end
end
$ gfortran-10-20191201 -c z1.f90
z1.f90:9:0:
9 | call s(x%c%len)
|
internal compiler error: in gfc_trans_call, at fortran/trans-stmt.c:392
0x74366e gfc_trans_call(gfc_code*, bool, tree_node*, tree_node*, bool)
../../gcc/fortran/trans-stmt.c:392
0x6d49f1 trans_code
../../gcc/fortran/trans.c:1920
0x6fda64 gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6798
0x686c26 translate_all_program_units
../../gcc/fortran/parse.c:6302
0x686c26 gfc_parse_file()
../../gcc/fortran/parse.c:6541
0x6d10bf gfc_be_parse_file
../../gcc/fortran/f95-lang.c:210
>From gcc-bugs-return-662042-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 18:36:47 2019
Return-Path: <gcc-bugs-return-662042-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117769 invoked by alias); 2 Dec 2019 18:36:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117721 invoked by uid 48); 2 Dec 2019 18:36:42 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92753] ICE in gfc_trans_call, at fortran/trans-stmt.c:392
Date: Mon, 02 Dec 2019 18:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-92753-4-ZC1NwZ4eq5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00112.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92753
G. Steinmetz <gscfq@t-online.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
--- Comment #1 from G. Steinmetz <gscfq@t-online.de> ---
Works without that parameter attribute, and also old fashioned :
$ cat z3.f90
module m
type t
character(3) :: c
end type
type(t), parameter :: x = t('abc')
end
program p
use m
call s(len(x%c))
contains
subroutine s(n)
print *, n
end
end
$ gfortran-10-20191201 z3.f90 && ./a.out
3
>From gcc-bugs-return-662043-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 18:40:38 2019
Return-Path: <gcc-bugs-return-662043-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28114 invoked by alias); 2 Dec 2019 18:40:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22396 invoked by uid 48); 2 Dec 2019 18:40:34 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92754] New: ICE in gfc_finish_var_decl, at fortran/trans-decl.c:693
Date: Mon, 02 Dec 2019 18:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92754-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00113.txt.bz2
Content-length: 1438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92754
Bug ID: 92754
Summary: ICE in gfc_finish_var_decl, at
fortran/trans-decl.c:693
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Started with gcc-9 before 20180501 :
$ cat z1.f90
program p
integer :: max
block
character :: x = max('a','b')
print *, x
end block
end
$ gfortran-10-20191201 -c z1.f90
z1.f90:1:0:
1 | program p
|
internal compiler error: in gfc_finish_var_decl, at fortran/trans-decl.c:693
0x6fa9e9 gfc_finish_var_decl
../../gcc/fortran/trans-decl.c:693
0x6f9d61 gfc_get_symbol_decl(gfc_symbol*)
../../gcc/fortran/trans-decl.c:1843
0x6fc8df generate_local_decl
../../gcc/fortran/trans-decl.c:5869
0x6bc5a2 do_traverse_symtree
../../gcc/fortran/symbol.c:4165
0x6fd884 generate_local_vars
../../gcc/fortran/trans-decl.c:6075
0x6fd884 gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6733
0x686c26 translate_all_program_units
../../gcc/fortran/parse.c:6302
0x686c26 gfc_parse_file()
../../gcc/fortran/parse.c:6541
0x6d10bf gfc_be_parse_file
../../gcc/fortran/f95-lang.c:210
>From gcc-bugs-return-662044-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 18:42:15 2019
Return-Path: <gcc-bugs-return-662044-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30174 invoked by alias); 2 Dec 2019 18:42:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30089 invoked by uid 48); 2 Dec 2019 18:42:12 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92398] [10 regression] error in update of gcc.target/powerpc/pr72804.c in r277872
Date: Mon, 02 Dec 2019 18:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92398-4-d1C5Nn9b0G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00114.txt.bz2
Content-length: 682
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92398
--- Comment #8 from seurer at gcc dot gnu.org ---
The changes in r278890 fix the earlier problems but introduce new ones:
failures in r278889 (not seen in r278890):
FAIL: gcc.target/powerpc/pr72804.c scan-assembler-times not 4
FAIL: gcc.target/powerpc/pr72804.c scan-assembler-times std 2
FAIL: gcc.target/powerpc/pr72804.c scan-assembler-not stxvd2x
FAIL: gcc.target/powerpc/pr72804.c scan-assembler-not xxpermdi
new failures in r278890:
FAIL: gcc.target/powerpc/pr72804.c scan-assembler-times \\mnot\\M 2
FAIL: gcc.target/powerpc/pr72804.c scan-assembler-not \\mlxvd2x\\M
saw this on both power 8 (BE) and power 9 (LE).
>From gcc-bugs-return-662045-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 18:44:55 2019
Return-Path: <gcc-bugs-return-662045-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72074 invoked by alias); 2 Dec 2019 18:44:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72036 invoked by uid 48); 2 Dec 2019 18:44:51 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92755] New: [10 Regression] ICE in gfc_dep_resolver, at fortran/dependency.c:2123
Date: Mon, 02 Dec 2019 18:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00115.txt.bz2
Content-length: 1625
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92755
Bug ID: 92755
Summary: [10 Regression] ICE in gfc_dep_resolver, at
fortran/dependency.c:2123
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Additional case, switched between 20190630 and 20190728 :
$ cat z1.f90
program p
type t
end type
type t2
class(t), allocatable :: a(:)
end type
type(t2) :: z
z%a = [z%a]
end
$ gfortran-10-20190630 -c z1.f90
$
$ gfortran-10-20191201 -c z1.f90
z1.f90:8:0:
8 | z%a = [z%a]
|
internal compiler error: in gfc_dep_resolver, at fortran/dependency.c:2123
0x6c9416 gfc_dep_resolver(gfc_ref*, gfc_ref*, gfc_reverse*, bool)
../../gcc/fortran/dependency.c:2123
0x6c98ac gfc_check_dependency(gfc_expr*, gfc_expr*, bool)
../../gcc/fortran/dependency.c:1394
0x6e2c8e gfc_conv_resolve_dependencies(gfc_loopinfo*, gfc_ss*, gfc_ss*)
../../gcc/fortran/trans-array.c:4851
0x714bc5 gfc_trans_assignment_1
../../gcc/fortran/trans-expr.c:10806
0x6d4617 trans_code
../../gcc/fortran/trans.c:1852
0x6fda64 gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6798
0x686c26 translate_all_program_units
../../gcc/fortran/parse.c:6302
0x686c26 gfc_parse_file()
../../gcc/fortran/parse.c:6541
0x6d10bf gfc_be_parse_file
../../gcc/fortran/f95-lang.c:210
>From gcc-bugs-return-662046-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 18:50:11 2019
Return-Path: <gcc-bugs-return-662046-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81474 invoked by alias); 2 Dec 2019 18:50:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81444 invoked by uid 48); 2 Dec 2019 18:50:07 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92756] New: [9/10 Regression] ICE in lower_omp, at omp-low.c:12988
Date: Mon, 02 Dec 2019 18:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00116.txt.bz2
Content-length: 1317
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92756
Bug ID: 92756
Summary: [9/10 Regression] ICE in lower_omp, at omp-low.c:12988
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Changed between 20181104 and 20181111 :
$ cat z1.f90
program p
integer :: i
!$omp teams distribute parallel do
do i = 1, 2
end do
end
$ gfortran-10-20191201 -c z1.f90 -fopenmp
during GIMPLE pass: omplower
z1.f90:3:0:
3 | !$omp teams distribute parallel do
|
internal compiler error: Segmentation fault
0xb7c01f crash_signal
../../gcc/toplev.c:328
0xa77dc1 gsi_start_1
../../gcc/gimple-iterator.h:105
0xa77dc1 lower_omp
../../gcc/omp-low.c:12988
0xa86653 lower_omp_taskreg
../../gcc/omp-low.c:11253
0xa7a1b7 lower_omp_1
../../gcc/omp-low.c:12852
0xa7a1b7 lower_omp
../../gcc/omp-low.c:12989
0xa784ee lower_omp_1
../../gcc/omp-low.c:12781
0xa784ee lower_omp
../../gcc/omp-low.c:12989
0xa7f99b execute_lower_omp
../../gcc/omp-low.c:13031
0xa7f99b execute
../../gcc/omp-low.c:13079
>From gcc-bugs-return-662047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 19:19:37 2019
Return-Path: <gcc-bugs-return-662047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37414 invoked by alias); 2 Dec 2019 19:19:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37384 invoked by uid 48); 2 Dec 2019 19:19:32 -0000
From: "ricardolafabreu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/92757] New: Documentation ambiguous/misleading about interplay of optimization and warning flags
Date: Mon, 02 Dec 2019 19:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ricardolafabreu at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00117.txt.bz2
Content-length: 2498
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
Bug ID: 92757
Summary: Documentation ambiguous/misleading about interplay of
optimization and warning flags
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
Assignee: unassigned at gcc dot gnu.org
Reporter: ricardolafabreu at gmail dot com
Target Milestone: ---
The documentation (man page for gcc 8.3.0 or
https://gcc.gnu.org/onlinedocs/gcc/) could be clearer in what concerns the
interaction of optimization and warnings. That optimization options influence
the correctness analysis (warnings report possible incorrections) is too
general and important a piece of information to be buried in the documentation
of individual warning flags.
The general documentation for those flag classes says things like
> You can request many specific warnings with options beginning with ‘-W’
or
> -Wall
>
> This enables all the warnings about constructions that some users consider questionable [...]
And the opening message in `--help=warnings` is
> The following options control compiler warning messages: [...]
I find this a bit misleading. There is an ambiguity in that some warnings,
"enabled" via a -Wxyz flag, may be effectively disabled due to optimization
options (or lack thereof). A particular consequence is that -W flags are not
enough to make a build that prints as many warnings as possible (particular -O
flags are needed).
While the text for the general flag classes claims they enable/control
warnings, it fails to mention that enablement/control is only partial. They
don't *entirely* enable warnings, not always. There is no hint to this in the
general text discussing optimization either, only in particular warning flags.
Without reading the documentation for the right specific warning flag, it is
easy to assume that warning and optimization flags are orthogonal in general.
To prevent ambiguity from arising in the first place, text claiming general
properties of -W flags could be completed with something like "provided the
required analysis are enabled with the chosen optimization". I believe this
would make the text more accurate and informative. For completeness, the
section on optimization could also say it affects what analysis are done and,
therefore, what warnings are printed.
>From gcc-bugs-return-662048-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 19:30:28 2019
Return-Path: <gcc-bugs-return-662048-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63259 invoked by alias); 2 Dec 2019 19:30:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62534 invoked by uid 48); 2 Dec 2019 19:30:12 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/92757] Documentation ambiguous/misleading about interplay of optimization and warning flags
Date: Mon, 02 Dec 2019 19:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92757-4-k9oUwd0Qm3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00118.txt.bz2
Content-length: 553
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>is too general and important a piece of information to be buried in the documentation of individual warning flags.
Yes because you should read the whole documentation rather than bits and pieces
of it. When a warning is outputted, the option the warning is associated with
is also outputted and so you could go and read about that specific option to
find information about if the warning is effected by optimization or not
>From gcc-bugs-return-662049-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 19:37:44 2019
Return-Path: <gcc-bugs-return-662049-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74077 invoked by alias); 2 Dec 2019 19:37:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74034 invoked by uid 48); 2 Dec 2019 19:37:40 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92758] New: [10 regression] r278833 breaks gcc.target/powerpc/fold-vec-splat-floatdouble.c
Date: Mon, 02 Dec 2019 19:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00119.txt.bz2
Content-length: 1089
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92758
Bug ID: 92758
Summary: [10 regression] r278833 breaks
gcc.target/powerpc/fold-vec-splat-floatdouble.c
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
FAIL: gcc.target/powerpc/fold-vec-splat-floatdouble.c scan-assembler-times
xxpermdi 3
This is one of those tests that just counts assembler instructions and the
count of xxpermdi changed
seurer@makalu-lp1:~/gcc/build/gcc-test2$ diff
fold-vec-splat-floatdouble.s.r278832 fold-vec-splat-floatdouble.s.r278833
94c94,95
< xxpermdi 34,34,34,0
---
> xxlor 0,34,34
> xxpermdi 34,0,0,0
113c114,115
< xxpermdi 34,34,34,3
---
> xxpermdi 0,34,34,2
> xxpermdi 34,0,0,0
which in this case looks like missed optimization given the extra instructions
are just copying things needlessly between registers.
>From gcc-bugs-return-662050-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 20:01:19 2019
Return-Path: <gcc-bugs-return-662050-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16402 invoked by alias); 2 Dec 2019 20:01:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16352 invoked by uid 48); 2 Dec 2019 20:01:14 -0000
From: "ricardolafabreu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/92757] Documentation ambiguous/misleading about interplay of optimization and warning flags
Date: Mon, 02 Dec 2019 20:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ricardolafabreu at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92757-4-ak1U10eurc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00120.txt.bz2
Content-length: 798
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #2 from Ricardo Abreu <ricardolafabreu at gmail dot com> ---
Saying "-Wall enables all the warnings that [...]" is inaccurate. Unless you
consider a very specific interpretation of "enables". Then it is ambiguous,
because there are other valid (and probably more intuitive) interpretations.
Preventing that ambiguity from arising in the first place would make for better
documentation. The reader should not have to read on specific warnings to find
that -Wall, on its own, does not really enable the warnings it claims.
The interplay of optimization and correctness analysis feels to me too general
to be left to the documentation of individual warning flags. It is something
pertaining to a bigger, structural scope.
>From gcc-bugs-return-662051-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 20:12:50 2019
Return-Path: <gcc-bugs-return-662051-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38732 invoked by alias); 2 Dec 2019 20:12:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38691 invoked by uid 48); 2 Dec 2019 20:12:42 -0000
From: "ricardolafabreu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/92757] Documentation ambiguous/misleading about interplay of optimization and warning flags
Date: Mon, 02 Dec 2019 20:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ricardolafabreu at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92757-4-4TlexQw0UE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00121.txt.bz2
Content-length: 385
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #3 from Ricardo Abreu <ricardolafabreu at gmail dot com> ---
Note that I would classify this as a request for improvement rather than a bug.
A manual is not a specification, it is something that should inform users, and
its contents can be better or worse in achieving that for reasons beyond strict
correctness.
>From gcc-bugs-return-662052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 20:31:13 2019
Return-Path: <gcc-bugs-return-662052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64007 invoked by alias); 2 Dec 2019 20:31:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63789 invoked by uid 48); 2 Dec 2019 20:30:55 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92176] LRA problem with reloads for subreg operands
Date: Mon, 02 Dec 2019 20:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ra, wrong-code
X-Bugzilla-Severity: major
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92176-4-9SkZYD3mvE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92176-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92176-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00122.txt.bz2
Content-length: 1093
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92176
--- Comment #5 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Andreas Krebbel from comment #3)
> 276.ira:
>
....
>
> /* Give the backend a chance to disallow the mode change. */
> if (GET_MODE_CLASS (xmode) != MODE_COMPLEX_INT
> && GET_MODE_CLASS (xmode) != MODE_COMPLEX_FLOAT
> && !REG_CAN_CHANGE_MODE_P (xregno, xmode, ymode)
> /* We can use mode change in LRA for some transformations. */
> && ! lra_in_progress) <----- ?
> return -1;
>
> I'm currently checking whether removing it makes any difference in code
> generation - apart from fixing the testcase.
As I remember this is necessary for some x86/x86-64 insn descriptions which
match operands of different modes one of which is XFmode. For matched reloads
LRA uses one pseudo and that creates incorrect RTL.
So I think just removing this code will not work for all targets. We should
probably somewhere check XFmode or introduce a machine-dependent hook.
I'll investigate this problem more.
>From gcc-bugs-return-662053-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 20:52:06 2019
Return-Path: <gcc-bugs-return-662053-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103785 invoked by alias); 2 Dec 2019 20:52:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103463 invoked by uid 48); 2 Dec 2019 20:52:00 -0000
From: "yyc1992 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92759] New: Typo in libstdcxx/v6/xmethods.py
Date: Mon, 02 Dec 2019 20:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yyc1992 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92759-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00123.txt.bz2
Content-length: 1038
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92759
Bug ID: 92759
Summary: Typo in libstdcxx/v6/xmethods.py
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: yyc1992 at gmail dot com
Target Milestone: ---
I get the following warning when running gdb/rr.
```
/usr/lib/../share/gcc-9.2.0/python/libstdcxx/v6/xmethods.py:731: SyntaxWarning:
list indices must be integers or slices, not str; perhaps you missed a comma?
refcounts = ['_M_refcount']['_M_pi']
```
Looking at the
[code](https://github.com/gcc-mirror/gcc/blob/daa87973f7a00bf3bb81d0644dd60f4efb83bb65/libstdc%2B%2B-v3/python/libstdcxx/v6/xmethods.py#L731)
I think that line should read
```
refcounts = obj['_M_refcount']['_M_pi']
```
instead.
I could submit a patch but I feel like it'll be faster/easier for someone here
to just fix this....
>From gcc-bugs-return-662054-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 21:31:54 2019
Return-Path: <gcc-bugs-return-662054-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40044 invoked by alias); 2 Dec 2019 21:31:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40015 invoked by uid 48); 2 Dec 2019 21:31:49 -0000
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92709] Cross Compilation failed for Latest GCC riscv64-linux-gnu on Linux/WSL2
Date: Mon, 02 Dec 2019 21:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilson at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92709-4-Pb3eHe6nc4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92709-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92709-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00124.txt.bz2
Content-length: 1606
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92709
Jim Wilson <wilson at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilson at gcc dot gnu.org
--- Comment #3 from Jim Wilson <wilson at gcc dot gnu.org> ---
>make[4]: Entering directory '/home/cqwrteur/gcc-riscv64-build/riscv64-linux-gnu/lib32/ilp32/libgcc'
>make[4]: *** No rule to make target 'all'. Stop.
Look in the riscv64-linux-gnu/lib32/ilp32/libgcc dir. There should be a
Makefile that is a copy of the $srcdir/libgcc/Makefile.in file with some sed
substition. If this isn't true, then it is the configure step that failed.
You can force the library dirs to reconfigure by deleting them. It gets a bit
more complicated with multilibs, I think you have to delete the top level
riscv64-linux-gnu/libgcc to force a reconfigure, but just a rm -rf
riscv64-linux-gnu works too and is simpler, though more stuff will be rebuilt.
You might want to do a -j1 make to get an easier to read build log.
I don't have a Windows machine at work, but there is only one WSL problem that
I have seen reported, and it is that WSL makes filesystems case-insensitive by
default which is contrary to linux practice. It is known that this will break
glibc builds which uses .os and .oS for two different kinds of files. I don't
think that this breaks gcc builds. But since you are trying to do a cross to
riscv64-linux-gnu you will run into this problem if you haven't already.
>From gcc-bugs-return-662055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 21:33:42 2019
Return-Path: <gcc-bugs-return-662055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41982 invoked by alias); 2 Dec 2019 21:33:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41926 invoked by uid 55); 2 Dec 2019 21:33:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92695] P1064R0 - virtual constexpr fails if object taken from array
Date: Mon, 02 Dec 2019 21:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92695-4-2rxxM4NkMd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00125.txt.bz2
Content-length: 635
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92695
--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Dec 2 21:33:06 2019
New Revision: 278912
URL: https://gcc.gnu.org/viewcvs?rev=278912&root=gcc&view=rev
Log:
PR c++/92695
* constexpr.c (cxx_eval_constant_expression) <case OBJ_TYPE_REF>: Use
STRIP_NOPS before checking for ADDR_EXPR.
* g++.dg/cpp2a/constexpr-virtual15.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-virtual15.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/constexpr.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662056-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 21:35:42 2019
Return-Path: <gcc-bugs-return-662056-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45686 invoked by alias); 2 Dec 2019 21:35:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45639 invoked by uid 48); 2 Dec 2019 21:35:37 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/92757] Documentation ambiguous/misleading about interplay of optimization and warning flags
Date: Mon, 02 Dec 2019 21:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: documentation, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-92757-4-dyUznXJveA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00126.txt.bz2
Content-length: 2244
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Ricardo Abreu from comment #2)
> Saying "-Wall enables all the warnings that [...]" is inaccurate. Unless you
> consider a very specific interpretation of "enables". Then it is ambiguous,
> because there are other valid (and probably more intuitive) interpretations.
It has an unambiguous meaning:
$ gcc -Q --help=warnings | fgrep maybe-uninit
-Wmaybe-uninitialized [disabled]
$ gcc -Q --help=warnings -Wall | fgrep maybe-uninit
-Wmaybe-uninitialized [enabled]
That's what it means by "enables". Whether a specific diagnostic is emitted for
a specific piece of code is a separate matter (and the whole point of the
-Wmaybe-uninitialied diagnostic is that it's not 100% reliable, that's why it
says "maybe").
> Preventing that ambiguity from arising in the first place would make for
> better documentation. The reader should not have to read on specific
> warnings to find that -Wall, on its own, does not really enable the warnings
> it claims.
I think you've misunderstood what Andrew said. The warning you originally
thought was buggy was:
main.cpp:23:19: error: 'a' may be used uninitialized in this function
[-Werror=maybe-uninitialized]
That tells you which warning has been triggered. If you had read the docs for
-Wmaybe-uninitialized you would see:
https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wmaybe-uninitialized
"These warnings are only possible in optimizing compilation, because
otherwise GCC does not keep track of the state of variables."
The docs for -Wall are not relevant here.
> The interplay of optimization and correctness analysis feels to me too
> general to be left to the documentation of individual warning flags. It is
> something pertaining to a bigger, structural scope.
I've proposed a patch:
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00087.html
>From gcc-bugs-return-662057-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 21:38:22 2019
Return-Path: <gcc-bugs-return-662057-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49548 invoked by alias); 2 Dec 2019 21:38:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49515 invoked by uid 48); 2 Dec 2019 21:38:18 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92759] Typo in libstdcxx/v6/xmethods.py
Date: Mon, 02 Dec 2019 21:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92759-4-VcE8Shp1dX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92759-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92759-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00127.txt.bz2
Content-length: 595
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92759
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Already fixed on trunk by r275644, on gcc-9-branch by r275645, on gcc-8-branch
by r275646, and on gcc-7-branch by r275647.
The fix is in GCC 7.5, and will be in 8.4 and 9.3.
>From gcc-bugs-return-662058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 22:05:25 2019
Return-Path: <gcc-bugs-return-662058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29889 invoked by alias); 2 Dec 2019 22:05:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29808 invoked by uid 48); 2 Dec 2019 22:05:21 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92760] New: [10 regression] several vector test cases fail on power 7 after r278800
Date: Mon, 02 Dec 2019 22:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00128.txt.bz2
Content-length: 1357
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92760
Bug ID: 92760
Summary: [10 regression] several vector test cases fail on
power 7 after r278800
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
FAIL: gcc.dg/vect/vect-82.c -flto -ffat-lto-objects scan-tree-dump-times vect
"vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-82.c scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-82_64.c -flto -ffat-lto-objects scan-tree-dump-times
vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-82_64.c scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-83.c -flto -ffat-lto-objects scan-tree-dump-times vect
"vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-83.c scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-83_64.c -flto -ffat-lto-objects scan-tree-dump-times
vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-83_64.c scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.target/powerpc/conv-vectorize-1.c scan-assembler \\mxvcvsxdsp\\M
FAIL: gcc.target/powerpc/conv-vectorize-1.c scan-assembler \\mxvcvuxdsp\\M
>From gcc-bugs-return-662059-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 23:16:35 2019
Return-Path: <gcc-bugs-return-662059-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80216 invoked by alias); 2 Dec 2019 23:16:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72116 invoked by uid 48); 2 Dec 2019 23:16:31 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92761] New: hash_table::expand invokes assignment on invalid objects
Date: Mon, 02 Dec 2019 23:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00129.txt.bz2
Content-length: 3081
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
Bug ID: 92761
Summary: hash_table::expand invokes assignment on invalid
objects
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
The GCC internal hash_table::expand() function invokes the assignment operator
on invalid/empty elements. The following test case inserted into the C++
parser (where I ran into the problem) reproduces the bug:
struct S
{
S (): p (&p) { }
S (const S &s): p (&p) { gcc_assert (s.p == &s.p); }
S& operator= (const S &s) { gcc_assert (s.p == &s.p); return *this; }
~S () { gcc_assert (p == &p); }
void *p;
};
hash_map<tree, S> x;
static void test_hash_table ()
{
for (int i = 0; i != 32; ++i)
x.put ((tree)i, S ());
x.empty ();
}
/* Parse one entire translation unit. */
void
c_parse_file (void)
{
test_hash_table ();
...
}
internal compiler error: in operator=, at cp/parser.c:43418
0xaeed4f S::operator=(S const&)
/src/gcc/61339/gcc/cp/parser.c:43418
0xaf3a7e hash_map<tree_node*, S,
simple_hashmap_traits<default_hash_traits<tree_node*>, S>
>::hash_entry::operator=(hash_map<tree_node*, S,
simple_hashmap_traits<default_hash_traits<tree_node*>, S> >::hash_entry const&)
/src/gcc/61339/gcc/hash-map.h:42
0xaf3c24 hash_table<hash_map<tree_node*, S,
simple_hashmap_traits<default_hash_traits<tree_node*>, S> >::hash_entry, false,
xcallocator>::expand()
/src/gcc/61339/gcc/hash-table.h:822
0xaf21a7 hash_table<hash_map<tree_node*, S,
simple_hashmap_traits<default_hash_traits<tree_node*>, S> >::hash_entry, false,
xcallocator>::find_slot_with_hash(tree_node* const&, unsigned int,
insert_option)
/src/gcc/61339/gcc/hash-table.h:962
0xaf02e4 hash_map<tree_node*, S,
simple_hashmap_traits<default_hash_traits<tree_node*>, S> >::put(tree_node*
const&, S const&)
/src/gcc/61339/gcc/hash-map.h:165
0xaea3b8 test_hash_table
/src/gcc/61339/gcc/cp/parser.c:43428
0xaea3e5 c_parse_file()
/src/gcc/61339/gcc/cp/parser.c:43438
0xcd34ab c_common_parse_file()
/src/gcc/61339/gcc/c-family/c-opts.c:1185
Please submit a full bug report,
As the stack trace shows, the problem is due to expand() directly assigning to
the (invalid) lvalue obtained from find_empty_slot_for_expand:
template<typename Descriptor, bool Lazy,
template<typename Type> class Allocator>
void
hash_table<Descriptor, Lazy, Allocator>::expand ()
{
value_type *oentries = m_entries;
...
value_type *p = oentries;
do
{
value_type &x = *p;
if (!is_empty (x) && !is_deleted (x))
{
value_type *q = find_empty_slot_for_expand (Descriptor::hash (x));
*q = x; <<< q points to a empty slot with no object in it
}
p++;
}
while (p < olimit);
...
}
>From gcc-bugs-return-662060-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 23:18:31 2019
Return-Path: <gcc-bugs-return-662060-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114456 invoked by alias); 2 Dec 2019 23:18:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114383 invoked by uid 48); 2 Dec 2019 23:18:27 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92761] hash_table::expand invokes assignment on invalid objects
Date: Mon, 02 Dec 2019 23:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords see_also
Message-ID: <bug-92761-4-MzkxRz7tg0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00130.txt.bz2
Content-length: 889
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=90959,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=90904,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=90923
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
For some other bugs in GCC containers see pr90959, pr90904, and pr90923.
>From gcc-bugs-return-662061-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 23:29:38 2019
Return-Path: <gcc-bugs-return-662061-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125046 invoked by alias); 2 Dec 2019 23:29:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124963 invoked by uid 48); 2 Dec 2019 23:29:34 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92761] hash_table::expand invokes assignment on invalid objects
Date: Mon, 02 Dec 2019 23:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92761-4-hJzVzeOVX7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00131.txt.bz2
Content-length: 263
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I don't think this is a valid testcase, given:
Both KeyId and Value may be non-trivial (non-POD) types provided
a suitabe Traits class.
>From gcc-bugs-return-662062-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 23:33:22 2019
Return-Path: <gcc-bugs-return-662062-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128963 invoked by alias); 2 Dec 2019 23:33:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128922 invoked by uid 48); 2 Dec 2019 23:33:17 -0000
From: "ricardolafabreu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/92757] Documentation ambiguous/misleading about interplay of optimization and warning flags
Date: Mon, 02 Dec 2019 23:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: documentation, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ricardolafabreu at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92757-4-1EbM1HxJsy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00132.txt.bz2
Content-length: 1476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #5 from Ricardo Abreu <ricardolafabreu at gmail dot com> ---
> It has an unambiguous meaning:
>
> $ gcc -Q --help=warnings | fgrep maybe-uninit
> -Wmaybe-uninitialized [disabled]
> $ gcc -Q --help=warnings -Wall | fgrep maybe-uninit
> -Wmaybe-uninitialized [enabled]
>
> That's what it means by "enables".
The sentence I quoted says -Wall enables a certain group of warnings, not
flags. It goes on to characterize that group. It conveys information on its
own, without directing to sub-flags.
I understand there is a more restrictive sense of "enables" where the sentence
is correct. It is the same as when saying that the on position of a switch
enables current to go through, in a circuit that requires two switches for
current to actually flow. But this is not the only viable one when reading the
sentence. Not even, I believe, the most intuitive. Therein lies ambiguity.
Even if reading the whole docs later restricts possible interpretations, humans
are not compilers and I propose the manual would be clearer if the necessary
clarification was offered where needed. I don't see what the motivation would
be to inform that a class of flags enable warnings without explaining that
enablement is dependent on other flags.
This is just this user's feedback, do with it as you see fit. IMO, the patch
you propose is already an obvious improvement.
>From gcc-bugs-return-662063-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 23:41:40 2019
Return-Path: <gcc-bugs-return-662063-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30738 invoked by alias); 2 Dec 2019 23:41:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24223 invoked by uid 48); 2 Dec 2019 23:41:36 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92761] hash_table::expand invokes assignment on invalid objects
Date: Mon, 02 Dec 2019 23:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92761-4-RDlbhvUeGd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00133.txt.bz2
Content-length: 481
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
You don't provide a hash_traits at all so this is invalid.
>From gcc-bugs-return-662064-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 23:44:35 2019
Return-Path: <gcc-bugs-return-662064-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39835 invoked by alias); 2 Dec 2019 23:44:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39776 invoked by uid 48); 2 Dec 2019 23:44:30 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/92757] Documentation ambiguous/misleading about interplay of optimization and warning flags
Date: Mon, 02 Dec 2019 23:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: documentation, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92757-4-6iuHHDccRB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00134.txt.bz2
Content-length: 559
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Ricardo Abreu from comment #5)
> The sentence I quoted says -Wall enables a certain group of warnings, not
> flags. It goes on to characterize that group. It conveys information on its
> own, without directing to sub-flags.
Except the VERY NEXT paragraph talks about the specific sub-flags it turns on.
It seems like you're trying pretty hard to find alternative meanings which
don't actually make sense in the context.
>From gcc-bugs-return-662065-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 02 23:53:50 2019
Return-Path: <gcc-bugs-return-662065-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64385 invoked by alias); 2 Dec 2019 23:53:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64289 invoked by uid 48); 2 Dec 2019 23:53:46 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92521] [[deprecated(("string-literal"))]] accepted with extra parentheses
Date: Mon, 02 Dec 2019 23:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-92521-4-aTFt1ydAc8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00135.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92521
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-02
Ever confirmed|0 |1
>From gcc-bugs-return-662066-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 00:50:11 2019
Return-Path: <gcc-bugs-return-662066-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52468 invoked by alias); 3 Dec 2019 00:50:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52430 invoked by uid 48); 3 Dec 2019 00:50:06 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92762] New: hash_table::empty_slow invokes assignment on invalid objects
Date: Tue, 03 Dec 2019 00:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00136.txt.bz2
Content-length: 4326
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92762
Bug ID: 92762
Summary: hash_table::empty_slow invokes assignment on invalid
objects
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
A similar bug to pr92761 I ran into: The GCC internal hash_table::empty_slow()
member function invokes the assignment operator on invalid/empty elements. The
following test case inserted into the C++ parser (where I ran into the problem)
reproduces the bug:
struct S
{
S (): p (&p) { }
S (const S &s): p (&p) { gcc_assert (s.p == &s.p); }
S& operator= (const S &s) {
gcc_assert (p == &p); <<< this fails because p is null
gcc_assert (s.p == &s.p);
return *this; }
~S () { gcc_assert (p == &p); }
void *p;
};
hash_map<tree, S> x;
static void test_hash_table ()
{
for (int i = 1; i != 8; ++i)
x.put ((tree)i, S ());
x.empty ();
}
/* Parse one entire translation unit. */
void
c_parse_file (void)
{
test_hash_table ();
...
}
internal compiler error: in operator=, at cp/parser.c:43419
0xaefdf1 S::operator=(S const&)
/src/gcc/61339/gcc/cp/parser.c:43419
0xaf4c6e hash_map<tree_node*, S,
simple_hashmap_traits<default_hash_traits<tree_node*>, S>
>::hash_entry::operator=(hash_map<tree_node*, S,
simple_hashmap_traits<default_hash_traits<tree_node*>, S> >::hash_entry const&)
/src/gcc/61339/gcc/hash-map.h:42
0xaf51b6 hash_table<hash_map<tree_node*, S,
simple_hashmap_traits<default_hash_traits<tree_node*>, S> >::hash_entry, false,
xcallocator>::empty_slow()
/src/gcc/61339/gcc/hash-table.h:878
0xaf3559 hash_table<hash_map<tree_node*, S,
simple_hashmap_traits<default_hash_traits<tree_node*>, S> >::hash_entry, false,
xcallocator>::empty()
/src/gcc/61339/gcc/hash-table.h:412
0xaf1475 hash_map<tree_node*, S,
simple_hashmap_traits<default_hash_traits<tree_node*>, S> >::empty()
/src/gcc/61339/gcc/hash-map.h:237
0xaeb3ff test_hash_table
/src/gcc/61339/gcc/cp/parser.c:43475
0xaeb40b c_parse_file()
/src/gcc/61339/gcc/cp/parser.c:43483
0xcd471d c_common_parse_file()
/src/gcc/61339/gcc/c-family/c-opts.c:1185
The problem is hash_table::empty_slow () calling Descriptor::remove() on the
existing entries first, invoking their destructor, but then assigning to them
in the second loop, which invokes the copy assignment operator.
I'm not quite sure what the purpose of the assignment or the memset call below
it is supposed to be. It was introduced in r249234 to avoid the new
-Wclass-memaccess warning but that was just a stab in the dark on my part made
with the assumption that the specializations of the template on non-trivial
types with a copy ctor and copy assignment were properly tested. Clearly,
that's not the case.
template<typename Descriptor, bool Lazy,
template<typename Type> class Allocator>
void
hash_table<Descriptor, Lazy, Allocator>::empty_slow ()
{
size_t size = m_size;
size_t nsize = size;
value_type *entries = m_entries;
for (size_t i = size - 1; i < size; i--)
if (!is_empty (entries[i]) && !is_deleted (entries[i]))
Descriptor::remove (entries[i]); << destroys the element
/* Instead of clearing megabyte, downsize the table. */
if (size > 1024*1024 / sizeof (value_type))
nsize = 1024 / sizeof (value_type);
else if (too_empty_p (m_n_elements))
nsize = m_n_elements * 2;
if (nsize != size)
{
unsigned int nindex = hash_table_higher_prime_index (nsize);
nsize = prime_tab[nindex].prime;
if (!m_ggc)
Allocator <value_type> ::data_free (m_entries);
else
ggc_free (m_entries);
m_entries = alloc_entries (nsize);
m_size = nsize;
m_size_prime_index = nindex;
}
else
{
#ifndef BROKEN_VALUE_INITIALIZATION
for ( ; size; ++entries, --size)
*entries = value_type (); <<< assigns to a destroyed element
#else
memset (entries, 0, size * sizeof (value_type));
#endif
}
m_n_deleted = 0;
m_n_elements = 0;
}
>From gcc-bugs-return-662068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 00:57:13 2019
Return-Path: <gcc-bugs-return-662068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25448 invoked by alias); 3 Dec 2019 00:57:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25412 invoked by uid 48); 3 Dec 2019 00:57:08 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92761] hash_table::expand invokes assignment on invalid objects
Date: Tue, 03 Dec 2019 00:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92761-4-PnpSg1GTtd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00138.txt.bz2
Content-length: 183
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
*** Bug 92762 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-662067-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 00:57:13 2019
Return-Path: <gcc-bugs-return-662067-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25442 invoked by alias); 3 Dec 2019 00:57:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25398 invoked by uid 48); 3 Dec 2019 00:57:08 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92762] hash_table::empty_slow invokes assignment on invalid objects
Date: Tue, 03 Dec 2019 00:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92762-4-1vnZydfitc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00137.txt.bz2
Content-length: 538
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92762
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Again you did not provide the hash_trait.
PR 92761.
*** This bug has been marked as a duplicate of bug 92761 ***
>From gcc-bugs-return-662069-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 01:11:48 2019
Return-Path: <gcc-bugs-return-662069-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38707 invoked by alias); 3 Dec 2019 01:11:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38606 invoked by uid 48); 3 Dec 2019 01:11:44 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92761] hash_table::expand invokes assignment on invalid objects
Date: Tue, 03 Dec 2019 01:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status resolution
Message-ID: <bug-92761-4-l8pYgH2cu9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00139.txt.bz2
Content-length: 3480
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
Status|RESOLVED |UNCONFIRMED
Resolution|WONTFIX |---
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Andrew, please avoid closing reports of valid problems that you don't
understand.
As I explained in comment #0, the hash_table invokes the assignment operator
directly, without going through the traits class. The hash traits classes also
don't provide an "assign" function, so defining such a class is not a solution.
A test case that includes a traits class is below.
struct S
{
S (): p (&p) { }
S (const S &s): p (&p) { gcc_assert (s.p == &s.p); }
S& operator= (const S &s) {
gcc_assert (p == &p);
gcc_assert (s.p == &s.p);
return *this; }
~S () { gcc_assert (p == &p); }
void *p;
};
typedef int_hash<int, INT_MIN, 0> IntHash;
template <class T>
void destroy (T &x)
{
x.~T ();
}
template <>
struct simple_hashmap_traits<IntHash, S>
{
typedef IntHash Traits;
typedef Traits::value_type key_type;
static hashval_t hash (key_type x) { return x; }
static bool equal_keys (key_type x, key_type y) { return x == y; }
template <typename T>
static void remove (T &x)
{
Traits::remove (x.m_key);
destroy (x.m_value);
}
template <typename T>
static bool is_empty (const T &x)
{
return Traits::is_empty (x.m_key);
}
template <typename T> static bool is_deleted (const T &x)
{
return Traits::is_deleted (x.m_key);
}
template <typename T> static void mark_empty (T &x)
{
Traits::mark_empty (x.m_key);
}
template <typename T> static void mark_deleted (T &x)
{
Traits::mark_deleted (x.m_key);
}
};
hash_map<int, S, simple_hashmap_traits<IntHash, S> > x;
static void test_hash_table ()
{
for (int i = 1; i != 32; ++i)
x.put (i, S ());
x.empty ();
}
/* Parse one entire translation unit. */
void
c_parse_file (void)
{
test_hash_table ();
...
}
internal compiler error: in operator=, at cp/parser.c:43419
0xaeedd1 S::operator=(S const&)
/src/gcc/61339/gcc/cp/parser.c:43419
0xaf3bb2 hash_map<int, S, simple_hashmap_traits<int_hash<int, -2147483648, 0>,
S> >::hash_entry::operator=(hash_map<int, S,
simple_hashmap_traits<int_hash<int, -2147483648, 0>, S> >::hash_entry const&)
/src/gcc/61339/gcc/hash-map.h:42
0xaf3d58 hash_table<hash_map<int, S, simple_hashmap_traits<int_hash<int,
-2147483648, 0>, S> >::hash_entry, false, xcallocator>::expand()
/src/gcc/61339/gcc/hash-table.h:822
0xaf2259 hash_table<hash_map<int, S, simple_hashmap_traits<int_hash<int,
-2147483648, 0>, S> >::hash_entry, false, xcallocator>::find_slot_with_hash(int
const&, unsigned int, insert_option)
/src/gcc/61339/gcc/hash-table.h:971
0xaf03b1 hash_map<int, S, simple_hashmap_traits<int_hash<int, -2147483648, 0>,
S> >::put(int const&, S const&)
/src/gcc/61339/gcc/hash-map.h:165
0xaea3b9 test_hash_table
/src/gcc/61339/gcc/cp/parser.c:43477
0xaea3eb c_parse_file()
/src/gcc/61339/gcc/cp/parser.c:43487
0xcd3645 c_common_parse_file()
/src/gcc/61339/gcc/c-family/c-opts.c:1185
Please submit a full bug report,
>From gcc-bugs-return-662070-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 01:18:04 2019
Return-Path: <gcc-bugs-return-662070-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43437 invoked by alias); 3 Dec 2019 01:18:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43302 invoked by uid 48); 3 Dec 2019 01:17:59 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92761] hash_table::expand invokes assignment on invalid objects
Date: Tue, 03 Dec 2019 01:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92761-4-7ORTHMp7N5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00140.txt.bz2
Content-length: 757
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Only values are being used in the whole of GCC are all PODs. So you are the
first one who are using non-PODs.
This is now not the right place to complain about an internal data structure
working correctly for all of the inputs that are used.
If you need to use non-PODs, then you need to patch GCC to do the correct thing
instead.
>From gcc-bugs-return-662071-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 01:21:10 2019
Return-Path: <gcc-bugs-return-662071-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45883 invoked by alias); 3 Dec 2019 01:21:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45852 invoked by uid 48); 3 Dec 2019 01:21:06 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92761] hash_table::expand invokes assignment on invalid objects
Date: Tue, 03 Dec 2019 01:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92761-4-TwbdubEEt4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00141.txt.bz2
Content-length: 228
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #6)
> Only values are being used in the whole of GCC are all PODs.
>From gcc-bugs-return-662072-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 01:28:24 2019
Return-Path: <gcc-bugs-return-662072-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110387 invoked by alias); 3 Dec 2019 01:28:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109876 invoked by uid 55); 3 Dec 2019 01:28:18 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88704] Accepts invalid program with [*] outside function prototype scope.
Date: Tue, 03 Dec 2019 01:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88704-4-pGDCsZK0Q9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88704-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88704-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00142.txt.bz2
Content-length: 1116
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88704
--- Comment #4 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Author: jsm28
Date: Tue Dec 3 01:27:43 2019
New Revision: 278917
URL: https://gcc.gnu.org/viewcvs?rev=278917&root=gcc&view=rev
Log:
Diagnose use of [*] in old-style parameter definitions (PR c/88704).
GCC wrongly accepts [*] in old-style parameter definitions because
because parm_flag is set on the scope used for those definitions and,
unlike the case of a prototype in a function definition, there is no
subsequent check to disallow this invalid usage. This patch adds such
a check. (At this point we don't have location information for the
[*], so the diagnostic location isn't ideal.)
Bootstrapped with no regressions for x86_64-pc-linux-gnu.
PR c/88704
gcc/c:
* c-decl.c (store_parm_decls_oldstyle): Diagnose use of [*] in
old-style parameter definitions.
gcc/testsuite:
* gcc.dg/vla-25.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/vla-25.c
Modified:
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-decl.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662073-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 01:30:51 2019
Return-Path: <gcc-bugs-return-662073-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115327 invoked by alias); 3 Dec 2019 01:30:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115192 invoked by uid 48); 3 Dec 2019 01:30:39 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88704] Accepts invalid program with [*] outside function prototype scope.
Date: Tue, 03 Dec 2019 01:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-88704-4-20txlVhVIo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88704-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88704-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00143.txt.bz2
Content-length: 492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88704
Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.0
--- Comment #5 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Fixed for GCC 10.
>From gcc-bugs-return-662074-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 01:31:01 2019
Return-Path: <gcc-bugs-return-662074-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116169 invoked by alias); 3 Dec 2019 01:31:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116131 invoked by uid 48); 3 Dec 2019 01:30:58 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92761] hash_table::expand invokes assignment on invalid objects
Date: Tue, 03 Dec 2019 01:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92761-4-dZ3Vv3FPhJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00144.txt.bz2
Content-length: 1363
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
Again, leave bugs alone that you don't understand. Quoting from the comment in
hash-table.h:
INTRODUCTION TO TYPES
Users of the hash table generally need to be aware of three types.
...
2. The type used to describe how to handle the value type within
the hash table. This descriptor type provides the hash table with
several things.
- A typedef named 'value_type' to the value type (from above).
Provided a suitable Descriptor class it may be a user-defined,
non-POD type.
There are at least two existing uses of hash-based containers whose elements
are non-trivial types. For example in gimple-ssa-isolate-paths.c:
typedef hash_map <gimple *, args_loc_t> locmap_t;
or in attribs.c:
typedef hash_set<excl_pair, false, excl_hash_traits> exclusion_set;
Regardless, Bugzilla is exactly where change requests are tracked, whether they
are to fix bugs or make enhancements.
>From gcc-bugs-return-662075-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 01:40:23 2019
Return-Path: <gcc-bugs-return-662075-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43450 invoked by alias); 3 Dec 2019 01:40:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43354 invoked by uid 48); 3 Dec 2019 01:40:19 -0000
From: "luoxhu at cn dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92398] [10 regression] error in update of gcc.target/powerpc/pr72804.c in r277872
Date: Tue, 03 Dec 2019 01:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: luoxhu at cn dot ibm.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92398-4-uYVJ9thaGi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00145.txt.bz2
Content-length: 1412
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92398
--- Comment #9 from Xiong Hu XS Luo <luoxhu at cn dot ibm.com> ---
(In reply to seurer from comment #8)
> The changes in r278890 fix the earlier problems but introduce new ones:
>
> failures in r278889 (not seen in r278890):
> FAIL: gcc.target/powerpc/pr72804.c scan-assembler-times not 4
> FAIL: gcc.target/powerpc/pr72804.c scan-assembler-times std 2
> FAIL: gcc.target/powerpc/pr72804.c scan-assembler-not stxvd2x
> FAIL: gcc.target/powerpc/pr72804.c scan-assembler-not xxpermdi
>
> new failures in r278890:
>
> FAIL: gcc.target/powerpc/pr72804.c scan-assembler-times \\mnot\\M 2
> FAIL: gcc.target/powerpc/pr72804.c scan-assembler-not \\mlxvd2x\\M
>
> saw this on both power 8 (BE) and power 9 (LE).
Spaces are strictly required in dg, when I copied my patch to svn repo and run
"svn patch", there is conflicts with latest code in pr72804.c, the typo happens
when copy the line manually, will commit it as obvious:
diff --git a/gcc/testsuite/gcc.target/powerpc/pr72804.c
b/gcc/testsuite/gcc.target/powerpc/pr72804.c
index d424bccd5c3..38dff549210 100644
--- a/gcc/testsuite/gcc.target/powerpc/pr72804.c
+++ b/gcc/testsuite/gcc.target/powerpc/pr72804.c
@@ -1,6 +1,6 @@
/* { dg-do compile { target { lp64 } } } */
/* { dg-require-effective-target powerpc_vsx_ok } */
-/* { dg-options "-O2 -mvsx"} */
+/* { dg-options "-O2 -mvsx" } */
>From gcc-bugs-return-662076-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 01:49:59 2019
Return-Path: <gcc-bugs-return-662076-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8705 invoked by alias); 3 Dec 2019 01:49:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8281 invoked by uid 48); 3 Dec 2019 01:49:47 -0000
From: "fxue at os dot amperecomputing.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92133] Support multi versioning on self recursive function
Date: Tue, 03 Dec 2019 01:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fxue at os dot amperecomputing.com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92133-4-MfDjD2bGMs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92133-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92133-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00146.txt.bz2
Content-length: 180
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92133
--- Comment #9 from Feng Xue <fxue at os dot amperecomputing.com> ---
Ok. For any followups on this, I'll create new tracker.
>From gcc-bugs-return-662077-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 02:45:42 2019
Return-Path: <gcc-bugs-return-662077-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27653 invoked by alias); 3 Dec 2019 02:45:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27273 invoked by uid 55); 3 Dec 2019 02:45:26 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92499] nios2 backend needs to consider allocated object size, not C object size for gprel optimization
Date: Tue, 03 Dec 2019 02:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92499-4-bAIcBKyiGS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00147.txt.bz2
Content-length: 1580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92499
--- Comment #10 from sandra at gcc dot gnu.org ---
Author: sandra
Date: Tue Dec 3 02:44:41 2019
New Revision: 278919
URL: https://gcc.gnu.org/viewcvs?rev=278919&root=gcc&view=rev
Log:
2019-12-02 Sandra Loosemore <sandra@codesourcery.com>
Fix bugs relating to flexibly-sized objects in nios2 backend.
PR target/92499
gcc/c/
* c-decl.c (flexible_array_type_p): Move to common code.
gcc/
* config/nios2/nios2.c (nios2_in_small_data_p): Do not consider
objects of flexible types to be small if they have internal linkage
or are declared extern.
* config/nios2/nios2.h (ASM_OUTPUT_ALIGNED_LOCAL): Replace with...
(ASM_OUTPUT_ALIGNED_DECL_LOCAL): ...this. Use targetm.in_small_data_p
instead of the size of the object initializer.
* tree.c (flexible_array_type_p): Move from C front end, and
generalize to handle fields in non-C structures.
* tree.h (flexible_array_type_p): Declare.
gcc/testsuite/
* gcc.target/nios2/pr92499-1.c: New.
* gcc.target/nios2/pr92499-2.c: New.
* gcc.target/nios2/pr92499-3.c: New.
Modified:
branches/gcc-9-branch/gcc/ChangeLog
branches/gcc-9-branch/gcc/c/ChangeLog
branches/gcc-9-branch/gcc/c/c-decl.c
branches/gcc-9-branch/gcc/config/nios2/nios2.c
branches/gcc-9-branch/gcc/config/nios2/nios2.h
branches/gcc-9-branch/gcc/testsuite/ChangeLog
branches/gcc-9-branch/gcc/tree.c
branches/gcc-9-branch/gcc/tree.h
>From gcc-bugs-return-662078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 02:50:40 2019
Return-Path: <gcc-bugs-return-662078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33827 invoked by alias); 3 Dec 2019 02:50:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33744 invoked by uid 48); 3 Dec 2019 02:50:35 -0000
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92760] [10 regression] several vector test cases fail on power 7 after r278800
Date: Tue, 03 Dec 2019 02:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92760-4-WGszTpLWb0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00148.txt.bz2
Content-length: 822
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92760
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |segher at gcc dot gnu.org
--- Comment #1 from Kewen Lin <linkw at gcc dot gnu.org> ---
This issue exposes one interesting point, ISA 2.06 (Power7) introduces partial
support on vector doubleword, so we can exploit them in vectorization, but more
instructions support on vector doubleword origins from ISA 2.07 (Power8),
that's why we set rs6000_vector_unit[V2DImode] only under VECTOR_P8_VECTOR.
To be consistent and allow us to use limited doubleword vector support, I'd
like to update it to check VECTOR_MEM_NONE_P is none as well.
>From gcc-bugs-return-662079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 03:06:46 2019
Return-Path: <gcc-bugs-return-662079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45437 invoked by alias); 3 Dec 2019 03:06:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45352 invoked by uid 48); 3 Dec 2019 03:06:40 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92499] nios2 backend needs to consider allocated object size, not C object size for gprel optimization
Date: Tue, 03 Dec 2019 03:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92499-4-nQchOkCmHJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00149.txt.bz2
Content-length: 1318
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92499
--- Comment #11 from sandra at gcc dot gnu.org ---
I've committed a patch to fix this for nios2 only to mainline and the GCC 9
branch.
I did consider an alternate 1-line fix to target-independent code:
Index: gcc/varasm.c
===================================================================
--- gcc/varasm.c (revision 278907)
+++ gcc/varasm.c (working copy)
@@ -1201,6 +1201,7 @@ get_variable_section (tree decl, bool pr
if (ADDR_SPACE_GENERIC_P (as)
&& !DECL_THREAD_LOCAL_P (decl)
+ && !targetm.in_small_data_p (decl)
&& !(prefer_noswitch_p && targetm.have_switchable_bss_sections)
&& bss_initializer_p (decl))
{
but I am not 100% sure this will DTRT on other affected targets. On anything
that uses default_elf_select_section this will put zero-initialized data in
.sbss if targetm.in_small_data_p is true, but is that actually where it's
supposed to go? E.g., are the linker scripts set up to cope with .sbss instead
of whatever lcomm_section maps to? I think I have to defer to the other target
maintainers for what is right for their respective back ends. :-S
>From gcc-bugs-return-662080-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 03:07:47 2019
Return-Path: <gcc-bugs-return-662080-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46474 invoked by alias); 3 Dec 2019 03:07:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46441 invoked by uid 48); 3 Dec 2019 03:07:43 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/92763] New: ICE in dwarf2out_abstract_function, at dwarf2out.c:22659, or in force_type_die, at dwarf2out.c:26224
Date: Tue, 03 Dec 2019 03:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00150.txt.bz2
Content-length: 4804
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92763
Bug ID: 92763
Summary: ICE in dwarf2out_abstract_function, at
dwarf2out.c:22659, or in force_type_die, at
dwarf2out.c:26224
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
g++-10.0.0-alpha20191201 snapshot (r278886), 9.2, 8.3, 7.5 all ICE when
compiling the following testcase reduced from
libgomp/testsuite/libgomp.c++/udr-21.C w/ -O1 -fopenmp
-fno-var-tracking-assignments -g:
struct A
{
typedef int T;
#pragma omp declare reduction (y : T : [&omp_out, &omp_in]() { omp_out +=
omp_in; return 0; }()) initializer (omp_priv = [omp_orig]() { return omp_orig;
}())
static void foo ();
};
void
A::foo ()
{
int r = 0, s = 0;
#pragma omp parallel for reduction (y : r, s)
for (int i = 0; i < 1; i++)
{
}
}
% g++-10.0.0-alpha20191201 -O1 -fopenmp -fno-var-tracking-assignments -g -c
k1pjvw8c.C
during GIMPLE pass: einline
k1pjvw8c.C: In function '_ZN1A3fooEv._omp_fn.0':
k1pjvw8c.C:4:157: internal compiler error: in dwarf2out_abstract_function, at
dwarf2out.c:22659
4 | : [&omp_out, &omp_in]() { omp_out += omp_in; return 0; }()) initializer
(omp_priv = [omp_orig]() { return omp_orig; }())
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
0xb846e7 dwarf2out_abstract_function
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/dwarf2out.c:22659
0xfbd65e expand_call_inline
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree-inline.c:5182
0xfbe56c gimple_expand_calls_inline
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree-inline.c:5214
0xfbe56c optimize_inline_calls(tree_node*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree-inline.c:5356
0x17d7ec6 early_inliner(function*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/ipa-inline.c:2974
Omitting -O1 yields the following ICE instead:
% g++-10.0.0-alpha20191201 -fopenmp -fno-var-tracking-assignments -g -c
k1pjvw8c.C
during RTL pass: final
k1pjvw8c.C: In lambda function:
k1pjvw8c.C:4:95: internal compiler error: in force_type_die, at
dwarf2out.c:26224
4 | #pragma omp declare reduction (y : T : [&omp_out, &omp_in]() {
omp_out += omp_in; return 0; }()) initializer (omp_priv = [omp_orig]() { return
omp_orig; }())
|
^
0x6ad480 force_type_die
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/dwarf2out.c:26224
0xb9ea99 force_type_die
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/dwarf2out.c:26218
0xb9ea99 get_context_die
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/dwarf2out.c:26138
0xb9ea99 get_context_die
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/dwarf2out.c:26130
0xb9ea99 force_decl_die
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/dwarf2out.c:26157
0xb955dd gen_subprogram_die
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/dwarf2out.c:22914
0xb973c3 gen_decl_die
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/dwarf2out.c:26453
0xb98964 dwarf2out_decl
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/dwarf2out.c:27017
0xb9929b dwarf2out_function_decl
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/dwarf2out.c:27032
0xc167fc rest_of_handle_final
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/final.c:4694
0xc167fc execute
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/final.c:4736
>From gcc-bugs-return-662082-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 03:23:33 2019
Return-Path: <gcc-bugs-return-662082-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56098 invoked by alias); 3 Dec 2019 03:23:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56050 invoked by uid 48); 3 Dec 2019 03:23:27 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92761] hash_table::expand invokes assignment on invalid objects
Date: Tue, 03 Dec 2019 03:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-92761-4-tEpcVVxn7X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00152.txt.bz2
Content-length: 571
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-03
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #9 from Martin Sebor <msebor at gcc dot gnu.org> ---
Testing a fix.
>From gcc-bugs-return-662081-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 03:23:09 2019
Return-Path: <gcc-bugs-return-662081-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55353 invoked by alias); 3 Dec 2019 03:23:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55309 invoked by uid 48); 3 Dec 2019 03:23:03 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92762] hash_table::empty_slow invokes assignment on invalid objects
Date: Tue, 03 Dec 2019 03:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92762-4-Etcz6WXHVK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00151.txt.bz2
Content-length: 314
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92762
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
This bug is distinct from pr92761 because it's in hash_table::empty_slow() and
pr92761 is in hash_table::expand(). I expect to post a patch for both so I'm
fine with handling them together.
>From gcc-bugs-return-662083-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 05:07:26 2019
Return-Path: <gcc-bugs-return-662083-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119274 invoked by alias); 3 Dec 2019 05:07:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119212 invoked by uid 48); 3 Dec 2019 05:07:23 -0000
From: "luoxhu at cn dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92133] Support multi versioning on self recursive function
Date: Tue, 03 Dec 2019 05:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: luoxhu at cn dot ibm.com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92133-4-DEwzzWTInF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92133-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92133-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00153.txt.bz2
Content-length: 361
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92133
--- Comment #10 from Xiong Hu XS Luo <luoxhu at cn dot ibm.com> ---
(In reply to Feng Xue from comment #9)
> Ok. For any followups on this, I'll create new tracker.
Seems "--param ipa-cp-eval-threshold=0 --param large-unit-insns=20000
-fno-inline" are required to do the recursive clone for digits_2?
>From gcc-bugs-return-662084-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 05:50:03 2019
Return-Path: <gcc-bugs-return-662084-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37449 invoked by alias); 3 Dec 2019 05:50:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37358 invoked by uid 48); 3 Dec 2019 05:49:59 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/79543] Inappropriate "ld --version" checking
Date: Tue, 03 Dec 2019 05:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-79543-4-VT1Lobk04K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79543-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79543-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00154.txt.bz2
Content-length: 1833
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79543
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Chung-Lin Tang from comment #5)
> Author: cltang
> Date: Tue Sep 3 14:10:26 2019
> New Revision: 275341
>
> URL: https://gcc.gnu.org/viewcvs?rev=275341&root=gcc&view=rev
> Log:
> 2019-09-03 Chung-Lin Tang <cltang@codesourcery.com>
>
> libatomic/
> PR other/79543
> * acinclude.m4 (LIBAT_CHECK_LINKER_FEATURES): Fix GNU ld --version
> scanning to conform to the GNU Coding Standards.
> * configure: Regenerate.
>
> libffi/
> PR other/79543
> * acinclude.m4 (LIBAT_CHECK_LINKER_FEATURES): Fix GNU ld --version
> scanning to conform to the GNU Coding Standards.
> * configure: Regenerate.
>
> libgomp/
> PR other/79543
> * acinclude.m4 (LIBGOMP_CHECK_LINKER_FEATURES): Fix GNU ld --version
> scanning to conform to the GNU Coding Standards.
> * configure: Regenerate.
>
> libitm/
> PR other/79543
> * acinclude.m4 (LIBITM_CHECK_LINKER_FEATURES): Fix GNU ld --version
> scanning to conform to the GNU Coding Standards.
> * configure: Regenerate.
>
> libstdc++-v3/
> PR other/79543
> * acinclude.m4 (GLIBCXX_CHECK_LINKER_FEATURES): Fix GNU ld --version
> scanning to conform to the GNU Coding Standards.
> * configure: Regenerate.
>
>
> Modified:
> trunk/libatomic/ChangeLog
> trunk/libatomic/acinclude.m4
> trunk/libatomic/configure
> trunk/libffi/ChangeLog
> trunk/libffi/acinclude.m4
> trunk/libffi/configure
> trunk/libgomp/ChangeLog
> trunk/libgomp/acinclude.m4
> trunk/libgomp/configure
> trunk/libitm/ChangeLog
> trunk/libitm/acinclude.m4
> trunk/libitm/configure
> trunk/libstdc++-v3/ChangeLog
> trunk/libstdc++-v3/acinclude.m4
> trunk/libstdc++-v3/configure
Did this fix it?
>From gcc-bugs-return-662085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 06:15:48 2019
Return-Path: <gcc-bugs-return-662085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71308 invoked by alias); 3 Dec 2019 06:15:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71235 invoked by uid 48); 3 Dec 2019 06:15:44 -0000
From: "fxue at os dot amperecomputing.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92133] Support multi versioning on self recursive function
Date: Tue, 03 Dec 2019 06:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fxue at os dot amperecomputing.com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92133-4-09wcsx01IH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92133-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92133-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00155.txt.bz2
Content-length: 199
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92133
--- Comment #11 from Feng Xue <fxue at os dot amperecomputing.com> ---
--param ipa-cp-eval-threshold=1 -param ipcp-unit-growth=80 is enough.
>From gcc-bugs-return-662086-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 06:43:12 2019
Return-Path: <gcc-bugs-return-662086-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103481 invoked by alias); 3 Dec 2019 06:43:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103414 invoked by uid 48); 3 Dec 2019 06:43:08 -0000
From: "lutztonineubert at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92695] P1064R0 - virtual constexpr fails if object taken from array
Date: Tue, 03 Dec 2019 06:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lutztonineubert at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92695-4-UZBXr4bn4w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00156.txt.bz2
Content-length: 311
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92695
--- Comment #15 from Toni Neubert <lutztonineubert at gmail dot com> ---
I really cannot help you with this. I am sorry. I don't understand the
compilers source code/internals at all. I just can thank you guys for your
ongoing work. I really appreciate it.
>From gcc-bugs-return-662087-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 07:06:23 2019
Return-Path: <gcc-bugs-return-662087-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60856 invoked by alias); 3 Dec 2019 07:06:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60784 invoked by uid 48); 3 Dec 2019 07:06:19 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92764] New: [10 Regression] ICE in gfc_procedure_use
Date: Tue, 03 Dec 2019 07:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92764-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00157.txt.bz2
Content-length: 3076
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92764
Bug ID: 92764
Summary: [10 Regression] ICE in gfc_procedure_use
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: error-recovery, ice-on-invalid-code
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
gfortran-10.0.0-alpha20191201 snapshot (r278886) ICEs when compiling the
following testcase:
type(e6) function dn()
call sub(dn)
end function dn
% powerpc-e300c3-linux-gnu-gfortran-10.0.0-alpha20191201 -c drnzq3vo.f90
drnzq3vo.f90:1:0:
1 | type(e6) function dn()
|
Error: The type for function 'dn' at (1) is not accessible
f951: internal compiler error: Segmentation fault
0xe6bc66 crash_signal
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/toplev.c:328
0x82ff02 gfc_procedure_use(gfc_symbol*, gfc_actual_arglist**, locus*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/fortran/interface.c:3891
0x89819c resolve_specific_s0
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/fortran/resolve.c:3515
0x89819c resolve_specific_s
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/fortran/resolve.c:3535
0x89819c resolve_call
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/fortran/resolve.c:3689
0x89e943 gfc_resolve_code(gfc_code*, gfc_namespace*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/fortran/resolve.c:11872
0x8a2b4c resolve_codes
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/fortran/resolve.c:17180
0x88e8a0 gfc_resolve(gfc_namespace*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/fortran/resolve.c:17215
0x88e8a0 gfc_resolve(gfc_namespace*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/fortran/resolve.c:17194
0x8803cb resolve_all_program_units
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/fortran/parse.c:6241
0x8803cb gfc_parse_file()
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/fortran/parse.c:6488
0x8ced4e gfc_be_parse_file
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/fortran/f95-lang.c:210
(While my target here is powerpc, the ICE is not target-specific.)
>From gcc-bugs-return-662088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 07:36:51 2019
Return-Path: <gcc-bugs-return-662088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97141 invoked by alias); 3 Dec 2019 07:36:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97094 invoked by uid 55); 3 Dec 2019 07:36:46 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Tue, 03 Dec 2019 07:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92645-4-oahoGyp0ir@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00158.txt.bz2
Content-length: 537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
--- Comment #17 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Dec 3 07:36:14 2019
New Revision: 278920
URL: https://gcc.gnu.org/viewcvs?rev=278920&root=gcc&view=rev
Log:
2019-12-03 Richard Biener <rguenther@suse.de>
PR tree-optimization/92645
* tree-ssa.c (execute_update_addresses_taken): Avoid representing
a full def of a vector via a BIT_INSERT_EXPR.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/tree-ssa.c
>From gcc-bugs-return-662089-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 08:19:41 2019
Return-Path: <gcc-bugs-return-662089-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35008 invoked by alias); 3 Dec 2019 08:19:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34953 invoked by uid 55); 3 Dec 2019 08:19:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92695] P1064R0 - virtual constexpr fails if object taken from array
Date: Tue, 03 Dec 2019 08:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92695-4-m8xhUrukHf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00159.txt.bz2
Content-length: 672
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92695
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Dec 3 08:19:04 2019
New Revision: 278921
URL: https://gcc.gnu.org/viewcvs?rev=278921&root=gcc&view=rev
Log:
PR c++/92695
* constexpr.c (cxx_bind_parameters_in_call): For virtual calls,
adjust the first argument to point to the derived object rather
than its base.
* g++.dg/cpp2a/constexpr-virtual14.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-virtual14.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/constexpr.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662090-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 08:20:53 2019
Return-Path: <gcc-bugs-return-662090-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47721 invoked by alias); 3 Dec 2019 08:20:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47687 invoked by uid 55); 3 Dec 2019 08:20:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92705] [10 Regression] ICE: Segmentation fault (in build_new_op_1)
Date: Tue, 03 Dec 2019 08:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92705-4-zQkdEQC8Nn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92705-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92705-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00160.txt.bz2
Content-length: 659
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92705
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Dec 3 08:20:18 2019
New Revision: 278922
URL: https://gcc.gnu.org/viewcvs?rev=278922&root=gcc&view=rev
Log:
PR c++/92705
* call.c (strip_standard_conversion): New function.
(build_new_op_1): Use it for user_conv_p.
(compare_ics): Likewise.
(source_type): Likewise.
* g++.dg/conversion/ambig4.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/conversion/ambig4.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/call.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662091-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 08:22:06 2019
Return-Path: <gcc-bugs-return-662091-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54352 invoked by alias); 3 Dec 2019 08:22:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54304 invoked by uid 55); 3 Dec 2019 08:22:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92732] Bit-field of scoped enumeration type cannot be initialized
Date: Tue, 03 Dec 2019 08:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92732-4-eP3o4JnODj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92732-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92732-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00161.txt.bz2
Content-length: 729
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92732
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Dec 3 08:21:29 2019
New Revision: 278923
URL: https://gcc.gnu.org/viewcvs?rev=278923&root=gcc&view=rev
Log:
PR c++/92732
* typeck2.c (digest_nsdmi_init): For bitfields, use
DECL_BIT_FIELD_TYPE instead of TREE_TYPE.
* g++.dg/cpp2a/bitfield3.C: Don't expect narrowing conversion
warnings.
* g++.dg/cpp2a/bitfield4.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp2a/bitfield4.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/typeck2.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/cpp2a/bitfield3.C
>From gcc-bugs-return-662092-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 08:23:41 2019
Return-Path: <gcc-bugs-return-662092-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56103 invoked by alias); 3 Dec 2019 08:23:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56042 invoked by uid 55); 3 Dec 2019 08:23:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92744] [10 Regression] error: insn does not satisfy its constraints since r278439
Date: Tue, 03 Dec 2019 08:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92744-4-DmouQjhqp9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00162.txt.bz2
Content-length: 612
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92744
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Dec 3 08:23:06 2019
New Revision: 278924
URL: https://gcc.gnu.org/viewcvs?rev=278924&root=gcc&view=rev
Log:
PR target/92744
* config/i386/i386.md (peephole2 for *swap<mode>): Use
general_reg_operand predicates instead of register_operand.
* g++.dg/dfp/pr92744.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/dfp/pr92744.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.md
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662093-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 08:33:41 2019
Return-Path: <gcc-bugs-return-662093-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124126 invoked by alias); 3 Dec 2019 08:33:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124081 invoked by uid 48); 3 Dec 2019 08:33:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92750] DSE fails to remove all dead clobbers
Date: Tue, 03 Dec 2019 08:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92750-4-wYswCPa02e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00163.txt.bz2
Content-length: 211
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92750
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
But these are offsetted/partial clobbers, and we can't track address-taken on
parts...
>From gcc-bugs-return-662094-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 08:51:45 2019
Return-Path: <gcc-bugs-return-662094-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8325 invoked by alias); 3 Dec 2019 08:51:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8168 invoked by uid 48); 3 Dec 2019 08:51:41 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92744] [10 Regression] error: insn does not satisfy its constraints since r278439
Date: Tue, 03 Dec 2019 08:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92744-4-Y3KjIqQ2XW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00164.txt.bz2
Content-length: 437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92744
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Should be fixed now.
>From gcc-bugs-return-662095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 08:53:41 2019
Return-Path: <gcc-bugs-return-662095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10477 invoked by alias); 3 Dec 2019 08:53:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10394 invoked by uid 48); 3 Dec 2019 08:53:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92732] Bit-field of scoped enumeration type cannot be initialized
Date: Tue, 03 Dec 2019 08:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92732-4-3OfOPM2Dow@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92732-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92732-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00165.txt.bz2
Content-length: 199
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92732
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Should be fixed on the trunk now, queued for backporting to 9 and 8 branches.
>From gcc-bugs-return-662096-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 08:54:09 2019
Return-Path: <gcc-bugs-return-662096-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11437 invoked by alias); 3 Dec 2019 08:54:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11291 invoked by uid 48); 3 Dec 2019 08:54:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92705] [10 Regression] ICE: Segmentation fault (in build_new_op_1)
Date: Tue, 03 Dec 2019 08:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to
Message-ID: <bug-92705-4-0nWmkODmy7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92705-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92705-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00166.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92705
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-662097-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 08:55:47 2019
Return-Path: <gcc-bugs-return-662097-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13456 invoked by alias); 3 Dec 2019 08:55:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13406 invoked by uid 48); 3 Dec 2019 08:55:44 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92695] P1064R0 - virtual constexpr fails if object taken from array
Date: Tue, 03 Dec 2019 08:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92695-4-x75c2jGcnR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00167.txt.bz2
Content-length: 572
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92695
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Toni Neubert from comment #15)
> I really cannot help you with this. I am sorry. I don't understand the
> compilers source code/internals at all. I just can thank you guys for your
> ongoing work. I really appreciate it.
The question wasn't meant at you, but at the C++ maintainers. From my POV, all
but #c12 should be fixed now (plus Jason mentioned some issue with multiple
inheritance and constexpr virtual method call evaluation).
>From gcc-bugs-return-662098-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 08:56:05 2019
Return-Path: <gcc-bugs-return-662098-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14277 invoked by alias); 3 Dec 2019 08:56:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14193 invoked by uid 48); 3 Dec 2019 08:56:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92695] P1064R0 - virtual constexpr fails if object taken from array
Date: Tue, 03 Dec 2019 08:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-92695-4-suBWMsy5RO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00168.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92695
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Assignee|jakub at gcc dot gnu.org |unassigned at gcc dot gnu.org
>From gcc-bugs-return-662099-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:02:19 2019
Return-Path: <gcc-bugs-return-662099-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25806 invoked by alias); 3 Dec 2019 09:02:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25749 invoked by uid 48); 3 Dec 2019 09:02:16 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] New: [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 09:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00169.txt.bz2
Content-length: 1656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
Bug ID: 92765
Summary: [10 Regression] Wrong code caused by folding of
-Wstring-compare since r276773
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
I've just isolated following code snippet from tar package:
$ cat buffer.c
struct posix_header {
char magic[2];
};
union Union {
char buffer[512];
struct posix_header header;
};
union Union a;
union Union *ptr;
int main(int argc, char **argv)
{
a.buffer[0] = 'a';
a.buffer[1] = 'b';
a.buffer[2] = '\0';
if (argc != 123)
ptr = &a;
if (__builtin_strcmp(ptr->header.magic, "x") == 0
|| __builtin_strcmp(ptr->buffer + __builtin_offsetof(struct posix_header,
magic), "ab") == 0)
;
else
__builtin_abort ();
return 0;
}
$ gcc -Wstring-compare buffer.c -O2 && ./a.out
buffer.c: In function ‘main’:
buffer.c:23:10: warning: ‘__builtin_strcmp’ of a string of length 2 and an
array of size 2 evaluates to nonzero [-Wstring-compare]
23 | || __builtin_strcmp(ptr->buffer + __builtin_offsetof(struct
posix_header, magic), "ab") == 0)
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Aborted (core dumped)
$ gcc -Wstring-compare buffer.c && ./a.out
[exits with 0]
>From gcc-bugs-return-662100-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:02:52 2019
Return-Path: <gcc-bugs-return-662100-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28210 invoked by alias); 3 Dec 2019 09:02:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28171 invoked by uid 48); 3 Dec 2019 09:02:49 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 09:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cf_known_to_work assigned_to target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92765-4-cjlPlO2CMq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00170.txt.bz2
Content-length: 710
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-03
Known to work| |9.2.0
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
>From gcc-bugs-return-662101-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:03:27 2019
Return-Path: <gcc-bugs-return-662101-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29344 invoked by alias); 3 Dec 2019 09:03:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29289 invoked by uid 48); 3 Dec 2019 09:03:23 -0000
From: "bisqwit at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92766] New: [Rejects valid] pointer+0 erroneously treated as rvalue
Date: Tue, 03 Dec 2019 09:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bisqwit at iki dot fi
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00171.txt.bz2
Content-length: 1326
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92766
Bug ID: 92766
Summary: [Rejects valid] pointer+0 erroneously treated as
rvalue
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: bisqwit at iki dot fi
Target Milestone: ---
template<typename T>
void foo(T&& begin, T&& end);
void test()
{
unsigned char buffer[16];
const unsigned char* ptr = buffer;
foo(ptr+0, ptr+8);
}
On GCC 8.3, this compiles fine.
On GCC 9.1 and trunk, fails to compile (-std=c++11, c++14, c++17, c++2a):
<source>:8:21: error: no matching function for call to 'foo(const unsigned
char*&, const unsigned char*)'
8 | foo(ptr+0, ptr+8);
| ^
<source>:2:6: note: candidate: 'template<class T> void foo(T&&, T&&)'
2 | void foo(T&& begin, T&& end);
| ^~~
<source>:2:6: note: template argument deduction/substitution failed:
<source>:8:21: note: deduced conflicting types for parameter 'T' ('const
unsigned char*&' and 'const unsigned char*')
8 | foo(ptr+0, ptr+8);
| ^
Compiler returned: 1
>From gcc-bugs-return-662102-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:21:19 2019
Return-Path: <gcc-bugs-return-662102-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65188 invoked by alias); 3 Dec 2019 09:21:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65133 invoked by uid 55); 3 Dec 2019 09:21:14 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92734] Missing match.pd simplification done by fold_binary_loc on generic
Date: Tue, 03 Dec 2019 09:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: easyhack, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92734-4-PxIuctytrU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00172.txt.bz2
Content-length: 634
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92734
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Dec 3 09:20:43 2019
New Revision: 278925
URL: https://gcc.gnu.org/viewcvs?rev=278925&root=gcc&view=rev
Log:
PR tree-optimization/92734
* match.pd ((CST1 - A) +- CST2 -> CST3 - A,
CST1 - (CST2 - A) -> CST3 + A): Handle nop casts around
inner subtraction.
* gcc.dg/tree-ssa/pr92734.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr92734.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/match.pd
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662103-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:24:51 2019
Return-Path: <gcc-bugs-return-662103-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68189 invoked by alias); 3 Dec 2019 09:24:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68120 invoked by uid 48); 3 Dec 2019 09:24:44 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/91025] cpp man page incorrectly describes -MD option
Date: Tue, 03 Dec 2019 09:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-91025-4-Iii6rHE7x3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91025-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91025-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00173.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91025
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
Ever confirmed|0 |1
>From gcc-bugs-return-662104-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:25:02 2019
Return-Path: <gcc-bugs-return-662104-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69043 invoked by alias); 3 Dec 2019 09:25:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68987 invoked by uid 48); 3 Dec 2019 09:24:58 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92764] [10 Regression] ICE in gfc_procedure_use
Date: Tue, 03 Dec 2019 09:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92764-4-7YWO9pjsjX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92764-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92764-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00174.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92764
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, it's at least as old as GCC 4.8.0.
>From gcc-bugs-return-662105-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:27:05 2019
Return-Path: <gcc-bugs-return-662105-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112619 invoked by alias); 3 Dec 2019 09:27:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112510 invoked by uid 48); 3 Dec 2019 09:27:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92766] [9/10 Regression] pointer+0 erroneously treated as lvalue
Date: Tue, 03 Dec 2019 09:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc version target_milestone short_desc everconfirmed
Message-ID: <bug-92766-4-2rpdB7oQIO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92766-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00175.txt.bz2
Content-length: 960
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92766
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
CC| |dmalcolm at gcc dot gnu.org,
| |jakub at gcc dot gnu.org
Version|unknown |10.0
Target Milestone|--- |9.3
Summary|pointer+0 erroneously |[9/10 Regression] pointer+0
|treated as lvalue |erroneously treated as
| |lvalue
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This changed with r267272.
>From gcc-bugs-return-662106-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:29:43 2019
Return-Path: <gcc-bugs-return-662106-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115083 invoked by alias); 3 Dec 2019 09:29:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115024 invoked by uid 48); 3 Dec 2019 09:29:39 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92764] ICE in gfc_procedure_use
Date: Tue, 03 Dec 2019 09:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-92764-4-rI2QkaH7Ov@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92764-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92764-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00176.txt.bz2
Content-length: 500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92764
Arseny Solokha <asolokha at gmx dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[10 Regression] ICE in |ICE in gfc_procedure_use
|gfc_procedure_use |
--- Comment #2 from Arseny Solokha <asolokha at gmx dot com> ---
Not a [10 Regression], then, although I could not reproduce it w/ 8.2.0.
>From gcc-bugs-return-662107-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:31:51 2019
Return-Path: <gcc-bugs-return-662107-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123392 invoked by alias); 3 Dec 2019 09:31:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123363 invoked by uid 48); 3 Dec 2019 09:31:47 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/92763] [8/9/10 Regression] ICE in dwarf2out_abstract_function, at dwarf2out.c:22659, or in force_type_die, at dwarf2out.c:26224
Date: Tue, 03 Dec 2019 09:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-92763-4-b0Un4yah30@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00177.txt.bz2
Content-length: 1090
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92763
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
CC| |marxin at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Target Milestone|--- |8.4
Summary|ICE in |[8/9/10 Regression] ICE in
|dwarf2out_abstract_function |dwarf2out_abstract_function
|, at dwarf2out.c:22659, or |, at dwarf2out.c:22659, or
|in force_type_die, at |in force_type_die, at
|dwarf2out.c:26224 |dwarf2out.c:26224
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with Richi's r240578.
>From gcc-bugs-return-662108-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:32:07 2019
Return-Path: <gcc-bugs-return-662108-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124128 invoked by alias); 3 Dec 2019 09:32:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124079 invoked by uid 48); 3 Dec 2019 09:32:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/91025] cpp man page incorrectly describes -MD option
Date: Tue, 03 Dec 2019 09:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91025-4-RlurrB7KMy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91025-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91025-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00178.txt.bz2
Content-length: 500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91025
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Thanks! As per https://gcc.gnu.org/contribute.html#patches patches should be
sent to the mailing list for review. They get missed/ignored when attached to
bugzilla. If this is your first patch for GCC it's probably small enough to not
need a copyright assignment, although you might want to complete one anyway,
see https://gcc.gnu.org/contribute.html#legal
Thanks again.
>From gcc-bugs-return-662110-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:33:31 2019
Return-Path: <gcc-bugs-return-662110-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127222 invoked by alias); 3 Dec 2019 09:33:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127160 invoked by uid 48); 3 Dec 2019 09:33:27 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91678] [9/10 Regression] decltype returns wrong type under certain conditions
Date: Tue, 03 Dec 2019 09:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: patch, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-91678-4-J6yJlvSso0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00180.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91678
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bisqwit at iki dot fi
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 92766 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-662109-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:33:31 2019
Return-Path: <gcc-bugs-return-662109-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127217 invoked by alias); 3 Dec 2019 09:33:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127137 invoked by uid 48); 3 Dec 2019 09:33:27 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92766] [9/10 Regression] pointer+0 erroneously treated as lvalue
Date: Tue, 03 Dec 2019 09:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92766-4-IJ4AA1F2WW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92766-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00179.txt.bz2
Content-length: 535
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92766
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Looks like a dup and Marek already posted a patch.
*** This bug has been marked as a duplicate of bug 91678 ***
>From gcc-bugs-return-662111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:34:08 2019
Return-Path: <gcc-bugs-return-662111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128789 invoked by alias); 3 Dec 2019 09:34:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128734 invoked by uid 48); 3 Dec 2019 09:34:04 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92764] ICE in gfc_procedure_use
Date: Tue, 03 Dec 2019 09:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92764-4-HBxxZw0Opd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92764-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92764-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00181.txt.bz2
Content-length: 273
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92764
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Arseny Solokha from comment #2)
> Not a [10 Regression], then, although I could not reproduce it w/ 8.2.0.
8.2.0 fails as well for me.
>From gcc-bugs-return-662112-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:34:30 2019
Return-Path: <gcc-bugs-return-662112-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129898 invoked by alias); 3 Dec 2019 09:34:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129809 invoked by uid 48); 3 Dec 2019 09:34:25 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91678] [9/10 Regression] decltype returns wrong type under certain conditions
Date: Tue, 03 Dec 2019 09:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: patch, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91678-4-Dy22VOXOnW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00182.txt.bz2
Content-length: 404
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91678
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Marek, are you still working on the patch?
Does it also fix the testcase from PR 92766?
template<typename T>
void foo(T&& begin, T&& end);
void test()
{
unsigned char buffer[16];
const unsigned char* ptr = buffer;
foo(ptr+0, ptr+8);
}
>From gcc-bugs-return-662113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:38:53 2019
Return-Path: <gcc-bugs-return-662113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9954 invoked by alias); 3 Dec 2019 09:38:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9908 invoked by uid 48); 3 Dec 2019 09:38:49 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92756] [9/10 Regression] ICE in lower_omp, at omp-low.c:12988
Date: Tue, 03 Dec 2019 09:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92756-4-dq5I9vJsb9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00183.txt.bz2
Content-length: 829
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92756
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
CC| |jakub at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
Known to work| |8.3.0
Target Milestone|--- |8.4
Ever confirmed|0 |1
Known to fail| |10.0, 9.2.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r265930.
>From gcc-bugs-return-662114-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:49:13 2019
Return-Path: <gcc-bugs-return-662114-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57715 invoked by alias); 3 Dec 2019 09:49:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57668 invoked by uid 48); 3 Dec 2019 09:49:09 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92755] [10 Regression] ICE in gfc_dep_resolver, at fortran/dependency.c:2123
Date: Tue, 03 Dec 2019 09:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92755-4-Fsrf2tBQm7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92755-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00184.txt.bz2
Content-length: 814
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92755
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
CC| |marxin at gcc dot gnu.org,
| |tkoenig at gcc dot gnu.org
Known to work| |9.2.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r273807.
>From gcc-bugs-return-662115-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 09:56:05 2019
Return-Path: <gcc-bugs-return-662115-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115028 invoked by alias); 3 Dec 2019 09:56:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114967 invoked by uid 48); 3 Dec 2019 09:56:01 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92754] ICE in gfc_finish_var_decl, at fortran/trans-decl.c:693
Date: Tue, 03 Dec 2019 09:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92754-4-ieG2e9L9Qy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92754-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92754-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00185.txt.bz2
Content-length: 698
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92754
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
CC| |burnus at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r218068, it was rejected before the revision.
>From gcc-bugs-return-662117-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:00:43 2019
Return-Path: <gcc-bugs-return-662117-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14995 invoked by alias); 3 Dec 2019 10:00:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11384 invoked by uid 48); 3 Dec 2019 10:00:35 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92755] [10 Regression] ICE in gfc_dep_resolver, at fortran/dependency.c:2123
Date: Tue, 03 Dec 2019 10:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-92755-4-cT2gQi1gwt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92755-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00187.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92755
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
>From gcc-bugs-return-662116-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:00:29 2019
Return-Path: <gcc-bugs-return-662116-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10578 invoked by alias); 3 Dec 2019 10:00:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10246 invoked by uid 48); 3 Dec 2019 10:00:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBpcGEvOTI3NDldIFsxMCBSZWdyZXNzaW9uXSB3YXJuaW5nOiBpbmxp?= =?UTF-8?B?bmluZyBmYWlsZWQgaW4gY2FsbCB0byDigJhzYWxzYTIw4oCZOiAtLXBhcmFt?= =?UTF-8?B?IG1heC1pbmxpbmUtaW5zbnMtc2luZ2xlIGxpbWl0IHJlYWNoZWQgYWZ0ZXIg?= =?UTF-8?B?cjI3NjUxNg==?Date: Tue, 03 Dec 2019 10:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords short_desc
Message-ID: <bug-92749-4-JJwwEuU7u4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00186.txt.bz2
Content-length: 833
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92749
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Summary|warning: inlining failed in |[10 Regression] warning:
|call to ‘salsa20’: --param |inlining failed in call to
|max-inline-insns-single |‘salsa20’: --param
|limit reached after r276516 |max-inline-insns-single
| |limit reached after r276516
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
-Winline + -Werror is somewhat "stupid" of course.
>From gcc-bugs-return-662118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:02:41 2019
Return-Path: <gcc-bugs-return-662118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39410 invoked by alias); 3 Dec 2019 10:02:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39332 invoked by uid 48); 3 Dec 2019 10:02:37 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92753] [9/10 Regression] ICE in gfc_trans_call, at fortran/trans-stmt.c:392
Date: Tue, 03 Dec 2019 10:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work short_desc everconfirmed cf_known_to_fail
Message-ID: <bug-92753-4-Bw8Z28UKQ8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00188.txt.bz2
Content-length: 1018
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92753
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
CC| |marxin at gcc dot gnu.org,
| |pault at gcc dot gnu.org
Known to work| |8.3.0
Summary|ICE in gfc_trans_call, at |[9/10 Regression] ICE in
|fortran/trans-stmt.c:392 |gfc_trans_call, at
| |fortran/trans-stmt.c:392
Ever confirmed|0 |1
Known to fail| |10.0, 9.2.0
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r265729, it was rejected before the revision.
>From gcc-bugs-return-662119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:05:53 2019
Return-Path: <gcc-bugs-return-662119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120308 invoked by alias); 3 Dec 2019 10:05:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114887 invoked by uid 48); 3 Dec 2019 10:05:49 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92748] Two different -Wreturn-type diagnostics for essentially same code
Date: Tue, 03 Dec 2019 10:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92748-4-b5fXs8XCa4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92748-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92748-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00189.txt.bz2
Content-length: 559
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92748
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
CC| |marxin at gcc dot gnu.org,
| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-662120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:07:01 2019
Return-Path: <gcc-bugs-return-662120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47684 invoked by alias); 3 Dec 2019 10:07:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45348 invoked by uid 48); 3 Dec 2019 10:06:56 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92735] unused member variable causes code to compile for member to function for undefined function
Date: Tue, 03 Dec 2019 10:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92735-4-OKyDNwQo8e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92735-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92735-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00190.txt.bz2
Content-length: 342
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92735
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Marc Pawlowsky from comment #0)
> on a related not I sent to clang bug report where if value is not static the
> code will compile.
https://bugs.llvm.org/show_bug.cgi?id=44175 (I think that's not a bug).
>From gcc-bugs-return-662121-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:17:01 2019
Return-Path: <gcc-bugs-return-662121-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128848 invoked by alias); 3 Dec 2019 10:17:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128774 invoked by uid 48); 3 Dec 2019 10:16:57 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 10:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92765-4-6Goh8sDyFM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00191.txt.bz2
Content-length: 562
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
You don't need -Wstring-compare for that, it is miscompiled even with just -O2,
during strlen1 pass when when incorrect range for the return value of the
second strcmp is determined.
>From gcc-bugs-return-662122-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:18:04 2019
Return-Path: <gcc-bugs-return-662122-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130423 invoked by alias); 3 Dec 2019 10:18:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130233 invoked by uid 48); 3 Dec 2019 10:18:00 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92735] unused member variable causes code to compile for member to function for undefined function
Date: Tue, 03 Dec 2019 10:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92735-4-fPhxkAF0iv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92735-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92735-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00192.txt.bz2
Content-length: 796
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92735
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
For the case reported here, Clang and EDG do reject it, but I'm not yet
convinced GCC is wrong to accept it.
The implicit instantiation of is_Foo<Bad> causes:
"the implicit instantiation of the declarations, but not of the definitions, of
the non-deleted class member functions, member classes, scoped member
enumerations, static data members, member templates, and friends;"
and:
"in particular, the initialization (and any associated side effects) of a
static data member does not occur unless the static data member is itself used
in a way that requires the definition of the static data member to exist."
Nothing requires the instantiation of is_Foo<Bad>::hello.
>From gcc-bugs-return-662123-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:23:29 2019
Return-Path: <gcc-bugs-return-662123-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35644 invoked by alias); 3 Dec 2019 10:23:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34572 invoked by uid 48); 3 Dec 2019 10:23:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92758] [10 regression] r278833 breaks gcc.target/powerpc/fold-vec-splat-floatdouble.c
Date: Tue, 03 Dec 2019 10:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed
Message-ID: <bug-92758-4-oPwhkfuXCc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00193.txt.bz2
Content-length: 1443
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92758
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |powerpc
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-03
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
OK, so the testcases look like
testf_00 (__vector float x)
{
vector(4) int _1;
vector(4) int _2;
int _4;
__vector float _5;
<bb 2> :
_1 = VIEW_CONVERT_EXPR<__vector signed int>(x_3(D));
_4 = BIT_FIELD_REF <x_3(D), 32, 0>;
_2 = {_4, _4, _4, _4};
_5 = VIEW_CONVERT_EXPR<__vector float>(_2);
return _5;
which we previously optimized to
<bb 2> :
_1 = VIEW_CONVERT_EXPR<__vector signed int>(x_3(D));
_4 = BIT_FIELD_REF <x_3(D), 32, 0>;
_7 = VIEW_CONVERT_EXPR<vector(4) int>(x_3(D));
_8 = VEC_PERM_EXPR <_7, _7, { 0, 0, 0, 0 }>;
_5 = VIEW_CONVERT_EXPR<__vector float>(_8);
return _5;
so power doesn't have a special splat instruction then it seems.
I'll simply revert the change to not consider uniform vector CTORs.
>From gcc-bugs-return-662125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:25:15 2019
Return-Path: <gcc-bugs-return-662125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40700 invoked by alias); 3 Dec 2019 10:25:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39250 invoked by uid 48); 3 Dec 2019 10:25:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/92763] [8/9/10 Regression] ICE in dwarf2out_abstract_function, at dwarf2out.c:22659, or in force_type_die, at dwarf2out.c:26224
Date: Tue, 03 Dec 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-92763-4-pfbCZ1LtqX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00195.txt.bz2
Content-length: 482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92763
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
I'll eventually look into it.
>From gcc-bugs-return-662124-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:25:02 2019
Return-Path: <gcc-bugs-return-662124-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39003 invoked by alias); 3 Dec 2019 10:25:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37766 invoked by uid 48); 3 Dec 2019 10:24:28 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92760] [10 regression] several vector test cases fail on power 7 after r278800
Date: Tue, 03 Dec 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-92760-4-S5gAQlDoK4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00194.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92760
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-662126-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:29:19 2019
Return-Path: <gcc-bugs-return-662126-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46572 invoked by alias); 3 Dec 2019 10:29:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46492 invoked by uid 48); 3 Dec 2019 10:29:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92734] Missing match.pd simplification done by fold_binary_loc on generic
Date: Tue, 03 Dec 2019 10:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: easyhack, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92734-4-MHAuvWJip6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00196.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92734
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-662127-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:38:26 2019
Return-Path: <gcc-bugs-return-662127-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101307 invoked by alias); 3 Dec 2019 10:38:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101227 invoked by uid 48); 3 Dec 2019 10:38:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 10:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92765-4-tKwuk0pcMr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00197.txt.bz2
Content-length: 1201
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'd say the bug is in determine_min_objsize, which makes assumption that are
simply not valid in GIMPLE after optimizations.
Before fre3 we have:
_2 = &ptr.0_1->header.magic;
_3 = __builtin_strcmp (_2, "x");
...
_4 = &ptr.0_1->buffer;
_5 = __builtin_strcmp (_4, "ab");
but fre3 changes that to:
_2 = &ptr.0_1->header.magic;
_3 = __builtin_strcmp (_2, "x");
...
_5 = __builtin_strcmp (_2, "ab");
because it determines that _2 and _4 have the same value. They do, but
determine_min_objsize attempts to argue from this change that the strcmp will
never be true, because &ptr.0_1->header.magic is a 2 byte array in a struct
inside of union. The source didn't have such an expression there though.
So, either we change GIMPLE and claim that such properties need to be
preserved, in that case SCCVN would need to either not do that optimization
(and other passes too) or say modify the expression that is kept say to ptr.0_1
or &ptr.0_1->buffer as one that has the larger minimum object size, or
determine_min_objsize simply can't make such assumptions.
>From gcc-bugs-return-662128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:38:36 2019
Return-Path: <gcc-bugs-return-662128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102359 invoked by alias); 3 Dec 2019 10:38:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102057 invoked by uid 48); 3 Dec 2019 10:38:31 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92591] ICE in optimize_sc, at modulo-sched.c:1063
Date: Tue, 03 Dec 2019 10:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: zhroma at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92591-4-8fQXVVglu8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92591-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92591-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00198.txt.bz2
Content-length: 185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92591
--- Comment #5 from Arseny Solokha <asolokha at gmx dot com> ---
Roman, are you going to submit these patches to the mailing list?
>From gcc-bugs-return-662129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:42:44 2019
Return-Path: <gcc-bugs-return-662129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107273 invoked by alias); 3 Dec 2019 10:42:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107115 invoked by uid 48); 3 Dec 2019 10:42:36 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 10:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92765-4-AjDZBcCzrA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00199.txt.bz2
Content-length: 230
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
But isn't the case magic could be considered a variable length field since it
is st the end of the struct?
>From gcc-bugs-return-662130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:43:13 2019
Return-Path: <gcc-bugs-return-662130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108214 invoked by alias); 3 Dec 2019 10:43:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108138 invoked by uid 48); 3 Dec 2019 10:43:09 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92765-4-WCrhbMR19T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00200.txt.bz2
Content-length: 1548
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> I'd say the bug is in determine_min_objsize, which makes assumption that are
> simply not valid in GIMPLE after optimizations.
> Before fre3 we have:
> _2 = &ptr.0_1->header.magic;
> _3 = __builtin_strcmp (_2, "x");
> ...
> _4 = &ptr.0_1->buffer;
> _5 = __builtin_strcmp (_4, "ab");
> but fre3 changes that to:
> _2 = &ptr.0_1->header.magic;
> _3 = __builtin_strcmp (_2, "x");
> ...
> _5 = __builtin_strcmp (_2, "ab");
> because it determines that _2 and _4 have the same value. They do, but
> determine_min_objsize attempts to argue from this change that the strcmp
> will never be true, because &ptr.0_1->header.magic is a 2 byte array in a
> struct inside of union. The source didn't have such an expression there
> though.
> So, either we change GIMPLE and claim that such properties need to be
> preserved, in that case SCCVN would need to either not do that optimization
> (and other passes too) or say modify the expression that is kept say to
> ptr.0_1 or &ptr.0_1->buffer as one that has the larger minimum object size,
> or determine_min_objsize simply can't make such assumptions.
determine_min_objsize cannot make such assumptions (when producing answers
used for optimization rather than just warnings).
We're sort-of fencing off FRE to aid the warning machinery but only for
zero-offset components and only before IPA inlining.
>From gcc-bugs-return-662131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:45:35 2019
Return-Path: <gcc-bugs-return-662131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8156 invoked by alias); 3 Dec 2019 10:45:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7693 invoked by uid 48); 3 Dec 2019 10:45:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 10:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92765-4-4iFuCHfSit@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00201.txt.bz2
Content-length: 585
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Note, determine_min_objsize calls compute_builtin_object_size with 2 rather
than 3, which means it is in this regard conservative and uses whole object
size rather than just subobject, we've been there in the past, punt on some
optimizations before the first objsz pass and for subobject sizes compute them
early now. But the rest of determine_min_objsize, if
compute_builtin_object_size fails, ignores this and thinks it can use subobject
sizes when it can't.
>From gcc-bugs-return-662132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:47:28 2019
Return-Path: <gcc-bugs-return-662132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33576 invoked by alias); 3 Dec 2019 10:47:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33543 invoked by uid 55); 3 Dec 2019 10:47:24 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92751] VN partial def support confused about clobbers
Date: Tue, 03 Dec 2019 10:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92751-4-eOjoPgwAd1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00202.txt.bz2
Content-length: 787
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92751
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Dec 3 10:46:52 2019
New Revision: 278931
URL: https://gcc.gnu.org/viewcvs?rev=278931&root=gcc&view=rev
Log:
2019-12-03 Richard Biener <rguenther@suse.de>
PR tree-optimization/92751
* tree-ssa-sccvn.c (vn_walk_cb_data::push_partial_def): Fail
when a clobber ends up in the partial-def vector.
(vn_reference_lookup_3): Let clobbers be handled by the
assignment from CTOR handling.
* g++.dg/tree-ssa/pr92751.C: New testcase.
Added:
trunk/gcc/testsuite/g++.dg/tree-ssa/pr92751.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-sccvn.c
>From gcc-bugs-return-662134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:48:59 2019
Return-Path: <gcc-bugs-return-662134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36100 invoked by alias); 3 Dec 2019 10:48:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35914 invoked by uid 48); 3 Dec 2019 10:48:55 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Tue, 03 Dec 2019 10:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92645-4-yvP5XtdBDO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00204.txt.bz2
Content-length: 472
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
Bug 92645 depends on bug 92751, which changed state.
Bug 92751 Summary: VN partial def support confused about clobbers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92751
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-662133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 10:48:59 2019
Return-Path: <gcc-bugs-return-662133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36008 invoked by alias); 3 Dec 2019 10:48:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35905 invoked by uid 48); 3 Dec 2019 10:48:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92751] VN partial def support confused about clobbers
Date: Tue, 03 Dec 2019 10:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92751-4-Q1antl23dX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00203.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92751
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-662135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 11:01:20 2019
Return-Path: <gcc-bugs-return-662135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92391 invoked by alias); 3 Dec 2019 11:01:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90899 invoked by uid 48); 3 Dec 2019 11:00:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92765-4-iAvLzgmEgU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00205.txt.bz2
Content-length: 971
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> But isn't the case magic could be considered a variable length field since
> it is st the end of the struct?
At end of struct or not doesn't really matter.
Consider another testcase that is miscompiled because of this:
union U { struct S { char a[2]; char b[2]; char c[2]; } s; char d[6]; } u;
__attribute__((noipa)) void
bar (char *p)
{
asm volatile ("" : : "g" (p) : "memory");
}
__attribute__((noipa)) void
foo (union U *x)
{
char *p = (char *) &x->s.b;
bar (p);
if (__builtin_strcmp (&x->d[2], "cde"))
__builtin_abort ();
}
int
main ()
{
__builtin_strcpy (u.d, "abcde");
foo (&u);
return 0;
}
Note, it works if instead of using (char *) &x->s.b it uses &x->s.b[0], because
determine_min_objsize has a hack to ignore sizes of one and zero, guess it
failed too often that way.
>From gcc-bugs-return-662136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 11:11:43 2019
Return-Path: <gcc-bugs-return-662136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112762 invoked by alias); 3 Dec 2019 11:11:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112719 invoked by uid 48); 3 Dec 2019 11:11:37 -0000
From: "ricardolafabreu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/92757] Documentation ambiguous/misleading about interplay of optimization and warning flags
Date: Tue, 03 Dec 2019 11:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: documentation, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ricardolafabreu at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92757-4-UYiiTbdjRo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00206.txt.bz2
Content-length: 836
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #7 from Ricardo Abreu <ricardolafabreu at gmail dot com> ---
Yes, the very next paragraph directs to tens of other paragraphs that mention
other switches. One has to read them SFINAE mode to discover the special
meaning of the general text. That may be considered strictly correct, but it is
still not very good documentation. It is bound to mislead many readers.
Usually CLI switches aren't silently inoperative until you provide other
switches. That is a questionable UI decision to begin with, if you ask me. How
can you say that expecting a switch to actually turn something on is trying
really hard to find alternative meanings? It all seems pretty obvious really, I
am only having to try hard explaining because you are trying so hard to dismiss
it.
>From gcc-bugs-return-662137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 11:14:17 2019
Return-Path: <gcc-bugs-return-662137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92560 invoked by alias); 3 Dec 2019 11:14:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86813 invoked by uid 55); 3 Dec 2019 11:14:13 -0000
From: "nsz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/91938] libgomp (and libitm) DSOs are incorrectly built with initial-exec tls-model
Date: Tue, 03 Dec 2019 11:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nsz at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91938-4-JizHnwxCzb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91938-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91938-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00207.txt.bz2
Content-length: 806
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91938
--- Comment #5 from nsz at gcc dot gnu.org ---
Author: nsz
Date: Tue Dec 3 11:13:38 2019
New Revision: 278932
URL: https://gcc.gnu.org/viewcvs?rev=278932&root=gcc&view=rev
Log:
musl: Fix invalid tls model in libgomp and libitm PR91938
Musl does not support initial-exec tls in dynamically loaded shared
libraries.
libgomp/ChangeLog:
2019-12-03 Szabolcs Nagy <szabolcs.nagy@arm.com>
PR libgomp/91938
* configure.tgt: Avoid IE tls on *-*-musl*.
libitm/ChangeLog:
2019-12-03 Szabolcs Nagy <szabolcs.nagy@arm.com>
PR libgomp/91938
* configure.tgt: Avoid IE tls on *-*-musl*.
Modified:
trunk/libgomp/ChangeLog
trunk/libgomp/configure.tgt
trunk/libitm/ChangeLog
trunk/libitm/configure.tgt
>From gcc-bugs-return-662138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 11:18:20 2019
Return-Path: <gcc-bugs-return-662138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30674 invoked by alias); 3 Dec 2019 11:18:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30609 invoked by uid 48); 3 Dec 2019 11:18:12 -0000
From: "ricardolafabreu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/92757] Documentation ambiguous/misleading about interplay of optimization and warning flags
Date: Tue, 03 Dec 2019 11:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: documentation, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ricardolafabreu at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92757-4-zAbMLr9vHr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00208.txt.bz2
Content-length: 602
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #8 from Ricardo Abreu <ricardolafabreu at gmail dot com> ---
Don't get me wrong, I have a lot of admiration for GCC and the people behind!
It approaches perfection to a level that is very unusual in software.
Still, that does not amount to saying it is perfect. There is always margin for
improvement. What I am perceiving is that you are so used to how it is that you
immediately resist considering how it could be. You may of course decide a
suggestion is not worth the effort, but that is not the same as claiming it
invalid.
>From gcc-bugs-return-662139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 11:34:29 2019
Return-Path: <gcc-bugs-return-662139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114768 invoked by alias); 3 Dec 2019 11:34:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114694 invoked by uid 48); 3 Dec 2019 11:34:25 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92706] SRA confuses FRE
Date: Tue, 03 Dec 2019 11:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-92706-4-x52qppsEBh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92706-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92706-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00209.txt.bz2
Content-length: 382
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92706
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jamborm at gcc dot gnu.org
>From gcc-bugs-return-662140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 11:36:35 2019
Return-Path: <gcc-bugs-return-662140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116643 invoked by alias); 3 Dec 2019 11:36:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116564 invoked by uid 48); 3 Dec 2019 11:36:28 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 11:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92765-4-Rsai05BmyA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00210.txt.bz2
Content-length: 1992
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Now, determine_min_objsize has been introduced for the strcmp_eq optimization
and maybe doing something conservative for the strcmp -> ~[0, 0] or [0, 0]
optimization there like get_base_address on the ADDR_EXPR argument would not be
appropriate for that use case, if the original use case is "is there a
guarantee at least that many bytes will be actually accessible". So maybe the
bug is actually in the caller, that assumes that if determine_min_objsize
returns something small and we need to strcmp that with some larger string that
it can't be equal. That is wrong though. Say if determine_min_objsize
successfully uses compute_builtin_object_size with kind 2, on
_3 = PHI <_1, _2>
where _1 = __builtin_malloc (2); and _2 = __builtin_malloc (16);
Here, __builtin_object_size (_3, 2) is 2 and __builtin_object_size (_3, 0) is
16.
If there is __builtin_strcmp (_3, "abcd"), we can't assume it is not equal
simply because determine_min_objsize returned 2 for _3, we would need to use
(non-existent) determine_max_objsize for that.
Perhaps to determine if it should warn determine_min_objsize is acceptable,
though it likely should use both determine_min_objsize and
determine_max_objsize and differentiate between is vs. may be in the warning
(perhaps have two levels of the warning). But for code generation,
determine_min_objsize is wrong.
__attribute__((noipa)) int
bar (char *x, int y)
{
asm volatile ("" : : "g" (x), "g" (y) : "memory");
if (y == 0)
__builtin_strcpy (x, "abcd");
return y;
}
__attribute__((noipa)) char *
foo (int x)
{
char *p;
if (x)
p = __builtin_malloc (2);
else
p = __builtin_calloc (16, 1);
if (bar (p, x))
return p;
if (__builtin_strcmp (p, "abcd") != 0)
__builtin_abort ();
return p;
}
int
main ()
{
__builtin_free (foo (0));
__builtin_free (foo (1));
return 0;
}
>From gcc-bugs-return-662141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 11:49:01 2019
Return-Path: <gcc-bugs-return-662141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42188 invoked by alias); 3 Dec 2019 11:48:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36612 invoked by uid 48); 3 Dec 2019 11:48:33 -0000
From: "tangyixuan at mail dot dlut.edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91839] missing error diagnosis for undeclared identifier
Date: Tue, 03 Dec 2019 11:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tangyixuan at mail dot dlut.edu.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91839-4-UesdGWiSs2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91839-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91839-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00211.txt.bz2
Content-length: 1305
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91839
--- Comment #3 from tangyixuan <tangyixuan at mail dot dlut.edu.cn> ---
(In reply to Jonathan Wakely from comment #2)
> I can confirm GCC doesn't suggest l_24, but I'm not sure it's reasonable to
> expect it to do so after so many parse errors.
>
> If you fix the first two errors then you do get it:
>
> 91839.c:6:10: error: ‘l_2’ undeclared (first use in this function); did you
> mean ‘l_24’?
> 6 | return l_2[0]; //error
> | ^~~
> | l_24
>
>
> Your code is ill-formed. GCC tells you it's ill-formed. I don't see a bug
> here.
Hi, thanks for your reply.
Error handler should not stop at the first error and report the errors as many
as possible.
When there are two errors in code, the second error of undeclared ‘b’ is
ignored:
static int f1(void; //error
static int f1(void)
{
return b; //error
}
$gcc -c s.c
s.c:2:13: error: storage class specified for parameter ‘f1’
2 | static int f1(void)
| ^~
s.c:3:1: error: expected ‘;’, ‘,’ or ‘)’ before ‘{’ token
3 | {
|
Maybe it could be improved at some extent.
>From gcc-bugs-return-662142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 11:59:53 2019
Return-Path: <gcc-bugs-return-662142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55698 invoked by alias); 3 Dec 2019 11:59:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55650 invoked by uid 55); 3 Dec 2019 11:59:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Tue, 03 Dec 2019 11:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92645-4-jviitZCvht@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00212.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
--- Comment #18 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Dec 3 11:59:13 2019
New Revision: 278934
URL: https://gcc.gnu.org/viewcvs?rev=278934&root=gcc&view=rev
Log:
2019-12-03 Richard Biener <rguenther@suse.de>
PR tree-optimization/92645
* gimple-fold.c (gimple_fold_builtin_memory_op): Fold memcpy
from or to a properly aligned register variable.
* gcc.target/i386/pr92645-5.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr92645-5.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/gimple-fold.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 12:12:44 2019
Return-Path: <gcc-bugs-return-662143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99774 invoked by alias); 3 Dec 2019 12:12:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99706 invoked by uid 48); 3 Dec 2019 12:12:38 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92734] Missing match.pd simplification done by fold_binary_loc on generic
Date: Tue, 03 Dec 2019 12:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: easyhack, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92734-4-QdH873iDIE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00213.txt.bz2
Content-length: 673
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92734
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'm wondering if we shouldn't adjust also the
/* (A +- B) - A -> +- B */
/* (A +- B) -+ B -> A */
/* A - (A +- B) -> -+ B */
/* A +- (B -+ A) -> +- B */
patterns. Say testcases like:
int
f1 (int x, unsigned y)
{
return (int) (x + y) - x;
}
int
f2 (int x, unsigned y)
{
int a = x + y;
return a - x;
}
aren't really optimized ATM until combine. And they aren't really optimized
even with -fwrapv until combine, so the "turn on -fwrapv late in GIMPLE and
redoce a few optimizations" proposal wouldn't solve that.
>From gcc-bugs-return-662144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 12:12:58 2019
Return-Path: <gcc-bugs-return-662144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100490 invoked by alias); 3 Dec 2019 12:12:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100418 invoked by uid 48); 3 Dec 2019 12:12:51 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/92757] Documentation ambiguous/misleading about interplay of optimization and warning flags
Date: Tue, 03 Dec 2019 12:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: documentation, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92757-4-6JbxdKcvCa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00214.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Ricardo Abreu from comment #7)
> Usually CLI switches aren't silently inoperative until you provide other
> switches.
Usually CLI applications don't have as many switches as GCC with as many
non-trivial interactions between them.
Also see https://gcc.gnu.org/wiki/FAQ#optimization-options
>From gcc-bugs-return-662145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 12:17:21 2019
Return-Path: <gcc-bugs-return-662145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111746 invoked by alias); 3 Dec 2019 12:17:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 111711 invoked by uid 48); 3 Dec 2019 12:17:16 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91839] missing error diagnosis for undeclared identifier
Date: Tue, 03 Dec 2019 12:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_severity
Message-ID: <bug-91839-4-LTqm0OeEJu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91839-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91839-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00215.txt.bz2
Content-length: 299
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91839
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
>From gcc-bugs-return-662146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 12:22:56 2019
Return-Path: <gcc-bugs-return-662146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116405 invoked by alias); 3 Dec 2019 12:22:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116352 invoked by uid 48); 3 Dec 2019 12:22:51 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92767] New: [m68k]: Random ICE: verify_flow_info failed
Date: Tue, 03 Dec 2019 12:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_file_loc bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget
Message-ID: <bug-92767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00216.txt.bz2
Content-length: 3039
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92767
Bug ID: 92767
Summary: [m68k]: Random ICE: verify_flow_info failed
Product: gcc
Version: 10.0
URL: https://buildd.debian.org/status/fetch.php?pkg=gcc-sna
pshot&arch=m68k&ver=1%3A20191130-1&stamp=1575330554&ra
w=0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: glaubitz at physik dot fu-berlin.de
CC: bernds at gcc dot gnu.org, schwab at gcc dot gnu.org
Target Milestone: ---
Target: m68k-*-*
Trying a full bootstrap with gm2 enabled on m68k, the build fails with an
internal compiler error:
GCC_FOR_TARGET /<<PKGBUILDDIR>>/build/./gcc/xgcc
-B/<<PKGBUILDDIR>>/build/./gcc/
bash ../../src/gcc/m2/tools-src/makeSystem -fpim \
../../src/gcc/m2/gm2-libs/SYSTEM.def \
../../src/gcc/m2/gm2-libs/SYSTEM.mod \
-I../../src/gcc/m2/gm2-libs \
"/<<PKGBUILDDIR>>/build/./gcc/xgm2
-B/<<PKGBUILDDIR>>/build/./gcc/"
/<<PKGBUILDDIR>>/build/gcc/m2/gm2-libs/SYSTEM.def
../../src/gcc/m2/gm2-libs/SYSTEM.mod: In function 'ShiftVal':
../../src/gcc/m2/gm2-libs/SYSTEM.mod:89:1: error: verify_flow_info: Wrong count
of block 23
89 | END ShiftVal ;
| ^~~
../../src/gcc/m2/gm2-libs/SYSTEM.mod:89:1: error: verify_flow_info: Wrong count
of block 22
during RTL pass: outof_cfglayout
../../src/gcc/m2/gm2-libs/SYSTEM.mod:89:1: internal compiler error:
verify_flow_info failed
mmap: Permission denied
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-snapshot/README.Bugs> for instructions.
But even with gm2 disabled, the issue shows at other places:
../../../src/libgomp/target.c: In function 'gomp_map_vars':
../../../src/libgomp/target.c:1052:1: error: verify_flow_info: Wrong count of
block 110
1052 | }
| ^
../../../src/libgomp/target.c:1052:1: error: verify_flow_info: Wrong count of
block 42
during RTL pass: expand
../../../src/libgomp/target.c:1052:1: internal compiler error: verify_flow_info
failed
mmap: Permission denied
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-snapshot/README.Bugs> for instructions.
From:
https://buildd.debian.org/status/fetch.php?pkg=gcc-snapshot&arch=m68k&ver=1%3A20190719-1&stamp=1563578948&raw=0
It seems the issue was introduced between r271016 and r271670 when comparing
the Debian builds at:
> https://buildd.debian.org/status/logs.php?pkg=gcc-snapshot&arch=m68k
Last successful build with snapshot version (20190508, r271016) and first
unsuccessful build with snapshot version (20190527, r271670).
The issue is older than the MODE_CC conversion recently performed on the m68k
backend.
I will perform some more testing to find out whether this issue might be
Debian-specific.
>From gcc-bugs-return-662148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 12:55:33 2019
Return-Path: <gcc-bugs-return-662148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113269 invoked by alias); 3 Dec 2019 12:55:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113226 invoked by uid 48); 3 Dec 2019 12:55:28 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91678] [9/10 Regression] decltype returns wrong type under certain conditions
Date: Tue, 03 Dec 2019 12:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: patch, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91678-4-hPxleSNUSc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00218.txt.bz2
Content-length: 283
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91678
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Sorry, I'll try to respond to
https://gcc.gnu.org/ml/gcc-patches/2019-09/msg01042.html
soon.
It doesn't seem to fix Comment 4 though, will have to look why :/.
>From gcc-bugs-return-662147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 12:55:08 2019
Return-Path: <gcc-bugs-return-662147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112481 invoked by alias); 3 Dec 2019 12:55:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112400 invoked by uid 48); 3 Dec 2019 12:55:01 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] New: Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 12:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00217.txt.bz2
Content-length: 3301
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
Bug ID: 92768
Summary: Maybe a wrong code for vector constants
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
I have a test-case from graphene package that started to fail with r273194:
$ cat matrix.c
#include <xmmintrin.h>
#define GRAPHENE_ALIGN16 __attribute__((aligned(16)))
typedef int v4si __attribute__((vector_size(16)));
typedef float v4sf __attribute__((vector_size(16)));
typedef __m128 graphene_simd4f_t;
typedef struct {
int f[4];
} graphene_simd4f_uif_t;
__m128
graphene_simd4x4f_inverse(__m128 r1_sum)
{
const graphene_simd4f_uif_t __pnpn = { {0x00000000, 0x80000000, 0x00000000,
0x80000000}};
return (graphene_simd4f_t) _mm_xor_ps((r1_sum), _mm_load_ps(__pnpn.f));
}
int main()
{
__m128 a = { -1.0f, -1.0f, -1.0f, -1.0f };
if (graphene_simd4x4f_inverse (a)[1] != 1.0)
__builtin_abort ();
return 0;
}
$ gcc -O2 matrix.c -ffast-math && ./a.out
matrix.c: In function ‘graphene_simd4x4f_inverse’:
matrix.c:17:69: warning: passing argument 1 of ‘_mm_load_ps’ from incompatible
pointer type [-Wincompatible-pointer-types]
17 | return (graphene_simd4f_t) _mm_xor_ps((r1_sum),
_mm_load_ps(__pnpn.f));
| ~~~~~~^~
| |
|
const int *
In file included from matrix.c:1:
/home/marxin/bin/gcc2/lib64/gcc/x86_64-pc-linux-gnu/10.0.0/include/xmmintrin.h:925:27:
note: expected ‘const float *’ but argument is of type ‘const int *’
925 | _mm_load_ps (float const *__P)
| ~~~~~~~~~~~~~^~~
Aborted (core dumped)
But without -ffast-math it's fine:
$ gcc -O2 matrix.c && ./a.out
matrix.c: In function ‘graphene_simd4x4f_inverse’:
matrix.c:17:69: warning: passing argument 1 of ‘_mm_load_ps’ from incompatible
pointer type [-Wincompatible-pointer-types]
17 | return (graphene_simd4f_t) _mm_xor_ps((r1_sum),
_mm_load_ps(__pnpn.f));
| ~~~~~~^~
| |
|
const int *
In file included from matrix.c:1:
/home/marxin/bin/gcc2/lib64/gcc/x86_64-pc-linux-gnu/10.0.0/include/xmmintrin.h:925:27:
note: expected ‘const float *’ but argument is of type ‘const int *’
925 | _mm_load_ps (float const *__P)
| ~~~~~~~~~~~~~^~~
>From gcc-bugs-return-662149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 12:56:04 2019
Return-Path: <gcc-bugs-return-662149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114059 invoked by alias); 3 Dec 2019 12:56:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114016 invoked by uid 48); 3 Dec 2019 12:55:58 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 12:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92768-4-1bzVZbx9JC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00219.txt.bz2
Content-length: 683
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
clang seems to be happy with -ffast-math:
$ clang -O2 matrix.c -ffast-math && ./a.out
matrix.c:17:63: warning: incompatible pointer types passing 'int const[4]' to
parameter of type 'const float *' [-Wincompatible-pointer-types]
return (graphene_simd4f_t) _mm_xor_ps((r1_sum), _mm_load_ps(__pnpn.f));
^~~~~~~~
/usr/lib64/clang/9.0.0/include/xmmintrin.h:1723:26: note: passing argument to
parameter '__p' here
_mm_load_ps(const float *__p)
^
1 warning generated.
>From gcc-bugs-return-662150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:01:02 2019
Return-Path: <gcc-bugs-return-662150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10701 invoked by alias); 3 Dec 2019 13:00:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10081 invoked by uid 48); 3 Dec 2019 13:00:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92734] Missing match.pd simplification done by fold_binary_loc on generic
Date: Tue, 03 Dec 2019 13:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: easyhack, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92734-4-8g1kgFXLLX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00220.txt.bz2
Content-length: 279
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92734
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47406
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47406&action=edit
gcc10-pr92734-2.patch
Untested patch that implements that.
>From gcc-bugs-return-662151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:07:53 2019
Return-Path: <gcc-bugs-return-662151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23750 invoked by alias); 3 Dec 2019 13:07:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23671 invoked by uid 48); 3 Dec 2019 13:07:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 13:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status target_milestone short_desc everconfirmed
Message-ID: <bug-92768-4-l0uBiUNvLG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00221.txt.bz2
Content-length: 1421
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-bisection
Status|UNCONFIRMED |NEW
Target Milestone|--- |8.4
Summary|[10 Regression] Maybe a |[8/9/10 Regression] Maybe a
|wrong code for vector |wrong code for vector
|constants |constants
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Testcase already failing with GCC 8 (but not GCC 7 appearantly):
#include <xmmintrin.h>
typedef int v4si __attribute__((vector_size(16)));
typedef float v4sf __attribute__((vector_size(16)));
__m128
graphene_simd4x4f_inverse(__m128 r1_sum)
{
v4si temi = (v4si) {0x00000000, 0x80000000, 0x00000000, 0x80000000};
v4sf temf = (v4sf) temi;
return (__m128) _mm_xor_ps((r1_sum), temf);
}
int main()
{
__m128 a = { -1.0f, -1.0f, -1.0f, -1.0f };
if (graphene_simd4x4f_inverse (a)[1] != 1.0)
__builtin_abort ();
return 0;
}
somehow we are "normalizing" FP numbers in constant folding, losing the signed
zeros. That worked in GCC 7.
Guess we can bisect that.
>From gcc-bugs-return-662152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:11:33 2019
Return-Path: <gcc-bugs-return-662152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28508 invoked by alias); 3 Dec 2019 13:11:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27897 invoked by uid 48); 3 Dec 2019 13:11:28 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 13:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92768-4-5yvsMDt4RL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00222.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Slightly cleaned up testcase:
#include <xmmintrin.h>
struct S { int f[4]; };
__m128
foo (__m128 x)
{
const struct S a = { {0x00000000, 0x80000000, 0x00000000, 0x80000000}};
return _mm_xor_ps (x, _mm_load_ps ((float *) a.f));
}
int
main ()
{
__m128 a = { -1.0f, -1.0f, -1.0f, -1.0f };
if (foo (a)[1] != 1.0)
__builtin_abort ();
return 0;
}
>From gcc-bugs-return-662153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:17:49 2019
Return-Path: <gcc-bugs-return-662153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50569 invoked by alias); 3 Dec 2019 13:17:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50509 invoked by uid 48); 3 Dec 2019 13:17:44 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 13:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92768-4-QQu7yrMPKs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00223.txt.bz2
Content-length: 412
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rsandifo at gcc dot gnu.org
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r255474.
>From gcc-bugs-return-662154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:18:28 2019
Return-Path: <gcc-bugs-return-662154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55583 invoked by alias); 3 Dec 2019 13:18:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55497 invoked by uid 48); 3 Dec 2019 13:18:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 13:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92768-4-CnhNOKfAaO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00224.txt.bz2
Content-length: 609
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Even more reduced:
#include <xmmintrin.h>
__m128
foo (__m128 x)
{
int f[4] __attribute__((aligned (16)))
= { 0x00000000, 0x80000000, 0x00000000, 0x80000000 };
return _mm_xor_ps (x, *(__m128 *) f);
}
int
main ()
{
__m128 a = { -1.0f, -1.0f, -1.0f, -1.0f };
if (foo (a)[1] != 1.0)
__builtin_abort ();
return 0;
}
Though, with -fno-signed-zeros, we say that the sign of a zero isn't
significant, but for this testcase it is very much significant.
So, maybe invalid?
>From gcc-bugs-return-662155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:18:30 2019
Return-Path: <gcc-bugs-return-662155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55784 invoked by alias); 3 Dec 2019 13:18:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55534 invoked by uid 48); 3 Dec 2019 13:18:26 -0000
From: "christophe.leroy@c-s.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92769] New: No way to set CR0[SO] on function return
Date: Tue, 03 Dec 2019 13:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christophe.leroy@c-s.fr
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92769-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00225.txt.bz2
Content-length: 924
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92769
Bug ID: 92769
Summary: No way to set CR0[SO] on function return
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: christophe.leroy@c-s.fr
Target Milestone: ---
Linux system calls and Linux VDSO calls require the error status to be
reflected through SO bit of CR0 register on function return.
There is no way to do that from C functions. This requires to add Assembly
trampoline functions just for that, with all associated drawbacks (adding a
stack frame to save LR, etc ...)
Would it be possible to add to builtin-functions which would set/clear SO on
function return ?
Something like:
- __builtin_ppc_return_with_so_set()
- __builtin_ppc_return_with_so_cleared()
>From gcc-bugs-return-662156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:19:24 2019
Return-Path: <gcc-bugs-return-662156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61610 invoked by alias); 3 Dec 2019 13:19:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57441 invoked by uid 48); 3 Dec 2019 13:19:19 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 13:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92768-4-Alh95wK93c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00226.txt.bz2
Content-length: 222
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Possibly the ->equal_p () use in vector-builder elides the -0.0 since it
may appear "equal" to 0.0?
>From gcc-bugs-return-662157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:22:21 2019
Return-Path: <gcc-bugs-return-662157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64228 invoked by alias); 3 Dec 2019 13:22:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64191 invoked by uid 48); 3 Dec 2019 13:22:17 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 13:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92768-4-fOHDcPTpUi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00227.txt.bz2
Content-length: 1094
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #5)
> Even more reduced:
> #include <xmmintrin.h>
>
> __m128
> foo (__m128 x)
> {
> int f[4] __attribute__((aligned (16)))
> = { 0x00000000, 0x80000000, 0x00000000, 0x80000000 };
> return _mm_xor_ps (x, *(__m128 *) f);
> }
>
> int
> main ()
> {
> __m128 a = { -1.0f, -1.0f, -1.0f, -1.0f };
> if (foo (a)[1] != 1.0)
> __builtin_abort ();
> return 0;
> }
>
> Though, with -fno-signed-zeros, we say that the sign of a zero isn't
> significant, but for this testcase it is very much significant.
> So, maybe invalid?
Well, clearly the testcase simply loads a vector which we do not expect
to alter bit-patterns.
The issue is that besides the new vector encoder stuff, that
native_interpret_expr can end up "normalizing" a FP number as well.
Note that various intrinsic docs suggest to use the matching
xor_ps variant if the main work is on float vectors while xor_pd
when working on integer vectors.
>From gcc-bugs-return-662158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:29:07 2019
Return-Path: <gcc-bugs-return-662158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16640 invoked by alias); 3 Dec 2019 13:29:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16591 invoked by uid 48); 3 Dec 2019 13:29:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92214] Unhelpful diagnostic for static_assert( some_concept(some_type) )
Date: Tue, 03 Dec 2019 13:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_severity
Message-ID: <bug-92214-4-3J8FIaJYO9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92214-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92214-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00228.txt.bz2
Content-length: 299
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92214
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
>From gcc-bugs-return-662159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:46:52 2019
Return-Path: <gcc-bugs-return-662159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44896 invoked by alias); 3 Dec 2019 13:46:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44823 invoked by uid 48); 3 Dec 2019 13:46:44 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 13:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92768-4-jqSETcKqLp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00229.txt.bz2
Content-length: 882
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #8 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Previously, in PR 86999 I pointed out to the reporter that it was okay for gcc
to turn a vector constructor with negative zeros to a trivial
all-positive-zeros constructor under -fno-signed-zeros, and nobody contradicted
me at the time.
I think the documentation needs to be clarified if that's not the intent, right
now I cannot for sure deduce from the manual what exactly the optimizations may
or may not do when constant propagation or such produces a "negative zero"
value.
>From gcc-bugs-return-662160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:47:13 2019
Return-Path: <gcc-bugs-return-662160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45781 invoked by alias); 3 Dec 2019 13:47:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45729 invoked by uid 48); 3 Dec 2019 13:47:08 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 13:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-92768-4-YBmEZyJisU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00230.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot gnu.org
--- Comment #9 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-662161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:51:53 2019
Return-Path: <gcc-bugs-return-662161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81477 invoked by alias); 3 Dec 2019 13:51:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81311 invoked by uid 48); 3 Dec 2019 13:51:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 13:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92768-4-ZGx4TBuI50@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00231.txt.bz2
Content-length: 930
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The vector builder calls operand_equal_p, which in turn does:
case REAL_CST:
if (real_identical (&TREE_REAL_CST (arg0), &TREE_REAL_CST (arg1)))
return true;
if (!HONOR_SIGNED_ZEROS (arg0))
{
/* If we do not distinguish between signed and unsigned zero,
consider them equal. */
if (real_zerop (arg0) && real_zerop (arg1))
return true;
}
return false;
So, what could be done is temporarily enable flag_signed_zeros in the vector
builder.
>From gcc-bugs-return-662162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:51:53 2019
Return-Path: <gcc-bugs-return-662162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81485 invoked by alias); 3 Dec 2019 13:51:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81335 invoked by uid 48); 3 Dec 2019 13:51:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81202] Concept parsing error for default template arguments
Date: Tue, 03 Dec 2019 13:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on blocked everconfirmed
Message-ID: <bug-81202-4-BdV68tBm1V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81202-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81202-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00232.txt.bz2
Content-length: 1874
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81202
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
Blocks| |67491
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Your spacebar seems to be broken, and your testcase is incomplete ("tple"?!)
Fixed:
template<class T, class AT = void>
constexpr bool IsPtrC = true;
template<class T, class AT = void> concept bool IsPtrC2 = IsPtrC<T, AT>;
template<bool B> using TEST = int;
TEST<IsPtrC<int>> i; // OK
TEST<IsPtrC2<int>> j; // error: parse error in template argument list
TEST<IsPtrC2<int, void>> k; // OK
TEST<(IsPtrC2<int>)> l; // OK
This is still rejected by current versions of GCC with -std=gnu++17 -fconcepts.
With GCC 8 and 9:
81202.cc:9:1: error: parse error in template argument list
9 | TEST<IsPtrC2<int>> j; // error: parse error in template argument
list
| ^~~~~~~~~~~~~~~~~~~~
81202.cc:9:1: error: declaration does not declare anything [-fpermissive]
And with trunk:
81202.cc:9:17: error: type/value mismatch at argument 1 in template parameter
list for 'template<bool B> using TEST = int'
9 | TEST<IsPtrC2<int>> j; // error: parse error in template argument
list
| ^~
81202.cc:9:17: note: expected a constant of type 'bool', got 'auto [requires
IsPtrC2<<placeholder>, int>]'
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67491
[Bug 67491] [meta-bug] concepts issues
>From gcc-bugs-return-662163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:53:34 2019
Return-Path: <gcc-bugs-return-662163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83367 invoked by alias); 3 Dec 2019 13:53:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83329 invoked by uid 48); 3 Dec 2019 13:53:29 -0000
From: "raphael.kubo.da.costa at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92770] New: std::unordered_map<T, U> requires both T and U to be fully declared
Date: Tue, 03 Dec 2019 13:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: raphael.kubo.da.costa at intel dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92770-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00233.txt.bz2
Content-length: 2445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92770
Bug ID: 92770
Summary: std::unordered_map<T, U> requires both T and U to be
fully declared
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: raphael.kubo.da.costa at intel dot com
Target Milestone: ---
$ cat unordered_map.cc
#include <unordered_map>
struct S;
class C {
std::unordered_map<S, int> map_;
};
$ g++ -std=gnu++14 -c unordered_map.cc
In file included from /usr/include/c++/9/unordered_map:43,
from unordered_map.cc:1:
/usr/include/c++/9/bits/stl_pair.h: In instantiation of ‘struct std::pair<const
S, int>’:
/usr/include/c++/9/ext/aligned_buffer.h:91:28: required from ‘struct
__gnu_cxx::__aligned_buffer<std::pair<const S, int> >’
/usr/include/c++/9/bits/hashtable_policy.h:233:43: required from ‘struct
std::__detail::_Hash_node_value_base<std::pair<const S, int> >’
/usr/include/c++/9/bits/hashtable_policy.h:264:12: required from ‘struct
std::__detail::_Hash_node<std::pair<const S, int>, true>’
/usr/include/c++/9/bits/hashtable_policy.h:2027:13: required from ‘struct
std::__detail::_Hashtable_alloc<std::allocator<std::__detail::_Hash_node<std::pair<const
S, int>, true> > >’
/usr/include/c++/9/bits/hashtable.h:173:11: required from ‘class
std::_Hashtable<S, std::pair<const S, int>, std::allocator<std::pair<const S,
int> >, std::__detail::_Select1st, std::equal_to<S>, std::hash<S>,
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash,
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<true,
false, true> >’
/usr/include/c++/9/bits/unordered_map.h:105:18: required from ‘class
std::unordered_map<S, int>’
unordered_map.cc:4:30: required from here
/usr/include/c++/9/bits/stl_pair.h:214:11: error: ‘std::pair<_T1, _T2>::first’
has incomplete type
214 | _T1 first; /// @c first is a copy of the first
object
| ^~~~~
unordered_map.cc:2:8: note: forward declaration of ‘struct S’
2 | struct S;
|
The excerpt above works fine with libc++ and MSVC's STL.
>From gcc-bugs-return-662164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 13:55:02 2019
Return-Path: <gcc-bugs-return-662164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87102 invoked by alias); 3 Dec 2019 13:55:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86724 invoked by uid 48); 3 Dec 2019 13:54:58 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92771] New: [9/10 Regression] Concept won't use default template argument
Date: Tue, 03 Dec 2019 13:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc blocked target_milestone
Message-ID: <bug-92771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00234.txt.bz2
Content-length: 1600
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92771
Bug ID: 92771
Summary: [9/10 Regression] Concept won't use default template
argument
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
CC: paolo at gcc dot gnu.org
Blocks: 67491
Target Milestone: ---
template<typename P, typename Q, typename Arghhh = void>
concept three = sizeof(P) == sizeof(Q);
#ifdef WORKAROUND
template<typename P, typename Q>
concept two = three<P, Q>;
#define three two
#endif
template<typename T, typename U>
constexpr auto
foo(const T& t, const U& u)
{
if constexpr (three<T, U>)
return &t == &u;
return false;
}
int main()
{
return foo(1, 2);
}
Using -std=gnu++2a this fails to compile:
c3.cc: In function 'constexpr auto foo(const T&, const U&)':
c3.cc:14:17: error: expected 'auto' or 'decltype(auto)' after 'three<T, U>'
14 | if constexpr (three<T, U>)
| ^~~~~~~~~~~
c3.cc:14:28: error: expected unqualified-id before ')' token
14 | if constexpr (three<T, U>)
| ^
Defining WORKAROUND to add the indirection through 'two' fixes it.
This was accepted prior to r260482 (which was fixing PR c++/84588).
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67491
[Bug 67491] [meta-bug] concepts issues
>From gcc-bugs-return-662165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:05:46 2019
Return-Path: <gcc-bugs-return-662165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102253 invoked by alias); 3 Dec 2019 14:05:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102183 invoked by uid 48); 3 Dec 2019 14:05:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92771] [9/10 Regression] Concept won't use default template argument
Date: Tue, 03 Dec 2019 14:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work everconfirmed cf_known_to_fail
Message-ID: <bug-92771-4-S0uWMC5u4p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00235.txt.bz2
Content-length: 532
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92771
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
Known to work| |8.3.1
Ever confirmed|0 |1
Known to fail| |10.0, 9.1.0, 9.2.0, 9.2.1
>From gcc-bugs-return-662166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:15:48 2019
Return-Path: <gcc-bugs-return-662166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127389 invoked by alias); 3 Dec 2019 14:15:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127212 invoked by uid 48); 3 Dec 2019 14:15:33 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92771] [9/10 Regression] Concept won't use default template argument
Date: Tue, 03 Dec 2019 14:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92771-4-JRpFxhNbOL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00236.txt.bz2
Content-length: 1024
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92771
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Reduced:
template<typename P, typename Arghhh = void>
concept one_or_two = true;
template<typename P>
concept one = one_or_two<P>;
template<typename T>
constexpr void
foo()
{
if (one<T>) // OK
{ }
if (one_or_two<T>) // ERROR
{ }
}
gcc-8-branch accepts this with -fconcepts.
gcc-9-branch rejects it with -fconcepts
92771.cc: In function 'constexpr void foo()':
92771.cc:14:20: error: expected unqualified-id before ')' token
14 | if (one_or_two<T>) // ERROR
| ^
trunk accepts with -fconcepts (?!?) but not with -std=gnu++2a:
92771.cc: In function 'constexpr void foo()':
92771.cc:14:7: error: expected 'auto' or 'decltype(auto)' after 'one_or_two<T>'
14 | if (one_or_two<T>) // ERROR
| ^~~~~~~~~~~~~
92771.cc:14:20: error: expected unqualified-id before ')' token
14 | if (one_or_two<T>) // ERROR
| ^
>From gcc-bugs-return-662167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:22:13 2019
Return-Path: <gcc-bugs-return-662167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10699 invoked by alias); 3 Dec 2019 14:22:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10671 invoked by uid 48); 3 Dec 2019 14:22:07 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92771] [9/10 Regression] Concept won't use default template argument
Date: Tue, 03 Dec 2019 14:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92771-4-vKG4DthHuJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00237.txt.bz2
Content-length: 363
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92771
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> trunk accepts with -fconcepts (?!?)
At r276764 it started to be accepted with -std=gnu++14 -fconcepts but is still
rejected with -std=gnu++17 -fconcepts or -std=gnu++2a -fconcepts. Odd.
>From gcc-bugs-return-662169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:25:32 2019
Return-Path: <gcc-bugs-return-662169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23859 invoked by alias); 3 Dec 2019 14:25:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23217 invoked by uid 48); 3 Dec 2019 14:25:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92770] std::unordered_map<T, U> requires both T and U to be fully declared
Date: Tue, 03 Dec 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92770-4-DgXBWXAAvp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92770-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92770-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00239.txt.bz2
Content-length: 765
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92770
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Not a bug.
(In reply to Raphael Kubo da Costa from comment #0)
> The excerpt above works fine with libc++ and MSVC's STL.
Implementations might accept it as an extension or by lucky accident, but the
standard says it's undefined:
http://eel.is/c++draft/requirements#res.on.functions-2.5
For our implementation accepting it is not possible.
>From gcc-bugs-return-662168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:25:24 2019
Return-Path: <gcc-bugs-return-662168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16044 invoked by alias); 3 Dec 2019 14:25:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74188 invoked by uid 48); 3 Dec 2019 14:24:26 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92754] ICE in gfc_finish_var_decl, at fortran/trans-decl.c:693
Date: Tue, 03 Dec 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92754-4-tLm6c6vVZZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92754-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92754-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00238.txt.bz2
Content-length: 1462
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92754
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Created attachment 47407
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47407&action=edit
Lightly tested patch
(In reply to Martin Liška from comment #1)
> Confirmed, started with r218068, it was rejected before the revision.
Which is from 2014 - 5 years ago … I am not sure whether it then really makes
sense to add someone as CC :-)
The problem is that gfc_finish_var_decl's
690 else if (sym->module && !sym->attr.result && !sym->attr.dummy)
is evaluated as true for the 'max' function as sym->module is "(intrinsic)" but
it is still marked as sym->attr.flavor == FL_VARIABLE and sym->attr.function ==
0
Or in other words, gfc_intrinsic_func_interface does:
expr->value.function.isym = specific;
if (!expr->symtree->n.sym->module)
gfc_intrinsic_symbol (expr->symtree->n.sym);
which updates expr->value.function and sets expr->symtree->n.sym to intrinsic,
but otherwise, expr->symtree->n.sym is still FL_UNKNOWN and attr.function = 0.
As this is now fine, resolve_unknown_f returns and nothing happens later. (The
expr type is expr->type == EXPR_CONST).
Something like the following seems to work. But one really needs to do
something like that for all gfc_intrinsic_func_interface calls, e.g. by adding
such a resolve call to gfc_intrinsic_func_interface itself.
>From gcc-bugs-return-662171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:31:55 2019
Return-Path: <gcc-bugs-return-662171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5645 invoked by alias); 3 Dec 2019 14:31:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5446 invoked by uid 48); 3 Dec 2019 14:31:35 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91073] [9/10 Regression] if constexpr no longer works directly with Concepts
Date: Tue, 03 Dec 2019 14:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-91073-4-kJxscHq6g7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91073-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91073-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00241.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91073
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |redi at gcc dot gnu.org
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 92771 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-662170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:31:54 2019
Return-Path: <gcc-bugs-return-662170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5552 invoked by alias); 3 Dec 2019 14:31:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5418 invoked by uid 48); 3 Dec 2019 14:31:34 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92771] [9/10 Regression] Concept won't use default template argument
Date: Tue, 03 Dec 2019 14:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92771-4-UoSIPrmykQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00240.txt.bz2
Content-length: 527
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92771
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Oh it's another manifestation of Bug 91073
*** This bug has been marked as a duplicate of bug 91073 ***
>From gcc-bugs-return-662172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:31:56 2019
Return-Path: <gcc-bugs-return-662172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5719 invoked by alias); 3 Dec 2019 14:31:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5512 invoked by uid 48); 3 Dec 2019 14:31:37 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67491] [meta-bug] concepts issues
Date: Tue, 03 Dec 2019 14:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-67491-4-EO1jvAosWx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67491-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67491-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00242.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67491
Bug 67491 depends on bug 92771, which changed state.
Bug 92771 Summary: [9/10 Regression] Concept won't use default template argument
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92771
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
>From gcc-bugs-return-662173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:32:51 2019
Return-Path: <gcc-bugs-return-662173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8915 invoked by alias); 3 Dec 2019 14:32:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8818 invoked by uid 48); 3 Dec 2019 14:32:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91073] [9/10 Regression] if constexpr no longer works directly with Concepts
Date: Tue, 03 Dec 2019 14:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on
Message-ID: <bug-91073-4-mofECmTF8l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91073-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91073-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00243.txt.bz2
Content-length: 1499
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91073
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2019-11-19 00:00:00 |2019-12-3
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #6)
> The bug only seems to happen when the concept is variadic.
Or has a default argument, as in the dup I just reported:
template<typename P, typename Arghhh = void>
concept one_or_two = true;
template<typename P>
concept one = one_or_two<P>;
template<typename T>
constexpr void
foo()
{
if (one<T>) // OK
{ }
if (one_or_two<T>) // ERROR
{ }
}
gcc-8-branch accepts this with -fconcepts.
gcc-9-branch rejects it with -fconcepts:
92771.cc: In function 'constexpr void foo()':
92771.cc:14:20: error: expected unqualified-id before ')' token
14 | if (one_or_two<T>) // ERROR
| ^
trunk accepts it with -std=gnu++14 -fconcepts (since r276764) but still rejects
it with -std=gnu++17 -fconcepts or -std=gnu++2a:
92771.cc: In function 'constexpr void foo()':
92771.cc:14:7: error: expected 'auto' or 'decltype(auto)' after 'one_or_two<T>'
14 | if (one_or_two<T>) // ERROR
| ^~~~~~~~~~~~~
92771.cc:14:20: error: expected unqualified-id before ')' token
14 | if (one_or_two<T>) // ERROR
| ^
>From gcc-bugs-return-662174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:34:38 2019
Return-Path: <gcc-bugs-return-662174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10452 invoked by alias); 3 Dec 2019 14:34:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10383 invoked by uid 48); 3 Dec 2019 14:34:33 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 14:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92765-4-2eXrILmacA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00244.txt.bz2
Content-length: 448
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #8 from Jeffrey A. Law <law at redhat dot com> ---
Perhaps related to:
https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01874.html
>From gcc-bugs-return-662175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:34:54 2019
Return-Path: <gcc-bugs-return-662175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11171 invoked by alias); 3 Dec 2019 14:34:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11118 invoked by uid 48); 3 Dec 2019 14:34:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91073] [9/10 Regression] if constexpr no longer works directly with Concepts
Date: Tue, 03 Dec 2019 14:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-91073-4-K8ROdWO1ZZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91073-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91073-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00245.txt.bz2
Content-length: 289
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91073
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
>From gcc-bugs-return-662176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:39:16 2019
Return-Path: <gcc-bugs-return-662176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21051 invoked by alias); 3 Dec 2019 14:39:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20409 invoked by uid 55); 3 Dec 2019 14:39:08 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 14:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92768-4-BUY6CBcMVH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00246.txt.bz2
Content-length: 1281
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
--- Comment #11 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 3 Dec 2019, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
>
> Jakub Jelinek <jakub at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |jakub at gcc dot gnu.org
>
> --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> The vector builder calls operand_equal_p, which in turn does:
> case REAL_CST:
> if (real_identical (&TREE_REAL_CST (arg0), &TREE_REAL_CST (arg1)))
> return true;
>
>
> if (!HONOR_SIGNED_ZEROS (arg0))
> {
> /* If we do not distinguish between signed and unsigned zero,
> consider them equal. */
> if (real_zerop (arg0) && real_zerop (arg1))
> return true;
> }
> return false;
> So, what could be done is temporarily enable flag_signed_zeros in the vector
> builder.
Alternatively add another flag to operand_equal_p to say whether
exact literal equality is asked for.
>From gcc-bugs-return-662177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:44:34 2019
Return-Path: <gcc-bugs-return-662177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45349 invoked by alias); 3 Dec 2019 14:44:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45303 invoked by uid 48); 3 Dec 2019 14:44:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 14:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92765-4-6IpISH7p11@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00247.txt.bz2
Content-length: 1169
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #8)
> Perhaps related to:
>
> https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01874.html
Yes, that is pretty much the same thing. One thing is whether it is safe or
unsafe to use what determine_min_objsize does for the purposes Qing introduced
(probably unsafe, if we e.g. consider what GCC uses for tree/rtl/gimple, unions
containing members with different sizes and where the mapped size is actually
just the size of the corresponding member; if VN would see first
&ptr->member.elt
of some larger element and then &ptr->smaller_member which has the same
address,
Qing's code could assume at least that many bytes are mapped and perform *_eq).
And another thing as the #c7 testcase shows that it is wrong to use minimum
object size, whatever exact definition it has, at least for code generation
purposes, it has to consider maximum object size instead, as the code tries to
optimize the str{,n}cmp into not equal if one object is small enough and the
other object is too large to fit in there.
>From gcc-bugs-return-662178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:47:37 2019
Return-Path: <gcc-bugs-return-662178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65894 invoked by alias); 3 Dec 2019 14:47:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65840 invoked by uid 48); 3 Dec 2019 14:47:33 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92758] [10 regression] r278833 breaks gcc.target/powerpc/fold-vec-splat-floatdouble.c
Date: Tue, 03 Dec 2019 14:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92758-4-OgoEBPZvoE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00248.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92758
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-662179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 14:48:01 2019
Return-Path: <gcc-bugs-return-662179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66803 invoked by alias); 3 Dec 2019 14:48:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66750 invoked by uid 55); 3 Dec 2019 14:47:56 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92758] [10 regression] r278833 breaks gcc.target/powerpc/fold-vec-splat-floatdouble.c
Date: Tue, 03 Dec 2019 14:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92758-4-m0rzh3Poq5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00249.txt.bz2
Content-length: 524
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92758
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Dec 3 14:47:24 2019
New Revision: 278938
URL: https://gcc.gnu.org/viewcvs?rev=278938&root=gcc&view=rev
Log:
2019-12-03 Richard Biener <rguenther@suse.de>
PR tree-optimization/92758
* tree-ssa-forwprop.c (simplify_vector_constructor): Restore
operation on uniform vectors.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/tree-ssa-forwprop.c
>From gcc-bugs-return-662180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 15:03:33 2019
Return-Path: <gcc-bugs-return-662180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117827 invoked by alias); 3 Dec 2019 15:03:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117779 invoked by uid 48); 3 Dec 2019 15:03:28 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 15:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92765-4-HUBBlxWdb8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00250.txt.bz2
Content-length: 1214
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Testcase showing wrong-code with the __builtin_strcmp_eq stuff (assuming the
testcase is considered valid):
/* { dg-do run { target mmap } } */
/* { dg-options "-O2" } */
#include <stdlib.h>
#include <sys/mman.h>
#ifndef MAP_ANONYMOUS
#define MAP_ANONYMOUS MAP_ANON
#endif
#ifndef MAP_ANON
#define MAP_ANON 0
#endif
#ifndef MAP_FAILED
#define MAP_FAILED ((void *)-1)
#endif
union U { struct T { char a[2]; char b[4094]; } c; struct S { char d[4]; int e;
} f; };
__attribute__((noipa)) void
bar (char *p)
{
asm volatile ("" : : "g" (p) : "memory");
}
__attribute__((noipa)) int
foo (union U *p)
{
bar ((char *) &p->c.b);
return __builtin_strcmp (&p->f.d[2], "abcdefghijk") == 0;
}
int
main ()
{
char *p = mmap (NULL, 131072, PROT_READ | PROT_WRITE,
MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
if (p == MAP_FAILED)
return 0;
if (munmap (p + 65536, 65536) < 0)
return 0;
union U *u;
u = (union U *) (p + 65536 - sizeof (u->f));
__builtin_memcpy (u->f.d, "abc", 4);
u->f.e = 1;
if (foo (u) != 0)
__builtin_abort ();
return 0;
}
>From gcc-bugs-return-662181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 15:09:17 2019
Return-Path: <gcc-bugs-return-662181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43656 invoked by alias); 3 Dec 2019 15:09:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43580 invoked by uid 48); 3 Dec 2019 15:09:12 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 15:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92768-4-Hdus7CrBKf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00251.txt.bz2
Content-length: 637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #11)
> Alternatively add another flag to operand_equal_p to say whether
> exact literal equality is asked for.
That is fine with me. Though, as I said on IRC, it can work then by accident,
but might break any time, e.g. won't VN if it sees with -fno-signed-zeros:
_2 = { 0.f, 0.f, 0.f, 0.f };
use (_2);
...
_5 = { 0.f, -0.f, 0.f, -0.f };
use (_5);
happily replace _5 with _2, or anything else that uses operand_equal_p and
won't pass this new magic flag?
>From gcc-bugs-return-662183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 15:13:33 2019
Return-Path: <gcc-bugs-return-662183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107917 invoked by alias); 3 Dec 2019 15:13:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107901 invoked by uid 48); 3 Dec 2019 15:13:29 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92762] hash_table::empty_slow invokes assignment on invalid objects
Date: Tue, 03 Dec 2019 15:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92762-4-ZltNg7UjyJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00253.txt.bz2
Content-length: 945
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92762
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
It looks to me like the whole else block with the BROKEN_VALUE_INITIALIZATION
guard is incorrect. The following test case aborts:
typedef int_hash<int, INT_MIN, INT_MAX> IntHash;
hash_map<int, int, simple_hashmap_traits<IntHash, int> > x;
static void test_hash_table ()
{
for (int i = 1; i != 32; ++i)
x.put (i, i);
x.empty ();
gcc_assert (!x.get (0)); << abort here
}
internal compiler error: in test_hash_table, at cp/parser.c:43483
0xaea59d test_hash_table
/src/gcc/61339/gcc/cp/parser.c:43483
0xaea5a9 c_parse_file()
/src/gcc/61339/gcc/cp/parser.c:43491
0xcd3987 c_common_parse_file()
/src/gcc/61339/gcc/c-family/c-opts.c:1185
Please submit a full bug report,
Changing the assert to
gcc_assert (!x.get (1));
leads to an infinite loop in hash_table::find_with_hash().
>From gcc-bugs-return-662182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 15:13:11 2019
Return-Path: <gcc-bugs-return-662182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107205 invoked by alias); 3 Dec 2019 15:13:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107182 invoked by uid 48); 3 Dec 2019 15:13:06 -0000
From: "ams at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92772] New: wrong code vectorizing masked max
Date: Tue, 03 Dec 2019 15:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: ams at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00252.txt.bz2
Content-length: 2227
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92772
Bug ID: 92772
Summary: wrong code vectorizing masked max
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: ams at gcc dot gnu.org
Target Milestone: ---
The testcase pr65947-10.c fails on amdgcn because there are more vector lanes
than there is data, and the algorithm created doesn't allow for this. (Actually
there's also a backend pattern missing, but I have a patch for that I'll commit
shortly.)
Here's the affected loop:
float last = 0;
for (int i = 0; i < 32; i++)
if (a[i] < min_v)
last = a[i];
Which produces the following code (long lines shortened).
vect_cst__33 = {min_v_11(D), .... min_v_11(D)};
vect__4.16_32 = .MASK_LOAD (a_10(D), 4B, { -1, [...] -1, 0, [...] 0 });
vect_last_6.17_34 = VEC_COND_EXPR <vect__4.16_32 < vect_cst__33,
vect__4.16_32, { 0.0, [...] 0.0 }>;
_38 = VEC_COND_EXPR <vect__4.16_32 < vect_cst__33, { 1, 2, [...] 64 }, { 0,
[...] 0 }>;
_40 = .REDUC_MAX (_38);
_41 = {_40, _40, [...] _40};
_43 = VEC_COND_EXPR <_38 == _41, vect_last_6.17_34, { 0.0, [...] 0.0 }>;
_44 = VIEW_CONVERT_EXPR<vector(64) unsigned int>(_43);
_45 = .REDUC_MAX (_44);
_46 = VIEW_CONVERT_EXPR<float>(_45);
return _46;
In English:
1. Do a masked load of 32 elements (into 64-lane register). Loads "0.0" into
the spare lanes.
2. Compare the all 64-lanes against "min_v". Label all the "true" lanes with
the lane number.
3. Use a reduction to find the greatest numbered "true" lane.
4. Zero all the loaded values apart from the one in the greatest lane.
5. Use a reduction to find the value of the lane that isn't zeroed.
That's slightly tortuous when we could just do a vec_extract on "_40", but
that's an aside.
The problem is in step 2: the spare lanes contain 0.0, which means that
comparing them against "min_v" returns "true". This means that the algorithm
always finds "last = a[63]" which isn't a real value and therefore always ends
up being "0.0".
>From gcc-bugs-return-662184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 15:17:56 2019
Return-Path: <gcc-bugs-return-662184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20669 invoked by alias); 3 Dec 2019 15:17:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20629 invoked by uid 48); 3 Dec 2019 15:17:51 -0000
From: "renault at fedoraproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92773] New: GCC compilation with big array / header is infinite
Date: Tue, 03 Dec 2019 15:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: renault at fedoraproject dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00254.txt.bz2
Content-length: 1088
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92773
Bug ID: 92773
Summary: GCC compilation with big array / header is infinite
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: renault at fedoraproject dot org
Target Milestone: ---
Created attachment 47408
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47408&action=edit
module driver
I'm working on a new Linux kernel module. I'm using Fedora 31 with GCC 9.2.1
This module has several big arrays generated by a external tool which should be
included into the driver itself. I use C headers for that.
Without those headers, the compilation works fine. But if I try to include
them, the compilation takes a infinite amount of time with cc1 process which
uses one CPU at 100%.
I tried with GCC 5.3.1 (Fedora 22) and 5.3.0 (Yocto) and the build succeed. And
I don't see any reason to have this behaviour on earlier GCC.
>From gcc-bugs-return-662186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 15:18:48 2019
Return-Path: <gcc-bugs-return-662186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22305 invoked by alias); 3 Dec 2019 15:18:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22255 invoked by uid 48); 3 Dec 2019 15:18:40 -0000
From: "renault at fedoraproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92773] GCC compilation with big array / header is infinite
Date: Tue, 03 Dec 2019 15:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: renault at fedoraproject dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92773-4-gLnRUkBsjX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00256.txt.bz2
Content-length: 278
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92773
--- Comment #2 from Charles-Antoine Couret <renault at fedoraproject dot org> ---
Created attachment 47410
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47410&action=edit
one big header which raises the problem
>From gcc-bugs-return-662185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 15:18:18 2019
Return-Path: <gcc-bugs-return-662185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21486 invoked by alias); 3 Dec 2019 15:18:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21446 invoked by uid 48); 3 Dec 2019 15:18:14 -0000
From: "renault at fedoraproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92773] GCC compilation with big array / header is infinite
Date: Tue, 03 Dec 2019 15:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: renault at fedoraproject dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92773-4-IXL0OEa2Ms@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00255.txt.bz2
Content-length: 259
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92773
--- Comment #1 from Charles-Antoine Couret <renault at fedoraproject dot org> ---
Created attachment 47409
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47409&action=edit
module driver header
>From gcc-bugs-return-662187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 15:29:27 2019
Return-Path: <gcc-bugs-return-662187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58129 invoked by alias); 3 Dec 2019 15:29:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58069 invoked by uid 48); 3 Dec 2019 15:29:23 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92758] [10 regression] r278833 breaks gcc.target/powerpc/fold-vec-splat-floatdouble.c
Date: Tue, 03 Dec 2019 15:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92758-4-NaFY4l3gah@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00257.txt.bz2
Content-length: 341
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92758
--- Comment #4 from seurer at gcc dot gnu.org ---
OK, thanks.
BTW, for reference this also affected a couple other test cases on LE power 8
and power 9.
FAIL: gcc.target/powerpc/swaps-p8-16.c scan-assembler vspltw
FAIL: gcc.target/powerpc/swaps-p8-27.c scan-assembler-times lxvd2x 2
>From gcc-bugs-return-662188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 15:43:47 2019
Return-Path: <gcc-bugs-return-662188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111634 invoked by alias); 3 Dec 2019 15:43:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 111609 invoked by uid 48); 3 Dec 2019 15:43:43 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/47857] Pragma once warning when compiling PCH
Date: Tue, 03 Dec 2019 15:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 4.4.5
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: romain.geissler at amadeus dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-47857-4-jRhlKM0mM1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47857-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00258.txt.bz2
Content-length: 519
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47857
Romain Geissler <romain.geissler at amadeus dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |romain.geissler at amadeus dot com
--- Comment #8 from Romain Geissler <romain.geissler at amadeus dot com> ---
Hi,
This is still the case up to gcc 9 (already released) and current trunk of gcc
10.
Cheers,
Romain
>From gcc-bugs-return-662189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 15:54:44 2019
Return-Path: <gcc-bugs-return-662189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33693 invoked by alias); 3 Dec 2019 15:54:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33664 invoked by uid 48); 3 Dec 2019 15:54:39 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92774] New: ICE with defaulted three-way comparison function
Date: Tue, 03 Dec 2019 15:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92774-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00259.txt.bz2
Content-length: 3379
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92774
Bug ID: 92774
Summary: ICE with defaulted three-way comparison function
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
#include <compare>
template<typename T>
struct X { };
template<typename T>
bool operator==(const X<T>&, const X<T>&) { return true; }
template<typename T>
bool operator<(const X<T>&, const X<T>&) { return true; }
struct Y
{
int a;
X<int> c;
auto operator <=>(Y const&) const = default;
};
void f()
{
auto x = Y() < Y();
}
This gets an ICE when compiled with -std=gnu++2a:
ice.cc: In member function 'constexpr auto Y::operator<=>(const Y&) const':
ice.cc:16:8: internal compiler error: tree check: expected class 'type', have
'exceptional' (error_mark) in is_cat, at cp/method.c:999
16 | auto operator <=>(Y const&) const = default;
| ^~~~~~~~
0x7e1d30 tree_class_check_failed(tree_node const*, tree_code_class, char
const*, int, char const*)
/home/jwakely/src/gcc/gcc/gcc/tree.c:9738
0x618612 tree_class_check(tree_node*, tree_code_class, char const*, int, char
const*)
/home/jwakely/src/gcc/gcc/gcc/tree.h:3396
0x618612 is_cat
/home/jwakely/src/gcc/gcc/gcc/cp/method.c:999
0x9a226c cat_tag_for
/home/jwakely/src/gcc/gcc/gcc/cp/method.c:1011
0x9a226c common_comparison_type
/home/jwakely/src/gcc/gcc/gcc/cp/method.c:1166
0x9a226c build_comparison_op
/home/jwakely/src/gcc/gcc/gcc/cp/method.c:1341
0x9a8809 synthesize_method(tree_node*)
/home/jwakely/src/gcc/gcc/gcc/cp/method.c:1501
0x9637c7 mark_used(tree_node*, int)
/home/jwakely/src/gcc/gcc/gcc/cp/decl2.c:5481
0x8c8611 build_over_call
/home/jwakely/src/gcc/gcc/gcc/cp/call.c:8956
0x8cfc58 build_new_op_1
/home/jwakely/src/gcc/gcc/gcc/cp/call.c:6234
0x8d023d build_new_op(op_location_t const&, tree_code, int, tree_node*,
tree_node*, tree_node*, tree_node**, int)
/home/jwakely/src/gcc/gcc/gcc/cp/call.c:6499
0xa9b533 build_x_binary_op(op_location_t const&, tree_code, tree_node*,
tree_code, tree_node*, tree_code, tree_node**, int)
/home/jwakely/src/gcc/gcc/gcc/cp/typeck.c:4229
0x9cc6e1 cp_parser_binary_expression
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:9645
0x9cd557 cp_parser_assignment_expression
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:9780
0x9ccf3d cp_parser_constant_expression
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:10074
0x9cd501 cp_parser_initializer_clause
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:23023
0x9d16a7 cp_parser_initializer
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:22961
0x9fa521 cp_parser_init_declarator
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:20669
0x9da932 cp_parser_simple_declaration
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:13624
0x9dc669 cp_parser_declaration_statement
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:13055
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-662190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 16:01:21 2019
Return-Path: <gcc-bugs-return-662190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90361 invoked by alias); 3 Dec 2019 16:00:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90202 invoked by uid 55); 3 Dec 2019 16:00:39 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91363] Implement P0960R3: Parenthesized initialization of aggregates
Date: Tue, 03 Dec 2019 16:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91363-4-sDI0SpeKzY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91363-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91363-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00260.txt.bz2
Content-length: 6356
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91363
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Tue Dec 3 15:59:40 2019
New Revision: 278939
URL: https://gcc.gnu.org/viewcvs?rev=278939&root=gcc&view=rev
Log:
PR c++/91363 - P0960R3: Parenthesized initialization of aggregates.
This patch implements C++20 P0960R3: Parenthesized initialization of aggregates
(<wg21.link/p0960>; see R0 for more background info). Essentially, if you have
an aggregate, you can now initialize it by (x, y), similarly to {x, y}. E.g.
struct A {
int x, y;
// no A(int, int) ctor (see paren-init14.C for = delete; case)
};
A a(1, 2);
The difference between ()-init and {}-init is that narrowing conversions are
permitted, designators are not permitted, a temporary object bound to
a reference does not have its lifetime extended, and there is no brace elision.
Further, things like
int a[](1, 2, 3); // will deduce the array size
const A& r(1, 2.3, 3); // narrowing is OK
int (&&rr)[](1, 2, 3);
int b[3](1, 2); // b[2] will be value-initialized
now work as expected. Note that
char f[]("fluff");
has always worked and this patch keeps it that way. Also note that A a((1, 2))
is not the same as A a{{1,2}}; the inner (1, 2) remains a COMPOUND_EXPR.
The approach I took was to handle (1, 2) similarly to {1, 2} -- conjure up
a CONSTRUCTOR, and introduce LOOKUP_AGGREGATE_PAREN_INIT to distinguish
between the two. This kind of initialization is only supported in C++20;
I've made no attempt to support it in earlier standards, like we don't
support CTAD pre-C++17, for instance.
* c-cppbuiltin.c (c_cpp_builtins): Predefine
__cpp_aggregate_paren_init=201902 for -std=c++2a.
* call.c (build_new_method_call_1): Handle parenthesized initialization
of aggregates by building up a CONSTRUCTOR.
(extend_ref_init_temps): Do nothing for CONSTRUCTOR_IS_PAREN_INIT.
* cp-tree.h (CONSTRUCTOR_IS_PAREN_INIT, LOOKUP_AGGREGATE_PAREN_INIT):
Define.
* decl.c (grok_reference_init): Handle aggregate initialization from
a parenthesized list of values.
(reshape_init): Do nothing for CONSTRUCTOR_IS_PAREN_INIT.
(check_initializer): Handle initialization of an array from a
parenthesized list of values. Use NULL_TREE instead of NULL.
* tree.c (build_cplus_new): Handle BRACE_ENCLOSED_INITIALIZER_P.
* typeck2.c (digest_init_r): Set LOOKUP_AGGREGATE_PAREN_INIT if it
receives a CONSTRUCTOR with CONSTRUCTOR_IS_PAREN_INIT set. Allow
narrowing when LOOKUP_AGGREGATE_PAREN_INIT.
(massage_init_elt): Don't lose LOOKUP_AGGREGATE_PAREN_INIT when passing
flags to digest_init_r.
* g++.dg/cpp0x/constexpr-99.C: Only expect an error in C++17 and
lesser.
* g++.dg/cpp0x/explicit7.C: Likewise.
* g++.dg/cpp0x/initlist12.C: Adjust dg-error.
* g++.dg/cpp0x/pr31437.C: Likewise.
* g++.dg/cpp2a/feat-cxx2a.C: Add __cpp_aggregate_paren_init test.
* g++.dg/cpp2a/paren-init1.C: New test.
* g++.dg/cpp2a/paren-init10.C: New test.
* g++.dg/cpp2a/paren-init11.C: New test.
* g++.dg/cpp2a/paren-init12.C: New test.
* g++.dg/cpp2a/paren-init13.C: New test.
* g++.dg/cpp2a/paren-init14.C: New test.
* g++.dg/cpp2a/paren-init15.C: New test.
* g++.dg/cpp2a/paren-init16.C: New test.
* g++.dg/cpp2a/paren-init17.C: New test.
* g++.dg/cpp2a/paren-init18.C: New test.
* g++.dg/cpp2a/paren-init19.C: New test.
* g++.dg/cpp2a/paren-init2.C: New test.
* g++.dg/cpp2a/paren-init3.C: New test.
* g++.dg/cpp2a/paren-init4.C: New test.
* g++.dg/cpp2a/paren-init5.C: New test.
* g++.dg/cpp2a/paren-init6.C: New test.
* g++.dg/cpp2a/paren-init7.C: New test.
* g++.dg/cpp2a/paren-init8.C: New test.
* g++.dg/cpp2a/paren-init9.C: New test.
* g++.dg/ext/desig10.C: Adjust dg-error.
* g++.dg/template/crash107.C: Likewise.
* g++.dg/template/crash95.C: Likewise.
* g++.old-deja/g++.jason/crash3.C: Likewise.
* g++.old-deja/g++.law/ctors11.C: Likewise.
* g++.old-deja/g++.law/ctors9.C: Likewise.
* g++.old-deja/g++.mike/net22.C: Likewise.
* g++.old-deja/g++.niklas/t128.C: Likewise.
Added:
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init1.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init10.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init11.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init12.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init13.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init14.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init15.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init16.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init17.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init18.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init19.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init2.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init3.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init4.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init5.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init6.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init7.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init8.C
trunk/gcc/testsuite/g++.dg/cpp2a/paren-init9.C
Modified:
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-cppbuiltin.c
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/call.c
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/decl.c
trunk/gcc/cp/tree.c
trunk/gcc/cp/typeck2.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-99.C
trunk/gcc/testsuite/g++.dg/cpp0x/explicit7.C
trunk/gcc/testsuite/g++.dg/cpp0x/initlist12.C
trunk/gcc/testsuite/g++.dg/cpp0x/pr31437.C
trunk/gcc/testsuite/g++.dg/cpp2a/feat-cxx2a.C
trunk/gcc/testsuite/g++.dg/ext/desig10.C
trunk/gcc/testsuite/g++.dg/template/crash107.C
trunk/gcc/testsuite/g++.dg/template/crash95.C
trunk/gcc/testsuite/g++.old-deja/g++.jason/crash3.C
trunk/gcc/testsuite/g++.old-deja/g++.law/ctors11.C
trunk/gcc/testsuite/g++.old-deja/g++.law/ctors9.C
trunk/gcc/testsuite/g++.old-deja/g++.mike/net22.C
trunk/gcc/testsuite/g++.old-deja/g++.niklas/t128.C
>From gcc-bugs-return-662191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 16:03:43 2019
Return-Path: <gcc-bugs-return-662191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92564 invoked by alias); 3 Dec 2019 16:03:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 92526 invoked by uid 48); 3 Dec 2019 16:03:38 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88323] implement C++20 language features.
Date: Tue, 03 Dec 2019 16:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88323-4-KuLPJXWnox@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88323-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88323-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00261.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88323
Bug 88323 depends on bug 91363, which changed state.
Bug 91363 Summary: Implement P0960R3: Parenthesized initialization of aggregates
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91363
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-662192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 16:03:43 2019
Return-Path: <gcc-bugs-return-662192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92569 invoked by alias); 3 Dec 2019 16:03:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 92507 invoked by uid 48); 3 Dec 2019 16:03:37 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91363] Implement P0960R3: Parenthesized initialization of aggregates
Date: Tue, 03 Dec 2019 16:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91363-4-gPOcgen2JE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91363-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91363-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00262.txt.bz2
Content-length: 446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91363
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Implemented for GCC 10.
>From gcc-bugs-return-662193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 16:12:49 2019
Return-Path: <gcc-bugs-return-662193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32644 invoked by alias); 3 Dec 2019 16:12:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32581 invoked by uid 48); 3 Dec 2019 16:12:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 16:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92765-4-rhGRcglrdV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00263.txt.bz2
Content-length: 3975
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Untested patch to fix all these wrong-code issues would be something like:
--- gcc/tree-ssa-strlen.c.jj 2019-11-28 09:35:32.443298424 +0100
+++ gcc/tree-ssa-strlen.c 2019-12-03 17:02:32.131658020 +0100
@@ -3473,54 +3473,30 @@ compute_string_length (int idx)
static unsigned HOST_WIDE_INT
determine_min_objsize (tree dest)
{
- unsigned HOST_WIDE_INT size = 0;
+ unsigned HOST_WIDE_INT size;
init_object_sizes ();
if (compute_builtin_object_size (dest, 2, &size))
return size;
- /* Try to determine the size of the object through the RHS
- of the assign statement. */
- if (TREE_CODE (dest) == SSA_NAME)
- {
- gimple *stmt = SSA_NAME_DEF_STMT (dest);
- if (!is_gimple_assign (stmt))
- return HOST_WIDE_INT_M1U;
-
- if (!gimple_assign_single_p (stmt)
- && !gimple_assign_unary_nop_p (stmt))
- return HOST_WIDE_INT_M1U;
+ return HOST_WIDE_INT_M1U;
+}
- dest = gimple_assign_rhs1 (stmt);
- return determine_min_objsize (dest);
- }
+/* Similarly, but maximum instead of minimum, and return 0 when the
+ size cannot be determined. */
- /* Try to determine the size of the object from its type. */
- if (TREE_CODE (dest) != ADDR_EXPR)
- return HOST_WIDE_INT_M1U;
-
- tree type = TREE_TYPE (dest);
- if (TREE_CODE (type) == POINTER_TYPE)
- type = TREE_TYPE (type);
-
- type = TYPE_MAIN_VARIANT (type);
-
- /* The size of a flexible array cannot be determined. Otherwise,
- for arrays with more than one element, return the size of its
- type. GCC itself misuses arrays of both zero and one elements
- as flexible array members so they are excluded as well. */
- if (TREE_CODE (type) != ARRAY_TYPE
- || !array_at_struct_end_p (dest))
- {
- tree type_size = TYPE_SIZE_UNIT (type);
- if (type_size && TREE_CODE (type_size) == INTEGER_CST
- && !integer_onep (type_size)
- && !integer_zerop (type_size))
- return tree_to_uhwi (type_size);
- }
+static unsigned HOST_WIDE_INT
+determine_max_objsize (tree dest)
+{
+ unsigned HOST_WIDE_INT size;
- return HOST_WIDE_INT_M1U;
+ init_object_sizes ();
+
+ if (compute_builtin_object_size (dest, 0, &size))
+ return size;
+
+ return 0;
}
/* Given strinfo IDX for ARG, set LENRNG[] to the range of lengths
@@ -3603,7 +3579,9 @@ get_len_or_size (tree arg, int idx, unsi
/* Set *SIZE to the size of the smallest object referenced
by ARG if ARG denotes a single object, or to HWI_M1U
otherwise. */
- *size = determine_min_objsize (arg);
+ *size = determine_max_objsize (arg);
+ if (*size == 0)
+ *size = HOST_WIDE_INT_M1U;
*nulterm = false;
}
}
plus add testsuite coverage from the testcases in this PR and deal with
testsuite regressions:
FAIL: gcc.dg/Wstring-compare.c (test for warnings, line 123)
FAIL: gcc.dg/strcmpopt_2.c scan-tree-dump-times strlen1 "cmp_eq \\(" 8
FAIL: gcc.dg/strcmpopt_4.c scan-tree-dump-times strlen1 "cmp_eq \\(" 1
FAIL: gcc.dg/strlenopt-69.c scan-tree-dump-not optimized "abort|strcmp|strncmp"
where strcmpopt_2.c now matches just 4 times instead of 8.
Or do we consider the #c10 testcase valid, but what strcmpopt_2.c does like:
typedef struct { char s[8]; int x; } S;
__attribute__ ((noinline)) int
f1 (S *s)
{
return __builtin_strcmp (s->s, "abc") != 0;
}
ok (in that if there is a pointer to S, at least sizeof (s->s) bytes will be
mapped? We could look through COMPONENT_REFs in the access path and if there
is any UNION_TYPE in there, be conservative and consider the same addresses in
all the union members and take conservative answer from all of them? Wouldn't
that still be a problem if we have union somewhere earlier and just take
address of a union member?
>From gcc-bugs-return-662194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 16:35:15 2019
Return-Path: <gcc-bugs-return-662194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24915 invoked by alias); 3 Dec 2019 16:35:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22741 invoked by uid 48); 3 Dec 2019 16:35:10 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 16:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92765-4-APX60qpZ1m@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00264.txt.bz2
Content-length: 409
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
--- Comment #12 from Martin Sebor <msebor at gcc dot gnu.org> ---
The __builtin_strcmp(ptr->header.magic, "x") call in comment #0 is undefined
because the two-element array ptr->header.magic is not a nul-terminated string.
The warning was designed to point that out.
Removing the call removes the bug from the test case and lets it run to
completion.
>From gcc-bugs-return-662195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 16:47:12 2019
Return-Path: <gcc-bugs-return-662195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55216 invoked by alias); 3 Dec 2019 16:47:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55145 invoked by uid 48); 3 Dec 2019 16:47:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92765] [10 Regression] Wrong code caused by folding of -Wstring-compare since r276773
Date: Tue, 03 Dec 2019 16:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92765-4-TVd6xQXIJt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00265.txt.bz2
Content-length: 804
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92765
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #12)
> The __builtin_strcmp(ptr->header.magic, "x") call in comment #0 is undefined
> because the two-element array ptr->header.magic is not a nul-terminated
> string. The warning was designed to point that out.
I don't agree with that view, but if you replace that first __builtin_strcmp
with say __builtin_memcmp(ptr->header.magic, "x", 2) == 0 it fails the same
way. Plus all the other testcases in this PR.
The first call really doesn't matter, all that matters is that there is
something taking address of ptr->header.magic earlier in the function.
And a warning designed on something the GIMPLE IL does not preserve is wrong.
>From gcc-bugs-return-662196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 17:05:58 2019
Return-Path: <gcc-bugs-return-662196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85997 invoked by alias); 3 Dec 2019 17:05:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85799 invoked by uid 55); 3 Dec 2019 17:05:53 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Tue, 03 Dec 2019 17:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92768-4-gfp7s7jeZx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00266.txt.bz2
Content-length: 894
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
--- Comment #13 from rguenther at suse dot de <rguenther at suse dot de> ---
On December 3, 2019 4:09:12 PM GMT+01:00, "jakub at gcc dot gnu.org"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
>
>--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
>(In reply to rguenther@suse.de from comment #11)
>> Alternatively add another flag to operand_equal_p to say whether
>> exact literal equality is asked for.
>
>That is fine with me. Though, as I said on IRC, it can work then by
>accident,
>but might break any time, e.g. won't VN if it sees with
>-fno-signed-zeros:
> _2 = { 0.f, 0.f, 0.f, 0.f };
> use (_2);
> ...
> _5 = { 0.f, -0.f, 0.f, -0.f };
> use (_5);
>happily replace _5 with _2, or anything else that uses operand_equal_p
>and
>won't pass this new magic flag?
Yes.
>From gcc-bugs-return-662197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 17:46:18 2019
Return-Path: <gcc-bugs-return-662197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50523 invoked by alias); 3 Dec 2019 17:46:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49970 invoked by uid 48); 3 Dec 2019 17:46:11 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65146] alignment of _Atomic structure member is not correct
Date: Tue, 03 Dec 2019 17:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-65146-4-jtv2njjZb6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65146-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65146-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00267.txt.bz2
Content-length: 753
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65146
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
CC| |jason at gcc dot gnu.org,
| |law at gcc dot gnu.org
--- Comment #18 from Jason Merrill <jason at gcc dot gnu.org> ---
Here's the thread on the psABI mailing list.
https://groups.google.com/forum/#!topic/ia32-abi/Tlu6Hs-ohPY
Can we please fix this for GCC 10? It's an important compatibility issue, and
becoming more important. Bumping to P1 to raise visibility.
>From gcc-bugs-return-662198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 18:06:26 2019
Return-Path: <gcc-bugs-return-662198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15566 invoked by alias); 3 Dec 2019 18:06:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15291 invoked by uid 48); 3 Dec 2019 18:06:21 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/91971] Profile directory concatenated with object file path
Date: Tue, 03 Dec 2019 18:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: qinzhao at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-91971-4-A44XLYpxW8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00268.txt.bz2
Content-length: 1020
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91971
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |ebotcazou at gcc dot gnu.org
Resolution|FIXED |---
--- Comment #7 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Reopened because the new behavior is problematic. Consider the file t.c:
int main (void)
{
return 0;
}
in the directory /home/eric and compile it like so:
gcc -c /home/eric/t.c -o /home/eric/t.o -fprofile-arcs -ftest-coverage
gcc /home/eric/t.o -o /home/eric/t -lgcov
/home/eric/t
You get the following couple of files in the directory:
#home#eric#t.gcda
#home#eric#t.gcno
whereas you would have gotten t.gcda and t.gcno before.
Please consider making the change conditional on -fprofile-dir= or somesuch.
>From gcc-bugs-return-662199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 18:16:18 2019
Return-Path: <gcc-bugs-return-662199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58132 invoked by alias); 3 Dec 2019 18:16:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57316 invoked by uid 55); 3 Dec 2019 18:15:06 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65146] alignment of _Atomic structure member is not correct
Date: Tue, 03 Dec 2019 18:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65146-4-99Pq4flyss@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65146-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65146-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00269.txt.bz2
Content-length: 1147
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65146
--- Comment #19 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Tue, 3 Dec 2019, jason at gcc dot gnu.org wrote:
> Can we please fix this for GCC 10? It's an important compatibility issue, and
> becoming more important. Bumping to P1 to raise visibility.
Are we taking "this" to mean specifically the issue described in the bug
summary, i.e. alignment in structures? (And not anything about adding
padding to atomic types, which isn't needed for correctness but might be
needed on some platforms for ABI compatibility with the system compilers
but is also likely to need changes somewhere to allow assignments from
atomic to non-atomic to work properly without e.g. trying to copy the
padding to a non-atomic type that doesn't include it - that might also
affect stdatomic.h, which generally uses __atomic_* with temporaries of
non-atomic type, which thus wouldn't have any such extra padding; maybe
the generic __atomic_* would need to have special handling of pointers to
different-sized arguments, or something like that.)
>From gcc-bugs-return-662200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 18:55:03 2019
Return-Path: <gcc-bugs-return-662200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107570 invoked by alias); 3 Dec 2019 18:55:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107287 invoked by uid 48); 3 Dec 2019 18:54:57 -0000
From: "andrew.burgess at embecosm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92775] New: Incorrect expression in DW_AT_byte_stride on an array
Date: Tue, 03 Dec 2019 18:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andrew.burgess at embecosm dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00270.txt.bz2
Content-length: 6404
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92775
Bug ID: 92775
Summary: Incorrect expression in DW_AT_byte_stride on an array
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: andrew.burgess at embecosm dot com
Target Milestone: ---
Created attachment 47411
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47411&action=edit
Example.
1. Unpack the example, and run 'make'. This creates a test binary
called 'test', and the DWARF from that binary is placed into
'test.dwarf'. Initially I'm using GCC 7.4.0.
2. In the generated 'test.dwarf' Find the DW_TAG_variable for
'point_dimension', note its DW_AT_type and DW_AT_location. For me
I have:
<2><e9>: Abbrev Number: 10 (DW_TAG_variable)
<ea> DW_AT_name : (indirect string, offset: 0x0):
point_dimension
<ee> DW_AT_decl_file : 1
<ef> DW_AT_decl_line : 13
<f0> DW_AT_type : <0x18a>
<f4> DW_AT_location : 9 byte block: 3 80 10 60 0 0 0 0 0
(DW_OP_addr: 601080)
...
<1><18a>: Abbrev Number: 16 (DW_TAG_array_type)
<18b> DW_AT_data_location: 2 byte block: 97 6
(DW_OP_push_object_address; DW_OP_deref)
<18e> DW_AT_associated : 4 byte block: 97 6 30 2e
(DW_OP_push_object_address; DW_OP_deref; DW_OP_lit0; DW_OP_ne)
<193> DW_AT_type : <0x5d>
<2><197>: Abbrev Number: 17 (DW_TAG_subrange_type)
<198> DW_AT_lower_bound : 4 byte block: 97 23 20 6
(DW_OP_push_object_address; DW_OP_plus_uconst: 32; DW_OP_deref)
<19d> DW_AT_upper_bound : 4 byte block: 97 23 28 6
(DW_OP_push_object_address; DW_OP_plus_uconst: 40; DW_OP_deref)
<1a2> DW_AT_byte_stride : 15 byte block: 97 23 18 6 3 b0 10 60 0 0 0 0
0 6 1e (DW_OP_push_object_address; DW_OP_plus_uconst: 24; DW_OP_deref;
DW_OP_addr: 6010b0; DW_OP_deref; DW_OP_mul)
3. Figure out the expression to read the DW_AT_byte_stride, from the above it
will be:
((*(0x601080 + 24)) * (*0x6010b0))
4. Run the test program, this just confirms what we expect the value
of 'point_dimension' to be, which is: { 2, 2, 2, 2, 2, 2, 2, 2, 2 }.
5. Now fire up GDB on the test program:
$ gdb test
(gdb) break 18
(gdb) run
(gdb) p/d ((*(0x601080 + 24)) * (*0x6010b0))
$1 = 24
# So the stride appears to be 24. Now to check, first, where's the
# first element:
(gdb) p &point_dimension(1)
$2 = (PTR TO -> ( integer(kind=8) )) 0x7fffffffccd8
# Now lets check the stride is correct by examining all the
# remaining elements:
(gdb) x/1w 0x7fffffffccd8 + (24 * 0)
0x7fffffffccd8: 2
(gdb) x/1w 0x7fffffffccd8 + (24 * 1)
0x7fffffffccf0: 2
(gdb) x/1w 0x7fffffffccd8 + (24 * 2)
0x7fffffffcd08: 2
(gdb) x/1w 0x7fffffffccd8 + (24 * 3)
0x7fffffffcd20: 2
(gdb) x/1w 0x7fffffffccd8 + (24 * 4)
0x7fffffffcd38: 2
(gdb) x/1w 0x7fffffffccd8 + (24 * 5)
0x7fffffffcd50: 2
(gdb) x/1w 0x7fffffffccd8 + (24 * 6)
0x7fffffffcd68: 2
(gdb) x/1w 0x7fffffffccd8 + (24 * 7)
0x7fffffffcd80: 2
(gdb) x/1w 0x7fffffffccd8 + (24 * 8)
0x7fffffffcd98: 2
# So it looks like a stride of 24 is correct. Based on the code
# this is what I would expect.
6. Now recompile the test with a later version of GCC. I've tested
8.3.0 and 9.2.0, plus a version from trunk from mid-October 2019.
The data below is from 9.2.0:
<2><e9>: Abbrev Number: 10 (DW_TAG_variable)
<ea> DW_AT_name : (indirect string, offset: 0x0):
point_dimension
<ee> DW_AT_decl_file : 1
<ef> DW_AT_decl_line : 13
<f0> DW_AT_type : <0x10f>
<f4> DW_AT_location : 9 byte block: 3 80 10 60 0 0 0 0 0
(DW_OP_addr: 601080)
...
<1><10f>: Abbrev Number: 13 (DW_TAG_array_type)
<110> DW_AT_data_location: 2 byte block: 97 6
(DW_OP_push_object_address; DW_OP_deref)
<113> DW_AT_associated : 4 byte block: 97 6 30 2e
(DW_OP_push_object_address; DW_OP_deref; DW_OP_lit0; DW_OP_ne)
<118> DW_AT_type : <0x5d>
<2><11c>: Abbrev Number: 14 (DW_TAG_subrange_type)
<11d> DW_AT_lower_bound : 4 byte block: 97 23 30 6
(DW_OP_push_object_address; DW_OP_plus_uconst: 48; DW_OP_deref)
<122> DW_AT_upper_bound : 4 byte block: 97 23 38 6
(DW_OP_push_object_address; DW_OP_plus_uconst: 56; DW_OP_deref)
<127> DW_AT_byte_stride : 6 byte block: 97 23 28 6 38 1e
(DW_OP_push_object_address; DW_OP_plus_uconst: 40; DW_OP_deref; DW_OP_lit8;
DW_OP_mul)
7. Notice that the DW_AT_byte_stride expression has changed, it now
looks like this:
((*(0x601080 + 40)) * 8)
8. Before we validate this in GDB, for our sanity rerun the test
program and confirm that it does the correct thing at run time, it
still prints the array as 9 elements, all containing the value 2.
9. Now fire up GDB on the test program:
$ gdb test
(gdb) break 18
(gdb) run
(gdb) p/d ((*(0x601080 + 40)) * 8)
$1 = 8
# So now the stride is reported as 8. This seems unlikely, but
# lets try it. Where's the first element.
(gdb) p &point_dimension(1)
$2 = (PTR TO -> ( integer(kind=8) )) 0x7fffffffcba8
# Now lets check all the other elements are in the correct place:
(gdb) x/1w 0x7fffffffcba8 + (8 * 0)
0x7fffffffcba8: 2
(gdb) x/1w 0x7fffffffcba8 + (8 * 1)
0x7fffffffcbb0: 3
(gdb) x/1w 0x7fffffffcba8 + (8 * 2)
0x7fffffffcbb8: 1
(gdb) x/1w 0x7fffffffcba8 + (8 * 3)
0x7fffffffcbc0: 2
(gdb) x/1w 0x7fffffffcba8 + (8 * 4)
0x7fffffffcbc8: 3
(gdb) x/1w 0x7fffffffcba8 + (8 * 5)
0x7fffffffcbd0: 1
(gdb) x/1w 0x7fffffffcba8 + (8 * 6)
0x7fffffffcbd8: 2
(gdb) x/1w 0x7fffffffcba8 + (8 * 7)
0x7fffffffcbe0: 3
(gdb) x/1w 0x7fffffffcba8 + (8 * 8)
0x7fffffffcbe8: 1
# Clearly this is not correct.
10. The conclusion is that the DW_AT_byte_stride attribute of the
DW_TAG_subrange_type for Fortran arrays is currently being generated
incorrectly.
>From gcc-bugs-return-662201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 18:56:53 2019
Return-Path: <gcc-bugs-return-662201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112266 invoked by alias); 3 Dec 2019 18:56:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112137 invoked by uid 48); 3 Dec 2019 18:56:48 -0000
From: "ch3root at openwall dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92486] Wrong optimization: padding in structs is not copied even with memcpy
Date: Tue, 03 Dec 2019 18:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ch3root at openwall dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92486-4-SFnmJKZ7pf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92486-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92486-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00271.txt.bz2
Content-length: 935
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92486
--- Comment #16 from Alexander Cherepanov <ch3root at openwall dot com> ---
BTW this bug combines nicely with pr71460. Possible effects:
- padding in a long double inside a struct is lost on x86-64;
- sNaN is converted to qNaN in a double inside a struct on x86-32.
Both are illustrated at https://godbolt.org/z/VKmGbY . E.g., the former, this:
----------------------------------------------------------------------
#include <string.h>
struct s1 { long double d; };
void f1(struct s1 *restrict p, struct s1 *restrict q)
{
*p = *q;
memcpy(p, q, sizeof(struct s1));
}
----------------------------------------------------------------------
is compiled into this:
----------------------------------------------------------------------
f1:
fldt (%rsi)
fstpt (%rdi)
ret
----------------------------------------------------------------------
>From gcc-bugs-return-662202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 19:04:35 2019
Return-Path: <gcc-bugs-return-662202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18800 invoked by alias); 3 Dec 2019 19:04:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18225 invoked by uid 48); 3 Dec 2019 19:04:27 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92776] New: Can't define member function out of line with non-type template parameter
Date: Tue, 03 Dec 2019 19:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: barry.revzin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00272.txt.bz2
Content-length: 1004
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92776
Bug ID: 92776
Summary: Can't define member function out of line with non-type
template parameter
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: barry.revzin at gmail dot com
Target Milestone: ---
From StackOverflow (https://stackoverflow.com/q/59163716/2069064):
struct A {};
template <A a>
struct B {
void f();
};
template <A a>
void B<a>::f() { }
On the gcc trunk on godbolt, this fails with:
<source>:9:14: error: invalid use of incomplete type 'struct B<((const A)a)>'
9 | void B<a>::f() { }
| ^
<source>:4:8: note: declaration of 'struct B<((const A)a)>'
4 | struct B {
| ^
But compiles fine if you replace the declaration of A with something like
"using A = int;"
>From gcc-bugs-return-662203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 19:09:37 2019
Return-Path: <gcc-bugs-return-662203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31029 invoked by alias); 3 Dec 2019 19:09:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30970 invoked by uid 48); 3 Dec 2019 19:09:32 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92756] [9/10 Regression] ICE in lower_omp, at omp-low.c:12988
Date: Tue, 03 Dec 2019 19:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status assigned_to target_milestone
Message-ID: <bug-92756-4-u7JRzJ7gRD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00273.txt.bz2
Content-length: 879
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92756
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|ice-on-invalid-code |
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Target Milestone|8.4 |9.3
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
It used to be invalid in OpenMP 4.5, but is completely valid in OpenMP 5.0.
Before the above mentioned change, it was the generic code that used to
diagnose it as invalid, but that was removed when C/C++ started supporting it.
Easiest is to support in Fortran too, after all, Fortran already gained some
OpenMP 5.0 features.
>From gcc-bugs-return-662204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 19:12:31 2019
Return-Path: <gcc-bugs-return-662204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50919 invoked by alias); 3 Dec 2019 19:12:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50836 invoked by uid 48); 3 Dec 2019 19:12:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92756] [9/10 Regression] ICE in lower_omp, at omp-low.c:12988
Date: Tue, 03 Dec 2019 19:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92756-4-PNyI1XBcQs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00274.txt.bz2
Content-length: 254
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92756
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47412
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47412&action=edit
gcc10-pr92756.patch
Untested fix.
>From gcc-bugs-return-662205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 19:28:29 2019
Return-Path: <gcc-bugs-return-662205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19354 invoked by alias); 3 Dec 2019 19:28:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19288 invoked by uid 55); 3 Dec 2019 19:28:23 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91369] Implement P0784R7: constexpr new
Date: Tue, 03 Dec 2019 19:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91369-4-QcIuuigQW6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00275.txt.bz2
Content-length: 1353
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91369
--- Comment #22 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Dec 3 19:27:47 2019
New Revision: 278945
URL: https://gcc.gnu.org/viewcvs?rev=278945&root=gcc&view=rev
Log:
PR c++/91369
* constexpr.c (struct constexpr_global_ctx): Add cleanups member,
initialize it in the ctor.
(cxx_eval_constant_expression) <case TARGET_EXPR>: If TARGET_EXPR_SLOT
is already in the values hash_map, don't evaluate it again. Put
TARGET_EXPR_SLOT into hash_map even if not lval, and push it into
save_exprs too. If there is TARGET_EXPR_CLEANUP and not
CLEANUP_EH_ONLY, push the cleanup to cleanups vector.
<case CLEANUP_POINT_EXPR>: Save outer cleanups, set cleanups to
local auto_vec, after evaluating the body evaluate cleanups and
restore previous cleanups.
<case TRY_CATCH_EXPR>: Don't crash if the first operand is NULL_TREE.
(cxx_eval_outermost_constant_expr): Set cleanups to local auto_vec,
after evaluating the expression evaluate cleanups.
* g++.dg/cpp2a/constexpr-new8.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-new8.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/constexpr.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 19:32:31 2019
Return-Path: <gcc-bugs-return-662206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24631 invoked by alias); 3 Dec 2019 19:32:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24437 invoked by uid 48); 3 Dec 2019 19:32:26 -0000
From: "jason.e.cobb at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92777] New: ICE on concept containing lambda with auto variable declaration
Date: Tue, 03 Dec 2019 19:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason.e.cobb at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92777-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00276.txt.bz2
Content-length: 1069
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92777
Bug ID: 92777
Summary: ICE on concept containing lambda with auto variable
declaration
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jason.e.cobb at gmail dot com
Target Milestone: ---
With GCC trunk in std=c++2a mode and the following code:
[begin code]
template<typename>
concept auto_in_lambda = requires() {
[](){
auto x = 4;
}();
};
static_assert(auto_in_lambda<int>);
[end code]
GCC ICEs with the following message:
<source>: In lambda function:
<source>:4:14: internal compiler error: in tsubst_decl, at cp/pt.c:14375
4 | auto x = 4;
| ^
GCC does not ICE if the concept is never instantiated, nor does it ICE if the
"auto" variable is changed to have a defined type.
On Compiler Explorer: https://godbolt.org/z/myujUX
>From gcc-bugs-return-662207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 19:33:22 2019
Return-Path: <gcc-bugs-return-662207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44790 invoked by alias); 3 Dec 2019 19:33:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44335 invoked by uid 48); 3 Dec 2019 19:33:18 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91369] Implement P0784R7: constexpr new
Date: Tue, 03 Dec 2019 19:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91369-4-p7iJZ0WvaL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00277.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91369
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #23 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Should be fixed now.
>From gcc-bugs-return-662208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 19:33:23 2019
Return-Path: <gcc-bugs-return-662208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45029 invoked by alias); 3 Dec 2019 19:33:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44447 invoked by uid 48); 3 Dec 2019 19:33:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88323] implement C++20 language features.
Date: Tue, 03 Dec 2019 19:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88323-4-FAMgRUkSFe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88323-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88323-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00278.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88323
Bug 88323 depends on bug 91369, which changed state.
Bug 91369 Summary: Implement P0784R7: constexpr new
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91369
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-662209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 19:33:23 2019
Return-Path: <gcc-bugs-return-662209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45058 invoked by alias); 3 Dec 2019 19:33:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44379 invoked by uid 48); 3 Dec 2019 19:33:18 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55004] [meta-bug] constexpr issues
Date: Tue, 03 Dec 2019 19:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-55004-4-VrwVOAhn04@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55004-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55004-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00279.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004
Bug 55004 depends on bug 91369, which changed state.
Bug 91369 Summary: Implement P0784R7: constexpr new
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91369
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-662210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 19:44:00 2019
Return-Path: <gcc-bugs-return-662210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72766 invoked by alias); 3 Dec 2019 19:44:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72737 invoked by uid 48); 3 Dec 2019 19:43:56 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92735] unused member variable causes code to compile for member to function for undefined function
Date: Tue, 03 Dec 2019 19:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92735-4-aHhuFTMNHx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92735-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92735-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00280.txt.bz2
Content-length: 196
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92735
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Related to http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_active.html#1396
>From gcc-bugs-return-662211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 19:52:59 2019
Return-Path: <gcc-bugs-return-662211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81259 invoked by alias); 3 Dec 2019 19:52:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81190 invoked by uid 48); 3 Dec 2019 19:52:53 -0000
From: "bernds at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92767] [m68k]: Random ICE: verify_flow_info failed
Date: Tue, 03 Dec 2019 19:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernds at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92767-4-rNDKnpq6Pj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92767-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00281.txt.bz2
Content-length: 380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92767
--- Comment #1 from Bernd Schmidt <bernds at gcc dot gnu.org> ---
People will be more likely to look at it if there's a preprocessed .i file that
reproduces the issue, ideally with a cross compiler rather than a native
bootstrap.
If it only occurs when bootstrapping, narrowing down the offending commit would
be helpful.
>From gcc-bugs-return-662212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 20:47:04 2019
Return-Path: <gcc-bugs-return-662212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36747 invoked by alias); 3 Dec 2019 20:47:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36692 invoked by uid 48); 3 Dec 2019 20:46:59 -0000
From: "h2+bugs at fsfe dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92778] New: ICE: Illegal instruction signal terminated program cc1plus
Date: Tue, 03 Dec 2019 20:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: h2+bugs at fsfe dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00282.txt.bz2
Content-length: 1022
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92778
Bug ID: 92778
Summary: ICE: Illegal instruction signal terminated program
cc1plus
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: h2+bugs at fsfe dot org
Target Milestone: ---
The beautiful intermediate code that I attached (Yes, I know it's huge), ICEs
with the very non-descriptive message of:
g++9: internal compiler error: Illegal instruction signal terminated program
cc1plus
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
The command to build the intermediate code is:
g++9 -std=c++17 -fconcepts -pthread -fopenmp lambda.ii
Reproducible with the compiler versions:
g++9 (FreeBSD Ports Collection) 9.2.0
g++9 (FreeBSD Ports Collection) 9.2.1 20191123
>From gcc-bugs-return-662213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 20:50:36 2019
Return-Path: <gcc-bugs-return-662213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51035 invoked by alias); 3 Dec 2019 20:50:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50993 invoked by uid 48); 3 Dec 2019 20:50:31 -0000
From: "h2+bugs at fsfe dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92778] ICE: Illegal instruction signal terminated program cc1plus
Date: Tue, 03 Dec 2019 20:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: h2+bugs at fsfe dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92778-4-lLFbfhTkGW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92778-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00283.txt.bz2
Content-length: 189
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92778
--- Comment #1 from Hannes Hauswedell <h2+bugs at fsfe dot org> ---
Here is the intermediate code:
https://hauswedell.net/lambda.ii.xz
>From gcc-bugs-return-662214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 20:51:28 2019
Return-Path: <gcc-bugs-return-662214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52157 invoked by alias); 3 Dec 2019 20:51:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52073 invoked by uid 48); 3 Dec 2019 20:51:23 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55735] ICE with deferred-length strings in COMMON
Date: Tue, 03 Dec 2019 20:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-55735-4-n1iFmfuXi3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55735-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55735-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00284.txt.bz2
Content-length: 1308
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55735
G. Steinmetz <gscfq@t-online.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gscfq@t-online.de
--- Comment #13 from G. Steinmetz <gscfq@t-online.de> ---
Updating variants :
$ cat z1.f90
program p
character(:), pointer :: c
common c
c = 'abc'
end
$ cat z2.f90
program p
character(:), pointer :: c
common c
n = len_trim(c)
end
$ gfortran-10-20191201 -c z1.f90
z1.f90:4:0:
4 | c = 'abc'
|
internal compiler error: in gfc_conv_variable, at fortran/trans-expr.c:2789
0x708eb9 gfc_conv_variable
../../gcc/fortran/trans-expr.c:2789
0x704afa gfc_conv_expr(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-expr.c:8665
0x71470f gfc_trans_assignment_1
../../gcc/fortran/trans-expr.c:10884
0x6d4617 trans_code
../../gcc/fortran/trans.c:1852
0x6fda64 gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6798
0x686c26 translate_all_program_units
../../gcc/fortran/parse.c:6302
0x686c26 gfc_parse_file()
../../gcc/fortran/parse.c:6541
0x6d10bf gfc_be_parse_file
../../gcc/fortran/f95-lang.c:210
>From gcc-bugs-return-662215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 20:51:43 2019
Return-Path: <gcc-bugs-return-662215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52925 invoked by alias); 3 Dec 2019 20:51:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52835 invoked by uid 48); 3 Dec 2019 20:51:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92778] ICE: Illegal instruction signal terminated program cc1plus
Date: Tue, 03 Dec 2019 20:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92778-4-GpR0yM1brU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92778-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00285.txt.bz2
Content-length: 247
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92778
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This usually means you built GCC (or one of the libraries it uses, like libgmp)
on a different machine with a different CPU.
>From gcc-bugs-return-662216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 20:52:08 2019
Return-Path: <gcc-bugs-return-662216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53789 invoked by alias); 3 Dec 2019 20:52:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53730 invoked by uid 48); 3 Dec 2019 20:52:02 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55735] ICE with deferred-length strings in COMMON
Date: Tue, 03 Dec 2019 20:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55735-4-k6iAeWtDW7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55735-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55735-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00286.txt.bz2
Content-length: 1080
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55735
--- Comment #14 from G. Steinmetz <gscfq@t-online.de> ---
$ cat z3.f90
program p
character(:), pointer :: c
common c
n = len(c)
end
$ gfortran-10-20191201 -c z3.f90
z3.f90:4:0:
4 | n = len(c)
|
internal compiler error: in gfc_conv_intrinsic_len, at
fortran/trans-intrinsic.c:7122
0x72ee62 gfc_conv_intrinsic_len
../../gcc/fortran/trans-intrinsic.c:7122
0x72ee62 gfc_conv_intrinsic_function(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-intrinsic.c:10166
0x704ada gfc_conv_expr(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-expr.c:8657
0x71445a gfc_trans_assignment_1
../../gcc/fortran/trans-expr.c:10848
0x6d4617 trans_code
../../gcc/fortran/trans.c:1852
0x6fda64 gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6798
0x686c26 translate_all_program_units
../../gcc/fortran/parse.c:6302
0x686c26 gfc_parse_file()
../../gcc/fortran/parse.c:6541
0x6d10bf gfc_be_parse_file
../../gcc/fortran/f95-lang.c:210
>From gcc-bugs-return-662217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 20:53:40 2019
Return-Path: <gcc-bugs-return-662217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106303 invoked by alias); 3 Dec 2019 20:53:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106215 invoked by uid 48); 3 Dec 2019 20:53:36 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92779] New: [8/9/10 Regression] ICE in gfc_conv_intrinsic_funcall, at fortran/trans-intrinsic.c:4225
Date: Tue, 03 Dec 2019 20:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92779-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00287.txt.bz2
Content-length: 2021
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92779
Bug ID: 92779
Summary: [8/9/10 Regression] ICE in gfc_conv_intrinsic_funcall,
at fortran/trans-intrinsic.c:4225
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Starting with gcc-8 before 20180525 :
$ cat z1.f90
program p
character(3) :: a = 'abc'
associate (y => spread(trim(a),1,2) // 'd')
print *, y
end associate
end
$ gfortran-7 -c z1.f90
$
$ gfortran-10-20191201 -c z1.f90
z1.f90:4:0:
4 | print *, y
|
internal compiler error: in gfc_conv_intrinsic_funcall, at
fortran/trans-intrinsic.c:4225
0x729f9e gfc_conv_intrinsic_funcall
../../gcc/fortran/trans-intrinsic.c:4225
0x72cfe7 gfc_conv_intrinsic_function(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-intrinsic.c:9778
0x704ada gfc_conv_expr(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-expr.c:8657
0x709129 gfc_conv_string_length(gfc_charlen*, gfc_expr*, stmtblock_t*)
../../gcc/fortran/trans-expr.c:2276
0x6e7b97 get_array_charlen
../../gcc/fortran/trans-array.c:7082
0x6e7c6e get_array_charlen
../../gcc/fortran/trans-array.c:7014
0x6e671a gfc_conv_expr_descriptor(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-array.c:7402
0x740442 trans_associate_var
../../gcc/fortran/trans-stmt.c:1889
0x747101 gfc_trans_block_construct(gfc_code*)
../../gcc/fortran/trans-stmt.c:2282
0x6d47b7 trans_code
../../gcc/fortran/trans.c:1948
0x6fda64 gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6798
0x686c26 translate_all_program_units
../../gcc/fortran/parse.c:6302
0x686c26 gfc_parse_file()
../../gcc/fortran/parse.c:6541
0x6d10bf gfc_be_parse_file
../../gcc/fortran/f95-lang.c:210
>From gcc-bugs-return-662218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 20:55:02 2019
Return-Path: <gcc-bugs-return-662218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123087 invoked by alias); 3 Dec 2019 20:55:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121982 invoked by uid 48); 3 Dec 2019 20:54:56 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92779] [8/9/10 Regression] ICE in gfc_conv_intrinsic_funcall, at fortran/trans-intrinsic.c:4225
Date: Tue, 03 Dec 2019 20:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-92779-4-zSp6IetU3l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92779-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92779-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00288.txt.bz2
Content-length: 764
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92779
G. Steinmetz <gscfq@t-online.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
--- Comment #1 from G. Steinmetz <gscfq@t-online.de> ---
These slightly modified variants are doing well :
$ cat z2.f90
program p
associate (y => spread(trim('abc'),1,2) // 'd')
print *, y
end associate
end
$ cat z3.f90
program p
character(3) :: a = 'abc'
associate (y => spread(a,1,2) // 'd')
print *, y
end associate
end
$ gfortran-10-20191201 z2.f90 && ./a.out
abcdabcd
$
$ gfortran-10-20191201 z3.f90 && ./a.out
abcdabcd
>From gcc-bugs-return-662219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 20:59:16 2019
Return-Path: <gcc-bugs-return-662219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27655 invoked by alias); 3 Dec 2019 20:59:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26936 invoked by uid 48); 3 Dec 2019 20:59:09 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92778] ICE: Illegal instruction signal terminated program cc1plus
Date: Tue, 03 Dec 2019 20:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92778-4-1p2E5W424h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92778-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00289.txt.bz2
Content-length: 3513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92778
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Because "illegal instruction" happens if the executable contains an instruction
that your CPU doesn't support. And that should never happen if you built GCC
correctly.
When I try to compile with gcc-9-branch it I get:
g++: internal compiler error: Segmentation fault signal terminated program
cc1plus
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
which suggests a stackoverflow or other memory problem.
With trunk I get:
In file included from
/home/hannes/devel/lambda/submodules/seqan3/include/seqan3/std/iterator:24,
from
/home/hannes/devel/lambda/submodules/seqan3/include/seqan3/core/type_traits/iterator.hpp:20,
from
/home/hannes/devel/lambda/submodules/seqan3/include/seqan3/core/type_traits/range.hpp:20,
from
/home/hannes/devel/lambda/submodules/seqan3/include/seqan3/range/views/translate_join.hpp:18,
from /home/hannes/devel/lambda/src/seqan2seqan3.hpp:7,
from /home/hannes/devel/lambda/src/lambda.cpp:22:
/home/hannes/devel/lambda/submodules/seqan3/submodules/range-v3/include/range/v3/iterator/access.hpp:222:76:
internal compiler error: in strip_typedefs, at cp/tree.c:1681
0x675f3a strip_typedefs(tree_node*, bool*, unsigned int)
/home/jwakely/src/gcc/gcc/gcc/cp/tree.c:1681
0x675f3a strip_typedefs(tree_node*, bool*, unsigned int)
/home/jwakely/src/gcc/gcc/gcc/cp/tree.c:1461
0x9f8792 canonicalize_type_argument
/home/jwakely/src/gcc/gcc/gcc/cp/pt.c:7935
0xa230db coerce_template_parms
/home/jwakely/src/gcc/gcc/gcc/cp/pt.c:8778
0xa336b9 lookup_template_class_1
/home/jwakely/src/gcc/gcc/gcc/cp/pt.c:9615
0xa336b9 lookup_template_class(tree_node*, tree_node*, tree_node*, tree_node*,
int, int)
/home/jwakely/src/gcc/gcc/gcc/cp/pt.c:9985
0xa5d73b finish_template_type(tree_node*, tree_node*, int)
/home/jwakely/src/gcc/gcc/gcc/cp/semantics.c:3396
0x9e44ad cp_parser_template_id
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:16544
0x9e473a cp_parser_class_name
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:23416
0x9e10bb cp_parser_qualifying_entity
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:6705
0x9e10bb cp_parser_nested_name_specifier_opt
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:6388
0x9ddfd0 cp_parser_simple_type_specifier
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:17925
0x9df247 cp_parser_postfix_expression
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:7103
0x9e78cf cp_parser_unary_expression
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:8472
0x9bf9af cp_parser_cast_expression
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:9365
0x9c0605 cp_parser_simple_cast_expression
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:29048
0x9c0605 cp_parser_binary_expression
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:9533
0x9c1247 cp_parser_assignment_expression
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:9768
0x9e318a cp_parser_template_argument
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:17196
0x9e318a cp_parser_template_argument_list
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:16895
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-662220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 21:01:24 2019
Return-Path: <gcc-bugs-return-662220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43665 invoked by alias); 3 Dec 2019 21:01:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42760 invoked by uid 48); 3 Dec 2019 21:01:17 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92780] New: [10 Regression] ICE in gfc_get_class_from_expr, at fortran/trans-expr.c:484
Date: Tue, 03 Dec 2019 21:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92780-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00290.txt.bz2
Content-length: 1809
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92780
Bug ID: 92780
Summary: [10 Regression] ICE in gfc_get_class_from_expr, at
fortran/trans-expr.c:484
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Changed between 20190922 (silently accepted) and 20190929 (ICE) :
$ cat z1.f90
program p
associate (y => p)
end associate
end
$ gfortran-10-20190922 -c z1.f90
$
$ gfortran-10-20191201 -c z1.f90
z1.f90:2:0:
2 | associate (y => p)
|
internal compiler error: tree check: expected class 'expression', have
'declaration' (function_decl) in tree_operand_check, at tree.h:3771
0x5ee034 tree_class_check_failed(tree_node const*, tree_code_class, char
const*, int, char const*)
../../gcc/tree.c:9738
0x742f19 expr_check(tree_node*, char const*, int, char const*)
../../gcc/tree.h:3442
0x742f19 tree_operand_check(tree_node*, int, char const*, int, char const*)
../../gcc/tree.h:3771
0x742f19 gfc_get_class_from_expr(tree_node*)
../../gcc/fortran/trans-expr.c:484
0x79b4c2 trans_associate_var
../../gcc/fortran/trans-stmt.c:2099
0x7a1d51 gfc_trans_block_construct(gfc_code*)
../../gcc/fortran/trans-stmt.c:2282
0x706e17 trans_code
../../gcc/fortran/trans.c:1948
0x73e04d gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6798
0x6b80f6 translate_all_program_units
../../gcc/fortran/parse.c:6302
0x6b80f6 gfc_parse_file()
../../gcc/fortran/parse.c:6541
0x7030ef gfc_be_parse_file
../../gcc/fortran/f95-lang.c:210
>From gcc-bugs-return-662221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 21:03:48 2019
Return-Path: <gcc-bugs-return-662221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80382 invoked by alias); 3 Dec 2019 21:03:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80364 invoked by uid 48); 3 Dec 2019 21:03:43 -0000
From: "h2+bugs at fsfe dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92778] ICE: Illegal instruction signal terminated program cc1plus
Date: Tue, 03 Dec 2019 21:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: h2+bugs at fsfe dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92778-4-nTJxQcNM1n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92778-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00291.txt.bz2
Content-length: 594
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92778
--- Comment #4 from Hannes Hauswedell <h2+bugs at fsfe dot org> ---
Thanks for the quick reply, Jonathan!
I am familiar with the error in general, but I am using vanilla packages by the
vendor (FreeBSD) which should not have any funky optimisations. Also, my
colleague just reported that she is seeing the same on gcc9 on Ubuntu -- I'll
try to confirm that myself.
The code is not expected to build on trunk/gcc10 because of other known and
reported issues (strip_typedefs...), so I think what you are seeing is not the
same thing.
>From gcc-bugs-return-662222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 21:06:26 2019
Return-Path: <gcc-bugs-return-662222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83341 invoked by alias); 3 Dec 2019 21:06:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83298 invoked by uid 48); 3 Dec 2019 21:06:21 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92781] New: ICE in convert_nonlocal_reference_op, at tree-nested.c:1065
Date: Tue, 03 Dec 2019 21:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92781-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00292.txt.bz2
Content-length: 3355
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92781
Bug ID: 92781
Summary: ICE in convert_nonlocal_reference_op, at
tree-nested.c:1065
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
This affects versions down to at least gfortran-4.9;
Starting with a legal source ...
$ cat z0.f90
function f()
character(:), allocatable :: f
f = 'abc'
end
$ gfortran-10-20191201 -c z0.f90
$
... then adding a local procedure (here unused and empty) :
$ cat z1.f90
function f()
character(:), allocatable :: f
f = 'abc'
contains
subroutine s
end
end
$ gfortran-10-20191201 -c z1.f90
z1.f90:1:0:
1 | function f()
|
internal compiler error: Segmentation fault
0xd0039f crash_signal
../../gcc/toplev.c:328
0xdbed18 contains_struct_check(tree_node*, tree_node_structure_enum, char
const*, int, char const*)
../../gcc/tree.h:3386
0xdbed18 convert_nonlocal_reference_op
../../gcc/tree-nested.c:1065
0x1028493 walk_tree_1(tree_node**, tree_node* (*)(tree_node**, int*, void*),
void*, hash_set<tree_node*, false, default_hash_traits<tree_node*> >*,
tree_node* (*)(tree_node**, int*, tree_node* (*)(tree_node**, int*, void*),
void*, hash_set<tree_node*, false, default_hash_traits<tree_node*> >*))
../../gcc/tree.c:11957
0x9fc177 walk_gimple_op(gimple*, tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
../../gcc/gimple-walk.c:221
0x9fc558 walk_gimple_stmt(gimple_stmt_iterator*, tree_node*
(*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**,
int*, void*), walk_stmt_info*)
../../gcc/gimple-walk.c:596
0x9fc740 walk_gimple_seq_mod(gimple**, tree_node* (*)(gimple_stmt_iterator*,
bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
../../gcc/gimple-walk.c:51
0x9fc681 walk_gimple_stmt(gimple_stmt_iterator*, tree_node*
(*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**,
int*, void*), walk_stmt_info*)
../../gcc/gimple-walk.c:641
0x9fc740 walk_gimple_seq_mod(gimple**, tree_node* (*)(gimple_stmt_iterator*,
bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
../../gcc/gimple-walk.c:51
0x9fc5e1 walk_gimple_stmt(gimple_stmt_iterator*, tree_node*
(*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**,
int*, void*), walk_stmt_info*)
../../gcc/gimple-walk.c:605
0x9fc740 walk_gimple_seq_mod(gimple**, tree_node* (*)(gimple_stmt_iterator*,
bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
../../gcc/gimple-walk.c:51
0xdb7df8 walk_body
../../gcc/tree-nested.c:713
0xdb7e48 walk_function
../../gcc/tree-nested.c:724
0xdb7e48 walk_all_functions
../../gcc/tree-nested.c:789
0xdc174f lower_nested_functions(tree_node*)
../../gcc/tree-nested.c:3528
0x84ed00 cgraph_node::analyze()
../../gcc/cgraphunit.c:675
0x8521f5 analyze_functions
../../gcc/cgraphunit.c:1212
0x853572 symbol_table::finalize_compilation_unit()
../../gcc/cgraphunit.c:2925
>From gcc-bugs-return-662223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 21:09:44 2019
Return-Path: <gcc-bugs-return-662223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95705 invoked by alias); 3 Dec 2019 21:09:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95674 invoked by uid 48); 3 Dec 2019 21:09:39 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92782] New: ICE in fold_convert_loc, at fold-const.c:2431
Date: Tue, 03 Dec 2019 21:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00293.txt.bz2
Content-length: 1255
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92782
Bug ID: 92782
Summary: ICE in fold_convert_loc, at fold-const.c:2431
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
With an improper type down to gfortran-7 :
$ cat z1.f90
subroutine test(a)
real :: a
!$omp target is_device_ptr(a)
!$omp end target
end
$ gfortran-10-20191201 -c z1.f90 -fopenmp
during GIMPLE pass: omplower
z1.f90:3:0:
3 | !$omp target is_device_ptr(a)
|
internal compiler error: in fold_convert_loc, at fold-const.c:2431
0x8ca047 fold_convert_loc(unsigned int, tree_node*, tree_node*)
../../gcc/fold-const.c:2430
0xa7c66b lower_omp_target
../../gcc/omp-low.c:12032
0xa7c66b lower_omp_1
../../gcc/omp-low.c:12846
0xa7c66b lower_omp
../../gcc/omp-low.c:12989
0xa784ee lower_omp_1
../../gcc/omp-low.c:12781
0xa784ee lower_omp
../../gcc/omp-low.c:12989
0xa7f99b execute_lower_omp
../../gcc/omp-low.c:13031
0xa7f99b execute
../../gcc/omp-low.c:13079
>From gcc-bugs-return-662224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 21:13:00 2019
Return-Path: <gcc-bugs-return-662224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98994 invoked by alias); 3 Dec 2019 21:12:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98913 invoked by uid 48); 3 Dec 2019 21:12:55 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92767] [m68k]: Random ICE: verify_flow_info failed
Date: Tue, 03 Dec 2019 21:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92767-4-gnCNTyhicf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92767-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00294.txt.bz2
Content-length: 363
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92767
--- Comment #2 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
A local native bootstrap went through without problems, so maybe it's a problem
with the Debian buildds. I'll try to track it down and if I can reproduce it
locally, I will provide the preprocessed source, of course.
>From gcc-bugs-return-662225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 21:31:14 2019
Return-Path: <gcc-bugs-return-662225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119312 invoked by alias); 3 Dec 2019 21:30:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119093 invoked by uid 48); 3 Dec 2019 21:30:44 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92661] [10 Regression] Bootstrap failure with builtin-types.def change
Date: Tue, 03 Dec 2019 21:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92661-4-wUNnkhT9j7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92661-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92661-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00295.txt.bz2
Content-length: 392
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92661
--- Comment #11 from Peter Bergner <bergner at gcc dot gnu.org> ---
I have a patch I'm testing for the second problem. Basically, it verifies that
the builtin we are overloading has already been defined or not. If it hasn't
(ie, it wasn't supported for some reason, like dfp being disabled), then we
skip defining this builtin too.
>From gcc-bugs-return-662226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 21:46:00 2019
Return-Path: <gcc-bugs-return-662226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3109 invoked by alias); 3 Dec 2019 21:45:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2979 invoked by uid 48); 3 Dec 2019 21:45:51 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92783] New: [10 regression] SEGV in field_byte_offset
Date: Tue, 03 Dec 2019 21:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget
Message-ID: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00296.txt.bz2
Content-length: 6827
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92783
Bug ID: 92783
Summary: [10 regression] SEGV in field_byte_offset
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: ebotcazou at gcc dot gnu.org
Target Milestone: ---
Target: sparc-sun-solaris2.11
Between 20191202 (r278904) and 20191203 (r278942), Solaris/SPARC Ada bootstrap
got broken:
/var/gcc/regression/trunk/11.5-gcc/build/./gcc/xgcc
-B/var/gcc/regression/trunk/11.5-gcc/build/./gcc/
-B/vol/gcc/sparc-sun-solaris2.11/bin/ -B/vol/gcc/sparc-sun-solaris2.11/lib/
-isystem /vol/gcc/sparc-sun-solaris2.11/include -isystem
/vol/gcc/sparc-sun-solaris2.11/sys-include -fchecking=1 -c -g -O2 -m64 -fPIC
-W -Wall -gnatpg -nostdinc -m64 s-interr.adb -o s-interr.o
raised CONSTRAINT_ERROR : SIGSEGV
The failure can be reproduced with
$ gnat1 -quiet -nostdinc -O2 -g -m64 -gnatpg -mcpu=v9 -mptr64 -mstack-bias
-mno-v8plus -gnatO s-interr.o s-interr.adb -o s-interr.s
Thread 2 received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1 (LWP 1)]
0x00c2d3d0 in field_byte_offset (cst_offset=0xffbfd768, ctx=0xffbfd908,
decl=0xfa901340) at /vol/gcc/src/hg/trunk/local/gcc/tree.h:3530
3530 return __t;
1: x/i $pc
=> 0xc2d3d0 <add_data_member_location_attribute(dw_die_ref, tree,
vlr_context*)+224>: lduh [ %g1 ], %g1
(gdb) p/x $g1
$1 = 0x0
(gdb) where
#0 0x00c2d3d0 in field_byte_offset (cst_offset=0xffbfd768, ctx=0xffbfd908,
decl=0xfa901340) at /vol/gcc/src/hg/trunk/local/gcc/tree.h:3530
#1 add_data_member_location_attribute (die=0xfaa25f50, decl=0xfa901340,
ctx=0xffbfd908) at /vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:19425
#2 0x00c2deb8 in gen_field_die (context_die=<optimized out>, ctx=0xffbfd908,
decl=0xfa901340) at /vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:24408
#3 gen_field_die (decl=0xfa901340, ctx=0xffbfd908,
context_die=<optimized out>)
at /vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:24380
#4 0x00c10e20 in gen_decl_die (decl=0xfa901340, origin=0x0, ctx=0xffbfd908,
context_die=0xfaa25e90)
at /vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:26548
#5 0x00c14178 in gen_member_die (context_die=<optimized out>, type=0xfa9049c0)
at /vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:25298
#6 gen_struct_or_union_type_die (usage=<optimized out>,
context_die=0xfa82e000, type=0xfa9049c0)
at /vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:25394
#7 gen_tagged_type_die (type=0xfa9049c0, context_die=0xfa82e000,
usage=<optimized out>) at /vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:25595
#8 0x00c15904 in gen_tagged_type_die (usage=DINFO_USAGE_DIR_USE,
context_die=0xfa82e000, type=0xfa9049c0)
at /vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:4256
#9 gen_type_die_with_usage (type=0xfa9049c0, context_die=0xfa82e000,
usage=DINFO_USAGE_DIR_USE) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:25790
#10 0x00c17708 in gen_type_die (type=0xfa9049c0, context_die=0xfa82e000) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:25844
#11 0x00c178d0 in add_gnat_descriptive_type_attribute (die=0xfaa25560,
type=0xfa904300, context_die=0xfa82e000) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:20713
#12 0x00c14190 in gen_struct_or_union_type_die (usage=<optimized out>,
context_die=0xfa82e000, type=0xfa904300) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:25396
#13 gen_tagged_type_die (type=0xfa904300, context_die=0xfa82e000,
usage=<optimized out>) at /vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:25595
#14 0x00c15904 in gen_tagged_type_die (usage=DINFO_USAGE_DIR_USE,
context_die=0xfa82e000, type=0xfa904300) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:4256
#15 gen_type_die_with_usage (type=0xfa904300, context_die=0xfa82e000,
usage=DINFO_USAGE_DIR_USE) at /vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:25790
#16 0x00c17708 in gen_type_die (type=0xfa904300, context_die=0xfa82e000) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:25844
#17 0x00c18148 in modified_type_die (type=0xfa904300, cv_quals=0,
reverse=<optimized out>, context_die=0xfa82e000) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:13446
#18 0x00c19cf4 in force_type_die (type=0xfa904300) at
/vol/gcc/src/hg/trunk/local/gcc/tree.h:3397
#19 0x00c19dc4 in force_type_die (type=0xfa904300) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:26218
#20 get_context_die (context=0xfa904300) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:26138
#21 get_context_die (context=<optimized out>) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:26130
#22 force_type_die (type=0xfa9043c0) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:26220
#23 0x00c1a030 in force_type_die (type=0xfa9043c0) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:26218
#24 get_context_die (context=0xfa9043c0) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:26138
#25 0x00c15fa8 in gen_descr_array_type_die (context_die=0xfa82e000,
info=0xffbfe0a0, type=0xfa904540) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:25712
#26 gen_type_die_with_usage (type=0xfa904540, context_die=0xfa82e000,
usage=DINFO_USAGE_DIR_USE) at /vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:25712
#27 0x00c17708 in gen_type_die (type=0xfa904540, context_die=0xfa82e000) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:25844
#28 0x00c10a28 in gen_decl_die (decl=0xfa900c60, origin=<optimized out>,
ctx=<optimized out>, context_die=0xfa82e000) at
/vol/gcc/src/hg/trunk/local/gcc/tree.h:3388
#29 0x00c12628 in dwarf2out_decl (decl=0xfa900c60) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:27017
#30 0x00c12cac in dwarf2out_type_decl (local=0, decl=0xfa900c60) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:26744
#31 dwarf2out_type_decl (decl=0xfa900c60, local=0) at
/vol/gcc/src/hg/trunk/local/gcc/dwarf2out.c:26739
#32 0x006516ac in gnat_write_global_declarations () at
/vol/gcc/src/hg/trunk/local/gcc/ada/gcc-interface/utils.c:5804
#33 0x00638478 in gnat_parse_file () at
/vol/gcc/src/hg/trunk/local/gcc/ada/gcc-interface/misc.c:119
#34 0x010bdcc0 in compile_file () at
/vol/gcc/src/hg/trunk/local/gcc/toplev.c:458
#35 0x010c0960 in do_compile () at
/vol/gcc/src/hg/trunk/local/gcc/toplev.c:2267
#36 toplev::main (this=0xffbfe60e, argc=<optimized out>, argv=<optimized out>)
at /vol/gcc/src/hg/trunk/local/gcc/toplev.c:2406
#37 0x0197c5e8 in main (argc=26, argv=0xffbfe674) at
/vol/gcc/src/hg/trunk/local/gcc/main.c:39
No patch in that range is immediately obvious, so I'll have to run a reghunt.
>From gcc-bugs-return-662227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 21:46:14 2019
Return-Path: <gcc-bugs-return-662227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3701 invoked by alias); 3 Dec 2019 21:46:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3149 invoked by uid 48); 3 Dec 2019 21:46:00 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92783] [10 regression] SEGV in field_byte_offset
Date: Tue, 03 Dec 2019 21:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-92783-4-7m8rk9PejI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00297.txt.bz2
Content-length: 286
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92783
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-662228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 21:59:43 2019
Return-Path: <gcc-bugs-return-662228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52579 invoked by alias); 3 Dec 2019 21:59:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52534 invoked by uid 48); 3 Dec 2019 21:59:38 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92783] [10 regression] SEGV in field_byte_offset
Date: Tue, 03 Dec 2019 21:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92783-4-99iDMkon6v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00298.txt.bz2
Content-length: 231
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92783
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> No patch in that range is immediately obvious, so I'll have to run a reghunt.
Probably r278930 though.
>From gcc-bugs-return-662230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 22:05:48 2019
Return-Path: <gcc-bugs-return-662230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70775 invoked by alias); 3 Dec 2019 22:05:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70737 invoked by uid 48); 3 Dec 2019 22:05:43 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92783] [10 regression] SEGV in field_byte_offset
Date: Tue, 03 Dec 2019 22:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-92783-4-qeAAeDaz9l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00300.txt.bz2
Content-length: 521
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92783
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC|ebotcazou at gcc dot gnu.org |
Assignee|unassigned at gcc dot gnu.org |ebotcazou at gcc dot gnu.org
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Fixing.
>From gcc-bugs-return-662229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 22:05:07 2019
Return-Path: <gcc-bugs-return-662229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69683 invoked by alias); 3 Dec 2019 22:05:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69612 invoked by uid 48); 3 Dec 2019 22:05:02 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92783] [10 regression] SEGV in field_byte_offset
Date: Tue, 03 Dec 2019 22:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-92783-4-KezHGbTATS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00299.txt.bz2
Content-length: 509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92783
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
Ever confirmed|0 |1
--- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
I think I know what's going on...
>From gcc-bugs-return-662231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 22:48:50 2019
Return-Path: <gcc-bugs-return-662231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75715 invoked by alias); 3 Dec 2019 22:48:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75623 invoked by uid 48); 3 Dec 2019 22:48:44 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92784] New: [10 regression] ICE when compiling g++.dg/torture/pr59226.C after r278944
Date: Tue, 03 Dec 2019 22:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92784-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00301.txt.bz2
Content-length: 4306
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92784
Bug ID: 92784
Summary: [10 regression] ICE when compiling
g++.dg/torture/pr59226.C after r278944
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
FAIL: g++.dg/torture/pr59226.C -O2 (internal compiler error)
FAIL: g++.dg/torture/pr59226.C -O2 (test for excess errors)
FAIL: g++.dg/torture/pr59226.C -O3 -g (internal compiler error)
FAIL: g++.dg/torture/pr59226.C -O3 -g (test for excess errors)
FAIL: g++.dg/torture/pr59226.C -Os (internal compiler error)
FAIL: g++.dg/torture/pr59226.C -Os (test for excess errors)
FAIL: g++.dg/torture/pr59226.C -O2 -flto -fno-use-linker-plugin
-flto-partition=none (internal compiler error)
FAIL: g++.dg/torture/pr59226.C -O2 -flto -fno-use-linker-plugin
-flto-partition=none (test for excess errors)
Executing on host:
/home/seurer/gcc/build/gcc-test2/gcc/testsuite/g++/../../xg++
-B/home/seurer/gcc/build/gcc-test2/gcc/testsuite/g++/../../
/home/seurer/gcc/gcc-test2/gcc/testsuite/g++.dg/torture/pr59226.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test2/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test2/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test2/libstdc++-v3/testsuite/util -fmessage-length=0
-O2 -S -o pr59226.s (timeout = 300)
spawn -ignore SIGHUP
/home/seurer/gcc/build/gcc-test2/gcc/testsuite/g++/../../xg++
-B/home/seurer/gcc/build/gcc-test2/gcc/testsuite/g++/../../
/home/seurer/gcc/gcc-test2/gcc/testsuite/g++.dg/torture/pr59226.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test2/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test2/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test2/libstdc++-v3/testsuite/util -fmessage-length=0 -O2
-S -o pr59226.s
/home/seurer/gcc/gcc-test2/gcc/testsuite/g++.dg/torture/pr59226.C:27:1: error:
calls_comdat_local is set outside of a comdat group
_ZTv0_n24_N1D3fooEv/4 (virtual void D::_ZTv0_n24_N1D3fooEv()) @0x3fffb5f00708
Type: function
Body removed by symtab_remove_unreachable_nodes
Visibility: externally_visible public weak comdat comdat_group:_ZN1D3fooEv
one_only section:.text._ZN1D3fooEv (implicit_section) virtual artificial
References:
Referring:
Availability: not_available
Function flags: calls_comdat_local indirect_call_target
Former thunk fixed offset 0 virtual value -24 indirect_offset 0 has virtual
offset 1
Called by:
Calls:
during IPA pass: inline
/home/seurer/gcc/gcc-test2/gcc/testsuite/g++.dg/torture/pr59226.C:27:1:
internal compiler error: verify_cgraph_node failed
0x1077d77b cgraph_node::verify_node()
/home/seurer/gcc/gcc-test2/gcc/cgraph.c:3444
0x1076a173 symtab_node::verify()
/home/seurer/gcc/gcc-test2/gcc/symtab.c:1279
0x1076bc07 symtab_node::verify_symtab_nodes()
/home/seurer/gcc/gcc-test2/gcc/symtab.c:1299
0x10b14fd3 symtab_node::checking_verify_symtab_nodes()
/home/seurer/gcc/gcc-test2/gcc/cgraph.h:650
0x10b14fd3 symbol_table::remove_unreachable_nodes(_IO_FILE*)
/home/seurer/gcc/gcc-test2/gcc/ipa.c:672
0x11940aab ipa_inline
/home/seurer/gcc/gcc-test2/gcc/ipa-inline.c:2695
0x11940aab execute
/home/seurer/gcc/gcc-test2/gcc/ipa-inline.c:3088
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
compiler exited with status 1
>From gcc-bugs-return-662232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 23:01:52 2019
Return-Path: <gcc-bugs-return-662232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88532 invoked by alias); 3 Dec 2019 23:01:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88482 invoked by uid 48); 3 Dec 2019 23:01:48 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92761] hash_table::expand invokes assignment on invalid objects
Date: Tue, 03 Dec 2019 23:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-92761-4-6FbQEBaazc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00302.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #10 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00180.html
>From gcc-bugs-return-662233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 23:11:23 2019
Return-Path: <gcc-bugs-return-662233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99768 invoked by alias); 3 Dec 2019 23:11:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99732 invoked by uid 55); 3 Dec 2019 23:11:18 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92783] [10 regression] SEGV in field_byte_offset
Date: Tue, 03 Dec 2019 23:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92783-4-8TK3gnVRdq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00303.txt.bz2
Content-length: 492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92783
--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Tue Dec 3 23:10:46 2019
New Revision: 278948
URL: https://gcc.gnu.org/viewcvs?rev=278948&root=gcc&view=rev
Log:
PR bootstrap/92783
* gcc-interface/utils.c (rest_of_record_type_compilation): Move down
the guard for the position of fields in the descriptive type.
Modified:
trunk/gcc/ada/gcc-interface/utils.c
>From gcc-bugs-return-662234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 23:13:18 2019
Return-Path: <gcc-bugs-return-662234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101298 invoked by alias); 3 Dec 2019 23:13:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101236 invoked by uid 48); 3 Dec 2019 23:13:14 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92783] [10 regression] SEGV in field_byte_offset
Date: Tue, 03 Dec 2019 23:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92783-4-qzUc4eYBhv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00304.txt.bz2
Content-length: 452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92783
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
This should work again now.
>From gcc-bugs-return-662235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 23:38:39 2019
Return-Path: <gcc-bugs-return-662235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14010 invoked by alias); 3 Dec 2019 23:38:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13956 invoked by uid 48); 3 Dec 2019 23:38:33 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92784] [10 regression] ICE when compiling g++.dg/torture/pr59226.C after r278944
Date: Tue, 03 Dec 2019 23:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92784-4-ofDg85Xbdl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92784-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92784-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00305.txt.bz2
Content-length: 587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92784
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-03
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
I see this natively on x86_64-linux as well.
>From gcc-bugs-return-662236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 23:58:27 2019
Return-Path: <gcc-bugs-return-662236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72668 invoked by alias); 3 Dec 2019 23:58:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72579 invoked by uid 55); 3 Dec 2019 23:58:21 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91073] [9/10 Regression] if constexpr no longer works directly with Concepts
Date: Tue, 03 Dec 2019 23:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91073-4-QKoVq1Jnew@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91073-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91073-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00306.txt.bz2
Content-length: 1733
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91073
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Tue Dec 3 23:57:46 2019
New Revision: 278951
URL: https://gcc.gnu.org/viewcvs?rev=278951&root=gcc&view=rev
Log:
libstdc++: Implement spaceship for std::pair (P1614R2)
This defines operator<=> as a non-member function template and does not
alter operator==. This contradicts the changes made by P1614R2, which
specify both as hidden friends, but that specification of operator<=> is
broken and the subject of a soon-to-be-published LWG issue.
* include/bits/stl_pair.h [__cpp_lib_three_way_comparison]
(operator<=>): Define for C++20.
* libsupc++/compare (__cmp2way_res_t): Rename to __cmp3way_res_t,
move into __detail namespace. Do not turn argument types into lvalues.
(__cmp3way_helper): Rename to __cmp3way_res_impl, move into __detail
namespace. Constrain with concepts instead of using void_t.
(compare_three_way_result): Adjust name of base class.
(compare_three_way_result_t): Use __cmp3way_res_impl directly.
(__detail::__3way_cmp_with): Add workaround for PR 91073.
(compare_three_way): Use workaround.
(__detail::__synth3way, __detail::__synth3way_t): Define new helpers
implementing synth-three-way and synth-three-way-result semantics.
* testsuite/20_util/pair/comparison_operators/constexpr_c++20.cc: New
test.
Added:
trunk/libstdc++-v3/testsuite/20_util/pair/comparison_operators/constexpr_c++20.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/stl_pair.h
trunk/libstdc++-v3/libsupc++/compare
>From gcc-bugs-return-662237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 03:01:20 2019
Return-Path: <gcc-bugs-return-662237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7300 invoked by alias); 4 Dec 2019 03:00:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3562 invoked by uid 48); 4 Dec 2019 03:00:46 -0000
From: "marcpawl at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92735] unused member variable causes code to compile for member to function for undefined function
Date: Wed, 04 Dec 2019 03:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marcpawl at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92735-4-sxA3DLBihz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92735-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92735-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00307.txt.bz2
Content-length: 1258
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92735
--- Comment #4 from Marc Pawlowsky <marcpawl at gmail dot com> ---
(In reply to Jonathan Wakely from comment #2)
> For the case reported here, Clang and EDG do reject it, but I'm not yet
> convinced GCC is wrong to accept it.
>
> The implicit instantiation of is_Foo<Bad> causes:
>
> "the implicit instantiation of the declarations, but not of the definitions,
> of the non-deleted class member functions, member classes, scoped member
> enumerations, static data members, member templates, and friends;"
>
> and:
>
> "in particular, the initialization (and any associated side effects) of a
> static data member does not occur unless the static data member is itself
> used in a way that requires the definition of the static data member to
> exist."
>
> Nothing requires the instantiation of is_Foo<Bad>::hello.
FYI, Forcing the use of hello does cause a compile time error.
template <typename T>
struct is_Foo {
using hello_fn_t = void (T::*)(int);
constexpr static void (T::*hello)(int) = &T::hello;
static constexpr bool value=(!!hello);
};
source>:16:46: error: 'hello' is not a member of 'Bad'
16 | constexpr static void (T::*hello)(int) = &T::hello;
>From gcc-bugs-return-662238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 03:28:37 2019
Return-Path: <gcc-bugs-return-662238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25103 invoked by alias); 4 Dec 2019 03:28:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25056 invoked by uid 48); 4 Dec 2019 03:28:33 -0000
From: "urbanjost at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92785] New: expressions passed as real arguments to a dummy polymorphic argument fail with indexing error
Date: Wed, 04 Dec 2019 03:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: urbanjost at comcast dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92785-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00308.txt.bz2
Content-length: 4136
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92785
Bug ID: 92785
Summary: expressions passed as real arguments to a dummy
polymorphic argument fail with indexing error
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: urbanjost at comcast dot net
Target Milestone: ---
I thought this was a duplicate of Bug 84074 at first. I could not
find a way to tell when a fix is applied to a release and GNU Fortran
(Ubuntu 9.2.1-17ubuntu1~18.04.1) 9.2.1 20191102 seems to have come out
after the fix for 84074 was applied?
Is there a field somewhere I am missing that would tell at what release
a fix becomes available?
Anyway, I took the code from Bug 84074 and compiled it and it ran OK
so I now assume this is a similar but distinct bug:
TEST PROGRAM
program tst
use iso_fortran_env, only : compiler_version, compiler_options
implicit none
integer :: i
integer :: ibad=0
integer :: iarr(10)=[(i*10,i=1,size(iarr))]
character(len=:),allocatable :: line
character(len=*),parameter :: expected= '10 20 30 40 50 60 70 80 90 100'
print '(4a)', &
'This file was compiled by ', compiler_version(), &
' using the options ', compiler_options()
call write_row('iarr ',iarr) ! pass in the array, OK
call write_row('iarr+0 ',iarr+0) ! pass in an expression,
SHIFTED(?)
call write_row('-iarr ',-iarr) ! pass in an expression,
SHIFTED(?)
call write_row('iarr(::1) ',iarr(::1))
call write_row('[iarr(::1)] ',[iarr(::1)])
call write_row('[(i*10,i=1,size(iarr))]',[(i*10,i=1,size(iarr))])
call write_row('10*[(i,i=1,size(iarr))]',10*[(i,i=1,size(iarr))])
if(ibad.gt.0)stop 'FAILED'
contains
subroutine write_scalar(g1)
class(*) :: g1
character(len=20) :: word
select type(g1)
type is (integer)
write(word,'(i0)') g1
line=line//trim(word)//' '
end select
end subroutine write_scalar
subroutine write_row(string,array )
character(len=*) :: string
class(*) :: array(:)
integer :: i
line=''
do i = 1,size(array)
call write_scalar( array(i) )
enddo
if(expected.eq.line)then
write(*,*)string,':GOOD'
else
write(*,*)string,':BAD. EXPECTED [',expected,'] got
[',trim(line),']'
ibad=ibad+1
endif
end subroutine write_row
end program tst
OUTPUTS
GIVES BAD ANSWERS WITHOUT BOUNDS CHECK
This file was compiled by GCC version 9.2.1 20191102 using the options
-mtune=generic -march=x86-64 -Wall -Wextra -fno-strict-aliasing -fwrapv
iarr :GOOD
iarr+0 :BAD. EXPECTED [10 20 30 40 50 60 70 80 90 100] got
[20 30 40 50 60 70 80 90 100 335544320]
-iarr :BAD. EXPECTED [10 20 30 40 50 60 70 80 90 100] got
[-20 -30 -40 -50 -60 -70 -80 -90 -100 335544320]
iarr(::1) :GOOD
[iarr(::1)] :BAD. EXPECTED [10 20 30 40 50 60 70 80 90 100] got
[20 30 40 50 60 70 80 90 100 8064]
[(i*10,i=1,size(iarr))]:GOOD
10*[(i,i=1,size(iarr))]:GOOD
This file was compiled by GCC version 9.2.1 20191102 using the options
-mtune=generic -march=x86-64 -g0 -Wall -Wextra -fbacktrace -fno-strict-aliasing
-fwrapv -fbounds-check
iarr :GOOD
STOP FAILED
FAILS WITH BOUNDS CHECK
At line 36 of file xx.f90
Fortran runtime error: Index '10' of dimension 1 of array 'array%_data'
above upper bound of 9
Error termination. Backtrace:
#0 0x7fab5f57f74a
#1 0x7fab5f580235
#2 0x7fab5f580712
#3 0x7fab5fe0190d
#4 0x7fab5fe00f58
#5 0x7fab5fe01f40
#6 0x7fab5f181b96
#7 0x7fab5fe00b29
#8 0xffffffffffffffff
>From gcc-bugs-return-662239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 05:11:23 2019
Return-Path: <gcc-bugs-return-662239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49027 invoked by alias); 4 Dec 2019 05:11:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48975 invoked by uid 55); 4 Dec 2019 05:11:18 -0000
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92760] [10 regression] several vector test cases fail on power 7 after r278800
Date: Wed, 04 Dec 2019 05:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92760-4-pcLuHyT700@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00309.txt.bz2
Content-length: 972
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92760
--- Comment #2 from Kewen Lin <linkw at gcc dot gnu.org> ---
Author: linkw
Date: Wed Dec 4 05:10:46 2019
New Revision: 278955
URL: https://gcc.gnu.org/viewcvs?rev=278955&root=gcc&view=rev
Log:
[rs6000] Fix PR92760 by checking VECTOR_MEM_NONE_P instead
PR92760 exposed one issue that VECTOR_UNIT_NONE_P (V2DImode) is true on Power7
then we won't return it as preferred_simd_mode but ISA 2.06 (Power7) does
introduce partial support on vector doubleword (very limitted) and more basic
support origins from ISA 2.07 (Power8) though. To make vectorizer still
leverage those few but available V2DImode related instructions, we need to
claim it's available on VSX (Power7 and up).
gcc/ChangeLog
PR target/92760
* gcc/config/rs6000/rs6000.c (rs6000_preferred_simd_mode): Use
VECTOR_MEM_NONE_P instead of VECTOR_UNIT_NONE_P.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/rs6000/rs6000.c
>From gcc-bugs-return-662240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 05:12:03 2019
Return-Path: <gcc-bugs-return-662240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49889 invoked by alias); 4 Dec 2019 05:12:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49823 invoked by uid 48); 4 Dec 2019 05:11:59 -0000
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92760] [10 regression] several vector test cases fail on power 7 after r278800
Date: Wed, 04 Dec 2019 05:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92760-4-qXsKfW1kro@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00310.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92760
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Kewen Lin <linkw at gcc dot gnu.org> ---
Fixed on trunk.
>From gcc-bugs-return-662241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 06:14:22 2019
Return-Path: <gcc-bugs-return-662241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49265 invoked by alias); 4 Dec 2019 06:14:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49242 invoked by uid 48); 4 Dec 2019 06:14:12 -0000
From: "xavierb at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92786] New: [c++11] static constexpr member link error
Date: Wed, 04 Dec 2019 06:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: xavierb at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92786-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00311.txt.bz2
Content-length: 926
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92786
Bug ID: 92786
Summary: [c++11] static constexpr member link error
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: xavierb at gmail dot com
Target Milestone: ---
hi,
this code doesn't link:
---
struct STest {
static int GetVal(int x) {return vals[x];}
static constexpr int vals[] = { 1,2,3,4,4,4,4 };
};
int main()
{
return STest::GetVal(1);
}
---
/usr/bin/ld: /tmp/ccqFvLiy.o: in function `STest::GetVal(int)':
bug.cpp:(.text._ZN5STest6GetValEi[_ZN5STest6GetValEi]+0x17): undefined
reference to `STest::vals'
collect2: error: ld returned 1 exit status
(seems to work fine with
clang >= 9 (but not with version <=8),
msvc and icc )
>From gcc-bugs-return-662242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 06:17:06 2019
Return-Path: <gcc-bugs-return-662242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52155 invoked by alias); 4 Dec 2019 06:17:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52093 invoked by uid 48); 4 Dec 2019 06:17:01 -0000
From: "boostcpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92652] function call to lambda expression that return true does not satisfy the constraint in requires-clause if using return type deduction
Date: Wed, 04 Dec 2019 06:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: boostcpp at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92652-4-rtGlFn0ypO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92652-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92652-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00312.txt.bz2
Content-length: 146
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92652
--- Comment #2 from Ryou Ezoe <boostcpp at gmail dot com> ---
Yes. this is C++20 concepts .
>From gcc-bugs-return-662243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 06:21:21 2019
Return-Path: <gcc-bugs-return-662243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64718 invoked by alias); 4 Dec 2019 06:21:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64680 invoked by uid 48); 4 Dec 2019 06:21:16 -0000
From: "xavierb at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92786] [c++11] static constexpr member link error
Date: Wed, 04 Dec 2019 06:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: xavierb at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92786-4-aVVxPttvPE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92786-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92786-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00313.txt.bz2
Content-length: 238
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92786
--- Comment #1 from Xavier B <xavierb at gmail dot com> ---
additional info:
- getting the array out of the struct works,
- using 'namespace' instead of 'struct' also works fine.
>From gcc-bugs-return-662244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 06:22:14 2019
Return-Path: <gcc-bugs-return-662244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65567 invoked by alias); 4 Dec 2019 06:22:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65542 invoked by uid 48); 4 Dec 2019 06:22:08 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92786] [c++11] static constexpr member link error
Date: Wed, 04 Dec 2019 06:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92786-4-noEiEB2nNi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92786-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92786-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00314.txt.bz2
Content-length: 573
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92786
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
You still need a definition and not just a declaration even with constexpr.
Though I think a newer C++ standard changed that; try -std=c++17 :)
>From gcc-bugs-return-662245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 06:25:10 2019
Return-Path: <gcc-bugs-return-662245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69873 invoked by alias); 4 Dec 2019 06:25:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69818 invoked by uid 48); 4 Dec 2019 06:25:04 -0000
From: "boostcpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92787] New: P0634R3 is not implemented correctly if parameter-declaration appears in a default argument
Date: Wed, 04 Dec 2019 06:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: boostcpp at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92787-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00315.txt.bz2
Content-length: 1140
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92787
Bug ID: 92787
Summary: P0634R3 is not implemented correctly if
parameter-declaration appears in a default argument
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: boostcpp at gmail dot com
Target Milestone: ---
The lambda expression's parameter-declaration don't assume a qualified-id to
name a type if that parameter-declaration appears in a default argument.
> parameter-declaration in a lambda-declarator, unless that parameter-declaration appears in a default argument, or
parameter-declaration of a (non-type) template-parameter.
template < typename T >
// lambda expression's parameter-declaration appears in a default argument
void f( typename T::type x = []( T::type x ){return x ;}( typename T::type{})
)
{
}
https://wandbox.org/permlink/7d2d6aqjZWOhL5Pq
But current GCC 10 head assume it to name a type.
Or am I reading the wording wrong?
>From gcc-bugs-return-662246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 07:02:11 2019
Return-Path: <gcc-bugs-return-662246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69094 invoked by alias); 4 Dec 2019 07:02:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69038 invoked by uid 48); 4 Dec 2019 07:02:06 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92784] [10 regression] ICE when compiling g++.dg/torture/pr59226.C after r278944
Date: Wed, 04 Dec 2019 07:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-92784-4-RKbi50nW5U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92784-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92784-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00316.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92784
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-662247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 07:04:12 2019
Return-Path: <gcc-bugs-return-662247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70649 invoked by alias); 4 Dec 2019 07:04:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70583 invoked by uid 48); 4 Dec 2019 07:04:06 -0000
From: "luoxhu at cn dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/92599] ICE in speculative_call_info, at cgraph.c:1142
Date: Wed, 04 Dec 2019 07:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: luoxhu at cn dot ibm.com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92599-4-Nr483UUvjr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00317.txt.bz2
Content-length: 2593
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92599
--- Comment #3 from Xiong Hu XS Luo <luoxhu at cn dot ibm.com> ---
(In reply to Martin Liška from comment #2)
> So we ICE at the end of cgraph_edge::speculative_call_info:
> (gdb) p ref
> $4 = <ipa_ref* 0x0>
>
> (gdb) p e
> $5 = <cgraph_edge* 0x7ffff769b5b0 (<cgraph_node * 0x7ffff74ac160
> "ConvertASEToModelSurfaces.constprop"/113> -> <cgraph_node * 0x7ffff74ac420
> "NumSurfaces"/115>)>
> (gdb) p e2
> $6 = <cgraph_edge* 0x7ffff769b750 (<cgraph_node * 0x7ffff74ac160
> "ConvertASEToModelSurfaces.constprop"/113> -> <cgraph_node * 0x0>)>
>
> As seen the edge is within idRenderModelStatic class.
> I bet the problem is the ODR warning message, the class is polymorphic in
> one TU, and normal class in another one.
Seems side effect in indirect->set_call_stmt.
The "ref" is changed in recursive call line "indirect->set_call_stmt (new_stmt,
false)", it will call resolve_speculation to redirect one of it's polymorphic
call
ConvertASEToModelSurfaces/2 => FindMaterial/45, ref->remove_reference will the
related reference, then ref will be pointed to another reference, then the
followed "ref->stmt = new_stmt" will update wrong stmt to the original
reference.
p *ref
$378 = {referring = 0x3fffb55f10e0, referred = 0x3fffb55f09d8, stmt =
0x3fffb7f71440, lto_stmt_uid = 10, referred_index = 1, use = IPA_REF_ADDR,
speculative = 1
After returning from indirect->set_call_stmt (new_stmt, false):
p *ref
$380 = {referring = 0x3fffb55f10e0, referred = 0x3fffb55f0ca8, stmt =
0x3fffb7f713b0, lto_stmt_uid = 6, referred_index = 1, use = IPA_REF_ADDR,
speculative = 1}
(gdb) pedge direct
$381 = 0x3fffb5560498 "ConvertASEToModelSurfaces.constprop/113"
$382 = 0x3fffb53d78a0 "FindMaterial/116"
(gdb) ps new_stmt
FindMaterial (_6);
ps ref->stmt
# .MEM = VDEF <.MEM>
OBJ_TYPE_REF(_5;(struct idRenderModelStatic)this_3(D)->1) (this_3(D));
How about patch candidate as below? Or check the ref->speculative is true after
return from indirect->set_call_stmt?
diff --git a/gcc/cgraph.c b/gcc/cgraph.c
index b75430f3f3a..65b6f93c3fe 100644
--- a/gcc/cgraph.c
+++ b/gcc/cgraph.c
@@ -793,7 +793,8 @@ cgraph_edge::set_call_stmt (gcall *new_stmt, bool
update_speculative)
speculative_call_info (direct, indirect, ref);
direct->set_call_stmt (new_stmt, false);
indirect->set_call_stmt (new_stmt, false);
- ref->stmt = new_stmt;
+ if (ref->lto_stmt_uid == direct->lto_stmt_uid)
+ ref->stmt = new_stmt;
return;
}
>From gcc-bugs-return-662248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 07:05:50 2019
Return-Path: <gcc-bugs-return-662248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73060 invoked by alias); 4 Dec 2019 07:05:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73034 invoked by uid 48); 4 Dec 2019 07:05:45 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92773] GCC compilation with big array / header is infinite
Date: Wed, 04 Dec 2019 07:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92773-4-cBXs9Kpb14@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00318.txt.bz2
Content-length: 770
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92773
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |compile-time-hog,
| |memory-hog
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-12-04
CC| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Can you please attach preprocessed source of the compilation unit that shows
the problem?
>From gcc-bugs-return-662249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 07:08:25 2019
Return-Path: <gcc-bugs-return-662249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75892 invoked by alias); 4 Dec 2019 07:08:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75780 invoked by uid 48); 4 Dec 2019 07:08:20 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92772] wrong code vectorizing masked max
Date: Wed, 04 Dec 2019 07:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: critical
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget cc blocked
Message-ID: <bug-92772-4-O26BAV9o6D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00319.txt.bz2
Content-length: 880
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92772
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Target| |amdgcn
CC| |rguenth at gcc dot gnu.org,
| |rsandifo at gcc dot gnu.org
Blocks| |53947
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Looks like cond-reduction cannot handle fully masked loops unless we'd somehow
mask the condition operation itself?
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
[Bug 53947] [meta-bug] vectorizer missed-optimizations
>From gcc-bugs-return-662250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 07:16:56 2019
Return-Path: <gcc-bugs-return-662250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86836 invoked by alias); 4 Dec 2019 07:16:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86790 invoked by uid 48); 4 Dec 2019 07:16:50 -0000
From: "luoxhu at cn dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/92599] ICE in speculative_call_info, at cgraph.c:1142
Date: Wed, 04 Dec 2019 07:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: luoxhu at cn dot ibm.com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92599-4-EGNLSiubMP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00320.txt.bz2
Content-length: 3192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92599
--- Comment #4 from Xiong Hu XS Luo <luoxhu at cn dot ibm.com> ---
(In reply to Xiong Hu XS Luo from comment #3)
> (In reply to Martin Liška from comment #2)
> > So we ICE at the end of cgraph_edge::speculative_call_info:
> > (gdb) p ref
> > $4 = <ipa_ref* 0x0>
> >
> > (gdb) p e
> > $5 = <cgraph_edge* 0x7ffff769b5b0 (<cgraph_node * 0x7ffff74ac160
> > "ConvertASEToModelSurfaces.constprop"/113> -> <cgraph_node * 0x7ffff74ac420
> > "NumSurfaces"/115>)>
> > (gdb) p e2
> > $6 = <cgraph_edge* 0x7ffff769b750 (<cgraph_node * 0x7ffff74ac160
> > "ConvertASEToModelSurfaces.constprop"/113> -> <cgraph_node * 0x0>)>
> >
> > As seen the edge is within idRenderModelStatic class.
> > I bet the problem is the ODR warning message, the class is polymorphic in
> > one TU, and normal class in another one.
>
> Seems side effect in indirect->set_call_stmt.
> The "ref" is changed in recursive call line "indirect->set_call_stmt
> (new_stmt, false)", it will call resolve_speculation to redirect one of it's
> polymorphic call
> ConvertASEToModelSurfaces/2 => FindMaterial/45, ref->remove_reference will
> the related reference, then ref will be pointed to another reference, then
> the followed "ref->stmt = new_stmt" will update wrong stmt to the original
> reference.
>
> p *ref
> $378 = {referring = 0x3fffb55f10e0, referred = 0x3fffb55f09d8, stmt =
> 0x3fffb7f71440, lto_stmt_uid = 10, referred_index = 1, use = IPA_REF_ADDR,
> speculative = 1
>
> After returning from indirect->set_call_stmt (new_stmt, false):
>
> p *ref
> $380 = {referring = 0x3fffb55f10e0, referred = 0x3fffb55f0ca8, stmt =
> 0x3fffb7f713b0, lto_stmt_uid = 6, referred_index = 1, use = IPA_REF_ADDR,
> speculative = 1}
>
> (gdb) pedge direct
> $381 = 0x3fffb5560498 "ConvertASEToModelSurfaces.constprop/113"
> $382 = 0x3fffb53d78a0 "FindMaterial/116"
> (gdb) ps new_stmt
> FindMaterial (_6);
> ps ref->stmt
> # .MEM = VDEF <.MEM>
> OBJ_TYPE_REF(_5;(struct idRenderModelStatic)this_3(D)->1) (this_3(D));
>
>
> How about patch candidate as below? Or check the ref->speculative is true
> after return from indirect->set_call_stmt?
Not "ref->speculative", should be indirect->speculative as indirect edge is
removed speculative now, or lto_stmt_uid is more reliable?
(gdb) p *indirect
$385 = {count = {static n_bits = 61, static max_count = 2305843009213693950,
static uninitialized_count = 2305843009213693951, m_val = 406913472214181285,
m_quality = AFDO}, caller = 0xa5a5a5a5a5a5a5a5, callee = 0xa5a5a5a5a5a5a5a5,
prev_caller = 0xa5a5a5a5a5a5a5a5, next_caller = 0xa5a5a5a5a5a5a5a5, prev_callee
= 0xa5a5a5a5
a5a5a5a5, next_callee = 0xa5a5a5a5a5a5a5a5, call_stmt = 0xa5a5a5a5a5a5a5a5,
indirect_info = 0xa5a5a5a5a5a5a5a5, aux = 0xa5a5a5a5a5a5a5a5, inline_failed =
2779096485, lto_stmt_uid = 2779096485, indirect_inlining_edge= 1,
indirect_unknown_callee = 0, call_stmt_cannot_inline_p = 1, can_throw_external
= 0, speculative = 0, in_polymorphic_cdtor = 1, m_uid = -1515870811,
m_summary_id = -1515870811}
>From gcc-bugs-return-662251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 07:51:31 2019
Return-Path: <gcc-bugs-return-662251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82628 invoked by alias); 4 Dec 2019 07:51:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82565 invoked by uid 48); 4 Dec 2019 07:51:26 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92788] New: [10 Regression] ICE in redirect_eh_edge_1, at tree-eh.c:2313
Date: Wed, 04 Dec 2019 07:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcctarget attachments.created
Message-ID: <bug-92788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00321.txt.bz2
Content-length: 3580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92788
Bug ID: 92788
Summary: [10 Regression] ICE in redirect_eh_edge_1, at
tree-eh.c:2313
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-invalid-code, ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
Target: x86_64-pc-linux-gnu
Created attachment 47413
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47413&action=edit
Testcase
g++-10.0.0-alpha20191201 snapshot (r278886) ICEs when compiling the attached
testcase, reduced from
libstdc++-v3/testsuite/28_regex/algorithms/regex_match/ecma/char/53622.cc, w/
-march=k8 -O3 -fnon-call-exceptions -ftracer:
% x86_64-pc-linux-gnu-g++-10.0.0-alpha20191201 -march=k8 -O3
-fnon-call-exceptions -ftracer -w -c s0uf5lnv.cc
during GIMPLE pass: dom
s0uf5lnv.cc: In copy constructor 'std::vector<_Tp,
_Alloc>::vector(std::vector<_Tp, _Alloc>&) [with _Tp =
std::Trans_NS___cxx11_regex_traits::_RegexMask; _Alloc =
new_allocator<std::Trans_NS___cxx11_regex_traits::_RegexMask>]':
s0uf5lnv.cc:154:5: internal compiler error: in redirect_eh_edge_1, at
tree-eh.c:2313
154 | vector(vector &__x) : _Base(0, _M_get_Tp_allocator()) {
| ^~~~~~
0x73dcdc redirect_eh_edge_1
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree-eh.c:2313
0xf979ea redirect_eh_edge(edge_def*, basic_block_def*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree-eh.c:2378
0xaee9a0 redirect_edge_and_branch(edge_def*, basic_block_def*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/cfghooks.c:373
0x1125d54 ssa_fix_duplicate_block_edges(redirection_data*, ssa_local_info_t*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree-ssa-threadupdate.c:1017
0x11282c9 ssa_fixup_template_block(redirection_data**, ssa_local_info_t*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree-ssa-threadupdate.c:1246
0x11282c9 void hash_table<redirection_data, false,
xcallocator>::traverse_noresize<ssa_local_info_t*,
&(ssa_fixup_template_block(redirection_data**,
ssa_local_info_t*))>(ssa_local_info_t*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/hash-table.h:1084
0x11282c9 void hash_table<redirection_data, false,
xcallocator>::traverse<ssa_local_info_t*,
&(ssa_fixup_template_block(redirection_data**,
ssa_local_info_t*))>(ssa_local_info_t*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/hash-table.h:1105
0x11282c9 thread_block_1
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree-ssa-threadupdate.c:1503
0x112990e thread_block
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree-ssa-threadupdate.c:1540
0x112990e thread_through_all_blocks(bool)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree-ssa-threadupdate.c:2652
0x1049eb7 execute
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/tree-ssa-dom.c:775
>From gcc-bugs-return-662252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 08:06:46 2019
Return-Path: <gcc-bugs-return-662252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63612 invoked by alias); 4 Dec 2019 08:06:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63536 invoked by uid 48); 4 Dec 2019 08:06:41 -0000
From: "lutztonineubert at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91369] Implement P0784R7: constexpr new
Date: Wed, 04 Dec 2019 08:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lutztonineubert at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91369-4-YPThKrock1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00322.txt.bz2
Content-length: 144
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91369
--- Comment #24 from Toni Neubert <lutztonineubert at gmail dot com> ---
Great thank you.
>From gcc-bugs-return-662253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 08:14:53 2019
Return-Path: <gcc-bugs-return-662253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111876 invoked by alias); 4 Dec 2019 08:14:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 111824 invoked by uid 48); 4 Dec 2019 08:14:48 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92772] wrong code vectorizing masked max
Date: Wed, 04 Dec 2019 08:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: critical
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92772-4-oEkfeuIPg3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00323.txt.bz2
Content-length: 413
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92772
--- Comment #2 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> Looks like cond-reduction cannot handle fully masked loops unless we'd
> somehow mask the condition operation itself?
Yeah, looks like it. We'd never noticed this for SVE because
we always use EXTRACT_LAST reductions instead.
>From gcc-bugs-return-662254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 08:29:58 2019
Return-Path: <gcc-bugs-return-662254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126182 invoked by alias); 4 Dec 2019 08:29:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126134 invoked by uid 48); 4 Dec 2019 08:29:53 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92754] ICE in gfc_finish_var_decl, at fortran/trans-decl.c:693
Date: Wed, 04 Dec 2019 08:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92754-4-UeEF37YmQU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92754-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92754-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00324.txt.bz2
Content-length: 184
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92754
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00153.html
>From gcc-bugs-return-662255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 08:47:50 2019
Return-Path: <gcc-bugs-return-662255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36772 invoked by alias); 4 Dec 2019 08:47:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36699 invoked by uid 55); 4 Dec 2019 08:47:45 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92756] [9/10 Regression] ICE in lower_omp, at omp-low.c:12988
Date: Wed, 04 Dec 2019 08:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92756-4-UvcoKk4Zfi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00325.txt.bz2
Content-length: 876
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92756
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Dec 4 08:47:13 2019
New Revision: 278956
URL: https://gcc.gnu.org/viewcvs?rev=278956&root=gcc&view=rev
Log:
PR fortran/92756
* trans-openmp.c (gfc_trans_omp_teams): Wrap OMP_TEAMS body into a
BIND_EXPR with a forced BLOCK.
* gfortran.dg/gomp/teams1.f90: New test.
* testsuite/libgomp.fortran/teams1.f90: New test.
* testsuite/libgomp.fortran/teams2.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/gomp/teams1.f90
trunk/libgomp/testsuite/libgomp.fortran/teams1.f90
trunk/libgomp/testsuite/libgomp.fortran/teams2.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-openmp.c
trunk/gcc/testsuite/ChangeLog
trunk/libgomp/ChangeLog
>From gcc-bugs-return-662256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 08:51:14 2019
Return-Path: <gcc-bugs-return-662256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40650 invoked by alias); 4 Dec 2019 08:51:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39895 invoked by uid 55); 4 Dec 2019 08:51:06 -0000
From: "luoxhu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92398] [10 regression] error in update of gcc.target/powerpc/pr72804.c in r277872
Date: Wed, 04 Dec 2019 08:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: luoxhu at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92398-4-HTOZjEH3aR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00326.txt.bz2
Content-length: 662
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92398
--- Comment #10 from luoxhu at gcc dot gnu.org ---
Author: luoxhu
Revision: 278890
Modified property: svn:log
Modified: svn:log at Wed Dec 4 08:50:33 2019
------------------------------------------------------------------------------
--- svn:log (original)
+++ svn:log Wed Dec 4 08:50:33 2019
@@ -10,7 +10,7 @@
2019-12-02 Luo Xiong Hu <luoxhu@linux.ibm.com>
- testsuite/pr92398
+ PR testsuite/92398
* gcc.target/powerpc/pr72804.c: Split the store function to...
* gcc.target/powerpc/pr92398.h: ... this one. New.
* gcc.target/powerpc/pr92398.p9+.c: New.
>From gcc-bugs-return-662257-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 08:51:31 2019
Return-Path: <gcc-bugs-return-662257-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42131 invoked by alias); 4 Dec 2019 08:51:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42092 invoked by uid 48); 4 Dec 2019 08:51:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92756] [9 Regression] ICE in lower_omp, at omp-low.c:12988
Date: Wed, 04 Dec 2019 08:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-92756-4-222RpxNlKP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00327.txt.bz2
Content-length: 529
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92756
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[9/10 Regression] ICE in |[9 Regression] ICE in
|lower_omp, at |lower_omp, at
|omp-low.c:12988 |omp-low.c:12988
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk so far.
>From gcc-bugs-return-662258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 09:20:06 2019
Return-Path: <gcc-bugs-return-662258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25526 invoked by alias); 4 Dec 2019 09:20:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25473 invoked by uid 48); 4 Dec 2019 09:20:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92788] [10 Regression] ICE in redirect_eh_edge_1, at tree-eh.c:2313
Date: Wed, 04 Dec 2019 09:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92788-4-uJfAtvFPOn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00328.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92788
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r272922, guess latent before. I'll have a look.
>From gcc-bugs-return-662259-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 09:20:18 2019
Return-Path: <gcc-bugs-return-662259-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26257 invoked by alias); 4 Dec 2019 09:20:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26207 invoked by uid 48); 4 Dec 2019 09:20:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92788] [10 Regression] ICE in redirect_eh_edge_1, at tree-eh.c:2313
Date: Wed, 04 Dec 2019 09:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-92788-4-ZzFsxEw9kz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00329.txt.bz2
Content-length: 291
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92788
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-662260-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 09:26:13 2019
Return-Path: <gcc-bugs-return-662260-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29938 invoked by alias); 4 Dec 2019 09:26:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29893 invoked by uid 48); 4 Dec 2019 09:26:09 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92784] [10 regression] ICE when compiling g++.dg/torture/pr59226.C after r278944
Date: Wed, 04 Dec 2019 09:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92784-4-rYLY4UiWJF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92784-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92784-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00330.txt.bz2
Content-length: 421
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92784
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yeah, on i686-linux too. Maybe everywhere.
>From gcc-bugs-return-662261-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 09:27:13 2019
Return-Path: <gcc-bugs-return-662261-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31109 invoked by alias); 4 Dec 2019 09:27:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31015 invoked by uid 48); 4 Dec 2019 09:27:09 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92789] New: Non-obvious ?: behaviour with structurally equivalent types
Date: Wed, 04 Dec 2019 09:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-92789-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00331.txt.bz2
Content-length: 1500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92789
Bug ID: 92789
Summary: Non-obvious ?: behaviour with structurally equivalent
types
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: rsandifo at gcc dot gnu.org
Target Milestone: ---
Target: aarch64*-*-*
As noted in https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00128.html
build_conditional_expr_1 uses same_type_p to check whether the "then"
and "else" types are the same. If they are, it uses the "then"
type for the result.
However, same_type_p uses structural equality when
TYPE_STRUCTURAL_EQUALITY_P is true. This means that we can treat
two distinct but equivalent types as "the same" and use the "then"
type for the result. For example:
#include <arm_neon.h>
typedef uint8_t gnu_uint8_t __attribute__ ((vector_size (16)));
void f(gnu_uint8_t x) {}
void g(uint8x16_t y) {}
correctly mangles f as _Z1fDv16_h and g as _Z1g12__Uint8x16_t. But:
void h1(decltype(*(int *)nullptr ? *(gnu_uint8_t *)nullptr : *(uint8x16_t
*)nullptr)) {}
void h2(decltype(*(int *)nullptr ? *(uint8x16_t *)nullptr : *(gnu_uint8_t
*)nullptr)) {}
mangles h1 as _Z2h1RDv16_h and h2 as _Z2h2R12__Uint8x16_t.
See https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00173.html for
Jason's comments on how this should work.
>From gcc-bugs-return-662262-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 09:29:11 2019
Return-Path: <gcc-bugs-return-662262-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33727 invoked by alias); 4 Dec 2019 09:29:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33620 invoked by uid 48); 4 Dec 2019 09:29:06 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92790] New: [OpenACC] declare device_resident - Fortran common blocks not handled / libgomp.oacc-fortran/declare-5.f90 fails
Date: Wed, 04 Dec 2019 09:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc dependson target_milestone
Message-ID: <bug-92790-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00332.txt.bz2
Content-length: 3880
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92790
Bug ID: 92790
Summary: [OpenACC] declare device_resident - Fortran common
blocks not handled /
libgomp.oacc-fortran/declare-5.f90 fails
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: openacc
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
CC: tschwinge at gcc dot gnu.org
Depends on: 63859, 90921, 92728
Target Milestone: ---
Related:
PR 90921 - this introduced the questionable module code, mentioned below;
it looks like a work-around for the issue of the main point in
this PR.
PR 63859 (a bit unclear what this PR is about)
(PR 92728 – ordering of common-block decl and using it in a decl+blank commons)
It turned out that for Fortran's common blocks, OpenACC's 'declare
device_resident' is not handled – causing libgomp.oacc-fortran/declare-5.f90 to
fail.
There is a RFC patch for this at the end of
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00149.html
However, the patch causes that the same(-)named common block is marked as
'declare target' in multiple procedures. That seems to be very sensible from
the FE side. However, the ME code generates multiple times the same mapping
code. Result:
libgomp: Trying to map into device [0x407218..0x40721c) object when
[0x407210..0x40721c) is already mapped
Ideally, the ME part would consolidate all of them into a single item (at least
per translation unit). And to support multiple translation units, the libgomp
part should be handles as 'pcreate' not as with 'create'.
[In terms of common blocks, those are static variables with the same name,
pointing to the same memory block.]
Additional issues (cf. email):
* Code for handling modules variables looks fragile (seems to assume that the
module symbol ends up in the main program) - that code looks like a work-around
for the issue above.
* Unclear what exactly get's mapped for
integer :: a,b,c
common /name/ a, b, c
declare device_resident(a)
will this map the whole /name/? (Current patch does so, cf. email;
other variants will also ICE)
I think it only makes sense if OpenACC requires that all is mapped, e.g.
by requiring the explicit /name/ instead of permitting single common-block
variables. Otherwise, it could also be handled by the FE as currently done,
i.e. if one of them is device-resident, all are.
* General question what's meant by device resident, i.e., whether the
same-named common block also exists on the host, i.e.
copy(/name/)
will map all of the host's common block to the device and back.
Of whether they only exist on the device, such that one passes individual
variables, which happen to have the same name, i.e.
copy(/name/)
passes a, b, c and one has to take care of them as single variables in the
parallel/kernels block.
* Question whether OpenACC permits:
block data
...
common /name/
end block data
* Blank commons spec issue, PR 92728
* Data mapping question - i.e. if /name/ is device resident; will automatic
mapping imply copy() and firstprivate for common-block variables accessed in
the parallels/kernels block?
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63859
[Bug 63859] Fortran OpenACC declare directive
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90921
[Bug 90921] Fortran OpenACC 'declare' directive's module handling causes
duplicate data clauses
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92728
[Bug 92728] [OpenMP][OpenACC] Common-block name clause matching issues: common
block needs to be defined before + blank common not supported
>From gcc-bugs-return-662263-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 09:39:26 2019
Return-Path: <gcc-bugs-return-662263-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57387 invoked by alias); 4 Dec 2019 09:39:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57325 invoked by uid 55); 4 Dec 2019 09:39:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92734] Missing match.pd simplification done by fold_binary_loc on generic
Date: Wed, 04 Dec 2019 09:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: easyhack, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92734-4-VG72fhq1nV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00333.txt.bz2
Content-length: 631
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92734
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Dec 4 09:38:48 2019
New Revision: 278958
URL: https://gcc.gnu.org/viewcvs?rev=278958&root=gcc&view=rev
Log:
PR tree-optimization/92734
* match.pd ((A +- B) - A -> +- B, (A +- B) -+ B -> A,
A - (A +- B) -> -+ B, A +- (B -+ A) -> +- B): Handle nop_convert.
* gcc.dg/tree-ssa/pr92734-2.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr92734-2.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/match.pd
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662264-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 09:44:52 2019
Return-Path: <gcc-bugs-return-662264-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87676 invoked by alias); 4 Dec 2019 09:44:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87338 invoked by uid 48); 4 Dec 2019 09:44:48 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92788] [10 Regression] ICE in redirect_eh_edge_1, at tree-eh.c:2313
Date: Wed, 04 Dec 2019 09:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92788-4-Qv543jXncN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00334.txt.bz2
Content-length: 481
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92788
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-04
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-662265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 09:55:08 2019
Return-Path: <gcc-bugs-return-662265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123104 invoked by alias); 4 Dec 2019 09:55:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122729 invoked by uid 48); 4 Dec 2019 09:54:59 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92791] New: [10 Regression] ICE in extract_insn, at recog.c:2311 since r278645
Date: Wed, 04 Dec 2019 09:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcchost cf_gcctarget attachments.created
Message-ID: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00335.txt.bz2
Content-length: 1714
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92791
Bug ID: 92791
Summary: [10 Regression] ICE in extract_insn, at recog.c:2311
since r278645
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
Host: i586-linux-gnu
Target: i586-linux-gnu
Created attachment 47414
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47414&action=edit
Source files
It's an ugly bug for which I spent 2 days with a reduction. Still I ended up
with ~7MB of source files. It's reduced from boost package:
$ g++ -fPIC -O2 -flto=auto -march=i686 -fno-strict-aliasing -c *.ii
...
$ g++ -flto=16 -shared 1.o 2.o 3.o 4.o 5.o 6.o 7.o 8.o 9.o 10.o 11.o 12.o 13.o
...
(insn 63 62 64 4 (set (strict_low_part (subreg:QI (reg/v:DI 128 [ sbuf_it ])
4))
(reg:QI 145)) "6.ii":2362:116 -1
(nil))
during RTL pass: vregs
6.ii:7056:1562: internal compiler error: in extract_insn, at recog.c:2311
0x827c17f _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
../../gcc/rtl-error.c:108
0x827c1aa _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
../../gcc/rtl-error.c:116
0x827a264 extract_insn(rtx_insn*)
../../gcc/recog.c:2311
0x85c3a91 instantiate_virtual_regs_in_insn
../../gcc/function.c:1607
0x85c3a91 instantiate_virtual_regs
../../gcc/function.c:1977
0x85c3a91 execute
../../gcc/function.c:2026
>From gcc-bugs-return-662266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 09:55:34 2019
Return-Path: <gcc-bugs-return-662266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123952 invoked by alias); 4 Dec 2019 09:55:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123859 invoked by uid 48); 4 Dec 2019 09:55:29 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92791] [10 Regression] ICE in extract_insn, at recog.c:2311 since r278645
Date: Wed, 04 Dec 2019 09:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92791-4-bhid47PffL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00336.txt.bz2
Content-length: 645
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92791
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-04
CC| |hubicka at gcc dot gnu.org
Known to work| |9.2.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
>From gcc-bugs-return-662267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 09:55:39 2019
Return-Path: <gcc-bugs-return-662267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124520 invoked by alias); 4 Dec 2019 09:55:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123856 invoked by uid 48); 4 Dec 2019 09:55:29 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Wed, 04 Dec 2019 09:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92768-4-ldxPWJTVXn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00337.txt.bz2
Content-length: 634
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
--- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
So I think it's unfortunate that we break testcases like this using _mm_xor_ps
with -ffast-math since users expect the mask to not be treated as signed
zero/zero. The error here obviously lies in the use of FP vectors for
arguments
to _mm_xor_ps but I have no idea how we can rectify users (correct) expectation
here. As Jakub says fixing the regression doesn't really solve the issue in
general.
Still I'd not expect middle-end core-infrastructure like the vector builder
to strip off signs from zeros.
>From gcc-bugs-return-662269-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 10:07:42 2019
Return-Path: <gcc-bugs-return-662269-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29509 invoked by alias); 4 Dec 2019 10:07:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29437 invoked by uid 48); 4 Dec 2019 10:07:37 -0000
From: "ams at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92772] wrong code vectorizing masked max
Date: Wed, 04 Dec 2019 10:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: critical
X-Bugzilla-Who: ams at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92772-4-40smGvPTXH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00339.txt.bz2
Content-length: 443
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92772
--- Comment #3 from Andrew Stubbs <ams at gcc dot gnu.org> ---
The GCN architecture can handle the masking, but I don't know how we'd
represent or apply that in the middle end?
I can probably implement extract_last, and that might be more efficient, but I
don't see how that will help the logic? The convoluted extraction is working
fine; it's the vector comparison that is misleading.
>From gcc-bugs-return-662268-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 10:07:01 2019
Return-Path: <gcc-bugs-return-662268-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28394 invoked by alias); 4 Dec 2019 10:07:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28323 invoked by uid 48); 4 Dec 2019 10:06:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Wed, 04 Dec 2019 10:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92768-4-1O4r3JbtiH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00338.txt.bz2
Content-length: 543
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
For SSE2+, the code can of course use _mm_xor_si128 instead and
_mm_castsi128_ps/_mm_castps_si128, but for SSE that is not an option.
And not really sure what can be done there, the _mm_xor_ps arguments are given,
and even if we e.g. change the xorps builtin to take integral vectors, there
still would be casts to the floating point vectors and still risk of the
optimizers with -fno-signed-zeros to optimize that away.
>From gcc-bugs-return-662271-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 10:21:05 2019
Return-Path: <gcc-bugs-return-662271-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57606 invoked by alias); 4 Dec 2019 10:21:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57520 invoked by uid 48); 4 Dec 2019 10:21:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92788] [10 Regression] ICE in redirect_eh_edge_1, at tree-eh.c:2313
Date: Wed, 04 Dec 2019 10:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92788-4-v9qN9Qa6qF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00341.txt.bz2
Content-length: 1727
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92788
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So, what happens is that we have a bb like:
<bb 13> [local count: 7102878]:
# __result_2 = PHI <_10(3)>
*this_4(D).D.3185._M_impl.D.3135._M_finish = __result_2;
with EH and normal successor edges.
dom_opt_dom_walker::optimize_stmt decides to remove the stmt (the only one in
the bb):
2160 if (cached_lhs && operand_equal_p (rhs, cached_lhs, 0))
2161 {
2162 basic_block bb = gimple_bb (stmt);
2163 unlink_stmt_vdef (stmt);
2164 if (gsi_remove (si, true))
2165 {
2166 bitmap_set_bit (need_eh_cleanup, bb->index);
2167 if (dump_file && (dump_flags & TDF_DETAILS))
2168 fprintf (dump_file, " Flagged to clear EH
edges.\n");
2169 }
2170 release_defs (stmt);
2171 *removed_p = true;
2172 return retval;
2173 }
but before we perform
780 /* Removal of statements may make some EH edges dead. Purge
781 such edges from the CFG as needed. */
782 if (!bitmap_empty_p (need_eh_cleanup))
...
to clean up those EH edges,
774 /* Thread jumps, creating duplicate blocks as needed. */
775 cfg_altered |= thread_through_all_blocks (may_peel_loop_headers_p);
is called, calls thread_block_1 on the bb 13 and ICE trying to redirect EH edge
on a copy of that BB, because for EH edges we obviously assume there is some
statement that can throw but there are no statements in the bb at all.
Not really sure what can be done here.
>From gcc-bugs-return-662270-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 10:21:05 2019
Return-Path: <gcc-bugs-return-662270-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57599 invoked by alias); 4 Dec 2019 10:21:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57515 invoked by uid 48); 4 Dec 2019 10:21:00 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92772] wrong code vectorizing masked max
Date: Wed, 04 Dec 2019 10:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: critical
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92772-4-vD1IitT8Vd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00340.txt.bz2
Content-length: 577
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92772
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
IIRC AVX512 also implements fully masked loops so the testcase should fail
there, too, if we adjust N accordingly (to 15 or 31). Hmm, can't seem to
trigger
the fully masked support here, maybe I misremember.
Btw, isn't the issue that the reduction looks at all lanes? That is,
I think the code simply assumes that for fully masked loops at least
one iteration is performed with all lanes active. So if you bump
N to 64 + 32 the test passes on amdgcn?
>From gcc-bugs-return-662272-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 10:25:52 2019
Return-Path: <gcc-bugs-return-662272-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76811 invoked by alias); 4 Dec 2019 10:25:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76770 invoked by uid 48); 4 Dec 2019 10:25:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92772] wrong code vectorizing masked max
Date: Wed, 04 Dec 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: critical
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92772-4-pvoUQrFY27@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00342.txt.bz2
Content-length: 842
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92772
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
And the issue is to be fixed in vect_create_epilog_for_reduction where
we create the index IV:
/* For cond reductions we want to create a new vector (INDEX_COND_EXPR)
which is updated with the current index of the loop for every match of
the original loop's cond_expr (VEC_STMT). This results in a vector
containing the last time the condition passed for that vector lane.
The first match will be a 1 to allow 0 to be used for non-matching
indexes. If there are no matches at all then the vector will be all
zeroes. */
if (STMT_VINFO_REDUC_TYPE (reduc_info) == COND_REDUCTION)
{
and the masking support needs to be added similarly to how
vectorizable_condition
handles it.
>From gcc-bugs-return-662273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 10:41:26 2019
Return-Path: <gcc-bugs-return-662273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26768 invoked by alias); 4 Dec 2019 10:41:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26741 invoked by uid 48); 4 Dec 2019 10:41:21 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92782] ICE in fold_convert_loc, at fold-const.c:2431
Date: Wed, 04 Dec 2019 10:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92782-4-hnKldww6fD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00343.txt.bz2
Content-length: 695
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92782
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-04
CC| |jakub at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r242037, before that the code was rejected.
>From gcc-bugs-return-662274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 10:44:34 2019
Return-Path: <gcc-bugs-return-662274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34833 invoked by alias); 4 Dec 2019 10:44:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34762 invoked by uid 48); 4 Dec 2019 10:44:29 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92780] [10 Regression] ICE in gfc_get_class_from_expr, at fortran/trans-expr.c:484
Date: Wed, 04 Dec 2019 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92780-4-qsiERFsY3H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92780-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92780-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00344.txt.bz2
Content-length: 823
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92780
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-04
CC| |marxin at gcc dot gnu.org,
| |pault at gcc dot gnu.org
Known to work| |9.2.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r276269.
>From gcc-bugs-return-662275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 10:49:48 2019
Return-Path: <gcc-bugs-return-662275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108323 invoked by alias); 4 Dec 2019 10:49:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107477 invoked by uid 48); 4 Dec 2019 10:49:40 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/91971] Profile directory concatenated with object file path
Date: Wed, 04 Dec 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-91971-4-A3p9Iz6Ku3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00345.txt.bz2
Content-length: 384
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91971
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |ASSIGNED
Assignee|qinzhao at gcc dot gnu.org |marxin at gcc dot gnu.org
>From gcc-bugs-return-662276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 10:50:33 2019
Return-Path: <gcc-bugs-return-662276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113266 invoked by alias); 4 Dec 2019 10:50:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112560 invoked by uid 48); 4 Dec 2019 10:50:26 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92779] [8/9/10 Regression] ICE in gfc_conv_intrinsic_funcall, at fortran/trans-intrinsic.c:4225
Date: Wed, 04 Dec 2019 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92779-4-K3SSm0tttK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92779-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92779-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00346.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92779
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-04
CC| |marxin at gcc dot gnu.org,
| |pault at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Started to ICE with r257827, before that it was rejected.
>From gcc-bugs-return-662277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 11:17:44 2019
Return-Path: <gcc-bugs-return-662277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74713 invoked by alias); 4 Dec 2019 11:17:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74668 invoked by uid 48); 4 Dec 2019 11:17:39 -0000
From: "ricardolafabreu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/92757] Documentation ambiguous/misleading about interplay of optimization and warning flags
Date: Wed, 04 Dec 2019 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: documentation, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ricardolafabreu at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92757-4-iSDLQmdWE9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00347.txt.bz2
Content-length: 905
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #10 from Ricardo Abreu <ricardolafabreu at gmail dot com> ---
> Usually CLI applications don't have as many switches as GCC with as many non-trivial interactions between them.
True, but I am not sure I understand your point. To me that sounds like all the
more reason to avoid coupling between them and document it prominently
otherwise.
My outsider impression is that, ideally, turning on -W... flags should turn on
whatever analysis was needed, independently of optimization. It would make for
smoother UI because it would be more in line with the natural affordance of a
switch. I suppose the increase in compilation cost would be justified by the
request for more checking. I am sure there are reasons why this is unfeasible,
undesirable, too risky... Better highlighting in documentation would alleviate
the surprise.
>From gcc-bugs-return-662278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 11:39:30 2019
Return-Path: <gcc-bugs-return-662278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39311 invoked by alias); 4 Dec 2019 11:39:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39275 invoked by uid 48); 4 Dec 2019 11:39:25 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/92792] New: [10 Regression] symbols dropped from libphobos
Date: Wed, 04 Dec 2019 11:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92792-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00348.txt.bz2
Content-length: 666
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92792
Bug ID: 92792
Summary: [10 Regression] symbols dropped from libphobos
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
Assignee: ibuclaw at gdcproject dot org
Reporter: doko at debian dot org
Target Milestone: ---
Created attachment 47415
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47415&action=edit
symbols diff
the current trunk 20191204 dropped two symbols from the shared phobos library.
Is this expected, should the soversion be bumped?
>From gcc-bugs-return-662279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 11:42:17 2019
Return-Path: <gcc-bugs-return-662279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53898 invoked by alias); 4 Dec 2019 11:42:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53842 invoked by uid 48); 4 Dec 2019 11:42:12 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBmb3J0cmFuLzkyNzkzXSBOZXc6IEZvcnRyYW4gTG9jYXRpb24gRGF0?= =?UTF-8?B?YSBmb3IgRGlhZ25vc3RpYyBsYWNrcyB0aGUgY29sdW1uIG51bWJlciDigJMg?= =?UTF-8?B?d2hlbiBwYXNzaW5nIG9uIHRvIE1F?Date: Wed, 04 Dec 2019 11:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00349.txt.bz2
Content-length: 1579
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92793
Bug ID: 92793
Summary: Fortran Location Data for Diagnostic lacks the column
number – when passing on to ME
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
Target Milestone: ---
Currently, all location_t locations (such as gfc_current_locus->lb->location)
always point to the beginning of the line, i.e. LOCATION_COLUMN(...) == 0.
For front-end diagnostic, this is corrected in gcc/fortran/error.c's
gfc_format_decoder using:
unsigned int offset = loc->nextc - loc->lb->line;
int loc_num = text->get_location (0) == UNKNOWN_LOCATION ? 0 : 1;
location_t src_loc
= linemap_position_for_loc_and_offset (line_table,
loc->lb->location,
offset);
But this correction does not happen when setting the location for 'tree', e.g.:
build_decl (ns->proc_name->declared_at.lb->location
or
tmp = fold_build1_loc (code->expr1->where.lb->location, LOOP_EXPR
or
…
The question is how to fix this best. My feeling is that it should already be
fixed in the scanner such that loc->lb->location is always correct and we
can get rid off the offset calculation in error.c
>From gcc-bugs-return-662280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 11:49:31 2019
Return-Path: <gcc-bugs-return-662280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61008 invoked by alias); 4 Dec 2019 11:49:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60912 invoked by uid 48); 4 Dec 2019 11:49:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92781] ICE in convert_nonlocal_reference_op, at tree-nested.c:1065
Date: Wed, 04 Dec 2019 11:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed attachments.created
Message-ID: <bug-92781-4-NnMf1fzpXq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92781-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92781-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00350.txt.bz2
Content-length: 690
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92781
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-04
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47416
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47416&action=edit
gcc10-pr92781.patch
Untested fix.
>From gcc-bugs-return-662281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 11:51:40 2019
Return-Path: <gcc-bugs-return-662281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63216 invoked by alias); 4 Dec 2019 11:51:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63180 invoked by uid 48); 4 Dec 2019 11:51:36 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92786] [c++11] static constexpr member link error
Date: Wed, 04 Dec 2019 11:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92786-4-OhwBefpmvI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92786-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92786-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00351.txt.bz2
Content-length: 332
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92786
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, this is
https://gcc.gnu.org/wiki/VerboseDiagnostics#missing_static_const_definition
In C++17 the static member is implicitly 'inline' which means the declaration
with an initializer is also a definition.
>From gcc-bugs-return-662282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 12:12:51 2019
Return-Path: <gcc-bugs-return-662282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106613 invoked by alias); 4 Dec 2019 12:12:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106568 invoked by uid 48); 4 Dec 2019 12:12:46 -0000
From: "ams at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92772] wrong code vectorizing masked max
Date: Wed, 04 Dec 2019 12:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: critical
X-Bugzilla-Who: ams at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92772-4-FdFzD6KN9T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00352.txt.bz2
Content-length: 763
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92772
--- Comment #6 from Andrew Stubbs <ams at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #4)
> Btw, isn't the issue that the reduction looks at all lanes? That is,
> I think the code simply assumes that for fully masked loops at least
> one iteration is performed with all lanes active. So if you bump
> N to 64 + 32 the test passes on amdgcn?
Yes, only the loads are masked. For most things this works fine, but not for
reductions or permutations, etc.
If I set N=64, and double the input array, then the test passes indeed.
Masking the load of the {1, 2, 3 .. 63} vector would solve the issue, as would
masking the comparison or the reduction (not that there's an optab for that).
>From gcc-bugs-return-662283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 12:18:43 2019
Return-Path: <gcc-bugs-return-662283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116864 invoked by alias); 4 Dec 2019 12:18:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116826 invoked by uid 48); 4 Dec 2019 12:18:38 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92794] New: [10 Regression] ICE in decide_about_value, at ipa-cp.c:5186
Date: Wed, 04 Dec 2019 12:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget
Message-ID: <bug-92794-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00353.txt.bz2
Content-length: 2211
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92794
Bug ID: 92794
Summary: [10 Regression] ICE in decide_about_value, at
ipa-cp.c:5186
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Target: powerpc-*-linux-gnu
gfortran-10.0.0-alpha20191201 snapshot (r278886) ICEs when compiling the
following testcase, extracted from
gcc/testsuite/gfortran.dg/unlimited_polymorphic_17.f90, for 32-bit BE powerpc
w/ -O3 --param ipa-cp-eval-threshold=2:
module m
implicit none
contains
recursive subroutine show_generic1(a)
class(*), intent(in) :: a(:)
call show_generic1 (a(2:))
return
end subroutine show_generic1
end module m
program test
use :: m
implicit none
real :: array(1:6) = (/ 0, 1, 2, 3, 4, 5 /)
call show_generic1 (array)
end program test
% powerpc-e300c3-linux-gnu-gfortran-10.0.0-alpha20191201 -O3 --param
ipa-cp-eval-threshold=2 -c u0qbclbb.f90
during IPA pass: cp
u0qbclbb.f90:11:0:
11 | use :: m
|
internal compiler error: in decide_about_value, at ipa-cp.c:5186
0x7babc9 decide_about_value<tree_node*>
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/ipa-cp.c:5186
0x1665c65 decide_whether_version_node
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/ipa-cp.c:5245
0x1665c65 ipcp_decision_stage
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/ipa-cp.c:5391
0x1665c65 ipcp_driver
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/ipa-cp.c:5574
0x1665c65 execute
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191201/work/gcc-10-20191201/gcc/ipa-cp.c:5665
>From gcc-bugs-return-662284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 12:20:33 2019
Return-Path: <gcc-bugs-return-662284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119418 invoked by alias); 4 Dec 2019 12:20:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119308 invoked by uid 55); 4 Dec 2019 12:20:27 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92754] ICE in gfc_finish_var_decl, at fortran/trans-decl.c:693
Date: Wed, 04 Dec 2019 12:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92754-4-XluREynv0w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92754-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92754-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00354.txt.bz2
Content-length: 768
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92754
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Wed Dec 4 12:19:55 2019
New Revision: 278961
URL: https://gcc.gnu.org/viewcvs?rev=278961&root=gcc&view=rev
Log:
Fortran] PR92754 - fix an issue with resolving intrinsic functions
gcc/fortran/
PR fortran/92754
* intrinsic.c (gfc_intrinsic_func_interface): Set
sym's flavor, intrinsic and function attribute if
unset.
gcc/testsuite/
PR fortran/92754
gfortran.dg/intrinsic_9.f90: New.
Added:
trunk/gcc/testsuite/gfortran.dg/intrinsic_9.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/intrinsic.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 12:21:10 2019
Return-Path: <gcc-bugs-return-662285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120355 invoked by alias); 4 Dec 2019 12:21:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120304 invoked by uid 48); 4 Dec 2019 12:21:06 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92754] ICE in gfc_finish_var_decl, at fortran/trans-decl.c:693
Date: Wed, 04 Dec 2019 12:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92754-4-IOI0Wcq4Bu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92754-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92754-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00355.txt.bz2
Content-length: 568
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92754
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> ---
FIXED on the GCC 10 trunk – not a (real) regression and potentially fragile
(cf. email); hence, no backporting.
Thanks for the bug report!
>From gcc-bugs-return-662286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 12:32:14 2019
Return-Path: <gcc-bugs-return-662286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31074 invoked by alias); 4 Dec 2019 12:32:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31036 invoked by uid 48); 4 Dec 2019 12:32:09 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92794] [10 Regression] ICE in decide_about_value, at ipa-cp.c:5186
Date: Wed, 04 Dec 2019 12:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cf_known_to_work cf_gcchost everconfirmed cf_known_to_fail
Message-ID: <bug-92794-4-3hmCrFl0zB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92794-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92794-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00356.txt.bz2
Content-length: 794
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92794
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-bisection
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-04
Known to work| |9.2.0
Host| |x86_64-linux-gnu
Ever confirmed|0 |1
Known to fail| |10.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, let me bisect that, one can see it with a cross-compiler as well.
>From gcc-bugs-return-662287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 12:56:46 2019
Return-Path: <gcc-bugs-return-662287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114674 invoked by alias); 4 Dec 2019 12:56:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114622 invoked by uid 48); 4 Dec 2019 12:56:41 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92794] [10 Regression] ICE in decide_about_value, at ipa-cp.c:5186
Date: Wed, 04 Dec 2019 12:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: fxue at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc assigned_to target_milestone
Message-ID: <bug-92794-4-ZRcEJIn4hY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92794-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92794-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00357.txt.bz2
Content-length: 547
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92794
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jamborm at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |fxue at gcc dot gnu.org
Target Milestone|--- |10.0
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r278193.
>From gcc-bugs-return-662288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 13:05:36 2019
Return-Path: <gcc-bugs-return-662288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127400 invoked by alias); 4 Dec 2019 13:05:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127343 invoked by uid 48); 4 Dec 2019 13:05:31 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92791] [10 Regression] ICE in extract_insn, at recog.c:2311 since r278645
Date: Wed, 04 Dec 2019 13:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-92791-4-srKqDrnNeA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00358.txt.bz2
Content-length: 549
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92791
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |jakub at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reproduced, looking at it now.
>From gcc-bugs-return-662289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 13:26:18 2019
Return-Path: <gcc-bugs-return-662289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38778 invoked by alias); 4 Dec 2019 13:26:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38745 invoked by uid 48); 4 Dec 2019 13:26:13 -0000
From: "tim.ruehsen at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/92795] New: Another slowness issue in the demangler (on trunk)
Date: Wed, 04 Dec 2019 13:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tim.ruehsen at gmx dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92795-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00359.txt.bz2
Content-length: 4304
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92795
Bug ID: 92795
Summary: Another slowness issue in the demangler (on trunk)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: demangler
Assignee: unassigned at gcc dot gnu.org
Reporter: tim.ruehsen at gmx dot de
Target Milestone: ---
c++filt
'_ZZ1_DOaaaa1z1psppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp1VEz1VE2On'
takes ~1200s to finish.
Relevant part of the callback
#6 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#7 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#8 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#9 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#10 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#11 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#12 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#13 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#14 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#15 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#16 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#17 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#18 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#19 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#20 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#21 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#22 0x514263 in d_find_pack
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4479:11
#23 0x50d514 in d_print_comp_inner
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:5685:33
#24 0x503a44 in d_print_comp
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:5781:3
#25 0x514138 in d_print_subexpr
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4540:3
#26 0x51150c in d_print_comp_inner
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:5514:4
#27 0x503a44 in d_print_comp
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:5781:3
#28 0x512ce5 in d_print_mod
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c
#29 0x50f6d4 in d_print_comp_inner
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:5155:4
#30 0x503a44 in d_print_comp
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:5781:3
#31 0x50edc2 in d_print_comp_inner
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:5331:2
#32 0x503a44 in d_print_comp
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:5781:3
#33 0x51384c in d_print_function_type
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:6084:5
#34 0x510d8d in d_print_comp_inner
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:5216:4
#35 0x503a44 in d_print_comp
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:5781:3
#36 0x510628 in d_print_comp_inner
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4813:2
#37 0x503a44 in d_print_comp
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:5781:3
#38 0x50dda3 in d_print_comp_inner
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4708:7
#39 0x503a44 in d_print_comp
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:5781:3
#40 0x50335e in cplus_demangle_print_callback
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:4352:5
#41 0x504a5e in d_demangle_callback
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:6345:16
#42 0x504325 in d_demangle
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:6367:12
#43 0x504209 in cplus_demangle_v3
/home/tim/src/binutils-gdb/libiberty/./cp-demangle.c:6524:10
#44 0x4fbc44 in cplus_demangle
/home/tim/src/binutils-gdb/libiberty/./cplus-dem.c:166:13
>From gcc-bugs-return-662290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 13:26:32 2019
Return-Path: <gcc-bugs-return-662290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39463 invoked by alias); 4 Dec 2019 13:26:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39433 invoked by uid 48); 4 Dec 2019 13:26:27 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92743] doc: -Wattribute-alias improperly indexed
Date: Wed, 04 Dec 2019 13:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: diagnostic, documentation, easyhack
X-Bugzilla-Severity: trivial
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92743-4-3EolaN1xEi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92743-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92743-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00360.txt.bz2
Content-length: 446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92743
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed with r272672.
>From gcc-bugs-return-662291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 13:27:34 2019
Return-Path: <gcc-bugs-return-662291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40592 invoked by alias); 4 Dec 2019 13:27:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40465 invoked by uid 48); 4 Dec 2019 13:27:28 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92796] New: [10 Regression] ICE in lra_assign, at lra-assigns.c:1646 on powerpc64le-linux-gnu
Date: Wed, 04 Dec 2019 13:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00361.txt.bz2
Content-length: 1214
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92796
Bug ID: 92796
Summary: [10 Regression] ICE in lra_assign, at
lra-assigns.c:1646 on powerpc64le-linux-gnu
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at debian dot org
Target Milestone: ---
Created attachment 47417
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47417&action=edit
preprocessed source
seen with r278959 on powerpc64le-linux-gnu, trunk:
// during RTL pass: reload
// ../../../src/libquadmath/math/acosq.c: In function 'acosq':
// ../../../src/libquadmath/math/acosq.c:317:1: internal compiler error: in
lra_assign, at lra-assigns.c:1646
// 317 | }
// | ^
// 0x106652fb lra_assign(bool&)
// ../../src/gcc/lra-assigns.c:1646
// 0x1065e353 lra(_IO_FILE*)
// ../../src/gcc/lra.c:2487
// 0x1060345b do_reload
// ../../src/gcc/ira.c:5518
// 0x1060345b execute
// ../../src/gcc/ira.c:5704
// Please submit a full bug report,
// with preprocessed source if appropriate.
>From gcc-bugs-return-662292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 13:32:25 2019
Return-Path: <gcc-bugs-return-662292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45424 invoked by alias); 4 Dec 2019 13:32:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45385 invoked by uid 48); 4 Dec 2019 13:32:20 -0000
From: "tim.ruehsen at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/92797] New: cplus_demangle() produces huge amount of output (on trunk)
Date: Wed, 04 Dec 2019 13:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tim.ruehsen at gmx dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00362.txt.bz2
Content-length: 713
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92797
Bug ID: 92797
Summary: cplus_demangle() produces huge amount of output (on
trunk)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: demangler
Assignee: unassigned at gcc dot gnu.org
Reporter: tim.ruehsen at gmx dot de
Target Milestone: ---
Created attachment 47418
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47418&action=edit
700mb output reproducer
c++file `cat slow-unit-150de9e10e6b2b6e62a6bac5b4c1fc87602ef3c6` (the attached
reproducer file) creates output of >700Mb.
>From gcc-bugs-return-662293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 13:37:18 2019
Return-Path: <gcc-bugs-return-662293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22577 invoked by alias); 4 Dec 2019 13:37:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15839 invoked by uid 48); 4 Dec 2019 13:37:14 -0000
From: "renault at fedoraproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92773] GCC compilation with big array / header is infinite
Date: Wed, 04 Dec 2019 13:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: renault at fedoraproject dot org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-92773-4-9gYl0z70Va@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00363.txt.bz2
Content-length: 775
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92773
Charles-Antoine Couret <renault at fedoraproject dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #47408|0 |1
is obsolete| |
Attachment #47409|0 |1
is obsolete| |
Attachment #47410|0 |1
is obsolete| |
--- Comment #4 from Charles-Antoine Couret <renault at fedoraproject dot org> ---
Created attachment 47419
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47419&action=edit
module driver after preprocessor
>From gcc-bugs-return-662294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 13:43:51 2019
Return-Path: <gcc-bugs-return-662294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89504 invoked by alias); 4 Dec 2019 13:43:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82953 invoked by uid 48); 4 Dec 2019 13:43:46 -0000
From: "tim.ruehsen at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/92797] cplus_demangle() produces huge amount of output (on trunk)
Date: Wed, 04 Dec 2019 13:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tim.ruehsen at gmx dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92797-4-VsaF5Uz1Pz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00364.txt.bz2
Content-length: 165
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92797
--- Comment #1 from Tim Ruehsen <tim.ruehsen at gmx dot de> ---
BTW, llvm-cxxfilt does not show this behavior.
>From gcc-bugs-return-662295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 13:45:59 2019
Return-Path: <gcc-bugs-return-662295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122069 invoked by alias); 4 Dec 2019 13:45:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120888 invoked by uid 48); 4 Dec 2019 13:45:45 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92773] GCC compilation with big array / header is infinite
Date: Wed, 04 Dec 2019 13:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92773-4-sLfz2WxwxF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00365.txt.bz2
Content-length: 194
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92773
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Hmm, compilation finishes instantly for me. I tried, -O2, -Os and -O3.
>From gcc-bugs-return-662296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 13:50:04 2019
Return-Path: <gcc-bugs-return-662296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12284 invoked by alias); 4 Dec 2019 13:50:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12174 invoked by uid 48); 4 Dec 2019 13:49:58 -0000
From: "andrew.burgess at embecosm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92775] Incorrect expression in DW_AT_byte_stride on an array
Date: Wed, 04 Dec 2019 13:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andrew.burgess at embecosm dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92775-4-ebF1PrjMZm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00366.txt.bz2
Content-length: 412
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92775
--- Comment #1 from Andrew Burgess <andrew.burgess at embecosm dot com> ---
I ran a bisect and this is the commit where GCC stops producing the DWARF I
would expect to see:
In GIT:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=47e6a59aedf4b114c2b4865c97a91a7b700cd991
In SVN:
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=251949
>From gcc-bugs-return-662297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 13:56:00 2019
Return-Path: <gcc-bugs-return-662297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10600 invoked by alias); 4 Dec 2019 13:55:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4241 invoked by uid 48); 4 Dec 2019 13:55:55 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92775] Incorrect expression in DW_AT_byte_stride on an array
Date: Wed, 04 Dec 2019 13:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92775-4-IJUUGPf5Uf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00367.txt.bz2
Content-length: 191
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92775
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
That means the get_array_descr_info langhook wasn't updated I guess.
>From gcc-bugs-return-662298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 13:56:59 2019
Return-Path: <gcc-bugs-return-662298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52637 invoked by alias); 4 Dec 2019 13:56:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52544 invoked by uid 48); 4 Dec 2019 13:56:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92775] [8/9/10 Regression] Incorrect expression in DW_AT_byte_stride on an array
Date: Wed, 04 Dec 2019 13:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work target_milestone short_desc
Message-ID: <bug-92775-4-7PvHzFy7GQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00368.txt.bz2
Content-length: 618
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92775
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |7.5.0
Target Milestone|--- |8.4
Summary|Incorrect expression in |[8/9/10 Regression]
|DW_AT_byte_stride on an |Incorrect expression in
|array |DW_AT_byte_stride on an
| |array
>From gcc-bugs-return-662300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 14:06:22 2019
Return-Path: <gcc-bugs-return-662300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112349 invoked by alias); 4 Dec 2019 14:06:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106429 invoked by uid 48); 4 Dec 2019 14:06:17 -0000
From: "zhroma at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92591] ICE in optimize_sc, at modulo-sched.c:1063
Date: Wed, 04 Dec 2019 14:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zhroma at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: zhroma at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92591-4-kbx95uNd3M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92591-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92591-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00370.txt.bz2
Content-length: 296
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92591
--- Comment #6 from Roman Zhuykov <zhroma at gcc dot gnu.org> ---
Patches are still testing. Arm (both 32 and 64 bit) cross compilers are OK,
and I want to test some additional scenarios for powerpc. Probably I'll post
patches next week.
>From gcc-bugs-return-662299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 14:06:12 2019
Return-Path: <gcc-bugs-return-662299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103066 invoked by alias); 4 Dec 2019 14:06:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96558 invoked by uid 48); 4 Dec 2019 14:06:07 -0000
From: "fc9vqetne38 at temp dot mailbox.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92798] New: -fshort-enums can break iterators of std::map
Date: Wed, 04 Dec 2019 14:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fc9vqetne38 at temp dot mailbox.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92798-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00369.txt.bz2
Content-length: 2363
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92798
Bug ID: 92798
Summary: -fshort-enums can break iterators of std::map
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: fc9vqetne38 at temp dot mailbox.org
Target Milestone: ---
Hi,
I'm having problems with iterators of std::map when -fshort-enums is enabled.
It somehow depends on the combination of compiler, stdlib and optimizations
(tested g++ and clang++, libstdc++ and libc++). The size of key (int vs. long)
and map also seem to matter. My layman guess is, that it's somehow related to
operator--.
Short example that shows the (to me unexpected) behavior, used versions of g++
and clang++ at the end:
#include <map>
#include <iostream>
int main() {
auto m = std::map<long, long>{{0,0}, {1,1}, {2,2}};
std::cout << std::boolalpha;
std::cout << (&(*m.begin()) == &(*m.rbegin())) << ' ';
std::cout << (m.begin() == --m.end()) << ' ';
std::cout << (++m.rbegin() == m.rend()) << ' ';
std::cout << (++m.begin() == m.end()) << ' ';
std::cout << (++(--m.end()) == m.end()) << '\n';
}
Compiling with g++ -fshort-enums main.cpp gives
true true true false false
while g++ main.cpp gives
false false false false true
I also tried compiling with clang++, libc++ and optimizations enabled in
various combinations.
1) g++ -nostdinc++ -I/usr/include/c++/v1 main.cpp -nodefaultlibs -lc++ -lc++abi
-lm -lc -lgcc_s -lgcc -fshort-enums
2) g++ -nostdinc++ -I/usr/include/c++/v1 main.cpp -nodefaultlibs -lc++ -lc++abi
-lm -lc -lgcc_s -lgcc -fshort-enums -O
3) clang++ -stdlib=libstdc++ -fshort-enums main.cpp
4) clang++ -O -stdlib=libstdc++ -fshort-enums main.cpp
5) clang++ -stdlib=libc++ -fshort-enums main.cpp
6) clang++ -O -stdlib=libc++ -fshort-enums main.cpp
All 1)-6) give
false false false false true
though 4) sometimes produces
true true true false false
e.g. when doing a range-based loop over the map before the comparisons.
Hope the report is legit and not too messy.
Cheers,
Christian
PS:
opensuse tumbleweed
g++ (SUSE Linux) 9.2.1 20190903 [gcc-9-branch revision 275330]
clang version 9.0.0 (tags/RELEASE_900/final 372316)
>From gcc-bugs-return-662301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 14:14:26 2019
Return-Path: <gcc-bugs-return-662301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93162 invoked by alias); 4 Dec 2019 14:14:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86555 invoked by uid 48); 4 Dec 2019 14:14:21 -0000
From: "anbu1024.me at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92799] New: ICE: in get, at cgraph.h:1339
Date: Wed, 04 Dec 2019 14:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anbu1024.me at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00371.txt.bz2
Content-length: 3190
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92799
Bug ID: 92799
Summary: ICE: in get, at cgraph.h:1339
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anbu1024.me at gmail dot com
Target Milestone: ---
$ cat test.c
static void __attribute__ ( ( weakref ( "bar" ) ) ) foo ( void ) { }
extern void foo ( void ) ;
--------------------------------------------------------------------------------
$ gcc-snapshot10 --version
gcc (GCC) 10.0.0 20191201 (experimental)
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
--------------------------------------------------------------------------------
$ gcc-snapshot10 test.c
test.c:2:53: internal compiler error: in get, at cgraph.h:1339
2 | static void __attribute__ ( ( weakref ( "bar" ) ) ) foo ( void ) { }
| ^~~
0x618bad cgraph_node::get(tree_node const*)
../../gcc-10-20191201/gcc/cgraph.h:1339
0x619c7a cgraph_node::get(tree_node const*)
../../gcc-10-20191201/gcc/tree.h:3387
0x619c7a cgraph_node::analyze()
../../gcc-10-20191201/gcc/cgraphunit.c:622
0x9268ef analyze_functions
../../gcc-10-20191201/gcc/cgraphunit.c:1212
0x9274a2 symbol_table::finalize_compilation_unit()
../../gcc-10-20191201/gcc/cgraphunit.c:2925
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
--------------------------------------------------------------------------------
$ gcc-snapshot9 --version
gcc (GCC) 9.2.1 20191123
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
--------------------------------------------------------------------------------
$ gcc-snapshot9 test.c
test.c:2:53: internal compiler error: Segmentation fault
2 | static void __attribute__ ( ( weakref ( "bar" ) ) ) foo ( void ) { }
| ^~~
0xa8c89f crash_signal
../../gcc-9-20191123/gcc/toplev.c:326
0x71f7c2 cgraph_node* dyn_cast<cgraph_node*, symtab_node>(symtab_node*)
../../gcc-9-20191123/gcc/is-a.h:227
0x71f7c2 cgraph_node::get(tree_node const*)
../../gcc-9-20191123/gcc/cgraph.h:1339
0x71f7c2 cgraph_node::analyze()
../../gcc-9-20191123/gcc/cgraphunit.c:640
0x721e77 analyze_functions
../../gcc-9-20191123/gcc/cgraphunit.c:1126
0x722a62 symbol_table::finalize_compilation_unit()
../../gcc-9-20191123/gcc/cgraphunit.c:2837
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-662302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 14:17:19 2019
Return-Path: <gcc-bugs-return-662302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121814 invoked by alias); 4 Dec 2019 14:17:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120883 invoked by uid 48); 4 Dec 2019 14:17:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92791] [10 Regression] ICE in extract_insn, at recog.c:2311 since r278645
Date: Wed, 04 Dec 2019 14:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92791-4-dqT2UpKgVg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00372.txt.bz2
Content-length: 652
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92791
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So:
struct S { S (void *a, bool b) : x (a), y (b) {} void *x; bool y; };
void bar (S);
void
foo (void *x)
{
S sbuf_it (x, x == nullptr);
bar (sbuf_it);
}
with -O2 -m32 -march=i686 -mtune=i586
gives the same insn, but is actually recognized.
>From what I can see, the problem is that this_fn_optabs points to something
that has been initialized in a function that has been optimized for size, but
this function is not. So, the question is, is it invalid to use
optimize_function_for_size_p (cfun) in optab conditions?
>From gcc-bugs-return-662303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 14:25:37 2019
Return-Path: <gcc-bugs-return-662303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12447 invoked by alias); 4 Dec 2019 14:25:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12358 invoked by uid 48); 4 Dec 2019 14:25:31 -0000
From: "christoph.muellner@theobroma-systems.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92800] New: IPA escape analysis for structs
Date: Wed, 04 Dec 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christoph.muellner@theobroma-systems.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92800-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00373.txt.bz2
Content-length: 1006
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92800
Bug ID: 92800
Summary: IPA escape analysis for structs
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: christoph.muellner@theobroma-systems.com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Having GCC infrastructure code to detect non-escaping
structs during whole-program analysis opens the door
for the field of struct reorganisation optimisations.
We are currently working on such infrastructure
and want to use this ticket to further publish
details and patches, and to collect feedback from
the community.
First implementation details:
* escape analysis for RECORD_TYPE types
* supporting code for IPA passes
* running after IPA visibility
* checking all externally visible symbols/signatures
* checking all type casts
>From gcc-bugs-return-662304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 14:29:03 2019
Return-Path: <gcc-bugs-return-662304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22483 invoked by alias); 4 Dec 2019 14:29:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22444 invoked by uid 48); 4 Dec 2019 14:28:58 -0000
From: "christoph.muellner@theobroma-systems.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92801] New: Drop unused struct fields
Date: Wed, 04 Dec 2019 14:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christoph.muellner@theobroma-systems.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00374.txt.bz2
Content-length: 1454
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92801
Bug ID: 92801
Summary: Drop unused struct fields
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: christoph.muellner@theobroma-systems.com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Non-escaping structs [1] can have their unused fields removed such that
they have a smaller memory footprint and thus allow
a more efficient cache utilisation.
We are currently working on such a pass and want to use this
ticket to further publish details and patches, and to collect
feedback from the community.
First implementation details:
* Iterate with gsi over function bodies to find field accesses
(e.g. in assignment, call, cond or switch statements).
* Allowed for removal if never accessed
* Allowed for removal if write-only (incl. removal of write statements)
* Removal based on modification of DECL_CHAIN() of TYPE_FIELDS(t)
Early tests showed, that this has the potential to eliminate
struct fields nextout and nextin from struct arc of CPU2017's mcf benchmark.
As elements of an struct arc array are accessed for the main calculation in
the hot loop, this benchmark is a good example, where this pass will help.
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92800
>From gcc-bugs-return-662305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 14:32:02 2019
Return-Path: <gcc-bugs-return-662305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27431 invoked by alias); 4 Dec 2019 14:32:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26837 invoked by uid 48); 4 Dec 2019 14:31:55 -0000
From: "christoph.muellner@theobroma-systems.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92538] Proposal for IPA init() constant propagation
Date: Wed, 04 Dec 2019 14:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christoph.muellner@theobroma-systems.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92538-4-JmGgaZAQtE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92538-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92538-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00375.txt.bz2
Content-length: 329
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92538
--- Comment #4 from Christoph Müllner <christoph.muellner@theobroma-systems.com> ---
Early tests with this pass showed that a bunch of SPEC CPU2017 benchmarks
benefit from this. For example, the written-once global variable TTSize of
sjeng
is eliminated by this pass.
>From gcc-bugs-return-662306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 14:36:06 2019
Return-Path: <gcc-bugs-return-662306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38376 invoked by alias); 4 Dec 2019 14:36:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38338 invoked by uid 48); 4 Dec 2019 14:36:01 -0000
From: "christoph.muellner@theobroma-systems.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92802] New: Struct field reordering
Date: Wed, 04 Dec 2019 14:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christoph.muellner@theobroma-systems.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92802-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00376.txt.bz2
Content-length: 967
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92802
Bug ID: 92802
Summary: Struct field reordering
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: christoph.muellner@theobroma-systems.com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Non-escaping structs [1] can be rearranged such that
they have a smaller memory footprint and thus allow
a more efficient cache utilisation.
We are currently working on such a pass and want to use this
ticket to further publish details and patches, and to collect
feedback from the community.
First implementation details:
* Reordering is based on modification of DECL_CHAIN()s of TYPE_FIELDS(t)
* Reordering based on size (biggest to smallest)
[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92800
>From gcc-bugs-return-662307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 14:53:58 2019
Return-Path: <gcc-bugs-return-662307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74531 invoked by alias); 4 Dec 2019 14:53:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74182 invoked by uid 48); 4 Dec 2019 14:53:52 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] New: [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Wed, 04 Dec 2019 14:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcchost
Message-ID: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00377.txt.bz2
Content-length: 1969
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
Bug ID: 92803
Summary: [10 Regression] error: type mismatch in
'vec_perm_expr' since r278764
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-linux-gnu
I see the following ICE reduced from 465.tonto:
$ gcc -O3 -flto=16 -march=haswell realmat.fppized.f90 realmat3.fppized.f90
-shared
realmat3.fppized.f90:7:15:
7 | do n = 1,order
| 1
Warning: Deleted feature: End expression in DO loop at (1) must be integer
realmat3.fppized.f90: In function 'gaussian_f_xyz_matrices':
realmat3.fppized.f90:4: error: type mismatch in 'vec_perm_expr'
4 | function gaussian_f_xyz_matrices(self) result(ftr)
|
vector(4) double
vector(4) double
vector(2) double
vector(4) unsigned long
_433 = VEC_PERM_EXPR <vect__315.16_333, _431, { 3, 5, 0, 1 }>;
during GIMPLE pass: forwprop
realmat3.fppized.f90:4: internal compiler error: verify_gimple failed
0xd16001 verify_gimple_in_cfg(function*, bool)
/home/marxin/Programming/gcc/gcc/tree-cfg.c:5445
0xbf458f execute_function_todo
/home/marxin/Programming/gcc/gcc/passes.c:1983
0xbf533e execute_todo
/home/marxin/Programming/gcc/gcc/passes.c:2037
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
make: *** [/tmp/ccEdrkBy.mk:2: /tmp/ccDaF6lu.ltrans0.ltrans.o] Error 1
lto-wrapper: fatal error: make returned 2 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
>From gcc-bugs-return-662309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 14:54:40 2019
Return-Path: <gcc-bugs-return-662309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75978 invoked by alias); 4 Dec 2019 14:54:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75959 invoked by uid 48); 4 Dec 2019 14:54:36 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Wed, 04 Dec 2019 14:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92803-4-9AOa0U9vMD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00379.txt.bz2
Content-length: 234
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Created attachment 47421
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47421&action=edit
test-case
>From gcc-bugs-return-662308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 14:54:20 2019
Return-Path: <gcc-bugs-return-662308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75274 invoked by alias); 4 Dec 2019 14:54:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75245 invoked by uid 48); 4 Dec 2019 14:54:15 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Wed, 04 Dec 2019 14:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92803-4-8mnDNt0e6U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00378.txt.bz2
Content-length: 234
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Created attachment 47420
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47420&action=edit
test-case
>From gcc-bugs-return-662310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 14:55:18 2019
Return-Path: <gcc-bugs-return-662310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77013 invoked by alias); 4 Dec 2019 14:55:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76972 invoked by uid 48); 4 Dec 2019 14:55:13 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Wed, 04 Dec 2019 14:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92803-4-ukFXigVL0m@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00380.txt.bz2
Content-length: 772
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-04
CC| |jakub at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Known to work| |9.2.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
>From gcc-bugs-return-662311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 15:14:59 2019
Return-Path: <gcc-bugs-return-662311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88488 invoked by alias); 4 Dec 2019 15:14:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88431 invoked by uid 48); 4 Dec 2019 15:14:54 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/85463] [nvptx] "exit" in offloaded region doesn't terminate process
Date: Wed, 04 Dec 2019 15:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: openacc, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85463-4-QGBPDgByUt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85463-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85463-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00381.txt.bz2
Content-length: 1259
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85463
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #2)
> Tom: Can the bug be marked as resolved?
One has
! { dg-output "libgomp: cuStreamSynchronize error.*" { target
openacc_nvidia_accel_selected } }
That's for the output:
----
ERROR STOP (possibly followed by a number or message string)
libgomp: cuStreamSynchronize error: an illegal instruction was encountered
----
Which is not that nice. Also the error code is not propagated. (It is the value
of the integer used with 'error stop' or one when using nothing or a string.)
I assume the illegal instruction was a way to cause terminations with non-zero
exit code …
In my opinion: I think that's the only issue with the current implementation;
if one regards this part as WONTFIX – then the commit in comment 1 has FIXED
it. Otherwise, one can leave this bug OPEN until a better solution is found.
>From gcc-bugs-return-662312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 15:49:34 2019
Return-Path: <gcc-bugs-return-662312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5938 invoked by alias); 4 Dec 2019 15:49:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5888 invoked by uid 48); 4 Dec 2019 15:49:28 -0000
From: "renault at fedoraproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92773] GCC compilation with big array / header is infinite
Date: Wed, 04 Dec 2019 15:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: renault at fedoraproject dot org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92773-4-quRZvUNjNi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00382.txt.bz2
Content-length: 901
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92773
--- Comment #6 from Charles-Antoine Couret <renault at fedoraproject dot org> ---
Ok with a friend we identified a bit more what is the issue.
So in fact I built (manually):
$ gcc -Wall sound/soc/codecs/tas5756m.i -o sound/soc/codecs/tas5756m.o
In that case, no output and it does not stop.
But with:
$ gcc sound/soc/codecs/tas5756m.i
It finished very quickly with some linker errors.
And with:
$ gcc -Wall sound/soc/codecs/tas5756m.i
There are a lot of outputs (warning for each line of my big arrays). And the
process is really slow, some minutes to display the first 1000 lines. It seems
slower over the time (the beginning seems really faster than the end).
I assume that's the issue that I got with Linux build system.
>From my point of view there is a performance regression somewhere. I don't
think this behaviour is normal.
>From gcc-bugs-return-662313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 15:50:17 2019
Return-Path: <gcc-bugs-return-662313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6875 invoked by alias); 4 Dec 2019 15:50:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6825 invoked by uid 48); 4 Dec 2019 15:50:13 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92798] -fshort-enums can break iterators of std::map
Date: Wed, 04 Dec 2019 15:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92798-4-1njCjVmuZj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92798-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92798-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00383.txt.bz2
Content-length: 391
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92798
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
-fshort-enums is an ABI-changing option, which means you should recompile the
entire toolchain including the standard libraries.
Why are you using it anyway? In C++ you can specify a fixed underlying type, so
you can control the exact size of each enumeration type.
>From gcc-bugs-return-662314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 15:54:34 2019
Return-Path: <gcc-bugs-return-662314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88617 invoked by alias); 4 Dec 2019 15:54:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88523 invoked by uid 48); 4 Dec 2019 15:54:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92791] [10 Regression] ICE in extract_insn, at recog.c:2311 since r278645
Date: Wed, 04 Dec 2019 15:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92791-4-UUvcDFUBk2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00384.txt.bz2
Content-length: 3021
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92791
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
We have in the documentation:
For a named pattern, the condition may not depend on the data in
the insn being matched, but only the target-machine-type flags.
The compiler needs to test these conditions during initialization
in order to learn exactly which named instructions are available in
a particular run.
and while optimize_function_for_size_p (cfun) doesn't depend on data in the
insn being matched, it can't be said to be target-machine-type flags either.
As -m32 -O2 -march=i686 testcase below shows, while I can't reproduce the ICE
on a short testcase yet (i.e. the case when init_all_optabs is called while
optimize_function_for_size_p (cfun) is true, but this_fn_optabs is later used
in a function where it is full, this testcase shows the other case, where the
optab is initialized while it is false, but is used when it is true, so this
testcase doesn't use movstrictqi even when it should.
struct S { S (void *a, bool b) : x (a), y (b) {} void *x; bool y; };
void bar (S);
__attribute__((noipa, cold, optimize ("Os"))) void
foo (void *x)
{
S sbuf_it (x, x == nullptr);
bar (sbuf_it);
}
__attribute__((noipa, hot)) void
bar (S x)
{
asm volatile ("" : : "r" (x.x), "q" (x.y) : "memory");
}
__attribute__((noipa, hot)) void
baz (void *x)
{
S sbuf_it (x, x == nullptr);
bar (sbuf_it);
}
__attribute__((noipa, cold, optimize ("Os"))) void
qux (void *x)
{
S sbuf_it (x, x == nullptr);
bar (sbuf_it);
}
int
main ()
{
foo (nullptr);
for (int i = 0; i < 100000; i++)
baz (nullptr);
qux (nullptr);
return 0;
}
Seems movstrict{qi,hi} are the only i386 patterns that in init_all_optabs (as
verified by preprocessing insn-opinit.c) where something depends on size or
speed optimization of current function.
Thus, I think we should go with a patch like:
2019-12-04 Jakub Jelinek <jakub@redhat.com>
PR target/92791
* config/i386/i386.md (movstrict<mode>): Move test for
TARGET_PARTIAL_REG_STALL and not optimizing for size from
expander's condition to the body - FAIL; in that case.
--- gcc/config/i386/i386.md.jj 2019-12-03 09:22:17.421777187 +0100
+++ gcc/config/i386/i386.md 2019-12-04 16:35:34.193669660 +0100
@@ -2801,10 +2801,11 @@ (define_peephole2
(define_expand "movstrict<mode>"
[(set (strict_low_part (match_operand:SWI12 0 "register_operand"))
(match_operand:SWI12 1 "general_operand"))]
- "!TARGET_PARTIAL_REG_STALL || optimize_function_for_size_p (cfun)"
+ ""
{
gcc_assert (SUBREG_P (operands[0]));
- if (GET_MODE_CLASS (GET_MODE (SUBREG_REG (operands[0]))) != MODE_INT)
+ if ((TARGET_PARTIAL_REG_STALL && optimize_function_for_speed_p (cfun))
+ || GET_MODE_CLASS (GET_MODE (SUBREG_REG (operands[0]))) != MODE_INT)
FAIL;
})
which fixes the #c0 ICE and improves the above testcase (makes the Os optimized
functions shorter).
>From gcc-bugs-return-662315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 15:56:02 2019
Return-Path: <gcc-bugs-return-662315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90209 invoked by alias); 4 Dec 2019 15:56:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90125 invoked by uid 48); 4 Dec 2019 15:55:57 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92804] New: [10 Regression] ICE trying to use concept as a nested-name-specifier
Date: Wed, 04 Dec 2019 15:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter blocked target_milestone
Message-ID: <bug-92804-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00385.txt.bz2
Content-length: 4176
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92804
Bug ID: 92804
Summary: [10 Regression] ICE trying to use concept as a
nested-name-specifier
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-invalid-code
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Blocks: 67491
Target Milestone: ---
template<typename T>
concept foo = true;
template<typename T>
void bar(T t)
{
if constexpr (foo<T>::value)
{
}
}
int main()
{
bar(1);
}
Compiled with -std=gnu++2a on trunk:
iced.cc: In function 'void bar(T)':
iced.cc:7:22: internal compiler error: in cp_parser_nested_name_specifier_opt,
at cp/parser.c:6467
7 | if constexpr (foo<T>::value)
| ^
0x9edca7 cp_parser_nested_name_specifier_opt
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:6467
0x9ea58b cp_parser_simple_type_specifier
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:17994
0x9d8ee0 cp_parser_type_specifier
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:17652
0x9d9ea6 cp_parser_decl_specifier_seq
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:14249
0x9f6e6f cp_parser_condition
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:12128
0x9dce0e cp_parser_selection_statement
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:11883
0x9dce0e cp_parser_statement
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:11258
0x9de1f2 cp_parser_statement_seq_opt
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:11742
0x9de2c8 cp_parser_compound_statement
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:11696
0x9f6755 cp_parser_function_body
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:22867
0x9f6755 cp_parser_ctor_initializer_opt_and_function_body
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:22918
0x9f9a91 cp_parser_function_definition_after_declarator
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:28675
0x9fa831 cp_parser_function_definition_from_specifiers_and_declarator
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:28591
0x9fa831 cp_parser_init_declarator
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:20496
0x9ff004 cp_parser_single_declaration
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:29166
0x9ff171 cp_parser_template_declaration_after_parameters
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:28738
0x9ffc89 cp_parser_explicit_template_declaration
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:29004
0x9ffc89 cp_parser_template_declaration_after_export
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:29023
0xa02999 cp_parser_declaration
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:13271
0xa02fe7 cp_parser_translation_unit
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:4721
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
With -std=gnu++17 -fconcepts on gcc-9-branch we get an inaccurate error (it's
not a variable template) but no ICE:
iced.cc: In function 'void bar(T)':
iced.cc:7:17: error: variable template-id 'foo<T>' in nested-name-specifier
7 | if constexpr (foo<T>::value)
| ^~~~~~
iced.cc:2:9: note: 'template<class T> concept const bool foo<T>' declared here
2 | concept foo = true;
| ^~~
iced.cc:7:30: error: expected initializer before ')' token
7 | if constexpr (foo<T>::value)
| ^
iced.cc:7:30: error: the value of 'value' is not usable in a constant
expression
iced.cc: In instantiation of 'void bar(T) [with T = int]':
iced.cc:14:8: required from here
iced.cc:7:3: error: the value of 'value' is not usable in a constant expression
7 | if constexpr (foo<T>::value)
| ^~
iced.cc:5:12: warning: unused parameter 't' [-Wunused-parameter]
5 | void bar(T t)
| ~~^
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67491
[Bug 67491] [meta-bug] concepts issues
>From gcc-bugs-return-662316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 15:57:32 2019
Return-Path: <gcc-bugs-return-662316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91766 invoked by alias); 4 Dec 2019 15:57:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91724 invoked by uid 48); 4 Dec 2019 15:57:27 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92804] [10 Regression] ICE trying to use concept as a nested-name-specifier
Date: Wed, 04 Dec 2019 15:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work cf_known_to_fail
Message-ID: <bug-92804-4-k2isSa2yOG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92804-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92804-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00386.txt.bz2
Content-length: 721
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92804
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |9.2.1
Known to fail| |10.0
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #0)
> With -std=gnu++17 -fconcepts on gcc-9-branch we get an inaccurate error
> (it's not a variable template) but no ICE:
Oh, and the same on trunk. It only ICEs with -std=gnu++2a
So arguably, not a regression, because GCC 9 doesn't support C++2a concepts.
>From gcc-bugs-return-662317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:09:54 2019
Return-Path: <gcc-bugs-return-662317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18822 invoked by alias); 4 Dec 2019 16:09:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18752 invoked by uid 48); 4 Dec 2019 16:09:48 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Wed, 04 Dec 2019 16:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92738-4-XxWEtPwbhC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00387.txt.bz2
Content-length: 939
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
--- Comment #12 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Wilco from comment #11)
> Would using -frepack-arrays solve this issue? I proposed making that the
> default a while back. It would do any repacking that is necessary at call
> sites rather than creating multiple copies of all loops in every function.
I'm not convinced that that is the answer - this would penalize (at runtime)
programs which use non-contiguous memory when _not_ passing them to
an explicit size or assumed size paramter. For example, all the optimizations
for passing a transposed argument would then no longer work.
What we could do instead is to introduce another option, -frepack-inline
(or whatever we want to call it) and enable this by default at all -O
except at -Os. People who have problems can then enable that option for
the specific files they have the problems with.
>From gcc-bugs-return-662318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:18:11 2019
Return-Path: <gcc-bugs-return-662318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47986 invoked by alias); 4 Dec 2019 16:18:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47952 invoked by uid 48); 4 Dec 2019 16:18:06 -0000
From: "ripero84 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92805] New: gfortran: blanks within literal constants should not be allowed
Date: Wed, 04 Dec 2019 16:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ripero84 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92805-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00388.txt.bz2
Content-length: 2677
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92805
Bug ID: 92805
Summary: gfortran: blanks within literal constants should not
be allowed
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: ripero84 at gmail dot com
Target Milestone: ---
I belive that when writing free source form and using kind parameters as part
of integer, real, logical or character literal constants, there cannot be any
blanks between the underscore and the kind-param, or between the underscore and
the rest of characters that are part of the same literal constant. This means
that, e.g.,
3.1415_4
is a valid real literal constant (if 4 is a valid real kind), but
3.1415 _4
3.1415_ 4
are not - and these don't have an possible interpretations as valid Fortran.
My interpretation is based on the following sections and rules of the Fortran
2018 standard:
* 6.2.1: "A lexical token is a keyword, name, literal constant other than a
complex literal constant [...]"
* 6.3.2.2: "In free source form blank characters shall not appear within
lexical tokens other than in a character context or in a format specification."
* R708, R714, and R725 establish that a trailing _kind-param is an optional
part of int-literal-constants, real-literal-constants, and
logical-literal-constants, respectively.
* R724 establishes that a leading kind-param_ is an optional part of a
char-literal-constant.
As far as I can see, these requirements go back all the way to the first
version of the standard that supported free source form, Fortran 90.
Unfortunately, all the versions of gfortran I've tried so far (9.2.1 20191109,
8.3.0, 7.5.0, 6.4.0 20181019), irrespective of the use of one of the -std=
flags or none, fail to detect the presence of blanks at one or both of the
sides of the underscore, and happily compile the source code. This happens
also irrespective of whether the kind-param is numeric (3.1415_4) or an integer
variable with the parameter attribute
INTEGER, PARAMETER :: k = KIND(1.0)
WRITE(*,*) 3.1415_k ! valid Fortran
WRITE(*,*) 3.1415 _k ! invalid Fortran not detected by gfortran
with the only exception of character literal constants, where gfortran actually
produces an error if one attempts to compile code where spaces are present and
the kind-param is given by a variable:
WRITE(*,*) 4_ 'b' ! invalid Fortran not detected by gfortran
INTEGER, PARAMETER :: k = KIND('a')
WRITE(*,*) k_ 'b' ! invalid Fortran detected by gfortran
>From gcc-bugs-return-662319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:19:11 2019
Return-Path: <gcc-bugs-return-662319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50002 invoked by alias); 4 Dec 2019 16:19:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49934 invoked by uid 48); 4 Dec 2019 16:19:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Wed, 04 Dec 2019 16:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92803-4-jHgGES41rR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00389.txt.bz2
Content-length: 334
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reduced testcase with -O2 -mavx:
typedef double v4df __attribute__((vector_size (32)));
typedef double v2df __attribute__((vector_size (16)));
v2df
foo (v4df x, double *p, v2df y)
{
return (v2df) { x[3], *p };
}
>From gcc-bugs-return-662320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:21:31 2019
Return-Path: <gcc-bugs-return-662320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59772 invoked by alias); 4 Dec 2019 16:21:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59716 invoked by uid 48); 4 Dec 2019 16:21:25 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92738] [10 regression] Large code size growth for -O2 binaries between 2019-05-19...2019-05-29
Date: Wed, 04 Dec 2019 16:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92738-4-Ckwl91acyo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00390.txt.bz2
Content-length: 308
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92738
--- Comment #13 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #12)
> People who have problems can then enable
I meant disable, of course.
> that option for
> the specific files they have the problems with.
>From gcc-bugs-return-662321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:25:27 2019
Return-Path: <gcc-bugs-return-662321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62120 invoked by alias); 4 Dec 2019 16:24:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62018 invoked by uid 48); 4 Dec 2019 16:24:43 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81178] [concepts] poor (partial?) diagnostic for alias substitution failure in a concept body
Date: Wed, 04 Dec 2019 16:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81178-4-W5h6DPIM6T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81178-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81178-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00391.txt.bz2
Content-length: 156
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81178
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Huh, trunk now accepts the program.
>From gcc-bugs-return-662322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:25:32 2019
Return-Path: <gcc-bugs-return-662322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62850 invoked by alias); 4 Dec 2019 16:25:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62209 invoked by uid 48); 4 Dec 2019 16:24:51 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92806] New: Suboptimal diagnostic for concept that depends on non-bool value
Date: Wed, 04 Dec 2019 16:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter blocked target_milestone
Message-ID: <bug-92806-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00392.txt.bz2
Content-length: 1668
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92806
Bug ID: 92806
Summary: Suboptimal diagnostic for concept that depends on
non-bool value
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Blocks: 67491
Target Milestone: ---
template<typename T>
struct trait
{
enum { value = 1 };
};
template<typename T>
concept foo = trait<T>::value;
static_assert(foo<int>);
Compiled with -std=gnu++2a:
nonbool.cc:8:9: required by the constraints of 'template<class T> concept
foo'
nonbool.cc:10:24: error: constraint does not have type 'bool'
10 | static_assert(foo<int>);
| ^
nonbool.cc:10:15: error: non-constant condition for static assertion
10 | static_assert(foo<int>);
| ^~~~~~~~
nonbool.cc:8:9: required by the constraints of 'template<class T> concept
foo'
nonbool.cc:10:15: error: constraint does not have type 'bool'
It's not clear from the diagnostic that the problem is trait<T>::value on line
8, so the user is left thinking "how can a concept not have type 'bool'?!"
The fix is something like:
template<typename T>
concept foo = (bool)trait<T>::value;
^~~~~~
so it would be helpful to diagnose the non-bool type at the location of the
concept definition, not its use.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67491
[Bug 67491] [meta-bug] concepts issues
>From gcc-bugs-return-662323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:27:37 2019
Return-Path: <gcc-bugs-return-662323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77095 invoked by alias); 4 Dec 2019 16:27:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76564 invoked by uid 48); 4 Dec 2019 16:27:30 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)
Date: Wed, 04 Dec 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: EH, ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92007-4-Oz6lya8cpW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00393.txt.bz2
Content-length: 217
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007
--- Comment #19 from Arseny Solokha <asolokha at gmx dot com> ---
I believe this is fixed on both affected branches for over a month, thus the PR
can be closed.
>From gcc-bugs-return-662324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:40:31 2019
Return-Path: <gcc-bugs-return-662324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24367 invoked by alias); 4 Dec 2019 16:40:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21556 invoked by uid 48); 4 Dec 2019 16:40:25 -0000
From: "ripero84 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92805] gfortran: blanks within literal constants should not be allowed
Date: Wed, 04 Dec 2019 16:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ripero84 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-92805-4-ZwvyEGbP2U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92805-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92805-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00394.txt.bz2
Content-length: 567
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92805
ripero84 at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ripero84 at gmail dot com
--- Comment #1 from ripero84 at gmail dot com ---
Created attachment 47422
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47422&action=edit
Test source files
I believe all attached tests should fail to compile, but currently only
char_*_var.f90 tests do so.
>From gcc-bugs-return-662325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:43:34 2019
Return-Path: <gcc-bugs-return-662325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40670 invoked by alias); 4 Dec 2019 16:43:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40392 invoked by uid 48); 4 Dec 2019 16:43:28 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92176] LRA problem with reloads for subreg operands
Date: Wed, 04 Dec 2019 16:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ra, wrong-code
X-Bugzilla-Severity: major
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92176-4-nHQu5do7ey@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92176-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92176-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00395.txt.bz2
Content-length: 4035
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92176
--- Comment #6 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #5)
>
> I'll investigate this problem more.
Hi, Andreas. The rtlanal code (!lra_in_progress) was added to GCC since the
first patch introducing LRA. As I wrote it was for x86/x86-64 insn
descriptions which match operands of different modes one of which is XFmode.
After that I introduced LRA_SUBREG_P for solving this problem. So I believe we
can remove the code in rtlanal. Here is the patch I'd like to commit. I
checked it on variety of targets. Is the patch ok for you? I am specially
interesting in your opinion about the test. It is hard for me get z13 machine,
so I decided to use scan-assembler-not instead of running you test.
Index: ../../gcc/gcc/ChangeLog
===================================================================
--- ../../gcc/gcc/ChangeLog (revision 278865)
+++ ../../gcc/gcc/ChangeLog (working copy)
@@ -1,3 +1,10 @@
+2019-12-04 Andreas Krebbel <krebbel@linux.ibm.com>
+ Vladimir Makarov <vmakarov@redhat.com>
+
+ PR rtl-optimization/92176
+ * lra.c (simplify_subreg_regno): Don't permit unconditional
+ changing mode for LRA too.
+
2019-11-29 Vladimir Makarov <vmakarov@redhat.com>
PR rtl-optimization/92283
Index: ../../gcc/gcc/rtlanal.c
===================================================================
--- ../../gcc/gcc/rtlanal.c (revision 278413)
+++ ../../gcc/gcc/rtlanal.c (working copy)
@@ -4009,9 +4009,7 @@ simplify_subreg_regno (unsigned int xreg
/* Give the backend a chance to disallow the mode change. */
if (GET_MODE_CLASS (xmode) != MODE_COMPLEX_INT
&& GET_MODE_CLASS (xmode) != MODE_COMPLEX_FLOAT
- && !REG_CAN_CHANGE_MODE_P (xregno, xmode, ymode)
- /* We can use mode change in LRA for some transformations. */
- && ! lra_in_progress)
+ && !REG_CAN_CHANGE_MODE_P (xregno, xmode, ymode))
return -1;
/* We shouldn't simplify stack-related registers. */
Index: ../../gcc/gcc/testsuite/ChangeLog
===================================================================
--- ../../gcc/gcc/testsuite/ChangeLog (revision 278770)
+++ ../../gcc/gcc/testsuite/ChangeLog (working copy)
@@ -1,3 +1,9 @@
+2019-12-04 Andreas Krebbel <krebbel@linux.ibm.com>
+ Vladimir Makarov <vmakarov@redhat.com>
+
+ PR rtl-optimization/92176
+ * gcc.target/s390/pr92176.c: New test.
+
2019-11-27 Vladimir Makarov <vmakarov@redhat.com>
PR rtl-optimization/90007
Index: ../../gcc/gcc/testsuite/gcc.target/s390/pr92176.c
===================================================================
--- ../../gcc/gcc/testsuite/gcc.target/s390/pr92176.c (nonexistent)
+++ ../../gcc/gcc/testsuite/gcc.target/s390/pr92176.c (working copy)
@@ -0,0 +1,33 @@
+/* { dg-do compile } */
+/* { dg-options "-O3 -march=z13" } */
+
+int a = 5, b, c, d, g, h, k, l, m, o;
+static int e[7];
+int *volatile i = &d;
+long j;
+
+short p(int f, int dummy) {
+ k = 0 != (*e = m);
+ j = 0;
+ for (; j < 59; j = j + 1)
+ *i |= b;
+ g = 1;
+ for (; g <= 4; g++) {
+ o = 0;
+ for (; o <= 4; o++)
+ i = (int * volatile)(long)l;
+ }
+ return 42;
+}
+
+void
+q() {
+ char *n = (char*)&b;
+
+ (*n = a) == p(e[6], c);
+ for (; h;)
+ for (;;)
+ ;
+}
+
+/* { dg-final { scan-assembler-not "\tvsteb" } } */
>From gcc-bugs-return-662327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:51:51 2019
Return-Path: <gcc-bugs-return-662327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50204 invoked by alias); 4 Dec 2019 16:51:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48268 invoked by uid 48); 4 Dec 2019 16:51:46 -0000
From: "skpgkp2 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92807] New: gcc generate extra move for the snippet code
Date: Wed, 04 Dec 2019 16:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: skpgkp2 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00397.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92807
Bug ID: 92807
Summary: gcc generate extra move for the snippet code
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: skpgkp2 at gmail dot com
Target Milestone: ---
>From gcc-bugs-return-662326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:51:26 2019
Return-Path: <gcc-bugs-return-662326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22464 invoked by alias); 4 Dec 2019 16:51:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20512 invoked by uid 48); 4 Dec 2019 16:51:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)
Date: Wed, 04 Dec 2019 16:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: EH, ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92007-4-V6M17sgOpm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00396.txt.bz2
Content-length: 421
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #20 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
.
>From gcc-bugs-return-662328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:52:14 2019
Return-Path: <gcc-bugs-return-662328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51006 invoked by alias); 4 Dec 2019 16:52:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50972 invoked by uid 48); 4 Dec 2019 16:52:09 -0000
From: "fc9vqetne38 at temp dot mailbox.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92798] -fshort-enums can break iterators of std::map
Date: Wed, 04 Dec 2019 16:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fc9vqetne38 at temp dot mailbox.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92798-4-yPPNiT3C3e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92798-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92798-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00398.txt.bz2
Content-length: 589
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92798
--- Comment #2 from Christian N <fc9vqetne38 at temp dot mailbox.org> ---
To be honest, I'm not sure when and why it came to be. The build instructions
are partially from an old project and weren't cleaned properly. The immediate
code base actually only uses scoped enums. The problem just came up and upon
investigating, removing the flag fixed it.
It didn't occur to me that basically everything needs recompilation with
-fshort-enums, but it makes perfect sense.
I suppose this report can be closed as invalid then!?
Thanks!
>From gcc-bugs-return-662329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:57:08 2019
Return-Path: <gcc-bugs-return-662329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82844 invoked by alias); 4 Dec 2019 16:57:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82783 invoked by uid 48); 4 Dec 2019 16:57:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Wed, 04 Dec 2019 16:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92803-4-N55ojYnHaE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00399.txt.bz2
Content-length: 1662
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Untested fix:
--- gcc/tree-ssa-forwprop.c.jj 2019-12-03 20:21:30.554464396 +0100
+++ gcc/tree-ssa-forwprop.c 2019-12-04 17:48:36.351450274 +0100
@@ -2283,11 +2283,11 @@ simplify_vector_constructor (gimple_stmt
gimple_seq stmts = NULL;
if (!orig[1])
orig[1] = orig[0];
- else if (orig[1] == error_mark_node
- && one_nonconstant)
+ else if (orig[1] == error_mark_node && one_nonconstant)
{
orig[1] = gimple_build_vector_from_val (&stmts, UNKNOWN_LOCATION,
- type, one_nonconstant);
+ TREE_TYPE (orig[0]),
+ one_nonconstant);
/* ??? We can see if we can safely convert to the original
element type. */
converted_orig1 = conv_code != ERROR_MARK;
Though, there is another issue, for the nelts 2 vectors
simplify_vector_constructor created code is actually larger than old code.
And, it might be beneficial if we one day implement clang-like
__builtin_shufflevector or at least add to VEC_PERM_EXPR or something similar
the possibility to say certain element is a don't care (for
__builtin_shufflevector I think that is -1 or negative?), as e.g. on AVX/AVX2
when extracting 128-bit vector out of 256-bit permutation all the upper
elements are don't care and we might get better code if the backend picks the
best element indexes for those to get smallest/fastest permutation.
>From gcc-bugs-return-662330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 16:59:14 2019
Return-Path: <gcc-bugs-return-662330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85588 invoked by alias); 4 Dec 2019 16:59:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85563 invoked by uid 48); 4 Dec 2019 16:59:09 -0000
From: "skpgkp2 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92807] gcc generate extra move for the snippet code along with lea instruction.
Date: Wed, 04 Dec 2019 16:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: skpgkp2 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc
Message-ID: <bug-92807-4-3XFW4NMbVr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92807-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00400.txt.bz2
Content-length: 3114
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92807
Sunil Pandey <skpgkp2 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl.tools at gmail dot com,
| |skpgkp2 at gmail dot com
Summary|gcc generate extra move for |gcc generate extra move for
|the snippet code |the snippet code along with
| |lea instruction.
--- Comment #1 from Sunil Pandey <skpgkp2 at gmail dot com> ---
$ cat t1.c
#include<stdint.h>
uint32_t abs2( uint32_t a )
{
uint32_t s = ((a>>15)&0x10001)*0xffff;
return (a+s)^s;
}
$ gcc --version
gcc (GCC) 9.2.1 20190827 (Red Hat 9.2.1-1)
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ gcc -Ofast -S t1.c -o t1.s.gcc.9
$ cat t1.s.gcc.9
.file "t1.c"
.text
.p2align 4
.globl abs2
.type abs2, @function
abs2:
.LFB0:
.cfi_startproc
movl %edi, %edx
shrl $15, %edx
andl $65537, %edx
movl %edx, %eax
sall $16, %eax
subl %edx, %eax
movl %eax, %edx
leal (%rdi,%rax), %eax
xorl %edx, %eax
ret
.cfi_endproc
.LFE0:
.size abs2, .-abs2
.ident "GCC: (GNU) 9.2.1 20190827 (Red Hat 9.2.1-1)"
.section .note.GNU-stack,"",@progbits
Intel compiler generate add instead of lea as well as 1 less mov instruction
for same code.
$ icc -Ofast -S t1.c -o t1.s.icc
$ cat t1.s.icc
.L_2__routine_start_abs2_0:
# -- Begin abs2
.text
# mark_begin;
.align 16,0x90
.globl abs2
# --- abs2(uint32_t)
abs2:
# parameter 1: %edi
..B1.1: # Preds ..B1.0
# Execution count [1.00e+00]
.cfi_startproc
..___tag_value_abs2.1:
..L2:
#3.1
movl %edi, %edx #4.23
shrl $15, %edx #4.23
andl $65537, %edx #4.27
movl %edx, %eax #4.36
shll $16, %eax #4.36
subl %edx, %eax #4.36
addl %eax, %edi #5.19
xorl %edi, %eax #5.22
ret #5.22
.align 16,0x90
# LOE
.cfi_endproc
# mark_end;
.type abs2,@function
.size abs2,.-abs2
..LNabs2.0:
.data
# -- End abs2
.data
.section .note.GNU-stack, ""
# End
>From gcc-bugs-return-662331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 17:01:20 2019
Return-Path: <gcc-bugs-return-662331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96416 invoked by alias); 4 Dec 2019 17:01:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96382 invoked by uid 48); 4 Dec 2019 17:01:14 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92807] gcc generate extra move for the snippet code along with lea instruction.
Date: Wed, 04 Dec 2019 17:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-92807-4-RRzlBL8vRD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92807-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00401.txt.bz2
Content-length: 546
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92807
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-04
Ever confirmed|0 |1
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
Shouldn't
leal (%rdi,%rax), %eax
be changed to
addl %edi, %eax
unconditionally?
>From gcc-bugs-return-662332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 17:13:41 2019
Return-Path: <gcc-bugs-return-662332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126111 invoked by alias); 4 Dec 2019 17:13:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126056 invoked by uid 48); 4 Dec 2019 17:13:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Wed, 04 Dec 2019 17:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-92803-4-U6ixQRePAz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00402.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47423
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47423&action=edit
gcc10-pr92803.patch
Full untested patch for the ICE.
>From gcc-bugs-return-662333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 17:29:39 2019
Return-Path: <gcc-bugs-return-662333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53017 invoked by alias); 4 Dec 2019 17:29:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52944 invoked by uid 48); 4 Dec 2019 17:29:33 -0000
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92767] [m68k]: Random ICE: verify_flow_info failed
Date: Wed, 04 Dec 2019 17:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikpelinux at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92767-4-xWerVJ8hvd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92767-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00403.txt.bz2
Content-length: 732
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92767
Mikael Pettersson <mikpelinux at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpelinux at gmail dot com
--- Comment #3 from Mikael Pettersson <mikpelinux at gmail dot com> ---
I've been doing many gcc-10 native bootstraps on m68k (Aranym) (roughly one per
week), and haven't hit any m68k-specific bootstrap failures. In particular,
r278681 (post-CC0 conversion) bootstrapped fine with c,ada,c++. My builds use
pristine sources, save for a local patch to disable a few test cases known to
time out on m68k.
>From gcc-bugs-return-662334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 17:34:01 2019
Return-Path: <gcc-bugs-return-662334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78597 invoked by alias); 4 Dec 2019 17:34:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 78541 invoked by uid 48); 4 Dec 2019 17:33:56 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92798] -fshort-enums can break iterators of std::map
Date: Wed, 04 Dec 2019 17:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92798-4-jXSVCygXQG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92798-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92798-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00404.txt.bz2
Content-length: 885
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92798
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Christian N from comment #2)
> It didn't occur to me that basically everything needs recompilation with
> -fshort-enums, but it makes perfect sense.
Read the fabulous manual:
Warning: the -fshort-enums switch causes GCC to generate code that is not
binary compatible with code generated without that switch. Use it to conform
to a non-default application binary interface.
> I suppose this report can be closed as invalid then!?
OK, done.
>From gcc-bugs-return-662335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 17:36:22 2019
Return-Path: <gcc-bugs-return-662335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86906 invoked by alias); 4 Dec 2019 17:36:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86800 invoked by uid 48); 4 Dec 2019 17:36:17 -0000
From: "momchil.velikov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92808] New: GCC sets BTI flag in .note.gnu.property section even though not all functions are compiled with BTI
Date: Wed, 04 Dec 2019 17:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: momchil.velikov at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92808-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00405.txt.bz2
Content-length: 1169
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92808
Bug ID: 92808
Summary: GCC sets BTI flag in .note.gnu.property section even
though not all functions are compiled with BTI
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: momchil.velikov at gmail dot com
Target Milestone: ---
When GCC compiles the following source
```
__attribute__((target("branch-protection=pac-ret"))) int f() { return 0; }
__attribute__((target("branch-protection=bti"))) int g() { return 0; }
```
with
aarch64-none-linux-gnu-gcc -c x7.c
the `.note.gnu.property` section has the BTI flag set:
```
$ llvm-readelf --notes x7.o
Displaying notes found at file offset 0x00000090 with length 0x00000020:
Owner Data size Description
GNU 0x00000010 NT_GNU_PROPERTY_TYPE_0 (property note)
Properties: aarch64 feature: BTI
```
IMHO, the flag should be clear, since not all of the functions are compiled
with BTI.
>From gcc-bugs-return-662336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 18:07:16 2019
Return-Path: <gcc-bugs-return-662336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38617 invoked by alias); 4 Dec 2019 18:07:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38559 invoked by uid 48); 4 Dec 2019 18:07:11 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92807] gcc generate extra move for the snippet code along with lea instruction.
Date: Wed, 04 Dec 2019 18:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92807-4-Gyuz87GxG7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92807-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00406.txt.bz2
Content-length: 485
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92807
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Well, lea has to be used in case the flags are live across it. Not the case of
this PR though of course.
>From gcc-bugs-return-662337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 18:14:35 2019
Return-Path: <gcc-bugs-return-662337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10226 invoked by alias); 4 Dec 2019 18:14:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3817 invoked by uid 48); 4 Dec 2019 18:14:30 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92801] Drop unused struct fields
Date: Wed, 04 Dec 2019 18:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92801-4-ZoxI8SwWG7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00407.txt.bz2
Content-length: 829
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92801
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Removal based on modification of DECL_CHAIN() of TYPE_FIELDS(t)
would mean you have to convert either all uses of such types or none. Wouldn't
it be better to rather do it just on particular uses of the types and replace
the types with a new shorter or reordered type instead? I mean, if you in a
couple of functions never access some fields or just write only access them,
but in another spot those fields are used, there is no reason to punt.
>From gcc-bugs-return-662338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 18:26:49 2019
Return-Path: <gcc-bugs-return-662338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113603 invoked by alias); 4 Dec 2019 18:26:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113571 invoked by uid 48); 4 Dec 2019 18:26:44 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92807] gcc generate extra move for the snippet code along with lea instruction.
Date: Wed, 04 Dec 2019 18:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92807-4-atb44jFObe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92807-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00408.txt.bz2
Content-length: 223
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92807
--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
Created attachment 47424
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47424&action=edit
A patch
>From gcc-bugs-return-662339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 18:32:08 2019
Return-Path: <gcc-bugs-return-662339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117965 invoked by alias); 4 Dec 2019 18:32:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117871 invoked by uid 48); 4 Dec 2019 18:32:02 -0000
From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92809] New: [10 regression] error: calls_comdat_local is set outside of a comdat group
Date: Wed, 04 Dec 2019 18:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dimhen at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92809-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00409.txt.bz2
Content-length: 3468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92809
Bug ID: 92809
Summary: [10 regression] error: calls_comdat_local is set
outside of a comdat group
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: dimhen at gmail dot com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
r278936 PASS
r278958 FAIL
Maybe dup PR86905?
$ $ cat x.ii
struct a {
int operator!=(a);
};
template <typename b> struct c : a {
b operator*();
void operator++();
};
template <typename d> struct e {
using f = c<d>;
f begin();
f end();
};
struct g {
virtual void anchor();
};
struct h {
e<int *> i;
virtual void j(int &);
void k();
};
struct l : g, h {
void j(int &) {}
};
void h::k() {
for (auto m : i)
j(*m);
}
$ g++ -fpreprocessed -O2 -std=c++11 -fchecking=1 -c x.ii
x.ii:27:1: error: calls_comdat_local is set outside of a comdat group
27 | }
| ^
_ZThn8_N1l1jERi/2 (virtual void l::_ZThn8_N1l1jERi(int&)) @0x7f578fca12d0
Type: function
Body removed by symtab_remove_unreachable_nodes
Visibility: externally_visible public weak comdat comdat_group:_ZN1l1jERi
one_only section:.text._ZN1l1jERi (implicit_section) virtual artificial
References:
Referring:
Availability: not_available
Function flags: calls_comdat_local indirect_call_target
Former thunk fixed offset -8 virtual value 0 indirect_offset 0 has virtual
offset 0
Called by:
Calls:
during IPA pass: inline
x.ii:27:1: internal compiler error: verify_cgraph_node failed
0xd7a956 cgraph_node::verify_node()
/home/dimhen/src/gcc_current/gcc/cgraph.c:3444
0xd6ea94 symtab_node::verify()
/home/dimhen/src/gcc_current/gcc/symtab.c:1279
0xd6fbbe symtab_node::verify_symtab_nodes()
/home/dimhen/src/gcc_current/gcc/symtab.c:1299
0xff0290 symtab_node::checking_verify_symtab_nodes()
/home/dimhen/src/gcc_current/gcc/cgraph.h:650
0xff0290 symbol_table::remove_unreachable_nodes(_IO_FILE*)
/home/dimhen/src/gcc_current/gcc/ipa.c:672
0x1b893f6 ipa_inline
/home/dimhen/src/gcc_current/gcc/ipa-inline.c:2695
0x1b893f6 execute
/home/dimhen/src/gcc_current/gcc/ipa-inline.c:3088
Please submit a full bug report,
g++ -v
Using built-in specs.
COLLECT_GCC=/home/dimhen/arch-gcc/gcc_current/bin/g++
COLLECT_LTO_WRAPPER=/home/dimhen/arch-gcc/gcc_current/libexec/gcc/x86_64-pc-linux-gnu/10.0.0/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
Target: x86_64-pc-linux-gnu
Configured with: /home/dimhen/src/gcc_current/configure
--prefix=/home/dimhen/arch-gcc/gcc_current
--enable-checking=yes,df,fold,rtl,extra --enable-languages=c,c++,lto
--disable-multilib --enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-gnu-unique-object --enable-linker-build-id
--with-linker-hash-style=gnu --enable-plugin --enable-initfini-array --with-isl
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-gnu-indirect-function --enable-cet --with-tune=native
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.0.0 20191204 (experimental) [trunk revision 278958] (GCC)
>From gcc-bugs-return-662341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 18:49:31 2019
Return-Path: <gcc-bugs-return-662341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15397 invoked by alias); 4 Dec 2019 18:49:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14202 invoked by uid 48); 4 Dec 2019 18:49:14 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92775] [8/9/10 Regression] Incorrect expression in DW_AT_byte_stride on an array
Date: Wed, 04 Dec 2019 18:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-92775-4-RjUQD4tigO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00411.txt.bz2
Content-length: 295
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92775
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
>From gcc-bugs-return-662340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 18:49:25 2019
Return-Path: <gcc-bugs-return-662340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14137 invoked by alias); 4 Dec 2019 18:49:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13723 invoked by uid 48); 4 Dec 2019 18:48:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92775] [8/9/10 Regression] Incorrect expression in DW_AT_byte_stride on an array
Date: Wed, 04 Dec 2019 18:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-92775-4-AYx8vb3sLk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00410.txt.bz2
Content-length: 664
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92775
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-04
CC| |jakub at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
It has been updated. I'll have a look.
>From gcc-bugs-return-662342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 19:18:21 2019
Return-Path: <gcc-bugs-return-662342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72253 invoked by alias); 4 Dec 2019 19:18:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72186 invoked by uid 48); 4 Dec 2019 19:18:15 -0000
From: "christoph.muellner@theobroma-systems.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92801] Drop unused struct fields
Date: Wed, 04 Dec 2019 19:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christoph.muellner@theobroma-systems.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92801-4-Maw1ShG1Yj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00412.txt.bz2
Content-length: 558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92801
--- Comment #2 from Christoph Müllner <christoph.muellner@theobroma-systems.com> ---
Yes, our current approach is all or nothing (i.e. all uses of a struct are
changed or none).
Optimizing individual uses of a type would allow a more tailored optimization.
We decided to defer such an approach in our first shot because it would
make the analysis more complex as we would make individual struct uses
incompatible and we would have to track these uses of the structs
(across compilation units).
>From gcc-bugs-return-662343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 19:54:04 2019
Return-Path: <gcc-bugs-return-662343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17970 invoked by alias); 4 Dec 2019 19:54:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17843 invoked by uid 55); 4 Dec 2019 19:53:59 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92661] [10 Regression] Bootstrap failure with builtin-types.def change
Date: Wed, 04 Dec 2019 19:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92661-4-lVgJDtrEHA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92661-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92661-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00413.txt.bz2
Content-length: 1005
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92661
--- Comment #12 from Peter Bergner <bergner at gcc dot gnu.org> ---
Author: bergner
Date: Wed Dec 4 19:53:26 2019
New Revision: 278973
URL: https://gcc.gnu.org/viewcvs?rev=278973&root=gcc&view=rev
Log:
Do not define builtins that overload disabled builtins.
PR bootstrap/92661
* config/rs6000/rs6000-c.c (struct altivec_builtin_types): Move to
rs6000.h.
(altivec_overloaded_builtins): Move to rs6000-call.c.
* config/rs6000/rs6000.h (struct altivec_builtin_types): Moved from
rs6000-c.c.
* config/rs6000/rs6000-call.c (rs6000_builtin_info): Make static.
(altivec_overloaded_builtins): Moved from rs6000-c.c.
(rs6000_common_init_builtins): Do no define builtins that overload
builtins that have been disabled.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/rs6000/rs6000-c.c
trunk/gcc/config/rs6000/rs6000-call.c
trunk/gcc/config/rs6000/rs6000.h
>From gcc-bugs-return-662344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 20:03:46 2019
Return-Path: <gcc-bugs-return-662344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42271 invoked by alias); 4 Dec 2019 20:03:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42205 invoked by uid 48); 4 Dec 2019 20:03:41 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92661] [10 Regression] Bootstrap failure with builtin-types.def change
Date: Wed, 04 Dec 2019 20:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92661-4-ZJMhAWVwTU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92661-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92661-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00414.txt.bz2
Content-length: 674
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92661
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #13 from Peter Bergner <bergner at gcc dot gnu.org> ---
Ok, second patch to fix the overloaded builtin issue has been committed to
trunk, so I'm marking this as resolved.
We are discussing about disabling the running of the powerpc/dfp/ tests when
DFP is disabled, but that isn't required for this bugzilla.
>From gcc-bugs-return-662345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 21:53:56 2019
Return-Path: <gcc-bugs-return-662345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95366 invoked by alias); 4 Dec 2019 21:53:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95308 invoked by uid 48); 4 Dec 2019 21:53:51 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92810] New: Compiling GCC go for aarch64_be-marvell-linux-gnu fails
Date: Wed, 04 Dec 2019 21:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget
Message-ID: <bug-92810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00415.txt.bz2
Content-length: 2202
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92810
Bug ID: 92810
Summary: Compiling GCC go for aarch64_be-marvell-linux-gnu
fails
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: build
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: pinskia at gcc dot gnu.org
CC: cmang at google dot com
Target Milestone: ---
Target: aarch64_be-marvell-linux-gnu
cpugen.go:3:1: error: expected operand
3 | const FunctionDescriptors = false
| ^
cpugen.go:3:1: error: expected ‘;’ or newline after top level declaration
version.go:67:13: error: expected ‘;’ or ‘)’ or newline
67 | BigEndian =
| ^
version.go:67:3: error: reference to undefined name ‘BigEndian’
67 | BigEndian =
| ^
libtool: compile:
/home/apinski/src/toolchain-10/build-aarch64_be-marvell-linux-gnu/./gcc/gccgo
-B/home/apinski/src/toolchain-10/build-aarch64_be-marvell-linux-gnu/./gcc/
-B/bajas/pinskia/src/toolchain-10/scripts/../marvell-tools-be/aarch64_be-marvell-linux-gnu/bin/
-B/bajas/pinskia/src/toolchain-10/scripts/../marvell-tools-be/aarch64_be-marvell-linux-gnu/lib/
-isystem
/bajas/pinskia/src/toolchain-10/scripts/../marvell-tools-be/aarch64_be-marvell-linux-gnu/include
-isystem
/bajas/pinskia/src/toolchain-10/scripts/../marvell-tools-be/aarch64_be-marvell-linux-gnu/sys-include
-L/home/apinski/src/toolchain-10/build-aarch64_be-marvell-linux-gnu/./ld -O2 -g
-I . -c -fgo-pkgpath=crypto/subtle
/bajas/pinskia/src/toolchain-10/scripts/../src/libgo/go/crypto/subtle/constant_time.go
-fPIC -o crypto/.libs/subtle.o
Makefile:2826: recipe for target 'runtime/internal/sys.lo' failed
make[5]: *** [runtime/internal/sys.lo] Error 1
make[5]: *** Waiting for unfinished jobs....
---- CUT ---
This is because aarch64_be is not detected at all in libgo/configure .
Currently only aarch64-*-* is detected:
aarch64-*-*)
GOARCH=arm64
;;
Even though arm64be is listed in ALLGOARCH.
>From gcc-bugs-return-662346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 21:57:16 2019
Return-Path: <gcc-bugs-return-662346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99171 invoked by alias); 4 Dec 2019 21:57:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99133 invoked by uid 48); 4 Dec 2019 21:57:11 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/92797] cplus_demangle() produces huge amount of output (on trunk)
Date: Wed, 04 Dec 2019 21:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92797-4-6JKlE4WSUh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00416.txt.bz2
Content-length: 269
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92797
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Tim Ruehsen from comment #1)
> BTW, llvm-cxxfilt does not show this behavior.
Could it because it does not implement the D demangler?
>From gcc-bugs-return-662347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 22:11:48 2019
Return-Path: <gcc-bugs-return-662347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18634 invoked by alias); 4 Dec 2019 22:11:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18241 invoked by uid 48); 4 Dec 2019 22:11:43 -0000
From: "david at westcontrol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92811] New: Odd optimisation differences with lambdas
Date: Wed, 04 Dec 2019 22:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: david at westcontrol dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00417.txt.bz2
Content-length: 1810
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92811
Bug ID: 92811
Summary: Odd optimisation differences with lambdas
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: david at westcontrol dot com
Target Milestone: ---
While playing with lambdas for higher order functions (in particular, functions
that manipulate functions and return new ones), I saw some differences in the
optimisations depending on seemingly minor changes to how functions are
defined. This is my sample code:
template <typename F>
auto twice(F f)
{
return [f](int v) { return f(f(v)); };
};
int g1(int i)
{
return i + 3;
};
auto g2 = [](int i) { return i + 3; };
int test(int i) {
auto tw = twice(g1);
return tw(i);
}
int test2(int i) {
auto tw = twice(g1);
auto tw2 = twice(tw);
return tw2(i);
}
int test3(int i) {
auto tw = twice(g2);
return tw(i);
}
int test4(int i) {
auto tw = twice(g2);
auto tw2 = twice(tw);
return tw2(i);
}
The generated assembly (x86-64) with -O2 or -O3 is:
g1(int):
leal 3(%rdi), %eax
ret
test(int):
leal 6(%rdi), %eax
ret
test2(int):
addl $6, %edi
call g1(int)
movl %eax, %edi
jmp g1(int)
test3(int):
leal 6(%rdi), %eax
ret
test4(int):
leal 12(%rdi), %eax
ret
With -O1, test3 and test4 (where the original function is a lambda) were still
fully optimised, while test1 and test2 had 2 and 4 calls to g1.
(For comparison, clang requires -O2 to get good code, but fully optimises all 4
test functions.)
>From gcc-bugs-return-662348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 22:25:14 2019
Return-Path: <gcc-bugs-return-662348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48460 invoked by alias); 4 Dec 2019 22:24:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48207 invoked by uid 48); 4 Dec 2019 22:24:33 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/84919] [8/9/10 Regression] error: passing argument 1 to restrict-qualified parameter aliases with argument 5 [-Werror=restrict]
Date: Wed, 04 Dec 2019 22:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords: deferred, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84919-4-RiB3oQLT7K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84919-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84919-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00418.txt.bz2
Content-length: 1446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84919
--- Comment #17 from Martin Sebor <msebor at gcc dot gnu.org> ---
The patch below avoids the warning. Unfortunately, as a result of bug 92666,
it triggers another bogus warning during bootstrap.
Index: gcc/c-family/c-common.c
===================================================================
--- gcc/c-family/c-common.c (revision 278975)
+++ gcc/c-family/c-common.c (working copy)
@@ -5763,8 +5763,26 @@ check_function_arguments (location_t loc, const_tr
if (warn_format)
check_function_sentinel (fntype, nargs, argarray);
- if (warn_restrict)
- warned_p |= check_function_restrict (fndecl, fntype, nargs, argarray);
+ if (fndecl && fndecl_built_in_p (fndecl, BUILT_IN_NORMAL))
+ {
+ switch (DECL_FUNCTION_CODE (fndecl))
+ {
+ case BUILT_IN_SPRINTF:
+ case BUILT_IN_SPRINTF_CHK:
+ case BUILT_IN_SNPRINTF:
+ case BUILT_IN_SNPRINTF_CHK:
+ /* Let the sprintf pass handle these. */
+ return warned_p;
+
+ default:
+ break;
+ }
+ }
+
+ /* check_function_restrict sets the DECL_READ_P for arguments
+ so it must be called unconiditionally. */
+ warned_p |= check_function_restrict (fndecl, fntype, nargs, argarray);
+
return warned_p;
}
>From gcc-bugs-return-662349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 22:41:56 2019
Return-Path: <gcc-bugs-return-662349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66813 invoked by alias); 4 Dec 2019 22:41:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66731 invoked by uid 48); 4 Dec 2019 22:41:50 -0000
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91661] ICE in gfc_conv_intrinsic_dot_product, at fortran/trans-intrinsic.c:4804
Date: Wed, 04 Dec 2019 22:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91661-4-o19pWpioqw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91661-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91661-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00419.txt.bz2
Content-length: 2638
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91661
--- Comment #4 from anlauf at gcc dot gnu.org ---
The following variant of the patch in comment#3 regtests cleanly and handles
more complex cases, like
integer, parameter :: b(a(1)+a(2)) = 3
Index: gcc/fortran/decl.c
===================================================================
--- gcc/fortran/decl.c (Revision 278972)
+++ gcc/fortran/decl.c (Arbeitskopie)
@@ -29,6 +29,7 @@ along with GCC; see the file COPYING3. If not see
#include "parse.h"
#include "constructor.h"
#include "target.h"
+#include "arith.h"
/* Macros to access allocate memory for gfc_data_variable,
gfc_data_value and gfc_data. */
@@ -2587,8 +2588,20 @@ variable_decl (int elem)
if (e->expr_type != EXPR_CONSTANT)
{
n = gfc_copy_expr (e);
+ switch (n->expr_type)
+ {
+ case EXPR_VARIABLE:
+ case EXPR_FUNCTION:
+ case EXPR_OP:
+ gfc_resolve_expr (n);
+ break;
+
+ default:
+ break;
+ }
gfc_simplify_expr (n, 1);
- if (n->expr_type == EXPR_CONSTANT)
+ if (n->expr_type == EXPR_CONSTANT
+ && gfc_range_check (n) == ARITH_OK)
gfc_replace_expr (e, n);
else
gfc_free_expr (n);
@@ -2597,8 +2610,20 @@ variable_decl (int elem)
if (e->expr_type != EXPR_CONSTANT)
{
n = gfc_copy_expr (e);
+ switch (n->expr_type)
+ {
+ case EXPR_VARIABLE:
+ case EXPR_FUNCTION:
+ case EXPR_OP:
+ gfc_resolve_expr (n);
+ break;
+
+ default:
+ break;
+ }
gfc_simplify_expr (n, 1);
- if (n->expr_type == EXPR_CONSTANT)
+ if (n->expr_type == EXPR_CONSTANT
+ && gfc_range_check (n) == ARITH_OK)
gfc_replace_expr (e, n);
else
gfc_free_expr (n);
Given the clumsiness to circumvent the issue with type-bound procedures,
I feel that the simplifications involved should be done at an earlier stage.
Anybody knows where that might be?
>From gcc-bugs-return-662350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 22:49:21 2019
Return-Path: <gcc-bugs-return-662350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92747 invoked by alias); 4 Dec 2019 22:49:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 92431 invoked by uid 48); 4 Dec 2019 22:48:38 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/70517] c++filt crashes when demangling a symbol
Date: Wed, 04 Dec 2019 22:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: 5.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-70517-4-XDCzfxs4dP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70517-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70517-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00420.txt.bz2
Content-length: 492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70517
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #5 from Christian Biesinger <cbiesinger at google dot com> ---
Using binutils from a month ago or so, this does not crash but also does not
demangle...
>From gcc-bugs-return-662351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 22:59:56 2019
Return-Path: <gcc-bugs-return-662351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21317 invoked by alias); 4 Dec 2019 22:59:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21205 invoked by uid 48); 4 Dec 2019 22:59:51 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/81682] Timeout in demangler
Date: Wed, 04 Dec 2019 22:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-81682-4-zzCTAQfTH7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00421.txt.bz2
Content-length: 484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81682
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #3 from Christian Biesinger <cbiesinger at google dot com> ---
In today's binutils, both those testcases run really quick in c++filt
(cxxfilt).
>From gcc-bugs-return-662352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:06:42 2019
Return-Path: <gcc-bugs-return-662352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41554 invoked by alias); 4 Dec 2019 23:06:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41525 invoked by uid 48); 4 Dec 2019 23:06:37 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/85309] demangler failed with signal 11
Date: Wed, 04 Dec 2019 23:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85309-4-AxvKja0BU4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85309-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85309-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00422.txt.bz2
Content-length: 904
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85309
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #1 from Christian Biesinger <cbiesinger at google dot com> ---
This seems to not crash in GDB from today:
GNU gdb (GDB) 9.0.50.20191204-git
(gdb) set lang c++
(gdb) demangle
_ZSt7forwardIRZN3ftz6Engine20ClientNetworkHandler13ProcessEventsEvEUlRT_E_EOS3_RNSt16remove_referenceIS3_E4typeE
ftz::Engine::ClientNetworkHandler::ProcessEvents()::{lambda(auto:1&)#1}&
std::forward<ftz::Engine::ClientNetworkHandler::ProcessEvents()::{lambda(auto:1&)#1}&>(std::remove_reference<ftz::Engine::ClientNetworkHandler::ProcessEvents()::{lambda(auto:1&)#1}&>::type&)
quit)
>From gcc-bugs-return-662353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:11:24 2019
Return-Path: <gcc-bugs-return-662353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8702 invoked by alias); 4 Dec 2019 23:11:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8643 invoked by uid 48); 4 Dec 2019 23:11:19 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/88629] Regression lead to Heap-buffer-overflow problem in function d_expression_1 in cp-demangle.c, as demonstrated by c++filt
Date: Wed, 04 Dec 2019 23:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88629-4-xRpdTGykq9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88629-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88629-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00423.txt.bz2
Content-length: 494
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88629
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #6 from Christian Biesinger <cbiesinger at google dot com> ---
I can't reproduce this on any of the three testcases with today's binutils
built with ASAN
>From gcc-bugs-return-662354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:13:07 2019
Return-Path: <gcc-bugs-return-662354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11989 invoked by alias); 4 Dec 2019 23:13:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11951 invoked by uid 48); 4 Dec 2019 23:13:02 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92812] New: Implement P1975R0: Fixing the wording of parenthesized aggregate-initialization
Date: Wed, 04 Dec 2019 23:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00424.txt.bz2
Content-length: 602
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92812
Bug ID: 92812
Summary: Implement P1975R0: Fixing the wording of parenthesized
aggregate-initialization
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mpolacek at gcc dot gnu.org
Target Milestone: ---
As per
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1975r0.html
This wasn't included in my patch for P0960.
>From gcc-bugs-return-662355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:14:08 2019
Return-Path: <gcc-bugs-return-662355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13226 invoked by alias); 4 Dec 2019 23:14:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13199 invoked by uid 48); 4 Dec 2019 23:14:02 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/89671] Demangling segfault
Date: Wed, 04 Dec 2019 23:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-89671-4-2qWFg0qAyj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89671-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89671-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00425.txt.bz2
Content-length: 531
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89671
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #2 from Christian Biesinger <cbiesinger at google dot com> ---
Hmm, this one crashes for me in c++filt 2.31.1 but not on today's trunk (though
it doesn't demangle it into anything, either)
>From gcc-bugs-return-662357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:19:27 2019
Return-Path: <gcc-bugs-return-662357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80771 invoked by alias); 4 Dec 2019 23:19:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80744 invoked by uid 48); 4 Dec 2019 23:19:22 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/92453] write buffer overflow in cplus_demangle()
Date: Wed, 04 Dec 2019 23:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92453-4-y39QBnQ7cH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92453-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92453-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00427.txt.bz2
Content-length: 502
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92453
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #2 from Christian Biesinger <cbiesinger at google dot com> ---
Could you send your patch to gcc-patches per
https://gcc.gnu.org/contribute.html#patches ? Thanks!
>From gcc-bugs-return-662356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:19:13 2019
Return-Path: <gcc-bugs-return-662356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80085 invoked by alias); 4 Dec 2019 23:19:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73653 invoked by uid 48); 4 Dec 2019 23:19:08 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92813] New: sprintf result not used by strlen pass
Date: Wed, 04 Dec 2019 23:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00426.txt.bz2
Content-length: 1866
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92813
Bug ID: 92813
Summary: sprintf result not used by strlen pass
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
With the integration of the sprintf pass into strlen, GCC 10 makes use of
string lengths computed by the strlen pass to also compute the size of sprintf
(and snprintf) output. This makes it possible to optimize calls like the one
if function f() below. But the integration exposes string lengths only in one
direction, and doesn't also make the lengths computed by the sprintf pass
available to the strlen pass. This can be seen in the dump for function g()
below which should be optimized away just like f() but isn't.
$ cat t.c && gcc -O2 -S -Wall -fdump-tree-optimized=/dev/stdout t.c
void f (void)
{
char a[8];
__builtin_strcpy (a, "1234");
if (__builtin_snprintf (0, 0, "%s", a) != 4)
__builtin_abort ();
}
void g (void)
{
char a[8];
__builtin_sprintf (a, "1234");
if (__builtin_strlen (a) != 4)
__builtin_abort ();
}
;; Function f (f, funcdef_no=0, decl_uid=1930, cgraph_uid=1, symbol_order=0)
f ()
{
<bb 2> [local count: 1073741824]:
return;
}
;; Function g (g, funcdef_no=1, decl_uid=1934, cgraph_uid=2, symbol_order=1)
g ()
{
char a[8];
long unsigned int _1;
<bb 2> [local count: 1073741824]:
__builtin_memcpy (&a, "1234", 5);
_1 = __builtin_strlen (&a);
if (_1 != 4)
goto <bb 3>; [0.00%]
else
goto <bb 4>; [100.00%]
<bb 3> [count: 0]:
__builtin_abort ();
<bb 4> [local count: 1073741824]:
a ={v} {CLOBBER};
return;
}
>From gcc-bugs-return-662358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:24:04 2019
Return-Path: <gcc-bugs-return-662358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85824 invoked by alias); 4 Dec 2019 23:24:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85715 invoked by uid 48); 4 Dec 2019 23:23:58 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92813] sprintf result not used by strlen pass
Date: Wed, 04 Dec 2019 23:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords blocked
Message-ID: <bug-92813-4-EKyyEn2vhj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00428.txt.bz2
Content-length: 2121
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92813
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic,
| |missed-optimization
Blocks| |83819
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Implementing this optimization will also make it possible to detect buffer
overflow in such cases:
$ cat t.c && gcc -O2 -S -Wall -fdump-tree-optimized=/dev/stdout t.c
char a[8];
void f (void)
{
__builtin_strcpy (a, "1234");
__builtin_sprintf (a + 4, "%s", "5678"); // warning (good)
}
void g (void)
{
__builtin_sprintf (a, "%s", "1234");
__builtin_strcat (a, "5678"); // missing warning
}
t.c: In function ‘f’:
t.c:6:32: warning: ‘__builtin_sprintf’ writing a terminating nul past the end
of the destination [-Wformat-overflow=]
6 | __builtin_sprintf (a + 4, "%s", "5678"); // warning (good)
| ^
t.c:6:3: note: ‘__builtin_sprintf’ output 5 bytes into a destination of size 4
6 | __builtin_sprintf (a + 4, "%s", "5678"); // warning (good)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
;; Function f (f, funcdef_no=0, decl_uid=1931, cgraph_uid=1, symbol_order=1)
f ()
{
<bb 2> [local count: 1073741824]:
__builtin_memcpy (&a, "1234", 5);
__builtin_sprintf (&MEM <char[8]> [(void *)&a + 4B], "%s", "5678"); [tail
call]
return;
}
;; Function g (g, funcdef_no=1, decl_uid=1934, cgraph_uid=2, symbol_order=2)
g ()
{
long unsigned int _3;
char[8] * _4;
<bb 2> [local count: 1073741824]:
__builtin_memcpy (&a, "1234", 5);
_3 = __builtin_strlen (&a);
_4 = &a + _3;
__builtin_memcpy (_4, "5678", 5); [tail call]
return;
}
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819
[Bug 83819] [meta-bug] missing strlen optimizations
>From gcc-bugs-return-662359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:25:07 2019
Return-Path: <gcc-bugs-return-662359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87108 invoked by alias); 4 Dec 2019 23:24:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86986 invoked by uid 48); 4 Dec 2019 23:24:49 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/84668] c++filt: out of memory allocating 18446744071696285694 bytes after a total of 135168 bytes
Date: Wed, 04 Dec 2019 23:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84668-4-g6ebiMNwar@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00429.txt.bz2
Content-length: 485
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84668
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #3 from Christian Biesinger <cbiesinger at google dot com> ---
Hmm this seems to be fixed on trunk for me, though still reproducible on 2.31.1
>From gcc-bugs-return-662360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:26:48 2019
Return-Path: <gcc-bugs-return-662360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89797 invoked by alias); 4 Dec 2019 23:26:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89727 invoked by uid 55); 4 Dec 2019 23:26:42 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88827] Rejects valid program using &* operator combination.
Date: Wed, 04 Dec 2019 23:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88827-4-bixbyPRpee@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88827-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88827-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00430.txt.bz2
Content-length: 3071
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88827
--- Comment #1 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Author: jsm28
Date: Wed Dec 4 23:26:10 2019
New Revision: 278976
URL: https://gcc.gnu.org/viewcvs?rev=278976&root=gcc&view=rev
Log:
Fix C handling of use of lvalues of incomplete types (PR c/36941, PR c/88827).
Bug 88827 points out that GCC should not be rejecting C code that
dereferences a pointer to an incomplete type in the case that uses &*
to take the address of the resulting lvalue, because no constraint is
violated in that case (other than for C90 when the incomplete type is
unqualified void, which we already handle correctly) and as the lvalue
never gets converted to an rvalue there is no undefined behavior
either.
This means that the diagnostic for such a dereference is bogus and
should be removed; if the lvalue gets converted to an rvalue, there
should be an appropriate error later for the use of the incomplete
type. In most cases, there is, but bug 36941 points out the lack of a
diagnostic when the incomplete (non-void) type gets cast to void
(where a diagnostic seems appropriate for this undefined behavior as a
matter of quality of implementation).
This patch removes the bogus diagnostic (and C_TYPE_ERROR_REPORTED
which was only used in the code that is removed - only that one, bogus
diagnostic had this duplicate suppression, not any of the other, more
legitimate diagnostics for use of incomplete types) and makes
convert_lvalue_to_rvalue call require_complete_type for arguments not
of void types, so that all relevant code paths (possibly except some
for ObjC) get incomplete types diagnosed. It's possible that this
makes some other checks for incomplete types obsolete, but no attempt
is made to remove any such checks.
Bootstrapped with no regressions for x86_64-pc-linux-gnu.
PR c/36941
PR c/88827
gcc/c:
* c-typeck.c (convert_lvalue_to_rvalue): Call
require_complete_type for arguments not of void types.
(build_indirect_ref): Do not diagnose dereferencing pointers to
incomplete types.
* c-tree.h (C_TYPE_ERROR_REPORTED): Remove.
gcc/testsuite:
* gcc.dg/lvalue-9.c, gcc.dg/lvalue-10.c: New tests.
* gcc.dg/array-8.c, gcc.dg/enum-incomplete-1.c,
gcc.dg/enum-incomplete-3.c, gcc.dg/noncompile/incomplete-3.c,
gcc.dg/pr48552-1.c, gcc.dg/pr48552-2.c, gcc.dg/pr63543.c,
gcc.dg/pr69796.c: Update expected diagnostics.
Added:
trunk/gcc/testsuite/gcc.dg/lvalue-10.c
trunk/gcc/testsuite/gcc.dg/lvalue-9.c
Modified:
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-tree.h
trunk/gcc/c/c-typeck.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/array-8.c
trunk/gcc/testsuite/gcc.dg/enum-incomplete-1.c
trunk/gcc/testsuite/gcc.dg/enum-incomplete-3.c
trunk/gcc/testsuite/gcc.dg/noncompile/incomplete-3.c
trunk/gcc/testsuite/gcc.dg/pr48552-1.c
trunk/gcc/testsuite/gcc.dg/pr48552-2.c
trunk/gcc/testsuite/gcc.dg/pr63543.c
trunk/gcc/testsuite/gcc.dg/pr69796.c
>From gcc-bugs-return-662361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:26:49 2019
Return-Path: <gcc-bugs-return-662361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89866 invoked by alias); 4 Dec 2019 23:26:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89745 invoked by uid 55); 4 Dec 2019 23:26:44 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/36941] gcc does not reject invalid cast
Date: Wed, 04 Dec 2019 23:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-36941-4-FStUmACB8Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-36941-4@http.gcc.gnu.org/bugzilla/>
References: <bug-36941-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00431.txt.bz2
Content-length: 3071
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36941
--- Comment #9 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Author: jsm28
Date: Wed Dec 4 23:26:10 2019
New Revision: 278976
URL: https://gcc.gnu.org/viewcvs?rev=278976&root=gcc&view=rev
Log:
Fix C handling of use of lvalues of incomplete types (PR c/36941, PR c/88827).
Bug 88827 points out that GCC should not be rejecting C code that
dereferences a pointer to an incomplete type in the case that uses &*
to take the address of the resulting lvalue, because no constraint is
violated in that case (other than for C90 when the incomplete type is
unqualified void, which we already handle correctly) and as the lvalue
never gets converted to an rvalue there is no undefined behavior
either.
This means that the diagnostic for such a dereference is bogus and
should be removed; if the lvalue gets converted to an rvalue, there
should be an appropriate error later for the use of the incomplete
type. In most cases, there is, but bug 36941 points out the lack of a
diagnostic when the incomplete (non-void) type gets cast to void
(where a diagnostic seems appropriate for this undefined behavior as a
matter of quality of implementation).
This patch removes the bogus diagnostic (and C_TYPE_ERROR_REPORTED
which was only used in the code that is removed - only that one, bogus
diagnostic had this duplicate suppression, not any of the other, more
legitimate diagnostics for use of incomplete types) and makes
convert_lvalue_to_rvalue call require_complete_type for arguments not
of void types, so that all relevant code paths (possibly except some
for ObjC) get incomplete types diagnosed. It's possible that this
makes some other checks for incomplete types obsolete, but no attempt
is made to remove any such checks.
Bootstrapped with no regressions for x86_64-pc-linux-gnu.
PR c/36941
PR c/88827
gcc/c:
* c-typeck.c (convert_lvalue_to_rvalue): Call
require_complete_type for arguments not of void types.
(build_indirect_ref): Do not diagnose dereferencing pointers to
incomplete types.
* c-tree.h (C_TYPE_ERROR_REPORTED): Remove.
gcc/testsuite:
* gcc.dg/lvalue-9.c, gcc.dg/lvalue-10.c: New tests.
* gcc.dg/array-8.c, gcc.dg/enum-incomplete-1.c,
gcc.dg/enum-incomplete-3.c, gcc.dg/noncompile/incomplete-3.c,
gcc.dg/pr48552-1.c, gcc.dg/pr48552-2.c, gcc.dg/pr63543.c,
gcc.dg/pr69796.c: Update expected diagnostics.
Added:
trunk/gcc/testsuite/gcc.dg/lvalue-10.c
trunk/gcc/testsuite/gcc.dg/lvalue-9.c
Modified:
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-tree.h
trunk/gcc/c/c-typeck.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/array-8.c
trunk/gcc/testsuite/gcc.dg/enum-incomplete-1.c
trunk/gcc/testsuite/gcc.dg/enum-incomplete-3.c
trunk/gcc/testsuite/gcc.dg/noncompile/incomplete-3.c
trunk/gcc/testsuite/gcc.dg/pr48552-1.c
trunk/gcc/testsuite/gcc.dg/pr48552-2.c
trunk/gcc/testsuite/gcc.dg/pr63543.c
trunk/gcc/testsuite/gcc.dg/pr69796.c
>From gcc-bugs-return-662362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:27:53 2019
Return-Path: <gcc-bugs-return-662362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93023 invoked by alias); 4 Dec 2019 23:27:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 92961 invoked by uid 48); 4 Dec 2019 23:27:48 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/36941] gcc does not reject invalid cast
Date: Wed, 04 Dec 2019 23:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-36941-4-zxmJynFc13@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-36941-4@http.gcc.gnu.org/bugzilla/>
References: <bug-36941-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00432.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36941
Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.0
--- Comment #10 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Fixed for GCC 10.
>From gcc-bugs-return-662364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:28:44 2019
Return-Path: <gcc-bugs-return-662364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99981 invoked by alias); 4 Dec 2019 23:28:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97708 invoked by uid 48); 4 Dec 2019 23:28:40 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/68159] Demangler crash (GDB PR 19190)
Date: Wed, 04 Dec 2019 23:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-68159-4-Esq7Hz0Svl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68159-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68159-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00434.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68159
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #16 from Christian Biesinger <cbiesinger at google dot com> ---
Looks like the answer is yes, based on my testing.
>From gcc-bugs-return-662363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:28:25 2019
Return-Path: <gcc-bugs-return-662363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96573 invoked by alias); 4 Dec 2019 23:28:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95787 invoked by uid 48); 4 Dec 2019 23:28:17 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88827] Rejects valid program using &* operator combination.
Date: Wed, 04 Dec 2019 23:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-88827-4-gWwwCxRUja@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88827-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88827-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00433.txt.bz2
Content-length: 492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88827
Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.0
--- Comment #2 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Fixed for GCC 10.
>From gcc-bugs-return-662365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:29:50 2019
Return-Path: <gcc-bugs-return-662365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15163 invoked by alias); 4 Dec 2019 23:29:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15114 invoked by uid 48); 4 Dec 2019 23:29:45 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/68159] Demangler crash (GDB PR 19190)
Date: Wed, 04 Dec 2019 23:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-68159-4-Z0IM6xIquT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68159-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68159-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00435.txt.bz2
Content-length: 245
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68159
--- Comment #17 from Christian Biesinger <cbiesinger at google dot com> ---
Sorry, rather, none of these testcases seem to crash anymore but the one from
comment 0 still does not demangle.
>From gcc-bugs-return-662366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:32:53 2019
Return-Path: <gcc-bugs-return-662366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25735 invoked by alias); 4 Dec 2019 23:32:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25681 invoked by uid 48); 4 Dec 2019 23:32:48 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/68700] demangler failed with signal 11
Date: Wed, 04 Dec 2019 23:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: 5.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-68700-4-xd3k9ZRB3c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68700-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68700-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00436.txt.bz2
Content-length: 485
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68700
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #3 from Christian Biesinger <cbiesinger at google dot com> ---
This does not seem to crash on binutils trunk, but it does not demangle either.
>From gcc-bugs-return-662367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:37:57 2019
Return-Path: <gcc-bugs-return-662367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32524 invoked by alias); 4 Dec 2019 23:37:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32271 invoked by uid 48); 4 Dec 2019 23:37:53 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/69094] erroneous demangling
Date: Wed, 04 Dec 2019 23:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-69094-4-PoIaJ39nND@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69094-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69094-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00437.txt.bz2
Content-length: 420
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69094
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #2 from Christian Biesinger <cbiesinger at google dot com> ---
Still happening.
>From gcc-bugs-return-662368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:40:33 2019
Return-Path: <gcc-bugs-return-662368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34639 invoked by alias); 4 Dec 2019 23:40:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34394 invoked by uid 48); 4 Dec 2019 23:40:28 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/82026] Undemanglable symbol
Date: Wed, 04 Dec 2019 23:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: 7.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-82026-4-VO0bcXfnJH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82026-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82026-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00438.txt.bz2
Content-length: 505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82026
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #2 from Christian Biesinger <cbiesinger at google dot com> ---
No longer crashes on binutils trunk, though it does crash 2.31.1. Trunk doesn't
demangle it, though
>From gcc-bugs-return-662369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:45:01 2019
Return-Path: <gcc-bugs-return-662369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44235 invoked by alias); 4 Dec 2019 23:45:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44160 invoked by uid 48); 4 Dec 2019 23:44:56 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/87241] A hang problem for c++filt
Date: Wed, 04 Dec 2019 23:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87241-4-DP1pXwcN6t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87241-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87241-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00439.txt.bz2
Content-length: 533
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87241
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #5 from Christian Biesinger <cbiesinger at google dot com> ---
This seems to be fixed on binutils trunk (in that it doesn't allocate lots of
memory and just returns early), but not in 2.31.1
>From gcc-bugs-return-662370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 04 23:46:34 2019
Return-Path: <gcc-bugs-return-662370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47672 invoked by alias); 4 Dec 2019 23:46:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47588 invoked by uid 48); 4 Dec 2019 23:46:28 -0000
From: "cbiesinger at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/83495] Segmentation Fault - 63915465
Date: Wed, 04 Dec 2019 23:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cbiesinger at google dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-83495-4-NGKfS7gWT3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83495-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83495-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00440.txt.bz2
Content-length: 569
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83495
Christian Biesinger <cbiesinger at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cbiesinger at google dot com
--- Comment #6 from Christian Biesinger <cbiesinger at google dot com> ---
The attachment contains a testcase: _ZZmmFoREES_
Current c++filt does not crash for me on that, but I don't know if it requires
a specific setup or this is fixed.
>From gcc-bugs-return-662371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 00:33:47 2019
Return-Path: <gcc-bugs-return-662371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94624 invoked by alias); 5 Dec 2019 00:33:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94594 invoked by uid 48); 5 Dec 2019 00:33:42 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92814] New: missing -Wstringop-overflow writing into a dynamically allocated flexible array member
Date: Thu, 05 Dec 2019 00:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00441.txt.bz2
Content-length: 1438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92814
Bug ID: 92814
Summary: missing -Wstringop-overflow writing into a dynamically
allocated flexible array member
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
With the first patch for pr91582 applied
(https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00652.html) and with
-Wno-array-bounds, GCC 10 issues -Wstringop-overflow for the buffer overflow in
g() but not in h(). Both should be diagnosed by -Wstringop-overflow.
$ cat t.c && gcc -O2 -S -Wall -Wno-array-bounds t.c
void f (void*);
struct S { int n; char ax[]; };
struct S s = { 3, { 1, 2, 3 } };
void g (void)
{
__builtin_strcpy (s.ax, "123"); // -Wstringop-overflow (good)
}
void h (void)
{
struct S *p = (struct S*)__builtin_malloc (sizeof *p + 3);
__builtin_strcpy (p->ax, "123"); // no warning (w/o -Warray-bounds)
f (p);
}
t.c: In function ‘g’:
t.c:9:3: warning: ‘__builtin_memcpy’ writing 4 bytes into a region of size 3
overflows the destination [-Wstringop-overflow=]
9 | __builtin_strcpy (s.ax, "123"); // -Wstringop-overflow (good)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>From gcc-bugs-return-662372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 00:51:30 2019
Return-Path: <gcc-bugs-return-662372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114829 invoked by alias); 5 Dec 2019 00:51:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114025 invoked by uid 48); 5 Dec 2019 00:51:25 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92815] New: spurious -Wstringop-overflow writing into a flexible array of an extern struct
Date: Thu, 05 Dec 2019 00:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00442.txt.bz2
Content-length: 1174
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92815
Bug ID: 92815
Summary: spurious -Wstringop-overflow writing into a flexible
array of an extern struct
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
Diagnosing the strcpy call below isn't justified because the flexible array
into which it writes is a member of an extern object that could be initialized
to be large enough to fit the string (e.g., as shown in the comment).
$ cat t.c && gcc -O2 -S -Wall -Wno-array-bounds t.c
extern struct S s /* = { 5, { 1, 2, 3, 4, 5 } } */;
void g (void)
{
__builtin_strcpy (s.ax, "123"); // bogus warning
}
t.c: In function ‘g’:
t.c:7:3: warning: ‘__builtin_memcpy’ writing 4 bytes into a region of size 0
overflows the destination [-Wstringop-overflow=]
7 | __builtin_strcpy (s.ax, "123"); // bogus warning
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>From gcc-bugs-return-662373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 00:54:04 2019
Return-Path: <gcc-bugs-return-662373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128180 invoked by alias); 5 Dec 2019 00:54:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128135 invoked by uid 48); 5 Dec 2019 00:53:58 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92815] [8/9/10 Regression] spurious -Wstringop-overflow writing into a flexible array of an extern struct
Date: Thu, 05 Dec 2019 00:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on blocked short_desc everconfirmed
Message-ID: <bug-92815-4-Kbhf6mzPXA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00443.txt.bz2
Content-length: 1717
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92815
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-05
Blocks| |88443
Summary|spurious |[8/9/10 Regression]
|-Wstringop-overflow writing |spurious
|into a flexible array of an |-Wstringop-overflow writing
|extern struct |into a flexible array of an
| |extern struct
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
The full test case is:
struct S { int n; char ax[]; };
extern struct S s /* = { 5, { 1, 2, 3, 4, 5 } } */;
void g (void)
{
__builtin_strcpy (s.ax, "123");
}
The false positive warning has been issued since r243419 (GCC 7.0):
r243419 | msebor | 2016-12-07 19:01:33 -0500 (Wed, 07 Dec 2016) | 68 lines
PR c/53562 - Add -Werror= support for -D_FORTIFY_SOURCE /
__builtin___memcpy_chk
PR middle-end/77784 - duplicate warning for snprintf when n > object size
PR middle-end/78149 - missing warning on strncpy buffer overflow due to an
excessive bound
PR middle-end/78138 - missing warnings on buffer overflow with non-constant
source length
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443
[Bug 88443] [meta-bug] bogus/missing -Wstringop-overflow warnings
>From gcc-bugs-return-662374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 00:58:22 2019
Return-Path: <gcc-bugs-return-662374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83908 invoked by alias); 5 Dec 2019 00:58:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83848 invoked by uid 48); 5 Dec 2019 00:58:16 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92815] [8/9/10 Regression] spurious -Wstringop-overflow writing into a flexible array of an extern struct
Date: Thu, 05 Dec 2019 00:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: blocked
Message-ID: <bug-92815-4-WVwBcOC7wb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00444.txt.bz2
Content-length: 1332
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92815
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |56456
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
With -Warray-bounds GCC issues:
t.c:7:3: warning: ‘__builtin_memcpy’ offset [4, 7] is out of the bounds [0, 4]
of object ‘s’ with type ‘struct S’ [-Warray-bounds]
7 | __builtin_strcpy (s.ax, "123");
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t.c:3:17: note: ‘s’ declared here
3 | extern struct S s /* = { 5, { 1, 2, 3, 4, 5 } } */;
| ^
The -Warray-bounds warning was in turn introduced in r255755 (in GCC 8.0):
r255755 | msebor | 2017-12-16 18:58:34 -0500 (Sat, 16 Dec 2017) | 81 lines
PR tree-optimization/78918 - missing -Wrestrict on memcpy copying over self
gcc/c-family/ChangeLog:
PR tree-optimization/78918
* c-common.c (check_function_restrict): Avoid checking built-ins.
* c.opt (-Wrestrict): Include in -Wall.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456
[Bug 56456] [meta-bug] bogus/missing -Warray-bounds
>From gcc-bugs-return-662375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 01:28:49 2019
Return-Path: <gcc-bugs-return-662375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114341 invoked by alias); 5 Dec 2019 01:28:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114302 invoked by uid 55); 5 Dec 2019 01:28:43 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91582] missing heap overflow detection for strcpy
Date: Thu, 05 Dec 2019 01:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91582-4-XNen1jnqgQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91582-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91582-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00445.txt.bz2
Content-length: 2278
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91582
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Thu Dec 5 01:28:11 2019
New Revision: 278983
URL: https://gcc.gnu.org/viewcvs?rev=278983&root=gcc&view=rev
Log:
PR middle-end/91582 - missing heap overflow detection for strcpy
gcc/ChangeLog:
PR middle-end/91582
* builtins.c (gimple_call_alloc_size): New function.
(compute_objsize): Add argument. Call gimple_call_alloc_size.
Handle variable offsets and indices.
* builtins.h (gimple_call_alloc_size): Declare.
(compute_objsize): Add argument.
* gcc/gimple-ssa-warn-restrict.c: Remove assertions.
* tree-ssa-strlen.c (handle_store): Handle calls to allocated objects.
gcc/testsuite/ChangeLog:
PR middle-end/91582
* c-c++-common/Wstringop-truncation.c: Remove xfails.
* g++.dg/warn/Wstringop-overflow-4.C: New test.
* g++.dg/ext/attr-alloc_size.C: Suppress -Warray-bounds.
* gcc.dg/Warray-bounds-56.c: New test.
* gcc.dg/Wstringop-overflow-22.c: New test.
* gcc.dg/attr-alloc_size.c: Suppress -Warray-bounds.
* gcc.dg/attr-copy-2.c: Same.
* gcc.dg/builtin-stringop-chk-5.c: Remove xfails.
* gcc.dg/builtin-stringop-chk-8.c: Same. Correct the text of expected
warnings.
* gcc.target/i386/pr82002-2a.c: Prune expected warning.
* gcc.target/i386/pr82002-2b.c: Same.
Added:
trunk/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C
trunk/gcc/testsuite/gcc.dg/Warray-bounds-56.c
trunk/gcc/testsuite/gcc.dg/Wstringop-overflow-25.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/builtins.c
trunk/gcc/builtins.h
trunk/gcc/gimple-ssa-warn-restrict.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/c-c++-common/Wstringop-truncation.c
trunk/gcc/testsuite/g++.dg/ext/attr-alloc_size.C
trunk/gcc/testsuite/gcc.dg/attr-alloc_size.c
trunk/gcc/testsuite/gcc.dg/attr-copy-2.c
trunk/gcc/testsuite/gcc.dg/builtin-stringop-chk-5.c
trunk/gcc/testsuite/gcc.dg/builtin-stringop-chk-8.c
trunk/gcc/testsuite/gcc.target/i386/pr82002-2a.c
trunk/gcc/testsuite/gcc.target/i386/pr82002-2b.c
trunk/gcc/tree-ssa-strlen.c
>From gcc-bugs-return-662376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 01:39:53 2019
Return-Path: <gcc-bugs-return-662376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124298 invoked by alias); 5 Dec 2019 01:39:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124244 invoked by uid 48); 5 Dec 2019 01:39:49 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91582] missing heap overflow detection for strcpy
Date: Thu, 05 Dec 2019 01:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91582-4-ZqXXlxojj7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91582-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91582-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00446.txt.bz2
Content-length: 348
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91582
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Part 2 of the patch series was committed in r278983. Part 1 and part 3 are
still waiting for review and approval:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00429.html
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02340.html
>From gcc-bugs-return-662377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 06:02:32 2019
Return-Path: <gcc-bugs-return-662377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34882 invoked by alias); 5 Dec 2019 06:02:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34352 invoked by uid 48); 5 Dec 2019 06:02:27 -0000
From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/39751] ICE in cp_lexer_new_from_tokens, at cp/parser.c:342
Date: Thu, 05 Dec 2019 06:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.5.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: dimhen at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-39751-4-Cw1aemdi5P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-39751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-39751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00447.txt.bz2
Content-length: 2550
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39751
--- Comment #11 from Dmitry G. Dyachenko <dimhen at gmail dot com> ---
Original test case from c#0 crash in trunk
gcc version 10.0.0 20191204 (experimental) [trunk revision 278972] (GCC)
$ g++ -fpreprocessed -fsyntax-only a.ii
a.ii:5:1: error: types may not be defined in template arguments
5 | {
| ^
a.ii:6:1: error: ISO C++ forbids declaration of ‘f’ with no type [-fpermissive]
6 | f () :
| ^
a.ii:6:6: error: expected ‘}’ at end of input
6 | f () :
| ^
a.ii:5:1: note: to match this ‘{’
5 | {
| ^
a.ii:6:6: error: expected template-argument at end of input
6 | f () :
| ^
a.ii:6:6: error: expected ‘>’ at end of input
a.ii:4:1: error: expected unqualified-id at end of input
4 | A < struct
| ^~~~~~~~~~
5 | {
| ~
6 | f () :
| ~~~~~~
a.ii:4:1: error: expected ‘}’ at end of input
a.ii:3:1: note: to match this ‘{’
3 | {
| ^
a.ii:4:1: internal compiler error: in cp_lexer_new_from_tokens, at
cp/parser.c:698
4 | A < struct
| ^~~~~~~~~~
5 | {
| ~
6 | f () :
| ~~~~~~
0x6541ef cp_parser_push_lexer_for_tokens
/home/dimhen/src/gcc_current/gcc/cp/parser.c:698
0xbb3005 cp_parser_late_parsing_for_member
/home/dimhen/src/gcc_current/gcc/cp/parser.c:29559
0xb91ee7 cp_parser_class_specifier_1
/home/dimhen/src/gcc_current/gcc/cp/parser.c:23942
0xb92e83 cp_parser_class_specifier
/home/dimhen/src/gcc_current/gcc/cp/parser.c:23966
0xb92e83 cp_parser_type_specifier
/home/dimhen/src/gcc_current/gcc/cp/parser.c:17576
0xb93f0f cp_parser_decl_specifier_seq
/home/dimhen/src/gcc_current/gcc/cp/parser.c:14249
0xbb95a5 cp_parser_single_declaration
/home/dimhen/src/gcc_current/gcc/cp/parser.c:29075
0xbb992b cp_parser_template_declaration_after_parameters
/home/dimhen/src/gcc_current/gcc/cp/parser.c:28738
0xbba080 cp_parser_explicit_template_declaration
/home/dimhen/src/gcc_current/gcc/cp/parser.c:29004
0xbbd3e9 cp_parser_declaration
/home/dimhen/src/gcc_current/gcc/cp/parser.c:13271
0xbbda0a cp_parser_translation_unit
/home/dimhen/src/gcc_current/gcc/cp/parser.c:4721
0xbbda0a c_parse_file()
/home/dimhen/src/gcc_current/gcc/cp/parser.c:43048
0xccf60b c_common_parse_file()
/home/dimhen/src/gcc_current/gcc/c-family/c-opts.c:1185
Please submit a full bug report,
>From gcc-bugs-return-662378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 07:25:08 2019
Return-Path: <gcc-bugs-return-662378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75312 invoked by alias); 5 Dec 2019 07:25:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75073 invoked by uid 48); 5 Dec 2019 07:25:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92799] ICE: in get, at cgraph.h:1339
Date: Thu, 05 Dec 2019 07:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc component
Message-ID: <bug-92799-4-jSfB13hHVP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00448.txt.bz2
Content-length: 637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92799
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
CC| |hubicka at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
Component|c |ipa
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Not sure if maybe invalid but then we should reject it.
>From gcc-bugs-return-662379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 07:27:32 2019
Return-Path: <gcc-bugs-return-662379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77586 invoked by alias); 5 Dec 2019 07:27:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77520 invoked by uid 48); 5 Dec 2019 07:27:27 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92800] IPA escape analysis for structs
Date: Thu, 05 Dec 2019 07:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92800-4-2rjtgz4XUF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92800-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92800-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00449.txt.bz2
Content-length: 277
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92800
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note there's people from Marvell working on the same thing, posting design docs
(some privately to me though). goblock@marvell.com was working on this.
>From gcc-bugs-return-662380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 07:29:09 2019
Return-Path: <gcc-bugs-return-662380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80562 invoked by alias); 5 Dec 2019 07:29:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79189 invoked by uid 48); 5 Dec 2019 07:29:04 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92801] Drop unused struct fields
Date: Thu, 05 Dec 2019 07:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92801-4-I1GuzQIvPO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00450.txt.bz2
Content-length: 350
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92801
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
You're repeating mistakes fromm the past. The "dumb" approach works for a
single
benchmark (mcf) but isn't at all usable for anything in the real world which
means it is of no use for GCC (when factoring in maintainance cost).
>From gcc-bugs-return-662381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 07:32:01 2019
Return-Path: <gcc-bugs-return-662381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83876 invoked by alias); 5 Dec 2019 07:32:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83746 invoked by uid 48); 5 Dec 2019 07:31:56 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Thu, 05 Dec 2019 07:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92803-4-Y8C1Z2TPAc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00451.txt.bz2
Content-length: 184
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Hmm, I don't think it is fully correct. Let me dig in a bit.
>From gcc-bugs-return-662382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 07:44:41 2019
Return-Path: <gcc-bugs-return-662382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101177 invoked by alias); 5 Dec 2019 07:44:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100550 invoked by uid 48); 5 Dec 2019 07:44:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Thu, 05 Dec 2019 07:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-92803-4-ln3hyXVp8E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00452.txt.bz2
Content-length: 492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|jakub at gcc dot gnu.org |rguenth at gcc dot gnu.org
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Will ICE
v4sf
bar (v4si x, float *p)
{
return (v4sf) { x[0], x[1], x[2], *p };
}
testing fix.
>From gcc-bugs-return-662383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 07:50:29 2019
Return-Path: <gcc-bugs-return-662383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106864 invoked by alias); 5 Dec 2019 07:50:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106707 invoked by uid 48); 5 Dec 2019 07:50:18 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Thu, 05 Dec 2019 07:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92803-4-Nc07sPmOSl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00453.txt.bz2
Content-length: 1569
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #4)
> Though, there is another issue, for the nelts 2 vectors
> simplify_vector_constructor created code is actually larger than old code.
> And, it might be beneficial if we one day implement clang-like
> __builtin_shufflevector or at least add to VEC_PERM_EXPR or something
> similar the possibility to say certain element is a don't care (for
> __builtin_shufflevector I think that is -1 or negative?), as e.g. on
> AVX/AVX2 when extracting 128-bit vector out of 256-bit permutation all the
> upper elements are don't care and we might get better code if the backend
> picks the best element indexes for those to get smallest/fastest permutation.
Using -1 as the don't care element also occured to me. Should be easy
to change for the vec_perm_const hook/expander I guess.
Not sure about VEC_PERM_EXPR given it also allows non-constant permutation
vectors. I thought about relaxing VEC_PERM_EXPR to support extract
(destination with less lanes than source(s)) and concat (destination with
more lanes than source(s)). Plus eventually allowing sources and destinations
to be scalars (interpret as punned to 1-element vector), which would be
syntactic sugar given explicit punning would be possible. It would be
nice to not expose that to the targets given that explodes the complexity
of vec_perm[_const] though.
Anyway, this isn't something for GCC 10, but yes, don't know would come in
handy.
>From gcc-bugs-return-662384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 08:13:49 2019
Return-Path: <gcc-bugs-return-662384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3406 invoked by alias); 5 Dec 2019 08:13:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3284 invoked by uid 48); 5 Dec 2019 08:13:44 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92773] [8/9/10 Regression] GCC compilation with big array / header is infinite
Date: Thu, 05 Dec 2019 08:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: compile-time-hog, diagnostic, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status target_milestone short_desc cf_known_to_fail
Message-ID: <bug-92773-4-UoZexzEP2k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00454.txt.bz2
Content-length: 1350
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92773
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|WAITING |NEW
Target Milestone|--- |8.4
Summary|GCC compilation with big |[8/9/10 Regression] GCC
|array / header is infinite |compilation with big array
| |/ header is infinite
Known to fail| |7.5.0
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. It's -Wmissing-braces causing the endless compilation. I see
'....' printed over and over and garbling the terminal.
sound/soc/codecs/tas5756m_hf3_cfg.h:5:38: warning: missing braces around
initializer [-Wmissing-braces]
......
......
......
......
......
......
......
......
......
......
sound/soc/codecs/tas5756m_hf3_cfg.h:5:38: warning: missing braces around
initializer [-Wmissing-braces]
......
......
......
......
......
......
The preprocessed source isn't liked by GCC 5 or 6 but since you say GCC 5
works fine for you it is a regression (likely -Wmissing-braces is "new").
>From gcc-bugs-return-662385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 08:20:41 2019
Return-Path: <gcc-bugs-return-662385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19348 invoked by alias); 5 Dec 2019 08:20:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19297 invoked by uid 48); 5 Dec 2019 08:20:36 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92773] [8/9/10 Regression] GCC compilation with big array / header is infinite
Date: Thu, 05 Dec 2019 08:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: compile-time-hog, diagnostic, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92773-4-JvnNiy95X8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00455.txt.bz2
Content-length: 749
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92773
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Smaller testcase:
typedef unsigned char cfg_u8;
typedef union {
struct {
cfg_u8 offset;
cfg_u8 value;
};
struct {
cfg_u8 command;
cfg_u8 param;
};
} cfg_reg;
#define FOO { 0x00, 0x00 },
#define FOO1 FOO FOO FOO FOO FOO FOO FOO FOO FOO
#define FOO2 FOO1 FOO1 FOO1 FOO1 FOO1 FOO1 FOO1 FOO1
cfg_reg tas5756m_init_hf3[] = { FOO2 };
now repeat more initializers (the original testcase has plenty).
I'd say the warning should be rate-limited somehow or simply only warn
once per array element type, not for reach element initialized. In this
case the warning is even questionable since the structs are anonymous?
>From gcc-bugs-return-662386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 08:25:04 2019
Return-Path: <gcc-bugs-return-662386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48540 invoked by alias); 5 Dec 2019 08:24:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48367 invoked by uid 48); 5 Dec 2019 08:24:25 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92804] [10 Regression] ICE trying to use concept as a nested-name-specifier
Date: Thu, 05 Dec 2019 08:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-92804-4-EkOZbVnQb3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92804-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92804-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00456.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92804
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-662387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 08:25:23 2019
Return-Path: <gcc-bugs-return-662387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49243 invoked by alias); 5 Dec 2019 08:25:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48845 invoked by uid 48); 5 Dec 2019 08:25:02 -0000
From: "rick at snowlight dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/67733] illumos needs a new target triple
Date: Thu, 05 Dec 2019 08:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rick at snowlight dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-67733-4-wQnTauXOUL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00457.txt.bz2
Content-length: 767
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67733
rick at snowlight dot net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rick at snowlight dot net
--- Comment #6 from rick at snowlight dot net ---
I want to counter with the assertion that this may well be a
distribution-specific matter, for changing the user and dev enviroment in that
way (removing legacy AT&T System 5 symlinks) seems largely gratuitous. Sure, go
talk to the GNU Build System maintainers about a *-sun-dilos2.11 target
definition, but generally illumos is still largely compatible with Solaris at
the source and user/dev environment level.
>From gcc-bugs-return-662388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 08:29:02 2019
Return-Path: <gcc-bugs-return-662388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63040 invoked by alias); 5 Dec 2019 08:29:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62931 invoked by uid 48); 5 Dec 2019 08:28:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Thu, 05 Dec 2019 08:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92803-4-tvesUMJg7y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00458.txt.bz2
Content-length: 334
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 47425
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47425&action=edit
my patch
testing this, the testcases optimization check likely requires some other
prerequestite from my tree.
>From gcc-bugs-return-662389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 08:37:42 2019
Return-Path: <gcc-bugs-return-662389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70117 invoked by alias); 5 Dec 2019 08:37:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70068 invoked by uid 48); 5 Dec 2019 08:37:37 -0000
From: "tim.ruehsen at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/92453] write buffer overflow in cplus_demangle()
Date: Thu, 05 Dec 2019 08:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tim.ruehsen at gmx dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92453-4-NHHNFgUQC8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92453-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92453-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00459.txt.bz2
Content-length: 355
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92453
--- Comment #3 from Tim Ruehsen <tim.ruehsen at gmx dot de> ---
(In reply to Christian Biesinger from comment #2)
> Could you send your patch to gcc-patches per
> https://gcc.gnu.org/contribute.html#patches ? Thanks!
I did that some days ago:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02682.html
>From gcc-bugs-return-662390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 08:44:30 2019
Return-Path: <gcc-bugs-return-662390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77605 invoked by alias); 5 Dec 2019 08:44:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77527 invoked by uid 48); 5 Dec 2019 08:44:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Thu, 05 Dec 2019 08:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92803-4-TCuT0DecWU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00460.txt.bz2
Content-length: 1380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Another testcase to consider (-O2 -mavx2):
typedef double v4df __attribute__((vector_size (32)));
typedef double v2df __attribute__((vector_size (16)));
typedef short v16hi __attribute__((vector_size (32)));
typedef short v8hi __attribute__((vector_size (16)));
v2df
foo (v4df x, double *p)
{
return (v2df) { x[1], *p };
}
v2df
bar (v4df x, double *p)
{
return (v2df) { x[0], *p };
}
v2df
baz (v2df x, double *p)
{
return (v2df) { x[1], *p };
}
v2df
qux (v2df x, double *p)
{
return (v2df) { x[0], *p };
}
Comparing gcc-9 with trunk + my patch, the differences are:
foo:
- vunpckhpd %xmm0, %xmm0, %xmm0
- vmovhpd (%rdi), %xmm0, %xmm0
+ vbroadcastsd (%rdi), %ymm1
+ vinsertf128 $1, %xmm1, %ymm0, %ymm0
+ vpermpd $77, %ymm0, %ymm0
bar:
- vmovhpd (%rdi), %xmm0, %xmm0
+ vbroadcastsd (%rdi), %ymm1
+ vinsertf128 $1, %xmm1, %ymm0, %ymm0
+ vpermpd $76, %ymm0, %ymm0
baz:
- vunpckhpd %xmm0, %xmm0, %xmm0
- vmovhpd (%rdi), %xmm0, %xmm0
+ vmovddup (%rdi), %xmm1
+ vunpckhpd %xmm1, %xmm0, %xmm0
qux:
- vmovhpd (%rdi), %xmm0, %xmm0
+ vmovapd %xmm0, %xmm1
+ vmovddup (%rdi), %xmm0
+ vmovsd %xmm1, %xmm0, %xmm0
>From gcc-bugs-return-662391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:01:06 2019
Return-Path: <gcc-bugs-return-662391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117244 invoked by alias); 5 Dec 2019 09:00:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116888 invoked by uid 48); 5 Dec 2019 09:00:37 -0000
From: "tim.ruehsen at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/92797] cplus_demangle() produces huge amount of output (on trunk)
Date: Thu, 05 Dec 2019 09:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tim.ruehsen at gmx dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92797-4-F4szjwYhlT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00461.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92797
--- Comment #3 from Tim Ruehsen <tim.ruehsen at gmx dot de> ---
(In reply to Andrew Pinski from comment #2)
> (In reply to Tim Ruehsen from comment #1)
> > BTW, llvm-cxxfilt does not show this behavior.
>
> Could it because it does not implement the D demangler?
Good point, that seems to be the reason. So please ignore my previous comment.
>From gcc-bugs-return-662392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:04:11 2019
Return-Path: <gcc-bugs-return-662392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122575 invoked by alias); 5 Dec 2019 09:04:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122500 invoked by uid 55); 5 Dec 2019 09:04:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92781] ICE in convert_nonlocal_reference_op, at tree-nested.c:1065
Date: Thu, 05 Dec 2019 09:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92781-4-5plPUKo5qR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92781-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92781-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00462.txt.bz2
Content-length: 720
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92781
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Dec 5 09:03:34 2019
New Revision: 278988
URL: https://gcc.gnu.org/viewcvs?rev=278988&root=gcc&view=rev
Log:
PR fortran/92781
* trans-decl.c (gfc_get_symbol_decl): If sym->backend_decl is
current_function_decl, add length to current rather than parent
function and expect DECL_CONTEXT (length) to be current_function_decl.
* gfortran.dg/pr92781.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/pr92781.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-decl.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:05:02 2019
Return-Path: <gcc-bugs-return-662393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125816 invoked by alias); 5 Dec 2019 09:05:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125713 invoked by uid 55); 5 Dec 2019 09:04:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92791] [10 Regression] ICE in extract_insn, at recog.c:2311 since r278645
Date: Thu, 05 Dec 2019 09:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92791-4-zCMl17xm3D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00463.txt.bz2
Content-length: 544
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92791
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Dec 5 09:04:24 2019
New Revision: 278989
URL: https://gcc.gnu.org/viewcvs?rev=278989&root=gcc&view=rev
Log:
PR target/92791
* config/i386/i386.md (movstrict<mode>): Move test for
TARGET_PARTIAL_REG_STALL and not optimizing for size from
expander's condition to the body - FAIL; in that case.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.md
>From gcc-bugs-return-662395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:09:40 2019
Return-Path: <gcc-bugs-return-662395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1418 invoked by alias); 5 Dec 2019 09:09:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1297 invoked by uid 48); 5 Dec 2019 09:09:34 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/91971] Profile directory concatenated with object file path
Date: Thu, 05 Dec 2019 09:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91971-4-dNwMycy1Hs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00465.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91971
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed again.
>From gcc-bugs-return-662394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:09:28 2019
Return-Path: <gcc-bugs-return-662394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 599 invoked by alias); 5 Dec 2019 09:09:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 456 invoked by uid 55); 5 Dec 2019 09:09:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/91971] Profile directory concatenated with object file path
Date: Thu, 05 Dec 2019 09:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91971-4-QEuZjFxD2S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00464.txt.bz2
Content-length: 542
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91971
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Thu Dec 5 09:08:44 2019
New Revision: 278990
URL: https://gcc.gnu.org/viewcvs?rev=278990&root=gcc&view=rev
Log:
Fix profile name files without -fprofile-dir.
2019-12-05 Martin Liska <mliska@suse.cz>
PR gcov-profile/91971
* coverage.c (coverage_init): Mangle full path
only when -fprofile-dir is used.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/coverage.c
>From gcc-bugs-return-662396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:44:05 2019
Return-Path: <gcc-bugs-return-662396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54407 invoked by alias); 5 Dec 2019 09:44:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54240 invoked by uid 48); 5 Dec 2019 09:44:00 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92816] New: [10 Regression] 35% performance drop for 433.milc with -O2 -flto on znver1 since r278879
Date: Thu, 05 Dec 2019 09:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92816-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00466.txt.bz2
Content-length: 743
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92816
Bug ID: 92816
Summary: [10 Regression] 35% performance drop for 433.milc with
-O2 -flto on znver1 since r278879
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org, marxin at gcc dot gnu.org
Target Milestone: ---
One can see that here:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=233.70.0
and also here (znver2):
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=292.70.0
>From gcc-bugs-return-662397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:46:01 2019
Return-Path: <gcc-bugs-return-662397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60295 invoked by alias); 5 Dec 2019 09:45:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57881 invoked by uid 48); 5 Dec 2019 09:45:27 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92816] [10 Regression] 35% performance drop for 433.milc with -O2 -flto on znver1 since r278879
Date: Thu, 05 Dec 2019 09:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work blocked target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92816-4-v5YeKDVLsu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92816-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92816-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00467.txt.bz2
Content-length: 774
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92816
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-05
Known to work| |9.2.0
Blocks| |26163
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
[Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
>From gcc-bugs-return-662399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:46:37 2019
Return-Path: <gcc-bugs-return-662399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62194 invoked by alias); 5 Dec 2019 09:46:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61635 invoked by uid 48); 5 Dec 2019 09:46:32 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92816] [10 Regression] 35% performance drop for 433.milc with -O2 -flto on znver1 since r278879
Date: Thu, 05 Dec 2019 09:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92816-4-t9VLUhyEei@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92816-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92816-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00469.txt.bz2
Content-length: 227
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92816
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
-march=skylake seems unaffected:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=227.70.0
>From gcc-bugs-return-662398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:46:32 2019
Return-Path: <gcc-bugs-return-662398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61290 invoked by alias); 5 Dec 2019 09:46:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60609 invoked by uid 48); 5 Dec 2019 09:46:05 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Thu, 05 Dec 2019 09:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92803-4-zZ4bGqSHBi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00468.txt.bz2
Content-length: 484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
Let's handle non-optimal code-gen in a separate bug.
>From gcc-bugs-return-662400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:46:47 2019
Return-Path: <gcc-bugs-return-662400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63088 invoked by alias); 5 Dec 2019 09:46:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62761 invoked by uid 55); 5 Dec 2019 09:46:41 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since r278764
Date: Thu, 05 Dec 2019 09:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92803-4-PFurbEUTh4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00470.txt.bz2
Content-length: 665
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Thu Dec 5 09:45:46 2019
New Revision: 278991
URL: https://gcc.gnu.org/viewcvs?rev=278991&root=gcc&view=rev
Log:
2019-12-05 Richard Biener <rguenther@suse.de>
PR tree-optimization/92803
* tree-ssa-forwprop.c (simplify_vector_constructor): Fix
invariant vector construction.
* gcc.target/i386/pr92803.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr92803.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-forwprop.c
>From gcc-bugs-return-662401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:47:49 2019
Return-Path: <gcc-bugs-return-662401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92489 invoked by alias); 5 Dec 2019 09:47:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86387 invoked by uid 48); 5 Dec 2019 09:47:45 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92809] [10 regression] error: calls_comdat_local is set outside of a comdat group
Date: Thu, 05 Dec 2019 09:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc target_milestone
Message-ID: <bug-92809-4-qvLzcKUHvb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92809-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92809-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00471.txt.bz2
Content-length: 370
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92809
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
Target Milestone|--- |10.0
>From gcc-bugs-return-662402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:49:31 2019
Return-Path: <gcc-bugs-return-662402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1766 invoked by alias); 5 Dec 2019 09:48:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1440 invoked by uid 55); 5 Dec 2019 09:48:23 -0000
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92055] [avr] Support 64-bit double
Date: Thu, 05 Dec 2019 09:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: gjl at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: gjl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92055-4-FRPbSlMeNf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92055-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92055-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00472.txt.bz2
Content-length: 441
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92055
--- Comment #12 from Georg-Johann Lay <gjl at gcc dot gnu.org> ---
Author: gjl
Date: Thu Dec 5 09:47:35 2019
New Revision: 278992
URL: https://gcc.gnu.org/viewcvs?rev=278992&root=gcc&view=rev
Log:
PR target/92055
* config/avr/t-avrlibc (MULTISUBDIR): Search for double, not double64.
Modified:
trunk/libgcc/ChangeLog
trunk/libgcc/config/avr/t-avrlibc
>From gcc-bugs-return-662403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:50:14 2019
Return-Path: <gcc-bugs-return-662403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4019 invoked by alias); 5 Dec 2019 09:50:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3947 invoked by uid 48); 5 Dec 2019 09:50:07 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92815] [8/9/10 Regression] spurious -Wstringop-overflow writing into a flexible array of an extern struct
Date: Thu, 05 Dec 2019 09:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-92815-4-cqqbVTxJLp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00473.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92815
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.4
>From gcc-bugs-return-662404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:51:29 2019
Return-Path: <gcc-bugs-return-662404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5484 invoked by alias); 5 Dec 2019 09:51:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5407 invoked by uid 48); 5 Dec 2019 09:51:20 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/92674] [8/9 Regression] ICE in gimple_phi_arg, at gimple.h:4406 since r240291
Date: Thu, 05 Dec 2019 09:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work short_desc cf_known_to_fail
Message-ID: <bug-92674-4-jBZpngSIuf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92674-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92674-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00474.txt.bz2
Content-length: 653
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92674
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |10.0
Summary|[8/9/10 Regression] ICE in |[8/9 Regression] ICE in
|gimple_phi_arg, at |gimple_phi_arg, at
|gimple.h:4406 since r240291 |gimple.h:4406 since r240291
Known to fail|10.0 |
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk sofar.
>From gcc-bugs-return-662405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:51:40 2019
Return-Path: <gcc-bugs-return-662405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6359 invoked by alias); 5 Dec 2019 09:51:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6220 invoked by uid 48); 5 Dec 2019 09:51:35 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/92674] [8/9 Regression] ICE in gimple_phi_arg, at gimple.h:4406 since r240291
Date: Thu, 05 Dec 2019 09:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-92674-4-GV3QQTPViO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92674-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92674-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00475.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92674
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|10.0 |8.4
>From gcc-bugs-return-662406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 09:56:38 2019
Return-Path: <gcc-bugs-return-662406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13744 invoked by alias); 5 Dec 2019 09:56:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13687 invoked by uid 48); 5 Dec 2019 09:56:33 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92809] [10 regression] error: calls_comdat_local is set outside of a comdat group
Date: Thu, 05 Dec 2019 09:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work assigned_to everconfirmed cf_known_to_fail
Message-ID: <bug-92809-4-couBTo0tJY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92809-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92809-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00476.txt.bz2
Content-length: 698
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92809
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-05
Known to work| |9.2.0
Assignee|unassigned at gcc dot gnu.org |hubicka at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |10.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r278944.
>From gcc-bugs-return-662407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 10:13:07 2019
Return-Path: <gcc-bugs-return-662407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65062 invoked by alias); 5 Dec 2019 10:13:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64992 invoked by uid 48); 5 Dec 2019 10:13:02 -0000
From: "pageexec at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/92817] New: the prototype of the built-in __gcov_exit function is wrong
Date: Thu, 05 Dec 2019 10:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pageexec at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00477.txt.bz2
Content-length: 1101
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92817
Bug ID: 92817
Summary: the prototype of the built-in __gcov_exit function is
wrong
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: gcov-profile
Assignee: unassigned at gcc dot gnu.org
Reporter: pageexec at gmail dot com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
git commit db46bcd377f4b4a26b9807a7cb3565a161178660 (since gcc 7) introduced
the callout to "void __gcov_exit(void)" however its construction looks like
this:
build_gcov_exit_decl (void)
{
tree init_fn = build_function_type_list (void_type_node, void_type_node,
NULL);
instead it should be this:
build_gcov_exit_decl (void)
{
tree init_fn = build_function_type_list (void_type_node, NULL);
as it is, the builtin-in prototype does not match what one would define in
source code and this trips up type based control-flow integrity checks.
>From gcc-bugs-return-662408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 10:14:33 2019
Return-Path: <gcc-bugs-return-662408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68006 invoked by alias); 5 Dec 2019 10:14:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67915 invoked by uid 48); 5 Dec 2019 10:14:22 -0000
From: "frederik at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92809] [10 regression] error: calls_comdat_local is set outside of a comdat group
Date: Thu, 05 Dec 2019 10:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frederik at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92809-4-ahHCcTcImH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92809-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92809-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00478.txt.bz2
Content-length: 490
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92809
Frederik Harwath <frederik at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |frederik at gcc dot gnu.org
--- Comment #2 from Frederik Harwath <frederik at gcc dot gnu.org> ---
We see the same error with the same backtrace when compiling
g++.dg/torture/pr59226.C for amdgcn.
>From gcc-bugs-return-662409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 10:18:57 2019
Return-Path: <gcc-bugs-return-662409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74166 invoked by alias); 5 Dec 2019 10:18:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74130 invoked by uid 48); 5 Dec 2019 10:18:53 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/92817] the prototype of the built-in __gcov_exit function is wrong
Date: Thu, 05 Dec 2019 10:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed
Message-ID: <bug-92817-4-79DTmUeyvJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92817-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00479.txt.bz2
Content-length: 658
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92817
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-05
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Let me fix it. Thanks for the report.
>From gcc-bugs-return-662410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 10:50:26 2019
Return-Path: <gcc-bugs-return-662410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26927 invoked by alias); 5 Dec 2019 10:50:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26885 invoked by uid 48); 5 Dec 2019 10:50:21 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92799] ICE: in get, at cgraph.h:1339
Date: Thu, 05 Dec 2019 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed
Message-ID: <bug-92799-4-vhIlDnFkLP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00480.txt.bz2
Content-length: 639
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92799
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-05
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
I can take a look.
>From gcc-bugs-return-662411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 11:04:34 2019
Return-Path: <gcc-bugs-return-662411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50888 invoked by alias); 5 Dec 2019 11:04:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50824 invoked by uid 48); 5 Dec 2019 11:04:30 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92775] [8/9/10 Regression] Incorrect expression in DW_AT_byte_stride on an array
Date: Thu, 05 Dec 2019 11:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92775-4-UcBoUkOVcb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00481.txt.bz2
Content-length: 961
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92775
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47426
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47426&action=edit
gcc10-pr92775.patch
Untested fix. Unfortunately, this regresses debug info size a little bit for
the common case where we know the span field in the descriptor is constant
equal to TYPE_SIZE_UNIT (etype), previously we used at least for sizes 1 to 31
DW_OP_litN, which is 1 byte long, and now we need to use 4 bytes -
DW_OP_push_object_address, DW_OP_plus_uconst, 32 (or 20 for ilp32),
DW_OP_deref.
It would be helpful if TYPE_LANG_SPECIFIC could contain some flag whether the
span field needs to be used or not, like in the past one could test
GFC_TYPE_ARRAY_SPAN (type) != NULL_TREE. If the FE provides something, the
debug hook can be adjusted to use the base->span only if really needed and
TYPE_SIZE_UNIT (etype) otherwise.
>From gcc-bugs-return-662413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 11:08:34 2019
Return-Path: <gcc-bugs-return-662413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55407 invoked by alias); 5 Dec 2019 11:08:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55306 invoked by uid 48); 5 Dec 2019 11:08:30 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92818] Typo in vec_perm -> bit_insert pattern
Date: Thu, 05 Dec 2019 11:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-92818-4-Nt4TNKXjXF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00483.txt.bz2
Content-length: 699
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92818
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization,
| |wrong-code
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-05
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-662412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 11:08:10 2019
Return-Path: <gcc-bugs-return-662412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54478 invoked by alias); 5 Dec 2019 11:08:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54409 invoked by uid 48); 5 Dec 2019 11:08:05 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92818] New: Typo in vec_perm -> bit_insert pattern
Date: Thu, 05 Dec 2019 11:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00482.txt.bz2
Content-length: 1204
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92818
Bug ID: 92818
Summary: Typo in vec_perm -> bit_insert pattern
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
Index: gcc/match.pd
===================================================================
--- gcc/match.pd (revision 278992)
+++ gcc/match.pd (working copy)
@@ -6049,7 +6049,7 @@ (define_operator_list COND_TERNARY
break;
if (at < encoded_nelts && sel.series_p (at + 1, 1, at + 1, 1))
{
- if (known_lt (at, nelts))
+ if (known_lt (poly_uint64 (sel[at]), nelts))
ins = fold_read_from_vector (cop0, sel[at]);
else
ins = fold_read_from_vector (cop1, sel[at] - nelts);
>From gcc-bugs-return-662415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 11:13:55 2019
Return-Path: <gcc-bugs-return-662415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64302 invoked by alias); 5 Dec 2019 11:13:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64233 invoked by uid 48); 5 Dec 2019 11:13:51 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92819] [10 Regression] Worse code generated on avx2 due to simplify_vector_constructor
Date: Thu, 05 Dec 2019 11:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on target_milestone everconfirmed
Message-ID: <bug-92819-4-f6HzGfWr99@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00485.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92819
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-05
Target Milestone|--- |10.0
Ever confirmed|0 |1
>From gcc-bugs-return-662414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 11:13:41 2019
Return-Path: <gcc-bugs-return-662414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62600 invoked by alias); 5 Dec 2019 11:13:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61752 invoked by uid 48); 5 Dec 2019 11:13:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92819] New: [10 Regression] Worse code generated on avx2 due to simplify_vector_constructor
Date: Thu, 05 Dec 2019 11:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc dependson target_milestone cf_gcchost
Message-ID: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00484.txt.bz2
Content-length: 3326
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92819
Bug ID: 92819
Summary: [10 Regression] Worse code generated on avx2 due to
simplify_vector_constructor
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
CC: asolokha at gmx dot com, jakub at gcc dot gnu.org,
marxin at gcc dot gnu.org, rguenth at gcc dot gnu.org
Depends on: 92803
Target Milestone: ---
Host: x86_64-linux-gnu
+++ This bug was initially created as a clone of Bug #92803 +++
For
/* { dg-do compile } */
/* { dg-options "-O2 -mavx2" } */
typedef double v4df __attribute__((vector_size (32)));
typedef double v2df __attribute__((vector_size (16)));
typedef short v16hi __attribute__((vector_size (32)));
typedef short v8hi __attribute__((vector_size (16)));
v2df
foo (v4df x, double *p)
{
return (v2df) { x[1], *p };
}
v2df
bar (v4df x, double *p)
{
return (v2df) { x[0], *p };
}
v2df
baz (v2df x, double *p)
{
return (v2df) { x[1], *p };
}
v2df
qux (v2df x, double *p)
{
return (v2df) { x[0], *p };
}
v2df
corge (v4df x, double *p, v2df y)
{
return (v2df) { x[3], *p };
}
generated code differences of gcc 9 and current trunk are:
@@ -6,8 +6,9 @@
foo:
.LFB0:
.cfi_startproc
- vunpckhpd %xmm0, %xmm0, %xmm0
- vmovhpd (%rdi), %xmm0, %xmm0
+ vbroadcastsd (%rdi), %ymm1
+ vinsertf128 $1, %xmm1, %ymm0, %ymm0
+ vpermpd $77, %ymm0, %ymm0
ret
.cfi_endproc
.LFE0:
@@ -18,7 +19,9 @@ foo:
bar:
.LFB1:
.cfi_startproc
- vmovhpd (%rdi), %xmm0, %xmm0
+ vbroadcastsd (%rdi), %ymm1
+ vinsertf128 $1, %xmm1, %ymm0, %ymm0
+ vpermpd $76, %ymm0, %ymm0
ret
.cfi_endproc
.LFE1:
@@ -29,8 +32,8 @@ bar:
baz:
.LFB2:
.cfi_startproc
- vunpckhpd %xmm0, %xmm0, %xmm0
- vmovhpd (%rdi), %xmm0, %xmm0
+ vmovddup (%rdi), %xmm1
+ vunpckhpd %xmm1, %xmm0, %xmm0
ret
.cfi_endproc
.LFE2:
@@ -41,7 +44,9 @@ baz:
qux:
.LFB3:
.cfi_startproc
- vmovhpd (%rdi), %xmm0, %xmm0
+ vmovapd %xmm0, %xmm1
+ vmovddup (%rdi), %xmm0
+ vmovsd %xmm1, %xmm0, %xmm0
ret
.cfi_endproc
.LFE3:
@@ -52,12 +57,13 @@ qux:
corge:
.LFB4:
.cfi_startproc
- vextractf128 $0x1, %ymm0, %xmm0
- vunpckhpd %xmm0, %xmm0, %xmm0
- vmovhpd (%rdi), %xmm0, %xmm0
+ vbroadcastsd (%rdi), %ymm2
+ vpermpd $78, %ymm0, %ymm1
+ vperm2f128 $2, %ymm2, %ymm0, %ymm0
+ vshufpd $11, %ymm0, %ymm1, %ymm0
ret
.cfi_endproc
.LFE4:
.size corge, .-corge
- .ident "GCC: (GNU) 9.2.1 20191121"
+ .ident "GCC: (GNU) 10.0.0 20191205 (experimental)"
.section .note.GNU-stack,"",@progbits
None of it is shorter, only baz is the same size as before.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92803
[Bug 92803] [10 Regression] error: type mismatch in 'vec_perm_expr' since
r278764
>From gcc-bugs-return-662416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 11:17:04 2019
Return-Path: <gcc-bugs-return-662416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114485 invoked by alias); 5 Dec 2019 11:17:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114416 invoked by uid 48); 5 Dec 2019 11:16:59 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92791] ICE in extract_insn, at recog.c:2311 since r278645
Date: Thu, 05 Dec 2019 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-92791-4-HhTyEVZv5w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00486.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92791
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[10 Regression] ICE in |ICE in extract_insn, at
|extract_insn, at |recog.c:2311 since r278645
|recog.c:2311 since r278645 |
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed the regression, keeping open for backports to release branches where the
bug is latent.
>From gcc-bugs-return-662417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 11:44:25 2019
Return-Path: <gcc-bugs-return-662417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29492 invoked by alias); 5 Dec 2019 11:44:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29415 invoked by uid 48); 5 Dec 2019 11:44:20 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] New: [10 Regression] libgo.so.15 has executable stack
Date: Thu, 05 Dec 2019 11:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00487.txt.bz2
Content-length: 588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
Bug ID: 92820
Summary: [10 Regression] libgo.so.15 has executable stack
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: doko at debian dot org
CC: cmang at google dot com
Target Milestone: ---
seen with trunk 20191204, almost all architectures except x86_64-linux-gnu. the
lintian tool detected that while packaging GCC 10.
>From gcc-bugs-return-662419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 11:46:55 2019
Return-Path: <gcc-bugs-return-662419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45341 invoked by alias); 5 Dec 2019 11:46:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44924 invoked by uid 48); 5 Dec 2019 11:46:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92819] [10 Regression] Worse code generated on avx2 due to simplify_vector_constructor
Date: Thu, 05 Dec 2019 11:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92819-4-9kNWwRg2jV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00489.txt.bz2
Content-length: 3571
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92819
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rsandifo at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Richard - when we have
_7 = { _2, _2 };
VEC_PERM <x_3(D), _7, { 0, 3 }>
then we somehow run into
/* See if the permutation is performing a single element
insert from a CONSTRUCTOR or constant and use a BIT_INSERT_EXPR
in that case. But only if the vector mode is supported,
otherwise this is invalid GIMPLE. */
if (TYPE_MODE (type) != BLKmode
&& (TREE_CODE (cop0) == VECTOR_CST
|| TREE_CODE (cop0) == CONSTRUCTOR
|| TREE_CODE (cop1) == VECTOR_CST
|| TREE_CODE (cop1) == CONSTRUCTOR))
{
if (sel.series_p (1, 1, nelts + 1, 1))
{
/* After canonicalizing the first elt to come from the
first vector we only can insert the first elt from
the first vector. */
at = 0;
if ((ins = fold_read_from_vector (cop0, sel[0])))
op0 = op1;
but of course cop0 isn't something we can simplify. So - why can
we only insert the first elt from the first vector? Is series_p
falsely triggering because both vectors are "series_p"? That said,
we can insert both ways but only one way succeeds in the end.
The code also looks like it would fail for V1m vectors since then
the base element number is out of range. That is, does the above
even make sense for nelts <= 2?
This is
v2df
qux (v2df x, double *p)
{
return (v2df) { x[0], *p };
}
it works for
v2df
qux (v2df x, double *p)
{
return (v2df) { *p, x[1] };
}
when guarding the special case with
TREE_CODE (cop0) == VECTOR_CST || TREE_CODE (cop0) == CONSTRUCTOR
the later code runs into
bool
vec_perm_indices::series_p (unsigned int out_base, unsigned int out_step,
element_type in_base, element_type in_step) const
{
/* Check the base value. */
if (maybe_ne (clamp (m_encoding.elt (out_base)), clamp (in_base)))
return false;
and thus doesn't handle insertion at the very last element? I can
"fix" that by doing
@@ -6047,9 +6049,11 @@ (define_operator_list COND_TERNARY
for (at = 0; at < encoded_nelts; ++at)
if (maybe_ne (sel[at], at))
break;
- if (at < encoded_nelts && sel.series_p (at + 1, 1, at + 1, 1))
+ if (at < encoded_nelts
+ && (known_eq (at + 1, nelts)
+ || sel.series_p (at + 1, 1, at + 1, 1)))
{
maybe the earlier series_p query needs to be adjusted similarly? Or do you
think that
@@ -6032,7 +6032,9 @@ (define_operator_list COND_TERNARY
|| TREE_CODE (cop1) == VECTOR_CST
|| TREE_CODE (cop1) == CONSTRUCTOR))
{
- if (sel.series_p (1, 1, nelts + 1, 1))
+ if (sel.series_p (1, 1, nelts + 1, 1)
+ && (TREE_CODE (cop0) == VECTOR_CST
+ || TREE_CODE (cop0) == CONSTRUCTOR))
{
/* After canonicalizing the first elt to come from the
first vector we only can insert the first elt from
is fine?
>From gcc-bugs-return-662418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 11:46:20 2019
Return-Path: <gcc-bugs-return-662418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43759 invoked by alias); 5 Dec 2019 11:46:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43602 invoked by uid 48); 5 Dec 2019 11:45:53 -0000
From: "emilio at crisal dot io" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92821] New: Miscompilation when passing 8-bit enum to extern function
Date: Thu, 05 Dec 2019 11:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emilio at crisal dot io
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00488.txt.bz2
Content-length: 1844
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92821
Bug ID: 92821
Summary: Miscompilation when passing 8-bit enum to extern
function
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: emilio at crisal dot io
Target Milestone: ---
Created attachment 47427
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47427&action=edit
Test-case that reproduces the bug with gcc 7.4 and -Os
We've seen a miscompilation of Firefox in GCC 7.4 when compiled with -Os, when
we pass an `enum class : uint8_t` to an extern function. See
https://bugzilla.mozilla.org/show_bug.cgi?id=1600735 for all the details.
It seems fixed in GCC 8. Bisection by redi (thanks!) points to
https://gcc.gnu.org/PR82260 as the culprit for the fix, which seems just a
missed optimization opportunity (thus me filing this bug).
The basic setup is just calling an extern function with an `enum class :
uint8_t` argument, and having that extern function compiled by LLVM (in this
case, by the Rust compiler). LLVM seems to rely on the caller zero-extending
the enum to 32 bits. Per bug 46942 it seems gcc also does something like this
usually (and it does happen to be the case for non -Os builds).
In the bad case, GCC uses a single `mov sil,bl` to set up the argument, which
means garbage on the rest of the register remains that LLVM assumes to be
zeroed.
It seems either GCC should probably always zero-extend when calling an extern
function, or LLVM should never rely on this zero-extension... I don't know what
the relevant ABI specifications say, but I'm happy to file an LLVM bug if this
is deemed not to be a GCC bug per se.
>From gcc-bugs-return-662420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 11:51:10 2019
Return-Path: <gcc-bugs-return-662420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56859 invoked by alias); 5 Dec 2019 11:51:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56791 invoked by uid 48); 5 Dec 2019 11:51:05 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92821] Miscompilation when passing 8-bit enum to extern function
Date: Thu, 05 Dec 2019 11:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92821-4-z25J33xf6h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00490.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92821
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
CC jakub who fixed it (or just made it latent) with r253050
>From gcc-bugs-return-662422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 11:58:57 2019
Return-Path: <gcc-bugs-return-662422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65565 invoked by alias); 5 Dec 2019 11:58:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65531 invoked by uid 48); 5 Dec 2019 11:58:53 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Thu, 05 Dec 2019 11:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc target_milestone
Message-ID: <bug-92820-4-WbOTKQZjMl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00492.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
CC| |rguenth at gcc dot gnu.org
Target Milestone|--- |10.0
>From gcc-bugs-return-662421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 11:58:32 2019
Return-Path: <gcc-bugs-return-662421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64828 invoked by alias); 5 Dec 2019 11:58:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64711 invoked by uid 48); 5 Dec 2019 11:58:26 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92819] [10 Regression] Worse code generated on avx2 due to simplify_vector_constructor
Date: Thu, 05 Dec 2019 11:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92819-4-W0EcxtUSzK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00491.txt.bz2
Content-length: 1845
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92819
--- Comment #2 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> Richard - when we have
>
> _7 = { _2, _2 };
> VEC_PERM <x_3(D), _7, { 0, 3 }>
>
> then we somehow run into
>
> /* See if the permutation is performing a single element
> insert from a CONSTRUCTOR or constant and use a BIT_INSERT_EXPR
> in that case. But only if the vector mode is supported,
> otherwise this is invalid GIMPLE. */
> if (TYPE_MODE (type) != BLKmode
> && (TREE_CODE (cop0) == VECTOR_CST
> || TREE_CODE (cop0) == CONSTRUCTOR
> || TREE_CODE (cop1) == VECTOR_CST
> || TREE_CODE (cop1) == CONSTRUCTOR))
> {
> if (sel.series_p (1, 1, nelts + 1, 1))
> {
> /* After canonicalizing the first elt to come from the
> first vector we only can insert the first elt from
> the first vector. */
> at = 0;
> if ((ins = fold_read_from_vector (cop0, sel[0])))
> op0 = op1;
>
> but of course cop0 isn't something we can simplify. So - why can
> we only insert the first elt from the first vector?
This is because the code has already canonicalised the order
of the oerands so that the first element of the result comes
from the first vector:
else if (known_ge (poly_uint64 (sel[0]), nelts))
{
std::swap (op0, op1);
sel.rotate_inputs (1);
}
So if we're inserting into the second lane or later, the
inserted element comes from the second vector.
Don't know if that answers the rest of the question too.
>From gcc-bugs-return-662423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 12:01:51 2019
Return-Path: <gcc-bugs-return-662423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41206 invoked by alias); 5 Dec 2019 12:01:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36345 invoked by uid 48); 5 Dec 2019 12:01:46 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92819] [10 Regression] Worse code generated on avx2 due to simplify_vector_constructor
Date: Thu, 05 Dec 2019 12:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92819-4-KuyX20Rmg9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00493.txt.bz2
Content-length: 332
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92819
--- Comment #3 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
I guess the issue is specific to 2-element vectors: { 0, 3 } can be seen as
inserting element 1 of the second vector into the first, of the first element
of the second vector into the second.
>From gcc-bugs-return-662424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 12:04:37 2019
Return-Path: <gcc-bugs-return-662424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98773 invoked by alias); 5 Dec 2019 12:04:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98699 invoked by uid 55); 5 Dec 2019 12:04:32 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92819] [10 Regression] Worse code generated on avx2 due to simplify_vector_constructor
Date: Thu, 05 Dec 2019 12:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92819-4-JPSwskFfsu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00494.txt.bz2
Content-length: 2341
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92819
--- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 5 Dec 2019, rsandifo at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92819
>
> --- Comment #2 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
> (In reply to Richard Biener from comment #1)
> > Richard - when we have
> >
> > _7 = { _2, _2 };
> > VEC_PERM <x_3(D), _7, { 0, 3 }>
> >
> > then we somehow run into
> >
> > /* See if the permutation is performing a single element
> > insert from a CONSTRUCTOR or constant and use a BIT_INSERT_EXPR
> > in that case. But only if the vector mode is supported,
> > otherwise this is invalid GIMPLE. */
> > if (TYPE_MODE (type) != BLKmode
> > && (TREE_CODE (cop0) == VECTOR_CST
> > || TREE_CODE (cop0) == CONSTRUCTOR
> > || TREE_CODE (cop1) == VECTOR_CST
> > || TREE_CODE (cop1) == CONSTRUCTOR))
> > {
> > if (sel.series_p (1, 1, nelts + 1, 1))
> > {
> > /* After canonicalizing the first elt to come from the
> > first vector we only can insert the first elt from
> > the first vector. */
> > at = 0;
> > if ((ins = fold_read_from_vector (cop0, sel[0])))
> > op0 = op1;
> >
> > but of course cop0 isn't something we can simplify. So - why can
> > we only insert the first elt from the first vector?
>
> This is because the code has already canonicalised the order
> of the oerands so that the first element of the result comes
> from the first vector:
>
> else if (known_ge (poly_uint64 (sel[0]), nelts))
> {
> std::swap (op0, op1);
> sel.rotate_inputs (1);
> }
>
> So if we're inserting into the second lane or later, the
> inserted element comes from the second vector.
OK, so indeed if we cannot perform the optimization with
an insert to lane zero then we can consider inserting
to lane two. So I conclude my check is good.
> Don't know if that answers the rest of the question too.
Guess it works for me. Will test a patch then.x
>From gcc-bugs-return-662425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 12:05:24 2019
Return-Path: <gcc-bugs-return-662425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100929 invoked by alias); 5 Dec 2019 12:05:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100741 invoked by uid 48); 5 Dec 2019 12:05:15 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92819] [10 Regression] Worse code generated on avx2 due to simplify_vector_constructor
Date: Thu, 05 Dec 2019 12:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92819-4-bKzEJX4D67@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00495.txt.bz2
Content-length: 641
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92819
--- Comment #5 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Sorry for the dribble of messages, but how about just
changing the "else" in:
if (sel.series_p (1, 1, nelts + 1, 1))
{
/* After canonicalizing the first elt to come from the
first vector we only can insert the first elt from
the first vector. */
at = 0;
if ((ins = fold_read_from_vector (cop0, sel[0])))
op0 = op1;
}
else
to "if (!ins)"?
>From gcc-bugs-return-662426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 12:12:20 2019
Return-Path: <gcc-bugs-return-662426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109666 invoked by alias); 5 Dec 2019 12:12:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109608 invoked by uid 55); 5 Dec 2019 12:12:15 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92819] [10 Regression] Worse code generated on avx2 due to simplify_vector_constructor
Date: Thu, 05 Dec 2019 12:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92819-4-wU4IwPU40v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00496.txt.bz2
Content-length: 1133
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92819
--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 5 Dec 2019, rsandifo at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92819
>
> --- Comment #5 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
> Sorry for the dribble of messages, but how about just
> changing the "else" in:
>
> if (sel.series_p (1, 1, nelts + 1, 1))
> {
> /* After canonicalizing the first elt to come from the
> first vector we only can insert the first elt from
> the first vector. */
> at = 0;
> if ((ins = fold_read_from_vector (cop0, sel[0])))
> op0 = op1;
> }
> else
>
> to "if (!ins)"?
Works for me, too. I wonder how to make it clear that all this
can only happen for two-element vectors though while the later
fix applies to all inserts-at-last-lane. Maybe it's all clearer
to single that out very explicitely. I'll at least write a comment...
>From gcc-bugs-return-662427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 12:29:17 2019
Return-Path: <gcc-bugs-return-662427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2574 invoked by alias); 5 Dec 2019 12:29:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2527 invoked by uid 48); 5 Dec 2019 12:29:12 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/92817] the prototype of the built-in __gcov_exit function is wrong
Date: Thu, 05 Dec 2019 12:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92817-4-xjM2Vb8fp7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92817-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00497.txt.bz2
Content-length: 383
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92817
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
>
> as it is, the builtin-in prototype does not match what one would define in
> source code and this trips up type based control-flow integrity checks.
You are right, it's wrong. Can you please explain to me what control-flow
integrity check do you use?
>From gcc-bugs-return-662428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 12:36:04 2019
Return-Path: <gcc-bugs-return-662428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106728 invoked by alias); 5 Dec 2019 12:36:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100105 invoked by uid 55); 5 Dec 2019 12:35:59 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/92817] the prototype of the built-in __gcov_exit function is wrong
Date: Thu, 05 Dec 2019 12:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92817-4-mmrgjmPdt7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92817-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00498.txt.bz2
Content-length: 518
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92817
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Thu Dec 5 12:35:26 2019
New Revision: 278995
URL: https://gcc.gnu.org/viewcvs?rev=278995&root=gcc&view=rev
Log:
Fix __gcov_exit fn prototype.
2019-12-05 Martin Liska <mliska@suse.cz>
PR gcov-profile/92817
* coverage.c (build_gcov_exit_decl): Remove superfluous
void_type_node.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/coverage.c
>From gcc-bugs-return-662429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 12:37:04 2019
Return-Path: <gcc-bugs-return-662429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109262 invoked by alias); 5 Dec 2019 12:37:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109190 invoked by uid 48); 5 Dec 2019 12:36:59 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/92817] the prototype of the built-in __gcov_exit function is wrong
Date: Thu, 05 Dec 2019 12:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92817-4-vA5lDHyPEp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92817-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00499.txt.bz2
Content-length: 473
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92817
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed on trunk, not planning to backport that.
>From gcc-bugs-return-662430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 12:49:39 2019
Return-Path: <gcc-bugs-return-662430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17931 invoked by alias); 5 Dec 2019 12:49:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17847 invoked by uid 48); 5 Dec 2019 12:49:34 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92821] Miscompilation when passing 8-bit enum to extern function
Date: Thu, 05 Dec 2019 12:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92821-4-Ecs6MBEowk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00500.txt.bz2
Content-length: 1229
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92821
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl.tools at gmail dot com,
| |hubicka at gcc dot gnu.org,
| |matz at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I believe it is a LLVM bug.
At least, reading
https://github.com/hjl-tools/x86-psABI/wiki/x86-64-psABI-1.0.pdf, I can't find
in the Parameter Passing section anything that would say that arguments smaller
than 64-bit are passed sign or zero extended to 64-bit like some other psABIs
require. The only related thing is
"When a value of type _Bool is returned or passed in a register or on the
stack,
bit 0 contains the truth value and bits 1 to 7 shall be zero."
with a footnote:
"Other bits are left unspecified, hence the consumer side of those values can
rely on it being 0 or 1 when truncated to 8 bit."
which says that _Bool has only significant low 8 bits and the rest is
unspecified.
>From gcc-bugs-return-662431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 12:59:35 2019
Return-Path: <gcc-bugs-return-662431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46224 invoked by alias); 5 Dec 2019 12:59:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46177 invoked by uid 48); 5 Dec 2019 12:59:31 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Thu, 05 Dec 2019 12:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92820-4-MnVs0TPG6B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00501.txt.bz2
Content-length: 155
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
Don't see that on aarch64 or riscv64.
>From gcc-bugs-return-662433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 13:03:43 2019
Return-Path: <gcc-bugs-return-662433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65981 invoked by alias); 5 Dec 2019 13:03:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65242 invoked by uid 55); 5 Dec 2019 13:03:33 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92818] Typo in vec_perm -> bit_insert pattern
Date: Thu, 05 Dec 2019 13:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92818-4-0R85AJKkf0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00503.txt.bz2
Content-length: 767
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92818
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Thu Dec 5 13:02:57 2019
New Revision: 278998
URL: https://gcc.gnu.org/viewcvs?rev=278998&root=gcc&view=rev
Log:
2019-12-05 Richard Biener <rguenther@suse.de>
PR middle-end/92818
* tree-ssa-forwprop.c (simplify_vector_constructor): Improve
heuristics on what don't care element to choose.
* match.pd (VEC_PERM_EXPR -> BIT_INSERT_EXPR): Fix typo.
* gcc.target/i386/pr92818.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr92818.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/match.pd
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-forwprop.c
>From gcc-bugs-return-662432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 13:03:26 2019
Return-Path: <gcc-bugs-return-662432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64218 invoked by alias); 5 Dec 2019 13:03:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64145 invoked by uid 48); 5 Dec 2019 13:03:19 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92822] New: regressions on aarch64 after r278938
Date: Thu, 05 Dec 2019 13:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00502.txt.bz2
Content-length: 2032
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92822
Bug ID: 92822
Summary: regressions on aarch64 after r278938
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
After commit r278938, I've noticed regressions on aarch64:
FAIL: gcc.target/aarch64/fmla_intrinsic_1.c scan-assembler-times
fmla\\tv[0-9]+.2s, v[0-9]+.2s, v[0-9]+.2s\\[[0-9]+\\] 2
FAIL: gcc.target/aarch64/fmls_intrinsic_1.c scan-assembler-times
fmls\\tv[0-9]+.2s, v[0-9]+.2s, v[0-9]+.2s\\[[0-9]+\\] 2
FAIL: gcc.target/aarch64/fmul_intrinsic_1.c scan-assembler-times
fmul\\td[0-9]+, d[0-9]+, d[0-9]+ 1
FAIL: gcc.target/aarch64/fmul_intrinsic_1.c scan-assembler-times
fmul\\tv[0-9]+.2d, v[0-9]+.2d, v[0-9]+.d\\[[0-9]+\\] 3
FAIL: gcc.target/aarch64/fmul_intrinsic_1.c scan-assembler-times
fmul\\tv[0-9]+.2s, v[0-9]+.2s, v[0-9]+.s\\[[0-9]+\\] 2
FAIL: gcc.target/aarch64/simd/vmulx_laneq_f32_1.c scan-assembler-times fmulx[
\t]+[vV][0-9]+.2[sS], ?[vV][0-9]+.2[sS], ?[vV][0-9]+.[sS]\\[0\\]\n 1
FAIL: gcc.target/aarch64/simd/vmulx_laneq_f32_1.c scan-assembler-times fmulx[
\t]+[vV][0-9]+.2[sS], ?[vV][0-9]+.2[sS], ?[vV][0-9]+.[sS]\\[1\\]\n 1
FAIL: gcc.target/aarch64/simd/vmulx_laneq_f32_1.c scan-assembler-times fmulx[
\t]+[vV][0-9]+.2[sS], ?[vV][0-9]+.2[sS], ?[vV][0-9]+.[sS]\\[2\\]\n 1
FAIL: gcc.target/aarch64/simd/vmulx_laneq_f32_1.c scan-assembler-times fmulx[
\t]+[vV][0-9]+.2[sS], ?[vV][0-9]+.2[sS], ?[vV][0-9]+.[sS]\\[3\\]\n 1
FAIL: gcc.target/aarch64/simd/vmulx_laneq_f64_1.c scan-assembler-times fmulx[
\t]+[dD][0-9]+, ?[dD][0-9]+, ?[vV][0-9]+.[dD]\\[0\\]\n 1
FAIL: gcc.target/aarch64/simd/vmulx_laneq_f64_1.c scan-assembler-times fmulx[
\t]+[dD][0-9]+, ?[dD][0-9]+, ?[vV][0-9]+.[dD]\\[1\\]\n 1
FAIL: gcc.target/aarch64/singleton_intrinsics_1.c scan-assembler-times
aarch64_get_lanev2di 2
>From gcc-bugs-return-662434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 13:05:05 2019
Return-Path: <gcc-bugs-return-662434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82842 invoked by alias); 5 Dec 2019 13:05:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82771 invoked by uid 48); 5 Dec 2019 13:05:00 -0000
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92823] New: Is that possible to optimize C++ exception??????????? I always HATE 2 phases of exception unwind
Date: Thu, 05 Dec 2019 13:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: EH
X-Bugzilla-Severity: normal
X-Bugzilla-Who: euloanty at live dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00504.txt.bz2
Content-length: 3059
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92823
Bug ID: 92823
Summary: Is that possible to optimize C++ exception???????????
I always HATE 2 phases of exception unwind
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: EH
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: euloanty at live dot com
Target Milestone: ---
This paper shows the possibility of optimizing the current exception model.
Just optimize lippincott function will yield huge benefits.
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1676r0.pdf
Here is the proposal of Bjarne Stroustrup:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1947r0.pdf
Same with clang. It also does 2 phase unwinding.
Stroustrup C++ exceptions and alternatives P1947
I think that the current implementations of C++ exception handling are
sub-optimal from a performance
standpoint and could be improved:
• GCC always (even in optimized modes) walks the stack twice to provide better
debug support.
• Implementations use complete RTTI implementations to do type matching
(ostensibly to
simplify use of dynamic linking).
• Cross-function optimizations of exception handling are still rare.
• Special-purpose stack-unwinding and type-matching algorithms are not used for
systems with
special requirements (e.g., with no dynamic linking or tight memories).
• Some exception handling mechanisms cater for generalizations and alternatives
not mandated
by the standard.
• There seem to be no optimization of the original case of passing and catching
simple exceptions
by value. Given final, we can know that a given exception type isn’t the root
of a hierarchy.
• Use of the general free store for all exception objects, rather than
pre-allocated memory for
common and important exceptions as anticipated in the original design.
One reason for the relative poverty of optimizations seems to be that since
exceptions were considered
slow there seemed no reason to optimize them. Thus, exception handling is now
relatively slower than it
was in the 1990s. Other kinds of code have been significantly optimized since
then.
As an example of a missed opportunity, I can mention the Chinese-remainder fast
constant-time type
matching algorithm that I published in 2005 [Gibbs]. For closed systems and
relatively small class
hierarchies (as are increasingly common in embedded systems), this eliminates
almost all of the type
matching cost.
It may also be the case that the table-based implementation approach is
sub-optimal for tiny memories
compared to error-code/stack-marking implementation approaches. The possibility
of special-purpose
implementations of exception handling for special-purpose systems ought to be
explored. The
Edinburgh experiments [Renwick] are encouraging for this direction of
exploration.
>From gcc-bugs-return-662435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 13:08:08 2019
Return-Path: <gcc-bugs-return-662435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93963 invoked by alias); 5 Dec 2019 13:08:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88857 invoked by uid 48); 5 Dec 2019 13:08:03 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92818] Typo in vec_perm -> bit_insert pattern
Date: Thu, 05 Dec 2019 13:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92818-4-yGTq5pIDoI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00505.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92818
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-662436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 13:10:33 2019
Return-Path: <gcc-bugs-return-662436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115282 invoked by alias); 5 Dec 2019 13:10:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115233 invoked by uid 48); 5 Dec 2019 13:10:28 -0000
From: "ch3root at openwall dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92824] New: Wrong optimization: representation of long doubles not copied even with memcpy
Date: Thu, 05 Dec 2019 13:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ch3root at openwall dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00506.txt.bz2
Content-length: 2080
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92824
Bug ID: 92824
Summary: Wrong optimization: representation of long doubles not
copied even with memcpy
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: ch3root at openwall dot com
Target Milestone: ---
Source code:
----------------------------------------------------------------------
#include <string.h>
#include <stdio.h>
int main()
{
long double x, y;
unsigned char *px = (unsigned char *)&x;
unsigned char *py = (unsigned char *)&y;
// make x pseudo-denormal
x = 0;
px[7] = 0x80;
// set padding
px[10] = 0x80;
px[11] = 0x80;
px[12] = 0x80;
px[13] = 0x80;
px[14] = 0x80;
px[15] = 0x80;
// uncomment if you don't like pseudo-denormals
//memset(&x, 0x80, sizeof x);
y = x;
memcpy(&y, &x, sizeof y);
for (int i = sizeof y; i-- > 0;)
printf("%02x ", py[i]);
printf("\n");
}
----------------------------------------------------------------------
Results:
----------------------------------------------------------------------
$ gcc -std=c11 -pedantic -Wall -Wextra test.c && ./a.out
80 80 80 80 80 80 00 00 80 00 00 00 00 00 00 00
$ gcc -std=c11 -pedantic -Wall -Wextra -O3 test.c && ./a.out
00 00 00 00 00 00 00 01 80 00 00 00 00 00 00 00
----------------------------------------------------------------------
gcc x86-64 version: gcc (GCC) 10.0.0 20191205 (experimental)
Another variation of pr92486 and pr71475. This time on trunk and without
structs. Feel free to close as dup.
There are two issues here:
- padding is not copied;
- if pseudo-denormals are not considered trap representions in gcc, their
non-padding bytes are not preserved too (the exponent is changed from 0 to 1).
(OTOH it seems sNaN in double on x86-32 is not converted to qNaN in such a
situation.)
>From gcc-bugs-return-662437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 13:12:15 2019
Return-Path: <gcc-bugs-return-662437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48851 invoked by alias); 5 Dec 2019 13:12:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41218 invoked by uid 48); 5 Dec 2019 13:12:10 -0000
From: "emilio at crisal dot io" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92821] Miscompilation when passing 8-bit enum to extern function
Date: Thu, 05 Dec 2019 13:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emilio at crisal dot io
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92821-4-M1znSFYGPr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00507.txt.bz2
Content-length: 414
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92821
--- Comment #3 from Emilio Cobos Álvarez (:emilio) <emilio at crisal dot io> ---
If my reading of https://godbolt.org/z/BNHxEY is correct (sorry, still a bit of
a noob with disassembly), it looks like GCC does correctly load only the low
byte in the equivalent implementation of the Rust function, but clang does
assume zero-extension to 32 bit... :/
>From gcc-bugs-return-662438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 13:14:03 2019
Return-Path: <gcc-bugs-return-662438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130138 invoked by alias); 5 Dec 2019 13:14:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130074 invoked by uid 48); 5 Dec 2019 13:13:58 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Thu, 05 Dec 2019 13:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92820-4-TpTWju25wn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00508.txt.bz2
Content-length: 201
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
--- Comment #2 from Matthias Klose <doko at debian dot org> ---
I don't see it here on x86_64-linux-gnu, aarch64-linux-gnu,
powerpc64le-linux-gnu.
>From gcc-bugs-return-662439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 13:21:28 2019
Return-Path: <gcc-bugs-return-662439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15583 invoked by alias); 5 Dec 2019 13:21:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15522 invoked by uid 48); 5 Dec 2019 13:21:22 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92825] New: Unnecesary stack protection and missed SLP vectorization in Firefox's LightPixel.
Date: Thu, 05 Dec 2019 13:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00509.txt.bz2
Content-length: 5317
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92825
Bug ID: 92825
Summary: Unnecesary stack protection and missed SLP
vectorization in Firefox's LightPixel.
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
Target Milestone: ---
Created attachment 47428
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47428&action=edit
full testcase
uint32_t DiffuseLightingSoftware::LightPixel(const Point3D& aNormal,
const Point3D& aVectorToLight,
uint32_t aColor) {
Float dotNL = std::max(0.0f, aNormal.DotProduct(aVectorToLight));
Float diffuseNL = mDiffuseConstant * dotNL;
union {
uint32_t bgra;
uint8_t components[4];
} color = {aColor};
color.components[B8G8R8A8_COMPONENT_BYTEOFFSET_B] = umin(
uint32_t(diffuseNL * color.components[B8G8R8A8_COMPONENT_BYTEOFFSET_B]),
255U);
color.components[B8G8R8A8_COMPONENT_BYTEOFFSET_G] = umin(
uint32_t(diffuseNL * color.components[B8G8R8A8_COMPONENT_BYTEOFFSET_G]),
255U);
color.components[B8G8R8A8_COMPONENT_BYTEOFFSET_R] = umin(
uint32_t(diffuseNL * color.components[B8G8R8A8_COMPONENT_BYTEOFFSET_R]),
255U);
color.components[B8G8R8A8_COMPONENT_BYTEOFFSET_A] = 255;
return color.bgra;
}
(full testcase attached)
Built with -O3 -fstack-protection-strong results in slower code with gcc10 than
with gcc9 or clang.
GCC produces:
│ 0000000004390e20 <mozilla::gfx::(anonymous
namespace)::SpecularLightingSoftware::LightPixel(mozilla::gfx::Point3DTyped<mozilla::gfx::UnknownUnits,
float> const&,
│
_ZN7mozilla3gfx12_GLOBAL__N_124SpecularLightingSoftware10LightPixelERKNS0_12Point3DTypedINS0_12UnknownUnitsEfEES7_j():
0.19 │ push %rbp
0.60 │ pxor %xmm5,%xmm5
0.05 │ mov %rsp,%rbp
0.12 │ push %rbx
0.65 │ sub $0x18,%rsp
0.33 │ movss 0x4(%rdx),%xmm0
0.10 │ movss (%rdx),%xmm1
0.58 │ mov %fs:0x28,%rax
0.03 │ mov %rax,-0x18(%rbp)
0.22 │ xor %eax,%eax
0.07 │ movss pw_32+0x1588,%xmm3
1.58 │ addss 0x8(%rdx),%xmm3
0.67 │ addss %xmm5,%xmm0
0.23 │ addss %xmm5,%xmm1
│ movaps %xmm0,%xmm2
0.41 │ movaps %xmm1,%xmm4
0.87 │ mulss %xmm0,%xmm2
0.28 │ mulss %xmm1,%xmm4
3.71 │ addss %xmm2,%xmm4
0.14 │ movaps %xmm3,%xmm2
0.04 │ mulss %xmm3,%xmm2
1.99 │ addss %xmm2,%xmm4
0.15 │ movss 0x4(%rsi),%xmm2
9.39 │ sqrtss %xmm4,%xmm4
8.90 │ divss %xmm4,%xmm0
2.10 │ divss %xmm4,%xmm3
1.08 │ mulss %xmm0,%xmm2
0.01 │ movss 0x8(%rsi),%xmm0
while clang
Percent│
_ZN7mozilla3gfx12_GLOBAL__N_124SpecularLightingSoftware10LightPixelERKNS0_12Point3DTypedINS0_12UnknownUnitsEfEES7_j():
0.11 │ xorps %xmm0,%xmm0
0.83 │ movss 0x4(%rdx),%xmm1
3.29 │ addss %xmm0,%xmm1
0.03 │ movss (%rdx),%xmm2
0.08 │ movss 0x8(%rdx),%xmm3
0.04 │ unpcklps %xmm2,%xmm3
0.59 │ movss
mozilla::gfx::ConvertComponentTransferFunctionToFilter(mozilla::gfx::ComponentTransferAttributes
const&, int, int, mozilla::gfx::DrawTarget*, RefPtr<m
1.00 │ addps %xmm2,%xmm3
0.10 │ movaps %xmm3,%xmm4
0.82 │ shufps $0xe5,%xmm3,%xmm4
3.05 │ mulss %xmm4,%xmm4
0.09 │ movaps %xmm1,%xmm5
0.12 │ mulss %xmm1,%xmm5
2.77 │ addss %xmm4,%xmm5
0.06 │ movaps %xmm3,%xmm4
0.00 │ mulss %xmm3,%xmm4
2.95 │ addss %xmm5,%xmm4
9.54 │ sqrtss %xmm4,%xmm4
8.84 │ divss %xmm4,%xmm1
0.08 │ shufps $0xe0,%xmm4,%xmm4
2.45 │ divps %xmm4,%xmm3
0.88 │ mulss 0x4(%rsi),%xmm1
0.01 │ movss (%rsi),%xmm4
│ movss 0x8(%rsi),%xmm5
0.02 │ unpcklps %xmm4,%xmm5
2.82 │ mulps %xmm3,%xmm5
0.03 │ movaps %xmm5,%xmm3
0.88 │ shufps $0xe5,%xmm5,%xmm3
3.47 │ addss %xmm1,%xmm3
3.39 │ addss %xmm5,%xmm3
3.09 │ cmpless %xmm3,%xmm0
1.77 │ andps %xmm2,%xmm0
3.01 │ mulss %xmm3,%xmm0
3.25 │ mulss
mozIGeckoMediaPluginService::COMTypeInfo<mozIGeckoMediaPluginService,
void,%xmm0
4.85 │ cvttss2si %xmm0,%eax
>From gcc-bugs-return-662440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 13:28:02 2019
Return-Path: <gcc-bugs-return-662440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46492 invoked by alias); 5 Dec 2019 13:28:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46230 invoked by uid 48); 5 Dec 2019 13:27:57 -0000
From: "emilio at crisal dot io" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92821] Miscompilation when passing 8-bit enum to extern function
Date: Thu, 05 Dec 2019 13:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emilio at crisal dot io
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also
Message-ID: <bug-92821-4-sXT4gOV9SB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00510.txt.bz2
Content-length: 583
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92821
Emilio Cobos Álvarez (:emilio) <emilio at crisal dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.llvm.org/show_
| |bug.cgi?id=44228
--- Comment #4 from Emilio Cobos Álvarez (:emilio) <emilio at crisal dot io> ---
I filed https://bugs.llvm.org/show_bug.cgi?id=44228 to get some input from LLVM
folks.
>From gcc-bugs-return-662441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 13:36:32 2019
Return-Path: <gcc-bugs-return-662441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54389 invoked by alias); 5 Dec 2019 13:36:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54332 invoked by uid 48); 5 Dec 2019 13:36:25 -0000
From: "pageexec at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/92817] the prototype of the built-in __gcov_exit function is wrong
Date: Thu, 05 Dec 2019 13:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pageexec at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92817-4-TFjLAQj7at@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92817-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00511.txt.bz2
Content-length: 580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92817
--- Comment #5 from PaX Team <pageexec at gmail dot com> ---
(In reply to Martin Liška from comment #2)
> You are right, it's wrong. Can you please explain to me what control-flow
> integrity check do you use?
it's my own called RAP (Reuse Attack Protector, see
https://pax.grsecurity.net/docs/PaXTeam-H2HC15-RAP-RIP-ROP.pdf). a public
version for linux (the kernel) is available in PaX and grsecurity though i
think that older version won't find this problem as it didn't handle internal
types like this at the time.
>From gcc-bugs-return-662442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 13:40:58 2019
Return-Path: <gcc-bugs-return-662442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57192 invoked by alias); 5 Dec 2019 13:40:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57117 invoked by uid 48); 5 Dec 2019 13:40:52 -0000
From: "matz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92821] Miscompilation when passing 8-bit enum to extern function
Date: Thu, 05 Dec 2019 13:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matz at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92821-4-hSSTo9aVAf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00512.txt.bz2
Content-length: 435
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92821
--- Comment #5 from Michael Matz <matz at gcc dot gnu.org> ---
Yes, we (intentionally) haven't required any extensions to happen for arguments
or return values smaller than 64bit (e.g. we haven't even specified that
arguments <= 32bit would be zero-extended in the high bits, as would have been
natural with the instruction set). If LLVM relies on that it would be a bug.
>From gcc-bugs-return-662443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 14:21:18 2019
Return-Path: <gcc-bugs-return-662443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24762 invoked by alias); 5 Dec 2019 14:21:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18564 invoked by uid 55); 5 Dec 2019 14:21:10 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Thu, 05 Dec 2019 14:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92768-4-kloH49j4Ig@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00513.txt.bz2
Content-length: 1139
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
--- Comment #16 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Thu Dec 5 14:20:38 2019
New Revision: 279002
URL: https://gcc.gnu.org/viewcvs?rev=279002&root=gcc&view=rev
Log:
Check for bitwise identity when encoding VECTOR_CSTs (PR 92768)
This PR shows that we weren't checking for bitwise-identical values
when trying to encode a VECTOR_CST, so -0.0 was treated the same as
0.0 for -fno-signed-zeros. The patch adds a new OEP flag to select
that behaviour.
2019-12-05 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR middle-end/92768
* tree-core.h (OEP_BITWISE): New flag.
* fold-const.c (operand_compare::operand_equal_p): Handle it.
* tree-vector-builder.h (tree_vector_builder::equal_p): Pass it.
gcc/testsuite/
PR middle-end/92768
* gcc.dg/pr92768.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/pr92768.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/fold-const.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-core.h
trunk/gcc/tree-vector-builder.h
>From gcc-bugs-return-662444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 14:28:18 2019
Return-Path: <gcc-bugs-return-662444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68390 invoked by alias); 5 Dec 2019 14:28:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68276 invoked by uid 48); 5 Dec 2019 14:28:11 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92825] Unnecesary stack protection and missed SLP vectorization in Firefox's LightPixel.
Date: Thu, 05 Dec 2019 14:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92825-4-DCvn2SYt1p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92825-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00514.txt.bz2
Content-length: 4445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92825
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-05
CC| |jakub at gcc dot gnu.org,
| |law at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The stack protection in there is because the expansion sees the color variable
(not optimized away) in there and that variable's type contains arrays.
I guess this boils down to:
int
foo (int r, int g, int b)
{
union U { int rgba; char p[4]; } u;
u.p[0] = r;
u.p[1] = g;
u.p[2] = b;
u.p[3] = -1;
return u.rgba;
}
While stack_vars_num is 0 here, we don't force u into memory, it gets assigned
a pseudo instead, stack protection is still forced because of
stack_protect_decl_p function.
Now, why it is done this way rather than only do such checks on the vars we
force into memory, like moving the stack_protect_decl_p call from where it is
currently to around:
/* If stack protection is enabled, we don't share space between
vulnerable data and non-vulnerable data. */
if (flag_stack_protect != 0
&& (flag_stack_protect != SPCT_FLAG_EXPLICIT
|| (flag_stack_protect == SPCT_FLAG_EXPLICIT
&& lookup_attribute ("stack_protect",
DECL_ATTRIBUTES
(current_function_decl)))))
add_stack_protection_conflicts ();
and iterate on stack_vars[0].decl ... stack_vars[stack_vars_num - 1].decl
instead of
FOR_EACH_LOCAL_DECL (cfun, i, var)
if (!is_global_var (var))
I have no idea.
We'd instrument fewer functions, sure, but vars that don't really live in
memory shouldn't result in stack overflows.
CCing Jeff as reviewer of the -fstack-protector-strong patches.
Completely untested patch that fixes the short testcase mentioned above:
--- gcc/cfgexpand.c.jj 2019-12-03 20:21:30.542464581 +0100
+++ gcc/cfgexpand.c 2019-12-05 15:19:08.578613685 +0100
@@ -2021,19 +2021,18 @@ static bool
stack_protect_decl_p ()
{
unsigned i;
- tree var;
- FOR_EACH_LOCAL_DECL (cfun, i, var)
- if (!is_global_var (var))
- {
- tree var_type = TREE_TYPE (var);
- if (VAR_P (var)
- && (TREE_CODE (var_type) == ARRAY_TYPE
- || TREE_ADDRESSABLE (var)
- || (RECORD_OR_UNION_TYPE_P (var_type)
- && record_or_union_type_has_array_p (var_type))))
- return true;
- }
+ for (i = 0; i < stack_vars_num; i++)
+ {
+ tree var = stack_vars[i].decl;
+ tree var_type = TREE_TYPE (var);
+ if (VAR_P (var)
+ && (TREE_CODE (var_type) == ARRAY_TYPE
+ || TREE_ADDRESSABLE (var)
+ || (RECORD_OR_UNION_TYPE_P (var_type)
+ && record_or_union_type_has_array_p (var_type))))
+ return true;
+ }
return false;
}
@@ -2103,8 +2102,7 @@ expand_used_vars (void)
}
if (flag_stack_protect == SPCT_FLAG_STRONG)
- gen_stack_protect_signal
- = stack_protect_decl_p () || stack_protect_return_slot_p ();
+ gen_stack_protect_signal = stack_protect_return_slot_p ();
/* At this point all variables on the local_decls with TREE_USED
set are not associated with any block scope. Lay them out. */
@@ -2180,6 +2178,9 @@ expand_used_vars (void)
if (stack_vars_num > 0)
{
+ if (flag_stack_protect == SPCT_FLAG_STRONG)
+ gen_stack_protect_signal |= stack_protect_decl_p ();
+
add_scope_conflicts ();
/* If stack protection is enabled, we don't share space between
Of course, pedantically it changes the meaning of -fstack-protector-strong from
variables with arrays to variables with arrays emitted into memory. Though, we
already don't count variables that are optimized away anyway.
Another question is if we need this stack_protect_decl_p function at all, I
mean, stack_protect_classify_type should already flag those variables as
needing protection and if it doesn't flag any, what is the point when no vars
would be emitted in the area of stack protected variables?
>From gcc-bugs-return-662445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 14:36:00 2019
Return-Path: <gcc-bugs-return-662445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10341 invoked by alias); 5 Dec 2019 14:35:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9900 invoked by uid 48); 5 Dec 2019 14:35:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92821] Miscompilation when passing 8-bit enum to extern function
Date: Thu, 05 Dec 2019 14:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92821-4-oUlcl3R3ZM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00515.txt.bz2
Content-length: 316
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92821
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Note that for most types one ends up with zero or sign extension already due to
C/C++ promotion rules, though in the ABI still can't use that as guarantee, but
C++ typed enums aren't promoted.
>From gcc-bugs-return-662446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 14:43:45 2019
Return-Path: <gcc-bugs-return-662446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27447 invoked by alias); 5 Dec 2019 14:43:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24544 invoked by uid 48); 5 Dec 2019 14:43:41 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92821] Miscompilation when passing 8-bit enum to extern function
Date: Thu, 05 Dec 2019 14:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92821-4-knRh5Yvih2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00516.txt.bz2
Content-length: 258
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92821
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Related links:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46942
https://groups.google.com/forum/?hl=en#!topic/x86-64-abi/E8O33onbnGQ
>From gcc-bugs-return-662447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 15:06:09 2019
Return-Path: <gcc-bugs-return-662447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72320 invoked by alias); 5 Dec 2019 15:06:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72268 invoked by uid 48); 5 Dec 2019 15:06:04 -0000
From: "kim.walisch at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92826] New: Impossible to silence warning: non-standard suffix on floating constant [-Wpedantic]
Date: Thu, 05 Dec 2019 15:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kim.walisch at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00517.txt.bz2
Content-length: 1628
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92826
Bug ID: 92826
Summary: Impossible to silence warning: non-standard suffix on
floating constant [-Wpedantic]
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: kim.walisch at gmail dot com
Target Milestone: ---
Created attachment 47429
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47429&action=edit
Causes warning when compiled using -Wpedantic
Hi,
GCC warns when using the Q suffix for __float128 constants and compiling using
-Wpedantic:
int main()
{
if (1.0Q > 0)
return 0;
else
return 1;
}
$ gcc -Wpedantic test.c -o test
test.c: In function ‘main’:
test.c:3:2: warning: non-standard suffix on floating constant [-Wpedantic]
if (1.0Q > 0)
^~
GCC even warns when using constants defined as macros from the <quadmath.h>
system header.
#include <quadmath.h>
int main()
{
if (1.0 > FLT128_MIN)
return 0;
else
return 1;
}
$ gcc -Wpedantic test.c -o test
test.c: In function ‘main’:
test.c:5:5: warning: non-standard suffix on floating constant [-Wpedantic]
if (1.0 > FLT128_MIN)
GCC should definitely not warn when using constants from <quadmath.h>. GCC
should also provide an option to disable these warnings (e.g.
-Wno-non-standard-suffix). People are currently using disgusting hacks to avoid
these warnings so please add an option for that.
>From gcc-bugs-return-662448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 15:12:15 2019
Return-Path: <gcc-bugs-return-662448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89821 invoked by alias); 5 Dec 2019 15:12:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89763 invoked by uid 48); 5 Dec 2019 15:12:10 -0000
From: "emilio at crisal dot io" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92821] Miscompilation when passing 8-bit enum to extern function
Date: Thu, 05 Dec 2019 15:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emilio at crisal dot io
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92821-4-fBkW9ZUrsw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00518.txt.bz2
Content-length: 1078
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92821
--- Comment #8 from Emilio Cobos Álvarez (:emilio) <emilio at crisal dot io> ---
(In reply to Jakub Jelinek from comment #6)
> Note that for most types one ends up with zero or sign extension already due
> to C/C++ promotion rules, though in the ABI still can't use that as
> guarantee, but C++ typed enums aren't promoted.
I see.
Another point that someone made in the Mozilla bug tracker is that the ABI, in
the "Scalar Types" table, specifies that enums are represented as a `signed
fourbyte`.
I'm not sure that applies to typed enums. But just in case, if it does, the ABI
may require sign/zero-extending these too?
Looking at https://bugs.llvm.org/show_bug.cgi?id=12207, which might be a dupe
of the LLVM bug I just filed, doesn't make me very hopeful of LLVM changing
their behavior here.
Would it make sense to make gcc always zero/sign-extend on the caller, even if
not required by the ABI or the language? This makes a bunch of calls from gcc
to llvm-compiled binaries potentially unsafe.
>From gcc-bugs-return-662449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 15:14:32 2019
Return-Path: <gcc-bugs-return-662449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98203 invoked by alias); 5 Dec 2019 15:14:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98137 invoked by uid 48); 5 Dec 2019 15:14:27 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92827] New: Missing data/state sharing/propagation between host and offloading devices
Date: Thu, 05 Dec 2019 15:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92827-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00519.txt.bz2
Content-length: 3141
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92827
Bug ID: 92827
Summary: Missing data/state sharing/propagation between host
and offloading devices
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: openacc, openmp
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: burnus at gcc dot gnu.org, jakub at gcc dot gnu.org
Target Milestone: ---
An issue known for a long time, now finally put into a PR.
We're currently missing data/state sharing/propagation between host and
offloading devices, which can lead to inconsistencies in behavior, and other
surprises. In particular, this concerns the state kept by all involved runtime
libraries, such as libgomp itself, libgfortran, libc/libm.
At process creation time, no constructors etc. are executed for offload devices
to initialize the respective runtime libraries' state, so these run with
uninitialized state, and we're lucky that this is doing reasonable things most
of the time.
---
For example,
<http://mid.mail-archive.com/875zvynbml.fsf@euler.schwinge.homeip.net>:
On 2018-12-12T14:00:18+0100, Thomas Schwinge <thomas@codesourcery.com> wrote:
> On Wed, 12 Dec 2018 10:36:17 +0100, Jakub Jelinek <jakub@redhat.com> wrote:
>> Eventually we need to find a way how to transfer some ICVs and other data
>> from the host to the offloading library, either process shared that aren't
>> changing, which can include the hostname, getpid, or some others that would
>> need to be passed for every target region.
>
> That would probably also include any state that the respective language
> runtime libraries maintain? For example, C's global rounding mode as set
> my "fesetround". ..., and I now wonder how to propagate that from the
> host libc to the target libcs, for example host: glibc vs. nvptx
> offloading: newlib -- have to do a host-side "fegetround" before each
> offloaded code region, or at least when there's been an intermediate
> host-side "fesetround" call (so have to track these?), and likewise for
> any other such state-changing functions? Also, the "options" array and
> call of "_gfortran_set_options" that the Fortran front end synthesizes
> into each "main" function?
Or,
<http://mid.mail-archive.com/2d74db4f-afc0-2821-51ce-88e64033c98a@codesourcery.com>:
On 2019-12-05T09:44:26+0100, Tobias Burnus <tobias@codesourcery.com> wrote:
> +! In gfortran's main program, libfortran's set_options is called - which sets
> +! compiler_options.backtrace = 1 by default. For an offload libgfortran, this
> +! is never called and, hence, "Error termination." is never printed. Thus:
> +! { dg-output "Error termination.*" { target { ! { openacc_nvidia_accel_selected || openacc_amdgcn_accel_selected } } } }
---
Probably the first task is to run any such constructors/setup on the offload
devices at all, and another task then is to keep state synchronized between
host and offload devices.
>From gcc-bugs-return-662450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 15:25:50 2019
Return-Path: <gcc-bugs-return-662450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41151 invoked by alias); 5 Dec 2019 15:25:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40658 invoked by uid 48); 5 Dec 2019 15:25:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92821] Miscompilation when passing 8-bit enum to extern function
Date: Thu, 05 Dec 2019 15:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92821-4-FEmRV5fklu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00520.txt.bz2
Content-length: 1206
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92821
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Emilio Cobos Álvarez (:emilio) from comment #8)
> Another point that someone made in the Mozilla bug tracker is that the ABI,
> in the "Scalar Types" table, specifies that enums are represented as a
> `signed fourbyte`.
It doesn't apply to typed enums nor normal enums that don't fit into the 4
bytes, such as enum E { -9223372036854775807LL, 9223372036854775807LL }; etc.
typed enums have a fixed underlying type and that is what they use, in your
case uint8_t.
> I'm not sure that applies to typed enums. But just in case, if it does, the
> ABI may require sign/zero-extending these too?
>
> Looking at https://bugs.llvm.org/show_bug.cgi?id=12207, which might be a
> dupe of the LLVM bug I just filed, doesn't make me very hopeful of LLVM
> changing their behavior here.
What really matters is what does the psABI say, and as you can see above
clarified from one of the ABI authors, there is intentionally no zero or sign
extension of shorter arguments.
So LLVM has a bug and that bug should be fixed in there, not worked around in
other compilers.
>From gcc-bugs-return-662451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 15:35:16 2019
Return-Path: <gcc-bugs-return-662451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63078 invoked by alias); 5 Dec 2019 15:35:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63017 invoked by uid 48); 5 Dec 2019 15:35:12 -0000
From: "emilio at crisal dot io" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92821] Miscompilation when passing 8-bit enum to extern function
Date: Thu, 05 Dec 2019 15:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emilio at crisal dot io
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92821-4-61RKqaBItj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00521.txt.bz2
Content-length: 1215
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92821
Emilio Cobos Álvarez (:emilio) <emilio at crisal dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #10 from Emilio Cobos Álvarez (:emilio) <emilio at crisal dot io> ---
(In reply to Jakub Jelinek from comment #9)
> What really matters is what does the psABI say, and as you can see above
> clarified from one of the ABI authors, there is intentionally no zero or
> sign extension of shorter arguments.
> So LLVM has a bug and that bug should be fixed in there, not worked around
> in other compilers.
Well, we do make changes in Gecko to improve interop with other browser engines
even when the spec doesn't explicitly specify a given behavior... But yeah, I
totally get that, and I hate when we have to do that too. It was worth a shot
though :)
At this point I guess this should be closed as invalid, unless someone or
further evidence shows there's something to fix in GCC.
Thanks for all your work in GCC :)
>From gcc-bugs-return-662452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 15:54:51 2019
Return-Path: <gcc-bugs-return-662452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8778 invoked by alias); 5 Dec 2019 15:54:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8738 invoked by uid 48); 5 Dec 2019 15:54:46 -0000
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92828] New: array out of bounds access in libcpp/mkdeps.c
Date: Thu, 05 Dec 2019 15:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: krebbel at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00522.txt.bz2
Content-length: 1957
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92828
Bug ID: 92828
Summary: array out of bounds access in libcpp/mkdeps.c
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: krebbel at gcc dot gnu.org
Target Milestone: ---
/* If T begins with any of the partial pathnames listed in d->vpathv,
then advance T to point beyond that pathname. */
static const char *
apply_vpath (class mkdeps *d, const char *t)
{
if (unsigned len = d->vpath.size ())
for (unsigned i = len; i--;)
{
if (!filename_ncmp (d->vpath[i].str, t, d->vpath[i].len))
{
const char *p = t + d->vpath[i].len;
if (!IS_DIR_SEPARATOR (*p))
goto not_this_one;
/* Do not simplify $(vpath)/../whatever. ??? Might not
be necessary. */
if (p[1] == '.' && p[2] == '.' && IS_DIR_SEPARATOR (p[3]))
goto not_this_one;
...
The last check causes
error: array subscript 2 is outside array bounds of ‘const char [2]’
if apply_vpath gets inlined into deps_add_target and deps_add_target gets
inlined into:
void
deps_add_default_target (class mkdeps *d, const char *tgt)
{
/* Only if we have no targets. */
if (d->targets.size ())
return;
if (tgt[0] == '\0')
{
__builtin_trap ();
deps_add_target (d, "-", 1);
}
...
This unfortunately triggers a bootstrap fail on IBM Z when using
--with-arch=z13 at configure time. For z13 we bump the inlining threshold so
that the inlining described above actually happens.
The right fix appears to be passing the length of the buffer along with the
buffer itself. Alternatively it might also be ok to just remove the check as
the comment above it suggests.
>From gcc-bugs-return-662453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 16:17:12 2019
Return-Path: <gcc-bugs-return-662453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100860 invoked by alias); 5 Dec 2019 16:17:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100711 invoked by uid 48); 5 Dec 2019 16:17:00 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92829] New: [10 regression] several test case failures starting with r278983
Date: Thu, 05 Dec 2019 16:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00523.txt.bz2
Content-length: 27618
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92829
Bug ID: 92829
Summary: [10 regression] several test case failures starting
with r278983
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
Some of the new test cases in the revision do not test cleanly and one old test
also now fails:
FAIL: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 117)
FAIL: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 117)
FAIL: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 117)
FAIL: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 117)
FAIL: gcc.dg/Warray-bounds-56.c (test for warnings, line 82)
FAIL: gcc.dg/Wstringop-overflow-25.c (test for warnings, line 317)
FAIL: gcc.dg/Wstringop-overflow-25.c (test for warnings, line 318)
FAIL: gcc.dg/Wstringop-overflow-25.c (test for warnings, line 319)
Details on one of the new failures:
Executing on host:
/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++98 -O2 -Wall -Wno-array-bounds -ftrack-macro-expansion=0 -S -o
Wstringop-overflow-4.s (timeout = 300)
spawn -ignore SIGHUP
/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++98 -O2 -Wall -Wno-array-bounds -ftrack-macro-expansion=0 -S -o
Wstringop-overflow-4.s
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C: In
function 'void test_strcpy_new_char(size_t)':
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:32:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 2 bytes into a region of size 1 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:36:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:40:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 4 bytes into a region of size 3 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:41:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 10 bytes into a region of size 3 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C: In
function 'void test_strcpy_new_char_array(size_t)':
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:86:3:
warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:91:3:
warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:89:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:95:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 5 bytes into a region of size 4 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:81:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 2 bytes into a region of size 1 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:83:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C: In
function 'void test_strcpy_new_int16_t(size_t)':
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:111:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:122:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 7 bytes into a region of size 6 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:123:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 10 bytes into a region of size 6 overflows the destination
[-Wstringop-overflow=]
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 32)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 36)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 40)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 41)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 81)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 83)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 86)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 89)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 91)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 95)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 111)
FAIL: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 117)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 122)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for warnings,
line 123)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++98 (test for excess errors)
Executing on host:
/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++14 -O2 -Wall -Wno-array-bounds -ftrack-macro-expansion=0 -S -o
Wstringop-overflow-4.s (timeout = 300)
spawn -ignore SIGHUP
/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++14 -O2 -Wall -Wno-array-bounds -ftrack-macro-expansion=0 -S -o
Wstringop-overflow-4.s
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C: In
function 'void test_strcpy_new_char(size_t)':
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:32:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 2 bytes into a region of size 1 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:36:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:40:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 4 bytes into a region of size 3 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:41:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 10 bytes into a region of size 3 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C: In
function 'void test_strcpy_new_char_array(size_t)':
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:86:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 1 byte into a region of size 0 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:89:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:91:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 1 byte into a region of size 0 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:95:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 5 bytes into a region of size 4 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:81:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 2 bytes into a region of size 1 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:83:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C: In
function 'void test_strcpy_new_int16_t(size_t)':
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:111:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:122:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 7 bytes into a region of size 6 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:123:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 10 bytes into a region of size 6 overflows the destination
[-Wstringop-overflow=]
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 32)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 36)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 40)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 41)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 81)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 83)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 86)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 89)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 91)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 95)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 111)
FAIL: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 117)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 122)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for warnings,
line 123)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++14 (test for excess errors)
Executing on host:
/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++17 -O2 -Wall -Wno-array-bounds -ftrack-macro-expansion=0 -S -o
Wstringop-overflow-4.s (timeout = 300)
spawn -ignore SIGHUP
/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++17 -O2 -Wall -Wno-array-bounds -ftrack-macro-expansion=0 -S -o
Wstringop-overflow-4.s
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C: In
function 'void test_strcpy_new_char(size_t)':
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:32:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 2 bytes into a region of size 1 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:36:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:40:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 4 bytes into a region of size 3 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:41:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 10 bytes into a region of size 3 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C: In
function 'void test_strcpy_new_char_array(size_t)':
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:86:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 1 byte into a region of size 0 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:89:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:91:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 1 byte into a region of size 0 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:95:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 5 bytes into a region of size 4 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:81:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 2 bytes into a region of size 1 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:83:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C: In
function 'void test_strcpy_new_int16_t(size_t)':
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:111:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:122:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 7 bytes into a region of size 6 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:123:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 10 bytes into a region of size 6 overflows the destination
[-Wstringop-overflow=]
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 32)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 36)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 40)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 41)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 81)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 83)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 86)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 89)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 91)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 95)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 111)
FAIL: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 117)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 122)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for warnings,
line 123)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++17 (test for excess errors)
Executing on host:
/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++2a -O2 -Wall -Wno-array-bounds -ftrack-macro-expansion=0 -S -o
Wstringop-overflow-4.s (timeout = 300)
spawn -ignore SIGHUP
/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++8/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++2a -O2 -Wall -Wno-array-bounds -ftrack-macro-expansion=0 -S -o
Wstringop-overflow-4.s
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C: In
function 'void test_strcpy_new_char(size_t)':
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:32:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 2 bytes into a region of size 1 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:36:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:40:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 4 bytes into a region of size 3 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:41:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 10 bytes into a region of size 3 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C: In
function 'void test_strcpy_new_char_array(size_t)':
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:86:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 1 byte into a region of size 0 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:89:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:91:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 1 byte into a region of size 0 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:95:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 5 bytes into a region of size 4 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:81:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 2 bytes into a region of size 1 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:83:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C: In
function 'void test_strcpy_new_int16_t(size_t)':
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:111:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 3 bytes into a region of size 2 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:122:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 7 bytes into a region of size 6 overflows the destination
[-Wstringop-overflow=]
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:123:3:
warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)'
writing 10 bytes into a region of size 6 overflows the destination
[-Wstringop-overflow=]
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 32)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 36)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 40)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 41)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 81)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 83)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 86)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 89)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 91)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 95)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 111)
FAIL: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 117)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 122)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for warnings,
line 123)
PASS: g++.dg/warn/Wstringop-overflow-4.C -std=gnu++2a (test for excess errors)
>From gcc-bugs-return-662454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 16:23:10 2019
Return-Path: <gcc-bugs-return-662454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121063 invoked by alias); 5 Dec 2019 16:23:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121020 invoked by uid 48); 5 Dec 2019 16:23:05 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92828] array out of bounds access in libcpp/mkdeps.c
Date: Thu, 05 Dec 2019 16:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-92828-4-5AOu7tjfpI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00524.txt.bz2
Content-length: 878
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92828
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I don't see how this will produce an out of bounds.
So we start out with:
checking if t[d->vpath[i].len] == '/'
then we check for t[d->vpath[i].len+1] == '.' and then t[d->vpath[i].len+2] ==
'.' and then t[d->vpath[i].len+3] == '/' .
None of that could cause an out of bounds for a string of "-" in the first
place.
mainly because of this:
filename_ncmp (d->vpath[i].str, t, d->vpath[i].len) //just strncmp
So some check of out of bounds (unconditional one at that) is going incorrectly
wrong.
>From gcc-bugs-return-662455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 16:40:46 2019
Return-Path: <gcc-bugs-return-662455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84719 invoked by alias); 5 Dec 2019 16:40:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84060 invoked by uid 48); 5 Dec 2019 16:40:39 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Thu, 05 Dec 2019 16:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92820-4-IuEKqdO47W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00525.txt.bz2
Content-length: 279
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
--- Comment #3 from Ian Lance Taylor <ian at airs dot com> ---
What architectures do you see it on? Do we just need to move the
.section .note.GNU-stack,"",@progbits
in runtime/go-context.S out of the #ifdef?
>From gcc-bugs-return-662456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 16:56:49 2019
Return-Path: <gcc-bugs-return-662456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13036 invoked by alias); 5 Dec 2019 16:56:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12972 invoked by uid 48); 5 Dec 2019 16:56:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92746] [10 Regression] ICE in check_noexcept_r, at cp/except.c:1114
Date: Thu, 05 Dec 2019 16:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92746-4-hwVRrP0UzZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00526.txt.bz2
Content-length: 476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92746
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |asutton at gcc dot gnu.org,
| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r278775.
>From gcc-bugs-return-662457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:02:57 2019
Return-Path: <gcc-bugs-return-662457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24002 invoked by alias); 5 Dec 2019 17:02:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23943 invoked by uid 48); 5 Dec 2019 17:02:52 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Thu, 05 Dec 2019 17:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92820-4-RIQxj2M1bo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00527.txt.bz2
Content-length: 300
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
--- Comment #4 from Matthias Klose <doko at debian dot org> ---
these are the architectures I see this:
i686-linux-gnu, s390x-linux-gnu, arm-linux-gnueabihf, arm-linux-gnueabi,
alpha-linux-gnu, powerpc-linux-gnu, sparc64-linux-gnu, sh4-linux-gnu
>From gcc-bugs-return-662458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:05:27 2019
Return-Path: <gcc-bugs-return-662458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32806 invoked by alias); 5 Dec 2019 17:05:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32771 invoked by uid 48); 5 Dec 2019 17:05:23 -0000
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92828] array out of bounds access in libcpp/mkdeps.c
Date: Thu, 05 Dec 2019 17:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: krebbel at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92828-4-AUSVBBpc5P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00528.txt.bz2
Content-length: 950
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92828
--- Comment #2 from Andreas Krebbel <krebbel at gcc dot gnu.org> ---
Created attachment 47430
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47430&action=edit
reduced testcase
on x86_64:
cc1plus -quiet -O2 t.cc -Wall --param max-inline-insns-auto=80
t.cc: In function 'void deps_add_default_target(mkdeps*, const char*)':
t.cc:47:24: warning: array subscript 2 is outside array bounds of 'const char
[2]' [-Warray-bounds]
47 | if (p[1] == '.' && p[2] == '.' && (((p[3]) == '/') || (((p[3]) ==
'\\') && (0)))) goto not_this_one;
| ~~~^
t.cc:47:42: warning: array subscript 3 is outside array bounds of 'const char
[2]' [-Warray-bounds]
47 | if (p[1] == '.' && p[2] == '.' && (((p[3]) == '/') || (((p[3]) ==
'\\') && (0)))) goto not_this_one;
| ~~~~^~
>From gcc-bugs-return-662459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:08:08 2019
Return-Path: <gcc-bugs-return-662459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36233 invoked by alias); 5 Dec 2019 17:08:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36199 invoked by uid 48); 5 Dec 2019 17:08:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92826] Impossible to silence warning: non-standard suffix on floating constant [-Wpedantic]
Date: Thu, 05 Dec 2019 17:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92826-4-MKeR9ouN18@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92826-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00529.txt.bz2
Content-length: 168
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92826
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I think this is a duplicate of an existing bug.
>From gcc-bugs-return-662460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:08:25 2019
Return-Path: <gcc-bugs-return-662460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37306 invoked by alias); 5 Dec 2019 17:08:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36861 invoked by uid 48); 5 Dec 2019 17:08:20 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92826] Impossible to silence warning: non-standard suffix on floating constant [-Wpedantic]
Date: Thu, 05 Dec 2019 17:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92826-4-ht8cbhAMYj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92826-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00530.txt.bz2
Content-length: 510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92826
--- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> ---
I thought the name "pedantic" made it clear that it is going to warn about
things that are just fine, and you shouldn't use it...
You can disable the warning by inserting __extension__ in your code. It might
be a good idea for quadmath.h to use __extension__ in its macro definitions. Or
the warning could check if the code actually lies in a system header, as so
many other warnings do.
>From gcc-bugs-return-662461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:14:39 2019
Return-Path: <gcc-bugs-return-662461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48725 invoked by alias); 5 Dec 2019 17:14:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48613 invoked by uid 48); 5 Dec 2019 17:14:35 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92828] array out of bounds access in libcpp/mkdeps.c
Date: Thu, 05 Dec 2019 17:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92828-4-jdQoHuGi9Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00531.txt.bz2
Content-length: 253
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92828
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Are you saying the warning shows up which causes the bootstrap to fail?
Because at runtime there should be no out of bounds access.
>From gcc-bugs-return-662462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:31:21 2019
Return-Path: <gcc-bugs-return-662462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98835 invoked by alias); 5 Dec 2019 17:31:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98381 invoked by uid 48); 5 Dec 2019 17:31:14 -0000
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92828] array out of bounds access in libcpp/mkdeps.c
Date: Thu, 05 Dec 2019 17:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: krebbel at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92828-4-xVXlEFvJl7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00532.txt.bz2
Content-length: 529
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92828
--- Comment #4 from Andreas Krebbel <krebbel at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> Are you saying the warning shows up which causes the bootstrap to fail?
> Because at runtime there should be no out of bounds access.
Yes. It is just the warning.
With an unknown value of d->vpath[i].len GCC cannot determine what the outcome
of the / check will be:
const char *p = t + d->vpath[i].len;
if (!IS_DIR_SEPARATOR (*p))
goto not_this_one;
>From gcc-bugs-return-662463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:35:00 2019
Return-Path: <gcc-bugs-return-662463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109151 invoked by alias); 5 Dec 2019 17:34:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109078 invoked by uid 48); 5 Dec 2019 17:34:53 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92796] [10 Regression] ICE in lra_assign, at lra-assigns.c:1646 on powerpc64le-linux-gnu
Date: Thu, 05 Dec 2019 17:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92796-4-X8TqTm9Op9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00533.txt.bz2
Content-length: 2439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92796
--- Comment #1 from Matthias Klose <doko at debian dot org> ---
$ cat acosq.i
typedef int a;
__ieee128 b();
typedef union {
__ieee128 c;
struct {
int d;
} e;
} f;
__ieee128 acosq(__ieee128 g) {
__ieee128 h, i, j, k, l, m, n, o;
a ix, p;
f q;
q.c = g;
ix = q.e.d & 5;
q.e.d = ix;
if (ix)
return g - g;
{
k = h = k * n;
i = i;
if (p)
i = l;
m = b();
o = m;
j = q.c * o;
return j;
}
}
$ /home/ubuntu/gcc/gcc-10-10-20191205/build/./gcc/xgcc
-B/home/ubuntu/gcc/gcc-10-10-20191205/build/gcc/
-B/usr/powerpc64le-linux-gnu/bin/ -B/usr/powerpc64le-linux-gnu/lib/ -Wall
-fchecking=1 -g -O2 -c acosq.i -fPIC acosq.i
during RTL pass: reload
acosq.i: In function 'acosq':
acosq.i:28:1: internal compiler error: in lra_assign, at lra-assigns.c:1646
28 | }
| ^
0x1066683b lra_assign(bool&)
../../src/gcc/lra-assigns.c:1646
0x1065f893 lra(_IO_FILE*)
../../src/gcc/lra.c:2487
0x1060499b do_reload
../../src/gcc/ira.c:5518
0x1060499b execute
../../src/gcc/ira.c:5704
Please submit a full bug report,
with preprocessed source if appropriate.
GCC configured with
--enable-languages=c,c++,go,d,fortran,objc,obj-c++
--prefix=/usr
--with-gcc-major-version-only
--program-suffix=-10
--program-prefix=powerpc64le-linux-gnu-
--enable-shared
--enable-linker-build-id
--libexecdir=/usr/lib
--without-included-gettext
--enable-threads=posix
--libdir=/usr/lib
--enable-nls
--enable-clocale=gnu
--enable-libstdcxx-debug
--enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new
--enable-gnu-unique-object
--enable-plugin
--enable-default-pie
--with-system-zlib
--disable-libphobos
--enable-objc-gc=auto
--enable-secureplt
--with-cpu=power8
--enable-targets=powerpcle-linux
--disable-multilib
--enable-multiarch
--disable-werror
--with-long-double-128
--enable-offload-targets=nvptx-none
--without-cuda-driver
--enable-checking=release
--build=powerpc64le-linux-gnu
--host=powerpc64le-linux-gnu
--target=powerpc64le-linux-gnu
>From gcc-bugs-return-662464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:36:02 2019
Return-Path: <gcc-bugs-return-662464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110401 invoked by alias); 5 Dec 2019 17:36:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110342 invoked by uid 48); 5 Dec 2019 17:35:58 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92796] [10 Regression] ICE in lra_assign, at lra-assigns.c:1646 on powerpc64le-linux-gnu
Date: Thu, 05 Dec 2019 17:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92796-4-T18qQ6Y8wc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00534.txt.bz2
Content-length: 126
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92796
--- Comment #2 from Matthias Klose <doko at debian dot org> ---
r278994
>From gcc-bugs-return-662465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:46:16 2019
Return-Path: <gcc-bugs-return-662465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12705 invoked by alias); 5 Dec 2019 17:46:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12191 invoked by uid 48); 5 Dec 2019 17:46:08 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92829] [10 regression] several test case failures starting with r278983
Date: Thu, 05 Dec 2019 17:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget cf_gcchost cf_gccbuild
Message-ID: <bug-92829-4-XYMTwmJPi9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00535.txt.bz2
Content-length: 767
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92829
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Target| |powerpc64*
Host| |powerpc64*
Build| |powerpc64*
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed on powerpc64le-unknown-linux-gnu:
https://gcc.gnu.org/ml/gcc-testresults/2019-12/msg00249.html
and powerpc64-unknown-linux-gnu
https://gcc.gnu.org/ml/gcc-testresults/2019-12/msg00248.html
but not on other targets.
>From gcc-bugs-return-662466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:46:16 2019
Return-Path: <gcc-bugs-return-662466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12809 invoked by alias); 5 Dec 2019 17:46:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11176 invoked by uid 48); 5 Dec 2019 17:45:54 -0000
From: "kim.walisch at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92826] Impossible to silence warning: non-standard suffix on floating constant [-Wpedantic]
Date: Thu, 05 Dec 2019 17:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kim.walisch at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92826-4-mC8BRdpGmf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92826-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00536.txt.bz2
Content-length: 1416
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92826
--- Comment #3 from kim.walisch at gmail dot com ---
> I thought the name "pedantic" made it clear that it is going to warn about things that are just fine, and you shouldn't use it...
A large number of projects (including mine) run automated tests using "-Wall
-Wextra -Wpedantic -Werror" and treat warnings as errors. This is why I
currently don't enable __float128 by default in my projects.
Before C++11 "long long" used to be a non standard type and GCC would print
warnings when using "long long". However GCC had an option (-Wno-long-long) to
turn these warnings off . For me the current __float128 warnings are similar to
the -Wlong-long warnings and so there should also be an option to turn these
warnings off.
And by the way, here is the disgusting hack the boost math library uses to get
rid of this warning. (And I am not even sure it works because there are people
complaining about this warning from the boost mast library on stack-overflow.)
#if defined(__GNUC__) && defined(BOOST_MATH_USE_FLOAT128)
//
// This is the only way we can avoid
// warning: non-standard suffix on floating constant [-Wpedantic]
// when building with -Wall -pedantic. Neither __extension__
// nor #pragma dianostic ignored work :(
//
#pragma GCC system_header
#endif
https://www.boost.org/doc/libs/develop/boost/math/special_functions/lambert_w.hpp
>From gcc-bugs-return-662467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:50:15 2019
Return-Path: <gcc-bugs-return-662467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23599 invoked by alias); 5 Dec 2019 17:50:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19127 invoked by uid 48); 5 Dec 2019 17:50:10 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92829] [10 regression] several test case failures starting with r278983
Date: Thu, 05 Dec 2019 17:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-92829-4-WZTRH7o10l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00537.txt.bz2
Content-length: 490
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92829
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-05
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-662469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:51:47 2019
Return-Path: <gcc-bugs-return-662469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34952 invoked by alias); 5 Dec 2019 17:51:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34908 invoked by uid 55); 5 Dec 2019 17:51:42 -0000
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Thu, 05 Dec 2019 17:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92820-4-n5UXC41P8X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00539.txt.bz2
Content-length: 504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
--- Comment #5 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Thu Dec 5 17:51:10 2019
New Revision: 279010
URL: https://gcc.gnu.org/viewcvs?rev=279010&root=gcc&view=rev
Log:
PR go/92820
runtime: always mark assembly file as non-executable stack
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/210037
Modified:
trunk/gcc/go/gofrontend/MERGE
trunk/libgo/runtime/go-context.S
>From gcc-bugs-return-662468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:51:01 2019
Return-Path: <gcc-bugs-return-662468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32473 invoked by alias); 5 Dec 2019 17:51:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32447 invoked by uid 55); 5 Dec 2019 17:50:56 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92826] Impossible to silence warning: non-standard suffix on floating constant [-Wpedantic]
Date: Thu, 05 Dec 2019 17:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92826-4-JwWnvaKenQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92826-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00538.txt.bz2
Content-length: 549
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92826
--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
TS 18661-3 has been accepted in principle for C2x, but no-one has done the
editing work needed to get it into the (LaTeX) form needed to add as an
Annex to the C standard. Once that's in, I'll update GCC so that uses of
_Float128 and the "f128" constant suffix will no longer be rejected with
-std=c2x (or -std=gnu2x) -Wpedantic (but the "q" suffix will continue to
be diagnosed).
>From gcc-bugs-return-662470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 17:52:13 2019
Return-Path: <gcc-bugs-return-662470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42240 invoked by alias); 5 Dec 2019 17:52:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41003 invoked by uid 48); 5 Dec 2019 17:52:07 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87488] hyperlink filenames in diagnostics
Date: Thu, 05 Dec 2019 17:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87488-4-tQFqJp2QxO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00540.txt.bz2
Content-length: 2328
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87488
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #13 from Tobias Burnus <burnus at gcc dot gnu.org> ---
While this works with xterm (ignored) and gnome-terminal (shows hyperlink),
but using KDE Konsole, the warnings now have:
warning: control reaches end of non-void function [\-Wreturn-type\]
That is: There are spurious \ in the output. Looking at the output of
Coreutil's 'ls --hyperlink', they use \a instead of \033\
I don't know whether there is a downside, but it seems to work fine.
The quoted reference (second link below or comment above pp_begin_url) states:
> OSC 8 ; params ; URI ST
at the beginning and
> OSC 8 ; ; ST
but not stating what ST exactly is.
Cross references:
* Coreutils: https://bugzilla.gnome.org/show_bug.cgi?id=779734 – they use '\a'
from the beginning w/o discussion
* https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda - this web
page suggests \033\
* KDE Konsole - no intention to implement it, cf.
https://bugs.kde.org/show_bug.cgi?id=379294
Assuming there is no (known) downside, I suggest to apply the patch:
diff --git a/gcc/pretty-print.c b/gcc/pretty-print.c
index c57a3dbd887..032baad0146 100644
--- a/gcc/pretty-print.c
+++ b/gcc/pretty-print.c
@@ -2052,7 +2052,7 @@ void
pp_begin_url (pretty_printer *pp, const char *url)
{
if (pp->show_urls)
- pp_printf (pp, "\33]8;;%s\33\\", url);
+ pp_printf (pp, "\33]8;;%s\a", url);
}
/* If URL-printing is enabled, write a "close URL" escape sequence to PP. */
@@ -2061,7 +2061,7 @@ void
pp_end_url (pretty_printer *pp)
{
if (pp->show_urls)
- pp_string (pp, "\33]8;;\33\\");
+ pp_string (pp, "\33]8;;\a");
}
#if CHECKING_P
@@ -2369,7 +2369,7 @@ test_urls ()
pp_begin_url (&pp, "http://example.com");
pp_string (&pp, "This is a link");
pp_end_url (&pp);
- ASSERT_STREQ ("\33]8;;http://example.com\33\\This is a link\33]8;;\33\\",
+ ASSERT_STREQ ("\33]8;;http://example.com\aThis is a link\33]8;;\a",
pp_formatted_text (&pp));
}
}
>From gcc-bugs-return-662471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 18:00:56 2019
Return-Path: <gcc-bugs-return-662471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130972 invoked by alias); 5 Dec 2019 18:00:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130743 invoked by uid 48); 5 Dec 2019 18:00:17 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Thu, 05 Dec 2019 18:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92820-4-5XHCFl1FUG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00541.txt.bz2
Content-length: 450
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
Ian Lance Taylor <ian at airs dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Ian Lance Taylor <ian at airs dot com> ---
Hopefully fixed. Let me know if not.
>From gcc-bugs-return-662472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 18:02:46 2019
Return-Path: <gcc-bugs-return-662472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7970 invoked by alias); 5 Dec 2019 18:02:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7920 invoked by uid 48); 5 Dec 2019 18:02:42 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92830] New: -fdiagnostics-url shows the wrong URL for warnings which are not in 'gcc' but e.g. in 'gfortran'
Date: Thu, 05 Dec 2019 18:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92830-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00542.txt.bz2
Content-length: 1068
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92830
Bug ID: 92830
Summary: -fdiagnostics-url shows the wrong URL for warnings
which are not in 'gcc' but e.g. in 'gfortran'
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
CC: dmalcolm at gcc dot gnu.org
Target Milestone: ---
Cf. also PR 87488
Create a file 'test.f90' with:
!-----------
print *, "Hello &
world"
end
!-----------
And run it: gfortran -Wall test.f90
This will show:
Warning: Missing ‘&’ in continued character constant at (1) [-Wampersand]
With the link:
https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wampersand
However, that's the wrong file. The correct link is:
https://gcc.gnu.org/onlinedocs/gfortran/Error-and-Warning-Options.html#index-Wampersand
>From gcc-bugs-return-662473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 18:28:41 2019
Return-Path: <gcc-bugs-return-662473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54725 invoked by alias); 5 Dec 2019 18:28:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54694 invoked by uid 48); 5 Dec 2019 18:28:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92831] New: extend_ref_init_temps_1 punts on COND_EXPRs
Date: Thu, 05 Dec 2019 18:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00543.txt.bz2
Content-length: 1618
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92831
Bug ID: 92831
Summary: extend_ref_init_temps_1 punts on COND_EXPRs
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
http://eel.is/c++draft/class.temporary#6.7
says that even ?: second and third operands need to be handled, but short
testcase modified from the standard one:
template<typename T> using id = T;
int i = 1;
int&& a = id<int[3]>{1, 2, 3}[i]; // temporary array has same
lifetime as a
const int& b = static_cast<const int&>(0); // temporary int has same lifetime
as b
int&& c = cond ? id<int[3]>{1, 2, 3}[i] : static_cast<int&&>(0);
// exactly one of the two
temporaries is lifetime-extended
like:
template<typename T> using id = T;
struct S { S () { s++; } ~S () { s--; } S (int) { s++; } static int s; };
int S::s = 0;
void
bar (bool cond)
{
if (S::s != (cond ? 7 : 5))
__builtin_abort ();
}
void
foo (bool cond)
{
int i = 1;
// temporary array has same lifetime as a
S&& a = id<S[3]>{1, 2, 3}[i];
// temporary S has same lifetime as b
const S& b = static_cast<const S&>(0);
// exactly one of the two temporaries is lifetime-extended
S&& c = cond ? id<S[3]>{1, 2, 3}[i] : static_cast<S&&>(0);
bar (cond);
}
int
main ()
{
foo (true);
foo (false);
}
fails with g++ and succeeds with clang++.
>From gcc-bugs-return-662474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 18:49:01 2019
Return-Path: <gcc-bugs-return-662474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104447 invoked by alias); 5 Dec 2019 18:49:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93506 invoked by uid 48); 5 Dec 2019 18:48:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92831] CWG1299 extend_ref_init_temps_1 punts on COND_EXPRs
Date: Thu, 05 Dec 2019 18:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc
Message-ID: <bug-92831-4-YPjfevGJ1r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00544.txt.bz2
Content-length: 627
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92831
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
Summary|extend_ref_init_temps_1 |CWG1299
|punts on COND_EXPRs |extend_ref_init_temps_1
| |punts on COND_EXPRs
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Seems this is http://wg21.link/p0727 aka CWG 1299.
>From gcc-bugs-return-662475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 18:53:42 2019
Return-Path: <gcc-bugs-return-662475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126751 invoked by alias); 5 Dec 2019 18:53:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126717 invoked by uid 48); 5 Dec 2019 18:53:38 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92832] New: valgrind error in incorporate_penalties
Date: Thu, 05 Dec 2019 18:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00545.txt.bz2
Content-length: 1502
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
Bug ID: 92832
Summary: valgrind error in incorporate_penalties
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
I just tried a valgrind build of gcc revision 279000 and got this:
==2020328== Conditional jump or move depends on uninitialised value(s)
==2020328== at 0x1488041: incorporate_penalties (ipa-cp.c:3174)
==2020328== by 0x1488041: good_cloning_opportunity_p(cgraph_node*, int, int,
profile_count, int) (ipa-cp.c:3230)
==2020328== by 0x14929CA: bool decide_about_value<tree_node*>(cgraph_node*,
int, long, ipcp_value<tree_node*>*, vec<tree_node*, va_heap, vl_ptr>,
vec<ipa_polymorphic_call_context, va_heap, vl_ptr>) (ipa-cp.c:5327)
==2020328== by 0x1494494: decide_whether_version_node (ipa-cp.c:5397)
svn blame says
278893 fxue if (info->node_within_scc && !info->node_is_self_scc)
Configure script is
../trunk/configure --prefix=/home/dcb/gcc/results.279000.valgrind \
--disable-bootstrap \
--disable-multilib \
--disable-werror \
--enable-checking=valgrind \
--enable-languages=c,c++,fortran
sed 's/-O2/-O3/' < Makefile > Makefile.tmp
mv Makefile.tmp Makefile
>From gcc-bugs-return-662476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 18:59:19 2019
Return-Path: <gcc-bugs-return-662476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26413 invoked by alias); 5 Dec 2019 18:59:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26340 invoked by uid 48); 5 Dec 2019 18:59:09 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87488] hyperlink filenames in diagnostics
Date: Thu, 05 Dec 2019 18:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87488-4-wqmWZKcazl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00546.txt.bz2
Content-length: 551
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87488
--- Comment #14 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks.
systemd also uses '\a':
https://github.com/systemd/systemd/blob/master/src/shared/pretty-print.c#L53
n = strjoin("\x1B]8;;", url, "\a", text, "\x1B]8;;\a");
I didn't see your update to this BZ after our discussion on IRC, and
independently came up with the same patch as your one in comment #13, so I
think that's the right approach.
Shall I go ahead and bootstrap/test/commit the patch, or do you want to?
>From gcc-bugs-return-662477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 19:01:12 2019
Return-Path: <gcc-bugs-return-662477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28134 invoked by alias); 5 Dec 2019 19:01:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27905 invoked by uid 48); 5 Dec 2019 19:00:52 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87488] hyperlink filenames in diagnostics
Date: Thu, 05 Dec 2019 19:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87488-4-H3jB0kgwwW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00547.txt.bz2
Content-length: 246
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87488
--- Comment #15 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
I guess the other thing to test it on is on older gnome terminals that predate
the support - but I don't have one handy.
>From gcc-bugs-return-662479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 19:04:54 2019
Return-Path: <gcc-bugs-return-662479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41093 invoked by alias); 5 Dec 2019 19:04:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32933 invoked by uid 48); 5 Dec 2019 19:04:47 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92833] New: ice for broken C code
Date: Thu, 05 Dec 2019 19:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00549.txt.bz2
Content-length: 978
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92833
Bug ID: 92833
Summary: ice for broken C code
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
For this list of C tokens:
char
<<
<<
<<
recent gcc trunk deals with it in a less than tidy fashion:
destDir/crash0.c:2:2: error: expected identifier or ‘(’ before ‘<<’ token
2 | <<
| ^~
destDir/crash0.c:4:2: internal compiler error: Segmentation fault
4 | <<
| ^~
0xeaa5a7 crash_signal
../../trunk/gcc/toplev.c:328
0x1994284 _cpp_lex_direct
../../trunk/libcpp/lex.c:2725
0x1995cc0 _cpp_lex_token
../../trunk/libcpp/lex.c:2608
0x199fc47 cpp_get_token_1
../../trunk/libcpp/macro.c:2707
>From gcc-bugs-return-662478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 19:04:51 2019
Return-Path: <gcc-bugs-return-662478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38796 invoked by alias); 5 Dec 2019 19:04:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31420 invoked by uid 48); 5 Dec 2019 19:04:45 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92831] CWG1299 extend_ref_init_temps_1 punts on COND_EXPRs
Date: Thu, 05 Dec 2019 19:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-92831-4-NgSN75XazH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00548.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92831
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-05
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-662480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 19:05:50 2019
Return-Path: <gcc-bugs-return-662480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117772 invoked by alias); 5 Dec 2019 19:05:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107051 invoked by uid 48); 5 Dec 2019 19:05:42 -0000
From: "egmont at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87488] hyperlink filenames in diagnostics
Date: Thu, 05 Dec 2019 19:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egmont at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87488-4-0jYaWMJYRK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00550.txt.bz2
Content-length: 1409
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87488
--- Comment #16 from Egmont Koblinger <egmont at gmail dot com> ---
(In reply to Tobias Burnus from comment #13)
> but using KDE Konsole, the warnings now have:
>
> warning: control reaches end of non-void function [\-Wreturn-type\]
>
> That is: There are spurious \ in the output.
This has recently been fixed and is going to be released in konsole 19.12. See
https://bugs.kde.org/show_bug.cgi?id=231405 for details.
I don't know when gcc 10 planned to be released, but if later than that then
very few users will hit this bug (and as far as I understand, they can still
disable this formatting in gcc, correct?).
> The quoted reference [...] but not stating what ST exactly is.
Please read that reference again carefully, it _does_ state what ST is. ECMA-48
also states what it is, and states it as the only terminator for an OSC
(section 8.3.89).
Contrary, BEL is a nonstandard extension.
That's why the OSC 8 spec also uses ST.
> Assuming there is no (known) downside
There is no practical downside I'm aware of, except that you would switch from
the official standard solution to an unofficial nonstandard one.
Should you do it in order to workaround a terminal emulator which failed to fix
this bug for 9.5 years after it was reported? Or should you comply with the
standards and blame them for this mistake? Your call.
>From gcc-bugs-return-662481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 19:08:30 2019
Return-Path: <gcc-bugs-return-662481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72585 invoked by alias); 5 Dec 2019 19:08:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72523 invoked by uid 48); 5 Dec 2019 19:08:26 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92796] [10 Regression] ICE in lra_assign, at lra-assigns.c:1646 on powerpc64le-linux-gnu
Date: Thu, 05 Dec 2019 19:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92796-4-RsuWru3pQ9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00551.txt.bz2
Content-length: 552
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92796
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |segher at gcc dot gnu.org
--- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Hi!
I cannot reproduce it, and neither can Peter. What are we missing?
That revision cannot be correct, btw, it doesn't touch any file involved
in this build.
>From gcc-bugs-return-662482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 19:13:19 2019
Return-Path: <gcc-bugs-return-662482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92669 invoked by alias); 5 Dec 2019 19:13:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 92631 invoked by uid 48); 5 Dec 2019 19:13:14 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92833] ice for broken C code
Date: Thu, 05 Dec 2019 19:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92833-4-dPjh1JDZNS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00552.txt.bz2
Content-length: 695
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92833
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |error-recovery,
| |ice-on-invalid-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-05
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-662483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 19:19:06 2019
Return-Path: <gcc-bugs-return-662483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11543 invoked by alias); 5 Dec 2019 19:19:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11465 invoked by uid 48); 5 Dec 2019 19:18:59 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92796] [10 Regression] ICE in lra_assign, at lra-assigns.c:1646 on powerpc64le-linux-gnu
Date: Thu, 05 Dec 2019 19:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92796-4-mhCl6Mff4A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00553.txt.bz2
Content-length: 308
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92796
--- Comment #4 from Matthias Klose <doko at debian dot org> ---
the revision always is the one from the LAST_UPDATED file.
This was a build on Ubuntu, which has more hardening flags enabled by default.
I'll recheck with a build on Debian unstable.
>From gcc-bugs-return-662484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 19:35:53 2019
Return-Path: <gcc-bugs-return-662484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31348 invoked by alias); 5 Dec 2019 19:35:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31272 invoked by uid 48); 5 Dec 2019 19:35:48 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92796] [10 Regression] ICE in lra_assign, at lra-assigns.c:1646 on powerpc64le-linux-gnu
Date: Thu, 05 Dec 2019 19:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-92796-4-PHKBJPX48v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00554.txt.bz2
Content-length: 646
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92796
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-05
Ever confirmed|0 |1
--- Comment #5 from Peter Bergner <bergner at gcc dot gnu.org> ---
Actually, I got it to ICE. I had to add -fstack-protector-strong to my
options, which your compile was adding automatically due to your configure
options. I'll have a look.
>From gcc-bugs-return-662485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:03:50 2019
Return-Path: <gcc-bugs-return-662485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67956 invoked by alias); 5 Dec 2019 20:03:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67899 invoked by uid 48); 5 Dec 2019 20:03:40 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92622] FAIL: gcc.dg/Warray-bounds-22.c on ILP32: missing warnings for VLA on lines 67 and 69
Date: Thu, 05 Dec 2019 20:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92622-4-O5bzOZ0Jk1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92622-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92622-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00555.txt.bz2
Content-length: 972
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92622
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
The reduced test case below reproduces the spurious nature of the failure
outside the test harness:
$ (set -x; cat t.c && for i in 1 2 3; do gcc -O2 -S -Warray-bounds
-ftrack-macro-expansion=0 -m32 t.c ; done)
+ cat t.c
#define DIFF_MAX __PTRDIFF_MAX__
#define DIFF_MIN (-DIFF_MAX - 1)
void f (int);
void g (unsigned m, unsigned n)
{
char a[m][n];
f (a[0][DIFF_MAX]);
}
+ for i in 1 2 3
+ gcc -O2 -S -Warray-bounds -ftrack-macro-expansion=0 -m32 t.c
t.c: In function ‘g’:
t.c:10:10: warning: array subscript 2147483647 is above array bounds of
‘char[<U5cf0> + 1]’ [-Warray-bounds]
10 | f (a[0][DIFF_MAX]);
| ~~~~^~~~~~~~~~
+ for i in 1 2 3
+ gcc -O2 -S -Warray-bounds -ftrack-macro-expansion=0 -m32 t.c
+ for i in 1 2 3
+ gcc -O2 -S -Warray-bounds -ftrack-macro-expansion=0 -m32 t.c
$
>From gcc-bugs-return-662487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:07:29 2019
Return-Path: <gcc-bugs-return-662487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77156 invoked by alias); 5 Dec 2019 20:07:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76434 invoked by uid 55); 5 Dec 2019 20:07:22 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92271] for consistency, __is_same_as should be named __is_same
Date: Thu, 05 Dec 2019 20:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92271-4-UeraQw5bgz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92271-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92271-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00557.txt.bz2
Content-length: 1025
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92271
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Thu Dec 5 20:06:46 2019
New Revision: 279018
URL: https://gcc.gnu.org/viewcvs?rev=279018&root=gcc&view=rev
Log:
PR c++/92271 - make __is_same alias for __is_same_as.
Richard Smith proposed adding a synonym for __is_same_as, to accomodate the
convention of exposing std::SOME_TRAIT<A, B>::value as __SOME_TRAIT(A, B).
So add that alias, and also adjust the C++ printer. I didn't bother changing
the RID_ identifier.
* c-common.c: Add __is_same, an alias for __is_same_as.
* cxx-pretty-print.c (pp_cxx_trait_expression) <case CPTK_IS_SAME_AS>:
Print "__is_same".
* g++.dg/ext/is_same.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/ext/is_same.C
Modified:
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-common.c
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cxx-pretty-print.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:07:06 2019
Return-Path: <gcc-bugs-return-662486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74471 invoked by alias); 5 Dec 2019 20:07:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73833 invoked by uid 48); 5 Dec 2019 20:07:01 -0000
From: "christoph.muellner@theobroma-systems.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92800] IPA escape analysis for structs
Date: Thu, 05 Dec 2019 20:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: christoph.muellner@theobroma-systems.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92800-4-DzmYCxpz6m@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92800-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92800-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00556.txt.bz2
Content-length: 245
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92800
--- Comment #2 from Christoph Müllner <christoph.muellner@theobroma-systems.com> ---
Thanks for mentioning that.
We have an upcoming conf call with Marvell where we will discuss this.
>From gcc-bugs-return-662488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:08:11 2019
Return-Path: <gcc-bugs-return-662488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80604 invoked by alias); 5 Dec 2019 20:08:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80524 invoked by uid 48); 5 Dec 2019 20:08:05 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92271] for consistency, __is_same_as should be named __is_same
Date: Thu, 05 Dec 2019 20:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92271-4-UkVKdXmbTc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92271-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92271-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00558.txt.bz2
Content-length: 428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92271
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Done.
>From gcc-bugs-return-662490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:13:50 2019
Return-Path: <gcc-bugs-return-662490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99992 invoked by alias); 5 Dec 2019 20:13:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99065 invoked by uid 55); 5 Dec 2019 20:13:41 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91353] Implement P1331R2: Permitting trivial default initialization in constexpr contexts
Date: Thu, 05 Dec 2019 20:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.1.1
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91353-4-9sGv7DfQBz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91353-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91353-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00560.txt.bz2
Content-length: 5201
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91353
--- Comment #8 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Thu Dec 5 20:13:03 2019
New Revision: 279019
URL: https://gcc.gnu.org/viewcvs?rev=279019&root=gcc&view=rev
Log:
PR c++/91353 - P1331R2: Allow trivial default init in constexpr
contexts.
This patch implements C++20 P1331, allowing trivial default initialization in
constexpr contexts.
* c-cppbuiltin.c (c_cpp_builtins): Adjust the value of __cpp_constexpr.
* class.c (trivial_default_constructor_is_constexpr): Return true in
C++20.
* constexpr.c (cx_check_missing_mem_inits): Allow missing field
initializers in C++20.
(cxx_eval_call_expression): Don't clear CONSTRUCTOR_NO_CLEARING for
constexpr constructors in C++20.
(reduced_constant_expression_p): Don't set FIELD for union and array
types. Skip empty class fields without initializers.
* decl.c (check_for_uninitialized_const_var): Permit trivial default
initialization in constexpr.
(next_initializable_field): Don't skip vptr fields.
* method.c (walk_field_subobs): Still consider a constructor that
doesn't initialize all the members constexpr.
* g++.dg/cpp0x/constexpr-array6.C: Adjust dg-error.
* g++.dg/cpp0x/constexpr-ctor.C: Likewise.
* g++.dg/cpp0x/constexpr-diag3.C: Likewise.
* g++.dg/cpp0x/constexpr-diag4.C: Likewise.
* g++.dg/cpp0x/constexpr-ex3.C: Likewise.
* g++.dg/cpp0x/constexpr-template2.C: Likewise.
* g++.dg/cpp0x/constexpr-union2.C: Likewise.
* g++.dg/cpp0x/lambda/lambda-mangle.C: Rip out a piece of code ...
* g++.dg/cpp0x/lambda/lambda-mangle6.C: ... and put it here.
* g++.dg/cpp0x/pr79118.C: Adjust dg-error.
* g++.dg/cpp1y/constexpr-83921-3.C: Likewise.
* g++.dg/cpp1y/constexpr-neg1.C: Likewise.
* g++.dg/cpp1z/constexpr-lambda12.C: Likewise.
* g++.dg/cpp1z/feat-cxx1z.C: Use -std=c++17.
* g++.dg/cpp2a/constexpr-init1.C: New test.
* g++.dg/cpp2a/constexpr-init2.C: New test.
* g++.dg/cpp2a/constexpr-init3.C: New test.
* g++.dg/cpp2a/constexpr-init4.C: New test.
* g++.dg/cpp2a/constexpr-init5.C: New test.
* g++.dg/cpp2a/constexpr-init6.C: New test.
* g++.dg/cpp2a/constexpr-init7.C: New test.
* g++.dg/cpp2a/constexpr-init8.C: New test.
* g++.dg/cpp2a/constexpr-init9.C: New test.
* g++.dg/cpp2a/constexpr-init10.C: New test.
* g++.dg/cpp2a/constexpr-init11.C: New test.
* g++.dg/cpp2a/constexpr-init12.C: New test.
* g++.dg/cpp2a/constexpr-init13.C: New test.
* g++.dg/cpp2a/constexpr-init14.C: New test.
* g++.dg/cpp2a/constexpr-init15.C: New test.
* g++.dg/cpp2a/constexpr-try5.C: Adjust dg-error.
* g++.dg/cpp2a/feat-cxx2a.C: Test __cpp_constexpr.
* g++.dg/cpp2a/lambda-mangle.C: New test.
* g++.dg/debug/dwarf2/pr44641.C: Skip for c++2a.
* g++.dg/ext/stmtexpr21.C: Adjust dg-error.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/lambda/lambda-mangle6.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init1.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init10.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init11.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init12.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init13.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init14.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init15.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init2.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init3.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init4.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init5.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init6.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init7.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init8.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-init9.C
trunk/gcc/testsuite/g++.dg/cpp2a/lambda-mangle.C
Modified:
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-cppbuiltin.c
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/class.c
trunk/gcc/cp/constexpr.c
trunk/gcc/cp/decl.c
trunk/gcc/cp/method.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-array6.C
trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-ctor.C
trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-diag3.C
trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-diag4.C
trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-ex3.C
trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-template2.C
trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-union2.C
trunk/gcc/testsuite/g++.dg/cpp0x/lambda/lambda-mangle.C
trunk/gcc/testsuite/g++.dg/cpp0x/pr79118.C
trunk/gcc/testsuite/g++.dg/cpp1y/constexpr-83921-3.C
trunk/gcc/testsuite/g++.dg/cpp1y/constexpr-neg1.C
trunk/gcc/testsuite/g++.dg/cpp1z/constexpr-lambda12.C
trunk/gcc/testsuite/g++.dg/cpp2a/constexpr-try5.C
trunk/gcc/testsuite/g++.dg/cpp2a/feat-cxx2a.C
trunk/gcc/testsuite/g++.dg/debug/dwarf2/pr44641.C
trunk/gcc/testsuite/g++.dg/ext/stmtexpr21.C
>From gcc-bugs-return-662489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:13:23 2019
Return-Path: <gcc-bugs-return-662489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95447 invoked by alias); 5 Dec 2019 20:13:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94574 invoked by uid 48); 5 Dec 2019 20:13:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92831] CWG1299 extend_ref_init_temps_1 punts on COND_EXPRs
Date: Thu, 05 Dec 2019 20:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92831-4-urmKjGxEze@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00559.txt.bz2
Content-length: 2518
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92831
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Even better testcase that has nested COND_EXPRs:
template<typename T> using id = T;
struct S { S () { s++; } ~S () { s--; } S (int) { s++; } static int s; };
int S::s = 0;
void
bar (bool cond, bool cond2)
{
if (S::s != (cond ? cond2 ? 7 : 5 : cond2 ? 8 : 9))
__builtin_abort ();
}
void
foo (bool cond, bool cond2)
{
int i = 1;
// temporary array has same lifetime as a
S&& a = id<S[3]>{1, 2, 3}[i];
// temporary S has same lifetime as b
const S& b = static_cast<const S&>(0);
// exactly one of the four temporaries is lifetime-extended
S&& c = cond ? cond2 ? id<S[3]>{1, 2, 3}[i] : static_cast<S&&>(0)
: cond2 ? id<S[4]>{1, 2, 3, 4}[i] : id<S[5]>{1, 2, 3, 4, 5}[i];
bar (cond, cond2);
}
int
main ()
{
foo (true, true);
foo (true, false);
foo (false, true);
foo (false, false);
}
--- gcc/cp/call.c.jj 2019-12-05 10:03:04.110181312 +0100
+++ gcc/cp/call.c 2019-12-05 20:35:08.386092965 +0100
@@ -12153,12 +12153,19 @@ extend_ref_init_temps_1 (tree decl, tree
= extend_ref_init_temps_1 (decl, TREE_OPERAND (sub, 1), cleanups);
return init;
}
+ if (TREE_CODE (sub) == COND_EXPR)
+ {
+ TREE_OPERAND (sub, 1)
+ = extend_ref_init_temps_1 (decl, TREE_OPERAND (sub, 1), cleanups);
+ TREE_OPERAND (sub, 2)
+ = extend_ref_init_temps_1 (decl, TREE_OPERAND (sub, 2), cleanups);
+ return init;
+ }
if (TREE_CODE (sub) != ADDR_EXPR)
return init;
/* Deal with binding to a subobject. */
for (p = &TREE_OPERAND (sub, 0);
- (TREE_CODE (*p) == COMPONENT_REF
- || TREE_CODE (*p) == ARRAY_REF); )
+ TREE_CODE (*p) == COMPONENT_REF || TREE_CODE (*p) == ARRAY_REF; )
p = &TREE_OPERAND (*p, 0);
if (TREE_CODE (*p) == TARGET_EXPR)
{
isn't sufficient, because if there are any cleanups added by either of the
recursive calls, we need to conditionalize those cleanups on whether the
particular COND_EXPR's first operand evaluated to true or false. I think
cp_save_expr won't do it for the nested cases though, because the SAVE_EXPR
might end up not being initialized. So we need to arrange for a bool temporary
that will be initialized to say false early, before the first COND_EXPR is
encountered, set it to true at the start of corresponding init code and wrap
cleanups with that guard.
Any better ideas?
>From gcc-bugs-return-662491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:18:19 2019
Return-Path: <gcc-bugs-return-662491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110254 invoked by alias); 5 Dec 2019 20:18:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110179 invoked by uid 48); 5 Dec 2019 20:18:14 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92834] New: misssed SLP vectorization in LightPixel
Date: Thu, 05 Dec 2019 20:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00561.txt.bz2
Content-length: 668
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92834
Bug ID: 92834
Summary: misssed SLP vectorization in LightPixel
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
Target Milestone: ---
Created attachment 47431
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47431&action=edit
simplified testcase
Clang is able to vectorize LightPixel which leads to about 10% improvements in
rasterflood-svg Firefox benchmark.
>From gcc-bugs-return-662492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:23:18 2019
Return-Path: <gcc-bugs-return-662492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118899 invoked by alias); 5 Dec 2019 20:23:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118843 invoked by uid 48); 5 Dec 2019 20:23:11 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92825] Unnecesary stack protection in Firefox's LightPixel.
Date: Thu, 05 Dec 2019 20:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-92825-4-TKSKTusEVh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92825-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00562.txt.bz2
Content-length: 701
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92825
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Unnecesary stack protection |Unnecesary stack protection
|and missed SLP |in Firefox's LightPixel.
|vectorization in Firefox's |
|LightPixel. |
--- Comment #2 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I have filled separate bug for the SLP issue so we do not mix multiple things
in one PR.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92834
>From gcc-bugs-return-662493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:41:16 2019
Return-Path: <gcc-bugs-return-662493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28569 invoked by alias); 5 Dec 2019 20:41:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27547 invoked by uid 48); 5 Dec 2019 20:41:09 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91353] Implement P1331R2: Permitting trivial default initialization in constexpr contexts
Date: Thu, 05 Dec 2019 20:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.1.1
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91353-4-ogKtGX2HI9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91353-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91353-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00563.txt.bz2
Content-length: 446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91353
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Implemented for GCC 10.
>From gcc-bugs-return-662495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:41:20 2019
Return-Path: <gcc-bugs-return-662495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29251 invoked by alias); 5 Dec 2019 20:41:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28149 invoked by uid 48); 5 Dec 2019 20:41:13 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88323] implement C++20 language features.
Date: Thu, 05 Dec 2019 20:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88323-4-bQQt6qU8jC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88323-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88323-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00564.txt.bz2
Content-length: 510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88323
Bug 88323 depends on bug 91353, which changed state.
Bug 91353 Summary: Implement P1331R2: Permitting trivial default initialization in constexpr contexts
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91353
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-662494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:41:18 2019
Return-Path: <gcc-bugs-return-662494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28967 invoked by alias); 5 Dec 2019 20:41:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27950 invoked by uid 48); 5 Dec 2019 20:41:12 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55004] [meta-bug] constexpr issues
Date: Thu, 05 Dec 2019 20:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-55004-4-lW3er4lbD0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55004-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55004-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00565.txt.bz2
Content-length: 510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004
Bug 55004 depends on bug 91353, which changed state.
Bug 91353 Summary: Implement P1331R2: Permitting trivial default initialization in constexpr contexts
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91353
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-662496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:42:08 2019
Return-Path: <gcc-bugs-return-662496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36502 invoked by alias); 5 Dec 2019 20:42:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35566 invoked by uid 48); 5 Dec 2019 20:42:01 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92833] ice for broken C code
Date: Thu, 05 Dec 2019 20:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92833-4-2N8Rx7fYAz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00566.txt.bz2
Content-length: 198
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92833
--- Comment #2 from David Binderman <dcb314 at hotmail dot com> ---
Something similar for this list of tokens:
extern
==
==
==
>From gcc-bugs-return-662497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 20:53:22 2019
Return-Path: <gcc-bugs-return-662497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69301 invoked by alias); 5 Dec 2019 20:53:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69259 invoked by uid 48); 5 Dec 2019 20:53:17 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92622] FAIL: gcc.dg/Warray-bounds-22.c on ILP32: missing warnings for VLA on lines 67 and 69
Date: Thu, 05 Dec 2019 20:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-92622-4-zaCyWNxZQ4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92622-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92622-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00567.txt.bz2
Content-length: 1186
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92622
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
I think I see the problem. It's due to the use of an uninitialized variable.
The patch below fixes it:
Index: gcc/tree-vrp.c
===================================================================
--- gcc/tree-vrp.c (revision 279008)
+++ gcc/tree-vrp.c (working copy)
@@ -3544,7 +3544,7 @@ vrp_prop::check_array_ref (location_t location, tr
decl = base;
}
- if (known_gt (off, 0))
+ if (base && known_gt (off, 0))
maxbound = wide_int_to_tree (sizetype,
wi::sub (wi::to_wide (maxbound),
off));
>From gcc-bugs-return-662498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 21:41:13 2019
Return-Path: <gcc-bugs-return-662498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95081 invoked by alias); 5 Dec 2019 21:41:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95035 invoked by uid 48); 5 Dec 2019 21:41:08 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84255] accepts redefinition of template variable
Date: Thu, 05 Dec 2019 21:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on
Message-ID: <bug-84255-4-2pGEylSvsu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84255-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84255-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00568.txt.bz2
Content-length: 484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84255
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2018-02-06 00:00:00 |2019-12-5
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Still present on trunk. Slightly reduced:
template<typename> bool var = false;
template<typename> bool var = true;
>From gcc-bugs-return-662499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 21:43:47 2019
Return-Path: <gcc-bugs-return-662499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97134 invoked by alias); 5 Dec 2019 21:43:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97066 invoked by uid 48); 5 Dec 2019 21:43:42 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92576] Definition of variable template without initializer is treated as declaration
Date: Thu, 05 Dec 2019 21:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also
Message-ID: <bug-92576-4-ixHjzZYD8M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92576-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92576-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00569.txt.bz2
Content-length: 716
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92576
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=84255,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=68012
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I think accepting the invalid first definition is PR 68012.
Accepting the second definition is PR 84255.
>From gcc-bugs-return-662501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 21:57:26 2019
Return-Path: <gcc-bugs-return-662501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126464 invoked by alias); 5 Dec 2019 21:57:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126240 invoked by uid 48); 5 Dec 2019 21:57:21 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92206] [10 Regression] ICE in strip_typedefs, at cp/tree.c:1682 since r277281
Date: Thu, 05 Dec 2019 21:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92206-4-pDSrkei6dA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92206-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92206-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00571.txt.bz2
Content-length: 185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92206
--- Comment #13 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
*** Bug 92441 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-662500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 21:57:24 2019
Return-Path: <gcc-bugs-return-662500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126322 invoked by alias); 5 Dec 2019 21:57:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126153 invoked by uid 48); 5 Dec 2019 21:57:19 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92441] [10 regression] ICE: in strip_typedefs, at cp/tree.c:1681
Date: Thu, 05 Dec 2019 21:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-92441-4-jWGhAXBFhB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92441-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92441-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00570.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92441
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |mpolacek at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
This has been fixed, assuming it's a dup of 92206.
*** This bug has been marked as a duplicate of bug 92206 ***
>From gcc-bugs-return-662502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 22:24:34 2019
Return-Path: <gcc-bugs-return-662502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73081 invoked by alias); 5 Dec 2019 22:24:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72917 invoked by uid 48); 5 Dec 2019 22:24:01 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84255] accepts redefinition of template variable
Date: Thu, 05 Dec 2019 22:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84255-4-3BHd8N6QdC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84255-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84255-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00572.txt.bz2
Content-length: 733
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84255
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
This should probably be caught in redeclaration_error_message but isn't because
2991 if (TREE_CODE (DECL_TEMPLATE_RESULT (newdecl)) != FUNCTION_DECL
2992 || (DECL_TEMPLATE_RESULT (newdecl)
2993 == DECL_TEMPLATE_RESULT (olddecl)))
2994 return NULL;
and here DECL_TEMPLATE_RESULT is a VAR_DECL.
>From gcc-bugs-return-662503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 22:27:12 2019
Return-Path: <gcc-bugs-return-662503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81256 invoked by alias); 5 Dec 2019 22:27:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81183 invoked by uid 48); 5 Dec 2019 22:27:08 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Thu, 05 Dec 2019 22:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc see_also
Message-ID: <bug-92820-4-zU2hMUiFDU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00573.txt.bz2
Content-length: 562
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=28036
--- Comment #7 from Eric Gallager <egallager at gcc dot gnu.org> ---
related: bug 28036
>From gcc-bugs-return-662504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 22:29:05 2019
Return-Path: <gcc-bugs-return-662504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83028 invoked by alias); 5 Dec 2019 22:29:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82950 invoked by uid 48); 5 Dec 2019 22:28:58 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/92453] write buffer overflow in cplus_demangle()
Date: Thu, 05 Dec 2019 22:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_file_loc cc
Message-ID: <bug-92453-4-cpgpS7pPxI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92453-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92453-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00574.txt.bz2
Content-length: 974
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92453
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
URL| |https://gcc.gnu.org/ml/gcc-
| |patches/2019-11/msg02682.ht
| |ml
CC| |egallager at gcc dot gnu.org
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Tim Ruehsen from comment #3)
> (In reply to Christian Biesinger from comment #2)
> > Could you send your patch to gcc-patches per
> > https://gcc.gnu.org/contribute.html#patches ? Thanks!
>
> I did that some days ago:
> https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02682.html
adding "patch" keyword then
>From gcc-bugs-return-662505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 22:31:07 2019
Return-Path: <gcc-bugs-return-662505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96164 invoked by alias); 5 Dec 2019 22:31:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86665 invoked by uid 48); 5 Dec 2019 22:30:44 -0000
From: "caplanr at predsci dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92835] New: [OpenACC] Run time error with enter./exit data
Date: Thu, 05 Dec 2019 22:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: caplanr at predsci dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00575.txt.bz2
Content-length: 689
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92835
Bug ID: 92835
Summary: [OpenACC] Run time error with enter./exit data
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: caplanr at predsci dot com
CC: jakub at gcc dot gnu.org
Target Milestone: ---
I am trying to compile and run my OpenACC code with GNU 9.1.0 branch.
I am getting the following error:
libgomp: >>>> GOACC_enter_exit_data UNHANDLED kind 0x01
What does this mean? My code works fine with PGI.
>From gcc-bugs-return-662506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 22:42:50 2019
Return-Path: <gcc-bugs-return-662506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15723 invoked by alias); 5 Dec 2019 22:42:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15706 invoked by uid 89); 5 Dec 2019 22:42:49 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=0.9 required=5.0 tests=AWL,BAYES_50,HTML_IMAGE_RATIO_04,HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=budget, Roboto, roboto, 400,400i,700,700i
X-HELO: expresspostermachine.com
Received: from expresspostermachine.com (HELO expresspostermachine.com) (74.208.26.91) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 05 Dec 2019 22:42:46 +0000
Received: from postermakerstudio.com (unknown [74.208.87.98]) by localhost.localdomain (Postfix) with ESMTPSA id D12B4F3476 for <gcc-bugs@gcc.gnu.org>; Thu, 5 Dec 2019 22:40:06 +0000 (UTC)
Date: Thu, 05 Dec 2019 22:42:00 -0000
To: gcc-bugs@gcc.gnu.org
From: Poster Studio <schools@expresspostermachine.com>
Reply-To: Poster Studio <schools@expresspostermachine.com>
Subject: A Poster Maker For Your School
Message-ID: <63GzYndM618wifSfzgiQG1LN2KgJI49ehr87rWydfxQ@postermakerstudio.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-SW-Source: 2019-12/txt/msg00576.txt.bz2
Content-length: 6295
Can't see this email?. View in browser
Make Giant School PostersWith One Button!
True, Full Color Letter-To-Poster!
With the Poster Studio Express, you can quickly and easily create giant posters by scanning letter sized originals and pressing one button!
Poster Makers Available In 13", 24", 36" 44" and 60" Sizes!
With the Poster Studio Express, any teacher or staff member can create wildly elaborate and engaging posters by simply pressing one button!No more expensive trips to your local printing store!
With Our Poster Templates,
Creativity Is Included.
The Poster Studio Express includes 100's of templates, 1,000's of fonts, and 100's of thousands of images! All making up the easiest and most complete way to quickly and easily produce economical, engaging and captivating classroom visuals that last!
Read More
We have packages available to suit any budget!
Visit Our Website For More Information
You are receiving this email because you have visited our site or asked us about the regular newsletter. This is a commercial email sent by Red Circle Solutions LLC. Poster Studio Express is a registered trademark of Red Circle Solutions. © 2019 Red Circle Solutions. 103 Godwin Ave, PMB 255, Midland Park, NJ 07432. 877-798-8951
Unsubscribe
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug tree-optimization/92714] [missed-optimization] aggregate initialization of an array fills the whole array with zeros first, including leading non-zero elements
[not found] <bug-92714-4@http.gcc.gnu.org/bugzilla/>
2019-11-29 9:01 ` [Bug middle-end/92714] [missed-optimization] aggregate initialization of an array fills the whole array with zeros first, including leading non-zero elements jakub at gcc dot gnu.org
@ 2021-12-22 10:06 ` pinskia at gcc dot gnu.org
1 sibling, 0 replies; 2+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-12-22 10:06 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92714
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|middle-end |tree-optimization
Severity|normal |enhancement
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-12-22 10:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-92714-4@http.gcc.gnu.org/bugzilla/>
2019-11-29 9:01 ` [Bug middle-end/92714] [missed-optimization] aggregate initialization of an array fills the whole array with zeros first, including leading non-zero elements jakub at gcc dot gnu.org
2021-12-22 10:06 ` [Bug tree-optimization/92714] " pinskia at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).