public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/61577] [4.9.0] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
@ 2014-06-21 11:01 ` FBergemann at web dot de
2015-10-15 11:04 ` [Bug target/61577] " josephpattara at gmail dot com
` (78 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: FBergemann at web dot de @ 2014-06-21 11:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
Frank Bergemann <FBergemann at web dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|blocker |major
--- Comment #2 from Frank Bergemann <FBergemann at web dot de> ---
Change importance.
First problem, that was hit, is about the native 'ld'.
Second problem could be stack size issue (however stack size used on hpux is
larger than used on other reference systems).
\Frank
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
2014-06-21 11:01 ` [Bug c++/61577] [4.9.0] can't compile on hp-ux v3 ia64 FBergemann at web dot de
@ 2015-10-15 11:04 ` josephpattara at gmail dot com
2015-10-19 11:34 ` josephpattara at gmail dot com
` (77 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: josephpattara at gmail dot com @ 2015-10-15 11:04 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
Joseph John <josephpattara at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |josephpattara at gmail dot com
--- Comment #3 from Joseph John <josephpattara at gmail dot com> ---
I am trying to compile GCC 4.9.2 on HP-UX 11.31 and am precisely getting the
same LD error. Do we have any update or toot cause on this issue?
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
2014-06-21 11:01 ` [Bug c++/61577] [4.9.0] can't compile on hp-ux v3 ia64 FBergemann at web dot de
2015-10-15 11:04 ` [Bug target/61577] " josephpattara at gmail dot com
@ 2015-10-19 11:34 ` josephpattara at gmail dot com
2019-07-05 1:51 ` dave.anglin at bell dot net
` (76 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: josephpattara at gmail dot com @ 2015-10-19 11:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #5 from Joseph John <josephpattara at gmail dot com> ---
I am still struggling to compiler any version giver than GCC 4.9.0 on ia64
platform still but as far as this issue is concerned I was able to get pass the
LD abort when I used the below options for configure:
CC="gcc -mlp64" CXX="g++ -mlp64"
With this option I was able to pass the linker abort just after the
libbackend.a creation but I run into a segmentation error which I believe is
the documented issue at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64919
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2015-10-19 11:34 ` josephpattara at gmail dot com
@ 2019-07-05 1:51 ` dave.anglin at bell dot net
2020-02-25 14:55 ` [Bug middle-end/61577] [4.9.0 Regression] " peter.bisroev at groundlabs dot com
` (75 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2019-07-05 1:51 UTC (permalink / raw)
To: gcc-bugs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 1155750 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #36 from dave.anglin at bell dot net ---
On 2019-07-03 6:06 p.m., elowe at elowe dot com wrote:
> The non-working .s file does this:
>
> .LC0:
> stringz "Hellos World"
>
> <edited for breivity>
>
> movl r36 = @gprel(.LC0)
> ;;
> add r36 = r1, r36
It seems to me that the gprel instruction would fault if the gp (r1) isn't
properly initialized
correctly before main is started.
>From gcc-bugs-return-648274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 03:19:21 2019
Return-Path: <gcc-bugs-return-648274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55655 invoked by alias); 5 Jul 2019 03:19: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 55608 invoked by uid 48); 5 Jul 2019 03:19:18 -0000
From: "elowe at elowe dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 03:19: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.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: elowe at elowe 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-61577-4-4sxHa6wkDc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00386.txt.bz2
Content-length: 452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #37 from EML <elowe at elowe dot com> ---
I wonder if is this patch is related:
https://gcc.gnu.org/ml/gcc-patches/2015-12/msg02193.html
"Before the patch generated code uses .GOT entry:
addl r14 = @ltoffx(a#), r1
ld8.mov r14 = [r14], a#
After the patch generated code uses static gprel relocation:
movl r14 = @gprel(a#)
add r14 = r1, r14
"
>From gcc-bugs-return-648275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 04:19:43 2019
Return-Path: <gcc-bugs-return-648275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23611 invoked by alias); 5 Jul 2019 04:19: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 23200 invoked by uid 48); 5 Jul 2019 04:19:40 -0000
From: "fxue at os dot amperecomputing.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/91088] New: IPA-cp cost evaluation is too conservative for "if (f(param) cmp const_val)" condition
Date: Fri, 05 Jul 2019 04:19: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fxue at os dot amperecomputing.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-91088-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00387.txt.bz2
Content-length: 1640
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91088
Bug ID: 91088
Summary: IPA-cp cost evaluation is too conservative for "if
(f(param) cmp const_val)" condition
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: fxue at os dot amperecomputing.com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Current IPA-cp only detects conditional statement like "if (param cmp
const_val)", and gives a reasonable cost evaluation used in function
versioning. But beyond this form, any generalized form as f(param), a function
on the parameter, which involves extra operations and constant values, will be
conservatively treated, have not use in cost computation.
The following is an example, compiled with "-O3 -fno-inline".
The value "5" is propagated into callee(), for "if (v < 3)", ipa-cp can
deduce that "true branch" will not be executed, and benefit for function
versioning is large. And for "if (v * 2 < 6)", ipa-cp can not handle that, and
conservatively takes cost of "true branch" into account, so get a "no need to
clone function" conclusion.
int foo();
int callee(int v)
{
// if (v < 3) // will make a constprop copy with v = 5
// if (v * 2 < 6) // will no make a constprop copy
{
foo();
foo();
foo();
foo();
foo();
foo();
foo();
foo();
foo();
}
else
return 1;
}
int caller()
{
return callee (5);
}
>From gcc-bugs-return-648276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 04:40:52 2019
Return-Path: <gcc-bugs-return-648276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75702 invoked by alias); 5 Jul 2019 04:40: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 74989 invoked by uid 48); 5 Jul 2019 04:40:49 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89976] missing uninitialized warning: laundering via passing object through a function
Date: Fri, 05 Jul 2019 04:40: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: 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-89976-4-DWHzIqrf81@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89976-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89976-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00388.txt.bz2
Content-length: 224
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89976
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
could you be a bit more specific about which lines exactly you're expecting the
warnings to go on?
>From gcc-bugs-return-648277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 04:49:20 2019
Return-Path: <gcc-bugs-return-648277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80880 invoked by alias); 5 Jul 2019 04:49: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 80844 invoked by uid 48); 5 Jul 2019 04:49:16 -0000
From: "fxue at os dot amperecomputing.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/91089] New: IPA-cp does setup proper cost model for switch default case in function versioning
Date: Fri, 05 Jul 2019 04:49: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fxue at os dot amperecomputing.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-91089-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00389.txt.bz2
Content-length: 1686
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91089
Bug ID: 91089
Summary: IPA-cp does setup proper cost model for switch default
case in function versioning
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: fxue at os dot amperecomputing.com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
IPA-cp always adds execution cost of switch default case into cost evaluation
for other switch case, which might miss opportunities of function versioning
when only certain case is proved to be executed after constant propagation.
The following is an example, compiled with "-O3 -fno-inline".
It is reasonable to make a function versioning for callee when "v=1", but
actually it does not happen. And if we replace "default" with "case = 4",
it clones the function as we expect.
In some situations, we can deduce a relative small execution predicate
for default case. If all switch cases are in a continuous value range, we
can use compare to range low and high bound to mark default switch case.
Additionally, range analysis can also give us more information to simplify
the predicate.
int foo();
int callee(int v)
{
int i = 0;
switch (v)
{
case 1:
i = 3;
break;
case 2:
i = 9;
break;
default:
foo();
foo();
foo();
foo();
foo();
foo();
foo();
foo();
foo();
}
return i;
}
int caller()
{
return callee (1);
}
>From gcc-bugs-return-648278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 04:54:57 2019
Return-Path: <gcc-bugs-return-648278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85384 invoked by alias); 5 Jul 2019 04:54: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 85339 invoked by uid 48); 5 Jul 2019 04:54:53 -0000
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 04: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: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: bugzilla-gcc at thewrittenword 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-61577-4-ZKdAkBrU4c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00390.txt.bz2
Content-length: 6278
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #38 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
I rebuilt 8.3.0 with minimal patches and am seeing the same failure as before.
From <objdir>/ia64-hp-hpux11.31/libstdc++-v3/config.log:
configure:7964: checking for ANSI C header files
configure:7984: /opt/build/china/gcc-8.3.0/.obj/./gcc/xgcc
-B/opt/build/china/gcc-8.3.0/.obj/./gcc/
-B/opt/build/gcc8/ia64-hp-hpux11.31/bin/
-B/opt/build/gcc8/ia64-hp-hpux11.31/lib/ -isystem
/opt/build/gcc8/ia64-hp-hpux11.31/include -isystem
/opt/build/gcc8/ia64-hp-hpux11.31/sys-include -c -O2 -g conftest.c >&5
configure:7984: $? = 0
configure:8057: /opt/build/china/gcc-8.3.0/.obj/./gcc/xgcc
-B/opt/build/china/gcc-8.3.0/.obj/./gcc/
-B/opt/build/gcc8/ia64-hp-hpux11.31/bin/
-B/opt/build/gcc8/ia64-hp-hpux11.31/lib/ -isystem
/opt/build/gcc8/ia64-hp-hpux11.31/include -isystem
/opt/build/gcc8/ia64-hp-hpux11.31/sys-include -o conftest -O2 -g
conftest.c >&5
configure:8057: $? = 0
configure:8057: ./conftest
/opt/build/china/gcc-8.3.0/libstdc++-v3/configure: line 1940: 18830
Segmentation fault (core dumped) ./conftest$ac_exeext
If I compile the conftest.c program between gcc-4.9.4 and the 8.3.0 stage 1
compiler:
--- gcc-4.9.4/conftest.s 2019-07-05 04:50:23 +0000
+++ /opt/build/china/gcc-8.3.0/.obj/ia64-hp-hpux11.31/libstdc++-v3/conftest.s
2019-07-05 04:50:13 +0000
@@ -27,42 +27,26 @@
;;
ld4 r14 = [r14]
;;
- addp4 r14 = 0,r14
- ;;
cmp.eq p6, p7 = 0, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L3
addl r14 = @ltoffx(__SB_masks#), r1
;;
ld8.mov r14 = [r14], __SB_masks#
;;
ld4 r14 = [r14]
- ;;
- addp4 r14 = 0,r14
ld4 r15 = [r34]
;;
shladd r15 = r15, 2, r0
;;
add r14 = r15, r14
;;
- addp4 r14 = 0,r14
+ addp4 r14 = r14, r0
;;
ld4 r14 = [r14]
;;
and r14 = 64, r14
;;
cmp4.ne p6, p7 = 0, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L4
br .L5
;;
@@ -73,33 +57,15 @@
mov r14 = r8
;;
cmp4.eq p6, p7 = 0, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L5
.L4:
ld4 r14 = [r34]
;;
cmp4.ge p6, p7 = 96, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L6
ld4 r14 = [r34]
;;
cmp4.lt p6, p7 = 122, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L6
.L5:
addl r14 = @ltoffx(__SB_masks#), r1
@@ -108,42 +74,26 @@
;;
ld4 r14 = [r14]
;;
- addp4 r14 = 0,r14
- ;;
cmp.eq p6, p7 = 0, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L7
addl r14 = @ltoffx(__SB_masks#), r1
;;
ld8.mov r14 = [r14], __SB_masks#
;;
ld4 r14 = [r14]
- ;;
- addp4 r14 = 0,r14
ld4 r15 = [r34]
;;
shladd r15 = r15, 2, r0
;;
add r14 = r15, r14
;;
- addp4 r14 = 0,r14
+ addp4 r14 = r14, r0
;;
ld4 r14 = [r14]
;;
and r14 = 64, r14
;;
cmp4.eq p6, p7 = 0, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L8
br .L9
;;
@@ -154,33 +104,15 @@
mov r14 = r8
;;
cmp4.ne p6, p7 = 0, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L9
.L8:
ld4 r14 = [r34]
;;
cmp4.ge p6, p7 = 96, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L9
ld4 r14 = [r34]
;;
cmp4.ge p6, p7 = 122, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L6
.L9:
ld4 r36 = [r34]
@@ -190,22 +122,10 @@
ld4 r14 = [r34]
;;
cmp4.ge p6, p7 = 96, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L10
ld4 r14 = [r34]
;;
cmp4.lt p6, p7 = 122, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L10
ld4 r14 = [r34]
;;
@@ -216,13 +136,7 @@
ld4 r14 = [r34]
.L11:
;;
- cmp4.eq p6, p7 = r14, r15
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
+ cmp4.eq p6, p7 = r15, r14
(p6) br.cond.dptk .L12
.L6:
addl r14 = 2, r0
@@ -239,12 +153,6 @@
addl r15 = 255, r0
;;
cmp4.ge p6, p7 = r15, r14
- ;;
- (p6) adds r14 = 1, r0
- ;;
- (p7) adds r14 = 0, r0
- ;;
- tbit.nz p6, p7 = r14, 0
(p6) br.cond.dptk .L14
mov r14 = r0
.L13:
Compiling the gcc-4.9.4 conftest.s with the gcc-8.3.0 stage 1 compiler and
executing it works fine. Doing the reverse (using gcc-4.9.4 to generate an
executable from the gcc-8.3.0 stage 1 generated conftest.s) reproduces the
segfault.
>From gcc-bugs-return-648279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 04:57:30 2019
Return-Path: <gcc-bugs-return-648279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87872 invoked by alias); 5 Jul 2019 04:57: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 87817 invoked by uid 48); 5 Jul 2019 04:57:27 -0000
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 04:57: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.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: bugzilla-gcc at thewrittenword 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-61577-4-T6QvJ7ngqP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00391.txt.bz2
Content-length: 2054
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #39 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to EML from comment #25)
> I have applied the patch and tried your other suggestions, still the stage1
> compiler has the same problems generating executables.
>
> In analyzing the intermediate files between working (gcc 4.93) and not
> (bootstrap 8.3), the intermediate files seem similar until the "mach" stage
>
> The problem seems to be in out the compiler decides to reference a string in
> the source.
>
> My program is:
>
> #include <stdio.h>
>
> int main()
> {
> printf("Hellos World\n");
> return 0;
> }
>
> The generated .s file for Working does this:
>
> .LC0:
> stringz "Hellos World"
>
> <edited for breivity>
>
> addl r36 = @ltoffx(.LC0), r1
> ;;
> ld8.mov r36 = [r36], .LC0
>
> The non-working .s file does this:
>
> .LC0:
> stringz "Hellos World"
>
> <edited for breivity>
>
> movl r36 = @gprel(.LC0)
> ;;
> add r36 = r1, r36
>
>
> If I replace those 3 lines and run the assembler+linker by hand - the
> non-working foo.s will run correctly
I can now duplicate what you're seeing:
$ diff -u gcc-4.9.4/hello.s gcc-8.3.0/hello.s
--- gcc-4.9.3/hello.s 2019-07-05 04:55:49 +0000
+++ gcc-8.3.0/hello.s 2019-07-05 04:55:44 +0000
@@ -1,5 +1,6 @@
.file "hello.c"
.pred.safe_across_calls p1-p5,p16-p63
+ .section .text, "ax", "progbits"
.section .rodata, "a", "progbits"
.align 8
.LC0:
@@ -19,9 +20,9 @@
mov r32 = b0
mov r35 = r1
.body
- addl r36 = @ltoffx(.LC0), r1
+ movl r36 = @gprel(.LC0)
;;
- ld8.mov r36 = [r36], .LC0
+ add r36 = r1, r36
br.call.sptk.many b0 = puts#
mov r1 = r35
mov r14 = r0
$ grep LTOFF <objdir>/gcc/config.status
D["HAVE_AS_LTOFFX_LDXMOV_RELOCS"]=" 1"
>From gcc-bugs-return-648280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 04:59:03 2019
Return-Path: <gcc-bugs-return-648280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89894 invoked by alias); 5 Jul 2019 04:59: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 89846 invoked by uid 48); 5 Jul 2019 04:59:00 -0000
From: "fxue at os dot amperecomputing.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91090] New: A suspicious code in tree-ssa-dom.c
Date: Fri, 05 Jul 2019 04:59: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fxue at os dot amperecomputing.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-91090-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00392.txt.bz2
Content-length: 1346
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91090
Bug ID: 91090
Summary: A suspicious code in tree-ssa-dom.c
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: fxue at os dot amperecomputing.com
Target Milestone: ---
Find code snippet in simplify_stmt_for_jump_threading ():
if (vr->kind () == VR_RANGE)
{
size_t i, j;
find_case_label_range (switch_stmt, vr->min (), vr->max (), &i, &j);
if (i == j)
{
tree label = gimple_switch_label (switch_stmt, i);
tree singleton;
if (CASE_HIGH (label) != NULL_TREE
? (tree_int_cst_compare (CASE_LOW (label), vr->min ()) <= 0
&& tree_int_cst_compare (CASE_HIGH (label), vr->max ()) >=
0)
: (vr->singleton_p (&singleton)
&& tree_int_cst_equal (CASE_LOW (label), singleton)))
return label;
if (i > j)
return gimple_switch_label (switch_stmt, 0);
}
}
The conditional "if (i > j)" should be outside of "if (i == j)"?
>From gcc-bugs-return-648281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 05:03:54 2019
Return-Path: <gcc-bugs-return-648281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95487 invoked by alias); 5 Jul 2019 05: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 95460 invoked by uid 48); 5 Jul 2019 05:03:51 -0000
From: "aleksey.covacevice at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91091] New: [missed optimization] Missing aliasing optimization
Date: Fri, 05 Jul 2019 05: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: 5.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aleksey.covacevice 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-91091-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00393.txt.bz2
Content-length: 1287
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91091
Bug ID: 91091
Summary: [missed optimization] Missing aliasing optimization
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: aleksey.covacevice at gmail dot com
Target Milestone: ---
Consider the following:
struct s { int x; };
struct t { int x; };
void swap(struct s* p, struct t* q) {
p->x = q->x;
q->x = p->x;
}
Aliasing rules forbid `p` and `q` to point to the same object; yet, GCC 5.4 and
most subsequent versions produce (-O3):
swap(s*, t*):
mov eax, DWORD PTR [rsi]
mov DWORD PTR [rdi], eax
mov DWORD PTR [rsi], eax // Possible alias between p and q
ret
whereas GCC versions 4.5.3 to 5.3 and versions 8.1 to 8.2 correctly produce:
swap(s*, t*):
mov eax, DWORD PTR [rsi]
mov DWORD PTR [rdi], eax
ret
All versions produce the correct code if __restrict__ is used on any pointer.
This behavior can be verified on Godbolt: https://godbolt.org/z/WYMoFI
>From gcc-bugs-return-648282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 05:48:39 2019
Return-Path: <gcc-bugs-return-648282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38241 invoked by alias); 5 Jul 2019 05:48: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 38108 invoked by uid 48); 5 Jul 2019 05:48:30 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/91088] IPA-cp cost evaluation is too conservative for "if (f(param) cmp const_val)" condition
Date: Fri, 05 Jul 2019 05:48: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: unknown
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-91088-4-oYbGQWz1jT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91088-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91088-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00394.txt.bz2
Content-length: 274
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91088
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
I am surprised we don't have a match.pd transformation for v * 2 < 6 with
undefined overflow. But that's only a side remark, not important for your
report.
>From gcc-bugs-return-648283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 05:53:51 2019
Return-Path: <gcc-bugs-return-648283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47563 invoked by alias); 5 Jul 2019 05: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 47467 invoked by uid 48); 5 Jul 2019 05:53:47 -0000
From: "colomar.6.4.3 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/10980] vararg functions are not inlined
Date: Fri, 05 Jul 2019 05:53: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: 3.3
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: colomar.6.4.3 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: cc
Message-ID: <bug-10980-4-8Dg0bgUs69@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-10980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-10980-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00395.txt.bz2
Content-length: 1360
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10980
Alejandro Colomar <colomar.6.4.3 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |colomar.6.4.3 at gmail dot com
--- Comment #13 from Alejandro Colomar <colomar.6.4.3 at gmail dot com> ---
static inline void TELL(const char *fmt, ...)
__attribute__((format(printf, 1, 2), always_inline));
static inline void TELL(const char *fmt, ...)
{
va_list ap;
va_start(ap,fmt);
vsyslog(LOG_NOTICE,_(fmt),ap);
va_end(ap);
}
The compiler should be able to see that it is a varargs
function with printf-like format, and that the only reason
for `va_list` to exist is to pass the varargs and not to use
them.
It is trivial to see that an inlined version would be
simplified to a call to `syslog`.
Example:
void foo(void)
{
char *world = "world";
char newline = '\n';
TELL("Hello %s%c%c", world, '!', newline);
}
could be inlined to the following code:
void foo(void)
{
char *world = "world";
char newline = '\n';
syslog(LOG_NOTICE, "Hello %s%c%c", world, '!', newline);
}
The same should happen with `vprintf`->`printf` and all those
families of functions.
>From gcc-bugs-return-648284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 07:10:41 2019
Return-Path: <gcc-bugs-return-648284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37787 invoked by alias); 5 Jul 2019 07:10: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 37326 invoked by uid 48); 5 Jul 2019 07:10:37 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] New: Error on implicit function declarations by default
Date: Fri, 05 Jul 2019 07: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: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw 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-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00396.txt.bz2
Content-length: 884
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
Bug ID: 91092
Summary: Error on implicit function declarations by default
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: fw at gcc dot gnu.org
Target Milestone: ---
Once configure scripts have been cleaned up (and we have verified this for
Fedora and perhaps Debian), c99/gnu99/c11/gnu11 mode should all default to
emitting errors for implicit function declarations.
Implicit function declarations were removed from C99, but have been kept in GCC
so far, mainly for compatibility with existing configure checks (which give
wrong results if implicit function declarations are used in tests).
>From gcc-bugs-return-648285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 07:13:01 2019
Return-Path: <gcc-bugs-return-648285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52230 invoked by alias); 5 Jul 2019 07:13: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 52183 invoked by uid 48); 5 Jul 2019 07:12:58 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91093] New: Error on implicit int by default
Date: Fri, 05 Jul 2019 07: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw 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-91093-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00397.txt.bz2
Content-length: 986
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91093
Bug ID: 91093
Summary: Error on implicit int by default
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: fw at gcc dot gnu.org
Target Milestone: ---
Once configure scripts have been cleaned up (and we have verified this for
Fedora and perhaps Debian), c99/gnu99/c11/gnu11 modes should all default to
emitting errors for implicit ints.
Implicit ints were removed from C99, but have been kept in GCC so far, mainly
for compatibility with existing configure checks (which give wrong results if
implicit ints are used in tests).
(Support for implicit ints is incompatible with using the auto keyword for
localized type inference, should that ever come for C, so it makes sense to
clean this up.)
>From gcc-bugs-return-648286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 08:48:50 2019
Return-Path: <gcc-bugs-return-648286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4718 invoked by alias); 5 Jul 2019 08: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 4298 invoked by uid 48); 5 Jul 2019 08:48:36 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91091] [missed optimization] Missing optimization in unaliased pointers
Date: Fri, 05 Jul 2019 08: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: 5.4.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 assigned_to everconfirmed
Message-ID: <bug-91091-4-R3CBR3FAT7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91091-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91091-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00398.txt.bz2
Content-length: 880
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91091
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-07-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> ---
Note that GCC middle-end semantics would allow partial overlaps here unless
you factor in alignment requirements.
There is actually code in GCC9+ that is supposed to handle this situation but
for some reason it doesn't work here. I'll see why.
>From gcc-bugs-return-648287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 08:51:03 2019
Return-Path: <gcc-bugs-return-648287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7711 invoked by alias); 5 Jul 2019 08:51: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 7601 invoked by uid 48); 5 Jul 2019 08:51:00 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91090] A suspicious code in tree-ssa-dom.c
Date: Fri, 05 Jul 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: tree-optimization
X-Bugzilla-Version: unknown
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 cc everconfirmed
Message-ID: <bug-91090-4-H4zW1ifcGW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91090-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91090-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00399.txt.bz2
Content-length: 580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91090
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-05
CC| |law at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Jeff - you touched this code last.
>From gcc-bugs-return-648288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 10:34:19 2019
Return-Path: <gcc-bugs-return-648288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118105 invoked by alias); 5 Jul 2019 10:34: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 118067 invoked by uid 48); 5 Jul 2019 10:34:16 -0000
From: "author at shakthimaan dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/90334] documentation for getting read-write SVN access is misleading
Date: Fri, 05 Jul 2019 10:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: author at shakthimaan 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-90334-4-CMJFWrwRfk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90334-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90334-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00400.txt.bz2
Content-length: 279
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90334
--- Comment #7 from Shakthi Kannan <author at shakthimaan dot com> ---
Created attachment 46559
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46559&action=edit
Use whitespace between sourceware.org and gcc.gnu.org
>From gcc-bugs-return-648289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 11:02:00 2019
Return-Path: <gcc-bugs-return-648289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40035 invoked by alias); 5 Jul 2019 11:01: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 39980 invoked by uid 48); 5 Jul 2019 11:01:56 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90883] Generated code is worse if returned struct is unnamed
Date: Fri, 05 Jul 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: 9.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-90883-4-6R4V682pYG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90883-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90883-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00401.txt.bz2
Content-length: 406
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90883
Wilco <wilco at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #15 from Wilco <wilco at gcc dot gnu.org> ---
Reopen
>From gcc-bugs-return-648290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 11:26:31 2019
Return-Path: <gcc-bugs-return-648290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52923 invoked by alias); 5 Jul 2019 11: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 52465 invoked by uid 48); 5 Jul 2019 11:26:26 -0000
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 11: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: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: bugzilla-gcc at thewrittenword 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-61577-4-8o0dhvNuw4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00402.txt.bz2
Content-length: 254
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #40 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
Created attachment 46560
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46560&action=edit
Revert PR60465
>From gcc-bugs-return-648291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 11:31:35 2019
Return-Path: <gcc-bugs-return-648291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58530 invoked by alias); 5 Jul 2019 11:31: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 58133 invoked by uid 48); 5 Jul 2019 11:31:31 -0000
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 11:31: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.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: bugzilla-gcc at thewrittenword 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-61577-4-pBRAhaQCXd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00403.txt.bz2
Content-length: 2819
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #41 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to The Written Word from comment #39)
> (In reply to EML from comment #25)
> > I have applied the patch and tried your other suggestions, still the stage1
> > compiler has the same problems generating executables.
> >
> > In analyzing the intermediate files between working (gcc 4.93) and not
> > (bootstrap 8.3), the intermediate files seem similar until the "mach" stage
> >
> > The problem seems to be in out the compiler decides to reference a string in
> > the source.
> >
> > My program is:
> >
> > #include <stdio.h>
> >
> > int main()
> > {
> > printf("Hellos World\n");
> > return 0;
> > }
> >
> > The generated .s file for Working does this:
> >
> > .LC0:
> > stringz "Hellos World"
> >
> > <edited for breivity>
> >
> > addl r36 = @ltoffx(.LC0), r1
> > ;;
> > ld8.mov r36 = [r36], .LC0
> >
> > The non-working .s file does this:
> >
> > .LC0:
> > stringz "Hellos World"
> >
> > <edited for breivity>
> >
> > movl r36 = @gprel(.LC0)
> > ;;
> > add r36 = r1, r36
> >
> >
> > If I replace those 3 lines and run the assembler+linker by hand - the
> > non-working foo.s will run correctly
>
> I can now duplicate what you're seeing:
> $ diff -u gcc-4.9.4/hello.s gcc-8.3.0/hello.s
> --- gcc-4.9.3/hello.s 2019-07-05 04:55:49 +0000
> +++ gcc-8.3.0/hello.s 2019-07-05 04:55:44 +0000
> @@ -1,5 +1,6 @@
> .file "hello.c"
> .pred.safe_across_calls p1-p5,p16-p63
> + .section .text, "ax", "progbits"
> .section .rodata, "a", "progbits"
> .align 8
> .LC0:
> @@ -19,9 +20,9 @@
> mov r32 = b0
> mov r35 = r1
> .body
> - addl r36 = @ltoffx(.LC0), r1
> + movl r36 = @gprel(.LC0)
> ;;
> - ld8.mov r36 = [r36], .LC0
> + add r36 = r1, r36
> br.call.sptk.many b0 = puts#
> mov r1 = r35
> mov r14 = r0
>
> $ grep LTOFF <objdir>/gcc/config.status
> D["HAVE_AS_LTOFFX_LDXMOV_RELOCS"]=" 1"
If I revert the patch for PR60465 (added as an attachment), then looking at the
difference between gcc-4.9.4/hello.s and gcc-8.3.0/hello.s gives:
--- gcc-4.9.4/hello.s 2019-07-05 04:55:49 +0000
+++ gcc-8.3.0/hello.s 2019-07-05 11:25:09 +0000
@@ -1,5 +1,6 @@
.file "hello.c"
.pred.safe_across_calls p1-p5,p16-p63
+ .section .text, "ax", "progbits"
.section .rodata, "a", "progbits"
.align 8
.LC0:
Reverting the patch doesn't bring us any closer to the segfault in libstdc++-v3
though.
>From gcc-bugs-return-648292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 11:49:51 2019
Return-Path: <gcc-bugs-return-648292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101572 invoked by alias); 5 Jul 2019 11:49: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 101314 invoked by uid 48); 5 Jul 2019 11:49:47 -0000
From: "jens.wellner at dlr dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/78884] [7/8/9/10] ICE when gimplifying VLA in OpenMP SIMD region
Date: Fri, 05 Jul 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: middle-end
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jens.wellner at dlr 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-78884-4-Db7jUIcmx2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78884-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78884-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00404.txt.bz2
Content-length: 183
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78884
--- Comment #10 from Jens Wellner <jens.wellner at dlr dot de> ---
I have tested the trunk and it is working as expected.
Thanks
>From gcc-bugs-return-648293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 11:56:59 2019
Return-Path: <gcc-bugs-return-648293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67650 invoked by alias); 5 Jul 2019 11: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 66992 invoked by uid 48); 5 Jul 2019 11:56:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91094] New: BB vectorization is too quick to disable itself because of possible unrolling needed
Date: Fri, 05 Jul 2019 11: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:
X-Bugzilla-Severity: enhancement
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-91094-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00405.txt.bz2
Content-length: 1939
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91094
Bug ID: 91094
Summary: BB vectorization is too quick to disable itself
because of possible unrolling needed
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
long long a[1024];
int b[1024];
void foo()
{
a[0] = b[0] + b[2];
a[1] = b[1] + b[3];
#if WORKS
a[2] = b[4] + b[6];
a[3] = b[5] + b[7];
#endif
}
The above is not vectorized fully (we vectorize the store) if !WORKS because
t2.c:12:1: missed: Build SLP failed: unrolling required in basic block SLP
which checks group_size (2) against the vector(4) int number of elements.
It works fine with WORKS because then group_size is 4.
A similar issue prevents SPEC x264 from being vectorized optimally.
Testcase from that:
typedef unsigned int uint32_t;
typedef unsigned char uint8_t;
#define HADAMARD4(d0, d1, d2, d3, s0, s1, s2, s3) {\
int t0 = s0 + s1;\
int t1 = s0 - s1;\
int t2 = s2 + s3;\
int t3 = s2 - s3;\
d0 = t0 + t2;\
d2 = t0 - t2;\
d1 = t1 + t3;\
d3 = t1 - t3;\
}
uint32_t tmp[4][4];
__attribute__ ((noinline,noclone))
void x264_pixel_satd_8x4( uint8_t *pix1, int i_pix1, uint8_t *pix2, int i_pix2
)
{
uint32_t a0, a1, a2, a3;
for( int i = 0; i < 4; i++, pix1 += i_pix1, pix2 += i_pix2 )
{
a0 = (pix1[0] - pix2[0]) + ((pix1[4] - pix2[4]) << 16);
a1 = (pix1[1] - pix2[1]) + ((pix1[5] - pix2[5]) << 16);
a2 = (pix1[2] - pix2[2]) + ((pix1[6] - pix2[6]) << 16);
a3 = (pix1[3] - pix2[3]) + ((pix1[7] - pix2[7]) << 16);
HADAMARD4( tmp[i][0], tmp[i][1], tmp[i][2], tmp[i][3], a0,a1,a2,a3 );
}
}
>From gcc-bugs-return-648294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 11:58:00 2019
Return-Path: <gcc-bugs-return-648294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68698 invoked by alias); 5 Jul 2019 11:58: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 68618 invoked by uid 48); 5 Jul 2019 11:57:56 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91094] BB vectorization is too quick to disable itself because of possible unrolling needed
Date: Fri, 05 Jul 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: missed-optimization
X-Bugzilla-Severity: enhancement
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-91094-4-PtDmevaUx8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91094-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91094-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00406.txt.bz2
Content-length: 971
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91094
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-07-05
Blocks| |53947, 26163
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 (eventually).
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)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
[Bug 53947] [meta-bug] vectorizer missed-optimizations
>From gcc-bugs-return-648295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 12:02:13 2019
Return-Path: <gcc-bugs-return-648295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120671 invoked by alias); 5 Jul 2019 12:02: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 115347 invoked by uid 55); 5 Jul 2019 12:02:09 -0000
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 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: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: dave.anglin at bell 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-61577-4-hEWu4x3X7M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00407.txt.bz2
Content-length: 1126
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #42 from dave.anglin at bell dot net ---
On 2019-07-05 12:57 a.m., bugzilla-gcc at thewrittenword dot com wrote:
> I can now duplicate what you're seeing:
> $ diff -u gcc-4.9.4/hello.s gcc-8.3.0/hello.s
> --- gcc-4.9.3/hello.s 2019-07-05 04:55:49 +0000
> +++ gcc-8.3.0/hello.s 2019-07-05 04:55:44 +0000
> @@ -1,5 +1,6 @@
> .file "hello.c"
> .pred.safe_across_calls p1-p5,p16-p63
> + .section .text, "ax", "progbits"
> .section .rodata, "a", "progbits"
With 8.3.0 assembly output, what happens if you change ".rodata" to ".data"?Â
It may
be that hpux can't handle gprel in .rodata.
The other possibility is gp is wrong.
> .align 8
> .LC0:
> @@ -19,9 +20,9 @@
> mov r32 = b0
> mov r35 = r1
> .body
> - addl r36 = @ltoffx(.LC0), r1
> + movl r36 = @gprel(.LC0)
> ;;
> - ld8.mov r36 = [r36], .LC0
> + add r36 = r1, r36
> br.call.sptk.many b0 = puts#
> mov r1 = r35
> mov r14 = r0
>From gcc-bugs-return-648296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 12:07:58 2019
Return-Path: <gcc-bugs-return-648296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44831 invoked by alias); 5 Jul 2019 12:07: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 44732 invoked by uid 48); 5 Jul 2019 12:07:54 -0000
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 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: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: bugzilla-gcc at thewrittenword 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-61577-4-vRb3wVtO3h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00408.txt.bz2
Content-length: 1648
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #43 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to dave.anglin from comment #42)
> On 2019-07-05 12:57 a.m., bugzilla-gcc at thewrittenword dot com wrote:
> > I can now duplicate what you're seeing:
> > $ diff -u gcc-4.9.4/hello.s gcc-8.3.0/hello.s
> > --- gcc-4.9.3/hello.s 2019-07-05 04:55:49 +0000
> > +++ gcc-8.3.0/hello.s 2019-07-05 04:55:44 +0000
> > @@ -1,5 +1,6 @@
> > .file "hello.c"
> > .pred.safe_across_calls p1-p5,p16-p63
> > + .section .text, "ax", "progbits"
> > .section .rodata, "a", "progbits"
> With 8.3.0 assembly output, what happens if you change ".rodata" to ".data"?
> It may
> be that hpux can't handle gprel in .rodata.
>
> The other possibility is gp is wrong.
> > .align 8
> > .LC0:
> > @@ -19,9 +20,9 @@
> > mov r32 = b0
> > mov r35 = r1
> > .body
> > - addl r36 = @ltoffx(.LC0), r1
> > + movl r36 = @gprel(.LC0)
> > ;;
> > - ld8.mov r36 = [r36], .LC0
> > + add r36 = r1, r36
> > br.call.sptk.many b0 = puts#
> > mov r1 = r35
> > mov r14 = r0
$ /opt/build/china/gcc-8.3.0/.obj-/./gcc/xgcc
-B/opt/build/china/gcc-8.3.0/.obj-/./gcc/
-B/opt/build/gcc8/ia64-hp-hpux11.31/bin/ -B/opt/build/gcc8/ia64-hp-hpux11.31
/lib/ -isystem /opt/build/gcc8/ia64-hp-hpux11.31/include -isystem
/opt/build/gcc8/ia64-hp-hpux11.31/sys-include hello.s
hello.s: Assembler messages:
hello.s:4: Warning: ignoring changed section attributes for .data
$ ./a.out
`
>From gcc-bugs-return-648297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 12:43:55 2019
Return-Path: <gcc-bugs-return-648297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42879 invoked by alias); 5 Jul 2019 12: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 39460 invoked by uid 48); 5 Jul 2019 12:43:52 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/90334] documentation for getting read-write SVN access is misleading
Date: Fri, 05 Jul 2019 12:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
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-90334-4-yncxGXitr3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90334-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90334-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00409.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90334
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed by https://gcc.gnu.org/ml/gcc-patches/2019-07/msg00435.html - thanks
>From gcc-bugs-return-648298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 12:49:42 2019
Return-Path: <gcc-bugs-return-648298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78149 invoked by alias); 5 Jul 2019 12:49: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 78126 invoked by uid 55); 5 Jul 2019 12:49:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91091] [missed optimization] Missing optimization in unaliased pointers
Date: Fri, 05 Jul 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: tree-optimization
X-Bugzilla-Version: 5.4.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-91091-4-yROyFiO8d4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91091-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91091-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00410.txt.bz2
Content-length: 780
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91091
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Fri Jul 5 12:48:42 2019
New Revision: 273134
URL: https://gcc.gnu.org/viewcvs?rev=273134&root=gcc&view=rev
Log:
2019-07-05 Richard Biener <rguenther@suse.de>
PR tree-optimization/91091
* tree-ssa-sccvn.c (vn_reference_lookup_3): Overlap of
accesses can happen with -fno-strict-aliasing.
* gcc.dg/tree-ssa/pr91091-1.c: New testcase.
* gcc.dg/tree-ssa/ssa-fre-61.c: Adjust.
Added:
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr91091-1.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-61.c
trunk/gcc/tree-ssa-sccvn.c
>From gcc-bugs-return-648299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 12:51:17 2019
Return-Path: <gcc-bugs-return-648299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79802 invoked by alias); 5 Jul 2019 12:51: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 79749 invoked by uid 48); 5 Jul 2019 12:51:13 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91091] [missed optimization] Missing optimization in unaliased pointers
Date: Fri, 05 Jul 2019 12: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: 5.4.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 cf_known_to_work resolution
Message-ID: <bug-91091-4-HwiGW7eKch@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91091-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91091-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00411.txt.bz2
Content-length: 494
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91091
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Known to work| |10.0
Resolution|--- |FIXED
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed for GCC 10.
>From gcc-bugs-return-648300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 12:51:21 2019
Return-Path: <gcc-bugs-return-648300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80282 invoked by alias); 5 Jul 2019 12: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 79805 invoked by uid 55); 5 Jul 2019 12: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/91091] [missed optimization] Missing optimization in unaliased pointers
Date: Fri, 05 Jul 2019 12: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: 5.4.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:
Message-ID: <bug-91091-4-RPUytzpsqH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91091-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91091-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00412.txt.bz2
Content-length: 1955
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91091
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Fri Jul 5 12:50:45 2019
New Revision: 273135
URL: https://gcc.gnu.org/viewcvs?rev=273135&root=gcc&view=rev
Log:
2019-07-05 Richard Biener <rguenther@suse.de>
PR tree-optimization/91091
* tree-ssa-alias.h (get_continuation_for_phi): Add tbaa_p parameter.
(walk_non_aliased_vuses): Likewise.
* tree-ssa-alias.c (maybe_skip_until): Pass down tbaa_p.
(get_continuation_for_phi): New tbaa_p parameter and pass
it down.
(walk_non_aliased_vuses): Likewise.
* ipa-prop.c (determine_known_aggregate_parts): Adjust.
* tree-ssa-pre.c (translate_vuse_through_block): Likewise.
* tree-ssa-scopedtables.c (avail_exprs_stack::lookup_avail_expr):
Likewise.
* tree-ssa-sccvn.c (struct vn_walk_cb_data): Add tbaa_p flag.
(adjust_offsets_for_equal_base_address): New function.
(vn_reference_lookup_3): Use it to catch more base equivalences.
Handle and pass down tbaa_p flag.
(vn_reference_lookup_pieces): Adjust.
(vn_reference_lookup): Remove alias-set altering, instead pass
down false as tbaa_p.
* gcc.dg/tree-ssa/pr91091-2.c: New testcase.
* gcc.dg/tree-ssa/ssa-fre-70.c: Likewise.
* gcc.dg/tree-ssa/ssa-fre-71.c: Likewise.
* gcc.dg/tree-ssa/ssa-fre-72.c: Likewise.
Added:
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr91091-2.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-70.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-71.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-72.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/ipa-prop.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-alias.c
trunk/gcc/tree-ssa-alias.h
trunk/gcc/tree-ssa-pre.c
trunk/gcc/tree-ssa-sccvn.c
trunk/gcc/tree-ssa-scopedtables.c
>From gcc-bugs-return-648301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 13:01:08 2019
Return-Path: <gcc-bugs-return-648301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117039 invoked by alias); 5 Jul 2019 13:01: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 116491 invoked by uid 48); 5 Jul 2019 13:00:40 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91060] [10 regression] gcc.c-torture/execute/scal-to-vec1.c fails on armeb-none-linux-gnueabihf since r272843
Date: Fri, 05 Jul 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: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon 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-91060-4-z3lCg89kig@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00413.txt.bz2
Content-length: 4647
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
--- Comment #4 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Unfortunately, it's still failing as of r273133.
It fails at the very first check:
v1 = 2 + v0; check (short, 8, v0, v1, 2, +, l);
The generated code for main is:
main:
@ args = 0, pretend = 0, frame = 16
@ frame_needed = 0, uses_anonymous_args = 0
movw r3, #:lower16:.LANCHOR0
vldr d16, .L6
vldr d17, .L6+8
movt r3, #:upper16:.LANCHOR0
vmov.i16 q9, #2 @ v8hi
ldr r0, [r3]
str lr, [sp, #-4]!
sub sp, sp, #20
vmov.16 d16[0], r0
sxth r1, r0
vadd.i16 q0, q8, q9
add ip, r1, #2
vmov.s16 r2, d0[3]
cmp ip, r2
vst1.64 {d0-d1}, [sp:64]
bne .L2
vmov.s16 r3, d0[2]
cmp r3, #3
bne .L2
vmov.s16 r0, d0[1]
cmp r0, #4
bne .L2
vmov.s16 r1, d0[0]
cmp r1, #5
bne .L2
vmov.s16 ip, d1[3]
cmp ip, #6
bne .L2
vmov.s16 r2, d1[2]
cmp r2, #7
bne .L2
vmov.s16 r3, d1[1]
cmp r3, #8
bne .L2
vmov.s16 r0, d1[0]
cmp r0, #9
bne .L2
mov r0, #0
add sp, sp, #20
@ sp needed
ldr pc, [sp], #4
.L2:
bl abort
.L7:
.align 3
.L6:
.short 1
.short 1
.short 2
.short 3
.short 4
.short 5
.short 6
.short 7
.size main, .-main
And the QEMU execution trace with CPU regs before TB execution:
IN: main
0x00010350: e3013024 movw r3, #4132 ; 0x1024
0x00010354: eddf0b27 vldr d16, [pc, #156] ; 0x103f8
0x00010358: eddf1b28 vldr d17, [pc, #160] ; 0x10400
0x0001035c: e3403002 movt r3, #2 ; 0x2
0x00010360: f2c02852 vmov.i16 q9, #2 ; 0x0002
0x00010364: e5930000 ldr r0, [r3]
0x00010368: e52de004 push {lr} ; (str lr, [sp, #-4]!)
0x0001036c: e24dd014 sub sp, sp, #20 ; 0x14
0x00010370: ee000bb0 vmov.16 d16[0], r0
0x00010374: e6bf1070 sxth r1, r0
0x00010378: f21008e2 vadd.i16 q0, q8, q9
0x0001037c: e281c002 add ip, r1, #2 ; 0x2
0x00010380: ee302b70 vmov.s16 r2, d0[3]
0x00010384: e15c0002 cmp ip, r2
0x00010388: f40d0adf vst1.64 {d0-d1}, [sp, :64]
0x0001038c: 1a000017 bne 0x103f0
R00=00000001 R01=40800534 R02=4080053c R03=00010350
R04=000104f8 R05=00000000 R06=00010408 R07=00000000
R08=00000000 R09=00000000 R10=40832000 R11=00000000
R12=00000000 R13=408003e8 R14=408b9808 R15=00010350
PSR=60070210 -ZC- A S usr32
----------------
IN: main
0x00010390: ee303b30 vmov.s16 r3, d0[2]
0x00010394: e3530003 cmp r3, #3 ; 0x3
0x00010398: 1a000014 bne 0x103f0
R00=00000001 R01=00000001 R02=00000003 R03=00021024
R04=000104f8 R05=00000000 R06=00010408 R07=00000000
R08=00000000 R09=00000000 R10=40832000 R11=00000000
R12=00000003 R13=408003d0 R14=408b9808 R15=00010390
PSR=60070210 -ZC- A S usr32
----------------
IN: main
0x0001039c: ee100b70 vmov.s16 r0, d0[1]
0x000103a0: e3500004 cmp r0, #4 ; 0x4
0x000103a4: 1a000011 bne 0x103f0
R00=00000001 R01=00000001 R02=00000003 R03=00000003
R04=000104f8 R05=00000000 R06=00010408 R07=00000000
R08=00000000 R09=00000000 R10=40832000 R11=00000000
R12=00000003 R13=408003d0 R14=408b9808 R15=0001039c
PSR=60070210 -ZC- A S usr32
----------------
IN: main
0x000103a8: ee101b30 vmov.s16 r1, d0[0]
0x000103ac: e3510005 cmp r1, #5 ; 0x5
0x000103b0: 1a00000e bne 0x103f0
R00=00000004 R01=00000001 R02=00000003 R03=00000003
R04=000104f8 R05=00000000 R06=00010408 R07=00000000
R08=00000000 R09=00000000 R10=40832000 R11=00000000
R12=00000003 R13=408003d0 R14=408b9808 R15=000103a8
PSR=60070210 -ZC- A S usr32
----------------
IN: main
0x000103f0: ebffffd2 bl 0x10340 (abort)
R00=00000004 R01=00000003 R02=00000003 R03=00000003 (****)
R04=000104f8 R05=00000000 R06=00010408 R07=00000000
R08=00000000 R09=00000000 R10=40832000 R11=00000000
R12=00000003 R13=408003d0 R14=408b9808 R15=000103f0
PSR=80070210 N--- A S usr32
From (****) we can see that R1 contains 3 instead of the expected 5.
>From gcc-bugs-return-648302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 13:17:30 2019
Return-Path: <gcc-bugs-return-648302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6438 invoked by alias); 5 Jul 2019 13: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 6389 invoked by uid 55); 5 Jul 2019 13:17:27 -0000
From: "samtebbs at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90712] [10 regression] gcc.dg/rtl/aarch64/subs_adds_sp.c fails with ICE
Date: Fri, 05 Jul 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: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: samtebbs 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-90712-4-ls5iWnerVo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00414.txt.bz2
Content-length: 613
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90712
--- Comment #1 from Sam Tebbs <samtebbs at gcc dot gnu.org> ---
Author: samtebbs
Date: Fri Jul 5 13:16:55 2019
New Revision: 273138
URL: https://gcc.gnu.org/viewcvs?rev=273138&root=gcc&view=rev
Log:
[PATCH][GCC][AARCH64] PR target/90712 Fix gcc.dg/rtl/aarch64/subs_adds_sp.c
regression
gcc/
2019-07-05 Sam Tebbs <sam.tebbs@arm.com>
PR target/90712
* aarch64/aarch64.c (aarch64_post_cfi_startproc): Replace thunk check
with a frame laid out check.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/aarch64/aarch64.c
>From gcc-bugs-return-648303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 13:39:10 2019
Return-Path: <gcc-bugs-return-648303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49741 invoked by alias); 5 Jul 2019 13:39: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 49696 invoked by uid 48); 5 Jul 2019 13:39:07 -0000
From: "raskolnikov at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91095] New: internal compiler error: in tsubst_copy
Date: Fri, 05 Jul 2019 13:39: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: raskolnikov at gnu 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-91095-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00415.txt.bz2
Content-length: 1766
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91095
Bug ID: 91095
Summary: internal compiler error: in tsubst_copy
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: raskolnikov at gnu dot org
Target Milestone: ---
Sorry that this submission does not comply with the minimal example policy. I
stumbled on this compiler issue:
/home/raskolnikov/dev/immer/test/flex_vector/fuzzed-3.cpp: In instantiation
of ‘int {anonymous}::run_input(const uint8_t*, std::size_t) [with long unsigned
int VarCount = 2; unsigned int Bits = 2; uint8_t = unsigned char; std::size_t =
long unsigned int]’:
/home/raskolnikov/dev/immer/test/flex_vector/fuzzed-3.cpp:221:9: required
from here
/home/raskolnikov/dev/immer/test/flex_vector/fuzzed-3.cpp:82:14: internal
compiler error: in tsubst_copy, at cp/pt.c:15603
82 | case op_push_back:
| ^~~~~~~~~~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
When building this file:
https://github.com/arximboldi/immer/blob/6d07c4ee0edfc8eebf929dcf8482eabd5552d361/test/flex_vector/fuzzed-3.cpp
There are instructions on the repository on how to build the project. This is
triggered in particular when running `make check`.
$CXX --version
g++ (GCC) 9.1.0
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.
>From gcc-bugs-return-648304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 14:17:44 2019
Return-Path: <gcc-bugs-return-648304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56018 invoked by alias); 5 Jul 2019 14:17: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 55967 invoked by uid 48); 5 Jul 2019 14:17:39 -0000
From: "nok.raven at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89976] missing uninitialized warning: laundering via passing object through a function
Date: Fri, 05 Jul 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: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nok.raven 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-89976-4-ZsAZo0AegW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89976-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89976-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00416.txt.bz2
Content-length: 666
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89976
--- Comment #2 from Nikita Kniazev <nok.raven at gmail dot com> ---
The same warning as when the object is constructed inside the main function:
int main()
{
XorYorZ x;
return x.x;
}
Also, the warning is not triggered in C++17+ mode with:
XorYorZ foo()
{
return XorYorZ();
}
where the guaranteed return value optimization have to happen and the code
must have the same meaning as:
int main()
{
XorYorZ x = XorYorZ();
return x.x;
}
which triggers the warning, and is the same as just `XorYorZ x;` because of
the presence of the user defined constructor in X/Y/Z and copy/move elision.
>From gcc-bugs-return-648305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 14:46:15 2019
Return-Path: <gcc-bugs-return-648305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44574 invoked by alias); 5 Jul 2019 14: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 38195 invoked by uid 55); 5 Jul 2019 14:46:03 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/83374] [DR1813] Bad std::is_standard_layout with two base class subobjects of the same type
Date: Fri, 05 Jul 2019 14: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: 6.3.0
X-Bugzilla-Keywords: accepts-invalid, 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83374-4-CXfAyD7TxM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83374-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83374-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00417.txt.bz2
Content-length: 791
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83374
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Fri Jul 5 14:45:30 2019
New Revision: 273139
URL: https://gcc.gnu.org/viewcvs?rev=273139&root=gcc&view=rev
Log:
DR 1813
PR c++/83374 - __is_standard_layout wrong for a class with repeated
bases.
* class.c (check_bases): Set CLASSTYPE_NON_STD_LAYOUT for a class if
CLASSTYPE_REPEATED_BASE_P is true.
* g++.dg/ext/is_std_layout3.C: New test.
* g++.dg/ext/is_std_layout4.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/ext/is_std_layout3.C
trunk/gcc/testsuite/g++.dg/ext/is_std_layout4.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/class.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-648306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 14:49:10 2019
Return-Path: <gcc-bugs-return-648306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65987 invoked by alias); 5 Jul 2019 14:49: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 64412 invoked by uid 48); 5 Jul 2019 14:49:07 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/83374] [DR1813] Bad std::is_standard_layout with two base class subobjects of the same type
Date: Fri, 05 Jul 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: c++
X-Bugzilla-Version: 6.3.0
X-Bugzilla-Keywords: accepts-invalid, patch, rejects-valid
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-83374-4-5uphdpriyK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83374-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83374-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00418.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83374
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> ---
Fixed for GCC 10.
>From gcc-bugs-return-648307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 14:51:14 2019
Return-Path: <gcc-bugs-return-648307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18559 invoked by alias); 5 Jul 2019 14: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 16551 invoked by uid 48); 5 Jul 2019 14:51:10 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/83374] [DR1813] Bad std::is_standard_layout with two base class subobjects of the same type
Date: Fri, 05 Jul 2019 14: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: 6.3.0
X-Bugzilla-Keywords: accepts-invalid, patch, rejects-valid
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:
Message-ID: <bug-83374-4-ZQgfsERpxe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83374-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83374-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00419.txt.bz2
Content-length: 159
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83374
--- Comment #7 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Related PRs:
PR91079
PR91080
PR91081
>From gcc-bugs-return-648308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 14:55:31 2019
Return-Path: <gcc-bugs-return-648308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31966 invoked by alias); 5 Jul 2019 14:55: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 31920 invoked by uid 48); 5 Jul 2019 14:55:28 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Fri, 05 Jul 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: c
X-Bugzilla-Version: unknown
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: cc
Message-ID: <bug-91092-4-aDF4NblC7X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00420.txt.bz2
Content-length: 476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |segher at gcc dot gnu.org
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Hrm, the configure test situation is a bit scary. Do you have some
examples of that?
>From gcc-bugs-return-648309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 14:57:43 2019
Return-Path: <gcc-bugs-return-648309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48765 invoked by alias); 5 Jul 2019 14:57: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 48737 invoked by uid 48); 5 Jul 2019 14:57:38 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91095] internal compiler error: in tsubst_copy
Date: Fri, 05 Jul 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: c++
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek 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-91095-4-hivuJ4REw7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91095-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91095-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00421.txt.bz2
Content-length: 671
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91095
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-07-05
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
It's fine if you don't have a minimal testcase, but please provide the
preprocessed source file (using -save-temps).
>From gcc-bugs-return-648310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 15:16:57 2019
Return-Path: <gcc-bugs-return-648310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72646 invoked by alias); 5 Jul 2019 15:16: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 72565 invoked by uid 48); 5 Jul 2019 15:16:54 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91096] New: Openmp vector max reduction incorrect
Date: Fri, 05 Jul 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: wilco 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-91096-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00422.txt.bz2
Content-length: 1322
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91096
Bug ID: 91096
Summary: Openmp vector max reduction incorrect
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: wilco at gcc dot gnu.org
Target Milestone: ---
The new gcc.dg/vect/vect-simd-14.c test produces incorrect reduction due to the
vectorizer adding fmax (result, FLT_MAX):
float b[1024], a[1024];
__attribute__((noipa)) float
bar (void)
{
float s = -__builtin_inff ();
#pragma omp simd reduction (inscan, max:s)
for (int i = 0; i < 1024; i++)
{
b[i] = s;
#pragma omp scan exclusive(s)
s = s > a[i] ? s : a[i];
}
return s;
}
When built with -ffast-math -ftree-vectorize -O2 -fdump-tree-vect-details
-fopenmp-simd it shows the following constants being used in the fmax
operations:
vect_cst__30 = { -3.4028234663852885981170418348451692544e+38,
-3.4028234663852885981170418348451692544e+38,
-3.4028234663852885981170418348451692544e+38,
-3.4028234663852885981170418348451692544e+38 };
This is 0xff7fffff / -0x1.fffffep+127 / FLT_MAX. As a result b[0] has the wrong
value - it should be -inff.
>From gcc-bugs-return-648311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 15:17:01 2019
Return-Path: <gcc-bugs-return-648311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73196 invoked by alias); 5 Jul 2019 15: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 72593 invoked by uid 48); 5 Jul 2019 15:16:55 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Fri, 05 Jul 2019 15: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw 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-91092-4-dNbg71SnAd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00423.txt.bz2
Content-length: 1081
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
--- Comment #2 from Florian Weimer <fw at gcc dot gnu.org> ---
Current util-linux is an example:
$ ./configure
[…]
checking wchar_t support... yes
[…]
$ ./configure CC="gcc -Werror=implicit-function-declaration"
[…]
configure: WARNING: wchar_t support not found; not building widechar
[…]
configure.ac has this:
AC_ARG_ENABLE([widechar],
AS_HELP_STRING([--disable-widechar], [do not compile wide character
support]),
[], [enable_widechar=check]
)
UL_BUILD_INIT([widechar])
UL_REQUIRES_COMPILE([widechar], [[
#include <wchar.h>
#include <wctype.h>
#include <stdio.h>
]], [[
wchar_t wc;
wint_t w;
w = fgetwc(stdin);
if (w == WEOF) exit(1);
wc = w;
fputwc(wc,stdout);
]],
[wchar_t support])
#include <stdlib.h> is missing for the exit function.
This is still a large task as a result, but the cost of not doing this also
quite high in terms of time wasted on hunting down source code bugs the
compiler has already identified successfully.
>From gcc-bugs-return-648312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 15:34:19 2019
Return-Path: <gcc-bugs-return-648312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56141 invoked by alias); 5 Jul 2019 15:34: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 56117 invoked by uid 48); 5 Jul 2019 15:34:15 -0000
From: "oth+gccbugs at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/91053] __builtin___clear_cache can fail
Date: Fri, 05 Jul 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: libgcc
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: oth+gccbugs 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:
Message-ID: <bug-91053-4-6o6nXQPC1q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91053-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91053-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00424.txt.bz2
Content-length: 204
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91053
--- Comment #2 from Orion Hodson <oth+gccbugs at google dot com> ---
For sure the goal wasn't to suggest that this was due to a privileged
operation.
>From gcc-bugs-return-648313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 15:34:32 2019
Return-Path: <gcc-bugs-return-648313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56867 invoked by alias); 5 Jul 2019 15:34: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 56828 invoked by uid 48); 5 Jul 2019 15:34:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91096] Openmp vector max reduction incorrect
Date: Fri, 05 Jul 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:
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-91096-4-trySUhbNyz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91096-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91096-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00425.txt.bz2
Content-length: 427
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91096
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> ---
Ugh, arm forces -ffast-math in the vect tests :(.
>From gcc-bugs-return-648314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 15:39:09 2019
Return-Path: <gcc-bugs-return-648314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63890 invoked by alias); 5 Jul 2019 15:39: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 63425 invoked by uid 48); 5 Jul 2019 15:39:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91096] Openmp vector max reduction incorrect
Date: Fri, 05 Jul 2019 15: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:
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: attachments.created
Message-ID: <bug-91096-4-0qie35CTJb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91096-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91096-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00426.txt.bz2
Content-length: 397
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91096
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 46561
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46561&action=edit
gcc10-pr91096.patch
Does this fix it for you? Works for me with:
make check-gcc RUNTESTFLAGS='--target_board=unix\{-ffast-math,\}
vect.exp=vect-simd*.c'
on x86_64-linux.
>From gcc-bugs-return-648315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 15:46:46 2019
Return-Path: <gcc-bugs-return-648315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77239 invoked by alias); 5 Jul 2019 15: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 77183 invoked by uid 48); 5 Jul 2019 15:46:42 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Fri, 05 Jul 2019 15: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: unknown
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-91092-4-iKtPvlL8Fl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00427.txt.bz2
Content-length: 675
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
autoconf should generate #line markers in its conftests so gcc can generate
fix-its that point to the corresponding snippets in the configure.ac file (or
included m4 macro files). Of course, that would require making a new autoconf
release, which hasn't been done in years, so...
>From gcc-bugs-return-648316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 15:52:55 2019
Return-Path: <gcc-bugs-return-648316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104128 invoked by alias); 5 Jul 2019 15:52: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 103853 invoked by uid 48); 5 Jul 2019 15:52:51 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91096] Openmp vector max reduction incorrect
Date: Fri, 05 Jul 2019 15: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco 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-91096-4-ryNn8qLXK4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91096-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91096-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00428.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91096
--- Comment #3 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> Created attachment 46561 [details]
> gcc10-pr91096.patch
>
> Does this fix it for you? Works for me with:
> make check-gcc RUNTESTFLAGS='--target_board=unix\{-ffast-math,\}
> vect.exp=vect-simd*.c'
> on x86_64-linux.
Yes that ensures the tests pass.
But why does it always add a redundant test with FLT_MAX in the loop?
>From gcc-bugs-return-648317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 16:02:10 2019
Return-Path: <gcc-bugs-return-648317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118646 invoked by alias); 5 Jul 2019 16: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 118607 invoked by uid 48); 5 Jul 2019 16:02:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91096] Openmp vector max reduction incorrect
Date: Fri, 05 Jul 2019 16: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:
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-91096-4-qfPOP274yZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91096-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91096-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00429.txt.bz2
Content-length: 834
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91096
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Wilco from comment #3)
> But why does it always add a redundant test with FLT_MAX in the loop?
Which loop do you mean? If the vectorized one, OpenMP has rules on what needs
to be done, at the start of the input phase the privatized variable needs to be
initialized using the reduction initializer (for max reduction that is the
neutral element for max, -inf when honoring infinities, otherwise most negative
finite value), then perform the body of the input phase, and then at the start
of the scan phase set the privatized variable to the current prefix sum of the
reduction. I'm not using -inf for -ffast-math, because -ffinite-math-only
assumes the operands aren't infinities nor nans.
>From gcc-bugs-return-648318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 16:23:53 2019
Return-Path: <gcc-bugs-return-648318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83012 invoked by alias); 5 Jul 2019 16:23: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 82069 invoked by uid 48); 5 Jul 2019 16:23:49 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Fri, 05 Jul 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: c
X-Bugzilla-Version: unknown
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:
Message-ID: <bug-91092-4-SnrCrji3hk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00430.txt.bz2
Content-length: 239
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
And it doesn't help all the existing configure scripts, that won't get
regenerated even if a new autoconf is released.
>From gcc-bugs-return-648319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 16:27:38 2019
Return-Path: <gcc-bugs-return-648319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6215 invoked by alias); 5 Jul 2019 16:27: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 6131 invoked by uid 48); 5 Jul 2019 16:27:35 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Fri, 05 Jul 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: c
X-Bugzilla-Version: unknown
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:
Message-ID: <bug-91092-4-IF96f7pPem@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00431.txt.bz2
Content-length: 329
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Would an ugly but pragmatic approach be possible? e.g. if the first line of the
translation unit is "/* confdefs.h */ then assume GCC is being invoked by
configure, and only warn instead of giving an error.
>From gcc-bugs-return-648320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 16:30:35 2019
Return-Path: <gcc-bugs-return-648320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8547 invoked by alias); 5 Jul 2019 16: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 8335 invoked by uid 48); 5 Jul 2019 16:30:10 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Fri, 05 Jul 2019 16: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: unknown
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:
Message-ID: <bug-91092-4-SYYOKp43C6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00432.txt.bz2
Content-length: 278
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
But don't do that if -Werror=implicit-function-declaration was used explicitly,
because maybe the configure test is actually trying to detect that error.
>From gcc-bugs-return-648321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 17:25:00 2019
Return-Path: <gcc-bugs-return-648321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83558 invoked by alias); 5 Jul 2019 17:24: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 83499 invoked by uid 48); 5 Jul 2019 17:24:56 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Fri, 05 Jul 2019 17: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: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw 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-91092-4-cJS4Iak2CV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00433.txt.bz2
Content-length: 485
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
--- Comment #7 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #5)
> Would an ugly but pragmatic approach be possible? e.g. if the first line of
> the translation unit is "/* confdefs.h */ then assume GCC is being invoked
> by configure, and only warn instead of giving an error.
As far as ugly hacks go, examining the file name is probably easier (I've only
seen conftest.c so far).
>From gcc-bugs-return-648322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 17:46:59 2019
Return-Path: <gcc-bugs-return-648322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5274 invoked by alias); 5 Jul 2019 17:46: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 5229 invoked by uid 48); 5 Jul 2019 17:46:56 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Fri, 05 Jul 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: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.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-91092-4-M9pUo48MOr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00434.txt.bz2
Content-length: 165
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
--- Comment #8 from Andreas Schwab <schwab@linux-m68k.org> ---
What about cmake, metaconfig, meson, scons, ...
>From gcc-bugs-return-648323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 17:56:10 2019
Return-Path: <gcc-bugs-return-648323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20741 invoked by alias); 5 Jul 2019 17:56: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 20658 invoked by uid 48); 5 Jul 2019 17:56:07 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Fri, 05 Jul 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: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw 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-91092-4-CuCcb8rkoS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00435.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
--- Comment #9 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to Andreas Schwab from comment #8)
> What about cmake, metaconfig, meson, scons, ...
I hope that the more modern things get this correct and encourage more
high-level checks.
I plan to build Fedora with a special GCC with additional logging for these
kinds of errors, and then submit the required changes upstream.
>From gcc-bugs-return-648324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 18:03:42 2019
Return-Path: <gcc-bugs-return-648324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28675 invoked by alias); 5 Jul 2019 18: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 28567 invoked by uid 55); 5 Jul 2019 18:03:37 -0000
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67184] Missed optimization with C++11 final specifier
Date: Fri, 05 Jul 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: c++
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: paolo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: paolo.carlini at oracle dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67184-4-J12m533SeW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67184-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67184-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00436.txt.bz2
Content-length: 849
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67184
--- Comment #17 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> ---
Author: paolo
Date: Fri Jul 5 18:03:05 2019
New Revision: 273147
URL: https://gcc.gnu.org/viewcvs?rev=273147&root=gcc&view=rev
Log:
/cp
2019-07-05 Paolo Carlini <paolo.carlini@oracle.com>
PR c++/67184 (again)
PR c++/69445
* call.c (build_over_call): Devirtualize user-defined operators
coming from a base too.
(build_new_method_call_1): Do not devirtualize here.
/testsuite
2019-07-05 Paolo Carlini <paolo.carlini@oracle.com>
PR c++/67184 (again)
PR c++/69445
* g++.dg/other/final4.C: New.
Added:
trunk/gcc/testsuite/g++.dg/other/final4.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/call.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-648325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 18:03:42 2019
Return-Path: <gcc-bugs-return-648325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28696 invoked by alias); 5 Jul 2019 18: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 28569 invoked by uid 55); 5 Jul 2019 18:03:37 -0000
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/69445] Fail to devirtualize call to base class function even though derived class type is 'final'
Date: Fri, 05 Jul 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: 6.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: paolo 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-69445-4-k9XLGK6OD6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69445-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69445-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00437.txt.bz2
Content-length: 848
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69445
--- Comment #7 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> ---
Author: paolo
Date: Fri Jul 5 18:03:05 2019
New Revision: 273147
URL: https://gcc.gnu.org/viewcvs?rev=273147&root=gcc&view=rev
Log:
/cp
2019-07-05 Paolo Carlini <paolo.carlini@oracle.com>
PR c++/67184 (again)
PR c++/69445
* call.c (build_over_call): Devirtualize user-defined operators
coming from a base too.
(build_new_method_call_1): Do not devirtualize here.
/testsuite
2019-07-05 Paolo Carlini <paolo.carlini@oracle.com>
PR c++/67184 (again)
PR c++/69445
* g++.dg/other/final4.C: New.
Added:
trunk/gcc/testsuite/g++.dg/other/final4.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/call.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-648326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 18:05:08 2019
Return-Path: <gcc-bugs-return-648326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30652 invoked by alias); 5 Jul 2019 18:05: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 30574 invoked by uid 48); 5 Jul 2019 18:05:05 -0000
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67184] Missed optimization with C++11 final specifier
Date: Fri, 05 Jul 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: c++
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: paolo.carlini at oracle dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: paolo.carlini at oracle dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-67184-4-5KTgMUJFTx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67184-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67184-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00438.txt.bz2
Content-length: 487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67184
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #18 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Finally should be completely fixed without regressions.
>From gcc-bugs-return-648327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 18:31:15 2019
Return-Path: <gcc-bugs-return-648327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9479 invoked by alias); 5 Jul 2019 18:31: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 3114 invoked by uid 48); 5 Jul 2019 18:31:08 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91097] New: [10 regression] many ICEs starting with r273131
Date: Fri, 05 Jul 2019 18:31: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: 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-91097-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00439.txt.bz2
Content-length: 19950
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91097
Bug ID: 91097
Summary: [10 regression] many ICEs starting with r273131
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
There were reports of a bunch of other ICEs recently but I don't think this
set.
One example:
spawn -ignore SIGHUP /home/seurer/gcc/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/build/gcc-test/gcc/
/home/seurer/gcc/gcc-test/gcc/testsuite/gcc.dg/graphite/block-1.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -O2 -ffast-math -floop-nest-optimize
-fdump-tree-graphite-all -lm -o ./block-1.exe
during GIMPLE pass: graphite
dump file: block-1.c.150t.graphite
/home/seurer/gcc/gcc-test/gcc/testsuite/gcc.dg/graphite/block-1.c: In function
'main':
/home/seurer/gcc/gcc-test/gcc/testsuite/gcc.dg/graphite/block-1.c:13:1:
internal compiler error: Segmentation fault
0x10a7048b crash_signal
/home/seurer/gcc/gcc-test/gcc/toplev.c:326
0x10c69600 make_temp_ssa_name
/home/seurer/gcc/gcc-test/gcc/tree-ssanames.h:152
0x10c69600 create_iv(tree_node*, tree_node*, tree_node*, loop*,
gimple_stmt_iterator*, bool, tree_node**, tree_node**)
/home/seurer/gcc/gcc-test/gcc/tree-ssa-loop-manip.c:81
0x1043f02f create_empty_loop_on_edge(edge_def*, tree_node*, tree_node*,
tree_node*, tree_node*, tree_node**, tree_node**, loop*)
/home/seurer/gcc/gcc-test/gcc/cfgloopmanip.c:831
0x11508c2f translate_isl_ast_to_gimple::graphite_create_new_loop(edge_def*,
isl_ast_node*, loop*, tree_node*, tree_node*, tree_node*, std::map<isl_id*,
tree_node*, std::less<isl_id*>, std::allocator<std::pair<isl_id* const,
tree_node*> > >&)
/home/seurer/gcc/gcc-test/gcc/graphite-isl-ast-to-gimple.c:593
0x1150a123 translate_isl_ast_to_gimple::translate_isl_ast_for_loop(loop*,
isl_ast_node*, edge_def*, tree_node*, tree_node*, tree_node*, std::map<isl_id*,
tree_node*, std::less<isl_id*>, std::allocator<std::pair<isl_id* const,
tree_node*> > >&)
/home/seurer/gcc/gcc-test/gcc/graphite-isl-ast-to-gimple.c:618
0x1150a5b7 translate_isl_ast_to_gimple::translate_isl_ast_node_for(loop*,
isl_ast_node*, edge_def*, std::map<isl_id*, tree_node*, std::less<isl_id*>,
std::allocator<std::pair<isl_id* const, tree_node*> > >&)
/home/seurer/gcc/gcc-test/gcc/graphite-isl-ast-to-gimple.c:753
0x1150a933 translate_isl_ast_to_gimple::translate_isl_ast_node_block(loop*,
isl_ast_node*, edge_def*, std::map<isl_id*, tree_node*, std::less<isl_id*>,
std::allocator<std::pair<isl_id* const, tree_node*> > >&)
/home/seurer/gcc/gcc-test/gcc/graphite-isl-ast-to-gimple.c:861
0x1150ae8f graphite_regenerate_ast_isl(scop*)
/home/seurer/gcc/gcc-test/gcc/graphite-isl-ast-to-gimple.c:1511
0x115043bf graphite_transform_loops()
/home/seurer/gcc/gcc-test/gcc/graphite.c:472
0x11504ad3 graphite_transforms
/home/seurer/gcc/gcc-test/gcc/graphite.c:538
0x11504ad3 execute
/home/seurer/gcc/gcc-test/gcc/graphite.c:615
Complete list:
> FAIL: gcc.dg/graphite/block-1.c (internal compiler error)
> FAIL: gcc.dg/graphite/block-1.c (test for excess errors)
> FAIL: gcc.dg/graphite/block-5.c (internal compiler error)
> FAIL: gcc.dg/graphite/block-5.c (test for excess errors)
> FAIL: gcc.dg/graphite/block-6.c (internal compiler error)
> FAIL: gcc.dg/graphite/block-6.c (test for excess errors)
> FAIL: gcc.dg/graphite/block-pr47654.c (internal compiler error)
> FAIL: gcc.dg/graphite/block-pr47654.c (test for excess errors)
> FAIL: gcc.dg/graphite/fuse-1.c (internal compiler error)
> FAIL: gcc.dg/graphite/fuse-1.c (test for excess errors)
> FAIL: gcc.dg/graphite/fuse-2.c (internal compiler error)
> FAIL: gcc.dg/graphite/fuse-2.c (test for excess errors)
> FAIL: gcc.dg/graphite/id-10.c (internal compiler error)
> FAIL: gcc.dg/graphite/id-10.c (test for excess errors)
> FAIL: gcc.dg/graphite/id-16.c (internal compiler error)
> FAIL: gcc.dg/graphite/id-16.c (test for excess errors)
> FAIL: gcc.dg/graphite/id-25.c (internal compiler error)
> FAIL: gcc.dg/graphite/id-25.c (test for excess errors)
> FAIL: gcc.dg/graphite/id-pr46834.c (internal compiler error)
> FAIL: gcc.dg/graphite/id-pr46834.c (test for excess errors)
> FAIL: gcc.dg/graphite/id-pr47046.c (internal compiler error)
> FAIL: gcc.dg/graphite/id-pr47046.c (test for excess errors)
> FAIL: gcc.dg/graphite/id-pr48805.c (internal compiler error)
> FAIL: gcc.dg/graphite/id-pr48805.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-0.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-0.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-1.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-1.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-10.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-10.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-11.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-11.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-12.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-12.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-12.c scan-tree-dump graphite "tiled by"
> FAIL: gcc.dg/graphite/interchange-13.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-13.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-14.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-14.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-14.c scan-tree-dump graphite "tiled by"
> FAIL: gcc.dg/graphite/interchange-15.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-15.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-15.c scan-tree-dump graphite "tiled by"
> FAIL: gcc.dg/graphite/interchange-2.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-2.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-3.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-3.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-4.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-4.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-5.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-5.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-6.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-6.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-7.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-7.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-8.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-8.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-8.c scan-tree-dump graphite "tiled by"
> FAIL: gcc.dg/graphite/interchange-9.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-9.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-mvt.c (internal compiler error)
> FAIL: gcc.dg/graphite/interchange-mvt.c (test for excess errors)
> FAIL: gcc.dg/graphite/interchange-mvt.c scan-tree-dump graphite "tiled by"
> FAIL: gcc.dg/graphite/pr29330.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr29330.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr29581-1.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr29581-1.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr29581-2.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr29581-2.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr29581-3.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr29581-3.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr29581-4.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr29581-4.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr30565.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr30565.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr31183.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr31183.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr33576.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr33576.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr36287.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr36287.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr37686.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr37686.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr42211.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr42211.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr42914.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr42914.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr42917.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr42917.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr43657.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr43657.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr46168.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr46168.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr46185.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr46185.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr46966.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr46966.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr68428.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr68428.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr68493.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr68493.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr68756.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr68756.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr69068.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr69068.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr69292.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr69292.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr69728.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr69728.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr70045.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr70045.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr71575-1.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr71575-1.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr77362.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr77362.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr80906.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr80906.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr80906.c scan-tree-dump graphite "isl AST to Gimple succeeded"
> FAIL: gcc.dg/graphite/pr81373-2.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr81373-2.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr81373.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr81373.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr82421.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr82421.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr83255.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr83255.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr83255.c scan-tree-dump graphite "loop nest optimized"
> FAIL: gcc.dg/graphite/pr83385.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr83385.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr83668.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr83668.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr84204.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr84204.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr84205.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr84205.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr84872.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr84872.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr85935.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr85935.c (test for excess errors)
> FAIL: gcc.dg/graphite/pr87931.c (internal compiler error)
> FAIL: gcc.dg/graphite/pr87931.c (test for excess errors)
> FAIL: gcc.dg/graphite/run-id-1.c (internal compiler error)
> FAIL: gcc.dg/graphite/run-id-1.c (test for excess errors)
> FAIL: gcc.dg/graphite/run-id-pr47653.c (internal compiler error)
> FAIL: gcc.dg/graphite/run-id-pr47653.c (test for excess errors)
> FAIL: gcc.dg/graphite/run-id-pr47654.c (internal compiler error)
> FAIL: gcc.dg/graphite/run-id-pr47654.c (test for excess errors)
> FAIL: gcc.dg/graphite/run-id-pr67700-1.c (internal compiler error)
> FAIL: gcc.dg/graphite/run-id-pr67700-1.c (test for excess errors)
> FAIL: gcc.dg/graphite/uns-block-1.c (internal compiler error)
> FAIL: gcc.dg/graphite/uns-block-1.c (test for excess errors)
> FAIL: gcc.dg/graphite/uns-interchange-12.c (internal compiler error)
> FAIL: gcc.dg/graphite/uns-interchange-12.c (test for excess errors)
> FAIL: gcc.dg/graphite/uns-interchange-12.c scan-tree-dump graphite "tiled by"
> FAIL: gcc.dg/graphite/uns-interchange-14.c (internal compiler error)
> FAIL: gcc.dg/graphite/uns-interchange-14.c (test for excess errors)
> FAIL: gcc.dg/graphite/uns-interchange-14.c scan-tree-dump graphite "tiled by"
> FAIL: gcc.dg/graphite/uns-interchange-15.c (internal compiler error)
> FAIL: gcc.dg/graphite/uns-interchange-15.c (test for excess errors)
> FAIL: gcc.dg/graphite/uns-interchange-15.c scan-tree-dump graphite "tiled by"
> FAIL: gcc.dg/graphite/uns-interchange-9.c (internal compiler error)
> FAIL: gcc.dg/graphite/uns-interchange-9.c (test for excess errors)
> FAIL: gcc.dg/graphite/uns-interchange-mvt.c (internal compiler error)
> FAIL: gcc.dg/graphite/uns-interchange-mvt.c (test for excess errors)
> FAIL: gcc.dg/graphite/uns-interchange-mvt.c scan-tree-dump graphite "tiled by"
> FAIL: gfortran.dg/graphite/PR67518.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/PR67518.f90 -O (test for excess errors)
> FAIL: gfortran.dg/graphite/id-14.f -O (internal compiler error)
> FAIL: gfortran.dg/graphite/id-14.f -O (test for excess errors)
> FAIL: gfortran.dg/graphite/id-15.f -O (internal compiler error)
> FAIL: gfortran.dg/graphite/id-15.f -O (test for excess errors)
> FAIL: gfortran.dg/graphite/id-27.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/id-27.f90 -O (test for excess errors)
> FAIL: gfortran.dg/graphite/id-28.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/id-28.f90 -O (test for excess errors)
> FAIL: gfortran.dg/graphite/id-9.f -O (internal compiler error)
> FAIL: gfortran.dg/graphite/id-9.f -O (test for excess errors)
> FAIL: gfortran.dg/graphite/interchange-1.f -O (internal compiler error)
> FAIL: gfortran.dg/graphite/interchange-1.f -O (test for excess errors)
> FAIL: gfortran.dg/graphite/interchange-3.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/interchange-3.f90 -O (test for excess errors)
> FAIL: gfortran.dg/graphite/pr14741.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/pr14741.f90 -O (test for excess errors)
> FAIL: gfortran.dg/graphite/pr29581.f90 -O1 (internal compiler error)
> FAIL: gfortran.dg/graphite/pr29581.f90 -O1 (test for excess errors)
> FAIL: gfortran.dg/graphite/pr29832.f90 -O1 (internal compiler error)
> FAIL: gfortran.dg/graphite/pr29832.f90 -O1 (test for excess errors)
> FAIL: gfortran.dg/graphite/pr29832.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (internal compiler error)
> FAIL: gfortran.dg/graphite/pr29832.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors)
> FAIL: gfortran.dg/graphite/pr29832.f90 -O3 -g (internal compiler error)
> FAIL: gfortran.dg/graphite/pr29832.f90 -O3 -g (test for excess errors)
> FAIL: gfortran.dg/graphite/pr39516.f -O (internal compiler error)
> FAIL: gfortran.dg/graphite/pr39516.f -O (test for excess errors)
> FAIL: gfortran.dg/graphite/pr42285.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/pr42285.f90 -O (test for excess errors)
> FAIL: gfortran.dg/graphite/pr42334.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/pr42334.f90 -O (test for excess errors)
> FAIL: gfortran.dg/graphite/pr43097.f -O (internal compiler error)
> FAIL: gfortran.dg/graphite/pr43097.f -O (test for excess errors)
> FAIL: gfortran.dg/graphite/pr68453.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/pr68453.f90 -O (test for excess errors)
> FAIL: gfortran.dg/graphite/pr68550-2.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/pr68550-2.f90 -O (test for excess errors)
> FAIL: gfortran.dg/graphite/pr71351.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/pr71351.f90 -O (test for excess errors)
> FAIL: gfortran.dg/graphite/pr71898.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/pr71898.f90 -O (test for excess errors)
> FAIL: gfortran.dg/graphite/pr82449.f -O (internal compiler error)
> FAIL: gfortran.dg/graphite/pr82449.f -O (test for excess errors)
> FAIL: gfortran.dg/graphite/pr90240.f -O (internal compiler error)
> FAIL: gfortran.dg/graphite/pr90240.f -O (test for excess errors)
> FAIL: gfortran.dg/graphite/run-id-1.f -O (internal compiler error)
> FAIL: gfortran.dg/graphite/run-id-1.f -O (test for excess errors)
> FAIL: gfortran.dg/graphite/run-id-2.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/run-id-2.f90 -O (test for excess errors)
> FAIL: gfortran.dg/graphite/vect-pr40979.f90 -O (internal compiler error)
> FAIL: gfortran.dg/graphite/vect-pr40979.f90 -O (test for excess errors)
> FAIL: libgomp.graphite/bounds.c (internal compiler error)
> FAIL: libgomp.graphite/bounds.c (test for excess errors)
> FAIL: libgomp.graphite/bounds.c scan-tree-dump-times graphite "0 loops carried no dependency" 1
> FAIL: libgomp.graphite/force-parallel-1.c (internal compiler error)
> FAIL: libgomp.graphite/force-parallel-1.c (test for excess errors)
> FAIL: libgomp.graphite/force-parallel-1.c scan-tree-dump-times graphite "2 loops carried no dependency" 1
> FAIL: libgomp.graphite/force-parallel-2.c (internal compiler error)
> FAIL: libgomp.graphite/force-parallel-2.c (test for excess errors)
> FAIL: libgomp.graphite/force-parallel-2.c scan-tree-dump-times graphite "2 loops carried no dependency" 1
> FAIL: libgomp.graphite/force-parallel-3.c (internal compiler error)
> FAIL: libgomp.graphite/force-parallel-3.c (test for excess errors)
> FAIL: libgomp.graphite/force-parallel-3.c scan-tree-dump-times graphite "4 loops carried no dependency" 1
> FAIL: libgomp.graphite/force-parallel-4.c (internal compiler error)
> FAIL: libgomp.graphite/force-parallel-4.c (test for excess errors)
> FAIL: libgomp.graphite/force-parallel-4.c scan-tree-dump-times graphite "1 loops carried no dependency" 1
> FAIL: libgomp.graphite/force-parallel-6.c (internal compiler error)
> FAIL: libgomp.graphite/force-parallel-6.c (test for excess errors)
> FAIL: libgomp.graphite/force-parallel-6.c scan-tree-dump-times graphite "1 loops carried no dependency" 1
> FAIL: libgomp.graphite/force-parallel-6.c scan-tree-dump-times optimized "loopfn.0" 4
> FAIL: libgomp.graphite/force-parallel-7.c (internal compiler error)
> FAIL: libgomp.graphite/force-parallel-7.c (test for excess errors)
> FAIL: libgomp.graphite/force-parallel-7.c scan-tree-dump-times graphite "5 loops carried no dependency" 1
> FAIL: libgomp.graphite/force-parallel-8.c (internal compiler error)
> FAIL: libgomp.graphite/force-parallel-8.c (test for excess errors)
> FAIL: libgomp.graphite/force-parallel-8.c scan-tree-dump-times graphite "5 loops carried no dependency" 1
> FAIL: libgomp.graphite/force-parallel-9.c (internal compiler error)
> FAIL: libgomp.graphite/force-parallel-9.c (test for excess errors)
> FAIL: libgomp.graphite/force-parallel-9.c scan-tree-dump-times graphite "4 loops carried no dependency" 1
<
>From gcc-bugs-return-648328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 18:38:00 2019
Return-Path: <gcc-bugs-return-648328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21887 invoked by alias); 5 Jul 2019 18:38: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 21832 invoked by uid 48); 5 Jul 2019 18:37:57 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91077] [8/9/10 Regression] Wrong indexing when using a pointer
Date: Fri, 05 Jul 2019 18: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: 9.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-91077-4-jEuFPizS6I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91077-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91077-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00440.txt.bz2
Content-length: 452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91077
--- Comment #6 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 46562
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46562&action=edit
Patch for the PR
This fixes the original problem and regtests OK.
I need to think this through and to test it against the other version of the
problem.
One way or another, I will post the fix and a testcase tomorrow.
Regards
Paul
>From gcc-bugs-return-648329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 18:39:52 2019
Return-Path: <gcc-bugs-return-648329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25254 invoked by alias); 5 Jul 2019 18:39: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 23402 invoked by uid 48); 5 Jul 2019 18:39:49 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91097] [10 regression] many ICEs starting with r273131
Date: Fri, 05 Jul 2019 18: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:
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status bug_file_loc resolution target_milestone
Message-ID: <bug-91097-4-YHA8xeRhIw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91097-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91097-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00441.txt.bz2
Content-length: 688
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91097
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
URL| |https://gcc.gnu.org/ml/gcc-
| |patches/2019-07/msg00472.ht
| |ml
Resolution|--- |FIXED
Target Milestone|--- |10.0
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
.
>From gcc-bugs-return-648330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 18:40:28 2019
Return-Path: <gcc-bugs-return-648330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51929 invoked by alias); 5 Jul 2019 18:40: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 48208 invoked by uid 48); 5 Jul 2019 18:40:24 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91077] [8/9/10 Regression] Wrong indexing when using a pointer
Date: Fri, 05 Jul 2019 18: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.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91077-4-IQ4PoRnuOK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91077-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91077-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00442.txt.bz2
Content-length: 1743
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91077
--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to ygal klein from comment #4)
> The following code presents a difference (!) between gfortran 8.2 and
> gfortran 9.1:
>
> program test
> implicit none
> integer, parameter :: length = 2
> real(8), dimension(length) :: a, b
> integer :: i
>
> type point
> real(8) :: x
> end type point
>
> type points
> type(point), dimension(:), pointer :: np=>null()
> end type points
>
> type stored
> integer :: l
> type(points), pointer :: nfpoint=>null()
> end type stored
>
> type(stored), dimension(:), pointer :: std=>null()
>
>
> allocate(std(1))
> allocate(std(1)%nfpoint)
> allocate(std(1)%nfpoint%np(length))
> std(1)%nfpoint%np(1)%x = 0.3d0
> std(1)%nfpoint%np(2)%x = 0.3555d0
>
> do i = 1, length
> write(*, "('std(1)%nfpoint%np(',i1,')%x = ',1e22.14)") i,
> std(1)%nfpoint%np(i)%x
> end do
> do i = 1, length
> write(*, "('std(1)%nfpoint%np(1:',i1,')%x = ',2e22.14)") i,
> std(1)%nfpoint%np(1:i)%x
> end do
> a = std(1)%nfpoint%np(1:2)%x
> b = [std(1)%nfpoint%np(1)%x, std(1)%nfpoint%np(2)%x]
> if (norm2(a - b) .gt. 1d-3) then
> write(*,*) 'failure'
> else
> write(*, *) 'success'
> end if
> end program test
>
>
> Running with gfortan-8.2 results with 'success' and running with
> gfortran-9.1 results with 'failure'.
>
> Removing the integer variable 'l' from the type 'stored' makes both versions
> (8.2 and 9.1) end with 'success'
>
> Thanks.
PS. The posted patch works with this guy too.
Thanks for posting the problem and staying in touch.
Regards
Paul
>From gcc-bugs-return-648331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 19:34:56 2019
Return-Path: <gcc-bugs-return-648331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58198 invoked by alias); 5 Jul 2019 19:34: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 58157 invoked by uid 48); 5 Jul 2019 19:34:52 -0000
From: "elowe at elowe dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 19:34: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.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: elowe at elowe 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-61577-4-3vYMAaRtzM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00443.txt.bz2
Content-length: 893
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #44 from EML <elowe at elowe dot com> ---
The aforementioned gprel patch I think is incorrect on HPUX, given this in
ia64.c
/* For HPUX, it is illegal to have relocations in shared segments. */
static int
ia64_hpux_reloc_rw_mask (void)
{
return 3;
}
Therefore, if I understand correctly, HP requires all relocations, even to
local data, to be dynamic. And I understand the entire purpose of the earlier
patch is in direct contradiction to this.
Removing this (by adding a !TARGET_HPUX) to ia64.c results in a little
progress.
I can now compile and run Hello World. Woot.
However, I have likely reached the same problem as "Word" - the EOF conftest in
libstdc++v3 fails.
(conftest actually crashed a couple times, the latest is for EOF)
So Hello World runs, but other relatively straightforward programs do not.
>From gcc-bugs-return-648333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 19:54:21 2019
Return-Path: <gcc-bugs-return-648333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85723 invoked by alias); 5 Jul 2019 19:54: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 85531 invoked by uid 48); 5 Jul 2019 19:54:18 -0000
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/90893] ODR violation
Date: Fri, 05 Jul 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: d
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ibuclaw at gdcproject 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: cc
Message-ID: <bug-90893-4-OcDsjQEIZ4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90893-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90893-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00445.txt.bz2
Content-length: 447
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90893
Iain Buclaw <ibuclaw at gdcproject dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jamborm at gcc dot gnu.org
--- Comment #2 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
*** Bug 91061 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-648332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 19:54:21 2019
Return-Path: <gcc-bugs-return-648332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85688 invoked by alias); 5 Jul 2019 19:54: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 85477 invoked by uid 48); 5 Jul 2019 19:54:18 -0000
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/91061] Enum type libcall_type violates the C++ One Definition Rule
Date: Fri, 05 Jul 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: d
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ibuclaw at gdcproject dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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_status resolution
Message-ID: <bug-91061-4-W0pGkaRv4n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91061-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91061-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00444.txt.bz2
Content-length: 510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91061
Iain Buclaw <ibuclaw at gdcproject dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
Duplicate of pr90893.
*** This bug has been marked as a duplicate of bug 90893 ***
>From gcc-bugs-return-648334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 20:09:57 2019
Return-Path: <gcc-bugs-return-648334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83043 invoked by alias); 5 Jul 2019 20:09: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 82986 invoked by uid 55); 5 Jul 2019 20:09:51 -0000
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 20:09: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.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: dave.anglin at bell 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-61577-4-VwKHUPpUaF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00446.txt.bz2
Content-length: 2943
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #45 from dave.anglin at bell dot net ---
On 2019-07-05 3:34 p.m., elowe at elowe dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
>
> --- Comment #44 from EML <elowe at elowe dot com> ---
> The aforementioned gprel patch I think is incorrect on HPUX, given this in
> ia64.c
>
> /* For HPUX, it is illegal to have relocations in shared segments. */
>
> static int
> ia64_hpux_reloc_rw_mask (void)
> {
> return 3;
> }
>
>
> Therefore, if I understand correctly, HP requires all relocations, even to
> local data, to be dynamic. And I understand the entire purpose of the earlier
> patch is in direct contradiction to this.
>
> Removing this (by adding a !TARGET_HPUX) to ia64.c results in a little
> progress.
I think this is wrong, but this is getting closer to a fix. Would like to see
the .s output.
We have in varasm.c:
section *
default_select_rtx_section (machine_mode mode ATTRIBUTE_UNUSED,
                           rtx x,
                           unsigned HOST_WIDE_INT align ATTRIBUTE_UNUSED)
{
 if (compute_reloc_for_rtx (x) & targetm.asm_out.reloc_rw_mask ())
   return data_section;
 else
   return readonly_data_section;
}
As you can see, when a bit is set in the reloc_rw_mask and the rtx requires
relocation,
the rtx is output in the data section.
I think the problem is the rtx is actually output in .rodata and the HP dynamic
linker
can't do this relocation in .rodata.
The ia64 target is actually using default_elf_select_rtx_section:
section *
default_elf_select_rtx_section (machine_mode mode, rtx x,
                               unsigned HOST_WIDE_INT align)
{
 int reloc = compute_reloc_for_rtx (x);
 /* ??? Handle small data here somehow. */
 if (reloc & targetm.asm_out.reloc_rw_mask ())
   {
     if (reloc == 1)
       return get_named_section (NULL, ".data.rel.ro.local", 1);
     else
       return get_named_section (NULL, ".data.rel.ro", 3);
   }
 return mergeable_constant_section (mode, align, 0);
}
It seems to me compute_reloc_for_rtx() must be doing the wrong thing for the
rtx
(i.e., returning 0).
You could dump the RTL by adding "-da" to the compile options. Then, you could
upload
the "final" file.
>From gcc-bugs-return-648335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 20:11:52 2019
Return-Path: <gcc-bugs-return-648335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85414 invoked by alias); 5 Jul 2019 20:11: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 85367 invoked by uid 48); 5 Jul 2019 20:11:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91098] New: [10 Regression] internal compiler error: tree check: expected var_decl or field_decl or function_decl or type_decl or template_decl, have using_decl in build_deduction_guide, at cp/pt.c:27167
Date: Fri, 05 Jul 2019 20: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: 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 target_milestone
Message-ID: <bug-91098-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00447.txt.bz2
Content-length: 3627
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91098
Bug ID: 91098
Summary: [10 Regression] internal compiler error: tree check:
expected var_decl or field_decl or function_decl or
type_decl or template_decl, have using_decl in
build_deduction_guide, at cp/pt.c:27167
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
Target Milestone: ---
This was rejected by GCC 9 but gives an ICE with trunk:
// { dg-options "-std=gnu++17" }
template<typename T, bool = true>
struct base;
template<typename T>
struct base<T, true>
{
base(T& t) : p(&t) { }
base(const base&) = delete;
T* p;
};
template<typename T>
struct atomic_ref : base<T>
{
using base<T>::base;
};
int main()
{
int i = 0;
atomic_ref r(i);
}
ctad_ice.cc: In function 'int main()':
ctad_ice.cc:22:17: internal compiler error: tree check: expected var_decl or
field_decl or function_decl or type_decl or template_decl, have using_decl in
build_deduction_guide, at cp/pt.c:27167
22 | atomic_ref r(i);
| ^
0x77ec68 tree_check_failed(tree_node const*, char const*, int, char const*,
...)
/home/jwakely/src/gcc/gcc/gcc/tree.c:9897
0x98461c tree_check5(tree_node*, char const*, int, char const*, tree_code,
tree_code, tree_code, tree_code, tree_code)
/home/jwakely/src/gcc/gcc/gcc/tree.h:3288
0x98461c build_deduction_guide
/home/jwakely/src/gcc/gcc/gcc/cp/pt.c:27167
0x9851e0 do_class_deduction
/home/jwakely/src/gcc/gcc/gcc/cp/pt.c:27399
0x9851e0 do_auto_deduction(tree_node*, tree_node*, tree_node*, int,
auto_deduction_context, tree_node*, int)
/home/jwakely/src/gcc/gcc/gcc/cp/pt.c:27533
0x8c083f cp_finish_decl(tree_node*, tree_node*, bool, tree_node*, int)
/home/jwakely/src/gcc/gcc/gcc/cp/decl.c:7018
0x96376b cp_parser_init_declarator
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:20491
0x945c6f cp_parser_simple_declaration
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:13525
0x947989 cp_parser_declaration_statement
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:12955
0x9485d3 cp_parser_statement
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:11284
0x949500 cp_parser_statement_seq_opt
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:11646
0x9495d7 cp_parser_compound_statement
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:11600
0x962500 cp_parser_function_body
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:22624
0x962500 cp_parser_ctor_initializer_opt_and_function_body
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:22675
0x962d86 cp_parser_function_definition_after_declarator
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:27776
0x963b1e cp_parser_function_definition_from_specifiers_and_declarator
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:27692
0x963b1e cp_parser_init_declarator
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:20261
0x945c6f cp_parser_simple_declaration
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:13525
0x96a402 cp_parser_declaration
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:13222
0x96abaf cp_parser_translation_unit
/home/jwakely/src/gcc/gcc/gcc/cp/parser.c:4690
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-648336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 20:28:51 2019
Return-Path: <gcc-bugs-return-648336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6101 invoked by alias); 5 Jul 2019 20:28: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 6055 invoked by uid 48); 5 Jul 2019 20:28:47 -0000
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 20: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: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: bugzilla-gcc at thewrittenword 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-61577-4-uCJKrQ1XxC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00448.txt.bz2
Content-length: 360
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #46 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to dave.anglin from comment #45)
>
> You could dump the RTL by adding "-da" to the compile options. Then, you
> could upload the "final" file.
I am uploading hello.c, hello.s, and hello.c.313r.dfinish.
>From gcc-bugs-return-648337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 20:29:21 2019
Return-Path: <gcc-bugs-return-648337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6918 invoked by alias); 5 Jul 2019 20:29: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 6863 invoked by uid 48); 5 Jul 2019 20:29:18 -0000
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 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: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: bugzilla-gcc at thewrittenword 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-61577-4-cTHeUWXeM2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00449.txt.bz2
Content-length: 260
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #47 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
Created attachment 46563
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46563&action=edit
Hello.c test program
>From gcc-bugs-return-648338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 20:30:46 2019
Return-Path: <gcc-bugs-return-648338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10078 invoked by alias); 5 Jul 2019 20:30: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 8922 invoked by uid 48); 5 Jul 2019 20:30:23 -0000
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 20:30: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.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: bugzilla-gcc at thewrittenword 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-61577-4-miBQTyduzY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00450.txt.bz2
Content-length: 560
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #48 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
Created attachment 46564
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46564&action=edit
hello.s assembly output of hello.c
/opt/build/china/gcc-8.3.0/.obj-/./gcc/xgcc
-B/opt/build/china/gcc-8.3.0/.obj-/./gcc/
-B/opt/build/gcc8/ia64-hp-hpux11.31/bin/
-B/opt/build/gcc8/ia64-hp-hpux11.31/lib/ -isystem
/opt/build/gcc8/ia64-hp-hpux11.31/include -isystem
/opt/build/gcc8/ia64-hp-hpux11.31/sys-include -S hello.c
>From gcc-bugs-return-648339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 20:31:05 2019
Return-Path: <gcc-bugs-return-648339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11111 invoked by alias); 5 Jul 2019 20:31: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 11071 invoked by uid 48); 5 Jul 2019 20:31:02 -0000
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 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: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: bugzilla-gcc at thewrittenword 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-61577-4-brz5N1IqUV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00451.txt.bz2
Content-length: 555
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #49 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
Created attachment 46565
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46565&action=edit
hello.c compiled with -da
/opt/build/china/gcc-8.3.0/.obj-/./gcc/xgcc
-B/opt/build/china/gcc-8.3.0/.obj-/./gcc/
-B/opt/build/gcc8/ia64-hp-hpux11.31/bin/
-B/opt/build/gcc8/ia64-hp-hpux11.31/lib/ -isystem
/opt/build/gcc8/ia64-hp-hpux11.31/include -isystem
/opt/build/gcc8/ia64-hp-hpux11.31/sys-include -g -da hello.c
>From gcc-bugs-return-648341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 20:52:19 2019
Return-Path: <gcc-bugs-return-648341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73719 invoked by alias); 5 Jul 2019 20:52: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 73610 invoked by uid 55); 5 Jul 2019 20:52:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/69445] Fail to devirtualize call to base class function even though derived class type is 'final'
Date: Fri, 05 Jul 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: tree-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub 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-69445-4-vvLbC88252@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69445-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69445-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00453.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69445
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jul 5 20:51:44 2019
New Revision: 273149
URL: https://gcc.gnu.org/viewcvs?rev=273149&root=gcc&view=rev
Log:
PR c++/67184
PR c++/69445
* call.c (build_new_method_call_1): Remove set but not used variable
binfo.
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/call.c
>From gcc-bugs-return-648340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 20:52:19 2019
Return-Path: <gcc-bugs-return-648340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73714 invoked by alias); 5 Jul 2019 20:52: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 73598 invoked by uid 55); 5 Jul 2019 20:52:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67184] Missed optimization with C++11 final specifier
Date: Fri, 05 Jul 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: c++
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
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: paolo.carlini at oracle dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67184-4-Vyok31jUfJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67184-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67184-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00452.txt.bz2
Content-length: 456
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67184
--- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jul 5 20:51:44 2019
New Revision: 273149
URL: https://gcc.gnu.org/viewcvs?rev=273149&root=gcc&view=rev
Log:
PR c++/67184
PR c++/69445
* call.c (build_new_method_call_1): Remove set but not used variable
binfo.
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/call.c
>From gcc-bugs-return-648342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 21:13:45 2019
Return-Path: <gcc-bugs-return-648342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111659 invoked by alias); 5 Jul 2019 21:13: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 111598 invoked by uid 55); 5 Jul 2019 21:13:42 -0000
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 21:13: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.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: dave.anglin at bell 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-61577-4-yqUQm9ZEMm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00454.txt.bz2
Content-length: 492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #50 from dave.anglin at bell dot net ---
On 2019-07-05 4:28 p.m., bugzilla-gcc at thewrittenword dot com wrote:
> I am uploading hello.c, hello.s, and hello.c.313r.dfinish.
I'm still puzzled why .LC0 ends up in .rodata.
(insn 30 2 34 2 (set (reg:DI 120 out0 [+-4 ])
(minus:DI (symbol_ref/f:SI ("*.LC0") [flags 0x2] <var_decl 776633c8
*.LC0>)
(reg:DI 1 r1))) "hello.c":5 108 {*gprel64_offset}
(nil))
>From gcc-bugs-return-648343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 21:15:50 2019
Return-Path: <gcc-bugs-return-648343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113748 invoked by alias); 5 Jul 2019 21:15: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 113704 invoked by uid 48); 5 Jul 2019 21:15:47 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/44032] internals documentation is not legally safe to use
Date: Fri, 05 Jul 2019 21:15: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: 4.6.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: blocker
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-44032-4-ed5eDcxcKz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-44032-4@http.gcc.gnu.org/bugzilla/>
References: <bug-44032-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00455.txt.bz2
Content-length: 306
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44032
--- Comment #7 from Eric Gallager <egallager at gcc dot gnu.org> ---
Richard says the FSF doesn't object to combinations of GFDL code from the
manual with GPL code from the source and that we can put a statement to this
effect in the internals manual.
>From gcc-bugs-return-648344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 21:18:48 2019
Return-Path: <gcc-bugs-return-648344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115542 invoked by alias); 5 Jul 2019 21: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 115487 invoked by uid 48); 5 Jul 2019 21:18:43 -0000
From: "fourmisain+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/70769] function definition wrongfully allowed inside comma separated member declaration list
Date: Fri, 05 Jul 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: c++
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: trivial
X-Bugzilla-Who: fourmisain+gcc 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: version
Message-ID: <bug-70769-4-570AAOJyQN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70769-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70769-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00456.txt.bz2
Content-length: 362
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70769
fourmisain+gcc at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|5.2.0 |9.1.0
--- Comment #1 from fourmisain+gcc at gmail dot com ---
Reconfirmed for 9.1.0
>From gcc-bugs-return-648345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 21:34:59 2019
Return-Path: <gcc-bugs-return-648345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70762 invoked by alias); 5 Jul 2019 21:34: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 70696 invoked by uid 48); 5 Jul 2019 21:34:55 -0000
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 21:34: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.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: bugzilla-gcc at thewrittenword 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-61577-4-C3ZtaHybQo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00457.txt.bz2
Content-length: 1880
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #51 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to dave.anglin from comment #50)
> On 2019-07-05 4:28 p.m., bugzilla-gcc at thewrittenword dot com wrote:
> > I am uploading hello.c, hello.s, and hello.c.313r.dfinish.
> I'm still puzzled why .LC0 ends up in .rodata.
>
> (insn 30 2 34 2 (set (reg:DI 120 out0 [+-4 ])
> (minus:DI (symbol_ref/f:SI ("*.LC0") [flags 0x2] <var_decl 776633c8
> *.LC0>)
> (reg:DI 1 r1))) "hello.c":5 108 {*gprel64_offset}
> (nil))
This is a diff of the RTL between two gcc-8.3.0 versions, one with PR60465
reverted and one without:
--- without-PR60465/hello.c.313r.dfinish 2019-07-05 20:37:38 +0000
+++ with-PR60465/hello.c.313r.dfinish 2019-07-05 20:26:13 +0000
@@ -31,16 +31,16 @@
(note 22 21 2 2 NOTE_INSN_PROLOGUE_END)
(note 2 22 30 2 NOTE_INSN_FUNCTION_BEG)
(insn 30 2 34 2 (set (reg:DI 120 out0 [+-4 ])
- (plus:DI (high:DI (symbol_ref/f:SI ("*.LC0") [flags 0x2] <var_decl
776633c8 *.LC0>))
- (reg:DI 1 r1))) "hello.c":5 110 {*load_symptr_high}
+ (minus:DI (symbol_ref/f:SI ("*.LC0") [flags 0x2] <var_decl 776633c8
*.LC0>)
+ (reg:DI 1 r1))) "hello.c":5 108 {*gprel64_offset}
(nil))
(insn 34 30 31 2 (unspec_volatile [
(const_int 3 [0x3])
] UNSPECV_INSN_GROUP_BARRIER) "hello.c":5 364 {insn_group_barrier}
(nil))
(insn 31 34 32 2 (set (reg:DI 120 out0 [+-4 ])
- (lo_sum:DI (mem/u/c:DI (reg:DI 120 out0 [+-4 ]) [0 S8 A64])
- (symbol_ref/f:SI ("*.LC0") [flags 0x2] <var_decl 776633c8
*.LC0>))) "hello.c":5 111 {*load_symptr_low}
+ (plus:DI (reg:DI 1 r1)
+ (reg:DI 120 out0 [+-4 ]))) "hello.c":5 206 {adddi3}
(nil))
(call_insn 32 31 33 2 (parallel [
(set (reg:SI 8 r8)
>From gcc-bugs-return-648346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 21:38:31 2019
Return-Path: <gcc-bugs-return-648346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75454 invoked by alias); 5 Jul 2019 21:38: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 75399 invoked by uid 48); 5 Jul 2019 21:38:28 -0000
From: "elowe at elowe dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 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: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: elowe at elowe 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-61577-4-zQbqMWMZT5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00458.txt.bz2
Content-length: 859
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #52 from EML <elowe at elowe dot com> ---
Note, regardless of reverting the gprel patch, GCC 8 puts the data in .rodata.
However, doesn't gcc 4.9.x do the same thing, it just moves it to GOT with
ltoffx?
.file "foo.c"
.pred.safe_across_calls p1-p5,p16-p63
.section .text, "ax", "progbits"
.Ltext0:
.section .rodata, "a", "progbits"
.align 8
.LC0:
stringz "Hellos World"
.section .text, "ax", "progbits"
Isn't LC0 here also in .rodata?
objdump -h -s fooContents of section .rodata:
40007f8 48656c6c 6f732057 6f726c64 00 Hellos World.
So gcc 4.9.x also puts the string into rodata?
(Not sure I'm reading all the files correctly, so perhaps I'm just reading it
all wrong)
>From gcc-bugs-return-648347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 21:46:52 2019
Return-Path: <gcc-bugs-return-648347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79929 invoked by alias); 5 Jul 2019 21:46: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 79892 invoked by uid 48); 5 Jul 2019 21:46:49 -0000
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 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: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: bugzilla-gcc at thewrittenword 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-61577-4-cCgAiQU3na@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00459.txt.bz2
Content-length: 2586
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #53 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to EML from comment #52)
> Note, regardless of reverting the gprel patch, GCC 8 puts the data in
> .rodata.
>
> However, doesn't gcc 4.9.x do the same thing, it just moves it to GOT with
> ltoffx?
>
> .file "foo.c"
> .pred.safe_across_calls p1-p5,p16-p63
> .section .text, "ax", "progbits"
> .Ltext0:
> .section .rodata, "a", "progbits"
> .align 8
> .LC0:
> stringz "Hellos World"
> .section .text, "ax", "progbits"
>
>
> Isn't LC0 here also in .rodata?
>
> objdump -h -s fooContents of section .rodata:
> 40007f8 48656c6c 6f732057 6f726c64 00 Hellos World.
>
>
> So gcc 4.9.x also puts the string into rodata?
>
> (Not sure I'm reading all the files correctly, so perhaps I'm just reading
> it all wrong)
gcc-4.4.6 does:
.file "hello.c"
.pred.safe_across_calls p1-p5,p16-p63
.section .rodata, "a", "progbits"
.align 8
.LC0:
stringz "Hellos World"
.section .text, "ax", "progbits"
.align 16
gcc-4.6.4 does:
.file "hello.c"
.pred.safe_across_calls p1-p5,p16-p63
.section .rodata, "a", "progbits"
.align 8
.LC0:
stringz "Hellos World"
.section .text, "ax", "progbits"
.align 16
gcc-4.7.4 does:
.pred.safe_across_calls p1-p5,p16-p63
.section .rodata, "a", "progbits"
.align 8
.LC0:
stringz "Hellos World"
.section .text, "ax", "progbits"
.align 16
gcc-4.8.5 does:
.pred.safe_across_calls p1-p5,p16-p63
.section .rodata, "a", "progbits"
.align 8
.LC0:
stringz "Hellos World"
.section .text, "ax", "progbits"
.align 16
gcc-4.9.4 (with gprel patch reverted) does:
.file "hello.c"
.pred.safe_across_calls p1-p5,p16-p63
.section .rodata, "a", "progbits"
.align 8
.LC0:
stringz "Hellos World"
.section .text, "ax", "progbits"
.align 16
gcc-8.3.0 (first stage) does:
.section .text, "ax", "progbits"
.section .rodata, "a", "progbits"
.align 8
.LC0:
stringz "Hellos World"
.section .text, "ax", "progbits"
.align 16
>From gcc-bugs-return-648348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 21:56:01 2019
Return-Path: <gcc-bugs-return-648348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92047 invoked by alias); 5 Jul 2019 21:56: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 91982 invoked by uid 48); 5 Jul 2019 21:55:58 -0000
From: "bugzilla-gcc at thewrittenword dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 21: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: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: bugzilla-gcc at thewrittenword 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-61577-4-j5eLMh5Fp7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00460.txt.bz2
Content-length: 1316
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #54 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to EML from comment #52)
> objdump -h -s foo
> Contents of section .rodata:
> 40007f8 48656c6c 6f732057 6f726c64 00 Hellos World.
>
>
> So gcc 4.9.x also puts the string into rodata?
>
> (Not sure I'm reading all the files correctly, so perhaps I'm just reading
> it all wrong)
I'm seeing the string in .rodata as well regardless of compiler version:
$ gobjdump -h -s -j .rodata a.out
a.out: file format elf32-ia64-hpux-big
Sections:
Idx Name Size VMA LMA File off Algn
10 .rodata 0000000d 040007c8 040007c8 000007c8 2**3
CONTENTS, ALLOC, LOAD, READONLY, DATA
Contents of section .rodata:
40007c8 48656c6c 6f732057 6f726c64 00 Hellos World.
And the HP C compiler has it in .rodata as well:
$ cc a.out
$ gobjdump -h -s -j .rodata a.out
a.out: file format elf32-ia64-hpux-big
Sections:
Idx Name Size VMA LMA File off Algn
11 .rodata 0000000e 040007c0 040007c0 000007c0 2**4
CONTENTS, ALLOC, LOAD, READONLY, DATA
Contents of section .rodata:
40007c0 48656c6c 6f732057 6f726c64 0a00 Hellos World..
>From gcc-bugs-return-648349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 22:18:54 2019
Return-Path: <gcc-bugs-return-648349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109940 invoked by alias); 5 Jul 2019 22:18: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 109860 invoked by uid 48); 5 Jul 2019 22:18:50 -0000
From: "pthaugen at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90813] [10 regression] gfortran.dg/proc_ptr_51.f90 fails (SIGSEGV) after 272084
Date: Fri, 05 Jul 2019 22:18: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pthaugen at linux dot ibm.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: cc
Message-ID: <bug-90813-4-TZVpSsK9FE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00461.txt.bz2
Content-length: 3652
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90813
Pat Haugen <pthaugen at linux dot ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pthaugen at linux dot ibm.com,
| |rguenth at gcc dot gnu.org
--- Comment #22 from Pat Haugen <pthaugen at linux dot ibm.com> ---
So the problem appears to be alias.c:true_dependence() telling
sched-deps.c:sched_analyze_2() that the following two instructions' memory
references don't alias.
Breakpoint 11, sched_analyze_2 (deps=0x7fffffffdbf8, x=0x7ffff59a1a40,
insn=0x7ffff57f16c0)
at /home/pthaugen/src/gcc/temp/gcc/gcc/sched-deps.c:2671
2671 if (true_dependence (pending_mem->element (), VOIDmode,
t)
(gdb) pr pending->insn()
(insn 37 36 38 4 (set (mem/f/c:DI (unspec:DI [
(symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
(reg:DI 2 2)
] UNSPEC_TOCREL) [8 c_+0 S8 A64])
(reg/f:DI 141)) "proc_ptr_51.f90":28:0 609 {*movdi_internal64}
(expr_list:REG_DEAD (reg/f:DI 141)
(nil)))
(gdb) pr insn
(insn 39 38 40 4 (set (reg/f:DI 143 [ c_ ])
(mem/f/c:DI (reg/f:DI 142) [8 c_+0 S8 A64])) "proc_ptr_51.f90":37:0 609
{*movdi_internal64}
(expr_list:REG_DEAD (reg/f:DI 142)
(expr_list:REG_EQUAL (mem/f/c:DI (symbol_ref:DI ("__f_MOD_c_") [flags
0xc0] <var_decl 0x7ffff7f70990 c_>) [8 c_+0 S8 A64])
(nil))))
Which then lets the scheduler move the load above the store. Since they really
are referring to the same location, we load up garbage (null) and branch to it.
Including some additional detail from a couple various spots in the debug
chain. Hoping someone with more alias.c knowledge can chime in.
Breakpoint 13, true_dependence_1 (mem=0x7ffff59a4878, mem_mode=E_VOIDmode,
mem_addr=0x0, x=0x7ffff59a8e08,
x_addr=0x0, mem_canonicalized=false) at
/home/pthaugen/src/gcc/temp/gcc/gcc/alias.c:2902
2902 {
(gdb) pr mem
(mem/f/c:DI (unspec:DI [
(symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
(reg:DI 2 2)
] UNSPEC_TOCREL) [8 c_+0 S8 A64])
(gdb) pr x
(mem/f/c:DI (symbol_ref:DI ("__f_MOD_c_") [flags 0xc0] <var_decl 0x7ffff7f70990
c_>) [8 c_+0 S8 A64])
...
(gdb) pr x_addr
(symbol_ref:DI ("__f_MOD_c_") [flags 0xc0] <var_decl 0x7ffff7f70990 c_>)
(gdb) pr true_mem_addr
(unspec:DI [
(symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
(reg:DI 2 2)
] UNSPEC_TOCREL)
(gdb) pr mem_base
(symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
2958 if (! base_alias_check (x_addr, base, true_mem_addr, mem_base,
(gdb) p base_alias_check (x_addr, base, true_mem_addr, mem_base, GET_MODE (x),
mem_mode)
$18 = 0
(gdb) s
base_alias_check (x=0x7ffff5992990, x_base=0x7ffff5992990, y=0x7ffff59a4890,
y_base=0x7ffff5990ac8,
x_mode=E_DImode, y_mode=E_DImode) at
/home/pthaugen/src/gcc/temp/gcc/gcc/alias.c:2174
2174 if (x_base == 0)
(gdb) pr x
(symbol_ref:DI ("__f_MOD_c_") [flags 0xc0] <var_decl 0x7ffff7f70990 c_>)
(gdb) pr x_base
(symbol_ref:DI ("__f_MOD_c_") [flags 0xc0] <var_decl 0x7ffff7f70990 c_>)
(gdb) pr y
(unspec:DI [
(symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
(reg:DI 2 2)
] UNSPEC_TOCREL)
(gdb) pr y_base
(symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
2221 return compare_base_symbol_refs (x_base, y_base) != 0;
(gdb) p compare_base_symbol_refs (x_base, y_base)
$19 = 0
2136 if (!x_node->definition)
(gdb) n
2137 return 0;
>From gcc-bugs-return-648350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 05 23:57:05 2019
Return-Path: <gcc-bugs-return-648350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39970 invoked by alias); 5 Jul 2019 23:57: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 39906 invoked by uid 48); 5 Jul 2019 23:57:01 -0000
From: "elowe at elowe dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Fri, 05 Jul 2019 23:57: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.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: elowe at elowe 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-61577-4-4YTODRAwnh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00462.txt.bz2
Content-length: 1022
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #55 from EML <elowe at elowe dot com> ---
Doing some more testing on my "gprel unfixed fix" 32-bit gcc, I found out that
it seems to be missing the 32-bit pointer swizzling needed to make 32bit
executables on 64-bit IA-64. The test program assembler is missing an addp4
instruction - when I add in this instruction, my second test program also
works.
This is defined as "ptr_extend" in the ia64.md. I don't know what it doesn't
seeem to be there, but it is definitely missing.
So I thought I would try to make a 64-bit GCC and then compile everything
64-bit just to see if that would work, since it doesn't need swizzling. This
still has the "gprel unfixed fix" though.
So far it has made it past all the conftest in the c++ library configure (so
already much further) and it has compiled libstdc++. There were, unfortunately,
some linker problems with "duplicate symbols" which seem to have been fatal.
However, this is much closer now on 64-bit
>From gcc-bugs-return-648351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 04:43:02 2019
Return-Path: <gcc-bugs-return-648351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6646 invoked by alias); 6 Jul 2019 04:43: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 6598 invoked by uid 48); 6 Jul 2019 04:42:59 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/86418] warn about mismatch in type between argument and parameter type for declaration without prototype
Date: Sat, 06 Jul 2019 04: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: 9.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:
Message-ID: <bug-86418-4-B5e71g7LPw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86418-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86418-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00463.txt.bz2
Content-length: 539
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86418
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #4)
> Confirmed. My preference would be to resolve pr82922 and diagnose all calls
> to functions without a prototype.
Agreed.
> Short of that, this could be handled by saving the type of the first call to a
> function without a prototype in a translation unit, comparing it to the type of
> each subsequent call, and warning if they don't match.
What about with LTO?
>From gcc-bugs-return-648352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 04:45:32 2019
Return-Path: <gcc-bugs-return-648352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8941 invoked by alias); 6 Jul 2019 04:45: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 8882 invoked by uid 48); 6 Jul 2019 04:45:28 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/82922] Request: add -Wstrict-prototypes to -Wextra as K&R style is obsolescent
Date: Sat, 06 Jul 2019 04: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: diagnostic, patch
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-82922-4-EmJMuAeaR4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82922-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82922-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00464.txt.bz2
Content-length: 643
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82922
--- Comment #8 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #7)
> I posted a GCC 9 patch here:
> https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00675.html
>
> It adds -Wstrict-prototypes to -Wall. Unfortunately, it got derailed by
> (IMO unsubstantiated) concerns about the impact on some poorly written
> configure tests. I'll see if I can find the time to adjust the patch to
> enable the option only with -Wextra and convince the powers that be to
> accept it into GCC 9.
OK, timeframe for GCC 9 has passed; what about for GCC 10?
>From gcc-bugs-return-648353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 04:47:59 2019
Return-Path: <gcc-bugs-return-648353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13372 invoked by alias); 6 Jul 2019 04:47: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 13353 invoked by uid 48); 6 Jul 2019 04:47:55 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/90581] provide an option to adjust the maximum depth of nested #include
Date: Sat, 06 Jul 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: preprocessor
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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-90581-4-diDdOgu0FN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90581-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90581-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00465.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90581
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |egallager at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to qinzhao from comment #4)
> the patch has been committed into upstream as today.
So... FIXED then.
>From gcc-bugs-return-648354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 07:51:18 2019
Return-Path: <gcc-bugs-return-648354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54613 invoked by alias); 6 Jul 2019 07:51: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 54582 invoked by uid 55); 6 Jul 2019 07:51:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91096] Openmp vector max reduction incorrect
Date: Sat, 06 Jul 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:
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-91096-4-5MwaYdwMn7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91096-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91096-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00466.txt.bz2
Content-length: 683
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91096
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sat Jul 6 07:50:44 2019
New Revision: 273156
URL: https://gcc.gnu.org/viewcvs?rev=273156&root=gcc&view=rev
Log:
PR tree-optimization/91096
* gcc.dg/vect/vect-simd-10.c (FLT_MIN_VALUE): Define.
(bar, main): Use it instead of -__builtin_inff ().
* gcc.dg/vect/vect-simd-14.c (FLT_MIN_VALUE): Define.
(bar, main): Use it instead of -__builtin_inff ().
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/vect/vect-simd-10.c
trunk/gcc/testsuite/gcc.dg/vect/vect-simd-14.c
>From gcc-bugs-return-648355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 07:59:29 2019
Return-Path: <gcc-bugs-return-648355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62021 invoked by alias); 6 Jul 2019 07:59: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 61988 invoked by uid 48); 6 Jul 2019 07:59:26 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/90581] provide an option to adjust the maximum depth of nested #include
Date: Sat, 06 Jul 2019 07:59: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
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: qinzhao at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-90581-4-jJX9MRza3Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90581-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90581-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00467.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90581
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-648356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 08:21:30 2019
Return-Path: <gcc-bugs-return-648356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105032 invoked by alias); 6 Jul 2019 08: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 104997 invoked by uid 48); 6 Jul 2019 08:21:27 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85746] Premature evaluation of __builtin_constant_p?
Date: Sat, 06 Jul 2019 08: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: 9.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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-85746-4-lQn0jQUffA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00468.txt.bz2
Content-length: 266
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85746
--- Comment #4 from Marc Glisse <glisse at gcc dot gnu.org> ---
Created attachment 46566
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46566&action=edit
untested patch to fold _bcp only when necessary
>From gcc-bugs-return-648357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 10:05:02 2019
Return-Path: <gcc-bugs-return-648357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14645 invoked by alias); 6 Jul 2019 10:05: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 14563 invoked by uid 48); 6 Jul 2019 10:04:59 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/78685] -Og generates too many "<optimized out>"s
Date: Sat, 06 Jul 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: debug
X-Bugzilla-Version: 6.2.1
X-Bugzilla-Keywords:
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_file_loc
Message-ID: <bug-78685-4-PsG6HMuwbm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78685-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78685-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00469.txt.bz2
Content-length: 941
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78685
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |https://gcc.gnu.org/ml/gcc-
| |patches/2019-06/msg01394.ht
| |ml
--- Comment #18 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #17)
> Richard Sandiford had a series of patches radically overhauling how -Og
> works in general that might affect this bug:
> https://gcc.gnu.org/ml/gcc-patches/2019-06/msg01392.html
> cc-ing him so he can comment on if it does in fact affect this bug.
Yeah, part 2 of the series fixes this PR:
https://gcc.gnu.org/ml/gcc-patches/2019-06/msg01394.html
>From gcc-bugs-return-648358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 10:41:08 2019
Return-Path: <gcc-bugs-return-648358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60938 invoked by alias); 6 Jul 2019 10:41: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 60865 invoked by uid 55); 6 Jul 2019 10:41:04 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90813] [10 regression] gfortran.dg/proc_ptr_51.f90 fails (SIGSEGV) after 272084
Date: Sat, 06 Jul 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: rtl-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: 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-90813-4-E81dDP9FCT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00470.txt.bz2
Content-length: 4099
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90813
--- Comment #23 from rguenther at suse dot de <rguenther at suse dot de> ---
On July 6, 2019 12:18:47 AM GMT+02:00, "pthaugen at linux dot ibm.com"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90813
>
>Pat Haugen <pthaugen at linux dot ibm.com> changed:
>
> What |Removed |Added
>----------------------------------------------------------------------------
> CC| |pthaugen at linux dot ibm.com,
> | |rguenth at gcc dot gnu.org
>
>--- Comment #22 from Pat Haugen <pthaugen at linux dot ibm.com> ---
>So the problem appears to be alias.c:true_dependence() telling
>sched-deps.c:sched_analyze_2() that the following two instructions'
>memory
>references don't alias.
>
>Breakpoint 11, sched_analyze_2 (deps=0x7fffffffdbf8, x=0x7ffff59a1a40,
>insn=0x7ffff57f16c0)
> at /home/pthaugen/src/gcc/temp/gcc/gcc/sched-deps.c:2671
>2671 if (true_dependence (pending_mem->element (),
>VOIDmode,
>t)
>(gdb) pr pending->insn()
>(insn 37 36 38 4 (set (mem/f/c:DI (unspec:DI [
> (symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
> (reg:DI 2 2)
> ] UNSPEC_TOCREL) [8 c_+0 S8 A64])
> (reg/f:DI 141)) "proc_ptr_51.f90":28:0 609 {*movdi_internal64}
> (expr_list:REG_DEAD (reg/f:DI 141)
> (nil)))
>
>(gdb) pr insn
>(insn 39 38 40 4 (set (reg/f:DI 143 [ c_ ])
>(mem/f/c:DI (reg/f:DI 142) [8 c_+0 S8 A64])) "proc_ptr_51.f90":37:0 609
>{*movdi_internal64}
> (expr_list:REG_DEAD (reg/f:DI 142)
> (expr_list:REG_EQUAL (mem/f/c:DI (symbol_ref:DI ("__f_MOD_c_") [flags
>0xc0] <var_decl 0x7ffff7f70990 c_>) [8 c_+0 S8 A64])
> (nil))))
>
>Which then lets the scheduler move the load above the store. Since they
>really
>are referring to the same location, we load up garbage (null) and
>branch to it.
>
>Including some additional detail from a couple various spots in the
>debug
>chain. Hoping someone with more alias.c knowledge can chime in.
>
>
>Breakpoint 13, true_dependence_1 (mem=0x7ffff59a4878,
>mem_mode=E_VOIDmode,
>mem_addr=0x0, x=0x7ffff59a8e08,
> x_addr=0x0, mem_canonicalized=false) at
>/home/pthaugen/src/gcc/temp/gcc/gcc/alias.c:2902
>2902 {
>(gdb) pr mem
>(mem/f/c:DI (unspec:DI [
> (symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
> (reg:DI 2 2)
> ] UNSPEC_TOCREL) [8 c_+0 S8 A64])
>(gdb) pr x
>(mem/f/c:DI (symbol_ref:DI ("__f_MOD_c_") [flags 0xc0] <var_decl
>0x7ffff7f70990
>c_>) [8 c_+0 S8 A64])
>
>...
>
>(gdb) pr x_addr
>(symbol_ref:DI ("__f_MOD_c_") [flags 0xc0] <var_decl 0x7ffff7f70990
>c_>)
>(gdb) pr true_mem_addr
>(unspec:DI [
> (symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
> (reg:DI 2 2)
> ] UNSPEC_TOCREL)
>(gdb) pr mem_base
>(symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
>
>2958 if (! base_alias_check (x_addr, base, true_mem_addr,
>mem_base,
>(gdb) p base_alias_check (x_addr, base, true_mem_addr, mem_base,
>GET_MODE (x),
>mem_mode)
>$18 = 0
>
>(gdb) s
>base_alias_check (x=0x7ffff5992990, x_base=0x7ffff5992990,
>y=0x7ffff59a4890,
>y_base=0x7ffff5990ac8,
> x_mode=E_DImode, y_mode=E_DImode) at
>/home/pthaugen/src/gcc/temp/gcc/gcc/alias.c:2174
>2174 if (x_base == 0)
>(gdb) pr x
>(symbol_ref:DI ("__f_MOD_c_") [flags 0xc0] <var_decl 0x7ffff7f70990
>c_>)
>(gdb) pr x_base
>(symbol_ref:DI ("__f_MOD_c_") [flags 0xc0] <var_decl 0x7ffff7f70990
>c_>)
>(gdb) pr y
>(unspec:DI [
> (symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
> (reg:DI 2 2)
> ] UNSPEC_TOCREL)
>(gdb) pr y_base
>(symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
>
>2221 return compare_base_symbol_refs (x_base, y_base) != 0;
>(gdb) p compare_base_symbol_refs (x_base, y_base)
>$19 = 0
>
>2136 if (!x_node->definition)
>(gdb) n
>2137 return 0;
We seem to access the same decl (see MEM_EXPR) once via section anchor and once
not. We seem to be confused about this in this very place?
>From gcc-bugs-return-648359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 13:15:59 2019
Return-Path: <gcc-bugs-return-648359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93987 invoked by alias); 6 Jul 2019 13:15: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 93935 invoked by uid 55); 6 Jul 2019 13:15:55 -0000
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Sat, 06 Jul 2019 13:15: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.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: dave.anglin at bell 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-61577-4-fURdpbVD6M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00471.txt.bz2
Content-length: 863
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #56 from dave.anglin at bell dot net ---
On 2019-07-05 7:57 p.m., elowe at elowe dot com wrote:
> Doing some more testing on my "gprel unfixed fix" 32-bit gcc, I found out that
> it seems to be missing the 32-bit pointer swizzling needed to make 32bit
> executables on 64-bit IA-64. The test program assembler is missing an addp4
> instruction - when I add in this instruction, my second test program also
> works.
Could be. The default hpux compiler generates ILP32 code and it's supposed to
be big-endian.
Could you compile hello world with "-c" option and run "objdump -r" on
resulting object?
Pointers are 32-bit in the ILP32 model. I think we should have GPREL32MSB
relocation but
maybe we have 64-bit reloc.
https://refspecs.linuxfoundation.org/elf/IA64-SysV-psABI.pdf
>From gcc-bugs-return-648360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 14:19:32 2019
Return-Path: <gcc-bugs-return-648360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66442 invoked by alias); 6 Jul 2019 14:19: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 66349 invoked by uid 48); 6 Jul 2019 14:19:25 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90813] [10 regression] gfortran.dg/proc_ptr_51.f90 fails (SIGSEGV) after 272084
Date: Sat, 06 Jul 2019 14: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher 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-90813-4-s4kvQLwm02@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00472.txt.bz2
Content-length: 208
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90813
--- Comment #24 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Is that disallowed? Is there any way to prevent that from happening, in
general?
>From gcc-bugs-return-648361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 14:20:35 2019
Return-Path: <gcc-bugs-return-648361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72563 invoked by alias); 6 Jul 2019 14:20: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 72519 invoked by uid 48); 6 Jul 2019 14:20:31 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91098] [10 Regression] internal compiler error: tree check: expected var_decl or field_decl or function_decl or type_decl or template_decl, have using_decl in build_deduction_guide, at cp/pt.c:27167
Date: Sat, 06 Jul 2019 14: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: 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 target_milestone everconfirmed
Message-ID: <bug-91098-4-tbc6YaMwag@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91098-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91098-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00473.txt.bz2
Content-length: 626
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91098
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-06
CC| |mpolacek at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r270765.
>From gcc-bugs-return-648362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 14:36:19 2019
Return-Path: <gcc-bugs-return-648362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88480 invoked by alias); 6 Jul 2019 14:36: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 88391 invoked by uid 48); 6 Jul 2019 14:36:15 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90813] [10 regression] gfortran.dg/proc_ptr_51.f90 fails (SIGSEGV) after 272084
Date: Sat, 06 Jul 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: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher 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-90813-4-d02b3kz9TT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00474.txt.bz2
Content-length: 3217
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90813
--- Comment #25 from Segher Boessenkool <segher at gcc dot gnu.org> ---
At expand time, the assignment is
;; c_ = c;
(insn 35 34 36 (set (reg/f:DI 140)
(unspec:DI [
(symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
(reg:DI 2 2)
] UNSPEC_TOCREL)) "proc_ptr_51.f90":26:0 -1
(expr_list:REG_EQUAL (symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
(nil)))
(insn 36 35 37 (set (reg/f:DI 141)
(unspec:DI [
(symbol_ref:DI ("__f_MOD_c") [flags 0x3] <function_decl
0x3fff7
86a7d00 c>)
(reg:DI 2 2)
] UNSPEC_TOCREL)) "proc_ptr_51.f90":26:0 -1
(expr_list:REG_EQUAL (symbol_ref:DI ("__f_MOD_c") [flags 0x3]
<function_de
cl 0x3fff786a7d00 c>)
(nil)))
(insn 37 36 0 (set (mem/f/c:DI (reg/f:DI 140) [13 c_+0 S8 A64])
(reg/f:DI 141)) "proc_ptr_51.f90":26:0 -1
(nil))
while the use is (immediately after that!)
;; rhs.2 = c_.5_12 (); [return slot optimization]
(insn 38 37 39 (set (reg:DI 142)
(plus:DI (reg/f:DI 112 virtual-stack-vars)
(const_int 48 [0x30]))) "proc_ptr_51.f90":35:0 -1
(nil))
(insn 39 38 40 (set (reg/f:DI 143)
(mem/u/c:DI (unspec:DI [
(symbol_ref/u:DI ("*.LC1") [flags 0x2])
(reg:DI 2 2)
] UNSPEC_TOCREL) [21 S8 A8])) "proc_ptr_51.f90":35:0 -1
(expr_list:REG_EQUAL (symbol_ref:DI ("__f_MOD_c_") [flags 0xc0] <var_decl
0x3fff7aa40990 c_>)
(nil)))
(insn 40 39 41 (set (reg/f:DI 144)
(mem/f/c:DI (reg/f:DI 143) [13 c_+0 S8 A64])) "proc_ptr_51.f90":35:0 -1
(nil))
(insn 41 40 42 (set (reg:DI 3 3)
(reg:DI 142)) "proc_ptr_51.f90":35:0 -1
(nil))
(insn 42 41 43 (set (reg:DI 145)
(mem:DI (reg/f:DI 144) [0 S8 A8])) "proc_ptr_51.f90":35:0 -1
(nil))
(insn 43 42 44 (set (reg:DI 97 ctr)
(reg:DI 145)) "proc_ptr_51.f90":35:0 -1
(nil))
(insn 44 43 45 (set (reg:DI 11 11)
(mem:DI (plus:DI (reg/f:DI 144)
(const_int 16 [0x10])) [0 S8 A8])) "proc_ptr_51.f90":35:0 -1
(nil))
(call_insn 45 44 46 (parallel [
(call (mem:SI (reg:DI 97 ctr) [0 *c_.5_12 S4 A8])
(const_int 64 [0x40]))
(use (mem:DI (plus:DI (reg/f:DI 144)
(const_int 8 [0x8])) [0 S8 A8]))
(set (reg:DI 2 2)
(unspec:DI [
(const_int 40 [0x28])
] UNSPEC_TOCSLOT))
(clobber (reg:DI 96 lr))
]) "proc_ptr_51.f90":35:0 -1
(expr_list:REG_CALL_DECL (nil)
(nil))
(expr_list (use (reg:DI 11 11))
(expr_list:DI (use (reg:DI 3 3))
(nil))))
(insn 46 45 47 (set (reg:DI 146)
(plus:DI (reg/f:DI 112 virtual-stack-vars)
(const_int 48 [0x30]))) "proc_ptr_51.f90":35:0 -1
(nil))
(insn 47 46 0 (set (reg:TI 127 [ rhs.2 ])
(mem:TI (reg:DI 146) [7 S16 A64])) "proc_ptr_51.f90":35:0 -1
(nil))
so it is wrong (if this is wrong!) at expand already.
In gimple this was:
c_ = c;
c_.5_12 = c_;
rhs.2 = c_.5_12 (); [return slot optimization]
>From gcc-bugs-return-648363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 15:00:56 2019
Return-Path: <gcc-bugs-return-648363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11807 invoked by alias); 6 Jul 2019 15: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 11753 invoked by uid 48); 6 Jul 2019 15:00:52 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67017] [DR1265] Mixing init-declarator for variables and functions in declaration with auto type-specifier
Date: Sat, 06 Jul 2019 15: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: unknown
X-Bugzilla-Keywords: accepts-invalid
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-67017-4-GtIvbFIF48@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67017-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67017-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00475.txt.bz2
Content-length: 520
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67017
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |mpolacek at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #7 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Resolved in r244071.
>From gcc-bugs-return-648364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 15:41:31 2019
Return-Path: <gcc-bugs-return-648364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47417 invoked by alias); 6 Jul 2019 15:41: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 47392 invoked by uid 48); 6 Jul 2019 15:41:28 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56248] [DR 580] access checking of template parameters done too early
Date: Sat, 06 Jul 2019 15: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: 4.8.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: 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-56248-4-sBoC7IzCBy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56248-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56248-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00476.txt.bz2
Content-length: 481
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56248
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-06
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-648365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 16:26:01 2019
Return-Path: <gcc-bugs-return-648365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5729 invoked by alias); 6 Jul 2019 16:25: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 5700 invoked by uid 48); 6 Jul 2019 16:25:56 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91090] A suspicious code in tree-ssa-dom.c
Date: Sat, 06 Jul 2019 16: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc assigned_to
Message-ID: <bug-91090-4-Fda0nlh0PP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91090-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91090-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00477.txt.bz2
Content-length: 625
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91090
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
Assignee|unassigned at gcc dot gnu.org |law at redhat dot com
--- Comment #2 from Jeffrey A. Law <law at redhat dot com> ---
I think that if (i > j) case should be at the same level as the (i == j) case.
It probably got goof'd up during reindention when the code was copied from
tree-vrp.c.
>From gcc-bugs-return-648366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 16:56:47 2019
Return-Path: <gcc-bugs-return-648366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110138 invoked by alias); 6 Jul 2019 16: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 110087 invoked by uid 48); 6 Jul 2019 16:56:44 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91099] New: constexpr vs -frounding-math
Date: Sat, 06 Jul 2019 16: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:
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-91099-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00478.txt.bz2
Content-length: 1845
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91099
Bug ID: 91099
Summary: constexpr vs -frounding-math
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: glisse at gcc dot gnu.org
Target Milestone: ---
constexpr double d = 1. / 3.;
currently fails to compile with -frounding-math. This behavior makes sense: we
do not know in what direction to round. However, -frounding-math is about the
dynamic rounding mode, while the above expression must be evaluated at compile
time, where there is no dynamic rounding mode (pragma fenv_round from C2a may
eventually provide a way to specify a relevant rounding mode). An alternative
to refusing to perform any inexact math at compile time would be, when the
computation is absolutely required to be performed at compile time, to use the
default rounding mode.
I tried adding:
Save<int> save_frm(flag_rounding_math, flag_rounding_math &
!ctx->manifestly_const_eval);
near the beginning of cxx_eval_constant_expression, where Save is
template<class T> struct Save {
T& ref; T old;
Save(T& t, T newval): ref(t), old(t) { ref = newval; }
~Save() { ref = old; }
};
which kind of works on trivial examples, but is defeated by constexpr-caching
if we change flag_rounding_math in the middle of a translation unit: if we have
previously (-fno-rounding-math) managed to fold a function computing 1./3, we
blindly reuse the result even if we now have -frounding-math. I don't know if
it would be acceptable to say that -frounding-math may not be changed in the
middle of a translation unit. (for pragma fenv_access, I currently think I
should use a different flag)
>From gcc-bugs-return-648367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 17:22:11 2019
Return-Path: <gcc-bugs-return-648367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129677 invoked by alias); 6 Jul 2019 17: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 129619 invoked by uid 48); 6 Jul 2019 17:22:08 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Sat, 06 Jul 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: 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: cc see_also
Message-ID: <bug-91092-4-yPqVtIUVRb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00479.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=89072
--- Comment #10 from Martin Sebor <msebor at gcc dot gnu.org> ---
See also pr89072 for a request to enable -Wall -Werror by default.
>From gcc-bugs-return-648368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 17:23:50 2019
Return-Path: <gcc-bugs-return-648368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130845 invoked by alias); 6 Jul 2019 17:23: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 130760 invoked by uid 48); 6 Jul 2019 17:23:46 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91093] Error on implicit int by default
Date: Sat, 06 Jul 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: c
X-Bugzilla-Version: unknown
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: cc see_also
Message-ID: <bug-91093-4-4JR9dETdB3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91093-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91093-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00480.txt.bz2
Content-length: 750
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91093
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=91092,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=89072
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
See also pr89072 for a request to enable -Wall -Werror by default.
>From gcc-bugs-return-648369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 18:11:25 2019
Return-Path: <gcc-bugs-return-648369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43689 invoked by alias); 6 Jul 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 43648 invoked by uid 48); 6 Jul 2019 18:11:21 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/89072] -Wall -Werror should be defaults
Date: Sat, 06 Jul 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: 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-89072-4-yHQtkfTPdS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89072-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89072-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00481.txt.bz2
Content-length: 1504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89072
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |segher at gcc dot gnu.org
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
-Werror should *never* be the default. Warnings are warnings, and errors
are errors. Warnings are for situations where the compiler cannot tell
whether what you did is wrong, and errors are for when it *can* tell
unambiguously that your program is incorrect.
Many warnings are *wrong*. That is in the nature of warnings. Refusing
to build a correct program is a disservice.
Warnings change frequently, with every release of GCC. On the other hand,
errors do not change (ignoring compiler bugs): incorrect programs stay
incorrect, and if we failed to diagnose an incorrect program before, that
does not change the fact that it was incorrect.
Making -Wall the default will potentially break the build of very many
projects, *especially* those that misguidedly use -Werror. I don't see
any less painful path to enabling -Wall by default. I don't really see
the point: there are other gcc command line mistakes that are made more
often, certainly by beginners (like forgetting -Wextra, or putting -l's
before the object files, or or or).
Beginners are better off not invoking the compiler driver directly.
>From gcc-bugs-return-648370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 18:53:17 2019
Return-Path: <gcc-bugs-return-648370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127448 invoked by alias); 6 Jul 2019 18:53: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 127413 invoked by uid 48); 6 Jul 2019 18:53:13 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/91100] New: [9,10 Regression] FAIL: gnat.dg/socket1.adb execution test
Date: Sat, 06 Jul 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: ada
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin 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_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-91100-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00482.txt.bz2
Content-length: 2458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91100
Bug ID: 91100
Summary: [9,10 Regression] FAIL: gnat.dg/socket1.adb execution
test
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
Assignee: unassigned at gcc dot gnu.org
Reporter: danglin at gcc dot gnu.org
Target Milestone: ---
Host: hppa2.0w-hp-hpux11.11
Target: hppa2.0w-hp-hpux11.11
Build: hppa64-hp-hpux11.11
ADA_INCLUDE_PATH=/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libada/adainclude
ADA_OBJECTS_PATH=/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libada/adainclude
Executing on host: /test/gnu/gcc/objdir/gcc/gnatmake
--GCC=/test/gnu/gcc/objdir/
gcc/xgcc --GNATBIND=/test/gnu/gcc/objdir/gcc/gnatbind
--GNATLINK=/test/gnu/gcc/o
bjdir/gcc/gnatlink -cargs -B/test/gnu/gcc/objdir/gcc -largs
--GCC=/test/gnu/gcc/objdir/gcc/xgcc\ -B/test/gnu/gcc/objdir/gcc\ -margs
--RTS=/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libada -q -f
/test/gnu/gcc/gcc/gcc/testsuite/gnat.dg/socket1.adb
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -lm -o ./socket1.exe (timeout = 300)
spawn /test/gnu/gcc/objdir/gcc/gnatmake --GCC=/test/gnu/gcc/objdir/gcc/xgcc
--GNATBIND=/test/gnu/gcc/objdir/gcc/gnatbind
--GNATLINK=/test/gnu/gcc/objdir/gcc/gnatlink -cargs -B/test/gnu/gcc/objdir/gcc
-largs --GCC=/test/gnu/gcc/objdir/gcc/xgcc -B/test/gnu/gcc/objdir/gcc -margs
--RTS=/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libada -q -f
/test/gnu/gcc/gcc/gcc/testsuite/gnat.dg/socket1.adb -fno-diagnostics-show-caret
-fno-diagnostics-show-line-numbers -fdiagnostics-color=never -lm -o
./socket1.exe
Executing on host: /test/gnu/gcc/objdir/gcc/gnatclean -c -q -n ./socket1
(timeout = 300)
spawn /test/gnu/gcc/objdir/gcc/gnatclean -c -q -n ./socket1
./socket1.ali
./socket1.o
PASS: gnat.dg/socket1.adb (test for excess errors)
Setting LD_LIBRARY_PATH to :/test/gnu/gcc/objdir/gcc::/test/gnu/gcc/objdir/gcc
spawn [open ...]
raised GNAT.SOCKETS.SOCKET_ERROR : [0] Error 0
FAIL: gnat.dg/socket1.adb execution test
Revision 272748 was okay with gcc-10. Fail seen with revision 273142.
Revision 272827 was okay with gcc-9. Fail seen with revision 272908.
Not sure how to debug (i.e., keep testsuite executable).
>From gcc-bugs-return-648371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 19:39:22 2019
Return-Path: <gcc-bugs-return-648371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22257 invoked by alias); 6 Jul 2019 19:39: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 22175 invoked by uid 48); 6 Jul 2019 19:39:19 -0000
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/84877] Local stack copy of BLKmode parameter on the stack is not aligned when the requested alignment exceeds MAX_SUPPORTED_STACK_ALIGNMENT
Date: Sat, 06 Jul 2019 19: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amylaar at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-84877-4-Wy6dUcxDtD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00483.txt.bz2
Content-length: 1525
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84877
Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amylaar at gcc dot gnu.org
--- Comment #10 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> ---
Created attachment 46567
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46567&action=edit
Fix for targets that pass the argument by invisible reference
I also observe this problem on esirisc.
assign_parm is only relevant for the testcase if the argument is passed by
value, where the copy is made in foo.
If the argument is passed by invisible reference, we have instead during
compilation of main expand_call calling initialize_argument_information, which
calls assign_temp, which calls assign_temp_for_type, which calls
assign_stack_local_1 .
The attached patch changes initialize_argument_information to use the same
code path as for variable-sized arguments; it's a bit more overhead, but I
would
think that excess alignment is a relatively rare case. If performance for this
alignment were really important, you could change the stack management so that
the alignment can be provided more cheaply.
Since the esirisc port is not in the FSF tree, it doesn't really count for
testing; also, the behaviour will vary depending on argument passing of the
target, so we need to test a variety of targets.
>From gcc-bugs-return-648372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 19:44:50 2019
Return-Path: <gcc-bugs-return-648372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7616 invoked by alias); 6 Jul 2019 19:44: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 7540 invoked by uid 48); 6 Jul 2019 19:44:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91096] Openmp vector max reduction incorrect
Date: Sat, 06 Jul 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: 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: 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 target_milestone
Message-ID: <bug-91096-4-yu5tgUmjTU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91096-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91096-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00484.txt.bz2
Content-length: 574
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91096
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Target Milestone|--- |10.0
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Should be fixed now.
>From gcc-bugs-return-648373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 20:07:48 2019
Return-Path: <gcc-bugs-return-648373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33493 invoked by alias); 6 Jul 2019 20:07: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 33400 invoked by uid 48); 6 Jul 2019 20:07:41 -0000
From: "frantisek at sumsal dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] New: Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Sat, 06 Jul 2019 20:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frantisek at sumsal 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00485.txt.bz2
Content-length: 14949
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
Bug ID: 91101
Summary: Possible performance regression in libasan with
detect_stack_use_after_return=1
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: frantisek at sumsal dot cz
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
Target Milestone: ---
Hello,
in systemd we recently noticed[0], that certain CI's started timeouting after
upgrade to gcc 9.1.0 and 9.1.1. After a bit of investigation it seems that the
runtime of instrumented binaries with ASan is more than doubled. (The GitHub
thread contains claims about the performance issue being present even without
sanitizers, but that hasn't been confirmed yet, so please ignore it).
Also, I apologize if this report is useless for upstream, since it's not using
the trunk GCC, but I'd really like to know if we're doing something
fundamentally wrong or if this is an actual issue. The following report is from
Arch Linux with GCC 9.1.0, but I also managed to reproduce this on Fedora
Rawhide with GCC 9.1.1[1]. As this thread is without any response so far, I've
been trying to collect as much information as possible regarding this issue, as
testing systemd with bleeding-edge software is particularly important for us.
The following statistics provide comparison between two particular systemd test
cases compiled with GCC 8.3.0 (with and without ASan and UBSan) and the same
statistics for GCC 9.1.0:
----
[vagrant@arch build]$ pacman -Q gcc gcc-libs
gcc 8.3.0-1
gcc-libs 8.3.0-1
[vagrant@arch build]$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared
--enable-threads=posix --enable-libmpx --with-system-zlib --with-isl
--enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu
--disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object
--enable-linker-build-id --enable-lto --enable-plugin
--enable-install-libiberty --with-linker-hash-style=gnu
--enable-gnu-indirect-function --enable-multilib --disable-werror
--enable-checking=release --enable-default-pie --enable-default-ssp
--enable-cet=auto
Thread model: posix
gcc version 8.3.0 (GCC)
# Basically git clone https://github.com/systemd/systemd /build
[vagrant@arch build]$ meson build-gcc-8.3.0-sanitizers
-Db_sanitize=address,undefined
<...snip...>
[vagrant@arch build]$ meson build-gcc-8.3.0
<...snip...>
[vagrant@arch build]$ ninja -C build-gcc-8.3.0-sanitizers
<...snip...>
[vagrant@arch build]$ ninja -C build-gcc-8.3.0
<...snip...>
# Sanitizer-specific options
[vagrant@arch build]$ export
ASAN_OPTIONS=strict_string_checks=1:detect_stack_use_after_return=1:check_initialization_order=1:strict_init_order=1
[vagrant@arch build]$ export
UBSAN_OPTIONS=print_stacktrace=1:print_summary=1:halt_on_error=1
# WITHOUT sanitizers
[vagrant@arch build]$ /bin/time -v build-gcc-8.3.0/test-conf-parser >/dev/null
<...snip...>
Command being timed: "build-gcc-8.3.0/test-conf-parser"
User time (seconds): 1.25
System time (seconds): 0.01
Percent of CPU this job got: 99%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:01.28
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 9944
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 0
Minor (reclaiming a frame) page faults: 930
Voluntary context switches: 12
Involuntary context switches: 107
Swaps: 0
File system inputs: 0
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
[vagrant@arch build]$ cd build-gcc-8.3.0 && /bin/time -v ../test/hwdb-test.sh
>/dev/null
Command being timed: "../test/hwdb-test.sh"
User time (seconds): 0.40
System time (seconds): 0.01
Percent of CPU this job got: 98%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.41
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 25752
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 0
Minor (reclaiming a frame) page faults: 7264
Voluntary context switches: 71
Involuntary context switches: 30
Swaps: 0
File system inputs: 0
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
# WITH sanitizers
[vagrant@arch build]$ /bin/time -v build-gcc-8.3.0-sanitizers/test-conf-parser
>/dev/null
<...snip...>
Command being timed: "build-gcc-8.3.0-sanitizers/test-conf-parser"
User time (seconds): 3.05
System time (seconds): 0.28
Percent of CPU this job got: 92%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:03.61
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 347056
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 16
Minor (reclaiming a frame) page faults: 180270
Voluntary context switches: 85
Involuntary context switches: 395
Swaps: 0
File system inputs: 35568
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
[vagrant@arch build]$ cd build-gcc-8.3.0-sanitizers/ && /bin/time -v
../test/hwdb-test.sh >/dev/null
Command being timed: "../test/hwdb-test.sh"
User time (seconds): 40.08
System time (seconds): 31.98
Percent of CPU this job got: 99%
Elapsed (wall clock) time (h:mm:ss or m:ss): 1:12.41
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 805060
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 3
Minor (reclaiming a frame) page faults: 22857463
Voluntary context switches: 97
Involuntary context switches: 414
Swaps: 0
File system inputs: 288
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
# GCC upgrade
[vagrant@arch build]$ sudo pacman -Sy gcc gcc-libs
...
Packages (2) gcc-9.1.0-2 gcc-libs-9.1.0-2
...
[vagrant@arch build]$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/9.1.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --enable-default-pie
--enable-default-ssp --enable-cet=auto
Thread model: posix
gcc version 9.1.0 (GCC)
[vagrant@arch build]$ meson build-gcc-9.1.0-sanitizers
-Db_sanitize=address,undefined
<...snip...>
[vagrant@arch build]$ meson build-gcc-9.1.0
<...snip...>
[vagrant@arch build]$ ninja -C build-gcc-9.1.0-sanitizers
<...snip...>
[vagrant@arch build]$ ninja -C build-gcc-9.1.0
<...snip...>
# WITHOUT sanitizers
[vagrant@arch build]$ /bin/time -v build-gcc-9.1.0/test-conf-parser >/dev/null
<...snip...>
Command being timed: "build-gcc-9.1.0/test-conf-parser"
User time (seconds): 1.26
System time (seconds): 0.00
Percent of CPU this job got: 99%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:01.28
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 10016
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 1
Minor (reclaiming a frame) page faults: 928
Voluntary context switches: 6
Involuntary context switches: 111
Swaps: 0
File system inputs: 96
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
[vagrant@arch build]$ cd build-gcc-9.1.0 && /bin/time -v ../test/hwdb-test.sh
>/dev/null
Command being timed: "../test/hwdb-test.sh"
User time (seconds): 0.43
System time (seconds): 0.03
Percent of CPU this job got: 95%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.49
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 25856
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 3
Minor (reclaiming a frame) page faults: 7279
Voluntary context switches: 108
Involuntary context switches: 68
Swaps: 0
File system inputs: 1144
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
# WITH sanitizers
[vagrant@arch build]$ /bin/time -v build-gcc-9.1.0-sanitizers/test-conf-parser
>/dev/null
<...snip...>
Command being timed: "build-gcc-9.1.0-sanitizers/test-conf-parser"
User time (seconds): 30.03
System time (seconds): 0.33
Percent of CPU this job got: 99%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:30.50
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 348972
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 17
Minor (reclaiming a frame) page faults: 180473
Voluntary context switches: 31
Involuntary context switches: 160
Swaps: 0
File system inputs: 5200
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
[vagrant@arch build]$ cd build-gcc-9.1.0-sanitizers/ && /bin/time -v
../test/hwdb-test.sh >/dev/null
Command being timed: "../test/hwdb-test.sh"
User time (seconds): 129.53
System time (seconds): 32.94
Percent of CPU this job got: 99%
Elapsed (wall clock) time (h:mm:ss or m:ss): 2:43.29
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 805868
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 6
Minor (reclaiming a frame) page faults: 22858160
Voluntary context switches: 118
Involuntary context switches: 1136
Swaps: 0
File system inputs: 11640
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
----
Notice the huge difference in user/wall time in the ASan+UBsan run, which is
~10 times slower with GCC 9.1.x as opposed to GCC 8.3.0.
However, by switching the `detect_stack_use_after_return` option off, the
performance issue is much less noticeable:
----
[vagrant@arch build]$ export
ASAN_OPTIONS=strict_string_checks=1:check_initialization_order=1:strict_init_order=1:detect_stack_use_after_return=0
[vagrant@arch build]$ /bin/time -v build-gcc-9.1.0-sanitizers/test-conf-parser
>/dev/null
<...snip...>
/tmp/test-conf-parser.Q8S7gi:1: Continuation line too long
Command being timed: "build-gcc-9.1.0-sanitizers/test-conf-parser"
User time (seconds): 2.61
System time (seconds): 0.23
Percent of CPU this job got: 99%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:02.87
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 347316
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 9
Minor (reclaiming a frame) page faults: 179814
Voluntary context switches: 22
Involuntary context switches: 108
Swaps: 0
File system inputs: 1160
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
[vagrant@arch build]$ cd build-gcc-9.1.0-sanitizers/ && /bin/time -v
../test/hwdb-test.sh >/dev/null
Command being timed: "../test/hwdb-test.sh"
User time (seconds): 22.71
System time (seconds): 32.06
Percent of CPU this job got: 99%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:55.11
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 802892
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 15
Minor (reclaiming a frame) page faults: 22856894
Voluntary context switches: 171
Involuntary context switches: 657
Swaps: 0
File system inputs: 25384
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
---
So far I've failed to convince meson/ninja to build systemd and leave the GCC's
temporary files intact, so I'll provide them as soon as possible.
Thank you.
[0] https://github.com/systemd/systemd/pull/12856#issuecomment-504395847
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1722949
>From gcc-bugs-return-648374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 20:23:30 2019
Return-Path: <gcc-bugs-return-648374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102079 invoked by alias); 6 Jul 2019 20:23: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 102045 invoked by uid 48); 6 Jul 2019 20:23:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91102] New: [9/10 Regression] aarch64 ICE on Linux kernel with -Os starting with r270266
Date: Sat, 06 Jul 2019 20:23: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.1.1
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-91102-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00486.txt.bz2
Content-length: 2006
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91102
Bug ID: 91102
Summary: [9/10 Regression] aarch64 ICE on Linux kernel with -Os
starting with r270266
Product: gcc
Version: 9.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
int
foo (long d, long l)
{
register long e asm ("x1") = d;
register long f asm("x2") = l;
asm ("" : : "r" (e), "r" (f));
}
struct T { int i; int j; };
union S { long h; struct T t; };
void
bar (union S b)
{
while (1)
{
union S c = b;
c.t.j++;
b.h = foo (b.h, c.h);
}
}
ICEs with -Os on aarch64-linux starting with r270266:
rh1727453.i: In function ‘bar’:
rh1727453.i:21:1: error: unable to generate reloads for:
21 | }
| ^
(insn 15 14 16 3 (set (reg/v:DI 2 x2 [ f ])
(ior:DI (and:DI (reg/v:DI 1 x1 [ e ])
(const_int 4294967295 [0xffffffff]))
(ashift:DI (subreg:DI (reg:SI 99) 0)
(const_int 32 [0x20])))) "rh1727453.i":5:17 794
{*aarch64_bfidi4_noand}
(expr_list:REG_DEAD (reg:SI 99)
(nil)))
during RTL pass: reload
rh1727453.i:21:1: internal compiler error: in curr_insn_transform, at
lra-constraints.c:3962
0xfa3363 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
../../gcc/rtl-error.c:108
0xe09d9f curr_insn_transform
../../gcc/lra-constraints.c:3962
0xe0d788 lra_constraints(bool)
../../gcc/lra-constraints.c:4978
0xdf5639 lra(_IO_FILE*)
../../gcc/lra.c:2472
0xd9d0c2 do_reload
../../gcc/ira.c:5516
0xd9d550 execute
../../gcc/ira.c:5700
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-648375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 20:33:01 2019
Return-Path: <gcc-bugs-return-648375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108837 invoked by alias); 6 Jul 2019 20:33: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 108772 invoked by uid 48); 6 Jul 2019 20:32:58 -0000
From: "frantisek at sumsal dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Sat, 06 Jul 2019 20:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frantisek at sumsal 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: attachments.created
Message-ID: <bug-91101-4-icX6vhu9Wd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00487.txt.bz2
Content-length: 255
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #1 from Frantisek Sumsal <frantisek at sumsal dot cz> ---
Created attachment 46568
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46568&action=edit
hwdb.i tempfile from GCC 9.1.0
>From gcc-bugs-return-648376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 20:33:40 2019
Return-Path: <gcc-bugs-return-648376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109821 invoked by alias); 6 Jul 2019 20: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 109748 invoked by uid 48); 6 Jul 2019 20:33:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91102] [9/10 Regression] aarch64 ICE on Linux kernel with -Os starting with r270266
Date: Sat, 06 Jul 2019 20:33: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.1.1
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: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget priority bug_status cf_reconfirmed_on cc target_milestone everconfirmed
Message-ID: <bug-91102-4-Vojl3ADs94@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00488.txt.bz2
Content-length: 3798
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91102
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |aarch64-linux
Priority|P3 |P2
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-06
CC| |segher at gcc dot gnu.org,
| |sje at gcc dot gnu.org,
| |vmakarov at gcc dot gnu.org
Target Milestone|--- |9.2
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Before combine we have:
(insn 12 11 14 3 (set (zero_extract:DI (reg/v:DI 95 [ c ])
(const_int 32 [0x20])
(const_int 32 [0x20]))
(reg:DI 100)) "rh1727453.i":18:12 782 {*insv_regdi}
(expr_list:REG_DEAD (reg:DI 100)
(nil)))
(insn 14 12 15 3 (set (reg/v:DI 1 x1 [ e ])
(reg:DI 92 [ b$h ])) "rh1727453.i":4:17 47 {*movdi_aarch64}
(expr_list:REG_DEAD (reg:DI 92 [ b$h ])
(nil)))
(insn 15 14 16 3 (set (reg/v:DI 2 x2 [ f ])
(reg/v:DI 95 [ c ])) "rh1727453.i":5:17 47 {*movdi_aarch64}
(expr_list:REG_DEAD (reg/v:DI 95 [ c ])
(nil)))
Combine makes it into:
(insn 14 12 15 3 (set (reg/v:DI 1 x1 [ e ])
(reg:DI 92 [ b$h ])) "rh1727453.i":4:17 47 {*movdi_aarch64}
(nil))
(insn 15 14 16 3 (set (reg/v:DI 2 x2 [ f ])
(ior:DI (and:DI (reg:DI 92 [ b$h ])
(const_int 4294967295 [0xffffffff]))
(ashift:DI (subreg:DI (reg:SI 99) 0)
(const_int 32 [0x20])))) "rh1727453.i":5:17 794
{*aarch64_bfidi4_noand}
(expr_list:REG_DEAD (reg:DI 92 [ b$h ])
(expr_list:REG_DEAD (reg:SI 99)
(nil))))
(note the hard reg output, but still no input).
But then something during IRA decides to replace that reg:DI 92 with reg:DI 1
x1:
(insn 14 12 15 3 (set (reg/v:DI 1 x1 [ e ])
(reg:DI 92 [ b$h ])) "rh1727453.i":4:17 47 {*movdi_aarch64}
(expr_list:REG_DEAD (reg:DI 92 [ b$h ])
(nil)))
(insn 15 14 16 3 (set (reg/v:DI 2 x2 [ f ])
(ior:DI (and:DI (reg/v:DI 1 x1 [ e ])
(const_int 4294967295 [0xffffffff]))
(ashift:DI (subreg:DI (reg:SI 99) 0)
(const_int 32 [0x20])))) "rh1727453.i":5:17 794
{*aarch64_bfidi4_noand}
(expr_list:REG_DEAD (reg:SI 99)
(nil)))
And LRA can't deal with that, because the pattern is:
(define_insn ("*aarch64_bfidi4_noand")
[
(set (match_operand:DI 0 ("register_operand") ("=r"))
(ior:DI (and:DI (match_operand:DI 1 ("register_operand") ("0"))
(match_operand:DI 2 ("const_int_operand") ("n")))
(ashift:DI (match_operand:DI 3 ("register_operand") ("r"))
(match_operand:DI 4 ("aarch64_simd_shift_imm_di") ("n")))))
] ("aarch64_masks_and_shift_for_bfi_p (DImode, UINTVAL (operands[2]),
UINTVAL (operands[4]),
HOST_WIDE_INT_M1U << UINTVAL
(operands[4]) )") ("*{
operands[5] = GEN_INT (GET_MODE_BITSIZE (DImode) - UINTVAL (operands[4]));
return "bfi\t%x0, %x3, %4, %5";
}")
[
(set_attr ("type") ("bfm"))
])
and thus wants LRA to reload the operand 1 into the same register as operand 0.
I think "register_operand" "=r" and "register_operand" "0" operands are
extremely common in all backends, so I don't see an obvious bug on the aarch64
backend size here.
Vlad, could you please have a look?
>From gcc-bugs-return-648377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 20:35:58 2019
Return-Path: <gcc-bugs-return-648377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114082 invoked by alias); 6 Jul 2019 20:35: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 114034 invoked by uid 48); 6 Jul 2019 20:35:55 -0000
From: "frantisek at sumsal dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Sat, 06 Jul 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: sanitizer
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frantisek at sumsal 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: attachments.created
Message-ID: <bug-91101-4-rNbP7o64w2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00489.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #2 from Frantisek Sumsal <frantisek at sumsal dot cz> ---
Created attachment 46569
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46569&action=edit
test-conf-parser.i tempfile from GCC 9.1.0 (compressed due to size)
>From gcc-bugs-return-648378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 20:56:07 2019
Return-Path: <gcc-bugs-return-648378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12387 invoked by alias); 6 Jul 2019 20:56: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 11642 invoked by uid 48); 6 Jul 2019 20:56:03 -0000
From: "frantisek at sumsal dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Sat, 06 Jul 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: sanitizer
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frantisek at sumsal 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-91101-4-yPdYRKZ8gS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00490.txt.bz2
Content-length: 7809
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #3 from Frantisek Sumsal <frantisek at sumsal dot cz> ---
ltrace stastistics:
# WITH sanitizers and detect_stack_use_after_return=1
[vagrant@arch build]$ export
ASAN_OPTIONS=strict_string_checks=1:detect_stack_use_after_return=1:check_initialization_order=1:strict_init_order=1
[vagrant@arch build]$ ltrace -c
build-gcc-9.1.0-sanitizers-tempfiles/test-conf-parser
<...snip...>
==25291==LeakSanitizer has encountered a fatal error.
==25291==HINT: For debugging, try setting environment variable
LSAN_OPTIONS=verbosity=1:log_threads=1
==25291==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc)
% time seconds usecs/call calls function
------ ----------- ----------- --------- --------------------
99.86 28.250721 1661807 17 config_parse
0.03 0.007281 3640 2 __asan_init
0.01 0.003920 230 17 log_internal_realm
0.01 0.003716 50 73 __asan_stack_malloc_0
0.01 0.002837 166 17 fmkostemp_safe
0.01 0.002085 122 17 fwrite
0.01 0.001718 101 17 unlink_tempfilep
0.01 0.001490 87 17 rewind
0.00 0.001354 79 17 safe_fclose
0.00 0.001311 77 17 strlen
0.00 0.001208 50 24 free
0.00 0.001191 170 7 config_parse_mode
0.00 0.000998 142 7 config_parse_unsigned
0.00 0.000984 140 7 config_parse_path
0.00 0.000946 135 7 config_parse_int
0.00 0.000941 52 18 __asan_stack_malloc_3
0.00 0.000921 102 9 config_parse_iec_size
0.00 0.000901 128 7 config_parse_sec
0.00 0.000850 56 15 strcmp
0.00 0.000850 121 7 config_parse_nsec
0.00 0.000826 91 9 config_parse_si_size
0.00 0.000800 47 17 log_get_max_level_realm
0.00 0.000460 460 1 log_parse_environment_realm
0.00 0.000381 63 6 config_parse_strv
0.00 0.000348 49 7 strcmp_ptr
0.00 0.000336 112 3 config_parse_log_facility
0.00 0.000314 104 3 config_parse_log_level
0.00 0.000299 49 6 strv_equal
0.00 0.000282 56 5 strv_free
0.00 0.000154 154 1 __asan_unregister_globals
0.00 0.000109 54 2 config_parse_iec_uint64
0.00 0.000079 79 1 __asan_register_globals
0.00 0.000057 57 1 log_open
0.00 0.000047 47 1 __asan_version_mismatch_check_v8
------ ----------- ----------- --------- --------------------
100.00 28.290715 382 total
# WITH sanitizers and detect_stack_use_after_return=0
[vagrant@arch build]$ export
ASAN_OPTIONS=strict_string_checks=1:detect_stack_use_after_return=0:check_initialization_order=1:strict_init_order=1
[vagrant@arch build]$ ltrace -c
build-gcc-9.1.0-sanitizers-tempfiles/test-conf-parser
<...snip...>
==25301==LeakSanitizer has encountered a fatal error.
==25301==HINT: For debugging, try setting environment variable
LSAN_OPTIONS=verbosity=1:log_threads=1
==25301==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc)
% time seconds usecs/call calls function
------ ----------- ----------- --------- --------------------
98.90 2.914199 171423 17 config_parse
0.23 0.006749 3374 2 __asan_init
0.10 0.002973 174 17 log_internal_realm
0.09 0.002646 155 17 fmkostemp_safe
0.07 0.002095 123 17 fwrite
0.05 0.001416 83 17 unlink_tempfilep
0.05 0.001406 82 17 rewind
0.04 0.001317 54 24 free
0.04 0.001257 73 17 strlen
0.04 0.001225 72 17 safe_fclose
0.04 0.001060 151 7 config_parse_mode
0.03 0.000891 52 17 log_get_max_level_realm
0.03 0.000877 97 9 config_parse_iec_size
0.03 0.000862 57 15 strcmp
0.03 0.000851 121 7 config_parse_int
0.03 0.000846 120 7 config_parse_unsigned
0.03 0.000841 120 7 config_parse_path
0.03 0.000838 93 9 config_parse_si_size
0.02 0.000692 98 7 config_parse_sec
0.02 0.000679 97 7 config_parse_nsec
0.01 0.000395 395 1 log_parse_environment_realm
0.01 0.000364 60 6 config_parse_strv
0.01 0.000359 51 7 strcmp_ptr
0.01 0.000324 108 3 config_parse_log_facility
0.01 0.000309 51 6 strv_equal
0.01 0.000282 56 5 strv_free
0.01 0.000266 88 3 config_parse_log_level
0.01 0.000154 154 1 __asan_unregister_globals
0.00 0.000109 54 2 config_parse_iec_uint64
0.00 0.000082 82 1 __asan_register_globals
0.00 0.000054 54 1 __asan_version_mismatch_check_v8
0.00 0.000049 49 1 log_open
------ ----------- ----------- --------- --------------------
100.00 2.946467 291 total
# WITHOUT sanitizers
[vagrant@arch build]$ ltrace -c build-gcc-9.1.0/test-conf-parser
<...snip...>
% time seconds usecs/call calls function
------ ----------- ----------- --------- --------------------
97.98 1.259239 74072 17 config_parse
0.27 0.003530 207 17 log_internal_realm
0.19 0.002399 141 17 fmkostemp_safe
0.16 0.002012 118 17 fwrite
0.13 0.001629 95 17 unlink_tempfilep
0.12 0.001539 90 17 rewind
0.10 0.001301 54 24 free
0.10 0.001274 74 17 strlen
0.10 0.001225 72 17 safe_fclose
0.08 0.001057 151 7 config_parse_mode
0.08 0.001032 60 17 log_get_max_level_realm
0.07 0.000955 136 7 config_parse_int
0.07 0.000953 105 9 config_parse_iec_size
0.07 0.000914 130 7 config_parse_unsigned
0.07 0.000869 96 9 config_parse_si_size
0.07 0.000840 120 7 config_parse_nsec
0.06 0.000792 113 7 config_parse_sec
0.06 0.000720 102 7 config_parse_path
0.06 0.000715 47 15 strcmp
0.03 0.000403 57 7 strcmp_ptr
0.02 0.000307 51 6 strv_equal
0.02 0.000292 97 3 config_parse_log_facility
0.02 0.000290 96 3 config_parse_log_level
0.02 0.000284 47 6 config_parse_strv
0.02 0.000250 50 5 strv_free
0.02 0.000249 249 1 log_parse_environment_realm
0.01 0.000128 64 2 config_parse_iec_uint64
0.00 0.000050 50 1 log_open
------ ----------- ----------- --------- --------------------
100.00 1.285248 286 total
----
For some reason the `config_parse` function (in this particular case) is called
almost 10 times more often with `detect_stack_use_after_return=1` than
withoiut, which is not the case with GCC 8.3.0 (where it is 205089 calls with
`detect_stack_use_after_return=1` versus 192490 without).
>From gcc-bugs-return-648379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 21:22:16 2019
Return-Path: <gcc-bugs-return-648379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33733 invoked by alias); 6 Jul 2019 21:22: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 32206 invoked by uid 48); 6 Jul 2019 21:22:12 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91102] [9/10 Regression] aarch64 ICE on Linux kernel with -Os starting with r270266
Date: Sat, 06 Jul 2019 21:22: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.1.1
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: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91102-4-Sx8wXVJOoY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00491.txt.bz2
Content-length: 335
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91102
--- Comment #2 from Segher Boessenkool <segher at gcc dot gnu.org> ---
91102.c: In function 'foo':
91102.c:7:1: warning: control reaches end of non-void function [-Wreturn-type]
7 | }
| ^
so ice-on-invalid-code?
Although, hrm, inserting "return 3;" there still ICEs.
>From gcc-bugs-return-648380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 21:42:37 2019
Return-Path: <gcc-bugs-return-648380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61584 invoked by alias); 6 Jul 2019 21: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 61542 invoked by uid 48); 6 Jul 2019 21:42:33 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91102] [9/10 Regression] aarch64 ICE on Linux kernel with -Os starting with r270266
Date: Sat, 06 Jul 2019 21: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: 9.1.1
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: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91102-4-HOhgCQjEoc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00492.txt.bz2
Content-length: 986
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91102
--- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Before combine there were also
(insn 8 7 9 3 (set (reg/v:DI 95 [ c ])
(reg:DI 92 [ b$h ])) "91102.c":18:15 47 {*movdi_aarch64}
(nil))
(insn 11 10 12 3 (set (reg:DI 100)
(subreg:DI (reg:SI 99) 0)) "91102.c":19:12 47 {*movdi_aarch64}
(expr_list:REG_DEAD (reg:SI 99)
(nil)))
making in total
insn_cost 4 for 8: r95:DI=r92:DI
insn_cost 4 for 11: r100:DI=r99:SI#0
REG_DEAD r99:SI
insn_cost 4 for 12: zero_extract(r95:DI,0x20,0x20)=r100:DI
REG_DEAD r100:DI
insn_cost 4 for 15: x2:DI=r95:DI
REG_DEAD r95:DI
becoming
replacement cost 12
modifying insn i3 15: x2:DI=r92:DI&0xffffffff|r99:SI#0<<0x20
REG_DEAD r92:DI
REG_DEAD r99:SI
which is just fine afaics.
Or do we want to not have hard regs on outputs either? Do we get better
register allocation that way, for example?
>From gcc-bugs-return-648381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 22:13:17 2019
Return-Path: <gcc-bugs-return-648381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82998 invoked by alias); 6 Jul 2019 22:13: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 82931 invoked by uid 48); 6 Jul 2019 22:13:13 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85746] Premature evaluation of __builtin_constant_p?
Date: Sat, 06 Jul 2019 22: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.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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85746-4-iDJIJBDp1e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00493.txt.bz2
Content-length: 842
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85746
--- Comment #5 from Marc Glisse <glisse at gcc dot gnu.org> ---
The patch breaks 3 tests on a bootstrapped compiler:
c-c++-common/Warray-bounds-2.c
c-c++-common/ubsan/ptr-overflow-sanitization-1.c
gcc.dg/Warray-bounds-30.c
The last one in particular shows that the compiler is miscompiled (it works
with the stage 1 compiler but breaks with stage 2 or 3). From the dumps, the
compilation seems to diverge in FRE1, so the miscompiled function might be in a
function called from FRE.
I find it suspicious that just refusing to fold __builtin_constant_p can cause
this. The 2 explanations I can think of are:
- latent bug uncovered by the change
- a variable that needs to be statically initialized (order of initialization?)
and ends up dynamically initialized because of the change
>From gcc-bugs-return-648382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 22:24:42 2019
Return-Path: <gcc-bugs-return-648382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90085 invoked by alias); 6 Jul 2019 22:24: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 89924 invoked by uid 48); 6 Jul 2019 22:24:24 -0000
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/40073] Vector short/char shifts generate sub-optimal code
Date: Sat, 06 Jul 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: tree-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: amylaar 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-40073-4-o3gMIGVeLx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-40073-4@http.gcc.gnu.org/bugzilla/>
References: <bug-40073-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00494.txt.bz2
Content-length: 851
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40073
--- Comment #16 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> ---
Going from gcc 8.2 to gcc 9.1, I find the following two test cases are now
autovectorized:
/* { dg-do compile } */
/* { dg-options "-O3" } */
/* Test auto-vectorization */
#include "vector-types.h"
#define LENGTH 256
__attribute__((aligned (VECTOR_SIZE))) short a[LENGTH], b[LENGTH];
short c;
void foo (void) {
int i;
for (i=0; i<LENGTH; i++){
a[i] = b[i] >> (c & 0xf);
}
}
/* { dg-do compile } */
/* { dg-options "-O3" } */
/* Test auto-vectorization */
#include "vector-types.h"
#define LENGTH 256
__attribute__((aligned (VECTOR_SIZE))) unsigned short a[LENGTH], b[LENGTH];
unsigned short c;
void foo (void) {
int i;
for (i=0; i<LENGTH; i++){
a[i] = b[i] >> (c & 0xf);
}
}
>From gcc-bugs-return-648383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 06 22:51:40 2019
Return-Path: <gcc-bugs-return-648383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126701 invoked by alias); 6 Jul 2019 22: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 126650 invoked by uid 48); 6 Jul 2019 22:51:37 -0000
From: "mh+gcc at glandium dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90756] [7/8/9 Regression] g++ ICE in convert_move, at expr.c:218 on i686 and s390x
Date: Sat, 06 Jul 2019 22: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mh+gcc at glandium dot 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90756-4-DhuLLRqAyG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00495.txt.bz2
Content-length: 191
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90756
--- Comment #18 from Mike Hommey <mh+gcc at glandium dot org> ---
And similar ICE as comment 14 with 8.3 too.
9.1 works with the patch.
>From gcc-bugs-return-648384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 05:27:43 2019
Return-Path: <gcc-bugs-return-648384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32455 invoked by alias); 7 Jul 2019 05:27: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 32421 invoked by uid 48); 7 Jul 2019 05:27:37 -0000
From: "peter at cordes dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91103] New: AVX512 vector element extract uses more than 1 shuffle instruction; VALIGND can grab any element
Date: Sun, 07 Jul 2019 05: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: peter at cordes dot ca
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-91103-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00496.txt.bz2
Content-length: 5718
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91103
Bug ID: 91103
Summary: AVX512 vector element extract uses more than 1 shuffle
instruction; VALIGND can grab any element
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: peter at cordes dot ca
Target Milestone: ---
Target: x86_64-*-*, i?86-*-*
GCC9.1 and current trunk aren't good at extracting high elements, whether it's
with GNU C native vector syntax, or when auto-vectorizing something that ends
with the result in the high element.
Using VALIGND we can get any element with one immediate instruction, but its
better to use AVX2 VPERMPD(immediate) when possible. Or inside loops,
VPERMPS(vector), or VPERMT2PS(vector). Or of course vextractf32x4 if possible
(element at the bottom of a 128-bit lane).
Or with only AVX2 available, VPERMPD(immediate) for high elements in __m256 and
__m256d vectors is still a big win.
#include <immintrin.h>
float elem12(__m512 v) { return v[12]; }
float elem15(__m512 v) { return v[15]; }
gcc -Ofast -march=skylake-avx512
https://godbolt.org/z/241r8p
elem15:
vextractf32x8 ymm0, zmm0, 0x1
vextractf128 xmm0, ymm0, 0x1 # elem12 ends here, after these 2
insns
vshufps xmm0, xmm0, xmm0, 255
# no vzeroupper I guess because the caller must have __m512 vars too,
recent optimization
ret
But AVX512F has vextractf32x4 to extract a 128-bit lane, which would preclude
the need for AVX2 vextractf128. That's what clang does.
Obviously inside a loop it would be *much* better to use a single lane-crossing
VPERMPS to also avoid the shufps. Intel Skylake easily bottlenecks on shuffle
throughput. We'd need a 15 in an XMM register as a control vector, but loading
it would be off the latency critical path. (If we needed the scalar
zero-extended instead of garbage in high elements, we could VPERMI2PS or
VPERMT2PS with a zeroed vector and a shuffle-control.)
---
If the element we want is an even element in the low 256 bits, we can get it
with a VPERMPD-immediate. GCC does this:
elem6(float __vector(16)): # GCC 10 trunk
vextractf128 xmm0, ymm0, 0x1
vunpckhps xmm0, xmm0, xmm0
ret
Instead it should be AVX2 vpermpd ymm0, ymm0, 3
This bug also applies to __m256, not just __m512
https://www.felixcloutier.com/x86/vpermpd
VPERMPD is a 64-bit granularity lane-crossing shuffle. The AVX512F immediate
version reuses the immediate for another 256-bit wide shuffle in the upper
half; only the vector-control version can bring an element from the top half of
a ZMM down to the bottom. But if we're going to use a vector control, we might
as well use VPERMPS.
For the integer version of this bug, use VPERMQ
------
But we can do even better by using an integer VALIGND (AVX512F) shuffle on FP
data. There unfortunately isn't an FP flavour of VALIGND, just integer.
AFAIK, Skylake-AVX512 still has no bypass-delay penalty for integer shuffles
between FP math instructions, i.e. the shift unit is connected to both FP and
integer forwarding networks. Intel's optimization manual for Skylake (client)
has a bypass-latency table that shows 0 extra latency cycles for SHUF/5/1,3
reading from anything, or anything reading from it.
https://www.felixcloutier.com/x86/valignd:valignq It's a 4 or 8-byte
granularity version of palignr, except that it's lane-crossing so the 256 and
512-bit versions are actually useful. The immediate shift count can thus bring
*any* element down to the bottom. (Using the same input twice makes it a
rotate).
VALIGND is good on Knight's Landing, too: unlike most 2-input shuffles, it has
1 per clock throughput.
For *any* compile-time-constant index, we can always compile v[i] to this:
extract15:
valignd zmm0, zmm0, zmm0, 15 # I think this is right.
ret
The only downside I'm aware of is that some future AVX512 CPU might not run
VALIGND as efficiently as SKX and KNL.
----
For vector elements narrower than 32 bits, we may need 2 shuffles even if we
consider using a shuffle-control vector. On Skylake-AVX512, AVX512BW vpermw
will get the job done, but costs 2 shuffle uops. On CannonLake (and presumably
other future Intel), it and AVX512VBMI vpermb are only 1 uop, so it's
definitely worth creating a shuffle-control vector if it can be reused.
Also worth considering instead of 2 shuffles: *unaligned* spill / reload like
ICC does for GNU C native vector indexing. Store-forwarding latency is only 6
or 7 cycles I think, and it avoids any port 5 pressure. Not generally a good
choice IMO when we can get the job done in one shuffle, but worth considering
if we need multiple elements. If the function doesn't need the stack aligned,
an unaligned spill is generally cheapish, and store-forwarding still works
efficiently.
IceLake is supposed to introduce a 2nd shuffle unit; that should help a lot to
reduce shuffle port throughput bottlenecks. So we don't want to get too
aggressive tuning for store/reload, I don't think.
----
Semi-related for integer shuffles:
long long integer_extract(__m256i v) {
return v[3];
}
uses a longer AVX512VL instruction instead of a shorter AVX2 vextracti128
integer_extract(long long __vector(4)):
vextracti64x2 xmm0, ymm0, 0x1 # should be vextracti128
vpextrq rax, xmm0, 1
ret
Or store/reload instead of these 2 shuffles, depending on context.
>From gcc-bugs-return-648385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 06:18:20 2019
Return-Path: <gcc-bugs-return-648385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64620 invoked by alias); 7 Jul 2019 06: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 64574 invoked by uid 48); 7 Jul 2019 06:18:17 -0000
From: "mh+gcc at glandium dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90756] [7/8/9 Regression] g++ ICE in convert_move, at expr.c:218 on i686 and s390x
Date: Sun, 07 Jul 2019 06:18: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.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mh+gcc at glandium dot 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90756-4-thQ2zD3zuW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00497.txt.bz2
Content-length: 224
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90756
--- Comment #19 from Mike Hommey <mh+gcc at glandium dot org> ---
Applying the patch from PR90139 and this one works fixes the ICEs on this file
with both GCC 7 and 8.
>From gcc-bugs-return-648386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 08:11:05 2019
Return-Path: <gcc-bugs-return-648386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115158 invoked by alias); 7 Jul 2019 08: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 115097 invoked by uid 48); 7 Jul 2019 08:10:49 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/91100] [9,10 Regression] FAIL: gnat.dg/socket1.adb execution test
Date: Sun, 07 Jul 2019 08:10: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: 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-91100-4-sxm1VP4ucW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91100-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91100-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00498.txt.bz2
Content-length: 613
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91100
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-07
CC| |ebotcazou at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Let's just disable the test on HP-UX as it is on Solaris.
>From gcc-bugs-return-648387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 09:12:08 2019
Return-Path: <gcc-bugs-return-648387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83150 invoked by alias); 7 Jul 2019 09:12: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 83106 invoked by uid 48); 7 Jul 2019 09:12:03 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85746] Premature evaluation of __builtin_constant_p?
Date: Sun, 07 Jul 2019 09: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.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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85746-4-Tf8xFjF12h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00499.txt.bz2
Content-length: 1206
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85746
--- Comment #6 from Marc Glisse <glisse at gcc dot gnu.org> ---
The problematic file seems to be tree-dfa.o, and the only difference I see in
the .original dump is the use of __builtin_constant_p in wi::lshift (3
occurrences because of templates)
- if (precision <= 64)
+ if (__builtin_constant_p (xi.D.16865.D.16740.precision > 64) != 0 &&
xi.D.16865.D.16740.precision > 64 ? ((__builtin_constant_p (shift <= 62) != 0
&& shift <= 62) && xi.D.16865.D.16740.len == 1) && *NON_LVALUE_EXPR
<xi.D.16865.D.16740.val> <= (const long int) (9223372036854775807 >> shift) :
precision <= 64)
which corresponds to the use of STATIC_CONSTANT_P in wide-int.h
if (STATIC_CONSTANT_P (xi.precision > HOST_BITS_PER_WIDE_INT)
? (STATIC_CONSTANT_P (shift < HOST_BITS_PER_WIDE_INT - 1)
&& xi.len == 1
&& xi.val[0] <= (HOST_WIDE_INT) ((unsigned HOST_WIDE_INT)
HOST_WIDE_INT_MAX >> shift))
: precision <= HOST_BITS_PER_WIDE_INT)
{
val[0] = xi.ulow () << shift;
result.set_len (1);
}
>From gcc-bugs-return-648388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 09:13:07 2019
Return-Path: <gcc-bugs-return-648388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85280 invoked by alias); 7 Jul 2019 09: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 85174 invoked by uid 48); 7 Jul 2019 09:13:03 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91102] [9/10 Regression] aarch64 ICE on Linux kernel with -Os starting with r270266
Date: Sun, 07 Jul 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: target
X-Bugzilla-Version: 9.1.1
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: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91102-4-q5qcKwdbfU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00500.txt.bz2
Content-length: 1803
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91102
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #2)
> 91102.c: In function 'foo':
> 91102.c:7:1: warning: control reaches end of non-void function
> [-Wreturn-type]
> 7 | }
> | ^
>
> so ice-on-invalid-code?
Well, invalid at runtime, so valid if not called.
> Although, hrm, inserting "return 3;" there still ICEs.
The testcase has been creduced and hand cleaned up, forgot about the return
value.
Let's talk about
int
foo (long d, long l)
{
register long e asm ("x1") = d;
register long f asm("x2") = l;
asm ("" : : "r" (e), "r" (f));
return 3;
}
struct T { int i; int j; };
union S { long h; struct T t; };
void
bar (union S b)
{
while (1)
{
union S c = b;
c.t.j++;
b.h = foo (b.h, c.h);
}
}
then. The change is done in decrease_live_ranges_number:
2128 if (sregno < FIRST_PSEUDO_REGISTER
2129 && reg_mentioned_p (dest, PATTERN (q)))
2130 failed = 1;
2131
2132 /* Attempt to replace all uses. */
2133 else if (!validate_replace_rtx (src, dest, q))
2134 failed = 1;
So, shouldn't we have some code for dregno < FIRST_PSEUDO_REGISTER that checks
for cases like this (dunno what exactly, just insns where already at least one
of the operands from extract_operands is a hard register, or more specifically
don't propagate into an operand that has number in a constraint and
corresponding argument is already (a different) hard register, something else?
>From gcc-bugs-return-648389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 09:25:39 2019
Return-Path: <gcc-bugs-return-648389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123625 invoked by alias); 7 Jul 2019 09: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 120667 invoked by uid 48); 7 Jul 2019 09:25:32 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90813] [10 regression] gfortran.dg/proc_ptr_51.f90 fails (SIGSEGV) after 272084
Date: Sun, 07 Jul 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: rtl-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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90813-4-MLMwNy0qAw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00501.txt.bz2
Content-length: 4501
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90813
--- Comment #26 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #25)
> At expand time, the assignment is
>
>
> ;; c_ = c;
>
> (insn 35 34 36 (set (reg/f:DI 140)
> (unspec:DI [
> (symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
> (reg:DI 2 2)
> ] UNSPEC_TOCREL)) "proc_ptr_51.f90":26:0 -1
> (expr_list:REG_EQUAL (symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
> (nil)))
>
> (insn 36 35 37 (set (reg/f:DI 141)
> (unspec:DI [
> (symbol_ref:DI ("__f_MOD_c") [flags 0x3] <function_decl
> 0x3fff7
> 86a7d00 c>)
> (reg:DI 2 2)
> ] UNSPEC_TOCREL)) "proc_ptr_51.f90":26:0 -1
> (expr_list:REG_EQUAL (symbol_ref:DI ("__f_MOD_c") [flags 0x3]
> <function_de
> cl 0x3fff786a7d00 c>)
> (nil)))
>
> (insn 37 36 0 (set (mem/f/c:DI (reg/f:DI 140) [13 c_+0 S8 A64])
> (reg/f:DI 141)) "proc_ptr_51.f90":26:0 -1
> (nil))
>
>
> while the use is (immediately after that!)
>
>
> ;; rhs.2 = c_.5_12 (); [return slot optimization]
>
> (insn 38 37 39 (set (reg:DI 142)
> (plus:DI (reg/f:DI 112 virtual-stack-vars)
> (const_int 48 [0x30]))) "proc_ptr_51.f90":35:0 -1
> (nil))
>
> (insn 39 38 40 (set (reg/f:DI 143)
> (mem/u/c:DI (unspec:DI [
> (symbol_ref/u:DI ("*.LC1") [flags 0x2])
> (reg:DI 2 2)
> ] UNSPEC_TOCREL) [21 S8 A8])) "proc_ptr_51.f90":35:0 -1
> (expr_list:REG_EQUAL (symbol_ref:DI ("__f_MOD_c_") [flags 0xc0]
> <var_decl 0x3fff7aa40990 c_>)
> (nil)))
>
> (insn 40 39 41 (set (reg/f:DI 144)
> (mem/f/c:DI (reg/f:DI 143) [13 c_+0 S8 A64])) "proc_ptr_51.f90":35:0
> -1
> (nil))
>
> (insn 41 40 42 (set (reg:DI 3 3)
> (reg:DI 142)) "proc_ptr_51.f90":35:0 -1
> (nil))
>
> (insn 42 41 43 (set (reg:DI 145)
> (mem:DI (reg/f:DI 144) [0 S8 A8])) "proc_ptr_51.f90":35:0 -1
> (nil))
>
> (insn 43 42 44 (set (reg:DI 97 ctr)
> (reg:DI 145)) "proc_ptr_51.f90":35:0 -1
> (nil))
>
> (insn 44 43 45 (set (reg:DI 11 11)
> (mem:DI (plus:DI (reg/f:DI 144)
> (const_int 16 [0x10])) [0 S8 A8])) "proc_ptr_51.f90":35:0 -1
> (nil))
>
> (call_insn 45 44 46 (parallel [
> (call (mem:SI (reg:DI 97 ctr) [0 *c_.5_12 S4 A8])
> (const_int 64 [0x40]))
> (use (mem:DI (plus:DI (reg/f:DI 144)
> (const_int 8 [0x8])) [0 S8 A8]))
> (set (reg:DI 2 2)
> (unspec:DI [
> (const_int 40 [0x28])
> ] UNSPEC_TOCSLOT))
> (clobber (reg:DI 96 lr))
> ]) "proc_ptr_51.f90":35:0 -1
> (expr_list:REG_CALL_DECL (nil)
> (nil))
> (expr_list (use (reg:DI 11 11))
> (expr_list:DI (use (reg:DI 3 3))
> (nil))))
>
> (insn 46 45 47 (set (reg:DI 146)
> (plus:DI (reg/f:DI 112 virtual-stack-vars)
> (const_int 48 [0x30]))) "proc_ptr_51.f90":35:0 -1
> (nil))
>
> (insn 47 46 0 (set (reg:TI 127 [ rhs.2 ])
> (mem:TI (reg:DI 146) [7 S16 A64])) "proc_ptr_51.f90":35:0 -1
> (nil))
>
>
>
> so it is wrong (if this is wrong!) at expand already.
>
>
> In gimple this was:
>
> c_ = c;
> c_.5_12 = c_;
> rhs.2 = c_.5_12 (); [return slot optimization]
OK, so this is really
static fnptrtype c_ = &c;
dumped in a weird way and then a load from the global var. Not sure why this
isn't optimized on GIMPLE (to a direct call)...
Note the type we're basing the indirect call ABI on is
struct __class_f_S_p (*<T5e3>) (void) _12;
not sure if that's correct. To me it seems the function returns a pointer,
not an aggregate. That may be very well the (frontend) issue?
For the C testcase
typedef void (*fnptr)(void);
void bar(void);
fnptr g;
fnptr foo()
{
g = bar;
return g;
}
we happily optimize the load, even when I make the types mismatching.
The odd thing is that for the Fortran example even the tree oracle claims
the store doesn't alias the load...
Because they are different variables! Dumping with -uid shows
c_D.3918 = cD.3925;
c_.5_12 = c_D.3933;
rhs.2D.4008 = c_.5_12 ();
that's probably not intended either... c_D.3933 is never initialized
anywhere in the testcase.
>From gcc-bugs-return-648391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 09:50:44 2019
Return-Path: <gcc-bugs-return-648391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20647 invoked by alias); 7 Jul 2019 09:50: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 20619 invoked by uid 48); 7 Jul 2019 09:50:41 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/91068] [10 regression][MIPS] New FAIL: madd-3.c and msub-5.c start with r272849
Date: Sun, 07 Jul 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: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
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-91068-4-Q9epQE1hRm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91068-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91068-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00503.txt.bz2
Content-length: 468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91068
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 on trunk.
>From gcc-bugs-return-648390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 09:50:00 2019
Return-Path: <gcc-bugs-return-648390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19765 invoked by alias); 7 Jul 2019 09:50: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 19715 invoked by uid 55); 7 Jul 2019 09:49:55 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/91068] [10 regression][MIPS] New FAIL: madd-3.c and msub-5.c start with r272849
Date: Sun, 07 Jul 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: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
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-91068-4-4vaz2KPr4T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91068-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91068-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00502.txt.bz2
Content-length: 3112
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91068
--- Comment #2 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Sun Jul 7 09:49:24 2019
New Revision: 273175
URL: https://gcc.gnu.org/viewcvs?rev=273175&root=gcc&view=rev
Log:
PR91068: Fix MIPS fallout from IRA matched operand changes
PR91068 is a case in which we have (ignoring non-LRA alternatives):
[(set (match_operand:SI 0 "register_operand" "=l,d?")
(plus:SI (mult:SI (match_operand:SI 1 "register_operand" "d,d")
(match_operand:SI 2 "register_operand" "d,d"))
(match_operand:SI 3 "register_operand" "0,d")))
(clobber (match_scratch:SI 4 "=X,l"))
(clobber (match_scratch:SI 5 "=X,&d"))]
where the first alternative is one instruction but the second is two.
This is very similar to the case that my recent IRA patches were
supposed to help. The crucial difference is that the cheap
alternative requires a single-register class while the expensive
alternative uses general registers.
This makes a difference when one of operand 0 or 3 can naturally be
allocated to LO but the other can't. If IRA makes that allocation,
both alternatives require one reload of equal cost and so the first
alternative clearly wins.
However, if we say that tying operands 0 and 3 saves the cost of a full
move, then all other things being equal, IRA will prefer to allocate
both registers to the same GPR. The registers will then naturally
fit the second alternative.
This has a more drastic effect in the MIPS case than it should because
using the GPR alternative is much more expensive there than it appears
to the RA. But that's really a separate problem and something we were
able to live with before my IRA patch.
What makes tying less useful here is the fact that the tied register is
a single-register class. I think in those circumstances it's better not
to use tied operands at all and instead use "l" for the inputs.
Allocating the input to LO, and allocating the output to LO, then depend
naturally on class costs. If we decide to allocate at least one of them
to LO, we'll use the cheap alternative, otherwise we'll (correctly) use
the expensive alternative. This effectively restores the situation
before my IRA patch, but this time making the preference on the input
register more explicit.
I originally wrote the patterns in the early days of IRA, and certainly
well before LRA. I think they were largely influened by reload rather
than RA proper (see the comment above *mul_acc_si, which is all about
the reload behaviour). LRA copes with the two-"l" case just fine.
The patch may well cause problems for -mno-lra, but I think we should
cull that option anyway.
2019-07-07 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR target/91068
* config/mips/mips.md (*mul_acc_si, *mul_acc_si_r3900, *macc)
(*msac, *msac_using_macc, *mul_sub_si): Use "l" for input operands
instead of matching them to "l" output operands.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/mips/mips.md
>From gcc-bugs-return-648392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 10:16:27 2019
Return-Path: <gcc-bugs-return-648392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34649 invoked by alias); 7 Jul 2019 10:16: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 34516 invoked by uid 48); 7 Jul 2019 10:16:05 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85746] Premature evaluation of __builtin_constant_p?
Date: Sun, 07 Jul 2019 10: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: 9.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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85746-4-SeX9PlYHxN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00504.txt.bz2
Content-length: 834
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85746
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rsandifo at gcc dot gnu.org
--- Comment #7 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #6)
> && xi.val[0] <= (HOST_WIDE_INT) ((unsigned HOST_WIDE_INT)
> HOST_WIDE_INT_MAX >> shift))
The issue occurs with xi.val[0] == -9223372036854775808 (lshift_large returns a
result of length 2 for that). I don't know if the code mishandles this case, or
if such a number is not supposed to exist in the first place, but that does
seem like a bug.
>From gcc-bugs-return-648393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 10:54:14 2019
Return-Path: <gcc-bugs-return-648393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127567 invoked by alias); 7 Jul 2019 10:54: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 127514 invoked by uid 55); 7 Jul 2019 10:54:09 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91077] [8/9/10 Regression] Wrong indexing when using a pointer
Date: Sun, 07 Jul 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: fortran
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91077-4-xFhLCSs0pJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91077-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91077-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00505.txt.bz2
Content-length: 795
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91077
--- Comment #8 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun Jul 7 10:53:37 2019
New Revision: 273176
URL: https://gcc.gnu.org/viewcvs?rev=273176&root=gcc&view=rev
Log:
2019-07-07 Paul Thomas <pault@gcc.gnu.org>
PR fortran/91077
* trans-array.c (gfc_conv_scalarized_array_ref) Delete code
that gave symbol backend decl for subref arrays and deferred
length variables.
2019-07-07 Paul Thomas <pault@gcc.gnu.org>
PR fortran/91077
* gfortran.dg/pointer_array_11.f90 : New test.
Added:
trunk/gcc/testsuite/gfortran.dg/pointer_array_11.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-648394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 12:01:24 2019
Return-Path: <gcc-bugs-return-648394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82874 invoked by alias); 7 Jul 2019 12:01: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 82812 invoked by uid 48); 7 Jul 2019 12:01:19 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91060] [10 regression] gcc.c-torture/execute/scal-to-vec1.c fails on armeb-none-linux-gnueabihf since r272843
Date: Sun, 07 Jul 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: middle-end
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: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-91060-4-yabWt3mt5B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00506.txt.bz2
Content-length: 2192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rsandifo at gcc dot gnu.org
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Hmm, using a cross configured as
trunk/configure --target=armeb-none-linux-gnueabihf --with-cpu=cortex-a9
--with-fpu=neon-fp16 --enable-languages=c
and trimming the testcase to the first line I cannot reproduce the reported
assembly. I get at -O3
.arm
.fpu softvfp
.type main, %function
main:
@ args = 0, pretend = 0, frame = 16
@ frame_needed = 0, uses_anonymous_args = 0
movw ip, #:lower16:.LANCHOR0
push {r4, r5, lr}
movt ip, #:upper16:.LANCHOR0
mov r0, #0
mov r1, r0
mov r2, r0
ldr ip, [ip]
mov r3, r0
mov r5, #3
mov r4, #5
movt r1, 4
movt r2, 6
movt r3, 8
sub sp, sp, #20
sxth ip, ip
bfi r1, r4, #0, #16
add ip, ip, #2
sxth lr, ip
bfi r0, lr, #16, #16
cmp ip, lr
mov lr, #7
mov ip, #9
bfi r0, r5, #0, #16
bfi r2, lr, #0, #16
bfi r3, ip, #0, #16
strd r0, [sp]
strd r2, [sp, #8]
bne .L5
mov r0, #0
add sp, sp, #20
@ sp needed
pop {r4, r5, pc}
.L5:
bl abort
also the GIMPLE looks good to me, we compare only the first non-constant
element and optimized the others at compile-time.
Are you sure the first line fails? The ones with bitwise handling look
more "interesting" (^, & and |) since vector lowering plays odd tricks there
and VN elides an intermediate VIEW_CONVERT_EXPR.
Not sure what is required to do a runtest with qemu, I can try throwing
in newlib and binutils into a combined tree, but is that enough?
Maybe Richard can help here as well.
>From gcc-bugs-return-648395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 12:28:00 2019
Return-Path: <gcc-bugs-return-648395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125062 invoked by alias); 7 Jul 2019 12:28: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 125032 invoked by uid 48); 7 Jul 2019 12:27:56 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91060] [10 regression] gcc.c-torture/execute/scal-to-vec1.c fails on armeb-none-linux-gnueabihf since r272843
Date: Sun, 07 Jul 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: middle-end
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: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91060-4-fmnpfa6wqI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00507.txt.bz2
Content-length: 189
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
hmm, armeb-linux doesn't use newlib. awkward to set up a cross :/
>From gcc-bugs-return-648396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 12:47:53 2019
Return-Path: <gcc-bugs-return-648396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57085 invoked by alias); 7 Jul 2019 12:47: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 57049 invoked by uid 48); 7 Jul 2019 12:47:49 -0000
From: "antifermion at protonmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91104] New: auto... in lambda expression reorders parameters
Date: Sun, 07 Jul 2019 12: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antifermion at protonmail 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-91104-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00508.txt.bz2
Content-length: 1407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91104
Bug ID: 91104
Summary: auto... in lambda expression reorders parameters
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: antifermion at protonmail dot com
Target Milestone: ---
Created attachment 46570
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46570&action=edit
source file to reproduce the bug
Code:
void test(void (*f)(int, int, int)) {
f(1, 2, 3);
}
int main() {
test([](auto... args) {
printf("%d %d %d\n", args...);
});
test([](int a, int b, int c) {
printf("%d %d %d\n", a, b, c);
});
}
Actual Output:
2 3 1
1 2 3
Expected Output:
1 2 3
1 2 3
Compiler flags:
g++ -std=c++17 -Wall -Wextra -fno-strict-aliasing -fwrapv
-fno-aggressive-loop-optimizations main.cpp -o main && ./main
(c++14 has the same behavior)
Output of g++ -v:
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-linux-gnu/9.1.0/lto-wrapper
Target: x86_64-linux-gnu
Configured with: /usr/src/gcc/configure --build=x86_64-linux-gnu
--disable-multilib --enable-languages=c,c++,fortran,go
Thread model: posix
gcc version 9.1.0 (GCC)
System type: Debian Stretch (amd64)
>From gcc-bugs-return-648397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 12:59:36 2019
Return-Path: <gcc-bugs-return-648397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66299 invoked by alias); 7 Jul 2019 12:59: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 66182 invoked by uid 48); 7 Jul 2019 12:59:31 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/90813] [10 regression] gfortran.dg/proc_ptr_51.f90 fails (SIGSEGV) after 272084
Date: Sun, 07 Jul 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: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
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-90813-4-hrZPc7nLln@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00509.txt.bz2
Content-length: 870
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90813
--- Comment #27 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #26)
> The odd thing is that for the Fortran example even the tree oracle claims
> the store doesn't alias the load...
>
> Because they are different variables! Dumping with -uid shows
>
> c_D.3918 = cD.3925;
> c_.5_12 = c_D.3933;
> rhs.2D.4008 = c_.5_12 ();
>
> that's probably not intended either... c_D.3933 is never initialized
> anywhere in the testcase.
Sorry to have to ask but... How did you get this dump?
gfortran -O3 -fdump-tree-all -uid proc_ptr_51.f90
and grepping for c_D under proc_ptr.f90.* (on POWER) does not show any
hits for me. (And what does -uid do?)
The last useful dump I can find results in what can be seen in
comment #14, which seems correct.
>From gcc-bugs-return-648398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 13:11:07 2019
Return-Path: <gcc-bugs-return-648398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19115 invoked by alias); 7 Jul 2019 13: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 19061 invoked by uid 55); 7 Jul 2019 13:11:03 -0000
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/91100] [9,10 Regression] FAIL: gnat.dg/socket1.adb execution test
Date: Sun, 07 Jul 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: ada
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dave.anglin at bell 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:
Message-ID: <bug-91100-4-jPLDx5CN5l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91100-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91100-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00510.txt.bz2
Content-length: 273
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91100
--- Comment #2 from dave.anglin at bell dot net ---
On 2019-07-07 4:10 a.m., ebotcazou at gcc dot gnu.org wrote:
> Let's just disable the test on HP-UX as it is on Solaris.
Okay. The pass/fail seems inconsistent.
>From gcc-bugs-return-648399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 13:22:55 2019
Return-Path: <gcc-bugs-return-648399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121037 invoked by alias); 7 Jul 2019 13: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 121004 invoked by uid 48); 7 Jul 2019 13:22:52 -0000
From: "gsocshubham at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91105] New: internal compiler error: maximum number of generated reload insns per insn achieved (90)
Date: Sun, 07 Jul 2019 13:22: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: gsocshubham 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 cf_gcchost cf_gcctarget cf_gccbuild attachments.created
Message-ID: <bug-91105-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00511.txt.bz2
Content-length: 2231
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91105
Bug ID: 91105
Summary: internal compiler error: maximum number of generated
reload insns per insn achieved (90)
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: gsocshubham at gmail dot com
Target Milestone: ---
Host: x86_64-linux-gnu
Target: x86_64-linux-gnu
Build: x86_64-linux-gnu
Created attachment 46571
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46571&action=edit
Preprocessed code of ICE causing program "crash1.c"
--------------------COMPILER CONFIGURATION------------------------------
Using built-in specs.
COLLECT_GCC=./xgcc
Target: x86_64-pc-linux-gnu
Configured with: ../gcc/configure --enable-languages=c,c++ --enable-lto
--disable-bootstrap : (reconfigured) ../gcc/configure --enable-lto
--disable-bootstrap --enable-languages=c,c++,lto --no-create --no-recursion
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.0.0 20190707 (experimental) (GCC)
--------------------COMMAND LINE USED FOR COMPILATION-----------------------
~/pull-martin-compiler/build/gcc/xgcc -B ~/pull-martin-compiler/build/gcc/
crash1.i -O0 -w
during RTL pass: reload
crash1.c: In function ‘func_1’:
crash1.c:1317:1: internal compiler error: maximum number of generated reload
insns per insn achieved (90)
0xadf746 lra_constraints(bool)
../../gcc/gcc/lra-constraints.c:4902
0xac711c lra(_IO_FILE*)
../../gcc/gcc/lra.c:2468
0xa7a4b9 do_reload
../../gcc/gcc/ira.c:5522
0xa7a4b9 execute
../../gcc/gcc/ira.c:5706
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.
---------------------------REDUCED TEST CASE--------------------------
void g();
struct a {
short b;
short c;
short d;
};
union {
struct a b;
} __attribute__((aligned(32), transparent_union)) e;
void f() { g(e); }
>From gcc-bugs-return-648400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 13:49:53 2019
Return-Path: <gcc-bugs-return-648400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45942 invoked by alias); 7 Jul 2019 13:49: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 45836 invoked by uid 48); 7 Jul 2019 13:49:48 -0000
From: "gsocshubham at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91106] New: internal compiler error: output_operand: invalid use of register 'frame'
Date: Sun, 07 Jul 2019 13:49: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: gsocshubham 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 cf_gcchost cf_gcctarget cf_gccbuild attachments.created
Message-ID: <bug-91106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00512.txt.bz2
Content-length: 2783
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91106
Bug ID: 91106
Summary: internal compiler error: output_operand: invalid use
of register 'frame'
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: gsocshubham at gmail dot com
Target Milestone: ---
Host: x86_64-linux-gnu
Target: x86_64-linux-gnu
Build: x86_64-linux-gnu
Created attachment 46572
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46572&action=edit
Preprocessed code of ICE causing program "crash2.c"
-----------------------COMPILER CONFIGURATION---------------------------------
Using built-in specs.
COLLECT_GCC=/home/extended_csmith/pull-martin-compiler/build/gcc/xgcc
Target: x86_64-pc-linux-gnu
Configured with: ../gcc/configure --enable-languages=c,c++ --enable-lto
--disable-bootstrap : (reconfigured) ../gcc/configure --enable-lto
--disable-bootstrap --enable-languages=c,c++,lto --no-create --no-recursion
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.0.0 20190707 (experimental) (GCC)
-----------------COMMAND LINE USED FOR COMPILATION-------------------------
~/pull-martin-compiler/build/gcc/xgcc -B ~/pull-martin-compiler/build/gcc/ -O0
crash2.i -w
during RTL pass: final
crash2.c: In function ‘func_1’:
crash2.c:982:1: internal compiler error: output_operand: invalid use of
register 'frame'
0x90fd53 output_operand_lossage(char const*, ...)
../../gcc/gcc/final.c:3610
0x101cdd4 ix86_print_operand_address_as
../../gcc/gcc/config/i386/i386.c:13152
0x101eaff ix86_print_operand(_IO_FILE*, rtx_def*, int)
../../gcc/gcc/config/i386/i386.c:12901
0x91006c output_operand(rtx_def*, int)
../../gcc/gcc/final.c:4052
0x91093e output_asm_insn(char const*, rtx_def**)
../../gcc/gcc/final.c:3964
0x91203f final_scan_insn_1
../../gcc/gcc/final.c:3107
0x9134fb final_scan_insn(rtx_insn*, _IO_FILE*, int, int, int*)
../../gcc/gcc/final.c:3153
0x913649 final_1
../../gcc/gcc/final.c:2021
0x914404 rest_of_handle_final
../../gcc/gcc/final.c:4659
0x914404 execute
../../gcc/gcc/final.c:4737
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.
-------------------------REDUCED CODE-------------------------------
void f();
#pragma pack(1)
struct a {
int b;
char c;
};
union {
struct a b;
} __attribute__((aligned(32), transparent_union)) d;
void e() { f(d); }
>From gcc-bugs-return-648401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 14:33:28 2019
Return-Path: <gcc-bugs-return-648401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33139 invoked by alias); 7 Jul 2019 14:33: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 33096 invoked by uid 55); 7 Jul 2019 14:33:25 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91077] [8/9/10 Regression] Wrong indexing when using a pointer
Date: Sun, 07 Jul 2019 14: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: 9.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91077-4-fLGTwWBN9i@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91077-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91077-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00513.txt.bz2
Content-length: 859
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91077
--- Comment #9 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun Jul 7 14:32:53 2019
New Revision: 273177
URL: https://gcc.gnu.org/viewcvs?rev=273177&root=gcc&view=rev
Log:
2019-07-07 Paul Thomas <pault@gcc.gnu.org>
PR fortran/91077
* trans-array.c (gfc_conv_scalarized_array_ref) Delete code
that gave symbol backend decl for subref arrays and deferred
length variables.
2019-07-07 Paul Thomas <pault@gcc.gnu.org>
PR fortran/91077
* gfortran.dg/pointer_array_11.f90 : New test.
Added:
branches/gcc-9-branch/gcc/testsuite/gfortran.dg/pointer_array_11.f90
Modified:
branches/gcc-9-branch/gcc/fortran/ChangeLog
branches/gcc-9-branch/gcc/fortran/trans-array.c
branches/gcc-9-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-648402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 14:38:14 2019
Return-Path: <gcc-bugs-return-648402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43051 invoked by alias); 7 Jul 2019 14:38: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 42765 invoked by uid 55); 7 Jul 2019 14:38:11 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/90813] [10 regression] gfortran.dg/proc_ptr_51.f90 fails (SIGSEGV) after 272084
Date: Sun, 07 Jul 2019 14: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: wrong-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-90813-4-rU6JSzEcQU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00514.txt.bz2
Content-length: 1172
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90813
--- Comment #28 from rguenther at suse dot de <rguenther at suse dot de> ---
On July 7, 2019 2:59:29 PM GMT+02:00, "tkoenig at gcc dot gnu.org"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90813
>
>--- Comment #27 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
>(In reply to Richard Biener from comment #26)
>
>> The odd thing is that for the Fortran example even the tree oracle
>claims
>> the store doesn't alias the load...
>>
>> Because they are different variables! Dumping with -uid shows
>>
>> c_D.3918 = cD.3925;
>> c_.5_12 = c_D.3933;
>> rhs.2D.4008 = c_.5_12 ();
>>
>> that's probably not intended either... c_D.3933 is never initialized
>> anywhere in the testcase.
>
>Sorry to have to ask but... How did you get this dump?
>
>gfortran -O3 -fdump-tree-all -uid proc_ptr_51.f90
-fdump-tree-all-uid without the space
>
>and grepping for c_D under proc_ptr.f90.* (on POWER) does not show any
>hits for me. (And what does -uid do?)
>
>The last useful dump I can find results in what can be seen in
>comment #14, which seems correct.
>From gcc-bugs-return-648403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 14:51:27 2019
Return-Path: <gcc-bugs-return-648403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67035 invoked by alias); 7 Jul 2019 14: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 66988 invoked by uid 55); 7 Jul 2019 14:51:24 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91077] [8/9/10 Regression] Wrong indexing when using a pointer
Date: Sun, 07 Jul 2019 14: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: 9.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91077-4-bzI3j7soUc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91077-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91077-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00515.txt.bz2
Content-length: 822
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91077
--- Comment #10 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun Jul 7 14:50:53 2019
New Revision: 273178
URL: https://gcc.gnu.org/viewcvs?rev=273178&root=gcc&view=rev
Log:
2019-07-07 Paul Thomas <pault@gcc.gnu.org>
PR fortran/91077
* trans-array.c (gfc_conv_scalarized_array_ref) Delete code
that gave symbol backend decl for subref arrays.
2019-07-07 Paul Thomas <pault@gcc.gnu.org>
PR fortran/91077
* gfortran.dg/pointer_array_11.f90 : New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/pointer_array_11.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/trans-array.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-648404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 15:10:59 2019
Return-Path: <gcc-bugs-return-648404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95914 invoked by alias); 7 Jul 2019 15:10: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 95788 invoked by uid 55); 7 Jul 2019 15:10:54 -0000
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/84877] Local stack copy of BLKmode parameter on the stack is not aligned when the requested alignment exceeds MAX_SUPPORTED_STACK_ALIGNMENT
Date: Sun, 07 Jul 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: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dave.anglin at bell dot net
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84877-4-ECW5yFNpBY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00516.txt.bz2
Content-length: 1586
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84877
--- Comment #11 from dave.anglin at bell dot net ---
On 2019-07-06 3:39 p.m., amylaar at gcc dot gnu.org wrote:
> Since the esirisc port is not in the FSF tree, it doesn't really count for
> testing; also, the behaviour will vary depending on argument passing of the
> target, so we need to test a variety of targets.
Test still fails on hppa:
(gdb) disass
Dump of assembler code for function main:
=> 0x00010388 <+0>:Â Â Â Â stw rp,-14(sp)
  0x0001038c <+4>:    addil L%0,dp,r1
  0x00010390 <+8>:    ldo 80(sp),sp
  0x00010394 <+12>:   ldo 10(r1),r1
  0x00010398 <+16>:   ldw 0(r1),ret0
  0x0001039c <+20>:   ldw 4(r1),ret1
  0x000103a0 <+24>:   stw ret0,-78(sp)
  0x000103a4 <+28>:   stw ret1,-74(sp)
  0x000103a8 <+32>:   ldo -78(sp),r26
  0x000103ac <+36>:   ldw 8(r1),r19
  0x000103b0 <+40>:   ldw c(r1),r20
  0x000103b4 <+44>:   stw r19,-70(sp)
  0x000103b8 <+48>:   stw r20,-6c(sp)
  0x000103bc <+52>:   b,l 0x10660 <foo>,rp
  0x000103c0 <+56>:   nop
$sp is aligned on entry to main:
(gdb) p/x $sp
$1 = 0xf8d02300
However, the invisible reference is a $sp - 0x78. That's not sufficiently
aligned.
Dave
>From gcc-bugs-return-648405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 16:19:11 2019
Return-Path: <gcc-bugs-return-648405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129742 invoked by alias); 7 Jul 2019 16:19: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 129705 invoked by uid 48); 7 Jul 2019 16:19:08 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91077] [8/9/10 Regression] Wrong indexing when using a pointer
Date: Sun, 07 Jul 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: fortran
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91077-4-6tbLylawn7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91077-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91077-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00517.txt.bz2
Content-length: 478
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91077
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #11 from Paul Thomas <pault at gcc dot gnu.org> ---
Fixed on all three branches.
Thanks for the report, Ygal.
Paul
>From gcc-bugs-return-648406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 16:39:52 2019
Return-Path: <gcc-bugs-return-648406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33866 invoked by alias); 7 Jul 2019 16:39: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 33837 invoked by uid 48); 7 Jul 2019 16:39:47 -0000
From: "colomar.6.4.3 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91107] New: __attribute__((pure)) to function with non-const pointers
Date: Sun, 07 Jul 2019 16:39: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: colomar.6.4.3 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-91107-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00518.txt.bz2
Content-length: 2636
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91107
Bug ID: 91107
Summary: __attribute__((pure)) to function with non-const
pointers
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: colomar.6.4.3 at gmail dot com
Target Milestone: ---
I have a function that takes two arrays and writes into a third array the
result of a pure function (c_i = a_i / b_i):
inline
void array_division (ptrdiff_t nmemb,
double dest[static nmemb],
const double src1[static nmemb],
const double src2[static nmemb])
__attribute__((nonnull, pure));
inline
void array_division (ptrdiff_t nmemb,
double dest[static nmemb],
const double src1[static nmemb],
const double src2[static nmemb])
{
for (ptrdiff_t i = 0; i < nmemb; i++)
dest[i] = src1[i] / src2[i];
}
Given that it works with full arrays instead of single variables, I can't just
return the output, and therefore need to modify the array through a pointer,
which goes against what a pure function is by the docs.
However, I think it is still as valid as any other pure function to be
optimized as a pure function.
A pure function is one that acts as a function of its parameters, and the
values pointed to by those parameters; and if none of the parameters, nor the
values pointed to by them, change between two calls, they should be redundant
and the call can be omitted, evaluating to the same value returned by the
previous call.
This function follows all those rules: If none of the 3 arrays change between
two function calls, the function call can be completely removed; and they
evaluate to the same value (which is none, because it's void).
Am I right in thinking that GCC should allow this usage of
__attibute__((pure))?
Or is there any optimization achieved by pure that would be defeated by this
function?
Btw, I tricked GCC into accepting to compile this code just by adding a dummy
`return 0;`. Is that safe, or is the optimization likely to produce broken
code?
If this function is finally accepted as a pure function, pure should be
accepted to be used in a void function, and accept non-const parameters, but if
not, I think there's no reason at all to allow non-const pointers, and should
probably be banned.
>From gcc-bugs-return-648407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 18:16:26 2019
Return-Path: <gcc-bugs-return-648407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126545 invoked by alias); 7 Jul 2019 18:16: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 124258 invoked by uid 48); 7 Jul 2019 18:16:16 -0000
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/84877] Local stack copy of BLKmode parameter on the stack is not aligned when the requested alignment exceeds MAX_SUPPORTED_STACK_ALIGNMENT
Date: Sun, 07 Jul 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: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hp at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84877-4-Bx5KfDZxsh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00519.txt.bz2
Content-length: 3209
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84877
--- Comment #12 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to Jorn Wolfgang Rennecke from comment #10)
> Created attachment 46567 [details]
> Fix for targets that pass the argument by invisible reference
Thanks for your efforts. This *may* have affected the code generated by
gcc.dg/pr84877.c; that test now passes, but that's unreliable as I've seen the
outcome depends on random stack alignment of the context, and my baseline is
from a context different enough. I believe inspecting the generated code isn't
of much interest given David Anglin's observations for hppa and...
However, it introduces these regressions:
+gcc.sum gcc.dg/pr80286.c
+gcc.sum gcc.dg/torture/pr78542.c
+gcc.sum gcc.dg/torture/pr86363.c
+gcc.sum gcc.dg/torture/va-arg-25.c
They are all internal compiler errors that seem to be one and the same (beware
of copypaste):
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/testsuite/gcc.dg/pr80286.c:
In function 'main':
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/testsuite/gcc.dg/pr80286.c:18:9:
internal compiler error: in co
nvert_move, at expr.c:217
0x7f6763 convert_move(rtx_def*, rtx_def*, int)
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/expr.c:217
0x7f6cf1 convert_modes(machine_mode, machine_mode, rtx_def*, int)
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/expr.c:712
0x7fd420 store_expr(tree_node*, rtx_def*, int, bool, bool)
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/expr.c:5710
0x6af577 initialize_argument_information
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/calls.c:2090
0x6b0d28 expand_call(tree_node*, rtx_def*, int)
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/calls.c:3612
0x7efcf7 expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/expr.c:11044
0x7fcd74 store_expr(tree_node*, rtx_def*, int, bool, bool)
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/expr.c:5685
0x7fe7e6 expand_assignment(tree_node*, tree_node*, bool)
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/expr.c:5447
0x6ca297 expand_call_stmt
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/cfgexpand.c:2727
0x6ca297 expand_gimple_stmt_1
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/cfgexpand.c:3708
0x6cb0e6 expand_gimple_stmt
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/cfgexpand.c:3867
0x6d08c5 expand_gimple_basic_block
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/cfgexpand.c:5907
0x6d3616 execute
/netapp/hp3_storage/hp/autotest/pr84877-amylaar1/gcc/gcc/cfgexpand.c:6530
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
FAIL: gcc.dg/pr80286.c (internal compiler error)
FAIL: gcc.dg/pr80286.c (test for excess errors)
>From gcc-bugs-return-648408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 18:43:20 2019
Return-Path: <gcc-bugs-return-648408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87310 invoked by alias); 7 Jul 2019 18:43: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 87280 invoked by uid 55); 7 Jul 2019 18:43:16 -0000
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91090] A suspicious code in tree-ssa-dom.c
Date: Sun, 07 Jul 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: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91090-4-z3ZqTpYxtB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91090-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91090-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00520.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91090
--- Comment #3 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Author: law
Date: Sun Jul 7 18:42:45 2019
New Revision: 273184
URL: https://gcc.gnu.org/viewcvs?rev=273184&root=gcc&view=rev
Log:
PR tree-optimization/91090
* tree-ssa-dom.c (simplify_stmt_for_jump_threading): Fix logic error
in handling of ranges to simplify switch statements.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/tree-ssa-dom.c
>From gcc-bugs-return-648409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 18:46:44 2019
Return-Path: <gcc-bugs-return-648409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91830 invoked by alias); 7 Jul 2019 18:46: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 91799 invoked by uid 48); 7 Jul 2019 18:46:41 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91090] A suspicious code in tree-ssa-dom.c
Date: Sun, 07 Jul 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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91090-4-4g42kpSBLI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91090-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91090-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00521.txt.bz2
Content-length: 545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91090
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Jeffrey A. Law <law at redhat dot com> ---
Fixed on the trunk. Only causes missed optimizations, so I don't think there's
a strong need to backport to the release branches.
>From gcc-bugs-return-648410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 19:51:21 2019
Return-Path: <gcc-bugs-return-648410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95008 invoked by alias); 7 Jul 2019 19:51: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 93469 invoked by uid 48); 7 Jul 2019 19:51:18 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61339] add mismatch between struct and class [-Wmismatched-tags] to non-bugs
Date: Sun, 07 Jul 2019 19: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.9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
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 assigned_to
Message-ID: <bug-61339-4-BFGHeyyoDQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61339-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61339-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00522.txt.bz2
Content-length: 463
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61339
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
--- Comment #10 from Martin Sebor <msebor at gcc dot gnu.org> ---
Testing a patch.
>From gcc-bugs-return-648411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 20:36:01 2019
Return-Path: <gcc-bugs-return-648411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71263 invoked by alias); 7 Jul 2019 20: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 71218 invoked by uid 48); 7 Jul 2019 20:35:57 -0000
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/91030] Poor performance of I/O -fconvert=big-endian
Date: Sun, 07 Jul 2019 20:36: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: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jb 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-91030-4-IQdgX62gYa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91030-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91030-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00523.txt.bz2
Content-length: 577
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91030
Janne Blomqvist <jb at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jb at gcc dot gnu.org
--- Comment #36 from Janne Blomqvist <jb at gcc dot gnu.org> ---
I have access to a system with Lustre, which is another parallel file system
popular in HPC. Unfortunately I don't have gcc trunk setup there, but I can
easily test the C benchmark; give me a day or two.
>From gcc-bugs-return-648412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 20:51:01 2019
Return-Path: <gcc-bugs-return-648412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98517 invoked by alias); 7 Jul 2019 20: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 98459 invoked by uid 48); 7 Jul 2019 20:50:58 -0000
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/91030] Poor performance of I/O -fconvert=big-endian
Date: Sun, 07 Jul 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: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jb 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-91030-4-AThXbRVh6o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91030-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91030-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00524.txt.bz2
Content-length: 365
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91030
--- Comment #37 from Janne Blomqvist <jb at gcc dot gnu.org> ---
One thing we could do would be to switch to pread and pwrite instead of using
lseek. That would avoid a few syscalls when updating the record length marker.
Though I guess the issue with GPFS isn't directly related to the number of
syscalls?
>From gcc-bugs-return-648413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 21:12:00 2019
Return-Path: <gcc-bugs-return-648413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112127 invoked by alias); 7 Jul 2019 21:12: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 112051 invoked by uid 55); 7 Jul 2019 21:11:56 -0000
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Sun, 07 Jul 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: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: dave.anglin at bell 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-61577-4-ezhrI0Zg4M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00525.txt.bz2
Content-length: 1109
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #57 from dave.anglin at bell dot net ---
On 2019-07-05 7:57 p.m., elowe at elowe dot com wrote:
> Doing some more testing on my "gprel unfixed fix" 32-bit gcc, I found out that
> it seems to be missing the 32-bit pointer swizzling needed to make 32bit
> executables on 64-bit IA-64. The test program assembler is missing an addp4
> instruction - when I add in this instruction, my second test program also
> works.
It's not clear to me that this is necessary. The movl instruction loads a
64-bit immediate.
In this case, it should be the offset between gp (r1) and .LC0. At the
br.call.sptk.many b0
instruction, r36 should contain the address of .LC0. You should be able to see
this with gdb.
It should be possible to adjust the offset to account for any difference
between 32 and
64-bit runtimes.
If the offset value is wrong, I think we have a binutils issue. Maybe -milp32
is not being
passed on hpux to assembler.
I don't see any difference between 32-bit and 64-bit code, or between hpux and
linux.
>From gcc-bugs-return-648414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 22:07:10 2019
Return-Path: <gcc-bugs-return-648414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42387 invoked by alias); 7 Jul 2019 22:07: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 42327 invoked by uid 48); 7 Jul 2019 22:07:05 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91102] [9/10 Regression] aarch64 ICE on Linux kernel with -Os starting with r270266
Date: Sun, 07 Jul 2019 22: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: 9.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
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: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91102-4-pltNyb1TPy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00526.txt.bz2
Content-length: 2592
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91102
--- Comment #5 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #1)
>
> Vlad, could you please have a look?
The culprit patch is actually
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=265942
Prohibiting reload for any user defined registers which should be matched is
too harsh. We still can reload operands using the match if no one is an
earlier clobber operand.
The following patch should solve the problem:
Index: ../../gcc/gcc/lra-constraints.c
===================================================================
--- ../../gcc/gcc/lra-constraints.c (revision 273177)
+++ ../../gcc/gcc/lra-constraints.c (working copy)
@@ -2172,8 +2172,9 @@
else
{
/* Operands don't match. If the operands are
- different user defined explicit hard registers,
- then we cannot make them match. */
+ different user defined explicit hard
+ registers, then we cannot make them match
+ when one is early clobber operand. */
if ((REG_P (*curr_id->operand_loc[nop])
|| SUBREG_P (*curr_id->operand_loc[nop]))
&& (REG_P (*curr_id->operand_loc[m])
@@ -2191,10 +2192,14 @@
&& REG_USERVAR_P (nop_reg)
&& REG_P (m_reg)
&& HARD_REGISTER_P (m_reg)
- && REG_USERVAR_P (m_reg))
- break;
+ && REG_USERVAR_P (m_reg)) {
+ for (int i = 0; i < early_clobbered_regs_num;
i++)
+ if (m == early_clobbered_nops[i])
+ break;
+ if (i < early_clobbered_regs_num ||
early_clobber_p)
+ break;
+ }
}
-
/* Both operands must allow a reload register,
otherwise we cannot make them match. */
if (curr_alt[m] == NO_REGS)
Although I'll take some time to think about the solution before submitting it
into the trunk.
>From gcc-bugs-return-648415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 07 23:28:19 2019
Return-Path: <gcc-bugs-return-648415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123425 invoked by alias); 7 Jul 2019 23:28: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 123317 invoked by uid 48); 7 Jul 2019 23:28:14 -0000
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/84877] Local stack copy of BLKmode parameter on the stack is not aligned when the requested alignment exceeds MAX_SUPPORTED_STACK_ALIGNMENT
Date: Sun, 07 Jul 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: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amylaar at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84877-4-KOj4izXp9v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00527.txt.bz2
Content-length: 1360
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84877
--- Comment #13 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> ---
(In reply to Hans-Peter Nilsson from comment #12)
> (In reply to Jorn Wolfgang Rennecke from comment #10)
> > Created attachment 46567 [details]
> > Fix for targets that pass the argument by invisible reference
>
> Thanks for your efforts. This *may* have affected the code generated by
> gcc.dg/pr84877.c; that test now passes, but that's unreliable as I've seen
> the outcome depends on random stack alignment of the context, and my
> baseline is from a context different enough. I believe inspecting the
> generated code isn't of much interest given David Anglin's observations for
> hppa and...
>
> However, it introduces these regressions:
> +gcc.sum gcc.dg/pr80286.c
> +gcc.sum gcc.dg/torture/pr78542.c
> +gcc.sum gcc.dg/torture/pr86363.c
> +gcc.sum gcc.dg/torture/va-arg-25.c
I tried if I could reproduce this with a cross-compiler built for
--target=hppa-linux-gnu; the va-arg-25.c test case needs headers, but the
others can be
compiled just using xgcc & cc1. I tried with the options in dg-options,
and for pr78542.c / pr86363.c I also tried additional -O options.
However, I don't see any ICE. Is there a special configuration or set of
options needed, or is this just impossible with a cross compiler?
>From gcc-bugs-return-648416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 00:13:33 2019
Return-Path: <gcc-bugs-return-648416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38861 invoked by alias); 8 Jul 2019 00:13: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 38777 invoked by uid 48); 8 Jul 2019 00:13:30 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/84877] Local stack copy of BLKmode parameter on the stack is not aligned when the requested alignment exceeds MAX_SUPPORTED_STACK_ALIGNMENT
Date: Mon, 08 Jul 2019 00:13: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-84877-4-zkV4Rwxn4i@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00528.txt.bz2
Content-length: 406
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84877
--- Comment #14 from John David Anglin <danglin at gcc dot gnu.org> ---
Created attachment 46573
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46573&action=edit
Preproccessed source for pr84877.c
I don't believe there are any new failures or ICEs on hppa-linux with your
patch.
pr84877 aborts due stack alignment as noted in prior comment.
>From gcc-bugs-return-648417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 00:39:31 2019
Return-Path: <gcc-bugs-return-648417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70458 invoked by alias); 8 Jul 2019 00:39: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 70377 invoked by uid 48); 8 Jul 2019 00:39:27 -0000
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/84877] Local stack copy of BLKmode parameter on the stack is not aligned when the requested alignment exceeds MAX_SUPPORTED_STACK_ALIGNMENT
Date: Mon, 08 Jul 2019 00: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amylaar at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-84877-4-Ra8oZe55LV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00529.txt.bz2
Content-length: 2348
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84877
--- Comment #15 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> ---
Created attachment 46574
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46574&action=edit
patch for the case that the stack is sufficiently aligned
(In reply to dave.anglin from comment #11)
> $sp is aligned on entry to main:
> (gdb) p/x $sp
> $1 = 0xf8d02300
>
> However, the invisible reference is a $sp - 0x78. That's not sufficiently
> aligned.
I've built a cross compiler to take a closer look.
MAX_SUPPORTED_STACK_ALIGNMENT is 512, so the problem is completely different
for this target. Looking at pa.h, the value comes from
PREFERRED_STACK_BOUNDARY :
/* Boundary (in *bits*) on which stack pointer is always aligned;
certain optimizations in combine depend on this.
The HP-UX runtime documents mandate 64-byte and 16-byte alignment for
the stack on the 32 and 64-bit ports, respectively. However, we
are only guaranteed that the stack is aligned to BIGGEST_ALIGNMENT
in main. Thus, we treat the former as the preferred alignment. */
#define STACK_BOUNDARY BIGGEST_ALIGNMENT
#define PREFERRED_STACK_BOUNDARY (TARGET_64BIT ? 128 : 512)
...
/* No data type wants to be aligned rounder than this. The long double
type has 16-byte alignment on the 64-bit target even though it was never
implemented in hardware. The software implementation only needs 8-byte
alignment. This matches the biggest alignment of the HP compilers. */
#define BIGGEST_ALIGNMENT (2 * BITS_PER_WORD)
Even with TARGET_64_BIT, we got a PREFERRED_STACK_BOUNDARY of 128 .
However:
#define UNITS_PER_WORD (TARGET_64BIT ? 8 : 4)
It seems suspicious that PREFERRED_STACK_BOUNDARY is smaller for TARGET_64BIT ?
Be this as it may, the problem for the 84877 testcase is not that the stack has
insufficient alignment, but that the stack slot doesn't have an aligned offset.
The alignment gets pruned in function.c:get_stack_local_alignment :
if (mode == BLKmode)
alignment = BIGGEST_ALIGNMENT;
I have attached a patch to preserve the alignment of the passed type for the
case that the stack is already sufficiently aligned.
To test the case where the stack is insufficiently aligned, for hppa we should
use a different testcase with > 512 bit alignment of the type.
>From gcc-bugs-return-648418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 03:39:37 2019
Return-Path: <gcc-bugs-return-648418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74961 invoked by alias); 8 Jul 2019 03:39: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 74909 invoked by uid 48); 8 Jul 2019 03:39:33 -0000
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/84877] Local stack copy of BLKmode parameter on the stack is not aligned when the requested alignment exceeds MAX_SUPPORTED_STACK_ALIGNMENT
Date: Mon, 08 Jul 2019 03: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hp at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84877-4-1p6nWTjrX6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00530.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84877
--- Comment #16 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to Jorn Wolfgang Rennecke from comment #13)
> I tried if I could reproduce this with a cross-compiler built for
> --target=hppa-linux-gnu;
My target of concern is cris-elf, just as in my earlier comment in this PR.
Sorry I missed mentioning this in my latest reply. A cross from x86_64-linux
should do it.
>From gcc-bugs-return-648419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 04:07:48 2019
Return-Path: <gcc-bugs-return-648419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28489 invoked by alias); 8 Jul 2019 04:07: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 28446 invoked by uid 48); 8 Jul 2019 04:07:45 -0000
From: "elowe at elowe dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Mon, 08 Jul 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: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: elowe at elowe 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-61577-4-kY78rnpONd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00531.txt.bz2
Content-length: 1261
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #58 from EML <elowe at elowe dot com> ---
32 Bit:
Second Test Program (derived from a crashing conftest)
#include <ctype.h>
int
main ()
{
int j = 0;
j = islower(0);
printf("j is: %d\n", j);
return 0;
}
<snip>
[.LCFI2:]
mov r35 = r1
.body
.loc 1 6 7
;;
st4 [r34] = r0
.loc 1 8 18
addl r14 = @ltoffx(__SB_masks#), r1
;;
ld8.mov r14 = [r14], __SB_masks#
;;
ld4 r14 = [r14]
.loc 1 8 16
;;
cmp.eq p6, p7 = 0, r14
(p6) br.cond.dptk .L2
.loc 1 8 35 discriminator 1
addl r14 = @ltoffx(__SB_masks#), r1
;;
ld8.mov r14 = [r14], __SB_masks#
;;
ld4 r14 = [r14]
;;
ld4 r14 = [r14] <<<--- crashes here. Missing addp4 r14 = 0,r14
.loc 1 8 16 discriminator 1
;;
and r14 = 64, r14
br .L3
;;
<snip>
If you insert the addp4 r14 = 0,r14 before that command (like gcc 4.9.3 does),
the program compiles and runs correctly
I'll upload the .s for "IsLower.c" - it's definitely a 32 bit executable, so
the correct options are being passed around.
>From gcc-bugs-return-648420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 04:11:32 2019
Return-Path: <gcc-bugs-return-648420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31460 invoked by alias); 8 Jul 2019 04:11: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 31409 invoked by uid 48); 8 Jul 2019 04:11:29 -0000
From: "elowe at elowe dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Mon, 08 Jul 2019 04: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: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: elowe at elowe 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-61577-4-4TDPGyOMK0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00532.txt.bz2
Content-length: 238
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #59 from EML <elowe at elowe dot com> ---
Created attachment 46575
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46575&action=edit
islower 32 bit test assembler
>From gcc-bugs-return-648421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 04:21:32 2019
Return-Path: <gcc-bugs-return-648421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36592 invoked by alias); 8 Jul 2019 04:21: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 36545 invoked by uid 48); 8 Jul 2019 04:21:29 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/44566] configuration with multiple targets / backends is not supported.
Date: Mon, 08 Jul 2019 04: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: 4.6.0
X-Bugzilla-Keywords: patch
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: cc
Message-ID: <bug-44566-4-yAIAOugxQL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-44566-4@http.gcc.gnu.org/bugzilla/>
References: <bug-44566-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00533.txt.bz2
Content-length: 1041
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44566
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |froydnj at gcc dot gnu.org,
| |mark at codesourcery dot com,
| |steven at gcc dot gnu.org
--- Comment #10 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jorn Wolfgang Rennecke from comment #7)
> The patches have been tested & posted to gcc-patches:
> http://gcc.gnu.org/ml/gcc-patches/2010-06/msg02492.html
> http://gcc.gnu.org/ml/gcc-patches/2010-06/msg02452.html
> http://gcc.gnu.org/ml/gcc-patches/2010-06/msg02495.html
> http://gcc.gnu.org/ml/gcc-patches/2010-06/msg02618.html
> http://gcc.gnu.org/ml/gcc-patches/2010-06/msg02645.html
> http://gcc.gnu.org/ml/gcc-patches/2010-06/msg02649.html
cc-ing some people from these threads
>From gcc-bugs-return-648422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 04:24:44 2019
Return-Path: <gcc-bugs-return-648422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41157 invoked by alias); 8 Jul 2019 04:24: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 41084 invoked by uid 48); 8 Jul 2019 04:24:41 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/77510] genautomata memory footprint for MIPS
Date: Mon, 08 Jul 2019 04:24: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: 5.4.0
X-Bugzilla-Keywords: build, memory-hog
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: cc
Message-ID: <bug-77510-4-9tNG7o2GnI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77510-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77510-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00534.txt.bz2
Content-length: 409
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77510
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mfortune at gmail dot com
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
cc-ing MIPS maintainer
>From gcc-bugs-return-648423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 04:29:56 2019
Return-Path: <gcc-bugs-return-648423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44532 invoked by alias); 8 Jul 2019 04: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 44474 invoked by uid 48); 8 Jul 2019 04:29:52 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87274] -std=c++11 breaks quadmath macros
Date: Mon, 08 Jul 2019 04: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: 8.2.1
X-Bugzilla-Keywords:
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-87274-4-uzlF198MDn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87274-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87274-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00535.txt.bz2
Content-length: 1526
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87274
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #4)
> (In reply to Jonathan Wakely from comment #2)
> > (In reply to Patrick J. LoPresti from comment #0)
> > > Note that my code does not use any quad-precision literals; just the
> > > documented `FLT128_MAX` macro.
> >
> > Which is a quad-precision literal, of course.
> >
> > > I realize quadmath is more a C thing than a C++ thing... But it would
> > > still be nice if this worked, IMO.
> >
> > It does work if you use the right options to allow the necessary extensions.
> >
> > > On a possibly related note, writing "__extension__" before a
> > > quad-precision literal does not silence this error. Perhaps it should (?)
> >
> > Yes, maybe. Confirming for that feature request.
>
>
> This is an error, not a warning nor a warning converted to an error.
> __extension__ silences warnings, it does not make something that should not
> compile into something that should compile.
>
> However, the following should work and it doesn't:
>
> // with -Wpedantic -std=gnu++11
> #include <quadmath.h>
> __float128 x0 = FLT128_MAX; /* warn */
> __float128 x1 = __extension__ FLT128_MAX; /* no warn */
That sounds like bug 71003 (which apparently was already added as related from
the other end, but just making sure to mention it on this end as well, since I
filed it and would like to see it fixed)
>From gcc-bugs-return-648424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 04:35:29 2019
Return-Path: <gcc-bugs-return-648424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48216 invoked by alias); 8 Jul 2019 04:35: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 48149 invoked by uid 48); 8 Jul 2019 04:35:26 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80518] -Wsuggest-override does not warn about missing override on destructor
Date: Mon, 08 Jul 2019 04: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: 5.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:
Message-ID: <bug-80518-4-oKNlx8xIIH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80518-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80518-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00536.txt.bz2
Content-length: 529
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80518
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Arnaud Desitter from comment #2)
> Interesting. Shame that there is no rationale.
>
> I suppose that "-Wsuggest-override=2" could warn about "override" missing
> for destructor.
I'd just like to repeat my preference for named options over numeric warning
levels here; named options are separately controllable and thus more useful.
Maybe call it -Wsuggest-override-destructor instead?
>From gcc-bugs-return-648425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 06:19:01 2019
Return-Path: <gcc-bugs-return-648425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44980 invoked by alias); 8 Jul 2019 06:19: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 44905 invoked by uid 48); 8 Jul 2019 06:18:58 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85746] Premature evaluation of __builtin_constant_p?
Date: Mon, 08 Jul 2019 06: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: 9.0
X-Bugzilla-Keywords: missed-optimization
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85746-4-XM6QHJyVX5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00537.txt.bz2
Content-length: 795
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85746
--- Comment #8 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #7)
> (In reply to Marc Glisse from comment #6)
> > && xi.val[0] <= (HOST_WIDE_INT) ((unsigned HOST_WIDE_INT)
> > HOST_WIDE_INT_MAX >> shift))
>
> The issue occurs with xi.val[0] == -9223372036854775808 (lshift_large
> returns a result of length 2 for that). I don't know if the code mishandles
> this case, or if such a number is not supposed to exist in the first place,
> but that does seem like a bug.
Yeah, looks like this should have been an unsigned HOST_WIDE_INT comparison
instead, i.e. casting xi.val[0] rather than the shift result.
>From gcc-bugs-return-648426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 06:35:20 2019
Return-Path: <gcc-bugs-return-648426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88817 invoked by alias); 8 Jul 2019 06:35: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 84393 invoked by uid 48); 8 Jul 2019 06:35:16 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91060] [10 regression] gcc.c-torture/execute/scal-to-vec1.c fails on armeb-none-linux-gnueabihf since r272843
Date: Mon, 08 Jul 2019 06:35: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: 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: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91060-4-UDhZ1Y5xAt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00538.txt.bz2
Content-length: 783
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
--- Comment #7 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Christophe Lyon from comment #4)
> Unfortunately, it's still failing as of r273133.
>
> It fails at the very first check:
> v1 = 2 + v0; check (short, 8, v0, v1, 2, +, l);
>
> The generated code for main is:
> main:
...
> vmov.16 d16[0], r0
> sxth r1, r0
> vadd.i16 q0, q8, q9
> add ip, r1, #2
> vmov.s16 r2, d0[3]
Yeah, this looks wrong. We should be adding 2 to a single element
here, but we're extracting from one index and inserting into another.
The first quoted instruction should be using [3] as well.
I'd be unsurprised if this was a target bug.
>From gcc-bugs-return-648427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 06:54:22 2019
Return-Path: <gcc-bugs-return-648427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21997 invoked by alias); 8 Jul 2019 06:54: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 21949 invoked by uid 48); 8 Jul 2019 06:54:18 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91060] [10 regression] gcc.c-torture/execute/scal-to-vec1.c fails on armeb-none-linux-gnueabihf since r272843
Date: Mon, 08 Jul 2019 06: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon 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-91060-4-rHnNZEAq0H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00539.txt.bz2
Content-length: 588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
--- Comment #8 from Christophe Lyon <clyon at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #5)
> Hmm, using a cross configured as
>
> trunk/configure --target=armeb-none-linux-gnueabihf --with-cpu=cortex-a9
> --with-fpu=neon-fp16 --enable-languages=c
>
> and trimming the testcase to the first line I cannot reproduce the reported
> assembly. I get at -O3
>
> .arm
> .fpu softvfp
For some reason, you are not targeting the right FPU, I have:
.arm
.fpu neon-fp16
>From gcc-bugs-return-648428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 06:56:28 2019
Return-Path: <gcc-bugs-return-648428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29619 invoked by alias); 8 Jul 2019 06:56: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 29559 invoked by uid 48); 8 Jul 2019 06:56:24 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91060] [10 regression] gcc.c-torture/execute/scal-to-vec1.c fails on armeb-none-linux-gnueabihf since r272843
Date: Mon, 08 Jul 2019 06:56: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: 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: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91060-4-d4aF1buis7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00540.txt.bz2
Content-length: 951
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
--- Comment #9 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to rsandifo@gcc.gnu.org from comment #7)
> (In reply to Christophe Lyon from comment #4)
> > Unfortunately, it's still failing as of r273133.
> >
> > It fails at the very first check:
> > v1 = 2 + v0; check (short, 8, v0, v1, 2, +, l);
> >
> > The generated code for main is:
> > main:
> ...
> > vmov.16 d16[0], r0
> > sxth r1, r0
> > vadd.i16 q0, q8, q9
> > add ip, r1, #2
> > vmov.s16 r2, d0[3]
>
> Yeah, this looks wrong. We should be adding 2 to a single element
> here, but we're extracting from one index and inserting into another.
> The first quoted instruction should be using [3] as well.
>
> I'd be unsurprised if this was a target bug.
Er, pretend that message never happened, first thing Monday morning :-)
>From gcc-bugs-return-648429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 07:06:28 2019
Return-Path: <gcc-bugs-return-648429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45148 invoked by alias); 8 Jul 2019 07: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 44594 invoked by uid 55); 8 Jul 2019 07:06:21 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91060] [10 regression] gcc.c-torture/execute/scal-to-vec1.c fails on armeb-none-linux-gnueabihf since r272843
Date: Mon, 08 Jul 2019 07:06: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: 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: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91060-4-RgkLC1FnVX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00541.txt.bz2
Content-length: 1135
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
--- Comment #10 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 8 Jul 2019, clyon at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
>
> --- Comment #8 from Christophe Lyon <clyon at gcc dot gnu.org> ---
> (In reply to Richard Biener from comment #5)
> > Hmm, using a cross configured as
> >
> > trunk/configure --target=armeb-none-linux-gnueabihf --with-cpu=cortex-a9
> > --with-fpu=neon-fp16 --enable-languages=c
> >
> > and trimming the testcase to the first line I cannot reproduce the reported
> > assembly. I get at -O3
> >
> > .arm
> > .fpu softvfp
>
> For some reason, you are not targeting the right FPU, I have:
> .arm
> .fpu neon-fp16
I noticed that - but it doesn't change even when supplying
-mpfu=neon-fp16 -mcpu=cortex-a9
I suppose some configure-time checking disables this feature somehow
without notifying me :/ (don't have a armeb assembler installed,
trying a pure cc1 cross)
Anyway, I can't reproduce even after spending 1+ hours on this.
>From gcc-bugs-return-648430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 07:10:01 2019
Return-Path: <gcc-bugs-return-648430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80536 invoked by alias); 8 Jul 2019 07:10: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 79976 invoked by uid 55); 8 Jul 2019 07:09:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83518] [8/9/10 Regression] Missing optimization: useless instructions should be dropped
Date: Mon, 08 Jul 2019 07: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: 8.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: P2
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-83518-4-cmAo5kVQm0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83518-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83518-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00542.txt.bz2
Content-length: 1505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Mon Jul 8 07:09:24 2019
New Revision: 273194
URL: https://gcc.gnu.org/viewcvs?rev=273194&root=gcc&view=rev
Log:
2019-07-08 Richard Biener <rguenther@suse.de>
PR tree-optimization/83518
* tree-ssa-sccvn.c: Include splay-tree.h.
(struct pd_range, struct pd_data): New.
(struct vn_walk_cb_data): Add data to track partial definitions.
(vn_walk_cb_data::~vn_walk_cb_data): New.
(vn_walk_cb_data::push_partial_def): New.
(pd_tree_alloc, pd_tree_dealloc, pd_range_compare): New.
(vn_reference_lookup_2): When partial defs are registered give up.
(vn_reference_lookup_3): Track partial defs for memset and
constructor zeroing and for defs from constants.
* gcc.dg/tree-ssa/ssa-fre-73.c: New testcase.
* gcc.dg/tree-ssa/ssa-fre-74.c: Likewise.
* gcc.dg/tree-ssa/ssa-fre-75.c: Likewise.
* gcc.dg/tree-ssa/ssa-fre-76.c: Likewise.
* g++.dg/tree-ssa/pr83518.C: Likewise.
Added:
trunk/gcc/testsuite/g++.dg/tree-ssa/pr83518.C
trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-73.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-74.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-75.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-76.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-sccvn.c
>From gcc-bugs-return-648431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 07:18:36 2019
Return-Path: <gcc-bugs-return-648431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59578 invoked by alias); 8 Jul 2019 07:18: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 59489 invoked by uid 48); 8 Jul 2019 07:18:31 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91060] [10 regression] gcc.c-torture/execute/scal-to-vec1.c fails on armeb-none-linux-gnueabihf since r272843
Date: Mon, 08 Jul 2019 07:18: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: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: component assigned_to
Message-ID: <bug-91060-4-9hUUHfLdXG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00543.txt.bz2
Content-length: 2053
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|middle-end |target
Assignee|rguenth at gcc dot gnu.org |rsandifo at gcc dot gnu.org
--- Comment #11 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #10)
> On Mon, 8 Jul 2019, clyon at gcc dot gnu.org wrote:
>
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
> >
> > --- Comment #8 from Christophe Lyon <clyon at gcc dot gnu.org> ---
> > (In reply to Richard Biener from comment #5)
> > > Hmm, using a cross configured as
> > >
> > > trunk/configure --target=armeb-none-linux-gnueabihf --with-cpu=cortex-a9
> > > --with-fpu=neon-fp16 --enable-languages=c
> > >
> > > and trimming the testcase to the first line I cannot reproduce the reported
> > > assembly. I get at -O3
> > >
> > > .arm
> > > .fpu softvfp
> >
> > For some reason, you are not targeting the right FPU, I have:
> > .arm
> > .fpu neon-fp16
>
> I noticed that - but it doesn't change even when supplying
> -mpfu=neon-fp16 -mcpu=cortex-a9
>
> I suppose some configure-time checking disables this feature somehow
> without notifying me :/ (don't have a armeb assembler installed,
> trying a pure cc1 cross)
>
> Anyway, I can't reproduce even after spending 1+ hours on this.
Yeah, I see the same thing building it that way. I needed to restate
the abi using -mfloat-abi=hard.
I'm pretty sure it's a target bug though. If a vector constructor
has a single nonconstant element, neon_expand_vector_init uses the
neon_vset_lane* patterns to set that index. But neon_vset_lane*
use the architecture lane numbering while neon_expand_vector_init
uses GCC lane numbering. Using the vec_set(_internal) patterns
should fix that.
>From gcc-bugs-return-648432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 08:01:42 2019
Return-Path: <gcc-bugs-return-648432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59836 invoked by alias); 8 Jul 2019 08:01: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 59765 invoked by uid 48); 8 Jul 2019 08:01:38 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 2019 08:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.1.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 everconfirmed
Message-ID: <bug-91101-4-RFoqXdAQMB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00544.txt.bz2
Content-length: 3585
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-07-08
Ever confirmed|0 |1
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Ok, I was able to make the build:
$ meson build -Db_sanitize=address,undefined -Dxkbcommon=false
with GCC 9.1.1:
$ time ./build/test-conf-parser
filename:1: lvalue= path is not absolute, ignoring: not_absolute/path
filename:1: String is not UTF-8 clean, ignoring assignment: /path/�
filename:1: Failed to parse log level, ignoring: garbage
filename:1: Failed to parse log facility, ignoring: garbage
filename:1: Failed to parse size value '-982', ignoring: Numerical result out
of range
filename:1: Failed to parse size value '49874444198739873000000G', ignoring:
Numerical result out of range
filename:1: Failed to parse size value 'garbage', ignoring: Invalid argument
filename:1: Failed to parse size value '-982', ignoring: Numerical result out
of range
filename:1: Failed to parse size value '49874444198739873000000G', ignoring:
Numerical result out of range
filename:1: Failed to parse size value 'garbage', ignoring: Invalid argument
filename:1: Failed to parse int value, ignoring:
99999999999999999999999999999999999999999999999999999999
filename:1: Failed to parse int value, ignoring:
-99999999999999999999999999999999999999999999999999999999
filename:1: Failed to parse int value, ignoring: 1G
filename:1: Failed to parse int value, ignoring: garbage
filename:1: Failed to parse unsigned value, ignoring:
99999999999999999999999999999999999999999999999999999999
filename:1: Failed to parse unsigned value, ignoring: 1G
filename:1: Failed to parse unsigned value, ignoring: garbage
filename:1: Failed to parse unsigned value, ignoring: 1000garbage
filename:1: Failed to parse mode value, ignoring: -777
filename:1: Failed to parse mode value, ignoring: 999
filename:1: Failed to parse mode value, ignoring: garbage
filename:1: Failed to parse mode value, ignoring: 777garbage
filename:1: Failed to parse mode value, ignoring: 777 garbage
filename:1: Failed to parse sec value, ignoring: -1
filename:1: Failed to parse sec value, ignoring: 10foo
filename:1: Failed to parse sec value, ignoring: garbage
filename:1: Failed to parse nsec value, ignoring: -1
filename:1: Failed to parse nsec value, ignoring: 10foo
filename:1: Failed to parse nsec value, ignoring: garbage
== test_config_parse[0] ==
== test_config_parse[1] ==
== test_config_parse[2] ==
== test_config_parse[3] ==
== test_config_parse[4] ==
== test_config_parse[5] ==
== test_config_parse[6] ==
== test_config_parse[7] ==
== test_config_parse[8] ==
== test_config_parse[9] ==
== test_config_parse[10] ==
== test_config_parse[11] ==
== test_config_parse[12] ==
== test_config_parse[13] ==
== test_config_parse[14] ==
== test_config_parse[15] ==
/tmp/test-conf-parser.l7EgI7:1: Line too long
== test_config_parse[16] ==
/tmp/test-conf-parser.2Fj9TE:1: Continuation line too long
real 0m2.176s
user 0m2.013s
sys 0m0.160s
which is probably fast enough. And I can't run the second test-case:
$ ./test/hwdb-test.sh
./systemd-hwdb does not exist, please build first
>From gcc-bugs-return-648433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 08:20:19 2019
Return-Path: <gcc-bugs-return-648433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7058 invoked by alias); 8 Jul 2019 08:20: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 6541 invoked by uid 48); 8 Jul 2019 08:20:14 -0000
From: "frantisek at sumsal dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 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: sanitizer
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frantisek at sumsal dot cz
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-91101-4-zmp8jaP4np@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00545.txt.bz2
Content-length: 1292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #5 from Frantisek Sumsal <frantisek at sumsal dot cz> ---
(In reply to Martin Liška from comment #4)
> Ok, I was able to make the build:
>
> $ meson build -Db_sanitize=address,undefined -Dxkbcommon=false
>
> with GCC 9.1.1:
>
> real 0m2.176s
> user 0m2.013s
> sys 0m0.160s
>
> which is probably fast enough. And I can't run the second test-case:
>
Yes, without any ASAN_OPTIONS the built binary behaves as "expected:
---
$ unset ASAN_OPTIONS
$ time build-gcc-9.1.0-sanitizers/test-conf-parser
<...snip...>
= test_config_parse[16] ==
/tmp/test-conf-parser.cvqFVQ:1: Continuation line too long
real 0m2.972s
user 0m2.680s
sys 0m0.280s
---
The real issue arises with ASAN_OPTIONS=detect_stack_use_after_return=1
---
$ export ASAN_OPTIONS=detect_stack_use_after_return=1
$ time build-gcc-9.1.0-sanitizers/test-conf-parser
<...snip...>
== test_config_parse[16] ==
/tmp/test-conf-parser.WhLgS1:1: Continuation line too long
real 0m29.637s
user 0m29.321s
sys 0m0.298s
---
> $ ./test/hwdb-test.sh
> ./systemd-hwdb does not exist, please build first
For this particular case you have to cd into the build directory first (cd
build && ../test/hwdb-test.sh)
>From gcc-bugs-return-648434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 08:25:38 2019
Return-Path: <gcc-bugs-return-648434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29151 invoked by alias); 8 Jul 2019 08:25: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 29040 invoked by uid 55); 8 Jul 2019 08:25:32 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/84877] Local stack copy of BLKmode parameter on the stack is not aligned when the requested alignment exceeds MAX_SUPPORTED_STACK_ALIGNMENT
Date: Mon, 08 Jul 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: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84877-4-SbUOPnJWGQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00546.txt.bz2
Content-length: 2470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84877
--- Comment #17 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #15 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> ---
> Created attachment 46574
> --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46574&action=edit
> patch for the case that the stack is sufficiently aligned
[...]
> I have attached a patch to preserve the alignment of the passed type for the
> case that the stack is already sufficiently aligned.
This patch breaks sparc-sun-solaris2.11 bootstrap with an ICE while
compiling stage2 function.c:
during RTL pass: expand
/vol/gcc/src/hg/trunk/local/gcc/function.c: In function 'void
assign_parm_find_data_types(assign_parm_data_all*, tree,
assign_parm_data_one*)':
/vol/gcc/src/hg/trunk/local/gcc/function.c:2426:49: internal compiler error: in
assign_stack_temp_for_type, at function.c:880
2426 | else if (targetm.calls.strict_argument_naming (all->args_so_far))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
0x11bc22f assign_stack_temp_for_type(machine_mode, poly_int<1u, long long>,
tree_node*)
/vol/gcc/src/hg/trunk/local/gcc/function.c:878
0x11bc963 assign_temp(tree_node*, int, int)
/vol/gcc/src/hg/trunk/local/gcc/function.c:1016
0xeab99b initialize_argument_information
/vol/gcc/src/hg/trunk/local/gcc/calls.c:2087
0xeb1957 expand_call(tree_node*, rtx_def*, int)
/vol/gcc/src/hg/trunk/local/gcc/calls.c:3605
0x112a247 expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
/vol/gcc/src/hg/trunk/local/gcc/expr.c:11044
0x111919b expand_expr_real(tree_node*, rtx_def*, machine_mode, expand_modifier,
rtx_def**, bool)
/vol/gcc/src/hg/trunk/local/gcc/expr.c:8286
0x110a06b store_expr(tree_node*, rtx_def*, int, bool, bool)
/vol/gcc/src/hg/trunk/local/gcc/expr.c:5685
0x11085bf expand_assignment(tree_node*, tree_node*, bool)
/vol/gcc/src/hg/trunk/local/gcc/expr.c:5447
0xed8cb3 expand_call_stmt
/vol/gcc/src/hg/trunk/local/gcc/cfgexpand.c:2727
0xedd453 expand_gimple_stmt_1
/vol/gcc/src/hg/trunk/local/gcc/cfgexpand.c:3708
0xedde3b expand_gimple_stmt
/vol/gcc/src/hg/trunk/local/gcc/cfgexpand.c:3867
0xee937f expand_gimple_basic_block
/vol/gcc/src/hg/trunk/local/gcc/cfgexpand.c:5907
0xeeb7c3 execute
/vol/gcc/src/hg/trunk/local/gcc/cfgexpand.c:6530
>From gcc-bugs-return-648435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 08:35:54 2019
Return-Path: <gcc-bugs-return-648435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52946 invoked by alias); 8 Jul 2019 08:35: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 52889 invoked by uid 55); 8 Jul 2019 08:35:49 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91060] [10 regression] gcc.c-torture/execute/scal-to-vec1.c fails on armeb-none-linux-gnueabihf since r272843
Date: Mon, 08 Jul 2019 08: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: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91060-4-vDyost5Gf2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00547.txt.bz2
Content-length: 2433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
--- Comment #12 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 8 Jul 2019, rsandifo at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
>
> rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Component|middle-end |target
> Assignee|rguenth at gcc dot gnu.org |rsandifo at gcc dot gnu.org
>
> --- Comment #11 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
> (In reply to rguenther@suse.de from comment #10)
> > On Mon, 8 Jul 2019, clyon at gcc dot gnu.org wrote:
> >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
> > >
> > > --- Comment #8 from Christophe Lyon <clyon at gcc dot gnu.org> ---
> > > (In reply to Richard Biener from comment #5)
> > > > Hmm, using a cross configured as
> > > >
> > > > trunk/configure --target=armeb-none-linux-gnueabihf --with-cpu=cortex-a9
> > > > --with-fpu=neon-fp16 --enable-languages=c
> > > >
> > > > and trimming the testcase to the first line I cannot reproduce the reported
> > > > assembly. I get at -O3
> > > >
> > > > .arm
> > > > .fpu softvfp
> > >
> > > For some reason, you are not targeting the right FPU, I have:
> > > .arm
> > > .fpu neon-fp16
> >
> > I noticed that - but it doesn't change even when supplying
> > -mpfu=neon-fp16 -mcpu=cortex-a9
> >
> > I suppose some configure-time checking disables this feature somehow
> > without notifying me :/ (don't have a armeb assembler installed,
> > trying a pure cc1 cross)
> >
> > Anyway, I can't reproduce even after spending 1+ hours on this.
>
> Yeah, I see the same thing building it that way. I needed to restate
> the abi using -mfloat-abi=hard.
Even when adding -mfloat-abi=hard I see .fpu softvfp ...
> I'm pretty sure it's a target bug though. If a vector constructor
> has a single nonconstant element, neon_expand_vector_init uses the
> neon_vset_lane* patterns to set that index. But neon_vset_lane*
> use the architecture lane numbering while neon_expand_vector_init
> uses GCC lane numbering. Using the vec_set(_internal) patterns
> should fix that.
I'm out of here then ;)
>From gcc-bugs-return-648436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 08:39:49 2019
Return-Path: <gcc-bugs-return-648436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69093 invoked by alias); 8 Jul 2019 08:39: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 69039 invoked by uid 48); 8 Jul 2019 08:39:46 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 2019 08:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.1.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:
Message-ID: <bug-91101-4-BeynV0uAga@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00548.txt.bz2
Content-length: 1552
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Frantisek Sumsal from comment #5)
> (In reply to Martin Liška from comment #4)
> > Ok, I was able to make the build:
> >
> > $ meson build -Db_sanitize=address,undefined -Dxkbcommon=false
> >
> > with GCC 9.1.1:
> >
> > real 0m2.176s
> > user 0m2.013s
> > sys 0m0.160s
> >
> > which is probably fast enough. And I can't run the second test-case:
> >
>
> Yes, without any ASAN_OPTIONS the built binary behaves as "expected:
>
> ---
>
> $ unset ASAN_OPTIONS
> $ time build-gcc-9.1.0-sanitizers/test-conf-parser
> <...snip...>
> = test_config_parse[16] ==
> /tmp/test-conf-parser.cvqFVQ:1: Continuation line too long
>
> real 0m2.972s
> user 0m2.680s
> sys 0m0.280s
>
> ---
>
> The real issue arises with ASAN_OPTIONS=detect_stack_use_after_return=1
Ahh, got it. Now it's really much slower.
Do you know how to tell meson to use CC=gcc-8?
>
> ---
>
> $ export ASAN_OPTIONS=detect_stack_use_after_return=1
> $ time build-gcc-9.1.0-sanitizers/test-conf-parser
> <...snip...>
> == test_config_parse[16] ==
> /tmp/test-conf-parser.WhLgS1:1: Continuation line too long
>
> real 0m29.637s
> user 0m29.321s
> sys 0m0.298s
>
> ---
>
>
> > $ ./test/hwdb-test.sh
> > ./systemd-hwdb does not exist, please build first
>
> For this particular case you have to cd into the build directory first (cd
> build && ../test/hwdb-test.sh)
Good.
>From gcc-bugs-return-648437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 08:39:59 2019
Return-Path: <gcc-bugs-return-648437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69770 invoked by alias); 8 Jul 2019 08:39: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 69722 invoked by uid 48); 8 Jul 2019 08:39:56 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91108] New: [8/9/10 Regression] Fails to pun through unions
Date: Mon, 08 Jul 2019 08:39: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: 9.1.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-91108-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00549.txt.bz2
Content-length: 929
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91108
Bug ID: 91108
Summary: [8/9/10 Regression] Fails to pun through unions
Product: gcc
Version: 9.1.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: ---
The following testcase fails to support our promise for punning through
union members if the access happens through the union.
/* { dg-do run } */
/* { dg-options "-O3 -fstrict-aliasing" } */
union U {
struct A { int : 2; int x : 8; } a;
struct B { int : 6; int x : 8; } b;
};
int __attribute__((noipa))
foo (union U *p, union U *q)
{
p->a.x = 1;
q->b.x = 1;
return p->a.x;
}
int
main()
{
union U x;
if (foo (&x, &x) != x.a.x)
__builtin_abort ();
return 0;
}
>From gcc-bugs-return-648438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 08:40:26 2019
Return-Path: <gcc-bugs-return-648438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70856 invoked by alias); 8 Jul 2019 08:40: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 70532 invoked by uid 48); 8 Jul 2019 08:40:20 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91108] [8/9/10 Regression] Fails to pun through unions
Date: Mon, 08 Jul 2019 08:40: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.1.0
X-Bugzilla-Keywords: alias, 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: P2
X-Bugzilla-Assigned-To: rguenth 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 assigned_to everconfirmed target_milestone
Message-ID: <bug-91108-4-hzbHdRWzRP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91108-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91108-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00550.txt.bz2
Content-length: 796
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91108
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Status|UNCONFIRMED |ASSIGNED
Known to work| |7.4.0
Keywords| |alias, wrong-code
Last reconfirmed| |2019-07-08
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
Target Milestone|--- |8.4
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-648439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 08:41:55 2019
Return-Path: <gcc-bugs-return-648439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72299 invoked by alias); 8 Jul 2019 08:41: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 72242 invoked by uid 48); 8 Jul 2019 08:41:51 -0000
From: "frantisek at sumsal dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 2019 08:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frantisek at sumsal dot cz
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-91101-4-F5t6HL5hYX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00551.txt.bz2
Content-length: 296
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #7 from Frantisek Sumsal <frantisek at sumsal dot cz> ---
(In reply to Martin Liška from comment #6)
> Do you know how to tell meson to use CC=gcc-8?
>
$ export CC=gcc-8 CXX=g++-8
$ meson build ...
should suffice
>From gcc-bugs-return-648440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 08:47:34 2019
Return-Path: <gcc-bugs-return-648440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76309 invoked by alias); 8 Jul 2019 08:47: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 76261 invoked by uid 48); 8 Jul 2019 08:47:29 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91060] [10 regression] gcc.c-torture/execute/scal-to-vec1.c fails on armeb-none-linux-gnueabihf since r272843
Date: Mon, 08 Jul 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: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon 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-91060-4-nEhL49eoEU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00552.txt.bz2
Content-length: 2436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
--- Comment #13 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Indeed, this seems to work:
diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c
index 820502a..4f69122 100644
--- a/gcc/config/arm/arm.c
+++ b/gcc/config/arm/arm.c
@@ -12471,7 +12471,7 @@ neon_expand_vector_init (rtx target, rtx vals)
if (n_var == 1)
{
rtx copy = copy_rtx (vals);
- rtx index = GEN_INT (one_var);
+ rtx index = GEN_INT (1 << one_var);
/* Load constant part of vector, substitute neighboring value for
varying element. */
@@ -12483,31 +12483,40 @@ neon_expand_vector_init (rtx target, rtx vals)
switch (mode)
{
case E_V8QImode:
- emit_insn (gen_neon_vset_lanev8qi (target, x, target, index));
+ emit_insn (gen_vec_setv8qi_internal (target, x, index, target));
break;
case E_V16QImode:
- emit_insn (gen_neon_vset_lanev16qi (target, x, target, index));
+ emit_insn (gen_vec_setv16qi_internal (target, x, index, target));
break;
case E_V4HImode:
- emit_insn (gen_neon_vset_lanev4hi (target, x, target, index));
+ emit_insn (gen_vec_setv4hi_internal (target, x, index, target));
break;
case E_V8HImode:
- emit_insn (gen_neon_vset_lanev8hi (target, x, target, index));
+ emit_insn (gen_vec_setv8hi_internal (target, x, index, target));
break;
case E_V2SImode:
- emit_insn (gen_neon_vset_lanev2si (target, x, target, index));
+ emit_insn (gen_vec_setv2si_internal (target, x, index, target));
break;
case E_V4SImode:
- emit_insn (gen_neon_vset_lanev4si (target, x, target, index));
+ emit_insn (gen_vec_setv4si_internal (target, x, index, target));
break;
case E_V2SFmode:
- emit_insn (gen_neon_vset_lanev2sf (target, x, target, index));
+ emit_insn (gen_vec_setv2sf_internal (target, x, index, target));
break;
case E_V4SFmode:
- emit_insn (gen_neon_vset_lanev4sf (target, x, target, index));
+ emit_insn (gen_vec_setv4sf_internal (target, x, index, target));
break;
case E_V2DImode:
- emit_insn (gen_neon_vset_lanev2di (target, x, target, index));
+ emit_insn (gen_vec_setv2di_internal (target, x, index, target));
break;
>From gcc-bugs-return-648441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 08:50:47 2019
Return-Path: <gcc-bugs-return-648441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102944 invoked by alias); 8 Jul 2019 08: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 102899 invoked by uid 48); 8 Jul 2019 08:50:43 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 2019 08:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.1.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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work cf_known_to_fail
Message-ID: <bug-91101-4-z42xkmkph6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00553.txt.bz2
Content-length: 756
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |ASSIGNED
Known to work| |8.3.1
Known to fail| |9.1.0
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Frantisek Sumsal from comment #7)
> (In reply to Martin Liška from comment #6)
>
> > Do you know how to tell meson to use CC=gcc-8?
> >
>
> $ export CC=gcc-8 CXX=g++-8
> $ meson build ...
>
> should suffice
Great, now I can confirm that!
>From gcc-bugs-return-648442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 09:02:25 2019
Return-Path: <gcc-bugs-return-648442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14260 invoked by alias); 8 Jul 2019 09:02: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 14213 invoked by uid 48); 8 Jul 2019 09:02:21 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91060] [10 regression] gcc.c-torture/execute/scal-to-vec1.c fails on armeb-none-linux-gnueabihf since r272843
Date: Mon, 08 Jul 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: target
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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-91060-4-pPXqjS6gfD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91060-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00554.txt.bz2
Content-length: 289
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91060
--- Comment #14 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Created attachment 46576
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46576&action=edit
Candidate patch
I'll test the attached overnight
>From gcc-bugs-return-648443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 09:23:10 2019
Return-Path: <gcc-bugs-return-648443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33823 invoked by alias); 8 Jul 2019 09:23: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 33778 invoked by uid 48); 8 Jul 2019 09:23:07 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80518] -Wsuggest-override does not warn about missing override on destructor
Date: Mon, 08 Jul 2019 09:23: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.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-80518-4-uMqn7UWYRp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80518-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80518-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00555.txt.bz2
Content-length: 323
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80518
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The guideline might be changing:
https://github.com/isocpp/CppCoreGuidelines/pull/1448
If that pull request is merged we might want to change -Wsuggest-override too,
without needing a separate option.
>From gcc-bugs-return-648444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 09:31:17 2019
Return-Path: <gcc-bugs-return-648444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40479 invoked by alias); 8 Jul 2019 09:31: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 40418 invoked by uid 48); 8 Jul 2019 09:31:13 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91103] AVX512 vector element extract uses more than 1 shuffle instruction; VALIGND can grab any element
Date: Mon, 08 Jul 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: 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: cc
Message-ID: <bug-91103-4-bzbQtsenrI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91103-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91103-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00556.txt.bz2
Content-length: 918
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91103
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
So when the vectorizer has the need to use strided stores it would be cheapest
to spill the vector and do N element loads and stores? I guess we can easily
get bottle-necked by the load/store op bandwith here? That is, the
vectorizer needs
for (lane)
dest[stride * lane] = vector[lane];
thus store a specific (constant) lane of a vector to memory, for each
vector lane. (we could use a scatter store here but only AVX512 has that
and builing the index vector could be tricky and not supported for all
element types)
>From gcc-bugs-return-648445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 09:39:58 2019
Return-Path: <gcc-bugs-return-648445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65525 invoked by alias); 8 Jul 2019 09:39: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 65443 invoked by uid 48); 8 Jul 2019 09:39:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91103] AVX512 vector element extract uses more than 1 shuffle instruction; VALIGND can grab any element
Date: Mon, 08 Jul 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: 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:
Message-ID: <bug-91103-4-Gf69NPKRvd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91103-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91103-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00557.txt.bz2
Content-length: 934
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91103
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> So when the vectorizer has the need to use strided stores it would be
> cheapest
> to spill the vector and do N element loads and stores? I guess we can easily
> get bottle-necked by the load/store op bandwith here? That is, the
> vectorizer needs
>
> for (lane)
> dest[stride * lane] = vector[lane];
>
> thus store a specific (constant) lane of a vector to memory, for each
> vector lane. (we could use a scatter store here but only AVX512 has that
> and builing the index vector could be tricky and not supported for all
> element types)
Indeed ICC seems to spill for AVX and AVX512 for
typedef int vsi __attribute__((vector_size(SIZE)));
void foo (vsi v, int *p, int *o)
{
for (int i = 0; i < sizeof(vsi)/4; ++i)
p[o[i]] = v[i];
}
>From gcc-bugs-return-648446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 09:49:39 2019
Return-Path: <gcc-bugs-return-648446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41285 invoked by alias); 8 Jul 2019 09: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 41248 invoked by uid 48); 8 Jul 2019 09:49:36 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91109] New: [10 regression][arm] gcc.c-torture/execute/20040709-1.c fails since r273135
Date: Mon, 08 Jul 2019 09:49: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-91109-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00558.txt.bz2
Content-length: 826
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91109
Bug ID: 91109
Summary: [10 regression][arm]
gcc.c-torture/execute/20040709-1.c fails since r273135
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: ---
Hi,
I've noticed that since r273135 (fix for PR91091), there is a regression on
arm-none-linux-gnueabi
--with-mode arm
--with-cpu cortex-a9
FAIL: gcc.c-torture/execute/20040709-1.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects execution test
There's no such regression on arm-none-linux-gnueabihf or if using --with-mode
thumb
>From gcc-bugs-return-648447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 09:51:42 2019
Return-Path: <gcc-bugs-return-648447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79909 invoked by alias); 8 Jul 2019 09: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 78387 invoked by uid 55); 8 Jul 2019 09:51:39 -0000
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65143] [C++11] missing devirtualization for virtual base in "final" classes
Date: Mon, 08 Jul 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: c++
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: paolo 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-65143-4-r62d4dGIkk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65143-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65143-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00559.txt.bz2
Content-length: 584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65143
--- Comment #10 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> ---
Author: paolo
Date: Mon Jul 8 09:51:07 2019
New Revision: 273228
URL: https://gcc.gnu.org/viewcvs?rev=273228&root=gcc&view=rev
Log:
2019-07-08 Paolo Carlini <paolo.carlini@oracle.com>
PR c++/65143
* g++.dg/tree-ssa/final2.C: New.
* g++.dg/tree-ssa/final3.C: Likewise.
Added:
trunk/gcc/testsuite/g++.dg/tree-ssa/final2.C
trunk/gcc/testsuite/g++.dg/tree-ssa/final3.C
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-648448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 09:52:29 2019
Return-Path: <gcc-bugs-return-648448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86805 invoked by alias); 8 Jul 2019 09:52: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 86726 invoked by uid 48); 8 Jul 2019 09:52:26 -0000
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65143] [C++11] missing devirtualization for virtual base in "final" classes
Date: Mon, 08 Jul 2019 09: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: 4.9.2
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: paolo.carlini at oracle 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: bug_status resolution target_milestone
Message-ID: <bug-65143-4-V2o0B1RBcr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65143-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65143-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00560.txt.bz2
Content-length: 513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65143
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.0
--- Comment #11 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Should be completely fixed.
>From gcc-bugs-return-648450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 09:56:50 2019
Return-Path: <gcc-bugs-return-648450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91268 invoked by alias); 8 Jul 2019 09:56: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 91238 invoked by uid 48); 8 Jul 2019 09:56:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91105] internal compiler error: maximum number of generated reload insns per insn achieved (90)
Date: Mon, 08 Jul 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: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, ra
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: keywords bug_status cf_reconfirmed_on component everconfirmed cf_known_to_fail
Message-ID: <bug-91105-4-0Lai7wGCmg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91105-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91105-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00562.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91105
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code, ra
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-08
Component|middle-end |target
Ever confirmed|0 |1
Known to fail| |4.8.5, 7.4.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Never worked it seems.
>From gcc-bugs-return-648449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 09:56:18 2019
Return-Path: <gcc-bugs-return-648449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90443 invoked by alias); 8 Jul 2019 09:56: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 90408 invoked by uid 48); 8 Jul 2019 09:56:15 -0000
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66999] Missing comma in lambda capture causes internal compiler error
Date: Mon, 08 Jul 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: c++
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: minor
X-Bugzilla-Who: paolo.carlini at oracle dot com
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: cc
Message-ID: <bug-66999-4-0X0a707TbN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66999-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66999-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00561.txt.bz2
Content-length: 467
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66999
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |paolo.carlini at oracle dot com
--- Comment #6 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Unfortunately we still issue two errors for the original testcase.
>From gcc-bugs-return-648451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 09:58:11 2019
Return-Path: <gcc-bugs-return-648451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92760 invoked by alias); 8 Jul 2019 09:58: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 92724 invoked by uid 48); 8 Jul 2019 09:58:08 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91106] internal compiler error: output_operand: invalid use of register 'frame'
Date: Mon, 08 Jul 2019 09:58: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: 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-91106-4-5rfTBVeFxj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00563.txt.bz2
Content-length: 166
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91106
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Did you paste the correct reduced testcase?
>From gcc-bugs-return-648452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 10:00:49 2019
Return-Path: <gcc-bugs-return-648452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106152 invoked by alias); 8 Jul 2019 10:00: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 104227 invoked by uid 48); 8 Jul 2019 10:00:45 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91107] __attribute__((pure)) to function with non-const pointers
Date: Mon, 08 Jul 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: c
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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-91107-4-PHBRh3RzPf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91107-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91107-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00564.txt.bz2
Content-length: 627
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91107
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
This function isn't pure. GCC would optimize
dest[0] = 0.;
array_division (n, dest, src1, src2);
return dest[0];
to return 0.0 since pure functions are assumed to not write to (global) memory.
>From gcc-bugs-return-648453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 10:03:51 2019
Return-Path: <gcc-bugs-return-648453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123294 invoked by alias); 8 Jul 2019 10:03: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 123270 invoked by uid 48); 8 Jul 2019 10:03:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91109] [10 regression][arm] gcc.c-torture/execute/20040709-1.c fails since r273135
Date: Mon, 08 Jul 2019 10: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: 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-91109-4-297xAmzVli@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91109-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91109-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00565.txt.bz2
Content-length: 629
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91109
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
Target Milestone|--- |10.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Can you help and check which test* () call fails? Also check whether
-fwhole-program instead of -flto makes it fail. Does it still fail when you
comment
all but the failing test* () call?
>From gcc-bugs-return-648454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 10:04:52 2019
Return-Path: <gcc-bugs-return-648454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125053 invoked by alias); 8 Jul 2019 10:04: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 124984 invoked by uid 48); 8 Jul 2019 10:04:48 -0000
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/84877] Local stack copy of BLKmode parameter on the stack is not aligned when the requested alignment exceeds MAX_SUPPORTED_STACK_ALIGNMENT
Date: Mon, 08 Jul 2019 10:04: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amylaar at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-84877-4-tw1BAPYTtq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00566.txt.bz2
Content-length: 2982
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84877
Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #46574|0 |1
is obsolete| |
--- Comment #18 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> ---
Created attachment 46577
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46577&action=edit
patch for aligned stack - but clamping max alignment at
MAX_SUPPORTED_STACK_ALIGNMENT
(In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #17)
> > --- Comment #15 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> ---
> > Created attachment 46574 [details]
> > --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46574&action=edit
> > patch for the case that the stack is sufficiently aligned
> [...]
> > I have attached a patch to preserve the alignment of the passed type for the
> > case that the stack is already sufficiently aligned.
>
> This patch breaks sparc-sun-solaris2.11 bootstrap with an ICE while
> compiling stage2 function.c:
>
> during RTL pass: expand
> /vol/gcc/src/hg/trunk/local/gcc/function.c: In function 'void
> assign_parm_find_data_types(assign_parm_data_all*, tree,
> assign_parm_data_one*)':
> /vol/gcc/src/hg/trunk/local/gcc/function.c:2426:49: internal compiler error:
This location doesn't make much sense to me. Maybe some artefact from
optimized compilation and register windows?
> in assign_stack_temp_for_type, at function.c:880
> 2426 | else if (targetm.calls.strict_argument_naming (all->args_so_far))
> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
> 0x11bc22f assign_stack_temp_for_type(machine_mode, poly_int<1u, long long>,
> tree_node*)
> /vol/gcc/src/hg/trunk/local/gcc/function.c:878
> 0x11bc963 assign_temp(tree_node*, int, int)
This looks like the modified assert there has triggered. It'd be interesting
to know why - i.e. what variable does want more alignment than
MAX_SUPPORTED_STACK_ALIGNMENT - during bootstrap? Or is this a BLKmode
variable with less alignment than BIGGEST_ALIGNMENT?
User code could specify silly alignments which we couldn't provide with
ordinary
allocation (using a fixed offset from sp/fp) and which could also blow up the
frame size too much if we tried, so it makes sense to clamp the alignment to
MAX_SUPPORTED_STACK_ALIGNMENT in get_stack_local_alignment.
The other side is that the code in assign_stack_temp_for_type seems to require
BIGGEST_ALIGNMENT for BLKmode; I'm not sure about assign_stack_local_1
slots. It seems a bit wasteful, but trying to reduce waste of space in the
stack frame is really a different issue, so I also modified the patch to use
at least BIGGEST_ALIGNMENT for BLKmode so that it's (bug-?)compatible in that
aspect with the previous code - see attached modified patch.
>From gcc-bugs-return-648455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 10:08:54 2019
Return-Path: <gcc-bugs-return-648455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127410 invoked by alias); 8 Jul 2019 10:08: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 127374 invoked by uid 48); 8 Jul 2019 10:08:51 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91105] internal compiler error: maximum number of generated reload insns per insn achieved (90)
Date: Mon, 08 Jul 2019 10:08: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: ice-on-valid-code, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak 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: component dependson
Message-ID: <bug-91105-4-8YxcySkCfF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91105-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91105-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00567.txt.bz2
Content-length: 589
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91105
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|target |middle-end
Depends on| |91001
--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
Not a target problem.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91001
[Bug 91001] internal compiler error: in extract_insn, at recog.c:2310
>From gcc-bugs-return-648456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 10:20:51 2019
Return-Path: <gcc-bugs-return-648456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62974 invoked by alias); 8 Jul 2019 10:20: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 62381 invoked by uid 48); 8 Jul 2019 10:20:47 -0000
From: "gsocshubham at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91106] internal compiler error: output_operand: invalid use of register 'frame'
Date: Mon, 08 Jul 2019 10:20: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: gsocshubham 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-91106-4-IHI6bF7LAC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00568.txt.bz2
Content-length: 524
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91106
--- Comment #2 from Shubham Narlawar <gsocshubham at gmail dot com> ---
(In reply to Richard Biener from comment #1)
> Did you paste the correct reduced testcase?
Here is the original reduced test case obtained from Creduce -
#pragma pack(1)
struct a {
int b;
char c
};
union {
struct a b
} __attribute__((aligned(32), transparent_union)) d;
e() { f(d); }
I tried to fix warnings by putting semicolon, data type and function
declaration where ever required.
>From gcc-bugs-return-648457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 10:48:58 2019
Return-Path: <gcc-bugs-return-648457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107816 invoked by alias); 8 Jul 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 107748 invoked by uid 48); 8 Jul 2019 10:48:53 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91110] New: [10 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in cp_omp_mappable_type_1, at cp/decl2.c:1421
Date: Mon, 08 Jul 2019 10:48: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: error-recovery, ice-on-invalid-code, openmp
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-91110-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00569.txt.bz2
Content-length: 4769
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91110
Bug ID: 91110
Summary: [10 Regression] ICE: tree check: expected class
'type', have 'exceptional' (error_mark) in
cp_omp_mappable_type_1, at cp/decl2.c:1421
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: error-recovery, ice-on-invalid-code, openmp
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-alpha20190707 snapshot (r273184) ICEs when compiling the following
testcase derived from gcc/testsuite/gcc.dg/gomp/_Atomic-5.c w/ -fopenmp:
void
f1 (void)
{
X int b[2];
b[0] = 1;
#pragma omp target map(to: b)
;
}
% g++-10.0.0-alpha20190707 -fopenmp -c e8gxtyxe.c
e8gxtyxe.c: In function 'void f1()':
e8gxtyxe.c:4:3: error: 'X' was not declared in this scope
4 | X int b[2];
| ^
e8gxtyxe.c:5:3: error: 'b' was not declared in this scope
5 | b[0] = 1;
| ^
e8gxtyxe.c:6:30: error: 'b' does not have a mappable type in 'map' clause
6 | #pragma omp target map(to: b)
| ^
e8gxtyxe.c:6:32: internal compiler error: tree check: expected class 'type',
have 'exceptional' (error_mark) in cp_omp_mappable_type_1, at cp/decl2.c:1421
6 | #pragma omp target map(to: b)
| ^
0x7d125e tree_class_check_failed(tree_node const*, tree_code_class, char
const*, int, char const*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/tree.c:9950
0x5f39fa tree_class_check(tree_node*, tree_code_class, char const*, int, char
const*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/tree.h:3340
0x5f39fa cp_omp_mappable_type_1
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/decl2.c:1421
0xa43c69 finish_omp_clauses(tree_node*, c_omp_region_type)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/semantics.c:7241
0x9b3267 cp_parser_omp_all_clauses
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:35735
0x9c4146 cp_parser_omp_target
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:38918
0x99f583 cp_parser_pragma
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:41352
0x9a76fd cp_parser_statement
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:11279
0x9a8665 cp_parser_statement_seq_opt
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:11667
0x9a8735 cp_parser_compound_statement
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:11621
0x9c0cbc cp_parser_function_body
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:22651
0x9c0cbc cp_parser_ctor_initializer_opt_and_function_body
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:22702
0x9c15ad cp_parser_function_definition_after_declarator
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:28016
0x9c23a3 cp_parser_function_definition_from_specifiers_and_declarator
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:27932
0x9c23a3 cp_parser_init_declarator
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:20288
0x9a4e7d cp_parser_simple_declaration
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:13546
0x9c8822 cp_parser_declaration
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:13243
0x9c8eb8 cp_parser_translation_unit
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:4699
0x9c8eb8 c_parse_file()
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/cp/parser.c:41495
0xad25ec c_common_parse_file()
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/c-family/c-opts.c:1160
>From gcc-bugs-return-648458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 10:51:23 2019
Return-Path: <gcc-bugs-return-648458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70216 invoked by alias); 8 Jul 2019 10:51: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 65099 invoked by uid 48); 8 Jul 2019 10:51:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91103] AVX512 vector element extract uses more than 1 shuffle instruction; VALIGND can grab any element
Date: Mon, 08 Jul 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: 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-91103-4-a1dSjzT6EC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91103-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91103-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00570.txt.bz2
Content-length: 3586
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91103
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl.tools at gmail dot com,
| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
For the constant vector element extraction, it can be done say with:
--- gcc/config/i386/sse.md.jj 2019-07-06 23:55:51.617641994 +0200
+++ gcc/config/i386/sse.md 2019-07-08 12:23:13.315509840 +0200
@@ -9351,7 +9351,7 @@ (define_insn "avx512f_sgetexp<mode><mask
[(set_attr "prefix" "evex")
(set_attr "mode" "<ssescalarmode>")])
-(define_insn "<mask_codefor><avx512>_align<mode><mask_name>"
+(define_insn "<avx512>_align<mode><mask_name>"
[(set (match_operand:VI48_AVX512VL 0 "register_operand" "=v")
(unspec:VI48_AVX512VL [(match_operand:VI48_AVX512VL 1
"register_operand" "v")
(match_operand:VI48_AVX512VL 2
"nonimmediate_operand" "vm")
--- gcc/config/i386/i386-expand.c.jj 2019-07-04 00:18:37.067010375 +0200
+++ gcc/config/i386/i386-expand.c 2019-07-08 12:37:24.687562956 +0200
@@ -14827,6 +14827,14 @@ ix86_expand_vector_extract (bool mmx_ok,
break;
case E_V16SFmode:
+ if (elt > 12)
+ {
+ tmp = gen_reg_rtx (V16SImode);
+ vec = gen_lowpart (V16SImode, vec);
+ emit_insn (gen_avx512f_alignv16si (tmp, vec, vec, GEN_INT (elt)));
+ vec = gen_lowpart (V16SFmode, tmp);
+ elt = 0;
+ }
tmp = gen_reg_rtx (V8SFmode);
if (elt < 8)
emit_insn (gen_vec_extract_lo_v16sf (tmp, vec));
@@ -14836,6 +14844,14 @@ ix86_expand_vector_extract (bool mmx_ok,
return;
case E_V8DFmode:
+ if (elt >= 6)
+ {
+ tmp = gen_reg_rtx (V8DImode);
+ vec = gen_lowpart (V8DImode, vec);
+ emit_insn (gen_avx512f_alignv8di (tmp, vec, vec, GEN_INT (elt)));
+ vec = gen_lowpart (V8DFmode, tmp);
+ elt = 0;
+ }
tmp = gen_reg_rtx (V4DFmode);
if (elt < 4)
emit_insn (gen_vec_extract_lo_v8df (tmp, vec));
@@ -14845,6 +14861,13 @@ ix86_expand_vector_extract (bool mmx_ok,
return;
case E_V16SImode:
+ if (elt > 12)
+ {
+ tmp = gen_reg_rtx (V16SImode);
+ emit_insn (gen_avx512f_alignv16si (tmp, vec, vec, GEN_INT (elt)));
+ vec = tmp;
+ elt = 0;
+ }
tmp = gen_reg_rtx (V8SImode);
if (elt < 8)
emit_insn (gen_vec_extract_lo_v16si (tmp, vec));
@@ -14854,6 +14877,13 @@ ix86_expand_vector_extract (bool mmx_ok,
return;
case E_V8DImode:
+ if (elt >= 6)
+ {
+ tmp = gen_reg_rtx (V8DImode);
+ emit_insn (gen_avx512f_alignv8di (tmp, vec, vec, GEN_INT (elt)));
+ vec = tmp;
+ elt = 0;
+ }
tmp = gen_reg_rtx (V4DImode);
if (elt < 4)
emit_insn (gen_vec_extract_lo_v8di (tmp, vec));
The question is in which cases it is beneficial, from pure -Os POV the
valignd/valignq is one instruction and for integer extractions needs a vmovd
afterwards,
so for 64-bit extraction might be also useful for double [3] and [5] (for long
long it is two insns in both cases), for 32-bit extraction
likely also shorter for float [5], [6], [7], [9], [10], [11], [12], but not for
int.
But I admit I have no idea on how fast what is.
>From gcc-bugs-return-648459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 10:57:27 2019
Return-Path: <gcc-bugs-return-648459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106220 invoked by alias); 8 Jul 2019 10:57: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 106183 invoked by uid 48); 8 Jul 2019 10:57:22 -0000
From: "will.deacon at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/91111] New: arm64 Linux kernel panics at boot due to unexpected register assignment in inline asm
Date: Mon, 08 Jul 2019 10:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: will.deacon at arm 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-91111-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00571.txt.bz2
Content-length: 5507
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91111
Bug ID: 91111
Summary: arm64 Linux kernel panics at boot due to unexpected
register assignment in inline asm
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: inline-asm
Assignee: unassigned at gcc dot gnu.org
Reporter: will.deacon at arm dot com
Target Milestone: ---
Created attachment 46578
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46578&action=edit
Output of -save-temps
When compiling the Linux kernel for arm64 with CONFIG_OPTIMIZE_INLINING=y
(which effectively removes the use of __attribute__((__always_inline__)) for
functions marked as inline), the atomic64 selftest fails due to a local
register variable being assigned to a different register from the one specified
when used in an inline asm block.
While I appreciate that we're treading on thin ice here, my reading of the
docs at:
https://gcc.gnu.org/onlinedocs/gcc/Local-Register-Variables.html#Local-Register-Variables
suggests that this should work.
To be more precise, this kernel code:
static inline long arch_atomic64_dec_if_positive(atomic64_t *v)
{
register long x0 asm ("x0") = (long)v;
asm volatile(ARM64_LSE_ATOMIC_INSN(
/* LL/SC */
__LL_SC_ATOMIC64(dec_if_positive)
__nops(6),
/* LSE atomics */
"1: ldr x30, %[v]\n"
" subs %[ret], x30, #1\n"
" b.lt 2f\n"
" casal x30, %[ret], %[v]\n"
" sub x30, x30, #1\n"
" sub x30, x30, %[ret]\n"
" cbnz x30, 1b\n"
"2:")
: [ret] "+&r" (x0), [v] "+Q" (v->counter)
:
: __LL_SC_CLOBBERS, "cc", "memory");
return x0;
}
requires that %[ret] expands to register x0, whereas it is instead expanding to
register x1. You can see this in the assembly code for the function:
.align 2
.type arch_atomic64_dec_if_positive, %function
arch_atomic64_dec_if_positive:
.LVL0:
.LFB244:
.file 1 "./arch/arm64/include/asm/atomic_lse.h"
.loc 1 411 1 view -0
.cfi_startproc
.loc 1 412 2 view .LVU1
.loc 1 414 2 view .LVU2
.loc 1 411 1 is_stmt 0 view .LVU3
stp x29, x30, [sp, -16]!
.cfi_def_cfa_offset 16
.cfi_offset 29, -16
.cfi_offset 30, -8
.LVL1:
.loc 1 414 2 view .LVU4
mov x1, x0
.loc 1 411 1 view .LVU5
mov x29, sp
.loc 1 414 2 view .LVU6
#APP
// 414 "./arch/arm64/include/asm/atomic_lse.h" 1
.if 1 == 1
661:
bl __ll_sc_arch_atomic64_dec_if_positive
.rept 6
nop
.endr
662:
.pushsection .altinstructions,"a"
.word 661b - .
.if 0 == 0
.word 663f - .
.else
.word 0- .
.endif
.hword 5
.byte 662b-661b
.byte 664f-663f
.popsection
.if 0 == 0
.pushsection .altinstr_replacement, "a"
663:
1: ldr x30, [x0]
subs x1, x30, #1
b.lt 2f
casal x30, x1, [x0]
sub x30, x30, #1
sub x30, x30, x1
cbnz x30, 1b
2:
664:
.popsection
.org . - (664b-663b) + (662b-661b)
.org . - (662b-661b) + (664b-663b)
.else
663:
664:
.endif
.endif
// 0 "" 2
.LVL2:
.loc 1 414 2 view .LVU7
#NO_APP
mov x0, x1
.LVL3:
.loc 1 431 2 is_stmt 1 view .LVU8
.loc 1 432 1 is_stmt 0 view .LVU9
ldp x29, x30, [sp], 16
.cfi_restore 30
.cfi_restore 29
.cfi_def_cfa_offset 0
ret
.cfi_endproc
.LFE244:
.size arch_atomic64_dec_if_positive, .-arch_atomic64_dec_if_positive
I've attached the .i/.s files output by:
aarch64-linux-gnu-gcc -save-temps -Wp,-MD,lib/.atomic64_test.o.d -nostdinc
-isystem
/home/will/system/aarch64/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu/bin/../lib/gcc/aarch64-linux-gnu/8.3.0/include
-I./arch/arm64/include -I./arch/arm64/include/generated -I./include
-I./arch/arm64/include/uapi -I./arch/arm64/include/generated/uapi
-I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h
-include ./include/linux/compiler_types.h -D__KERNEL__ -mlittle-endian
-DKASAN_SHADOW_SCALE_SHIFT=3 -Wall -Wundef -Werror=strict-prototypes
-Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE
-Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security
-std=gnu89 -mgeneral-regs-only -DCONFIG_AS_LSE=1
-fno-asynchronous-unwind-tables -Wno-psabi -mabi=lp64
-DKASAN_SHADOW_SCALE_SHIFT=3 -fno-delete-null-pointer-checks -Wno-frame-address
-Wno-format-truncation -Wno-format-overflow -O2
--param=allow-store-data-races=0 -Wframe-larger-than=2048
-fstack-protector-strong -Wno-unused-but-set-variable
-Wno-unused-const-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls
-fno-var-tracking-assignments -g -Wdeclaration-after-statement -Wvla
-Wno-pointer-sign -Wno-stringop-truncation -fno-strict-overflow
-fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack
-Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init
-fmacro-prefix-map=./= -Wno-packed-not-aligned
-DKBUILD_BASENAME='"atomic64_test"' -DKBUILD_MODNAME='"atomic64_test"' -c -o
lib/atomic64_test.o lib/atomic64_test.c
>From gcc-bugs-return-648460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 11:25:20 2019
Return-Path: <gcc-bugs-return-648460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61738 invoked by alias); 8 Jul 2019 11:25: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 61329 invoked by uid 48); 8 Jul 2019 11:24:43 -0000
From: "stefan.kneifel at bluewin dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91102] [9/10 Regression] aarch64 ICE on Linux kernel with -Os starting with r270266
Date: Mon, 08 Jul 2019 11: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: 9.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: stefan.kneifel at bluewin dot ch
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91102-4-ABEHxmOIlD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00572.txt.bz2
Content-length: 268
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91102
--- Comment #6 from Stefan Kneifel <stefan.kneifel at bluewin dot ch> ---
It seems to fix the bug - at least the original problem (ICE during compiling
Linux kernel for aarch64 with -Os) is solved by this patch.
>From gcc-bugs-return-648461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 11:25:25 2019
Return-Path: <gcc-bugs-return-648461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62206 invoked by alias); 8 Jul 2019 11:25: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 61745 invoked by uid 48); 8 Jul 2019 11:25:14 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91110] [10 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in cp_omp_mappable_type_1, at cp/decl2.c:1421
Date: Mon, 08 Jul 2019 11: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: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to target_milestone everconfirmed
Message-ID: <bug-91110-4-1o5Rhgxff1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91110-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91110-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00573.txt.bz2
Content-length: 714
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91110
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-07-08
CC| |jakub at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Most likely caused by r273078.
>From gcc-bugs-return-648462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 11:26:10 2019
Return-Path: <gcc-bugs-return-648462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63237 invoked by alias); 8 Jul 2019 11:26: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 63196 invoked by uid 48); 8 Jul 2019 11:26:06 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/91111] arm64 Linux kernel panics at boot due to unexpected register assignment in inline asm
Date: Mon, 08 Jul 2019 11:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov 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_gcctarget bug_status cf_known_to_work keywords cf_reconfirmed_on cc everconfirmed cf_known_to_fail
Message-ID: <bug-91111-4-WUSTwcH2Uf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91111-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91111-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00574.txt.bz2
Content-length: 849
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91111
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |aarch64
Status|UNCONFIRMED |NEW
Known to work| |10.0, 9.1.0
Keywords| |wrong-code
Last reconfirmed| |2019-07-08
CC| |ktkachov at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |6.5.0, 7.4.1, 8.3.1
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Hmm, I see this using x0 properly on GCC 9.1 and trunk but GCC 8 and earlier
use x1
>From gcc-bugs-return-648463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 11:34:31 2019
Return-Path: <gcc-bugs-return-648463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75154 invoked by alias); 8 Jul 2019 11: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 75123 invoked by uid 48); 8 Jul 2019 11:34:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91110] [10 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in cp_omp_mappable_type_1, at cp/decl2.c:1421
Date: Mon, 08 Jul 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: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-91110-4-aYLC6NgV9l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91110-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91110-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00575.txt.bz2
Content-length: 551
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91110
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 46579
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46579&action=edit
gcc10-pr91110.patch
error_mark_node type doesn't have TYPE_MAIN_DECL, but more importantly,
error_mark_node on a type doesn't mean the type is incomplete, it means the
type is invalid, and some diagnostics should have been emitted already why it
is invalid. So, IMNSHO we shouldn't emit any clarification messages in that
case.
>From gcc-bugs-return-648464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 11:34:40 2019
Return-Path: <gcc-bugs-return-648464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75857 invoked by alias); 8 Jul 2019 11:34: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 75795 invoked by uid 55); 8 Jul 2019 11:34:36 -0000
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/84877] Local stack copy of BLKmode parameter on the stack is not aligned when the requested alignment exceeds MAX_SUPPORTED_STACK_ALIGNMENT
Date: Mon, 08 Jul 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: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dave.anglin at bell dot net
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84877-4-b8swi0PJyb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00576.txt.bz2
Content-length: 1048
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84877
--- Comment #19 from dave.anglin at bell dot net ---
On 2019-07-07 8:39 p.m., amylaar at gcc dot gnu.org wrote:
> It seems suspicious that PREFERRED_STACK_BOUNDARY is smaller for TARGET_64BIT ?
That's the way HP defined things. The preferred stack boundary for 32-bit code
was
larger than it needed to be. Possibly, someone thought that making it cache
aligned
would be good.
>
> Be this as it may, the problem for the 84877 testcase is not that the stack has
> insufficient alignment, but that the stack slot doesn't have an aligned offset.
>
> The alignment gets pruned in function.c:get_stack_local_alignment :
>
> if (mode == BLKmode)
> alignment = BIGGEST_ALIGNMENT;
>
> I have attached a patch to preserve the alignment of the passed type for the
> case that the stack is already sufficiently aligned.
>
> To test the case where the stack is insufficiently aligned, for hppa we should
> use a different testcase with > 512 bit alignment of the type.
>From gcc-bugs-return-648465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 11:46:31 2019
Return-Path: <gcc-bugs-return-648465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107879 invoked by alias); 8 Jul 2019 11:46: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 107620 invoked by uid 48); 8 Jul 2019 11:46:26 -0000
From: "colomar.6.4.3 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91107] __attribute__((pure)) to function with non-const pointers
Date: Mon, 08 Jul 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: c
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: colomar.6.4.3 at gmail 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-91107-4-wyYyErF7nM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91107-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91107-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00577.txt.bz2
Content-length: 777
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91107
--- Comment #2 from Alejandro Colomar <colomar.6.4.3 at gmail dot com> ---
Technically it can modify globals as long as that doesn't affect the state of
the program, but in this case it is affecting the state of the program, so it
isn't a pure function.
Fair enough, then the bug claim is that GCC shouldn't allow functions accepting
non-const pointers.
--- Comment #3 from Alejandro Colomar <colomar.6.4.3 at gmail dot com> ---
Technically it can modify globals as long as that doesn't affect the state of
the program, but in this case it is affecting the state of the program, so it
isn't a pure function.
Fair enough, then the bug claim is that GCC shouldn't allow functions accepting
non-const pointers.
>From gcc-bugs-return-648466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 11:46:31 2019
Return-Path: <gcc-bugs-return-648466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107884 invoked by alias); 8 Jul 2019 11:46: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 107624 invoked by uid 48); 8 Jul 2019 11:46:27 -0000
From: "colomar.6.4.3 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91107] __attribute__((pure)) to function with non-const pointers
Date: Mon, 08 Jul 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: c
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: colomar.6.4.3 at gmail 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-91107-4-D9Wr2iOegl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91107-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91107-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00578.txt.bz2
Content-length: 777
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91107
--- Comment #2 from Alejandro Colomar <colomar.6.4.3 at gmail dot com> ---
Technically it can modify globals as long as that doesn't affect the state of
the program, but in this case it is affecting the state of the program, so it
isn't a pure function.
Fair enough, then the bug claim is that GCC shouldn't allow functions accepting
non-const pointers.
--- Comment #3 from Alejandro Colomar <colomar.6.4.3 at gmail dot com> ---
Technically it can modify globals as long as that doesn't affect the state of
the program, but in this case it is affecting the state of the program, so it
isn't a pure function.
Fair enough, then the bug claim is that GCC shouldn't allow functions accepting
non-const pointers.
>From gcc-bugs-return-648467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 11:47:06 2019
Return-Path: <gcc-bugs-return-648467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109654 invoked by alias); 8 Jul 2019 11:47: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 109604 invoked by uid 55); 8 Jul 2019 11:47:02 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91108] [8/9/10 Regression] Fails to pun through unions
Date: Mon, 08 Jul 2019 11: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: 9.1.0
X-Bugzilla-Keywords: alias, 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: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91108-4-7FR9YhVAm7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91108-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91108-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00579.txt.bz2
Content-length: 809
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91108
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Mon Jul 8 11:46:26 2019
New Revision: 273232
URL: https://gcc.gnu.org/viewcvs?rev=273232&root=gcc&view=rev
Log:
2019-07-08 Richard Biener <rguenther@suse.de>
PR tree-optimization/91108
* tree-ssa-sccvn.c: Include builtins.h.
(vn_reference_lookup_3): Use only alignment constraints to
verify same-valued store disambiguation.
* gcc.dg/tree-ssa/ssa-fre-61.c: Adjust back.
* gcc.dg/tree-ssa/ssa-fre-78.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-78.c
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-61.c
trunk/gcc/tree-ssa-sccvn.c
>From gcc-bugs-return-648468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 11:49:39 2019
Return-Path: <gcc-bugs-return-648468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111989 invoked by alias); 8 Jul 2019 11:49: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 111941 invoked by uid 55); 8 Jul 2019 11:49:35 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91108] [8/9/10 Regression] Fails to pun through unions
Date: Mon, 08 Jul 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: tree-optimization
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: alias, 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: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91108-4-44Yny77vg7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91108-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91108-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00580.txt.bz2
Content-length: 908
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91108
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Mon Jul 8 11:48:48 2019
New Revision: 273233
URL: https://gcc.gnu.org/viewcvs?rev=273233&root=gcc&view=rev
Log:
2019-07-08 Richard Biener <rguenther@suse.de>
PR tree-optimization/91108
* tree-ssa-sccvn.c: Include builtins.h.
(vn_reference_lookup_3): Use only alignment constraints to
verify same-valued store disambiguation.
* gcc.dg/tree-ssa/pr91091-1.c: New testcase.
* gcc.dg/tree-ssa/ssa-fre-78.c: Likewise.
Added:
branches/gcc-9-branch/gcc/testsuite/gcc.dg/tree-ssa/pr91091-1.c
branches/gcc-9-branch/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-78.c
Modified:
branches/gcc-9-branch/gcc/ChangeLog
branches/gcc-9-branch/gcc/testsuite/ChangeLog
branches/gcc-9-branch/gcc/tree-ssa-sccvn.c
>From gcc-bugs-return-648469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 11:51:07 2019
Return-Path: <gcc-bugs-return-648469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115329 invoked by alias); 8 Jul 2019 11:51: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 115279 invoked by uid 48); 8 Jul 2019 11:51:03 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83518] [8/9 Regression] Missing optimization: useless instructions should be dropped
Date: Mon, 08 Jul 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: tree-optimization
X-Bugzilla-Version: 8.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: P2
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_known_to_work resolution short_desc cf_known_to_fail
Message-ID: <bug-83518-4-4UORIX5vG7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83518-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83518-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00581.txt.bz2
Content-length: 860
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Known to work| |10.0
Resolution|--- |FIXED
Summary|[8/9/10 Regression] Missing |[8/9 Regression] Missing
|optimization: useless |optimization: useless
|instructions should be |instructions should be
|dropped |dropped
Known to fail| |8.3.0, 9.1.0
--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk, not something for backporting.
>From gcc-bugs-return-648470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 11:52:30 2019
Return-Path: <gcc-bugs-return-648470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116562 invoked by alias); 8 Jul 2019 11:52: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 116514 invoked by uid 48); 8 Jul 2019 11:52:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91059] [10 regression] gcc.c-torture/execute/builtins/snprintf-chk.c fails on aarch64-elf since r272843
Date: Mon, 08 Jul 2019 11: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: wrong-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: component
Message-ID: <bug-91059-4-rRGZqaP8kW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00582.txt.bz2
Content-length: 427
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91059
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|tree-optimization |target
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Likely target issue - please aarch64 folks investigate first.
>From gcc-bugs-return-648471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 11:53:16 2019
Return-Path: <gcc-bugs-return-648471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117486 invoked by alias); 8 Jul 2019 11:53: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 117408 invoked by uid 48); 8 Jul 2019 11:53:10 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBsdG8vOTA5OTBdIFsxMCBSZWdyZXNzaW9uXSBJQ0U6IGVycm9yOiA=?= =?UTF-8?B?4oCYY29tcG9uZW50X3JlZuKAmSBMSFMgaW4gY2xvYmJlciBzdGF0ZW1lbnQ=?Date: Mon, 08 Jul 2019 11:53: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: 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-90990-4-J1OM02HJEb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90990-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90990-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00583.txt.bz2
Content-length: 605
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90990
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Honza installed a patch.
2019-07-02 Jan Hubicka <jh@suse.cz>
* tree-inline.c (remap_gimple_stmt): Do not subtitute handled
components
to clobber of return value.
>From gcc-bugs-return-648472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 12:19:21 2019
Return-Path: <gcc-bugs-return-648472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16166 invoked by alias); 8 Jul 2019 12:19: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 16145 invoked by uid 48); 8 Jul 2019 12:19:17 -0000
From: "ivan.kharpalev at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91112] New: Bad error message for virtual function of a template class. Wrong "required from here" line number
Date: Mon, 08 Jul 2019 12:19: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ivan.kharpalev 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-91112-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00584.txt.bz2
Content-length: 821
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91112
Bug ID: 91112
Summary: Bad error message for virtual function of a template
class. Wrong "required from here" line number
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ivan.kharpalev at gmail dot com
Target Milestone: ---
https://godbolt.org/z/orxMIj
I expect to see number of the line that triggers instantiation.
gcc-7 and clang show it.
P.S.
It even does not show bad method invocation line if it was called via base
class pointer.
https://godbolt.org/z/-SN5n5
It only shows call line for the class itself
https://godbolt.org/z/kmaUQt
>From gcc-bugs-return-648473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 12:35:13 2019
Return-Path: <gcc-bugs-return-648473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16174 invoked by alias); 8 Jul 2019 12:35: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 16092 invoked by uid 48); 8 Jul 2019 12:35:09 -0000
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/91030] Poor performance of I/O -fconvert=big-endian
Date: Mon, 08 Jul 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: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jb 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-91030-4-HiQqWS9PIA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91030-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91030-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00585.txt.bz2
Content-length: 1846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91030
--- Comment #38 from Janne Blomqvist <jb at gcc dot gnu.org> ---
First, I think there's a bug in the benchmark in comment #c20. It writes
blocksize * sizeof(double), but then advances only blocksize for each iteration
of the loop. Fixed version writing just bytes below:
#include <sys/time.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <sys/statvfs.h>
#include <fcntl.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
double walltime (void)
{
struct timeval TV;
double elapsed;
gettimeofday(&TV, NULL);
elapsed = (double) TV.tv_sec + 1.0e-6*((double) TV.tv_usec);
return elapsed;
}
#define NAME "out.dat"
#define N 250000000
int main()
{
int fd;
unsigned char *p, *w;
long i, size, blocksize, left, to_write;
int bits;
double t1, t2;
struct statvfs buf;
printf ("Test using %ld bytes\n", (long) N);
statvfs (".", &buf);
printf ("Block size of file system: %ld\n", buf.f_bsize);
p = malloc(N * sizeof (*p));
for (i=0; i<N; i++)
p[i] = i;
for (bits = 10; bits < 27; bits++)
{
sync();
blocksize = 1 << bits;
printf("bs = %10ld, ", blocksize);
unlink (NAME);
fd = open(NAME, O_WRONLY|O_CREAT, S_IRUSR | S_IWUSR);
if (fd < 0)
{
perror ("Open of " NAME " failed");
exit(1);
}
left = N;
w = p;
t1 = walltime();
while (left > 0)
{
if (left >= blocksize)
to_write = blocksize;
else
to_write = left;
write (fd, w, blocksize);
w += to_write;
left -= to_write;
}
close (fd);
t2 = walltime ();
printf ("%.2f MiB/s\n", N / (t2-t1) / 1048576);
}
free (p);
unlink (NAME);
return 0;
}
>From gcc-bugs-return-648474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 12:42:15 2019
Return-Path: <gcc-bugs-return-648474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38993 invoked by alias); 8 Jul 2019 12: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 38911 invoked by uid 48); 8 Jul 2019 12:42:12 -0000
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/91030] Poor performance of I/O -fconvert=big-endian
Date: Mon, 08 Jul 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: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jb 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-91030-4-iFwQyN9PH9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91030-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91030-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00586.txt.bz2
Content-length: 1709
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91030
--- Comment #39 from Janne Blomqvist <jb at gcc dot gnu.org> ---
Now, with the fixed benchmark in the previous comment, on Lustre (version 2.5)
system I get:
Test using 250000000 bytes
Block size of file system: 4096
bs = 1024, 53.27 MiB/s
bs = 2048, 73.99 MiB/s
bs = 4096, 222.41 MiB/s
bs = 8192, 351.38 MiB/s
bs = 16384, 483.86 MiB/s
bs = 32768, 583.76 MiB/s
bs = 65536, 677.11 MiB/s
bs = 131072, 748.60 MiB/s
bs = 262144, 700.69 MiB/s
bs = 524288, 811.76 MiB/s
bs = 1048576, 1032.99 MiB/s
bs = 2097152, 1034.03 MiB/s
bs = 4194304, 1063.74 MiB/s
bs = 8388608, 1030.15 MiB/s
bs = 16777216, 1084.82 MiB/s
bs = 33554432, 1067.05 MiB/s
bs = 67108864, 1063.79 MiB/s
On the same system, on a NFS filesystem connected with Infiniband I get:
Test using 250000000 bytes
Block size of file system: 1048576
bs = 1024, 301.41 MiB/s
bs = 2048, 351.51 MiB/s
bs = 4096, 471.39 MiB/s
bs = 8192, 444.61 MiB/s
bs = 16384, 510.88 MiB/s
bs = 32768, 527.99 MiB/s
bs = 65536, 516.57 MiB/s
bs = 131072, 481.38 MiB/s
bs = 262144, 514.29 MiB/s
bs = 524288, 462.06 MiB/s
bs = 1048576, 528.30 MiB/s
bs = 2097152, 526.76 MiB/s
bs = 4194304, 501.09 MiB/s
bs = 8388608, 493.61 MiB/s
bs = 16777216, 550.24 MiB/s
bs = 33554432, 532.20 MiB/s
bs = 67108864, 532.82 MiB/s
So for Lustre, a buffer size bigger than the current 8 kB at least seems
justified. While Lustre sees improvements all the way to 1 MB buffer size,
such large buffers by default seems a bit excessive.
>From gcc-bugs-return-648475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 12:49:32 2019
Return-Path: <gcc-bugs-return-648475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120841 invoked by alias); 8 Jul 2019 12:49: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 117034 invoked by uid 48); 8 Jul 2019 12:49:28 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90712] [10 regression] gcc.dg/rtl/aarch64/subs_adds_sp.c fails with ICE
Date: Mon, 08 Jul 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: 10.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: 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-90712-4-wNrzu8G9Dx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00587.txt.bz2
Content-length: 480
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90712
Wilco <wilco at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |wilco at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #2 from Wilco <wilco at gcc dot gnu.org> ---
Fixed
>From gcc-bugs-return-648476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 13:04:30 2019
Return-Path: <gcc-bugs-return-648476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79154 invoked by alias); 8 Jul 2019 13:04: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 78690 invoked by uid 48); 8 Jul 2019 13:04:25 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 2019 13:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.1.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-91101-4-PLW7sz1bUI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00588.txt.bz2
Content-length: 146
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r259641.
>From gcc-bugs-return-648477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 13:24:43 2019
Return-Path: <gcc-bugs-return-648477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99110 invoked by alias); 8 Jul 2019 13:24: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 99030 invoked by uid 48); 8 Jul 2019 13:24:39 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 2019 13:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.1.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-91101-4-oqOJNcTHUM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00589.txt.bz2
Content-length: 3042
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #10 from Martin Liška <marxin at gcc dot gnu.org> ---
The issue is that __asan_stack_malloc_0 function is very high in perf profile:
# Overhead Command Shared Object Symbol
# ........ ............... ........................
........................................................................
#
91.97% test-conf-parse libasan.so.5.0.0 [.]
__asan_stack_malloc_0
7.00% test-conf-parse libsystemd-shared-242.so [.] config_parse
0.12% test-conf-parse libsystemd-shared-242.so [.] read_line_full
0.11% test-conf-parse libc-2.29.so [.] _IO_getc
0.10% test-conf-parse libc-2.29.so [.] __strlen_avx2
0.08% test-conf-parse libsystemd-shared-242.so [.] safe_fgetc
0.07% test-conf-parse libsystemd-shared-242.so [.] categorize_eol
perf annotate says:
: Disassembly of section .text:
:
: 0000000000034a00 <__asan_stack_malloc_0>:
: __asan_stack_malloc_0():
: extern "C" SANITIZER_INTERFACE_ATTRIBUTE void
__asan_stack_free_##class_id( \
: uptr ptr, uptr size) {
\
: OnFree(ptr, class_id, size);
\
: }
...
: _ZN6__asan9FakeStack8AllocateEmmm():
: GC(real_stack);
0.00 : 34b30: mov %rbp,%rsi
0.00 : 34b33: mov %rax,%rdi
0.00 : 34b36: callq 34800 <__asan::FakeStack::GC(unsigned long)>
0.00 : 34b3b: jmpq 34a2c <__asan_stack_malloc_0+0x2c>
: for (int i = 0; i < num_iter; i++) {
0.00 : 34b40: xor %ecx,%ecx
0.12 : 34b42: add $0x1,%ecx
17.35 : 34b45: cmp %ecx,%r8d
17.95 : 34b48: je 34b70 <__asan_stack_malloc_0+0x170>
: uptr pos = ModuloNumberOfFrames(stack_size_log,
class_id, hint_position++);
0.00 : 34b4a: mov %rdx,%rax
0.01 : 34b4d: add $0x1,%rdx
: _ZN6__asan9FakeStack20ModuloNumberOfFramesEmmm():
: return n & (NumberOfFrames(stack_size_log, class_id) -
1);
0.01 : 34b51: and %rsi,%rax
: _ZN6__asan9FakeStack8AllocateEmmm():
0.03 : 34b54: mov %rdx,(%rbx)
: if (flags[pos]) continue;
0.10 : 34b57: lea 0x1000(%rbx,%rax,1),%rdi
31.71 : 34b5f: cmpb $0x0,(%rdi)
32.65 : 34b62: je 34a72 <__asan_stack_malloc_0+0x72>
0.00 : 34b68: jmp 34b42 <__asan_stack_malloc_0+0x142>
0.00 : 34b6a: nopw 0x0(%rax,%rax,1)
>From gcc-bugs-return-648478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 13:42:26 2019
Return-Path: <gcc-bugs-return-648478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28410 invoked by alias); 8 Jul 2019 13:42: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 27565 invoked by uid 48); 8 Jul 2019 13:42:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91112] [8 Regression] Bad error message for virtual function of a template class. Wrong "required from here" line number
Date: Mon, 08 Jul 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: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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 everconfirmed
Message-ID: <bug-91112-4-xUibEl7KQB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91112-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91112-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00590.txt.bz2
Content-length: 548
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91112
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-07-08
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Please provide the code, not URLs (as https://gcc.gnu.org/bugs/ requests).
>From gcc-bugs-return-648479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 13:47:58 2019
Return-Path: <gcc-bugs-return-648479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65669 invoked by alias); 8 Jul 2019 13:47: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 63510 invoked by uid 48); 8 Jul 2019 13:47:54 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 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: sanitizer
X-Bugzilla-Version: 9.1.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-91101-4-RqmkUwjnzJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00591.txt.bz2
Content-length: 811
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #11 from Martin Liška <marxin at gcc dot gnu.org> ---
If I apply the following patch:
diff --git a/libsanitizer/asan/asan_fake_stack.cc
b/libsanitizer/asan/asan_fake_stack.cc
index 3140f9a2aeb..2034769161e 100644
--- a/libsanitizer/asan/asan_fake_stack.cc
+++ b/libsanitizer/asan/asan_fake_stack.cc
@@ -198,6 +198,9 @@ static FakeStack *GetFakeStackFast() {
}
ALWAYS_INLINE uptr OnMalloc(uptr class_id, uptr size) {
+ VReport(1, "T%d: OnMalloc called for size: %d\n",
+ GetCurrentTidOrInvalid(), size);
+
FakeStack *fs = GetFakeStackFast();
if (!fs) return 0;
uptr local_stack;
I see a rapid change of calls of the function from 15381->2127789, where the
change is an allocation 64B:
OnMalloc called for size: 64
>From gcc-bugs-return-648480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 13:54:48 2019
Return-Path: <gcc-bugs-return-648480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123120 invoked by alias); 8 Jul 2019 13:54: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 123074 invoked by uid 48); 8 Jul 2019 13:54:44 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 2019 13:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.1.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-91101-4-DFUpsnqOpI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00592.txt.bz2
Content-length: 1563
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #12 from Martin Liška <marxin at gcc dot gnu.org> ---
So the suspected allocation that happens is:
#0 0x00007ffff723abb2 in __asan::FakeStack::Allocate
(real_stack=140737488344072, class_id=0, stack_size_log=20,
this=0x7ffff25f7000) at ../../../../libsanitizer/asan/asan_fake_stack.cc:103
#1 __asan::OnMalloc (size=<optimized out>, class_id=0) at
../../../../libsanitizer/asan/asan_fake_stack.cc:208
#2 __asan_stack_malloc_0 (size=<optimized out>) at
../../../../libsanitizer/asan/asan_fake_stack.cc:234
#3 0x00007ffff6b5e6c5 in categorize_eol (c=120 'x', flags=(unknown: 0)) at
../src/basic/fileio.c:759
#4 0x00007ffff6b5eb01 in read_line_full (f=0x616000003f80, limit=1048576,
flags=(unknown: 0), ret=0x7ffff290b760) at ../src/basic/fileio.c:833
#5 0x00007ffff6a25be6 in read_line (f=0x616000003f80, limit=1048576,
ret=0x7ffff290b760) at ../src/basic/fileio.h:90
#6 0x00007ffff6a2818f in config_parse (unit=0x0, filename=0x7ffff290b320
"/tmp/test-conf-parser.gVYMCp", f=0x616000003f80, sections=0x60b300 "Section",
lookup=0x4020a0 <config_item_table_lookup@plt>, table=0x7ffff290b2a0,
flags=CONFIG_PARSE_WARN, userdata=0x0)
at ../src/shared/conf-parser.c:309
#7 0x0000000000404967 in test_config_parse (i=15, s=0x409d20
"[Section]\nsetting1=", 'x' <repeats 181 times>...) at
../src/test/test-conf-parser.c:334
#8 0x0000000000404ef0 in main (argc=1, argv=0x7fffffffdc58) at
../src/test/test-conf-parser.c:392
>From gcc-bugs-return-648481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 14:05:39 2019
Return-Path: <gcc-bugs-return-648481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8402 invoked by alias); 8 Jul 2019 14:05: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 8310 invoked by uid 48); 8 Jul 2019 14:05:32 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 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: sanitizer
X-Bugzilla-Version: 9.1.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-91101-4-5svobOD8jf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00593.txt.bz2
Content-length: 1079
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #13 from Martin Liška <marxin at gcc dot gnu.org> ---
And the stack difference is:
Before:
;; Function categorize_eol (categorize_eol, funcdef_no=127, decl_uid=8513,
cgraph_uid=127, symbol_order=127)
categorize_eol (char c, ReadLineFlags flags)
{
_Bool _found;
EndOfLineMarker D.9001;
_Bool D.8520;
_Bool _1;
EndOfLineMarker _3;
_Bool _7;
EndOfLineMarker _9;
EndOfLineMarker _10;
EndOfLineMarker _11;
EndOfLineMarker _12;
<bb 2> :
_found_4 = 0;
if (flags_5(D) == 1)
goto <bb 3>; [INV]
else
goto <bb 4>; [INV]
...
After:
;; Function categorize_eol (categorize_eol, funcdef_no=127, decl_uid=8513,
cgraph_uid=127, symbol_order=127)
categorize_eol (char c, ReadLineFlags flags)
{
long double D.8516[1] = {1.0e+0}; <--- This stack variable.
_Bool _found;
EndOfLineMarker D.9001;
_Bool D.8520;
_Bool _1;
EndOfLineMarker _3;
_Bool _7;
EndOfLineMarker _9;
EndOfLineMarker _10;
EndOfLineMarker _11;
EndOfLineMarker _12;
...
>From gcc-bugs-return-648482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 14:17:19 2019
Return-Path: <gcc-bugs-return-648482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19699 invoked by alias); 8 Jul 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 19660 invoked by uid 48); 8 Jul 2019 14:17:15 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 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: sanitizer
X-Bugzilla-Version: 9.1.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: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91101-4-Zgprmide4O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00594.txt.bz2
Content-length: 576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |INVALID
--- Comment #14 from Martin Liška <marxin at gcc dot gnu.org> ---
Ahh, I've got it. The systemd is built in the configuration without any
optimization level! Please use -O2, that should speed up it significantly.
>From gcc-bugs-return-648483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 14:21:36 2019
Return-Path: <gcc-bugs-return-648483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28186 invoked by alias); 8 Jul 2019 14:21: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 28134 invoked by uid 48); 8 Jul 2019 14:21:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 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: sanitizer
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
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-91101-4-RMliaFq9ib@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00595.txt.bz2
Content-length: 990
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Seems systemd abuses compound literals even in cases where they make no sense,
perhaps one of those in a short function like that is no longer optimized away
completely and that is why it triggers all the __asan_malloc_0 calls in there
where formerly it got away without that.
E.g.
#define assert_cc(expr) \
struct CONCATENATE(_assert_struct_, __COUNTER__) { \
char x[(expr) ? 0 : -1]; \
};
doesn't make any sense to me, why not say
do { extern char CONCATENATE(_assert_var_, __COUNTER__) [(expr) ? 0 : -1]; }
while (0)
instead?
The IN_SET macro has another compound literal:
assert_cc((sizeof((long double[]){__VA_ARGS__})/sizeof(long double)) <= 20);
It would surprise me if you can't do such counting without resorting to
compound literals.
>From gcc-bugs-return-648484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 14:31:28 2019
Return-Path: <gcc-bugs-return-648484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62491 invoked by alias); 8 Jul 2019 14:31: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 62455 invoked by uid 48); 8 Jul 2019 14:31:25 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91059] [10 regression] gcc.c-torture/execute/builtins/snprintf-chk.c fails on aarch64-elf since r272843
Date: Mon, 08 Jul 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: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco 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
Message-ID: <bug-91059-4-X5yE5khnkK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00596.txt.bz2
Content-length: 588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91059
Wilco <wilco at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilco at gcc dot gnu.org
--- Comment #2 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> Likely target issue - please aarch64 folks investigate first.
I'll have a look, but I bet it's PR78529 again since failures only happen with
LTO and static linking with newlib.
>From gcc-bugs-return-648485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 15:33:14 2019
Return-Path: <gcc-bugs-return-648485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9347 invoked by alias); 8 Jul 2019 15:33: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 6188 invoked by uid 48); 8 Jul 2019 15:33:11 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Mon, 08 Jul 2019 15:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
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-91101-4-18nCGS0C5k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00597.txt.bz2
Content-length: 1631
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #15)
> Seems systemd abuses compound literals even in cases where they make no
> sense, perhaps one of those in a short function like that is no longer
> optimized away completely and that is why it triggers all the
> __asan_malloc_0 calls in there where formerly it got away without that.
> E.g.
> #define assert_cc(expr) \
> struct CONCATENATE(_assert_struct_, __COUNTER__) { \
> char x[(expr) ? 0 : -1]; \
> };
> doesn't make any sense to me, why not say
> do { extern char CONCATENATE(_assert_var_, __COUNTER__) [(expr) ? 0 : -1]; }
> while (0)
> instead?
> The IN_SET macro has another compound literal:
> assert_cc((sizeof((long double[]){__VA_ARGS__})/sizeof(long double)) <= 20);
> It would surprise me if you can't do such counting without resorting to
> compound literals.
As IN_SET is turning the __VA_ARGS__ arguments into case N:, those have to be
constant expressions, so you could say replace IN_SET's
assert_cc((sizeof((long double[]){__VA_ARGS__})/sizeof(long double)) <= 20);
with static long double __assert_in_set __attribute__((__unused__)) [] = {
__VA_ARGS__ };
assert_cc(sizeof (__assert_in_set)/sizeof(long double)) <= 20);
or similar, this is in its own scope, so doesn't need to use any __COUNTER__
etc.
With -O1 and above it would be surely optimized away, and with -O0 it would be
much less costly for asan.
>From gcc-bugs-return-648486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 15:37:38 2019
Return-Path: <gcc-bugs-return-648486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44413 invoked by alias); 8 Jul 2019 15:37: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 43878 invoked by uid 48); 8 Jul 2019 15:37:33 -0000
From: "nsz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91113] New: add declare_simd_variant attribute support
Date: Mon, 08 Jul 2019 15:37: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: 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-91113-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00598.txt.bz2
Content-length: 2646
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91113
Bug ID: 91113
Summary: add declare_simd_variant attribute support
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: nsz at gcc dot gnu.org
Target Milestone: ---
to declare vector functions on aarch64 for one simd architecture only,
support for the openmp 5.0 declare variant syntax is required, but
full support for the omp declare variant pragma is excessive.
(for the aarch64 use-case, see user defined vector functions in
https://developer.arm.com/docs/101129/latest )
I suggest introducing an attribute in gcc that can handle a subset
of omp declare variant pragma and works in c and fortran declarations
for declare simd functions.
I think the syntax and semantics for the attribute should follow
the proposal for clang (without the clang_ prefix):
http://lists.llvm.org/pipermail/llvm-dev/2019-June/132987.html
```
declare_simd_variant
(<variant-func-id>, <simd clauses>{, <context selector clauses>})
<variant-func-id>:= The name of a function variant that is a base
language identifier, or, for C++, a template-id.
<simd clauses> := <simdlen>, <mask>{, <optional simd clauses>}
<simdlen> := simdlen(<positive number>) | simdlen("scalable")
<mask> := inbranch | notinbranch
<optional simd clauses> := <linear clause>
| <uniform clause>
| <align clause> | {,<optional simd clauses>}
<linear clause> := linear_ref(<var>,<step>)
| linear_var(<var>, <step>)
| linear_uval(<var>, <step>)
| linear(<var>, <step>)
<step> := <var> | <non zero number>
<uniform clause> := uniform(<var>)
<align clause> := align(<var>, <positive number>)
<var> := Name of a parameter in the scalar function declaration/definition
<non zero number> := ... | -2 | -1 | 1 | 2 | ...
<positive number> := 1 | 2 | 3 | ...
<context selector clauses> := {<isa>}{,} {<arch>}
<isa> := isa(target-specific-value)
<arch> := arch(target-specific-value)
```
example usage:
```
__attribute__(declare_simd_variant("vfoo", simdlen(2), notinbranch,
isa("simd"))
double foo(double x);
float64x2_t vfoo(float64x2_t vx);
```
should be equivalent to the openmp 5.0 code
```
#pragma omp declare variant(vfoo) \
match(construct={simd(simdlen(2), notinbranch)}, device={isa("simd")})
double foo(double x);
float64x2_t vfoo(float64x2_t vx);
```
>From gcc-bugs-return-648487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 15:51:54 2019
Return-Path: <gcc-bugs-return-648487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29826 invoked by alias); 8 Jul 2019 15:51: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 29773 invoked by uid 55); 8 Jul 2019 15:51:51 -0000
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Mon, 08 Jul 2019 15: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: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: dave.anglin at bell 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-61577-4-E6EZA3QHBD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00599.txt.bz2
Content-length: 2638
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #60 from dave.anglin at bell dot net ---
On 2019-07-08 12:07 a.m., elowe at elowe dot com wrote:
> If you insert the addp4 r14 = 0,r14 before that command (like gcc 4.9.3 does),
> the program compiles and runs correctly
It would be useful to do a regression search to determine the revision that
changed the above behavior.
>
> I'll upload the .s for "IsLower.c" - it's definitely a 32 bit executable, so
> the correct options are being passed around.
I'm not sure why you say the .s for "IsLower.c" is a 32-bit executable and that
the correct options are
being passed around. You haven't shown the assembler or linker commands used
to create the executable.
For applications like the hello world program, there is very little difference
between the 32 and 64-bit
assembler output generated by gcc (cc1).
I'm still trying to understand the problem with the gprel relocation. It seems
to work in 64-bit but not
in 32-bit. While there might be issues with assembler or linker, you are
probably correct that we need
to swizzle pointer with ILP32.
You could try adding something like the following to this hunk after the
emit_insn() line:
 else if (local_symbolic_operand64 (src, VOIDmode))
   {
     /* We want to use @gprel rather than @ltoff relocations for local
        symbols:
         - @gprel does not require dynamic linker
         - and does not use .sdata section
        https://gcc.gnu.org/bugzilla/60465 */
     emit_insn (gen_load_gprel64 (dest, src));
   }
if (TARGET_ILP32)
 {
   rtx tmp;
   tmp = gen_rtx_REG_offset (dest, ptr_mode, REGNO (dest),
                              byte_lowpart_offset (ptr_mode, GET_MODE
(dest)));
   REG_POINTER (tmp) = 1;
   emit_insn (gen_ptr_extend (dest, tmp));
 }
Alternatively, you could try disabling the local_symbolic_operand64 predicate
in predicates.md:
(define_predicate "local_symbolic_operand64"
 (match_code "symbol_ref,const")
{
 switch (GET_CODE (op))
   {
Just add
if (TARGET_ILP32)
 return false;
before switch statement.
>From gcc-bugs-return-648488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 16:18:01 2019
Return-Path: <gcc-bugs-return-648488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93674 invoked by alias); 8 Jul 2019 16:18: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 93554 invoked by uid 48); 8 Jul 2019 16:17:57 -0000
From: "bugdal at aerifal dot cx" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/89072] -Wall -Werror should be defaults
Date: Mon, 08 Jul 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: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: bugdal at aerifal dot cx
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-89072-4-TmmlGexmzr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89072-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89072-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00600.txt.bz2
Content-length: 675
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89072
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugdal at aerifal dot cx
--- Comment #2 from Rich Felker <bugdal at aerifal dot cx> ---
Just here to second that -Werror should never be the default and that it's
pretty much entirely wrong. -Werror is useful for imposing development policy
in a development environment you control. It's not at all okay for shipping
source that the user will compile in an environment you don't control.
>From gcc-bugs-return-648489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 16:22:15 2019
Return-Path: <gcc-bugs-return-648489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128797 invoked by alias); 8 Jul 2019 16:22: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 128749 invoked by uid 48); 8 Jul 2019 16:22:11 -0000
From: "elowe at elowe dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Mon, 08 Jul 2019 16:22: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.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: elowe at elowe 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-61577-4-L01SdXFK6S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00601.txt.bz2
Content-length: 1582
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #61 from EML <elowe at elowe dot com> ---
Sorry, perhaps I have confused the situation.
I have already patched my compiler to remove the gprel in both 32 and 64.
That gprel patch breaks things in both 32 and 64. I'm reasonably convinced the
patch is wrong for HP-UX, so I'm moving forward with that assumption.
When I remove that gprel patch - the 64bit stage 1 compiler is able to compile
hello world, islower, as well as all the other "conftest" programs
successfully. It can compile libstdc++ as well (some duplicate symbols
however).
However, the 32-bit compiler does not work which I believe to be a pointer
swizzle issue.
I've confirmed the binary is 32bit as follows:
-bash-5.0$ file islower
islower: ELF-32 executable object file - IA64
-bash-5.0$ elfdump -f islower
islower:
*** ELF Header ***
Class: ELF-32
Data: Big-endian
OS: HP-UX
ABI Version: 1
Type: EXEC
Machine: IPF
Version: 1
Entry Addr: 0x40008b0
Program Hdr Offset: 0x34
Section Hdr Offset: 0x1104c
Flags: trapnil
Flags: big-endian PSR
Flags: IA-64
Elf Hdr Size: 0x34
Program Hdr Size: 0x20
Program Hdr Number: 12
Section Hdr Size: 0x28
Section Hdr Number: 43
Section Hdr String Idx: 42
>From gcc-bugs-return-648490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 16:23:06 2019
Return-Path: <gcc-bugs-return-648490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129699 invoked by alias); 8 Jul 2019 16:23: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 129630 invoked by uid 48); 8 Jul 2019 16:23:02 -0000
From: "bugdal at aerifal dot cx" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Mon, 08 Jul 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: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugdal at aerifal dot cx
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-91092-4-SuC187GcMA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00602.txt.bz2
Content-length: 869
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugdal at aerifal dot cx
--- Comment #11 from Rich Felker <bugdal at aerifal dot cx> ---
I'm strongly in favor of fixing this, but the configure situation is a mess.
Doing this needs both an active project to fix configure scripts (starting with
upstream autoconf/gnulib ones, and at least in the past, the maintainers'
misguided opinions that testing for symbol presence with missing or invalid
declarations was a valid configure test! see: https://ewontfix.com/13/) and
probably one of the workarounds described above (detecting configure use and
not erroring out in that case?).
>From gcc-bugs-return-648491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 16:58:03 2019
Return-Path: <gcc-bugs-return-648491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56470 invoked by alias); 8 Jul 2019 16:58: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 56329 invoked by uid 48); 8 Jul 2019 16:57:59 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91059] [10 regression] gcc.c-torture/execute/builtins/snprintf-chk.c fails on aarch64-elf since r272843
Date: Mon, 08 Jul 2019 16:58: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco 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-91059-4-fF2CxTbZX1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00603.txt.bz2
Content-length: 208
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91059
--- Comment #3 from Wilco <wilco at gcc dot gnu.org> ---
Confirmed it's the same memset register corruption issue. The fix is trivial:
add -fno-ipa-ra.
>From gcc-bugs-return-648492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 17:01:54 2019
Return-Path: <gcc-bugs-return-648492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6491 invoked by alias); 8 Jul 2019 17: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 6425 invoked by uid 55); 8 Jul 2019 17:01:49 -0000
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Mon, 08 Jul 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: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: dave.anglin at bell 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-61577-4-b6FoPdpuCJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00604.txt.bz2
Content-length: 646
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #62 from dave.anglin at bell dot net ---
On 2019-07-08 12:22 p.m., elowe at elowe dot com wrote:
> When I remove that gprel patch - the 64bit stage 1 compiler is able to compile
> hello world, islower, as well as all the other "conftest" programs
> successfully. It can compile libstdc++ as well (some duplicate symbols
> however).
I doubt removing the gprel patch is an acceptable solution as it fixed a bug on
Linux. A better
solution is to disable the local_symbolic_operand64 predicate on hpux.
That should fix hello world. Then, we can move to other issues.
>From gcc-bugs-return-648494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 17:02:37 2019
Return-Path: <gcc-bugs-return-648494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8330 invoked by alias); 8 Jul 2019 17:02: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 8220 invoked by uid 48); 8 Jul 2019 17:02:33 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/78529] gcc.c-torture/execute/builtins/strcat-chk.c failed with lto/O2
Date: Mon, 08 Jul 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: testsuite
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: lto
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: cc
Message-ID: <bug-78529-4-vdEVzaWi5V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78529-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78529-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00606.txt.bz2
Content-length: 446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |clyon at gcc dot gnu.org
--- Comment #38 from Richard Biener <rguenth at gcc dot gnu.org> ---
*** Bug 91059 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-648493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 17:02:37 2019
Return-Path: <gcc-bugs-return-648493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8311 invoked by alias); 8 Jul 2019 17:02: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 8180 invoked by uid 48); 8 Jul 2019 17:02:32 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91059] [10 regression] gcc.c-torture/execute/builtins/snprintf-chk.c fails on aarch64-elf since r272843
Date: Mon, 08 Jul 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: testsuite
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: 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-91059-4-Xgwx1ioOA5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00605.txt.bz2
Content-length: 503
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91059
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
duplicate then
*** This bug has been marked as a duplicate of bug 78529 ***
>From gcc-bugs-return-648496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 17:03:17 2019
Return-Path: <gcc-bugs-return-648496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10418 invoked by alias); 8 Jul 2019 17:03: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 10169 invoked by uid 48); 8 Jul 2019 17:03:10 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91092] Error on implicit function declarations by default
Date: Mon, 08 Jul 2019 17: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: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher 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-91092-4-qQZVEQ6YvU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00609.txt.bz2
Content-length: 568
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91092
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-08
Ever confirmed|0 |1
--- Comment #12 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Given the above, I don't think it can ever be ready in time for GCC 10.
But, confirmed.
>From gcc-bugs-return-648497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 17:03:17 2019
Return-Path: <gcc-bugs-return-648497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10437 invoked by alias); 8 Jul 2019 17:03: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 10199 invoked by uid 55); 8 Jul 2019 17:03:11 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/78529] gcc.c-torture/execute/builtins/strcat-chk.c failed with lto/O2
Date: Mon, 08 Jul 2019 17: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: 7.0
X-Bugzilla-Keywords: lto
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-78529-4-pw20nCiusd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78529-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78529-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00608.txt.bz2
Content-length: 939
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
--- Comment #39 from Wilco <wilco at gcc dot gnu.org> ---
Author: wilco
Date: Mon Jul 8 17:02:35 2019
New Revision: 273238
URL: https://gcc.gnu.org/viewcvs?rev=273238&root=gcc&view=rev
Log:
Turn of ipa-ra in builtins test (PR91059)
The gcc.c-torture/execute/builtins/lib directory contains a reimplementation
of many C library string functions, which causes non-trivial register
allocation
bugs with LTO and static linked libraries. To fix this long-standing test
issue, turn off ipa-ra which avoids the register corruption across calls. All
builtin torture tests now pass on aarch64-none-elf. Committed as obvious.
testsuite/
PR testsuite/91059
PR testsuite/78529
* gcc.c-torture/execute/builtins/builtins.exp: Add -fno-ipa-ra.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.c-torture/execute/builtins/builtins.exp
>From gcc-bugs-return-648495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 17:03:15 2019
Return-Path: <gcc-bugs-return-648495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10302 invoked by alias); 8 Jul 2019 17:03: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 10130 invoked by uid 55); 8 Jul 2019 17:03:09 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91059] [10 regression] gcc.c-torture/execute/builtins/snprintf-chk.c fails on aarch64-elf since r272843
Date: Mon, 08 Jul 2019 17: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco 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:
Message-ID: <bug-91059-4-LhByJhXqfl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00607.txt.bz2
Content-length: 938
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91059
--- Comment #5 from Wilco <wilco at gcc dot gnu.org> ---
Author: wilco
Date: Mon Jul 8 17:02:35 2019
New Revision: 273238
URL: https://gcc.gnu.org/viewcvs?rev=273238&root=gcc&view=rev
Log:
Turn of ipa-ra in builtins test (PR91059)
The gcc.c-torture/execute/builtins/lib directory contains a reimplementation
of many C library string functions, which causes non-trivial register
allocation
bugs with LTO and static linked libraries. To fix this long-standing test
issue, turn off ipa-ra which avoids the register corruption across calls. All
builtin torture tests now pass on aarch64-none-elf. Committed as obvious.
testsuite/
PR testsuite/91059
PR testsuite/78529
* gcc.c-torture/execute/builtins/builtins.exp: Add -fno-ipa-ra.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.c-torture/execute/builtins/builtins.exp
>From gcc-bugs-return-648498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 17:06:30 2019
Return-Path: <gcc-bugs-return-648498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16424 invoked by alias); 8 Jul 2019 17:06: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 16352 invoked by uid 48); 8 Jul 2019 17:06:27 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/78529] gcc.c-torture/execute/builtins/strcat-chk.c failed with lto/O2
Date: Mon, 08 Jul 2019 17:06: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: 7.0
X-Bugzilla-Keywords: lto
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: wilco at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution assigned_to
Message-ID: <bug-78529-4-iEogKdgHp4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78529-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78529-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00610.txt.bz2
Content-length: 564
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78529
Wilco <wilco at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |wilco at gcc dot gnu.org
Resolution|--- |FIXED
Assignee|unassigned at gcc dot gnu.org |wilco at gcc dot gnu.org
--- Comment #40 from Wilco <wilco at gcc dot gnu.org> ---
Fixed
>From gcc-bugs-return-648499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 17:35:47 2019
Return-Path: <gcc-bugs-return-648499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62588 invoked by alias); 8 Jul 2019 17:35: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 62543 invoked by uid 55); 8 Jul 2019 17:35:43 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88233] combine fails to merge insns leaving unneeded reg copies
Date: Mon, 08 Jul 2019 17: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.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88233-4-u3y25qVJnm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88233-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88233-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00611.txt.bz2
Content-length: 1797
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88233
--- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Author: segher
Date: Mon Jul 8 17:35:12 2019
New Revision: 273240
URL: https://gcc.gnu.org/viewcvs?rev=273240&root=gcc&view=rev
Log:
subreg: Add -fsplit-wide-types-early (PR88233)
Currently the second lower-subreg pass is run right before RA. This
is much too late to be very useful. At least for targets that do not
have RTL patterns for operations on multi-register modes it is a lot
better to split patterns earlier, before combine and all related
passes.
This adds an option -fsplit-wide-types-early that does that, and
enables it by default for rs6000.
PR rtl-optimization/88233
* common.opt (fsplit-wide-types-early): New option.
* common/config/rs6000/rs6000-common.c
(rs6000_option_optimization_table): Add OPT_fsplit_wide_types_early for
OPT_LEVELS_ALL.
* doc/invoke.texi (Optimization Options): Add -fsplit-wide-types-early.
* lower-subreg.c (pass_lower_subreg2::gate): Add test for
flag_split_wide_types_early.
(pass_data_lower_subreg3): New.
(pass_lower_subreg3): New.
(make_pass_lower_subreg3): New.
* passes.def (pass_lower_subreg2): Move after the loop passes.
(pass_lower_subreg3): New, inserted where pass_lower_subreg2 was.
* tree-pass.h (make_pass_lower_subreg2): Move up, to its new place in
the pass pipeline; its previous place is taken by ...
(make_pass_lower_subreg3): ... this.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/common.opt
trunk/gcc/common/config/rs6000/rs6000-common.c
trunk/gcc/doc/invoke.texi
trunk/gcc/lower-subreg.c
trunk/gcc/passes.def
trunk/gcc/tree-pass.h
>From gcc-bugs-return-648500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 17:54:04 2019
Return-Path: <gcc-bugs-return-648500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89431 invoked by alias); 8 Jul 2019 17: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 89313 invoked by uid 48); 8 Jul 2019 17:53:58 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91010] ICE: Segmentation fault (in location_wrapper_p)
Date: Mon, 08 Jul 2019 17: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, openmp
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: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91010-4-IH4fOO2wzU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00612.txt.bz2
Content-length: 146
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91010
--- Comment #4 from Arseny Solokha <asolokha at gmx dot com> ---
Can this PR be closed now?
>From gcc-bugs-return-648501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 17:54:05 2019
Return-Path: <gcc-bugs-return-648501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89494 invoked by alias); 8 Jul 2019 17:54: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 89389 invoked by uid 48); 8 Jul 2019 17:54:01 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91114] New: [10 Regression] ICE in vect_analyze_loop, at tree-vect-loop.c:2415
Date: Mon, 08 Jul 2019 17:54: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-checking, ice-on-valid-code, openmp
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-91114-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00613.txt.bz2
Content-length: 1565
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91114
Bug ID: 91114
Summary: [10 Regression] ICE in vect_analyze_loop, at
tree-vect-loop.c:2415
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-checking, ice-on-valid-code, openmp
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-alpha20190707 snapshot (r273184) ICEs when compiling the following
testcase w/ -O1 -fopenmp-simd:
void
ne (double *zu)
{
int h3;
#pragma omp simd simdlen (4)
for (h3 = 0; h3 < 4; ++h3)
zu[h3] = 0;
}
% x86_64-unknown-linux-gnu-gcc-10.0.0-alpha20190707 -O1 -fopenmp-simd -c
hnkztevu.c
during GIMPLE pass: vect
hnkztevu.c: In function 'ne':
hnkztevu.c:2:1: internal compiler error: in vect_analyze_loop, at
tree-vect-loop.c:2415
2 | ne (double *zu)
| ^~
0x6fe6b2 vect_analyze_loop(loop*, _loop_vec_info*, vec_info_shared*)
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/tree-vect-loop.c:2415
0xfc5495 try_vectorize_loop_1
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/tree-vectorizer.c:886
0xfc613f vectorize_loops()
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20190707/work/gcc-10-20190707/gcc/tree-vectorizer.c:1114
>From gcc-bugs-return-648502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 18:51:51 2019
Return-Path: <gcc-bugs-return-648502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121821 invoked by alias); 8 Jul 2019 18: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 121755 invoked by uid 48); 8 Jul 2019 18:51:47 -0000
From: "elowe at elowe dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Mon, 08 Jul 2019 18: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: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: elowe at elowe 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-61577-4-Pnw1AeO1bt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00614.txt.bz2
Content-length: 750
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #63 from EML <elowe at elowe dot com> ---
Sorry, I didn't undo the patch completely.
I made a very simple change:
--- ia64.c.orig 2019-07-08 14:43:33 +0000
+++ ia64.c 2019-07-05 16:46:24 +0000
@@ -1137,7 +1137,7 @@
emit_insn (gen_load_fptr (dest, src));
else if (sdata_symbolic_operand (src, VOIDmode))
emit_insn (gen_load_gprel (dest, src));
- else if (local_symbolic_operand64 (src, VOIDmode))
+ else if (local_symbolic_operand64 (src, VOIDmode) && !TARGET_HPUX)
{
/* We want to use @gprel rather than @ltoff relocations for local
symbols:
Which I think has the same effect as disabling it in predicate. I'm happy with
either approach.
>From gcc-bugs-return-648503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 19:14:55 2019
Return-Path: <gcc-bugs-return-648503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13102 invoked by alias); 8 Jul 2019 19: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 13008 invoked by uid 48); 8 Jul 2019 19:14:48 -0000
From: "fhsueh at roku dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91115] New: stack-buffer-overflow on memset local variable when creating thread on ARM Linux
Date: Mon, 08 Jul 2019 19:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fhsueh at roku 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-91115-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00615.txt.bz2
Content-length: 7155
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91115
Bug ID: 91115
Summary: stack-buffer-overflow on memset local variable when
creating thread on ARM Linux
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: fhsueh at roku dot com
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
Target Milestone: ---
I'm getting a ASAN stack-buffer-overflow when thread is starting on ARM Linux.
gcc-8.3 and glibc-2.22. Here's the output, cleaned up a bit:
>>>>>
==1541==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x9bffebf8 at
pc 0xa3585e98 bp 0x9bffebc4 sp 0x9bffe790
WRITE of size 36 at 0x9bffebf8 thread T10
#0 0xa3585e97 in __interceptor_memset
gcc-8.3.0/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:709
#1 0x9f6d378b in __pthread_attr_init_2_1
glibc-2.22/nptl/pthread_attr_init.c:41
#2 0xa3619053 in __sanitizer::GetThreadStackTopAndBottom(bool, unsigned
long*, unsigned long*)
gcc-8.3.0/libsanitizer/sanitizer_common/sanitizer_linux_libcdep.cc:105
#3 0xa361940b in __sanitizer::GetThreadStackAndTls(bool, unsigned long*,
unsigned long*, unsigned long*, unsigned long*)
gcc-8.3.0/libsanitizer/sanitizer_common/sanitizer_linux_libcdep.cc:415
#4 0xa360f147 in
__asan::AsanThread::SetThreadStackAndTls(__asan::AsanThread::InitOptions
const*) gcc-8.3.0/libsanitizer/asan/asan_thread.cc:287
#5 0xa360f237 in __asan::AsanThread::Init(__asan::AsanThread::InitOptions
const*) gcc-8.3.0/libsanitizer/asan/asan_thread.cc:224
#6 0xa360f367 in __asan::AsanThread::ThreadStart(unsigned long,
__sanitizer::atomic_uintptr_t*) gcc-8.3.0/libsanitizer/asan/asan_thread.cc:241
#7 0x9f6d1d63 in start_thread glibc-2.22/nptl/pthread_create.c:336
Address 0x9bffebf8 is located in stack of thread T9 at offset 664 in frame
#0 0x25b6e3f in _M_run arm-roku-linux-gnueabi/include/c++/8.3.0/thread:196
This frame has 13 object(s):
[32, 36) 'bt'
[96, 100) 'bt'
[160, 168) '<unknown>'
[224, 232) '<unknown>'
[288, 296) '<unknown>'
[352, 360) '<unknown>'
[416, 424) '<unknown>'
[480, 488) '<unknown>'
[544, 552) 'lock'
[608, 620) 'cd'
[672, 684) 'cd' <== Memory access at offset 664 partially underflows this
variable
[736, 748) '<unknown>'
[800, 812) '<unknown>'
HINT: this may be a false positive if your program uses some custom stack
unwind mechanism or swapcontext
(longjmp and C++ exceptions *are* supported)
Thread T9 created by T0 here:
#0 0xa35cdc1f in __interceptor_pthread_create
gcc-8.3.0/libsanitizer/asan/asan_interceptors.cc:202
#1 0x9f83d543 in
std::thread::_M_start_thread(std::unique_ptr<std::thread::_State,
std::default_delete<std::thread::_State> >, void (*)())
(/usr/lib/libstdc++.so.6+0x9c543)
SUMMARY: AddressSanitizer: stack-buffer-overflow
gcc-8.3.0/libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc:709
in __interceptor_memset
Shadow bytes around the buggy address:
0x437ffd20: 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1
0x437ffd30: 04 f2 f2 f2 f2 f2 f2 f2 04 f2 f2 f2 f2 f2 f2 f2
0x437ffd40: 00 f2 f2 f2 f2 f2 f2 f2 00 f2 f2 f2 f2 f2 f2 f2
0x437ffd50: 00 f2 f2 f2 f2 f2 f2 f2 00 f2 f2 f2 f2 f2 f2 f2
0x437ffd60: 00 f2 f2 f2 f2 f2 f2 f2 00 f2 f2 f2 f2 f2 f2 f2
=>0x437ffd70: 00 f2 f2 f2 f2 f2 f2 f2 00 04 f2 f2 f2 f2 f2[f2]
0x437ffd80: 00 04 f2 f2 f2 f2 f2 f2 00 04 f2 f2 f2 f2 f2 f2
0x437ffd90: 00 04 f2 f2 00 00 00 00 00 00 00 00 00 00 00 00
0x437ffda0: 00 00 00[ 363.983356] grsec: bruteforce prevention initiated for
the next 30 minutes or until service restarted, stalling each fork 30 seconds.
Please investigate the crash report for /bin/Application[Application:1541]
uid/euid:0/0 gid/egid:0/0, parent /bin/Application[Application:1480]
uid/euid:501/501 gid/egid:501/501
00 00 00 00 00 00 00 00 00 00 00 00 00
0x437ffdb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x437ffdc0: 00 00 00 00 364.068455] ltcore_dump: starting dump
m 00 00 00 00 00 00 grsec: From 10.14.24.38: denied resource overstep by
requesting 52 for RLIMIT_CORE against limit 0 for
/bin/Application[Application:1542] uid/euid:501/501 gid/egid:501/501, parent
/bin/busybox[sh:1394] uid/euid:0/0 gid/egid:0/0
[1m 00 grsec: From 10.14.24.38: denied resource overstep by requesting 84 for
RLIMIT_CORE against limit 0 for /bin/Application[Application:1542]
uid/euid:501/501 gid/egid:501/501, parent /bin/busybox[sh:1394] uid/euid:0/0
gid/egid:0/0
[0m00 00[ 364.128767] grsec: From 10.14.24.38: denied resource overstep by
requesting 116 for RLIMIT_CORE against limit 0 for
/bin/Application[Application:1542] uid/euid:501/501 gid/egid:501/501, parent
/bin/busybox[sh:1394] uid/euid:0/0 gid/egid:0/0
00 00 364.152847] grsec: From 10.14.24.38: denied resource overstep by
requesting 148 for RLIMIT_CORE against limit 0 for
/bin/Application[Application:1542] uid/euid:501/501 gid/egid:501/501, parent
/bin/busybox[sh:1394] uid/euid:0/0 gid/egid:0/0
1m 00
Shado[ 364.177095] grsec: From 10.14.24.38: denied resource overstep by
requesting 180 for RLIMIT_CORE against limit 0 for
/bin/Application[Application:1542] uid/euid:501/501 gid/egid:501/501, parent
/bin/busybox[sh:1394] uid/euid:0/0 gid/egid:0/0
w byte legend (one shadow byte r[ 364.201006] grsec: From 10.14.24.38: denied
resource overstep by requesting 212 for RLIMIT_CORE against limit 0 for
/bin/Application[Application:1542] uid/euid:501/501 gid/egid:501/501, parent
/bin/busybox[sh:1394] uid/euid:0/0 gid/egid:0/0
[ 364.225137] grsec: more alerts, logging disabled for 10 seconds
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Thread T10 created by T0 here:
#0 0xa35cdc1f in __interceptor_pthread_create
gcc-8.3.0/libsanitizer/asan/asan_interceptors.cc:202
#1 0x9f83d543 in
std::thread::_M_start_thread(std::unique_ptr<std::thread::_State,
std::default_delete<std::thread::_State> >, void (*)())
(/usr/lib/libstdc++.so.6+0x9c543)
#2 0x41b58ab1 (<unknown module>)
==1541==ABORTING
<<<<<
I found similar case when redhat user moved from GCC 5 to 6:
https://bugzilla.redhat.com/show_bug.cgi?id=1386445
My use case has similar characteristics in that it's very deterministic and
that the intercepted memset() thinks a local variable lives in another thread's
stack.
I'm working on trying this on gcc-9.1.0. Thanks!
>From gcc-bugs-return-648504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 19:18:58 2019
Return-Path: <gcc-bugs-return-648504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16984 invoked by alias); 8 Jul 2019 19:18: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 16922 invoked by uid 48); 8 Jul 2019 19:18:55 -0000
From: "fhsueh at roku dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91115] stack-buffer-overflow on memset local variable when creating thread on ARM Linux
Date: Mon, 08 Jul 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: sanitizer
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fhsueh at roku 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-91115-4-YVRd43VYAw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91115-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91115-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00616.txt.bz2
Content-length: 306
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91115
--- Comment #1 from Fred Hsueh <fhsueh at roku dot com> ---
Created attachment 46580
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46580&action=edit
Fixup memory location of shadow
This shadow location works better than the 32-bit default.
>From gcc-bugs-return-648505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 19:37:11 2019
Return-Path: <gcc-bugs-return-648505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66773 invoked by alias); 8 Jul 2019 19:37: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 66722 invoked by uid 55); 8 Jul 2019 19:37:07 -0000
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61577] [4.9.0] can't compile on hp-ux v3 ia64
Date: Mon, 08 Jul 2019 19:37: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.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: dave.anglin at bell 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-61577-4-HD5nn2rMKU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00617.txt.bz2
Content-length: 1172
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #64 from dave.anglin at bell dot net ---
On 2019-07-08 2:51 p.m., elowe at elowe dot com wrote:
> I made a very simple change:
>
> --- ia64.c.orig 2019-07-08 14:43:33 +0000
> +++ ia64.c 2019-07-05 16:46:24 +0000
> @@ -1137,7 +1137,7 @@
> emit_insn (gen_load_fptr (dest, src));
> else if (sdata_symbolic_operand (src, VOIDmode))
> emit_insn (gen_load_gprel (dest, src));
> - else if (local_symbolic_operand64 (src, VOIDmode))
> + else if (local_symbolic_operand64 (src, VOIDmode) && !TARGET_HPUX)
> {
> /* We want to use @gprel rather than @ltoff relocations for local
> symbols:
>
> Which I think has the same effect as disabling it in predicate. I'm happy with
> either approach.
Okay, I assume we are now at the problem in comment #58. Would you upload the
final RTL
dump for "IsLower.c" ("-da" opttion will generate)? It would also be useful to
find the change
which introduced the regression for "IsLower.c".
You could post the above patch with a ChangeLog to gcc-patches. It's small
enough that a FSF
assignment shouldn't be needed.
>From gcc-bugs-return-648506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 20:13:58 2019
Return-Path: <gcc-bugs-return-648506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14980 invoked by alias); 8 Jul 2019 20:13: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 13694 invoked by uid 48); 8 Jul 2019 20:13:54 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91109] [10 regression][arm] gcc.c-torture/execute/20040709-1.c fails since r273135
Date: Mon, 08 Jul 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: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91109-4-xOZHTpaLgr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91109-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91109-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00618.txt.bz2
Content-length: 396
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91109
--- Comment #2 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Removing the test*() calls from the end, the first failing one is testX().
However, if I remove all the preceding ones, the test passes.
Using -fwhole-program instead of -flto has no effect: the test still fails.
Adding a printf() call in check() also makes the test pass.
>From gcc-bugs-return-648507-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 20:23:26 2019
Return-Path: <gcc-bugs-return-648507-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94913 invoked by alias); 8 Jul 2019 20: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 94849 invoked by uid 48); 8 Jul 2019 20:23:22 -0000
From: "paolo.carlini at oracle dot com" <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: Mon, 08 Jul 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: c++
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo.carlini at oracle 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91073-4-4vAuzQpWWq@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-07/txt/msg00619.txt.bz2
Content-length: 536
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91073
--- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> ---
In principle the issue is rather simple. The
cp_parser_maybe_commit_to_declaration at the beginning of cp_parser_condition
since r260482 thinks erroneously that the just parsed HasInit<decltype(foo),
int> must be a declaration. In practice, I'm still not sure which is the best
way to solve this... well, I'm not even sure we are supposed to actively work
now on relatively minor concept-related issues.
>From gcc-bugs-return-648508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 20:39:21 2019
Return-Path: <gcc-bugs-return-648508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122703 invoked by alias); 8 Jul 2019 20:39: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 122651 invoked by uid 55); 8 Jul 2019 20:39:18 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88233] combine fails to merge insns leaving unneeded reg copies
Date: Mon, 08 Jul 2019 20:39: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.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88233-4-aGmOh0glvQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88233-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88233-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00620.txt.bz2
Content-length: 636
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88233
--- Comment #4 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Author: segher
Date: Mon Jul 8 20:38:46 2019
New Revision: 273245
URL: https://gcc.gnu.org/viewcvs?rev=273245&root=gcc&view=rev
Log:
rs6000: Add testcase for PR88233
This testcase tests that with -mcpu=power8 we do not generate any
mtvsr* instructions, and we do the copy with {l,st}xvd2x.
gcc/testsuite/
PR rtl-optimization/88233
* gcc.target/powerpc/pr88233.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.target/powerpc/pr88233.c
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-648509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 20:48:07 2019
Return-Path: <gcc-bugs-return-648509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16284 invoked by alias); 8 Jul 2019 20:48: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 16152 invoked by uid 48); 8 Jul 2019 20:48:02 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91116] New: bad register choices for rs6000 -m32
Date: Mon, 08 Jul 2019 20:48: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: 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-91116-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00621.txt.bz2
Content-length: 1072
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91116
Bug ID: 91116
Summary: bad register choices for rs6000 -m32
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: segher at gcc dot gnu.org
Target Milestone: ---
In the new testcase pr88233.c, which is
typedef struct { double a[2]; } A;
A
foo (const A *a)
{
return *a;
}
we currently get as generated code for -m32
addi 10,4,4
lfiwzx 10,0,4
addi 9,3,12
lfiwzx 11,0,10
addi 10,4,8
lfiwzx 12,0,10
addi 10,4,12
stfiwx 10,0,3
lfiwzx 0,0,10
addi 10,3,4
stfiwx 11,0,10
addi 10,3,8
stfiwx 12,0,10
stfiwx 0,0,9
blr
Expand decides to do this as four SImode copies, which isn't such a great
idea, of course; but RA thinks it is cost 0 to put a SImode in an FP or
altivec register. That won't fly.
>From gcc-bugs-return-648510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 22:03:43 2019
Return-Path: <gcc-bugs-return-648510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39817 invoked by alias); 8 Jul 2019 22: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 39725 invoked by uid 48); 8 Jul 2019 22:03:39 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61339] add mismatch between struct and class [-Wmismatched-tags] to non-bugs
Date: Mon, 08 Jul 2019 22: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: 4.9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: enhancement
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-61339-4-JTcJsCKg59@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61339-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61339-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00622.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61339
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2019-07/msg00621.html
>From gcc-bugs-return-648511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 22:09:01 2019
Return-Path: <gcc-bugs-return-648511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89501 invoked by alias); 8 Jul 2019 22:09: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 89447 invoked by uid 55); 8 Jul 2019 22:08:58 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91110] [10 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in cp_omp_mappable_type_1, at cp/decl2.c:1421
Date: Mon, 08 Jul 2019 22: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: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91110-4-IVhDa3eZQ8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91110-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91110-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00623.txt.bz2
Content-length: 572
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91110
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Jul 8 22:08:27 2019
New Revision: 273248
URL: https://gcc.gnu.org/viewcvs?rev=273248&root=gcc&view=rev
Log:
PR c++/91110
* decl2.c (cp_omp_mappable_type_1): Don't emit any note for
error_mark_node type.
* g++.dg/gomp/pr91110.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/gomp/pr91110.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/decl2.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-648512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 08 22:31:45 2019
Return-Path: <gcc-bugs-return-648512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127689 invoked by alias); 8 Jul 2019 22:31: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 125757 invoked by uid 48); 8 Jul 2019 22:31:41 -0000
From: "wolfwings+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91117] New: _mm_movpi64_epi64/_mm_movepi64_pi64 generating store+load instead of using MOVQ2DQ/MOVDQ2Q
Date: Mon, 08 Jul 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: target
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wolfwings+gcc 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-91117-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00624.txt.bz2
Content-length: 2428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91117
Bug ID: 91117
Summary: _mm_movpi64_epi64/_mm_movepi64_pi64 generating
store+load instead of using MOVQ2DQ/MOVDQ2Q
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: wolfwings+gcc at gmail dot com
Target Milestone: ---
_mm_movpi64_epi64 is never using MOVQ2DQ (and _mm_movepi64_pi64 never using
MOVDQ2Q) despite documentation it should when used in mixed MMX -> SSE
situations, and that these are in fact the intrinsics to use when desiring the
Q2DQ/DQ2Q opcodes.
This appears to be due to the header defining them causing fallback memory
write then read except in (technically invalid) SSE -> SSE cases where a MOVD
is used.
Tested on GCC 7.4 + 9.1 locally, with additional testing on Godbolt all showing
identical code being generated all the way back to 4.x series.
Compiled with -O1:
#include <emmintrin.h>
__m128i test( __m128i input ) {
__m64 x = _mm_movepi64_pi64( input );
return _mm_movpi64_epi64( _mm_mullo_pi16( x, x ) );
}
Generated assembly on GCC 9.1:
movq %xmm0, -16(%rsp)
movq -16(%rsp), %mm0
movq %mm0, %mm1
pmullw %mm0, %mm1
movq %mm1, -16(%rsp)
movq -16(%rsp), %xmm0
ret
A version that makes explicit calls to movq2dq/movdq2q works and outputs the
expected assembly sequence:
#include <emmintrin.h>
static inline __m64 _my_movepi64_pi64( __m128i input ) {
__m64 result;
asm( "movdq2q %1, %0" : "=y" (result) : "x" (input) : );
return result;
}
static inline __m128i _my_movpi64_epi64( __m64 input ) {
__m128i result;
asm( "movq2dq %1, %0" : "=x" (result) : "y" (input) : );
return result;
}
__m128i test( __m128i input ) {
__m64 x = _my_movepi64_pi64( input );
return _my_movpi64_epi64( _mm_mullo_pi16( x, x ) );
}
Generated assembly on GCC 7.4, 9.1, and others via Godbolt, again with -O1 (-O2
and -O3 make no difference):
movdq2q %xmm0, %mm0
pmullw %mm0, %mm0
movq2dq %mm0, %xmm0
ret
For completeness, ICC generates the 'short' code form on all available versions
without needing the inline assembly workaround.
>From gcc-bugs-return-648513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 01:08:17 2019
Return-Path: <gcc-bugs-return-648513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129083 invoked by alias); 9 Jul 2019 01:08: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 129060 invoked by uid 48); 9 Jul 2019 01:08:13 -0000
From: "alan.avbs at rocketmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91118] New: ubsan does not work with openmp default (none) directive
Date: Tue, 09 Jul 2019 01:08: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.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: alan.avbs at rocketmail 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-91118-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00625.txt.bz2
Content-length: 1389
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91118
Bug ID: 91118
Summary: ubsan does not work with openmp default (none)
directive
Product: gcc
Version: 9.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: alan.avbs at rocketmail dot com
Target Milestone: ---
Program fails to compile when using -fsanitize=undefined and using
the directive default(none) in a parallel region.
For instance:
#include <iostream>
int main()
{
#pragma omp parallel default(none) shared(std::cerr)
{
std::cerr<<"hello"<<std::endl;
}
return 0;
}
Fails to compile with error:
test.cc: In function ‘int main()’:
test.cc:7:28: error: ‘_ZTISo’ not specified in enclosing ‘parallel’
7 | std::cerr<<"hello"<<std::endl;
| ^~~~
test.cc:5:9: error: enclosing ‘parallel’
5 | #pragma omp parallel default(none) shared(std::cerr)
|
The code works with previous g++ versions. However I am aware of the change in
behavior as documented
here(https://www.gnu.org/software/gcc/gcc-9/porting_to.html). Also there is a
similar bug opened some years ago (#64888).
>From gcc-bugs-return-648514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 01:16:03 2019
Return-Path: <gcc-bugs-return-648514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8608 invoked by alias); 9 Jul 2019 01: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 8462 invoked by uid 48); 9 Jul 2019 01:15:54 -0000
From: "peter at cordes dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91103] AVX512 vector element extract uses more than 1 shuffle instruction; VALIGND can grab any element
Date: Tue, 09 Jul 2019 01: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: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: peter at cordes dot ca
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-91103-4-0dsPjovjDN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91103-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91103-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00626.txt.bz2
Content-length: 3599
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91103
--- Comment #4 from Peter Cordes <peter at cordes dot ca> ---
We should not put any stock in what ICC does for GNU C native vector indexing.
I think it doesn't know how to optimize that because it *always* spills/reloads
even for `vec[0]` which could be a no-op. And it's always a full-width spill
(ZMM), not just the low XMM/YMM part that contains the desired element. I
mainly mentioned ICC in my initial post to suggest the store/reload strategy in
general as an *option*.
ICC also doesn't optimize intriniscs: it pretty much always faithfully
transliterates them to asm. e.g. v = _mm_add_epi32(v, _mm_set1_epi32(1));
twice compiles to two separate paddd instructions, instead of one with a
constant of set1(2).
If we want to see ICC's strided-store strategy, we'd need to write some pure C
that auto-vectorizes.
----
That said, store/reload is certainly a valid option when we want all the
elements, and gets *more* attractive with wider vectors, where the one extra
store amortizes over more elements.
Strided stores will typically bottleneck on cache/memory bandwidth unless the
destination lines are already hot in L1d. But if there's other work in the
loop, we care about OoO exec of that work with the stores, so uop throughput
could be a factor.
If we're tuning for Intel Haswell/Skylake with 1 per clock shuffles but 2 loads
+ 1 store per clock throughput (if we avoid indexed addressing modes for
stores), then it's very attractive and unlikely to be a bottleneck.
There's typically spare load execution-unit cycles in a loop that's also doing
stores + other work. You need every other uop to be (or include) a load to
bottleneck on that at 4 uops per clock, unless you have indexed stores (which
can't run on the simple store-AGU on port 7 and need to run on port 2/3, taking
a cycle from a load). Cache-split loads do get replayed to grab the 2nd half,
so it costs extra execution-unit pressure as well as extra cache-read cycles.
Intel says Ice will have 2 load + 2 store pipes, and a 2nd shuffle unit. A
mixed strategy there might be interesting: extract the high 256 bits to memory
with vextractf32x8 and reload it, but shuffle the low 128/256 bits. That
strategy might be good on earlier CPUs, too. At least with movss + extractps
stores from the low XMM where we can do that directly.
AMD before Ryzen 2 has only 2 AGUs, so only 2 memory ops per clock, up to one
of which can be a store. It's definitely worth considering extracting the high
128-bit half of a YMM and using movss then shuffles like vextractps: 2 uops on
Ryzen or AMD.
-----
If the stride is small enough (so more than 1 element fits in a vector), we
should consider shuffle + vmaskmovps masked stores, or with AVX512 then
AVX512 masked stores.
But for larger strides, AVX512 scatter may get better in the future. It's
currently (SKX) 43 uops for VSCATTERDPS or ...DD ZMM, so not very friendly to
surrounding code. It sustains one per 17 clock throughput, slightly worse than
1 element stored per clock cycle. Same throughput on KNL, but only 4 uops so
it can overlap much better with surrounding code.
----
For qword elements, we have efficient stores of the high or low half of an XMM.
A MOVHPS store doesn't need a shuffle uop on most Intel CPUs. So we only need
1 (YMM) or 3 (ZMM) shuffles to get each of the high 128-bit lanes down to an
XMM register.
Unfortunately on Ryzen, MOVHPS [mem], xmm costs a shuffle+store. But Ryzen has
shuffle EUs on multiple ports.
>From gcc-bugs-return-648515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 04:15:49 2019
Return-Path: <gcc-bugs-return-648515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17463 invoked by alias); 9 Jul 2019 04:15: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 17067 invoked by uid 48); 9 Jul 2019 04:15:40 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64867] split warning for passing non-POD to varargs function from -Wconditionally-supported into new warning flag, -Wnon-pod-varargs
Date: Tue, 09 Jul 2019 04: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: unknown
X-Bugzilla-Keywords: diagnostic, easyhack
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: cc
Message-ID: <bug-64867-4-bBs7zpJNPV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64867-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00627.txt.bz2
Content-length: 475
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64867
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #26 from Eric Gallager <egallager at gcc dot gnu.org> ---
Martin Sebor has been doing stuff related to warnings about POD-ness lately;
cc-ing him
>From gcc-bugs-return-648517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 04:16:21 2019
Return-Path: <gcc-bugs-return-648517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18499 invoked by alias); 9 Jul 2019 04:16: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 18397 invoked by uid 55); 9 Jul 2019 04:16:17 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/71924] missing -Wreturn-local-addr returning alloca result
Date: Tue, 09 Jul 2019 04: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: 7.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: enhancement
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-71924-4-prk3gCRDdR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71924-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71924-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00629.txt.bz2
Content-length: 2754
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71924
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Tue Jul 9 04:15:42 2019
New Revision: 273261
URL: https://gcc.gnu.org/viewcvs?rev=273261&root=gcc&view=rev
Log:
PR middle-end/71924 - missing -Wreturn-local-addr returning alloca result
PR middle-end/90549 - missing -Wreturn-local-addr maybe returning an address of
a local array plus offset
gcc/ChangeLog:
PR middle-end/71924
PR middle-end/90549
* gimple-ssa-isolate-paths.c (isolate_path): Add attribute. Update
comment.
(args_loc_t): New type.
(args_loc_t, locmap_t): same.
(diag_returned_locals): New function.
(is_addr_local): Same.
(handle_return_addr_local_phi_arg, warn_return_addr_local): Same.
(find_implicit_erroneous_behavior): Call
warn_return_addr_local_phi_arg.
(find_explicit_erroneous_behavior): Call warn_return_addr_local.
gcc/testsuite/ChangeLog:
PR middle-end/71924
PR middle-end/90549
* gcc.c-torture/execute/return-addr.c: New test.
* gcc.dg/Wreturn-local-addr-2.c: New test.
* gcc.dg/Wreturn-local-addr-4.c: New test.
* gcc.dg/Wreturn-local-addr-5.c: New test.
* gcc.dg/Wreturn-local-addr-6.c: New test.
* gcc.dg/Wreturn-local-addr-7.c: New test.
* gcc.dg/Wreturn-local-addr-8.c: New test.
* gcc.dg/Wreturn-local-addr-9.c: New test.
* gcc.dg/Wreturn-local-addr-10.c: New test.
* gcc.dg/Walloca-4.c: Handle expected warnings.
* gcc.dg/pr41551.c: Same.
* gcc.dg/pr59523.c: Same.
* gcc.dg/tree-ssa/pr88775-2.c: Same.
* gcc.dg/tree-ssa/alias-37.c: Same.
* gcc.dg/winline-7.c: Same.
Added:
trunk/gcc/testsuite/gcc.c-torture/execute/return-addr.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-10.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-2.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-3.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-4.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-5.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-6.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-7.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-8.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-9.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/gimple-ssa-isolate-paths.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/Walloca-4.c
trunk/gcc/testsuite/gcc.dg/pr41551.c
trunk/gcc/testsuite/gcc.dg/pr59523.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/alias-37.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr88775-2.c
trunk/gcc/testsuite/gcc.dg/winline-7.c
trunk/libgcc/generic-morestack.c
>From gcc-bugs-return-648516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 04:16:21 2019
Return-Path: <gcc-bugs-return-648516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18453 invoked by alias); 9 Jul 2019 04:16: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 18403 invoked by uid 55); 9 Jul 2019 04:16:17 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90549] missing -Wreturn-local-addr maybe returning an address of a local array plus offset
Date: Tue, 09 Jul 2019 04:16: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-90549-4-kzVaBdsRR9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90549-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90549-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00628.txt.bz2
Content-length: 2754
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90549
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Tue Jul 9 04:15:42 2019
New Revision: 273261
URL: https://gcc.gnu.org/viewcvs?rev=273261&root=gcc&view=rev
Log:
PR middle-end/71924 - missing -Wreturn-local-addr returning alloca result
PR middle-end/90549 - missing -Wreturn-local-addr maybe returning an address of
a local array plus offset
gcc/ChangeLog:
PR middle-end/71924
PR middle-end/90549
* gimple-ssa-isolate-paths.c (isolate_path): Add attribute. Update
comment.
(args_loc_t): New type.
(args_loc_t, locmap_t): same.
(diag_returned_locals): New function.
(is_addr_local): Same.
(handle_return_addr_local_phi_arg, warn_return_addr_local): Same.
(find_implicit_erroneous_behavior): Call
warn_return_addr_local_phi_arg.
(find_explicit_erroneous_behavior): Call warn_return_addr_local.
gcc/testsuite/ChangeLog:
PR middle-end/71924
PR middle-end/90549
* gcc.c-torture/execute/return-addr.c: New test.
* gcc.dg/Wreturn-local-addr-2.c: New test.
* gcc.dg/Wreturn-local-addr-4.c: New test.
* gcc.dg/Wreturn-local-addr-5.c: New test.
* gcc.dg/Wreturn-local-addr-6.c: New test.
* gcc.dg/Wreturn-local-addr-7.c: New test.
* gcc.dg/Wreturn-local-addr-8.c: New test.
* gcc.dg/Wreturn-local-addr-9.c: New test.
* gcc.dg/Wreturn-local-addr-10.c: New test.
* gcc.dg/Walloca-4.c: Handle expected warnings.
* gcc.dg/pr41551.c: Same.
* gcc.dg/pr59523.c: Same.
* gcc.dg/tree-ssa/pr88775-2.c: Same.
* gcc.dg/tree-ssa/alias-37.c: Same.
* gcc.dg/winline-7.c: Same.
Added:
trunk/gcc/testsuite/gcc.c-torture/execute/return-addr.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-10.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-2.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-3.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-4.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-5.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-6.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-7.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-8.c
trunk/gcc/testsuite/gcc.dg/Wreturn-local-addr-9.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/gimple-ssa-isolate-paths.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/Walloca-4.c
trunk/gcc/testsuite/gcc.dg/pr41551.c
trunk/gcc/testsuite/gcc.dg/pr59523.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/alias-37.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr88775-2.c
trunk/gcc/testsuite/gcc.dg/winline-7.c
trunk/libgcc/generic-morestack.c
>From gcc-bugs-return-648519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 04:16:54 2019
Return-Path: <gcc-bugs-return-648519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19875 invoked by alias); 9 Jul 2019 04:16: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 19819 invoked by uid 48); 9 Jul 2019 04:16:51 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90556] [meta-bug] bogus/missing -Wreturn-local-addr
Date: Tue, 09 Jul 2019 04:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_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: 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-90556-4-lUkO4771ln@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90556-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90556-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00631.txt.bz2
Content-length: 477
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90556
Bug 90556 depends on bug 71924, which changed state.
Bug 71924 Summary: missing -Wreturn-local-addr returning alloca result
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71924
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-648518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 04:16:54 2019
Return-Path: <gcc-bugs-return-648518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19854 invoked by alias); 9 Jul 2019 04: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 19793 invoked by uid 48); 9 Jul 2019 04:16:47 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/71924] missing -Wreturn-local-addr returning alloca result
Date: Tue, 09 Jul 2019 04: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: 7.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: enhancement
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 target_milestone
Message-ID: <bug-71924-4-k9kIAxpno0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71924-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71924-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00630.txt.bz2
Content-length: 498
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71924
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.0
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch committed in r273261.
>From gcc-bugs-return-648521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 04:19:08 2019
Return-Path: <gcc-bugs-return-648521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22576 invoked by alias); 9 Jul 2019 04:19: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 22484 invoked by uid 48); 9 Jul 2019 04:19:05 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90556] [meta-bug] bogus/missing -Wreturn-local-addr
Date: Tue, 09 Jul 2019 04:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_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: 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-90556-4-2V8zizDMZJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90556-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90556-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00633.txt.bz2
Content-length: 511
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90556
Bug 90556 depends on bug 90549, which changed state.
Bug 90549 Summary: missing -Wreturn-local-addr maybe returning an address of a local array plus offset
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90549
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-648520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 04:19:08 2019
Return-Path: <gcc-bugs-return-648520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22523 invoked by alias); 9 Jul 2019 04:19: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 22465 invoked by uid 48); 9 Jul 2019 04:19:04 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90549] missing -Wreturn-local-addr maybe returning an address of a local array plus offset
Date: Tue, 09 Jul 2019 04:19: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: 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 target_milestone
Message-ID: <bug-90549-4-7g3zClH1Vc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90549-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90549-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00632.txt.bz2
Content-length: 1117
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90549
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.0
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
Fixed via r273261. Both functions in the test case are now diagnosed:
pr90549.c: In function ‘f’:
pr90549.c:7:10: warning: function may return address of local variable
[-Wreturn-local-addr]
7 | return p; // -Wreturn-local-addr (good)
| ^
pr90549.c:5:7: note: declared here
5 | int b[2];
| ^
pr90549.c: In function ‘g’:
pr90549.c:15:12: warning: function may return address of local variable
[-Wreturn-local-addr]
15 | return p + 1; // missing -Wreturn-local-addr
| ~~^~~
pr90549.c:12:7: note: declared here
12 | int b[2];
| ^
>From gcc-bugs-return-648522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 06:17:48 2019
Return-Path: <gcc-bugs-return-648522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81254 invoked by alias); 9 Jul 2019 06: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 81222 invoked by uid 48); 9 Jul 2019 06:17:45 -0000
From: "me at adhokshajmishraonline dot in" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91119] New: Bogus type re-difinition error
Date: Tue, 09 Jul 2019 06: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: me at adhokshajmishraonline dot in
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-91119-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00634.txt.bz2
Content-length: 1888
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91119
Bug ID: 91119
Summary: Bogus type re-difinition error
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: me at adhokshajmishraonline dot in
Target Milestone: ---
Test code
---------
class A {};
class B {
using C = A;
enum D {
A,
};
};
When the above code is compiled using g++ (g++ -c test.cpp -o test.o), the
compiler produces the following output:
â•â”€ adhokshajmishra@andromeda î‚° in /tmp î‚°
╰─➤ g++ -c test.cpp -o test.o
test.cpp:7:9: error: declaration of ‘A’ changes meaning of ‘A’ [-fpermissive]
7 | A,
| ^
test.cpp:1:7: note: ‘A’ declared here as ‘class A’
1 | class A {};
| ^
If the same code is compiled with clang, there is no error produced. The
following workaround seems to work:
class A {};
class B {
using C = ::A;
enum D {
A,
};
};
As far as I know, original test code is correct as per C++11 standard:
<quote>
A class name (9.1) or enumeration name (7.2) can be hidden by the name of a
variable, data member, function, or enumerator declared in the same scope. If a
class or enumeration name and a variable, data member, function, or enumerator
are declared in the same scope (in any order) with the same name, the class or
enumeration name is hidden wherever the variable, data member, function, or
enumerator name is visible.
</quote>
>From gcc-bugs-return-648523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 06:23:04 2019
Return-Path: <gcc-bugs-return-648523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85218 invoked by alias); 9 Jul 2019 06:23: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 85198 invoked by uid 48); 9 Jul 2019 06:23:01 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91119] Bogus type re-difinition error
Date: Tue, 09 Jul 2019 06:23: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:
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-91119-4-6a3fn4gxci@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91119-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91119-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00635.txt.bz2
Content-length: 237
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91119
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
No GCC is correct. There is another section which you missed made this code
invalid but no diagnostic is required.
>From gcc-bugs-return-648524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 06:26:00 2019
Return-Path: <gcc-bugs-return-648524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87634 invoked by alias); 9 Jul 2019 06:26: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 87624 invoked by uid 48); 9 Jul 2019 06:25:57 -0000
From: "me at adhokshajmishraonline dot in" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91119] Bogus type re-difinition error
Date: Tue, 09 Jul 2019 06: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: me at adhokshajmishraonline dot in
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-91119-4-UEtfPnivIs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91119-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91119-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00636.txt.bz2
Content-length: 368
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91119
--- Comment #2 from Adhokshaj Mishra <me at adhokshajmishraonline dot in> ---
(In reply to Andrew Pinski from comment #1)
> No GCC is correct. There is another section which you missed made this code
> invalid but no diagnostic is required.
Can you please point to the section which makes this code invalid?
>From gcc-bugs-return-648525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 06:40:56 2019
Return-Path: <gcc-bugs-return-648525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119424 invoked by alias); 9 Jul 2019 06:40: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 119393 invoked by uid 48); 9 Jul 2019 06:40:53 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91115] stack-buffer-overflow on memset local variable when creating thread on ARM Linux
Date: Tue, 09 Jul 2019 06:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.3.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 everconfirmed
Message-ID: <bug-91115-4-M050usB46w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91115-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91115-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00637.txt.bz2
Content-length: 752
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91115
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-07-09
Ever confirmed|0 |1
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Would it be please possible to provide a test-case?
Note that memset is aware of shadow memory and it should properly mark it. You
can also do a debugging session where you can put a hardware breakpoint to the
shadow memory location which then causes the ASAN error.
>From gcc-bugs-return-648526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 07:44:50 2019
Return-Path: <gcc-bugs-return-648526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72153 invoked by alias); 9 Jul 2019 07:44: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 72086 invoked by uid 48); 9 Jul 2019 07:44:45 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91103] AVX512 vector element extract uses more than 1 shuffle instruction; VALIGND can grab any element
Date: Tue, 09 Jul 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: 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: 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-91103-4-6C2HK6p9F0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91103-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91103-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00638.txt.bz2
Content-length: 933
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91103
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-09
Ever confirmed|0 |1
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Thanks for the detailed analysis - currently the vectorizer makes N explicit
element extracts and N explicit scalar stores. That's not very friendly for
the targets to generate the kind of mixed code from. I'm thinking of
somehow generalizing how we represent strided stores similar to scatters
but in a way making the index vector implicitely specified by an affine
combination (constant * reg). It probably needs another set of expanders
for that though.
>From gcc-bugs-return-648527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 07:47:24 2019
Return-Path: <gcc-bugs-return-648527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78717 invoked by alias); 9 Jul 2019 07:47: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 78670 invoked by uid 48); 9 Jul 2019 07:47:20 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91114] [10 Regression] ICE in vect_analyze_loop, at tree-vect-loop.c:2415
Date: Tue, 09 Jul 2019 07: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: ice-checking, ice-on-valid-code, openmp
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-91114-4-ajauyWAXE3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00639.txt.bz2
Content-length: 568
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91114
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
Target Milestone|--- |10.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
if (fatal)
{
gcc_checking_assert (first_loop_vinfo == NULL);
probably caused by Jakubs recent change?
>From gcc-bugs-return-648528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 07:48:42 2019
Return-Path: <gcc-bugs-return-648528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82891 invoked by alias); 9 Jul 2019 07:48: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 82798 invoked by uid 48); 9 Jul 2019 07:48:29 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91112] [8 Regression] Bad error message for virtual function of a template class. Wrong "required from here" line number
Date: Tue, 09 Jul 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: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords target_milestone
Message-ID: <bug-91112-4-ocvMYhy9c8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91112-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91112-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00640.txt.bz2
Content-length: 353
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91112
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Target Milestone|--- |8.4
>From gcc-bugs-return-648529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 07:54:30 2019
Return-Path: <gcc-bugs-return-648529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112582 invoked by alias); 9 Jul 2019 07:54: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 112013 invoked by uid 48); 9 Jul 2019 07:54:25 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91114] [10 Regression] ICE in vect_analyze_loop, at tree-vect-loop.c:2415
Date: Tue, 09 Jul 2019 07: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-checking, ice-on-valid-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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work everconfirmed cf_known_to_fail
Message-ID: <bug-91114-4-5fWeiKEHxn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00641.txt.bz2
Content-length: 757
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91114
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-09
CC| |marxin at gcc dot gnu.org,
| |uros at gcc dot gnu.org
Known to work| |9.1.1
Ever confirmed|0 |1
Known to fail| |10.0
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r272711.
>From gcc-bugs-return-648530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 07:59:16 2019
Return-Path: <gcc-bugs-return-648530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7004 invoked by alias); 9 Jul 2019 07: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 6955 invoked by uid 48); 9 Jul 2019 07:59:13 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91083] inconsistent -Wsign-compare warnings
Date: Tue, 09 Jul 2019 07: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.1.0
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-91083-4-uoA1TV9oya@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91083-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91083-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00642.txt.bz2
Content-length: 649
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91083
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-09
CC| |jason 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> ---
Started with r270136.
>From gcc-bugs-return-648531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 08:04:46 2019
Return-Path: <gcc-bugs-return-648531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20653 invoked by alias); 9 Jul 2019 08:04: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 20611 invoked by uid 48); 9 Jul 2019 08:04:42 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91117] _mm_movpi64_epi64/_mm_movepi64_pi64 generating store+load instead of using MOVQ2DQ/MOVDQ2Q
Date: Tue, 09 Jul 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: target
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak 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-91117-4-IQB4DmBnGc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91117-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91117-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00643.txt.bz2
Content-length: 741
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91117
--- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
The generated code is created the way it is partially by design, and partially
by missing (!y,*x) alternative in *vec_extractv2di_0_sse. GCC lowers intrinsics
to generic operations, and this has its pluses (generic optimizations can be
used) and minuses. For the later, generic operations should avoid to allocate
MMX registers unless absolutely necessary, and the compiler discourages their
use by penalizing operations (moves) involving MMX registers.
gcc-10 emulates MMX operations using SSE instructions, so your code gets
compiled to:
pmullw %xmm0, %xmm0
movq %xmm0, %xmm0
ret
>From gcc-bugs-return-648532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 08:10:17 2019
Return-Path: <gcc-bugs-return-648532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54308 invoked by alias); 9 Jul 2019 08:10: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 54262 invoked by uid 48); 9 Jul 2019 08:10:14 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91114] [10 Regression] ICE in vect_analyze_loop, at tree-vect-loop.c:2415
Date: Tue, 09 Jul 2019 08: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-checking, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91114-4-8VBbEVbyN1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00644.txt.bz2
Content-length: 258
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91114
--- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Martin Liška from comment #2)
> Started with r272711.
This revision just exposes a generic issue in tree vectorizer.
>From gcc-bugs-return-648533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 08:40:25 2019
Return-Path: <gcc-bugs-return-648533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5594 invoked by alias); 9 Jul 2019 08:40: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 5560 invoked by uid 48); 9 Jul 2019 08:40:22 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91119] Bogus type re-difinition error
Date: Tue, 09 Jul 2019 08:40: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:
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-91119-4-DtwgQShCRt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91119-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91119-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00645.txt.bz2
Content-length: 643
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91119
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> ---
[basic.scope.class] paragraph 2:
"A name N used in a class S shall refer to the same declaration in its context
and when re-evaluated in the completed scope of S. No diagnostic is required
for a violation of this rule."
>From gcc-bugs-return-648535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 09:24:53 2019
Return-Path: <gcc-bugs-return-648535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103004 invoked by alias); 9 Jul 2019 09: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 102770 invoked by uid 48); 9 Jul 2019 09:24:49 -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: Tue, 09 Jul 2019 09:24: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-miu2cqPsMx@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-07/txt/msg00647.txt.bz2
Content-length: 482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 91071, which changed state.
Bug 91071 Summary: [10 Regression] Miscompare of 410.bwaves since r272644
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91071
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
>From gcc-bugs-return-648534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 09:24:52 2019
Return-Path: <gcc-bugs-return-648534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102913 invoked by alias); 9 Jul 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 102583 invoked by uid 48); 9 Jul 2019 09:24:45 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91071] [10 Regression] Miscompare of 410.bwaves since r272644
Date: Tue, 09 Jul 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: 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: RESOLVED
X-Bugzilla-Resolution: WONTFIX
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-91071-4-C7H0gtDzgZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91071-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91071-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00646.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91071
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
Closing ..
>From gcc-bugs-return-648536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 10:03:19 2019
Return-Path: <gcc-bugs-return-648536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127478 invoked by alias); 9 Jul 2019 10:03: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 127101 invoked by uid 48); 9 Jul 2019 10:03:12 -0000
From: "development at jordi dot vilar.cat" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91120] New: broken template instantiation for std::string_view values
Date: Tue, 09 Jul 2019 10: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: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: development at jordi dot vilar.cat
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-91120-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00648.txt.bz2
Content-length: 904
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91120
Bug ID: 91120
Summary: broken template instantiation for std::string_view
values
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: development at jordi dot vilar.cat
Target Milestone: ---
The following code fails to compile with gcc 9.1 and -std=c++2a:
#include <string_view>
using namespace std::string_view_literals;
template<std::string_view> struct test_type {};
auto test = test_type<""sv>{};
reporting the following diagnostics message:
error: '""' is not a valid template argument of type 'const char*' because '""'
is not a variable
using other literal types (integral types, std::array, etc.) seems to work.
>From gcc-bugs-return-648537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 10:51:44 2019
Return-Path: <gcc-bugs-return-648537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49095 invoked by alias); 9 Jul 2019 10:51: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 49055 invoked by uid 48); 9 Jul 2019 10:51:41 -0000
From: "gcc-bugs at marehr dot dialup.fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91121] New: ICE with type deduction guides and CRTP base class
Date: Tue, 09 Jul 2019 10:51: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: gcc-bugs at marehr dot dialup.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
Message-ID: <bug-91121-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00649.txt.bz2
Content-length: 2060
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91121
Bug ID: 91121
Summary: ICE with type deduction guides and CRTP base class
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc-bugs at marehr dot dialup.fu-berlin.de
Target Milestone: ---
Hello gcc-team,
the following code will ICE
```c++
template <typename> struct a { a(int); };
template <typename> struct b : a<b<int>> { using a<b>::a; };
template <typename c> b(c)->b<c>;
struct e {
template <typename d> e(d);
} e{b{2}};
```
with
```
> g++-git -std=c++17 ice.cpp
ice.cpp:6:8: internal compiler error: Segmentation fault
6 | } e{b{2}};
| ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
```
gcc version:
```
g++-git -v
Using built-in specs.
COLLECT_GCC=g++-git
COLLECT_LTO_WRAPPER=/opt/gcc/gcc-git/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /home/marehr/Packages/gcc-git/src/gcc/configure --prefix=/usr
--libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared
--enable-threads=posix --with-system-zlib --with-isl --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch
--disable-libssp --enable-gnu-unique-object --enable-linker-build-id
--enable-lto --enable-plugin --enable-install-libiberty
--with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib
--disable-werror --enable-checking=release --enable-default-pie
--enable-default-ssp --enable-cet=auto
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.0.0 20190709 (experimental) (GCC)
```
Thank you!
>From gcc-bugs-return-648538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 10:55:50 2019
Return-Path: <gcc-bugs-return-648538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52397 invoked by alias); 9 Jul 2019 10:55: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 52369 invoked by uid 48); 9 Jul 2019 10:55:47 -0000
From: "gcc-bugs at marehr dot dialup.fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91121] ICE with type deduction guides and CRTP base class
Date: Tue, 09 Jul 2019 10: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: gcc-bugs at marehr dot dialup.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-91121-4-nXckDtv2j5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91121-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91121-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00650.txt.bz2
Content-length: 205
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91121
--- Comment #1 from gcc-bugs at marehr dot dialup.fu-berlin.de ---
Oh it might be the same one as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90764
>From gcc-bugs-return-648539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 11:16:05 2019
Return-Path: <gcc-bugs-return-648539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85556 invoked by alias); 9 Jul 2019 11:16: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 85340 invoked by uid 48); 9 Jul 2019 11:15:41 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91114] [10 Regression] ICE in vect_analyze_loop, at tree-vect-loop.c:2415
Date: Tue, 09 Jul 2019 11:16: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-checking, ice-on-valid-code, openmp
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: bug_status assigned_to
Message-ID: <bug-91114-4-NdjZWZpJvw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00651.txt.bz2
Content-length: 969
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91114
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 #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the assert says that 'fatal' issues should pop up with _all_ vector sizes.
This is to avoid missed optimizations where the first tried one says 'fatal'
but a later tried one would not (so it's not a correctness assert).
So the first run with vector size 16 doesn't fail fatally but the second with
vector_size 8 does because there isn't a vector type to vectorize 'double'
(so we don't consider V1DF in mode_for_vector (inner_mode, nunits)).
So having a vector type for some stmt isn't really a fatal error.
>From gcc-bugs-return-648540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 11:21:25 2019
Return-Path: <gcc-bugs-return-648540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89480 invoked by alias); 9 Jul 2019 11:21: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 89401 invoked by uid 48); 9 Jul 2019 11:21:21 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91114] [10 Regression] ICE in vect_analyze_loop, at tree-vect-loop.c:2415
Date: Tue, 09 Jul 2019 11: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-checking, ice-on-valid-code, openmp
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-91114-4-MgELcOYli0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00652.txt.bz2
Content-length: 1218
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91114
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Index: gcc/tree-vect-data-refs.c
===================================================================
--- gcc/tree-vect-data-refs.c (revision 273294)
+++ gcc/tree-vect-data-refs.c (working copy)
@@ -4360,6 +4360,8 @@ vect_analyze_data_refs (vec_info *vinfo,
STMT_VINFO_VECTORIZABLE (stmt_info) = false;
continue;
}
+ if (fatal)
+ *fatal = false;
return opt_result::failure_at (stmt_info->stmt,
"not vectorized:"
" no vectype for stmt: %G"
fixes the ICE. In reality we'd want to see whether there is _any_
vector type we could use here and fail fatally if there isn't any,
also recording constraints like a minimum vector size. But then the
whole scheme iterating over sizes is not something we'd want to preserve
forever (we want to conciously use multiple sizes in the same loop when
applicable).
>From gcc-bugs-return-648541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 11:36:37 2019
Return-Path: <gcc-bugs-return-648541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117032 invoked by alias); 9 Jul 2019 11:36: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 116910 invoked by uid 55); 9 Jul 2019 11:36:32 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91109] [10 regression][arm] gcc.c-torture/execute/20040709-1.c fails since r273135
Date: Tue, 09 Jul 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:
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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91109-4-1cm6Oa0bA7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91109-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91109-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00653.txt.bz2
Content-length: 1273
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91109
--- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 8 Jul 2019, clyon at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91109
>
> --- Comment #2 from Christophe Lyon <clyon at gcc dot gnu.org> ---
> Removing the test*() calls from the end, the first failing one is testX().
> However, if I remove all the preceding ones, the test passes.
Ugh. Not very much simplification. I suppose trying to trim the
number of test() calls before testX() isn't possible?
> Using -fwhole-program instead of -flto has no effect: the test still fails.
That's good news OTOH and simplifies analysis.
> Adding a printf() call in check() also makes the test pass.
test##S you mean probably. But yes, that's expected.
Given there's no regression with hard float having testW () might
be important (uses long double). There may be also ABI differences
(sizeof (long double)) when switching between hard-float and soft-float?
Looking at a cross long double == double == 8 bytes.
Again I'm expecting a target issue here.
The rev. made a difference in inlining because it removes less
stores as redundant during early optimizations. testN is no
longer inlined.
>From gcc-bugs-return-648542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 11:41:31 2019
Return-Path: <gcc-bugs-return-648542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121119 invoked by alias); 9 Jul 2019 11: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 121101 invoked by uid 48); 9 Jul 2019 11:41:27 -0000
From: "bruno.manga95 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91122] New: alignas gives up evaluating a constant expression in template context
Date: Tue, 09 Jul 2019 11:41: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bruno.manga95 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-91122-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00654.txt.bz2
Content-length: 986
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91122
Bug ID: 91122
Summary: alignas gives up evaluating a constant expression in
template context
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: bruno.manga95 at gmail dot com
Target Milestone: ---
The following code:
template <class T>
constexpr T min( const T& a, const T& b)
{
return a < b ? a : b;
}
template <class T, unsigned long N>
constexpr unsigned long alignment()
{
return min(sizeof(T), N);
}
template <class T, unsigned long N>
struct alignas(alignment<T, N>()) foo {};
int main()
{
foo<int, 4> f;
}
fails to compile on gc 9.1, but worked on previous releases and works again on
trunk: https://gcc.godbolt.org/z/0dSqva
I'm just wondering if the fix will be backported to gcc 9.2
>From gcc-bugs-return-648543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 11:56:55 2019
Return-Path: <gcc-bugs-return-648543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54744 invoked by alias); 9 Jul 2019 11: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 54710 invoked by uid 48); 9 Jul 2019 11:56:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91123] New: [10 Regression] no longer removes redundant store
Date: Tue, 09 Jul 2019 11: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:
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-91123-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00655.txt.bz2
Content-length: 1701
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91123
Bug ID: 91123
Summary: [10 Regression] no longer removes redundant store
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: ---
Since r273135 FRE no longer removes the redundant store in
struct X { int i; int j; };
struct X x, y;
void foo ()
{
x.i = 1;
y = x;
y.i = 1; // redundant
}
which is because of
static void *
vn_reference_lookup_3 (ao_ref *ref, tree vuse, void *data_,
bool *disambiguate_only)
{
...
/* If we are looking for redundant stores do not create new hashtable
entries from aliasing defs with made up alias-sets. */
if (*disambiguate_only || !data->tbaa_p)
return (void *)-1;
I have added this check because we're doing
val = vn_reference_lookup (lhs, gimple_vuse (stmt), VN_WALKREWRITE,
&vnresult, false);
...
/* We can only remove the later store if the former aliases
at least all accesses the later one does or if the store
was to readonly memory storing the same value. */
alias_set_type set = get_alias_set (lhs);
if (! vnresult
|| vnresult->set == set
|| alias_set_subset_of (set, vnresult->set))
and vn_reference_lookup_3 inserts expressions (vnresult) using the
lookup alias-set but here we're looking for the dynamic type before
the store we're looking up.
>From gcc-bugs-return-648544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 11:57:06 2019
Return-Path: <gcc-bugs-return-648544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55459 invoked by alias); 9 Jul 2019 11:57: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 55437 invoked by uid 48); 9 Jul 2019 11:57:02 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91123] [10 Regression] no longer removes redundant store
Date: Tue, 09 Jul 2019 11: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: 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: keywords bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed
Message-ID: <bug-91123-4-0HjjAwYD8o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91123-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91123-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00656.txt.bz2
Content-length: 617
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91123
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-07-09
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
>From gcc-bugs-return-648546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 11:57:28 2019
Return-Path: <gcc-bugs-return-648546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56825 invoked by alias); 9 Jul 2019 11:57: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 56785 invoked by uid 48); 9 Jul 2019 11:57:25 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91124] [10 regression] gcc.target/i386/avx512vl-vpshldvd-2.c etc. FAIL
Date: Tue, 09 Jul 2019 11:57: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: 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-91124-4-SU7Nx8FeDK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00658.txt.bz2
Content-length: 286
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91124
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-648545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 11:57:16 2019
Return-Path: <gcc-bugs-return-648545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56143 invoked by alias); 9 Jul 2019 11: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 56102 invoked by uid 48); 9 Jul 2019 11:57:11 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91124] New: [10 regression] gcc.target/i386/avx512vl-vpshldvd-2.c etc. FAIL
Date: Tue, 09 Jul 2019 11:57: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: 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 target_milestone cf_gcctarget
Message-ID: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00657.txt.bz2
Content-length: 1679
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91124
Bug ID: 91124
Summary: [10 regression] gcc.target/i386/avx512vl-vpshldvd-2.c
etc. FAIL
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
Target Milestone: ---
Target: i?86-*-*, x86_64-*-*
Between 20190707 (r273173) and 20190708 (r273237), two gcc.target/i386
testcases
started to FAIL:
+FAIL: gcc.target/i386/avx512vl-vpshldvd-2.c (test for excess errors)
+UNRESOLVED: gcc.target/i386/avx512vl-vpshldvd-2.c compilation failed to
produce executable
Excess errors:
/var/gcc/regression/trunk/11-gcc-gas/build/gcc/include/avx512vbmi2vlintrin.h:873:19:
error: the last argument must be an 8-bit immediate
/var/gcc/regression/trunk/11-gcc-gas/build/gcc/include/avx512vbmi2vlintrin.h:881:19:
error: the last argument must be an 8-bit immediate
+FAIL: gcc.target/i386/avx512vl-vpshrdvd-2.c (test for excess errors)
+UNRESOLVED: gcc.target/i386/avx512vl-vpshrdvd-2.c compilation failed to
produce executable
Excess errors:
/var/gcc/regression/trunk/11-gcc-gas/build/gcc/include/avx512vbmi2vlintrin.h:729:19:
error: the last argument must be an 8-bit immediate
/var/gcc/regression/trunk/11-gcc-gas/build/gcc/include/avx512vbmi2vlintrin.h:737:19:
error: the last argument must be an 8-bit immediate
I'm seeing it on i386-pc-solaris2.11 (32 and 64-bit), and there are
gcc-testresults reports for i586-unknown-freebsd11.2, i686-pc-linux-gnu,
and x86_64-pc-linux-gnu.
>From gcc-bugs-return-648547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 12:09:38 2019
Return-Path: <gcc-bugs-return-648547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115435 invoked by alias); 9 Jul 2019 12:09: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 115360 invoked by uid 48); 9 Jul 2019 12:09:33 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91125] New: -frepo can't build tramp3d
Date: Tue, 09 Jul 2019 12:09: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: 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 target_milestone
Message-ID: <bug-91125-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00659.txt.bz2
Content-length: 4843
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91125
Bug ID: 91125
Summary: -frepo can't build tramp3d
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
As mentioned here:
https://gcc.gnu.org/ml/gcc/2019-07/msg00068.html
the compilation of tramp3d fails with:
g++ tramp3d-v4.o
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
collect: recompiling tramp3d-v4.cpp
collect: relinking
/usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld:
/tmp/ccEeuyj7.ltrans0.ltrans.o: in function
`RefCountedBlockPtr<FieldEngineBaseData<3, Vector<3, double, Full>,
ViewEngine<3, IndexFunction<GenericURM<MeshTraits<3, double,
UniformRectilinearTag, CartesianTag, 3> >::PositionsFunctor> > >, false,
RefBlockController<FieldEngineBaseData<3, Vector<3, double, Full>,
ViewEngine<3, IndexFunction<GenericURM<MeshTraits<3, double,
UniformRectilinearTag, CartesianTag, 3> >::PositionsFunctor> > > >
>::RefCountedBlockPtr(RefCountedBlockPtr<FieldEngineBaseData<3, Vector<3,
double, Full>, ViewEngine<3, IndexFunction<GenericURM<MeshTraits<3, double,
UniformRectilinearTag, CartesianTag, 3> >::PositionsFunctor> > >, false,
RefBlockController<FieldEngineBaseData<3, Vector<3, double, Full>,
ViewEngine<3, IndexFunction<GenericURM<MeshTraits<3, double,
UniformRectilinearTag, CartesianTag, 3> >::PositionsFunctor> > > > > const&)':
<artificial>:(.text+0x4181b): undefined reference to
`RefCountedPtr<RefBlockController<FieldEngineBaseData<3, Vector<3, double,
Full>, ViewEngine<3, IndexFunction<GenericURM<MeshTraits<3, double,
UniformRectilinearTag, CartesianTag, 3> >::PositionsFunctor> > > >
>::RefCountedPtr(RefCountedPtr<RefBlockController<FieldEngineBaseData<3,
Vector<3, double, Full>, ViewEngine<3, IndexFunction<GenericURM<MeshTraits<3,
double, UniformRectilinearTag, CartesianTag, 3> >::PositionsFunctor> > > > >
const&)'
/usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld:
/tmp/ccEeuyj7.ltrans0.ltrans.o: in function `std::_Vector_base<Node<Range<3>,
Interval<3> >, std::allocator<Node<Range<3>, Interval<3> > >
>::_Vector_impl::~_Vector_impl()':
<artificial>:(.text+0xc1890): undefined reference to
`std::allocator<Node<Range<3>, Interval<3> > >::~allocator()'
/usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld:
/tmp/ccEeuyj7.ltrans0.ltrans.o: in function `std::_Vector_base<Node<Range<3>,
Interval<3> >, std::allocator<Node<Range<3>, Interval<3> > >
>::_Vector_base()':
<artificial>:(.text+0xc18aa): undefined reference to
`std::_Vector_base<Node<Range<3>, Interval<3> >, std::allocator<Node<Range<3>,
Interval<3> > > >::_Vector_impl::_Vector_impl()'
/usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld:
/tmp/ccEeuyj7.ltrans0.ltrans.o: in function `std::vector<INode<3>,
std::allocator<INode<3> > >::_S_use_relocate()':
<artificial>:(.text+0xc496f): undefined reference to `std::vector<INode<3>,
std::allocator<INode<3> > >::_S_nothrow_relocate(std::integral_constant<bool,
true>)'
/usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld:
/tmp/ccEeuyj7.ltrans0.ltrans.o: in function `std::_Vector_base<Node<Range<3>,
Interval<3> >, std::allocator<Node<Range<3>, Interval<3> > >
>::~_Vector_base()':
<artificial>:(.text+0xc4cc1): undefined reference to
`std::_Vector_base<Node<Range<3>, Interval<3> >, std::allocator<Node<Range<3>,
Interval<3> > > >::_M_deallocate(Node<Range<3>, Interval<3> >*, unsigned long)'
/usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld:
/tmp/ccEeuyj7.ltrans0.ltrans.o: in function `DataBlockPtr<double,
false>::DataBlockPtr()':
<artificial>:(.text+0xc6f96): undefined reference to
`RefCountedBlockPtr<double, false, DataBlockController<double>
>::RefCountedBlockPtr()'
[... many other undefined references ...]
>From gcc-bugs-return-648548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 12:28:50 2019
Return-Path: <gcc-bugs-return-648548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27957 invoked by alias); 9 Jul 2019 12:28: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 27919 invoked by uid 48); 9 Jul 2019 12:28:47 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91124] [10 regression] gcc.target/i386/avx512vl-vpshldvd-2.c etc. FAIL
Date: Tue, 09 Jul 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: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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-91124-4-euR63FwQO1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00660.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91124
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-09
CC| |iains at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Reduced range on darwin: r273173 (OK) and r273237 (error).
>From gcc-bugs-return-648549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 12:29:46 2019
Return-Path: <gcc-bugs-return-648549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28910 invoked by alias); 9 Jul 2019 12:29: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 28867 invoked by uid 48); 9 Jul 2019 12:29:43 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91124] [10 regression] gcc.target/i386/avx512vl-vpshldvd-2.c etc. FAIL
Date: Tue, 09 Jul 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: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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-91124-4-wKScdHuBjq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00661.txt.bz2
Content-length: 150
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91124
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Not exactly reduced!-(
>From gcc-bugs-return-648550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 12:37:03 2019
Return-Path: <gcc-bugs-return-648550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69820 invoked by alias); 9 Jul 2019 12:37: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 69781 invoked by uid 48); 9 Jul 2019 12:37:00 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91124] [10 regression] gcc.target/i386/avx512vl-vpshldvd-2.c etc. FAIL
Date: Tue, 09 Jul 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: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91124-4-QL2UpgHfbh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00662.txt.bz2
Content-length: 247
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91124
--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #2)
> Not exactly reduced!-(
273184 (OK) - 273243 (FAIL) is my smallest interval.
>From gcc-bugs-return-648551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 13:27:16 2019
Return-Path: <gcc-bugs-return-648551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21228 invoked by alias); 9 Jul 2019 13:27: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 21101 invoked by uid 48); 9 Jul 2019 13:27:13 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91114] [10 Regression] ICE in vect_analyze_loop, at tree-vect-loop.c:2415
Date: Tue, 09 Jul 2019 13:27: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-checking, ice-on-valid-code, openmp
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-91114-4-ZZiNX3l1TD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00663.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91114
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-648552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 13:27:18 2019
Return-Path: <gcc-bugs-return-648552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21472 invoked by alias); 9 Jul 2019 13:27: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 21172 invoked by uid 55); 9 Jul 2019 13:27:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91114] [10 Regression] ICE in vect_analyze_loop, at tree-vect-loop.c:2415
Date: Tue, 09 Jul 2019 13:27: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-checking, ice-on-valid-code, openmp
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-91114-4-OWE6HisjgN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91114-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00664.txt.bz2
Content-length: 663
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91114
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Jul 9 13:26:43 2019
New Revision: 273306
URL: https://gcc.gnu.org/viewcvs?rev=273306&root=gcc&view=rev
Log:
2019-07-09 Richard Biener <rguenther@suse.de>
PR tree-optimization/91114
* tree-vect-data-refs.c (vect_analyze_data_refs): Failure to
find a vector type isn't fatal.
* gcc.dg/vect/pr91114.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/vect/pr91114.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-vect-data-refs.c
>From gcc-bugs-return-648553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 13:57:46 2019
Return-Path: <gcc-bugs-return-648553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43674 invoked by alias); 9 Jul 2019 13:57: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 43614 invoked by uid 48); 9 Jul 2019 13:57:43 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83518] [8/9 Regression] Missing optimization: useless instructions should be dropped
Date: Tue, 09 Jul 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: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
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-83518-4-OXjbcAFrRr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83518-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83518-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00665.txt.bz2
Content-length: 597
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
Wilco <wilco at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilco at gcc dot gnu.org
--- Comment #12 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #11)
> Fixed on trunk, not something for backporting.
The pr83518.C test fails on AArch64 and Arm (and presumably more targets). Are
you missing options or relying on specific vector widths?
>From gcc-bugs-return-648554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 14:03:49 2019
Return-Path: <gcc-bugs-return-648554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98186 invoked by alias); 9 Jul 2019 14:03: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 98069 invoked by uid 55); 9 Jul 2019 14:03:41 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83518] [8/9 Regression] Missing optimization: useless instructions should be dropped
Date: Tue, 09 Jul 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: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
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-83518-4-z7KvAlW2ap@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83518-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83518-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00666.txt.bz2
Content-length: 1052
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
--- Comment #13 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 9 Jul 2019, wilco at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
>
> Wilco <wilco at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |wilco at gcc dot gnu.org
>
> --- Comment #12 from Wilco <wilco at gcc dot gnu.org> ---
> (In reply to Richard Biener from comment #11)
> > Fixed on trunk, not something for backporting.
>
> The pr83518.C test fails on AArch64 and Arm (and presumably more targets). Are
> you missing options or relying on specific vector widths?
I'm not relying on vectorization (it passes for me with
-fno-tree-vectorize). But I'm relying on unrolling. And also on
constant folding - maybe this is the usual
arr[0] = 5;
arr[1] = 4;
...
vs.
arr = .LC0;
thing?
>From gcc-bugs-return-648555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 14:06:27 2019
Return-Path: <gcc-bugs-return-648555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8942 invoked by alias); 9 Jul 2019 14: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 8877 invoked by uid 48); 9 Jul 2019 14:06:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83518] [8/9 Regression] Missing optimization: useless instructions should be dropped
Date: Tue, 09 Jul 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: tree-optimization
X-Bugzilla-Version: 8.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: P2
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-83518-4-KtZjWMKaUl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83518-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83518-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00667.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
--- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
Yeah. It is
<bb 2> [local count: 178992762]:
arr = *.LC0;
arr[0] = 5;
vect__56.15_75 = MEM <vector(2) int> [(int *)&arr];
I'll fix that (well, I'll try).
>From gcc-bugs-return-648556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 14:07:26 2019
Return-Path: <gcc-bugs-return-648556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12658 invoked by alias); 9 Jul 2019 14: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 12630 invoked by uid 48); 9 Jul 2019 14:07:22 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91049] wrong location in -Wreturn-local-addr for a return throw
Date: Tue, 09 Jul 2019 14:07: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
X-Bugzilla-Severity: minor
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: cc component
Message-ID: <bug-91049-4-3oSRi4I3kU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91049-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91049-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00668.txt.bz2
Content-length: 503
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91049
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
Component|c++ |middle-end
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
This warning is generated in gimple-ssa-isolate-paths.c.
>From gcc-bugs-return-648557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 14:09:16 2019
Return-Path: <gcc-bugs-return-648557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24611 invoked by alias); 9 Jul 2019 14: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 24582 invoked by uid 48); 9 Jul 2019 14:09:13 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83518] [8/9 Regression] Missing optimization: useless instructions should be dropped
Date: Tue, 09 Jul 2019 14: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: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
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-83518-4-dlnr63Tvy1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83518-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83518-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00669.txt.bz2
Content-length: 404
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83518
--- Comment #15 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #14)
> Yeah. It is
>
> <bb 2> [local count: 178992762]:
> arr = *.LC0;
> arr[0] = 5;
> vect__56.15_75 = MEM <vector(2) int> [(int *)&arr];
>
> I'll fix that (well, I'll try).
Right, it's fine with -fno-tree-vectorize on AArch64.
>From gcc-bugs-return-648558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 14:30:35 2019
Return-Path: <gcc-bugs-return-648558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31374 invoked by alias); 9 Jul 2019 14:30: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 31278 invoked by uid 48); 9 Jul 2019 14:30:27 -0000
From: "wolfwings+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91117] _mm_movpi64_epi64/_mm_movepi64_pi64 generating store+load instead of using MOVQ2DQ/MOVDQ2Q
Date: Tue, 09 Jul 2019 14:30: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.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wolfwings+gcc 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-91117-4-pscMWLjwo0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91117-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91117-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00670.txt.bz2
Content-length: 755
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91117
--- Comment #2 from Wolf . <wolfwings+gcc at gmail dot com> ---
Is there any way to still access MMX instructions/registers with intrinsics in
gcc-10 at all or is this bug "fixable but that code generation option will go
away entirely with gcc-10 so it wouldn't matter" then?
The full code block I found this hiccup in was running out of SSE registers on
the pre-AVX Silvermont platform it's on (so no 3-op VEX available) so I moved
some early operations to MMX registers instead.
This freed up all register pressure, allowing the constants used to stay
in-register for the full processing loop and avoiding almost all spills/stalls,
which is where I found this hiccup in the first place.
>From gcc-bugs-return-648559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 15:04:28 2019
Return-Path: <gcc-bugs-return-648559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5401 invoked by alias); 9 Jul 2019 15:04: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 5343 invoked by uid 48); 9 Jul 2019 15:04:25 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/42575] arm-eabi-gcc 64-bit multiply weirdness
Date: Tue, 09 Jul 2019 15: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: 5.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-42575-4-SoRSqchbml@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-42575-4@http.gcc.gnu.org/bugzilla/>
References: <bug-42575-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00671.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42575
Christophe Lyon <clyon at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |clyon at gcc dot gnu.org
--- Comment #18 from Christophe Lyon <clyon at gcc dot gnu.org> ---
This is still wrong with current trunk.
>From gcc-bugs-return-648560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 15:10:59 2019
Return-Path: <gcc-bugs-return-648560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13407 invoked by alias); 9 Jul 2019 15:10: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 13392 invoked by uid 48); 9 Jul 2019 15:10:55 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91117] _mm_movpi64_epi64/_mm_movepi64_pi64 generating store+load instead of using MOVQ2DQ/MOVDQ2Q
Date: Tue, 09 Jul 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: target
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak 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-91117-4-F7CJKrkNAm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91117-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91117-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00672.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91117
--- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Wolf . from comment #2)
> Is there any way to still access MMX instructions/registers with intrinsics
> in gcc-10 at all or is this bug "fixable but that code generation option
> will go away entirely with gcc-10 so it wouldn't matter" then?
The plan is to deprecate MMX instructions in gcc-10.
>From gcc-bugs-return-648561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 15:46:01 2019
Return-Path: <gcc-bugs-return-648561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110980 invoked by alias); 9 Jul 2019 15:46: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 110917 invoked by uid 48); 9 Jul 2019 15:45:57 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91124] [10 regression] gcc.target/i386/avx512vl-vpshldvd-2.c etc. FAIL
Date: Tue, 09 Jul 2019 15: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: 10.0
X-Bugzilla-Keywords: needs-bisection, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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-91124-4-K87GEu6mLA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00673.txt.bz2
Content-length: 441
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91124
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
r273193 is OK r273200 is not. Likely r273194.
>From gcc-bugs-return-648562-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 15:50:52 2019
Return-Path: <gcc-bugs-return-648562-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45353 invoked by alias); 9 Jul 2019 15:50: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 45322 invoked by uid 48); 9 Jul 2019 15:50:48 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91049] wrong location in -Wreturn-local-addr for a return with a conditional expression
Date: Tue, 09 Jul 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: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: minor
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: short_desc
Message-ID: <bug-91049-4-LzHyMVKITA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91049-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91049-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00674.txt.bz2
Content-length: 2500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91049
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|wrong location in |wrong location in
|-Wreturn-local-addr for a |-Wreturn-local-addr for a
|return throw |return with a conditional
| |expression
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
I'm not sure this a middle-end issue. The path isolation pass uses the
location of the return statement to issue the warning. In C, the location is
that of the whole operand to the statement. That also doesn't seem quite right
but it's less confusing than in C++ where the location corresponds to just one
of the operand (the second one?). When the operand is not the address of a
local variable it's plain wrong.
The difference in the location between C and C++ can be seen as early as the
Gimple dump. It only shows the beginning location so it's not complete but
it's the starting location that's the problem. Here's C:
$ cat a.C && gcc -O2 -S -Wall -fdump-tree-gimple-lineno=/dev/stdout -xc a.C
void* g (int i)
{
extern int j;
return i ?
&i :
&j;
}
g (int i)
[a.C:2:1] {
void * D.1913;
int * iftmp.0;
extern int j;
[a.C:4:12] i.1_1 = i;
[a.C:5:13] if (i.1_1 != 0) goto <D.1915>; else goto <D.1916>;
<D.1915>:
[a.C:5:13] iftmp.0 = [a.C:5:10] &i;
goto <D.1917>;
<D.1916>:
[a.C:5:13] iftmp.0 = [a.C:6:10] &j;
<D.1917>:
[a.C:5:13] D.1913 = iftmp.0;
[a.C:5:13] return D.1913;
}
a.C: In function ‘g’:
a.C:5:13: warning: function may return address of local variable
[-Wreturn-local-addr]
4 | return i ?
| ~~~
5 | &i :
| ~~~^
6 | &j;
| ~~
a.C:1:14: note: declared here
1 | void* g (int i)
| ~~~~^
and here's the dump for the same test case compiled as C++:
g (int i)
[a.C:6:12] {
void * D.2304;
int * iftmp.0;
extern int j;
[a.C:6:11] i.1_1 = i;
[a.C:6:11] if (i.1_1 != 0) goto <D.2306>; else goto <D.2307>;
<D.2306>:
[a.C:6:11] iftmp.0 = [a.C:5:10] &i;
goto <D.2308>;
<D.2307>:
[a.C:6:11] iftmp.0 = [a.C:6:10] &j;
<D.2308>:
[a.C:6:11] D.2304 = iftmp.0;
[a.C:6:11] return D.2304;
}
>From gcc-bugs-return-648563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 16:08:49 2019
Return-Path: <gcc-bugs-return-648563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106891 invoked by alias); 9 Jul 2019 16:08: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 106825 invoked by uid 48); 9 Jul 2019 16:08:46 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/42575] arm-eabi-gcc 64-bit multiply weirdness
Date: Tue, 09 Jul 2019 16: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: 5.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-42575-4-LhShvIZ0Yb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-42575-4@http.gcc.gnu.org/bugzilla/>
References: <bug-42575-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00675.txt.bz2
Content-length: 983
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42575
Wilco <wilco at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilco at gcc dot gnu.org
--- Comment #19 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Christophe Lyon from comment #18)
> This is still wrong with current trunk.
I don't see it happening since expansion of DImode instructions improved. The
only case that uses an extra register is -mcpu=cortex-a9/-mcpu=cortex-a5 with
-O2 -mthumb:
mul r3, r0, r3
push {r4}
mov r4, r1
umull r0, r1, r0, r2
mla r2, r2, r4, r3
ldr r4, [sp], #4
add r1, r1, r2
bx lr
I don't think we should expect perfect register allocation in severely
constrained cases like this - scheduling can increase register pressure.
>From gcc-bugs-return-648564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 16:36:50 2019
Return-Path: <gcc-bugs-return-648564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35383 invoked by alias); 9 Jul 2019 16:36: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 35274 invoked by uid 55); 9 Jul 2019 16:36:36 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61339] add mismatch between struct and class [-Wmismatched-tags] to non-bugs
Date: Tue, 09 Jul 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: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: enhancement
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-61339-4-ADKxrw5M74@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61339-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61339-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00676.txt.bz2
Content-length: 11676
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61339
--- Comment #12 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Tue Jul 9 16:36:00 2019
New Revision: 273308
URL: https://gcc.gnu.org/viewcvs?rev=273308&root=gcc&view=rev
Log:
PR c++/61339 - add mismatch between struct and class [-Wmismatched-tags] to
non-bugs
gcc/c/ChangeLog:
PR c++/61339
* c-decl.c: Change class-key from class to struct and vice versa
to match convention and avoid -Wclass-is-pod and -Wstruct-no-pod.
* gimple-parser.c: Same.
gcc/c-family/ChangeLog:
PR c++/61339
* c-format.c (check_argument_type): Change class-key from class to
struct and vice versa to match convention and avoid -Wclass-is-pod
and -Wstruct-no-pod.
* c-pretty-print.h: Same.
gcc/cp/ChangeLog:
PR c++/61339
* constexpr.c (cxx_eval_call_expression): Change class-key from class
to struct and vice versa to match convention and avoid -Wclass-is-pod
and -Wstruct-no-pod.
* constraint.cc (get_concept_definition): Same.
* cp-tree.h: Same.
* cxx-pretty-print.h: Same.
* error.c: Same.
* logic.cc (term_list::replace): Same.
* name-lookup.c (find_local_binding): Same.
* pt.c (tsubst_binary_right_fold): Same.
* search.c (field_accessor_p): Same.
* semantics.c (expand_or_defer_fn): Same.
gcc/lto/ChangeLog:
PR c++/61339
* lto-dump.c: Change class-key from classi to struct and vice versa
to match convention and avoid -Wclass-is-pod and -Wstruct-no-pod.
gcc/ChangeLog:
PR c++/61339
* align.h: Change class-key from class to struct and vice versa
to match convention and avoid -Wclass-is-pod and -Wstruct-no-pod.
* alloc-pool.h: Same.
* asan.c (shadow_mem_size): Same.
* auto-profile.c: Same.
* basic-block.h: Same.
* bitmap.h: Same.
* cfgexpand.c (set_rtl): Same.
(expand_one_stack_var_at): Same.
* cfghooks.h: Same.
* cfgloop.h: Same.
* cgraph.h: Same.
* config/i386/i386.h: Same.
* df-problems.c (df_print_bb_index): Same.
* df-scan.c: Same.
* df.h (df_single_use): Same.
* diagnostic-show-locus.c (layout::print_annotation_line): Same.
(layout::annotation_line_showed_range_p): Same.
(get_printed_columns): Same.
(correction::ensure_terminated): Same.
(line_corrections::~line_corrections): Same.
* dojump.h: Same.
* dse.c: Same.
* dump-context.h: Same.
* dumpfile.h: Same.
* dwarf2out.c: Same.
* edit-context.c: Same.
* fibonacci_heap.c (test_union_of_equal_heaps): Same.
* flags.h: Same.
* function.c (assign_stack_local): Same.
* function.h: Same.
* gcc.c: Same.
* gcov.c (block_info::block_info): Same.
* genattrtab.c: Same.
* genextract.c: Same.
* genmatch.c (comparison_code_p): Same.
(id_base::id_base): Same.
(decision_tree::print): Same.
* genoutput.c: Same.
* genpreds.c (write_one_predicate_function): Same.
* genrecog.c (validate_pattern): Same.
(find_operand_positions): Same.
(optimize_subroutine_group): Same.
(merge_pattern_transition::merge_pattern_transition): Same.
(merge_pattern_info::merge_pattern_info): Same.
(merge_state_result::merge_state_result): Same.
(merge_into_state): Same.
* gensupport.c: Same.
* gensupport.h: Same.
* ggc-common.c (init_ggc_heuristics): Same.
* ggc-tests.c (test_union): Same.
* gimple-loop-interchange.cc (dump_induction): Same.
* gimple-loop-versioning.cc: Same.
* gimple-match.h (gimple_match_cond::any_else): Same.
* gimple-ssa-backprop.c: Same.
* gimple-ssa-sprintf.c: Same.
* gimple-ssa-store-merging.c (store_operand_info::store_operand_info):
Same.
(store_immediate_info::store_immediate_info): Same.
(merged_store_group::apply_stores): Same.
(get_location_for_stmts): Same.
* gimple-ssa-strength-reduction.c: Same.
* gimple-ssa-warn-alloca.c: Same.
* gimple-ssa-warn-restrict.c (pass_wrestrict::execute): Same.
* godump.c (go_type_decl): Same.
* hash-map-tests.c (test_map_of_strings_to_int): Same.
* hash-map.h: Same.
* hash-set-tests.c (test_set_of_strings): Same.
* hsa-brig.c: Same.
* hsa-common.h: Same.
* hsa-gen.c (transformable_switch_to_sbr_p): Same.
* input.c (assert_loceq): Same.
* input.h: Same.
* ipa-cp.c: Same.
* ipa-devirt.c (possible_polymorphic_call_targets_1): Same.
* ipa-fnsummary.h: Same.
* ipa-inline.h: Same.
* ipa-prop.h: Same.
* ipa-split.c (visit_bb): Same.
* ira-int.h (minmax_set_iter_next): Same.
* loop-invariant.c: Same.
* loop-iv.c: Same.
* lra-eliminations.c: Same.
* lra-int.h: Same.
* lra-lives.c (mark_regno_dead): Same.
* lra-remat.c: Same.
* lra-spills.c: Same.
* lto-streamer.h: Same.
* mem-stats.h: Same.
* omp-grid.c (omp_grid_lastprivate_predicate): Same.
* omp-low.c (omp_clause_aligned_alignment): Same.
* optabs-query.h (get_vcond_eq_icode): Same.
* optabs.h: Same.
* opts.c (wrap_help): Same.
* poly-int.h: Same.
* predict.c (predict_paths_leading_to_edge): Same.
* pretty-print.h: Same.
* profile-count.h: Same.
* read-md.h: Same.
* read-rtl-function.c: Same.
* ree.c: Same.
* reginfo.c: Same.
* regrename.c: Same.
* regrename.h: Same.
* reload.h: Same.
* rtl-iter.h: Same.
* rtl.h (costs_add_n_insns): Same.
* sanopt.c: Same.
* sched-int.h: Same.
* sel-sched-ir.h: Same.
* selftest.h: Same.
* sese.h (vec_find): Same.
* stmt.c: Same.
* target-globals.h: Same.
* tree-affine.c (aff_combination_find_elt): Same.
* tree-affine.h: Same.
* tree-data-ref.h: Same.
* tree-outof-ssa.c (ssa_is_replaceable_p): Same.
* tree-predcom.c: Same.
* tree-scalar-evolution.c (find_var_scev_info): Same.
* tree-ssa-alias.h: Same.
* tree-ssa-ccp.c: Same.
* tree-ssa-coalesce.c (ssa_conflicts_dump): Same.
* tree-ssa-loop-im.c (for_all_locs_in_loop): Same.
(rewrite_mem_refs): Same.
(execute_sm_if_changed): Same.
(hoist_memory_references): Same.
* tree-ssa-loop-ivopts.c (operator<=): Same.
* tree-ssa-loop.h: Same.
* tree-ssa-pre.c (get_or_alloc_expr_for_name): Same.
* tree-ssa-structalias.c: Same.
* tree-switch-conversion.h (cluster::cluster): Same.
(simple_cluster::simple_cluster): Same.
* tree-vect-patterns.c (type_conversion_p): Same.
* tree-vectorizer.c (dump_stmt_cost): Same.
* tree-vectorizer.h (loop_vec_info_for_loop): Same.
* tree.c (protected_set_expr_location): Same.
* tree.h (desired_pro_or_demotion_p): Same.
(fndecl_built_in_p): Same.
* unique-ptr-tests.cc: Same.
* var-tracking.c (delete_variable_part): Same.
* varasm.c (assemble_real): Same.
(tree_output_constant_def): Same.
* vec.c: Same.
* wide-int-bitmask.h: Same.
* wide-int.h (decompose): Same.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/align.h
trunk/gcc/alloc-pool.h
trunk/gcc/asan.c
trunk/gcc/auto-profile.c
trunk/gcc/basic-block.h
trunk/gcc/bitmap.h
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-format.c
trunk/gcc/c-family/c-pretty-print.h
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-decl.c
trunk/gcc/c/gimple-parser.c
trunk/gcc/cfgexpand.c
trunk/gcc/cfghooks.h
trunk/gcc/cfgloop.h
trunk/gcc/cgraph.h
trunk/gcc/config/i386/i386.h
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/constexpr.c
trunk/gcc/cp/constraint.cc
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/cxx-pretty-print.h
trunk/gcc/cp/error.c
trunk/gcc/cp/logic.cc
trunk/gcc/cp/name-lookup.c
trunk/gcc/cp/pt.c
trunk/gcc/cp/search.c
trunk/gcc/cp/semantics.c
trunk/gcc/df-problems.c
trunk/gcc/df-scan.c
trunk/gcc/df.h
trunk/gcc/diagnostic-show-locus.c
trunk/gcc/dojump.h
trunk/gcc/dse.c
trunk/gcc/dump-context.h
trunk/gcc/dumpfile.h
trunk/gcc/dwarf2out.c
trunk/gcc/edit-context.c
trunk/gcc/fibonacci_heap.c
trunk/gcc/flags.h
trunk/gcc/function.c
trunk/gcc/function.h
trunk/gcc/gcc.c
trunk/gcc/gcov.c
trunk/gcc/genattrtab.c
trunk/gcc/genextract.c
trunk/gcc/genmatch.c
trunk/gcc/genoutput.c
trunk/gcc/genpreds.c
trunk/gcc/genrecog.c
trunk/gcc/gensupport.c
trunk/gcc/gensupport.h
trunk/gcc/ggc-common.c
trunk/gcc/ggc-tests.c
trunk/gcc/gimple-loop-interchange.cc
trunk/gcc/gimple-loop-versioning.cc
trunk/gcc/gimple-match.h
trunk/gcc/gimple-ssa-backprop.c
trunk/gcc/gimple-ssa-sprintf.c
trunk/gcc/gimple-ssa-store-merging.c
trunk/gcc/gimple-ssa-strength-reduction.c
trunk/gcc/gimple-ssa-warn-alloca.c
trunk/gcc/gimple-ssa-warn-restrict.c
trunk/gcc/godump.c
trunk/gcc/hash-map-tests.c
trunk/gcc/hash-map.h
trunk/gcc/hash-set-tests.c
trunk/gcc/hsa-brig.c
trunk/gcc/hsa-common.h
trunk/gcc/hsa-gen.c
trunk/gcc/input.c
trunk/gcc/input.h
trunk/gcc/ipa-cp.c
trunk/gcc/ipa-devirt.c
trunk/gcc/ipa-fnsummary.h
trunk/gcc/ipa-inline.h
trunk/gcc/ipa-prop.h
trunk/gcc/ipa-split.c
trunk/gcc/ira-int.h
trunk/gcc/loop-invariant.c
trunk/gcc/loop-iv.c
trunk/gcc/lra-eliminations.c
trunk/gcc/lra-int.h
trunk/gcc/lra-lives.c
trunk/gcc/lra-remat.c
trunk/gcc/lra-spills.c
trunk/gcc/lto-streamer.h
trunk/gcc/lto/ChangeLog
trunk/gcc/lto/lto-dump.c
trunk/gcc/mem-stats.h
trunk/gcc/omp-grid.c
trunk/gcc/omp-low.c
trunk/gcc/optabs-query.h
trunk/gcc/optabs.h
trunk/gcc/opts.c
trunk/gcc/poly-int.h
trunk/gcc/predict.c
trunk/gcc/pretty-print.h
trunk/gcc/profile-count.h
trunk/gcc/read-md.h
trunk/gcc/read-rtl-function.c
trunk/gcc/ree.c
trunk/gcc/reginfo.c
trunk/gcc/regrename.c
trunk/gcc/regrename.h
trunk/gcc/reload.h
trunk/gcc/rtl-iter.h
trunk/gcc/rtl.h
trunk/gcc/sanopt.c
trunk/gcc/sched-int.h
trunk/gcc/sel-sched-ir.h
trunk/gcc/selftest.h
trunk/gcc/sese.h
trunk/gcc/stmt.c
trunk/gcc/target-globals.h
trunk/gcc/tree-affine.c
trunk/gcc/tree-affine.h
trunk/gcc/tree-data-ref.h
trunk/gcc/tree-outof-ssa.c
trunk/gcc/tree-predcom.c
trunk/gcc/tree-scalar-evolution.c
trunk/gcc/tree-ssa-alias.h
trunk/gcc/tree-ssa-ccp.c
trunk/gcc/tree-ssa-coalesce.c
trunk/gcc/tree-ssa-loop-im.c
trunk/gcc/tree-ssa-loop-ivopts.c
trunk/gcc/tree-ssa-loop.h
trunk/gcc/tree-ssa-pre.c
trunk/gcc/tree-ssa-structalias.c
trunk/gcc/tree-switch-conversion.h
trunk/gcc/tree-vect-patterns.c
trunk/gcc/tree-vectorizer.c
trunk/gcc/tree-vectorizer.h
trunk/gcc/tree.c
trunk/gcc/tree.h
trunk/gcc/unique-ptr-tests.cc
trunk/gcc/var-tracking.c
trunk/gcc/varasm.c
trunk/gcc/vec.c
trunk/gcc/wide-int-bitmask.h
trunk/gcc/wide-int.h
trunk/libcpp/ChangeLog
trunk/libcpp/include/line-map.h
trunk/libcpp/mkdeps.c
>From gcc-bugs-return-648565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 16:57:39 2019
Return-Path: <gcc-bugs-return-648565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89628 invoked by alias); 9 Jul 2019 16:57: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 89566 invoked by uid 48); 9 Jul 2019 16:57:35 -0000
From: "fhsueh at roku dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91115] stack-buffer-overflow on memset local variable when creating thread on ARM Linux
Date: Tue, 09 Jul 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: sanitizer
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fhsueh at roku 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:
Message-ID: <bug-91115-4-7Fdw8v5b3P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91115-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91115-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00677.txt.bz2
Content-length: 473
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91115
--- Comment #3 from Fred Hsueh <fhsueh at roku dot com> ---
The actual SP and shadow byte location varies a bit between each run. Other
than that, the signature looks very similar. Another thing to note is that the
program has a high thread count, perhaps ~140.
Any tips, preferences, or good starting points to look at for creating the
testcase? I can't find any in ASAN or ARM related pre-existing cases.
thanks!
>From gcc-bugs-return-648566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 17:47:06 2019
Return-Path: <gcc-bugs-return-648566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41790 invoked by alias); 9 Jul 2019 17:47: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 41734 invoked by uid 48); 9 Jul 2019 17:47:02 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91124] [10 regression] gcc.target/i386/avx512vl-vpshldvd-2.c etc. FAIL
Date: Tue, 09 Jul 2019 17: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: needs-bisection, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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-91124-4-YkmRCl3fh8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00678.txt.bz2
Content-length: 157
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91124
--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Likely r273194.
Confirmed.
>From gcc-bugs-return-648567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 18:00:49 2019
Return-Path: <gcc-bugs-return-648567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50058 invoked by alias); 9 Jul 2019 18:00: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 47945 invoked by uid 48); 9 Jul 2019 18:00:44 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91126] New: [10 regression] Incorrect constant propagation of BIT_FIELD_REF
Date: Tue, 09 Jul 2019 18:00: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: wilco 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-91126-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00679.txt.bz2
Content-length: 2079
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91126
Bug ID: 91126
Summary: [10 regression] Incorrect constant propagation of
BIT_FIELD_REF
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: wilco at gcc dot gnu.org
Target Milestone: ---
gcc.c-torture/execute/pr31448-2.c generates incorrect code due to a recent
change with -O2 -mbig-endian on AArch64. fre3 constant-folds a BIT_FIELD_REF
<a, 32, 0> with value 0xFEFEFEFE as 0xFFFEFEFE. As a result the if-statement is
removed and we abort:
Value numbering store a.iIndex1 to -65794
Setting value number of .MEM_8 to .MEM_8 (changed)
Value numbering stmt = _1 = BIT_FIELD_REF <a, 32, 0>;
Successfully combined 2 partial definitions
Setting value number of _1 to 4294901503 (changed)
Value numbering stmt = _2 = _1 & 4294967040;
Match-and-simplified _1 & 4294967040 to 4294901248
RHS _1 & 4294967040 simplified to 4294901248
Setting value number of _2 to 4294901248 (changed)
Value numbering stmt = if (_2 != 4278124032)
marking known outgoing edge 2 -> 3 executable
Block 1: BB4 found not executable
...
Merging blocks 2 and 3
fix_loop_structure: fixing up loops for function
main ()
{
struct stD.3411 aD.3421;
;; basic block 2, loop depth 0, count 0 (precise), probably never executed
;; Invalid sum of incoming counts 1073741824 (estimated locally), should be 0
(precise)
;; prev block 0, next block 1, flags: (NEW, REACHABLE, VISITED)
;; pred: ENTRY [always] count:1073741824 (estimated locally)
(FALLTHRU,EXECUTABLE)
# .MEM_4 = VDEF <.MEM_3(D)>
nextD.3412 = &aD.3421;
# .MEM_7 = VDEF <.MEM_4>
aD.3421.iIndexD.3408 = -65794;
# .MEM_8 = VDEF <.MEM_7>
aD.3421.iIndex1D.3409 = -65794;
# .MEM_6 = VDEF <.MEM_8>
# USE = nonlocal { D.3421 } (escaped)
# CLB = nonlocal { D.3421 } (escaped)
abortD.1083 ();
;; succ:
}
>From gcc-bugs-return-648568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 18:12:58 2019
Return-Path: <gcc-bugs-return-648568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19515 invoked by alias); 9 Jul 2019 18: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 15191 invoked by uid 48); 9 Jul 2019 18:12:53 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91126] [10 regression] Incorrect constant propagation of BIT_FIELD_REF
Date: Tue, 09 Jul 2019 18: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: 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 cc
Message-ID: <bug-91126-4-UoUaO8WTvI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00680.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91126
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
CC| |pinskia at gcc dot gnu.org
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
BIT_FIELD_INSERT also has similar wrong behavior.
>From gcc-bugs-return-648569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 18:33:38 2019
Return-Path: <gcc-bugs-return-648569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42875 invoked by alias); 9 Jul 2019 18:33: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 42701 invoked by uid 55); 9 Jul 2019 18:33:22 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61339] add mismatch between struct and class [-Wmismatched-tags] to non-bugs
Date: Tue, 09 Jul 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: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: enhancement
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-61339-4-2XymwuRP5k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61339-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61339-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00681.txt.bz2
Content-length: 66742
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61339
--- Comment #13 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Tue Jul 9 18:32:49 2019
New Revision: 273311
URL: https://gcc.gnu.org/viewcvs?rev=273311&root=gcc&view=rev
Log:
PR c++/61339 - add mismatch between struct and class [-Wmismatched-tags] to
non-bugs
gcc/c/ChangeLog:
PR c++/61339
* c-decl.c (xref_tag): Change class-key of PODs to struct and others
to class.
(field_decl_cmp): Same.
* c-parser.c (c_parser_struct_or_union_specifier): Same.
* c-tree.h: Same.
* gimple-parser.c (c_parser_gimple_compound_statement): Same.
gcc/c-family/ChangeLog:
PR c++/61339
* c-opts.c (handle_deferred_opts): : Change class-key of PODs to struct
and others to class.
* c-pretty-print.h: Same.
gcc/cp/ChangeLog:
PR c++/61339
* cp-tree.h: Change class-key of PODs to struct and others to class.
* search.c: Same.
* semantics.c (finalize_nrv_r): Same.
gcc/lto/ChangeLog:
PR c++/61339
* lto-common.c (lto_splay_tree_new): : Change class-key of PODs
to struct and others to class.
(mentions_vars_p): Same.
(register_resolution): Same.
(lto_register_var_decl_in_symtab): Same.
(lto_register_function_decl_in_symtab): Same.
(cmp_tree): Same.
(lto_read_decls): Same.
gcc/ChangeLog:
PR c++/61339
* auto-profile.c: Change class-key of PODs to struct and others
to class.
* basic-block.h: Same.
* bitmap.c (bitmap_alloc): Same.
* bitmap.h: Same.
* builtins.c (expand_builtin_prefetch): Same.
(expand_builtin_interclass_mathfn): Same.
(expand_builtin_strlen): Same.
(expand_builtin_mempcpy_args): Same.
(expand_cmpstr): Same.
(expand_builtin___clear_cache): Same.
(expand_ifn_atomic_bit_test_and): Same.
(expand_builtin_thread_pointer): Same.
(expand_builtin_set_thread_pointer): Same.
* caller-save.c (setup_save_areas): Same.
(replace_reg_with_saved_mem): Same.
(insert_restore): Same.
(insert_save): Same.
(add_used_regs): Same.
* cfg.c (get_bb_copy): Same.
(set_loop_copy): Same.
* cfg.h: Same.
* cfganal.h: Same.
* cfgexpand.c (alloc_stack_frame_space): Same.
(add_stack_var): Same.
(add_stack_var_conflict): Same.
(add_scope_conflicts_1): Same.
(update_alias_info_with_stack_vars): Same.
(expand_used_vars): Same.
* cfghooks.c (redirect_edge_and_branch_force): Same.
(delete_basic_block): Same.
(split_edge): Same.
(make_forwarder_block): Same.
(force_nonfallthru): Same.
(duplicate_block): Same.
(lv_flush_pending_stmts): Same.
* cfghooks.h: Same.
* cfgloop.c (flow_loops_cfg_dump): Same.
(flow_loop_nested_p): Same.
(superloop_at_depth): Same.
(get_loop_latch_edges): Same.
(flow_loop_dump): Same.
(flow_loops_dump): Same.
(flow_loops_free): Same.
(flow_loop_nodes_find): Same.
(establish_preds): Same.
(flow_loop_tree_node_add): Same.
(flow_loop_tree_node_remove): Same.
(flow_loops_find): Same.
(find_subloop_latch_edge_by_profile): Same.
(find_subloop_latch_edge_by_ivs): Same.
(mfb_redirect_edges_in_set): Same.
(form_subloop): Same.
(merge_latch_edges): Same.
(disambiguate_multiple_latches): Same.
(disambiguate_loops_with_multiple_latches): Same.
(flow_bb_inside_loop_p): Same.
(glb_enum_p): Same.
(get_loop_body_with_size): Same.
(get_loop_body): Same.
(fill_sons_in_loop): Same.
(get_loop_body_in_dom_order): Same.
(get_loop_body_in_custom_order): Same.
(release_recorded_exits): Same.
(get_loop_exit_edges): Same.
(num_loop_branches): Same.
(remove_bb_from_loops): Same.
(find_common_loop): Same.
(delete_loop): Same.
(cancel_loop): Same.
(verify_loop_structure): Same.
(loop_preheader_edge): Same.
(loop_exit_edge_p): Same.
(single_exit): Same.
(loop_exits_to_bb_p): Same.
(loop_exits_from_bb_p): Same.
(get_loop_location): Same.
(record_niter_bound): Same.
(get_estimated_loop_iterations_int): Same.
(max_stmt_executions_int): Same.
(likely_max_stmt_executions_int): Same.
(get_estimated_loop_iterations): Same.
(get_max_loop_iterations): Same.
(get_max_loop_iterations_int): Same.
(get_likely_max_loop_iterations): Same.
* cfgloop.h (simple_loop_desc): Same.
(get_loop): Same.
(loop_depth): Same.
(loop_outer): Same.
(loop_iterator::next): Same.
(loop_outermost): Same.
* cfgloopanal.c (mark_irreducible_loops): Same.
(num_loop_insns): Same.
(average_num_loop_insns): Same.
(expected_loop_iterations_unbounded): Same.
(expected_loop_iterations): Same.
(mark_loop_exit_edges): Same.
(single_likely_exit): Same.
* cfgloopmanip.c (fix_bb_placement): Same.
(fix_bb_placements): Same.
(remove_path): Same.
(place_new_loop): Same.
(add_loop): Same.
(scale_loop_frequencies): Same.
(scale_loop_profile): Same.
(create_empty_if_region_on_edge): Same.
(create_empty_loop_on_edge): Same.
(loopify): Same.
(unloop): Same.
(fix_loop_placements): Same.
(copy_loop_info): Same.
(duplicate_loop): Same.
(duplicate_subloops): Same.
(loop_redirect_edge): Same.
(can_duplicate_loop_p): Same.
(duplicate_loop_to_header_edge): Same.
(mfb_keep_just): Same.
(has_preds_from_loop): Same.
(create_preheader): Same.
(create_preheaders): Same.
(lv_adjust_loop_entry_edge): Same.
(loop_version): Same.
* cfgloopmanip.h: Same.
* cgraph.h: Same.
* cgraphbuild.c: Same.
* combine.c (make_extraction): Same.
* config/i386/i386-features.c: Same.
* config/i386/i386-features.h: Same.
* config/i386/i386.c (ix86_emit_outlined_ms2sysv_save): Same.
(ix86_emit_outlined_ms2sysv_restore): Same.
(ix86_noce_conversion_profitable_p): Same.
(ix86_init_cost): Same.
(ix86_simd_clone_usable): Same.
* configure.ac: Same.
* coretypes.h: Same.
* data-streamer-in.c (string_for_index): Same.
(streamer_read_indexed_string): Same.
(streamer_read_string): Same.
(bp_unpack_indexed_string): Same.
(bp_unpack_string): Same.
(streamer_read_uhwi): Same.
(streamer_read_hwi): Same.
(streamer_read_gcov_count): Same.
(streamer_read_wide_int): Same.
* data-streamer.h (streamer_write_bitpack): Same.
(bp_unpack_value): Same.
(streamer_write_char_stream): Same.
(streamer_write_hwi_in_range): Same.
(streamer_write_record_start): Same.
* ddg.c (create_ddg_dep_from_intra_loop_link): Same.
(add_cross_iteration_register_deps): Same.
(build_intra_loop_deps): Same.
* df-core.c (df_analyze): Same.
(loop_post_order_compute): Same.
(loop_inverted_post_order_compute): Same.
* df-problems.c (df_rd_alloc): Same.
(df_rd_simulate_one_insn): Same.
(df_rd_local_compute): Same.
(df_rd_init_solution): Same.
(df_rd_confluence_n): Same.
(df_rd_transfer_function): Same.
(df_rd_free): Same.
(df_rd_dump_defs_set): Same.
(df_rd_top_dump): Same.
(df_lr_alloc): Same.
(df_lr_reset): Same.
(df_lr_local_compute): Same.
(df_lr_init): Same.
(df_lr_confluence_n): Same.
(df_lr_free): Same.
(df_lr_top_dump): Same.
(df_lr_verify_transfer_functions): Same.
(df_live_alloc): Same.
(df_live_reset): Same.
(df_live_init): Same.
(df_live_confluence_n): Same.
(df_live_finalize): Same.
(df_live_free): Same.
(df_live_top_dump): Same.
(df_live_verify_transfer_functions): Same.
(df_mir_alloc): Same.
(df_mir_reset): Same.
(df_mir_init): Same.
(df_mir_confluence_n): Same.
(df_mir_free): Same.
(df_mir_top_dump): Same.
(df_word_lr_alloc): Same.
(df_word_lr_reset): Same.
(df_word_lr_init): Same.
(df_word_lr_confluence_n): Same.
(df_word_lr_free): Same.
(df_word_lr_top_dump): Same.
(df_md_alloc): Same.
(df_md_simulate_one_insn): Same.
(df_md_reset): Same.
(df_md_init): Same.
(df_md_free): Same.
(df_md_top_dump): Same.
* df-scan.c (df_insn_delete): Same.
(df_insn_rescan): Same.
(df_notes_rescan): Same.
(df_sort_and_compress_mws): Same.
(df_install_mws): Same.
(df_refs_add_to_chains): Same.
(df_ref_create_structure): Same.
(df_ref_record): Same.
(df_def_record_1): Same.
(df_find_hard_reg_defs): Same.
(df_uses_record): Same.
(df_get_conditional_uses): Same.
(df_get_call_refs): Same.
(df_recompute_luids): Same.
(df_get_entry_block_def_set): Same.
(df_entry_block_defs_collect): Same.
(df_get_exit_block_use_set): Same.
(df_exit_block_uses_collect): Same.
(df_mws_verify): Same.
(df_bb_verify): Same.
* df.h (df_scan_get_bb_info): Same.
* doc/tm.texi: Same.
* dse.c (record_store): Same.
* dumpfile.h: Same.
* emit-rtl.c (const_fixed_hasher::equal): Same.
(set_mem_attributes_minus_bitpos): Same.
(change_address): Same.
(adjust_address_1): Same.
(offset_address): Same.
* emit-rtl.h: Same.
* except.c (dw2_build_landing_pads): Same.
(sjlj_emit_dispatch_table): Same.
* explow.c (allocate_dynamic_stack_space): Same.
(emit_stack_probe): Same.
(probe_stack_range): Same.
* expmed.c (store_bit_field_using_insv): Same.
(store_bit_field_1): Same.
(store_integral_bit_field): Same.
(extract_bit_field_using_extv): Same.
(extract_bit_field_1): Same.
(emit_cstore): Same.
* expr.c (emit_block_move_via_cpymem): Same.
(expand_cmpstrn_or_cmpmem): Same.
(set_storage_via_setmem): Same.
(emit_single_push_insn_1): Same.
(expand_assignment): Same.
(store_constructor): Same.
(expand_expr_real_2): Same.
(expand_expr_real_1): Same.
(try_casesi): Same.
* flags.h: Same.
* function.c (try_fit_stack_local): Same.
(assign_stack_local_1): Same.
(assign_stack_local): Same.
(cut_slot_from_list): Same.
(insert_slot_to_list): Same.
(max_slot_level): Same.
(move_slot_to_level): Same.
(temp_address_hasher::equal): Same.
(remove_unused_temp_slot_addresses): Same.
(assign_temp): Same.
(combine_temp_slots): Same.
(update_temp_slot_address): Same.
(preserve_temp_slots): Same.
* function.h: Same.
* fwprop.c: Same.
* gcc-rich-location.h: Same.
* gcov.c: Same.
* genattrtab.c (check_attr_test): Same.
(check_attr_value): Same.
(convert_set_attr_alternative): Same.
(convert_set_attr): Same.
(check_defs): Same.
(copy_boolean): Same.
(get_attr_value): Same.
(expand_delays): Same.
(make_length_attrs): Same.
(min_fn): Same.
(make_alternative_compare): Same.
(simplify_test_exp): Same.
(tests_attr_p): Same.
(get_attr_order): Same.
(clear_struct_flag): Same.
(gen_attr): Same.
(compares_alternatives_p): Same.
(gen_insn): Same.
(gen_delay): Same.
(find_attrs_to_cache): Same.
(write_test_expr): Same.
(walk_attr_value): Same.
(write_attr_get): Same.
(eliminate_known_true): Same.
(write_insn_cases): Same.
(write_attr_case): Same.
(write_attr_valueq): Same.
(write_attr_value): Same.
(write_dummy_eligible_delay): Same.
(next_comma_elt): Same.
(find_attr): Same.
(make_internal_attr): Same.
(copy_rtx_unchanging): Same.
(gen_insn_reserv): Same.
(check_tune_attr): Same.
(make_automaton_attrs): Same.
(handle_arg): Same.
* genextract.c (gen_insn): Same.
(VEC_char_to_string): Same.
* genmatch.c (print_operand): Same.
(lower): Same.
(parser::parse_operation): Same.
(parser::parse_capture): Same.
(parser::parse_c_expr): Same.
(parser::parse_simplify): Same.
(main): Same.
* genoutput.c (output_operand_data): Same.
(output_get_insn_name): Same.
(compare_operands): Same.
(place_operands): Same.
(process_template): Same.
(validate_insn_alternatives): Same.
(validate_insn_operands): Same.
(gen_expand): Same.
(note_constraint): Same.
* genpreds.c (write_one_predicate_function): Same.
(add_constraint): Same.
(process_define_register_constraint): Same.
(write_lookup_constraint_1): Same.
(write_lookup_constraint_array): Same.
(write_insn_constraint_len): Same.
(write_reg_class_for_constraint_1): Same.
(write_constraint_satisfied_p_array): Same.
* genrecog.c (optimize_subroutine_group): Same.
* gensupport.c (process_define_predicate): Same.
(queue_pattern): Same.
(remove_from_queue): Same.
(process_rtx): Same.
(is_predicable): Same.
(change_subst_attribute): Same.
(subst_pattern_match): Same.
(alter_constraints): Same.
(alter_attrs_for_insn): Same.
(shift_output_template): Same.
(alter_output_for_subst_insn): Same.
(process_one_cond_exec): Same.
(subst_dup): Same.
(process_define_cond_exec): Same.
(mnemonic_htab_callback): Same.
(gen_mnemonic_attr): Same.
(read_md_rtx): Same.
* ggc-page.c: Same.
* gimple-loop-interchange.cc (dump_reduction): Same.
(dump_induction): Same.
(loop_cand::~loop_cand): Same.
(free_data_refs_with_aux): Same.
(tree_loop_interchange::interchange_loops): Same.
(tree_loop_interchange::map_inductions_to_loop): Same.
(tree_loop_interchange::move_code_to_inner_loop): Same.
(compute_access_stride): Same.
(compute_access_strides): Same.
(proper_loop_form_for_interchange): Same.
(tree_loop_interchange_compute_ddrs): Same.
(prune_datarefs_not_in_loop): Same.
(prepare_data_references): Same.
(pass_linterchange::execute): Same.
* gimple-loop-jam.c (bb_prevents_fusion_p): Same.
(unroll_jam_possible_p): Same.
(fuse_loops): Same.
(adjust_unroll_factor): Same.
(tree_loop_unroll_and_jam): Same.
* gimple-loop-versioning.cc (loop_versioning::~loop_versioning): Same.
(loop_versioning::expensive_stmt_p): Same.
(loop_versioning::version_for_unity): Same.
(loop_versioning::dump_inner_likelihood): Same.
(loop_versioning::find_per_loop_multiplication): Same.
(loop_versioning::analyze_term_using_scevs): Same.
(loop_versioning::record_address_fragment): Same.
(loop_versioning::analyze_expr): Same.
(loop_versioning::analyze_blocks): Same.
(loop_versioning::prune_conditions): Same.
(loop_versioning::merge_loop_info): Same.
(loop_versioning::add_loop_to_queue): Same.
(loop_versioning::decide_whether_loop_is_versionable): Same.
(loop_versioning::make_versioning_decisions): Same.
(loop_versioning::implement_versioning_decisions): Same.
* gimple-ssa-evrp-analyze.c
(evrp_range_analyzer::record_ranges_from_phis): Same.
* gimple-ssa-store-merging.c (split_store::split_store): Same.
(count_multiple_uses): Same.
(split_group): Same.
(imm_store_chain_info::output_merged_store): Same.
(pass_store_merging::process_store): Same.
* gimple-ssa-strength-reduction.c (slsr_process_phi): Same.
* gimple-ssa-warn-alloca.c (adjusted_warn_limit): Same.
(is_max): Same.
(alloca_call_type): Same.
(pass_walloca::execute): Same.
* gimple-streamer-in.c (input_phi): Same.
(input_gimple_stmt): Same.
* gimple-streamer.h: Same.
* godump.c (go_force_record_alignment): Same.
(go_format_type): Same.
(go_output_type): Same.
(go_output_fndecl): Same.
(go_output_typedef): Same.
(keyword_hash_init): Same.
(find_dummy_types): Same.
* graph.c (draw_cfg_nodes_no_loops): Same.
(draw_cfg_nodes_for_loop): Same.
* hard-reg-set.h (hard_reg_set_iter_next): Same.
* hsa-brig.c: Same.
* hsa-common.h (hsa_internal_fn_hasher::equal): Same.
* hsa-dump.c (dump_hsa_cfun): Same.
* hsa-gen.c (gen_function_def_parameters): Same.
* hsa-regalloc.c (dump_hsa_cfun_regalloc): Same.
* input.c (dump_line_table_statistics): Same.
(test_lexer): Same.
* input.h: Same.
* internal-fn.c (get_multi_vector_move): Same.
(expand_load_lanes_optab_fn): Same.
(expand_GOMP_SIMT_ENTER_ALLOC): Same.
(expand_GOMP_SIMT_EXIT): Same.
(expand_GOMP_SIMT_LAST_LANE): Same.
(expand_GOMP_SIMT_ORDERED_PRED): Same.
(expand_GOMP_SIMT_VOTE_ANY): Same.
(expand_GOMP_SIMT_XCHG_BFLY): Same.
(expand_GOMP_SIMT_XCHG_IDX): Same.
(expand_addsub_overflow): Same.
(expand_neg_overflow): Same.
(expand_mul_overflow): Same.
(expand_call_mem_ref): Same.
(expand_mask_load_optab_fn): Same.
(expand_scatter_store_optab_fn): Same.
(expand_gather_load_optab_fn): Same.
* ipa-cp.c (ipa_get_parm_lattices): Same.
(print_all_lattices): Same.
(ignore_edge_p): Same.
(build_toporder_info): Same.
(free_toporder_info): Same.
(push_node_to_stack): Same.
(ipcp_lattice<valtype>::set_contains_variable): Same.
(set_agg_lats_to_bottom): Same.
(ipcp_bits_lattice::meet_with): Same.
(set_single_call_flag): Same.
(initialize_node_lattices): Same.
(ipa_get_jf_ancestor_result): Same.
(ipcp_verify_propagated_values): Same.
(propagate_scalar_across_jump_function): Same.
(propagate_context_across_jump_function): Same.
(propagate_bits_across_jump_function): Same.
(ipa_vr_operation_and_type_effects): Same.
(propagate_vr_across_jump_function): Same.
(set_check_aggs_by_ref): Same.
(set_chain_of_aglats_contains_variable): Same.
(merge_aggregate_lattices): Same.
(agg_pass_through_permissible_p): Same.
(propagate_aggs_across_jump_function): Same.
(call_passes_through_thunk_p): Same.
(propagate_constants_across_call): Same.
(devirtualization_time_bonus): Same.
(good_cloning_opportunity_p): Same.
(context_independent_aggregate_values): Same.
(gather_context_independent_values): Same.
(perform_estimation_of_a_value): Same.
(estimate_local_effects): Same.
(value_topo_info<valtype>::add_val): Same.
(add_all_node_vals_to_toposort): Same.
(value_topo_info<valtype>::propagate_effects): Same.
(ipcp_propagate_stage): Same.
(ipcp_discover_new_direct_edges): Same.
(same_node_or_its_all_contexts_clone_p): Same.
(cgraph_edge_brings_value_p): Same.
(gather_edges_for_value): Same.
(create_specialized_node): Same.
(find_more_scalar_values_for_callers_subset): Same.
(find_more_contexts_for_caller_subset): Same.
(copy_plats_to_inter): Same.
(intersect_aggregates_with_edge): Same.
(find_aggregate_values_for_callers_subset): Same.
(cgraph_edge_brings_all_agg_vals_for_node): Same.
(decide_about_value): Same.
(decide_whether_version_node): Same.
(spread_undeadness): Same.
(identify_dead_nodes): Same.
(ipcp_store_vr_results): Same.
* ipa-devirt.c (final_warning_record::grow_type_warnings): Same.
* ipa-fnsummary.c (ipa_fn_summary::account_size_time): Same.
(redirect_to_unreachable): Same.
(edge_set_predicate): Same.
(evaluate_conditions_for_known_args): Same.
(evaluate_properties_for_edge): Same.
(ipa_fn_summary_t::duplicate): Same.
(ipa_call_summary_t::duplicate): Same.
(dump_ipa_call_summary): Same.
(ipa_dump_fn_summary): Same.
(eliminated_by_inlining_prob): Same.
(set_cond_stmt_execution_predicate): Same.
(set_switch_stmt_execution_predicate): Same.
(compute_bb_predicates): Same.
(will_be_nonconstant_expr_predicate): Same.
(phi_result_unknown_predicate): Same.
(analyze_function_body): Same.
(compute_fn_summary): Same.
(estimate_edge_devirt_benefit): Same.
(estimate_edge_size_and_time): Same.
(estimate_calls_size_and_time): Same.
(estimate_node_size_and_time): Same.
(remap_edge_change_prob): Same.
(remap_edge_summaries): Same.
(ipa_merge_fn_summary_after_inlining): Same.
(ipa_fn_summary_generate): Same.
(inline_read_section): Same.
(ipa_fn_summary_read): Same.
(ipa_fn_summary_write): Same.
* ipa-fnsummary.h: Same.
* ipa-hsa.c (ipa_hsa_read_section): Same.
* ipa-icf-gimple.c (func_checker::compare_loops): Same.
* ipa-icf.c (sem_function::param_used_p): Same.
* ipa-inline-analysis.c (do_estimate_edge_time): Same.
* ipa-inline.c (edge_badness): Same.
(inline_small_functions): Same.
* ipa-polymorphic-call.c
(ipa_polymorphic_call_context::stream_out): Same.
* ipa-predicate.c (predicate::remap_after_duplication): Same.
(predicate::remap_after_inlining): Same.
(predicate::stream_out): Same.
* ipa-predicate.h: Same.
* ipa-profile.c (ipa_profile_read_summary): Same.
* ipa-prop.c (ipa_get_param_decl_index_1): Same.
(count_formal_params): Same.
(ipa_dump_param): Same.
(ipa_alloc_node_params): Same.
(ipa_print_node_jump_functions_for_edge): Same.
(ipa_print_node_jump_functions): Same.
(ipa_load_from_parm_agg): Same.
(get_ancestor_addr_info): Same.
(ipa_compute_jump_functions_for_edge): Same.
(ipa_analyze_virtual_call_uses): Same.
(ipa_analyze_stmt_uses): Same.
(ipa_analyze_params_uses_in_bb): Same.
(update_jump_functions_after_inlining): Same.
(try_decrement_rdesc_refcount): Same.
(ipa_impossible_devirt_target): Same.
(update_indirect_edges_after_inlining): Same.
(combine_controlled_uses_counters): Same.
(ipa_edge_args_sum_t::duplicate): Same.
(ipa_write_jump_function): Same.
(ipa_write_indirect_edge_info): Same.
(ipa_write_node_info): Same.
(ipa_read_edge_info): Same.
(ipa_prop_read_section): Same.
(read_replacements_section): Same.
* ipa-prop.h (ipa_get_param_count): Same.
(ipa_get_param): Same.
(ipa_get_type): Same.
(ipa_get_param_move_cost): Same.
(ipa_set_param_used): Same.
(ipa_get_controlled_uses): Same.
(ipa_set_controlled_uses): Same.
(ipa_get_cs_argument_count): Same.
* ipa-pure-const.c (analyze_function): Same.
(pure_const_read_summary): Same.
* ipa-ref.h: Same.
* ipa-reference.c (ipa_reference_read_optimization_summary): Same.
* ipa-split.c (test_nonssa_use): Same.
(dump_split_point): Same.
(dominated_by_forbidden): Same.
(split_part_set_ssa_name_p): Same.
(find_split_points): Same.
* ira-build.c (finish_loop_tree_nodes): Same.
(low_pressure_loop_node_p): Same.
* ira-color.c (ira_reuse_stack_slot): Same.
* ira-int.h: Same.
* ira.c (setup_reg_equiv): Same.
(print_insn_chain): Same.
(ira): Same.
* loop-doloop.c (doloop_condition_get): Same.
(add_test): Same.
(record_reg_sets): Same.
(doloop_optimize): Same.
* loop-init.c (loop_optimizer_init): Same.
(fix_loop_structure): Same.
* loop-invariant.c (merge_identical_invariants): Same.
(compute_always_reached): Same.
(find_exits): Same.
(may_assign_reg_p): Same.
(find_invariants_bb): Same.
(find_invariants_body): Same.
(replace_uses): Same.
(can_move_invariant_reg): Same.
(free_inv_motion_data): Same.
(move_single_loop_invariants): Same.
(change_pressure): Same.
(mark_ref_regs): Same.
(calculate_loop_reg_pressure): Same.
* loop-iv.c (biv_entry_hasher::equal): Same.
(iv_extend_to_rtx_code): Same.
(check_iv_ref_table_size): Same.
(clear_iv_info): Same.
(latch_dominating_def): Same.
(iv_get_reaching_def): Same.
(iv_constant): Same.
(iv_subreg): Same.
(iv_extend): Same.
(iv_neg): Same.
(iv_add): Same.
(iv_mult): Same.
(get_biv_step): Same.
(record_iv): Same.
(analyzed_for_bivness_p): Same.
(record_biv): Same.
(iv_analyze_biv): Same.
(iv_analyze_expr): Same.
(iv_analyze_def): Same.
(iv_analyze_op): Same.
(iv_analyze): Same.
(iv_analyze_result): Same.
(biv_p): Same.
(eliminate_implied_conditions): Same.
(simplify_using_initial_values): Same.
(shorten_into_mode): Same.
(canonicalize_iv_subregs): Same.
(determine_max_iter): Same.
(check_simple_exit): Same.
(find_simple_exit): Same.
(get_simple_loop_desc): Same.
* loop-unroll.c (report_unroll): Same.
(decide_unrolling): Same.
(unroll_loops): Same.
(loop_exit_at_end_p): Same.
(decide_unroll_constant_iterations): Same.
(unroll_loop_constant_iterations): Same.
(compare_and_jump_seq): Same.
(unroll_loop_runtime_iterations): Same.
(decide_unroll_stupid): Same.
(unroll_loop_stupid): Same.
(referenced_in_one_insn_in_loop_p): Same.
(reset_debug_uses_in_loop): Same.
(analyze_iv_to_split_insn): Same.
* lra-eliminations.c (lra_debug_elim_table): Same.
(setup_can_eliminate): Same.
(form_sum): Same.
(lra_get_elimination_hard_regno): Same.
(lra_eliminate_regs_1): Same.
(eliminate_regs_in_insn): Same.
(update_reg_eliminate): Same.
(init_elimination): Same.
(lra_eliminate): Same.
* lra-int.h: Same.
* lra-lives.c (initiate_live_solver): Same.
* lra-remat.c (create_remat_bb_data): Same.
* lra-spills.c (lra_spill): Same.
* lra.c (lra_set_insn_recog_data): Same.
(lra_set_used_insn_alternative_by_uid): Same.
(init_reg_info): Same.
(expand_reg_info): Same.
* lto-cgraph.c (output_symtab): Same.
(read_identifier): Same.
(get_alias_symbol): Same.
(input_node): Same.
(input_varpool_node): Same.
(input_ref): Same.
(input_edge): Same.
(input_cgraph_1): Same.
(input_refs): Same.
(input_symtab): Same.
(input_offload_tables): Same.
(output_cgraph_opt_summary): Same.
(input_edge_opt_summary): Same.
(input_cgraph_opt_section): Same.
* lto-section-in.c (lto_free_raw_section_data): Same.
(lto_create_simple_input_block): Same.
(lto_free_function_in_decl_state_for_node): Same.
* lto-streamer-in.c (lto_tag_check_set): Same.
(lto_location_cache::revert_location_cache): Same.
(lto_location_cache::input_location): Same.
(lto_input_location): Same.
(stream_input_location_now): Same.
(lto_input_tree_ref): Same.
(lto_input_eh_catch_list): Same.
(input_eh_region): Same.
(lto_init_eh): Same.
(make_new_block): Same.
(input_cfg): Same.
(fixup_call_stmt_edges): Same.
(input_struct_function_base): Same.
(input_function): Same.
(lto_read_body_or_constructor): Same.
(lto_read_tree_1): Same.
(lto_read_tree): Same.
(lto_input_scc): Same.
(lto_input_tree_1): Same.
(lto_input_toplevel_asms): Same.
(lto_input_mode_table): Same.
(lto_reader_init): Same.
(lto_data_in_create): Same.
* lto-streamer-out.c (output_cfg): Same.
* lto-streamer.h: Same.
* modulo-sched.c (duplicate_insns_of_cycles): Same.
(generate_prolog_epilog): Same.
(mark_loop_unsched): Same.
(dump_insn_location): Same.
(loop_canon_p): Same.
(sms_schedule): Same.
* omp-expand.c (expand_omp_for_ordered_loops): Same.
(expand_omp_for_generic): Same.
(expand_omp_for_static_nochunk): Same.
(expand_omp_for_static_chunk): Same.
(expand_omp_simd): Same.
(expand_omp_taskloop_for_inner): Same.
(expand_oacc_for): Same.
(expand_omp_atomic_pipeline): Same.
(mark_loops_in_oacc_kernels_region): Same.
* omp-offload.c (oacc_xform_loop): Same.
* omp-simd-clone.c (simd_clone_adjust): Same.
* optabs-query.c (get_traditional_extraction_insn): Same.
* optabs.c (expand_vector_broadcast): Same.
(expand_binop_directly): Same.
(expand_twoval_unop): Same.
(expand_twoval_binop): Same.
(expand_unop_direct): Same.
(emit_indirect_jump): Same.
(emit_conditional_move): Same.
(emit_conditional_neg_or_complement): Same.
(emit_conditional_add): Same.
(vector_compare_rtx): Same.
(expand_vec_perm_1): Same.
(expand_vec_perm_const): Same.
(expand_vec_cond_expr): Same.
(expand_vec_series_expr): Same.
(maybe_emit_atomic_exchange): Same.
(maybe_emit_sync_lock_test_and_set): Same.
(expand_atomic_compare_and_swap): Same.
(expand_atomic_load): Same.
(expand_atomic_store): Same.
(maybe_emit_op): Same.
(valid_multiword_target_p): Same.
(create_integer_operand): Same.
(maybe_legitimize_operand_same_code): Same.
(maybe_legitimize_operand): Same.
(create_convert_operand_from_type): Same.
(can_reuse_operands_p): Same.
(maybe_legitimize_operands): Same.
(maybe_gen_insn): Same.
(maybe_expand_insn): Same.
(maybe_expand_jump_insn): Same.
(expand_insn): Same.
* optabs.h (create_expand_operand): Same.
(create_fixed_operand): Same.
(create_output_operand): Same.
(create_input_operand): Same.
(create_convert_operand_to): Same.
(create_convert_operand_from): Same.
* optinfo.h: Same.
* poly-int.h: Same.
* predict.c (optimize_insn_for_speed_p): Same.
(optimize_loop_for_size_p): Same.
(optimize_loop_for_speed_p): Same.
(optimize_loop_nest_for_speed_p): Same.
(get_base_value): Same.
(predicted_by_loop_heuristics_p): Same.
(predict_extra_loop_exits): Same.
(predict_loops): Same.
(predict_paths_for_bb): Same.
(predict_paths_leading_to): Same.
(propagate_freq): Same.
(pass_profile::execute): Same.
* predict.h: Same.
* profile-count.c (profile_count::differs_from_p): Same.
(profile_probability::differs_lot_from_p): Same.
* profile-count.h: Same.
* profile.c (branch_prob): Same.
* regrename.c (free_chain_data): Same.
(mark_conflict): Same.
(create_new_chain): Same.
(merge_overlapping_regs): Same.
(init_rename_info): Same.
(merge_chains): Same.
(regrename_analyze): Same.
(regrename_do_replace): Same.
(scan_rtx_reg): Same.
(record_out_operands): Same.
(build_def_use): Same.
* regrename.h: Same.
* reload.h: Same.
* reload1.c (init_reload): Same.
(maybe_fix_stack_asms): Same.
(copy_reloads): Same.
(count_pseudo): Same.
(count_spilled_pseudo): Same.
(find_reg): Same.
(find_reload_regs): Same.
(select_reload_regs): Same.
(spill_hard_reg): Same.
(fixup_eh_region_note): Same.
(set_reload_reg): Same.
(allocate_reload_reg): Same.
(compute_reload_subreg_offset): Same.
(reload_adjust_reg_for_icode): Same.
(emit_input_reload_insns): Same.
(emit_output_reload_insns): Same.
(do_input_reload): Same.
(inherit_piecemeal_p): Same.
* rtl.h: Same.
* sanopt.c (maybe_get_dominating_check): Same.
(maybe_optimize_ubsan_ptr_ifn): Same.
(can_remove_asan_check): Same.
(maybe_optimize_asan_check_ifn): Same.
(sanopt_optimize_walker): Same.
* sched-deps.c (add_dependence_list): Same.
(chain_to_prev_insn): Same.
(add_insn_mem_dependence): Same.
(create_insn_reg_set): Same.
(maybe_extend_reg_info_p): Same.
(sched_analyze_reg): Same.
(sched_analyze_1): Same.
(get_implicit_reg_pending_clobbers): Same.
(chain_to_prev_insn_p): Same.
(deps_analyze_insn): Same.
(deps_start_bb): Same.
(sched_free_deps): Same.
(init_deps): Same.
(init_deps_reg_last): Same.
(free_deps): Same.
* sched-ebb.c: Same.
* sched-int.h: Same.
* sched-rgn.c (add_branch_dependences): Same.
(concat_insn_mem_list): Same.
(deps_join): Same.
(sched_rgn_compute_dependencies): Same.
* sel-sched-ir.c (reset_target_context): Same.
(copy_deps_context): Same.
(init_id_from_df): Same.
(has_dependence_p): Same.
(change_loops_latches): Same.
(bb_top_order_comparator): Same.
(make_region_from_loop_preheader): Same.
(sel_init_pipelining): Same.
(get_loop_nest_for_rgn): Same.
(make_regions_from_the_rest): Same.
(sel_is_loop_preheader_p): Same.
* sel-sched-ir.h (inner_loop_header_p): Same.
(get_all_loop_exits): Same.
* selftest.h: Same.
* sese.c (sese_build_liveouts): Same.
(sese_insert_phis_for_liveouts): Same.
* sese.h (defined_in_sese_p): Same.
* sreal.c (sreal::stream_out): Same.
* sreal.h: Same.
* streamer-hooks.h: Same.
* target-globals.c (save_target_globals): Same.
* target-globals.h: Same.
* target.def: Same.
* target.h: Same.
* targhooks.c (default_has_ifunc_p): Same.
(default_empty_mask_is_expensive): Same.
(default_init_cost): Same.
* targhooks.h: Same.
* toplev.c: Same.
* tree-affine.c (aff_combination_mult): Same.
(aff_combination_expand): Same.
(aff_combination_constant_multiple_p): Same.
* tree-affine.h: Same.
* tree-cfg.c (build_gimple_cfg): Same.
(replace_loop_annotate_in_block): Same.
(replace_uses_by): Same.
(remove_bb): Same.
(dump_cfg_stats): Same.
(gimple_duplicate_sese_region): Same.
(gimple_duplicate_sese_tail): Same.
(move_block_to_fn): Same.
(replace_block_vars_by_duplicates): Same.
(move_sese_region_to_fn): Same.
(print_loops_bb): Same.
(print_loop): Same.
(print_loops): Same.
(debug): Same.
(debug_loops): Same.
* tree-cfg.h: Same.
* tree-chrec.c (chrec_fold_plus_poly_poly): Same.
(chrec_fold_multiply_poly_poly): Same.
(chrec_evaluate): Same.
(chrec_component_in_loop_num): Same.
(reset_evolution_in_loop): Same.
(is_multivariate_chrec): Same.
(chrec_contains_symbols): Same.
(nb_vars_in_chrec): Same.
(chrec_convert_1): Same.
(chrec_convert_aggressive): Same.
* tree-chrec.h: Same.
* tree-core.h: Same.
* tree-data-ref.c (dump_data_dependence_relation): Same.
(canonicalize_base_object_address): Same.
(data_ref_compare_tree): Same.
(prune_runtime_alias_test_list): Same.
(get_segment_min_max): Same.
(create_intersect_range_checks): Same.
(conflict_fn_no_dependence): Same.
(object_address_invariant_in_loop_p): Same.
(analyze_ziv_subscript): Same.
(analyze_siv_subscript_cst_affine): Same.
(analyze_miv_subscript): Same.
(analyze_overlapping_iterations): Same.
(build_classic_dist_vector_1): Same.
(add_other_self_distances): Same.
(same_access_functions): Same.
(build_classic_dir_vector): Same.
(subscript_dependence_tester_1): Same.
(subscript_dependence_tester): Same.
(access_functions_are_affine_or_constant_p): Same.
(get_references_in_stmt): Same.
(loop_nest_has_data_refs): Same.
(graphite_find_data_references_in_stmt): Same.
(find_data_references_in_bb): Same.
(get_base_for_alignment): Same.
(find_loop_nest_1): Same.
(find_loop_nest): Same.
* tree-data-ref.h (dr_alignment): Same.
(ddr_dependence_level): Same.
* tree-if-conv.c (fold_build_cond_expr): Same.
(add_to_predicate_list): Same.
(add_to_dst_predicate_list): Same.
(phi_convertible_by_degenerating_args): Same.
(idx_within_array_bound): Same.
(all_preds_critical_p): Same.
(pred_blocks_visited_p): Same.
(predicate_bbs): Same.
(build_region): Same.
(if_convertible_loop_p_1): Same.
(is_cond_scalar_reduction): Same.
(predicate_scalar_phi): Same.
(remove_conditions_and_labels): Same.
(combine_blocks): Same.
(version_loop_for_if_conversion): Same.
(versionable_outer_loop_p): Same.
(ifcvt_local_dce): Same.
(tree_if_conversion): Same.
(pass_if_conversion::gate): Same.
* tree-if-conv.h: Same.
* tree-inline.c (maybe_move_debug_stmts_to_successors): Same.
* tree-loop-distribution.c (bb_top_order_cmp): Same.
(free_rdg): Same.
(stmt_has_scalar_dependences_outside_loop): Same.
(copy_loop_before): Same.
(create_bb_after_loop): Same.
(const_with_all_bytes_same): Same.
(generate_memset_builtin): Same.
(generate_memcpy_builtin): Same.
(destroy_loop): Same.
(build_rdg_partition_for_vertex): Same.
(compute_access_range): Same.
(data_ref_segment_size): Same.
(latch_dominated_by_data_ref): Same.
(compute_alias_check_pairs): Same.
(fuse_memset_builtins): Same.
(finalize_partitions): Same.
(find_seed_stmts_for_distribution): Same.
(prepare_perfect_loop_nest): Same.
* tree-parloops.c (lambda_transform_legal_p): Same.
(loop_parallel_p): Same.
(reduc_stmt_res): Same.
(add_field_for_name): Same.
(create_call_for_reduction_1): Same.
(replace_uses_in_bb_by): Same.
(transform_to_exit_first_loop_alt): Same.
(try_transform_to_exit_first_loop_alt): Same.
(transform_to_exit_first_loop): Same.
(num_phis): Same.
(gen_parallel_loop): Same.
(gather_scalar_reductions): Same.
(get_omp_data_i_param): Same.
(try_create_reduction_list): Same.
(oacc_entry_exit_single_gang): Same.
(parallelize_loops): Same.
* tree-pass.h: Same.
* tree-predcom.c (determine_offset): Same.
(last_always_executed_block): Same.
(split_data_refs_to_components): Same.
(suitable_component_p): Same.
(valid_initializer_p): Same.
(find_looparound_phi): Same.
(insert_looparound_copy): Same.
(add_looparound_copies): Same.
(determine_roots_comp): Same.
(predcom_tmp_var): Same.
(initialize_root_vars): Same.
(initialize_root_vars_store_elim_1): Same.
(initialize_root_vars_store_elim_2): Same.
(finalize_eliminated_stores): Same.
(initialize_root_vars_lm): Same.
(remove_stmt): Same.
(determine_unroll_factor): Same.
(execute_pred_commoning_cbck): Same.
(base_names_in_chain_on): Same.
(combine_chains): Same.
(pcom_stmt_dominates_stmt_p): Same.
(try_combine_chains): Same.
(prepare_initializers_chain_store_elim): Same.
(prepare_initializers_chain): Same.
(prepare_initializers): Same.
(prepare_finalizers_chain): Same.
(prepare_finalizers): Same.
(insert_init_seqs): Same.
* tree-scalar-evolution.c (loop_phi_node_p): Same.
(compute_overall_effect_of_inner_loop): Same.
(add_to_evolution_1): Same.
(add_to_evolution): Same.
(follow_ssa_edge_binary): Same.
(follow_ssa_edge_expr): Same.
(backedge_phi_arg_p): Same.
(follow_ssa_edge_in_condition_phi_branch): Same.
(follow_ssa_edge_in_condition_phi): Same.
(follow_ssa_edge_inner_loop_phi): Same.
(follow_ssa_edge): Same.
(analyze_evolution_in_loop): Same.
(analyze_initial_condition): Same.
(interpret_loop_phi): Same.
(interpret_condition_phi): Same.
(interpret_rhs_expr): Same.
(interpret_expr): Same.
(interpret_gimple_assign): Same.
(analyze_scalar_evolution_1): Same.
(analyze_scalar_evolution): Same.
(analyze_scalar_evolution_for_address_of): Same.
(get_instantiated_value_entry): Same.
(loop_closed_phi_def): Same.
(instantiate_scev_name): Same.
(instantiate_scev_poly): Same.
(instantiate_scev_binary): Same.
(instantiate_scev_convert): Same.
(instantiate_scev_not): Same.
(instantiate_scev_r): Same.
(instantiate_scev): Same.
(resolve_mixers): Same.
(initialize_scalar_evolutions_analyzer): Same.
(scev_reset_htab): Same.
(scev_reset): Same.
(derive_simple_iv_with_niters): Same.
(simple_iv_with_niters): Same.
(expression_expensive_p): Same.
(final_value_replacement_loop): Same.
* tree-scalar-evolution.h (block_before_loop): Same.
* tree-ssa-address.h: Same.
* tree-ssa-dce.c (find_obviously_necessary_stmts): Same.
* tree-ssa-dom.c (edge_info::record_simple_equiv): Same.
(record_edge_info): Same.
* tree-ssa-live.c (var_map_base_fini): Same.
(remove_unused_locals): Same.
* tree-ssa-live.h: Same.
* tree-ssa-loop-ch.c (should_duplicate_loop_header_p): Same.
(pass_ch_vect::execute): Same.
(pass_ch::process_loop_p): Same.
* tree-ssa-loop-im.c (mem_ref_hasher::hash): Same.
(movement_possibility): Same.
(outermost_invariant_loop): Same.
(stmt_cost): Same.
(determine_max_movement): Same.
(invariantness_dom_walker::before_dom_children): Same.
(move_computations): Same.
(may_move_till): Same.
(force_move_till_op): Same.
(force_move_till): Same.
(memref_free): Same.
(record_mem_ref_loc): Same.
(set_ref_stored_in_loop): Same.
(mark_ref_stored): Same.
(sort_bbs_in_loop_postorder_cmp): Same.
(sort_locs_in_loop_postorder_cmp): Same.
(analyze_memory_references): Same.
(mem_refs_may_alias_p): Same.
(find_ref_loc_in_loop_cmp): Same.
(rewrite_mem_ref_loc::operator): Same.
(first_mem_ref_loc_1::operator): Same.
(sm_set_flag_if_changed::operator): Same.
(execute_sm_if_changed_flag_set): Same.
(execute_sm): Same.
(hoist_memory_references): Same.
(ref_always_accessed::operator): Same.
(refs_independent_p): Same.
(record_dep_loop): Same.
(ref_indep_loop_p_1): Same.
(ref_indep_loop_p): Same.
(can_sm_ref_p): Same.
(find_refs_for_sm): Same.
(loop_suitable_for_sm): Same.
(store_motion_loop): Same.
(store_motion): Same.
(fill_always_executed_in): Same.
* tree-ssa-loop-ivcanon.c (constant_after_peeling): Same.
(estimated_unrolled_size): Same.
(loop_edge_to_cancel): Same.
(remove_exits_and_undefined_stmts): Same.
(remove_redundant_iv_tests): Same.
(unloop_loops): Same.
(estimated_peeled_sequence_size): Same.
(try_peel_loop): Same.
(canonicalize_loop_induction_variables): Same.
(canonicalize_induction_variables): Same.
* tree-ssa-loop-ivopts.c (iv_inv_expr_hasher::equal): Same.
(name_info): Same.
(stmt_after_inc_pos): Same.
(contains_abnormal_ssa_name_p): Same.
(niter_for_exit): Same.
(find_bivs): Same.
(mark_bivs): Same.
(find_givs_in_bb): Same.
(find_induction_variables): Same.
(find_interesting_uses_cond): Same.
(outermost_invariant_loop_for_expr): Same.
(idx_find_step): Same.
(add_candidate_1): Same.
(add_iv_candidate_derived_from_uses): Same.
(alloc_use_cost_map): Same.
(prepare_decl_rtl): Same.
(generic_predict_doloop_p): Same.
(computation_cost): Same.
(determine_common_wider_type): Same.
(get_computation_aff_1): Same.
(get_use_type): Same.
(determine_group_iv_cost_address): Same.
(iv_period): Same.
(difference_cannot_overflow_p): Same.
(may_eliminate_iv): Same.
(determine_set_costs): Same.
(cheaper_cost_pair): Same.
(compare_cost_pair): Same.
(iv_ca_cand_for_group): Same.
(iv_ca_recount_cost): Same.
(iv_ca_set_remove_invs): Same.
(iv_ca_set_no_cp): Same.
(iv_ca_set_add_invs): Same.
(iv_ca_set_cp): Same.
(iv_ca_add_group): Same.
(iv_ca_cost): Same.
(iv_ca_compare_deps): Same.
(iv_ca_delta_reverse): Same.
(iv_ca_delta_commit): Same.
(iv_ca_cand_used_p): Same.
(iv_ca_delta_free): Same.
(iv_ca_new): Same.
(iv_ca_free): Same.
(iv_ca_dump): Same.
(iv_ca_extend): Same.
(iv_ca_narrow): Same.
(iv_ca_prune): Same.
(cheaper_cost_with_cand): Same.
(iv_ca_replace): Same.
(try_add_cand_for): Same.
(get_initial_solution): Same.
(try_improve_iv_set): Same.
(find_optimal_iv_set_1): Same.
(create_new_iv): Same.
(rewrite_use_compare): Same.
(remove_unused_ivs): Same.
(determine_scaling_factor): Same.
* tree-ssa-loop-ivopts.h: Same.
* tree-ssa-loop-manip.c (create_iv): Same.
(compute_live_loop_exits): Same.
(add_exit_phi): Same.
(add_exit_phis): Same.
(find_uses_to_rename_use): Same.
(find_uses_to_rename_def): Same.
(find_uses_to_rename_in_loop): Same.
(rewrite_into_loop_closed_ssa): Same.
(check_loop_closed_ssa_bb): Same.
(split_loop_exit_edge): Same.
(ip_end_pos): Same.
(ip_normal_pos): Same.
(copy_phi_node_args): Same.
(gimple_duplicate_loop_to_header_edge): Same.
(can_unroll_loop_p): Same.
(determine_exit_conditions): Same.
(scale_dominated_blocks_in_loop): Same.
(niter_for_unrolled_loop): Same.
(tree_transform_and_unroll_loop): Same.
(rewrite_all_phi_nodes_with_iv): Same.
* tree-ssa-loop-manip.h: Same.
* tree-ssa-loop-niter.c (number_of_iterations_ne_max): Same.
(number_of_iterations_ne): Same.
(assert_no_overflow_lt): Same.
(assert_loop_rolls_lt): Same.
(number_of_iterations_lt): Same.
(adjust_cond_for_loop_until_wrap): Same.
(tree_simplify_using_condition): Same.
(simplify_using_initial_conditions): Same.
(simplify_using_outer_evolutions): Same.
(loop_only_exit_p): Same.
(ssa_defined_by_minus_one_stmt_p): Same.
(number_of_iterations_popcount): Same.
(number_of_iterations_exit): Same.
(find_loop_niter): Same.
(finite_loop_p): Same.
(chain_of_csts_start): Same.
(get_val_for): Same.
(loop_niter_by_eval): Same.
(derive_constant_upper_bound_ops): Same.
(do_warn_aggressive_loop_optimizations): Same.
(record_estimate): Same.
(get_cst_init_from_scev): Same.
(record_nonwrapping_iv): Same.
(idx_infer_loop_bounds): Same.
(infer_loop_bounds_from_ref): Same.
(infer_loop_bounds_from_array): Same.
(infer_loop_bounds_from_pointer_arith): Same.
(infer_loop_bounds_from_signedness): Same.
(bound_index): Same.
(discover_iteration_bound_by_body_walk): Same.
(maybe_lower_iteration_bound): Same.
(estimate_numbers_of_iterations): Same.
(estimated_loop_iterations): Same.
(estimated_loop_iterations_int): Same.
(max_loop_iterations): Same.
(max_loop_iterations_int): Same.
(likely_max_loop_iterations): Same.
(likely_max_loop_iterations_int): Same.
(estimated_stmt_executions_int): Same.
(max_stmt_executions): Same.
(likely_max_stmt_executions): Same.
(estimated_stmt_executions): Same.
(stmt_dominates_stmt_p): Same.
(nowrap_type_p): Same.
(loop_exits_before_overflow): Same.
(scev_var_range_cant_overflow): Same.
(scev_probably_wraps_p): Same.
(free_numbers_of_iterations_estimates): Same.
* tree-ssa-loop-niter.h: Same.
* tree-ssa-loop-prefetch.c (release_mem_refs): Same.
(idx_analyze_ref): Same.
(analyze_ref): Same.
(gather_memory_references_ref): Same.
(mark_nontemporal_store): Same.
(emit_mfence_after_loop): Same.
(may_use_storent_in_loop_p): Same.
(mark_nontemporal_stores): Same.
(should_unroll_loop_p): Same.
(volume_of_dist_vector): Same.
(add_subscript_strides): Same.
(self_reuse_distance): Same.
(insn_to_prefetch_ratio_too_small_p): Same.
* tree-ssa-loop-split.c (split_at_bb_p): Same.
(patch_loop_exit): Same.
(find_or_create_guard_phi): Same.
(easy_exit_values): Same.
(connect_loop_phis): Same.
(connect_loops): Same.
(compute_new_first_bound): Same.
(split_loop): Same.
(tree_ssa_split_loops): Same.
* tree-ssa-loop-unswitch.c (tree_ssa_unswitch_loops): Same.
(is_maybe_undefined): Same.
(tree_may_unswitch_on): Same.
(simplify_using_entry_checks): Same.
(tree_unswitch_single_loop): Same.
(tree_unswitch_loop): Same.
(tree_unswitch_outer_loop): Same.
(empty_bb_without_guard_p): Same.
(used_outside_loop_p): Same.
(get_vop_from_header): Same.
(hoist_guard): Same.
* tree-ssa-loop.c (gate_oacc_kernels): Same.
(get_lsm_tmp_name): Same.
* tree-ssa-loop.h: Same.
* tree-ssa-reassoc.c (add_repeat_to_ops_vec): Same.
(build_and_add_sum): Same.
(no_side_effect_bb): Same.
(get_ops): Same.
(linearize_expr): Same.
(should_break_up_subtract): Same.
(linearize_expr_tree): Same.
* tree-ssa-scopedtables.c: Same.
* tree-ssa-scopedtables.h: Same.
* tree-ssa-structalias.c (condense_visit): Same.
(label_visit): Same.
(dump_pred_graph): Same.
(perform_var_substitution): Same.
(move_complex_constraints): Same.
(remove_preds_and_fake_succs): Same.
* tree-ssa-threadupdate.c (dbds_continue_enumeration_p): Same.
(determine_bb_domination_status): Same.
(duplicate_thread_path): Same.
(thread_through_all_blocks): Same.
* tree-ssa-threadupdate.h: Same.
* tree-streamer-in.c (streamer_read_string_cst): Same.
(input_identifier): Same.
(unpack_ts_type_common_value_fields): Same.
(unpack_ts_block_value_fields): Same.
(unpack_ts_translation_unit_decl_value_fields): Same.
(unpack_ts_omp_clause_value_fields): Same.
(streamer_read_tree_bitfields): Same.
(streamer_alloc_tree): Same.
(lto_input_ts_common_tree_pointers): Same.
(lto_input_ts_vector_tree_pointers): Same.
(lto_input_ts_poly_tree_pointers): Same.
(lto_input_ts_complex_tree_pointers): Same.
(lto_input_ts_decl_minimal_tree_pointers): Same.
(lto_input_ts_decl_common_tree_pointers): Same.
(lto_input_ts_decl_non_common_tree_pointers): Same.
(lto_input_ts_decl_with_vis_tree_pointers): Same.
(lto_input_ts_field_decl_tree_pointers): Same.
(lto_input_ts_function_decl_tree_pointers): Same.
(lto_input_ts_type_common_tree_pointers): Same.
(lto_input_ts_type_non_common_tree_pointers): Same.
(lto_input_ts_list_tree_pointers): Same.
(lto_input_ts_vec_tree_pointers): Same.
(lto_input_ts_exp_tree_pointers): Same.
(lto_input_ts_block_tree_pointers): Same.
(lto_input_ts_binfo_tree_pointers): Same.
(lto_input_ts_constructor_tree_pointers): Same.
(lto_input_ts_omp_clause_tree_pointers): Same.
(streamer_read_tree_body): Same.
* tree-streamer.h: Same.
* tree-switch-conversion.c (bit_test_cluster::is_beneficial): Same.
* tree-vect-data-refs.c (vect_get_smallest_scalar_type): Same.
(vect_analyze_possibly_independent_ddr): Same.
(vect_analyze_data_ref_dependence): Same.
(vect_compute_data_ref_alignment): Same.
(vect_enhance_data_refs_alignment): Same.
(vect_analyze_data_ref_access): Same.
(vect_check_gather_scatter): Same.
(vect_find_stmt_data_reference): Same.
(vect_create_addr_base_for_vector_ref): Same.
(vect_setup_realignment): Same.
(vect_supportable_dr_alignment): Same.
* tree-vect-loop-manip.c (rename_variables_in_bb): Same.
(adjust_phi_and_debug_stmts): Same.
(vect_set_loop_mask): Same.
(add_preheader_seq): Same.
(vect_maybe_permute_loop_masks): Same.
(vect_set_loop_masks_directly): Same.
(vect_set_loop_condition_masked): Same.
(vect_set_loop_condition_unmasked): Same.
(slpeel_duplicate_current_defs_from_edges): Same.
(slpeel_add_loop_guard): Same.
(slpeel_can_duplicate_loop_p): Same.
(create_lcssa_for_virtual_phi): Same.
(iv_phi_p): Same.
(vect_update_ivs_after_vectorizer): Same.
(vect_gen_vector_loop_niters_mult_vf): Same.
(slpeel_update_phi_nodes_for_loops): Same.
(slpeel_update_phi_nodes_for_guard1): Same.
(find_guard_arg): Same.
(slpeel_update_phi_nodes_for_guard2): Same.
(slpeel_update_phi_nodes_for_lcssa): Same.
(vect_do_peeling): Same.
(vect_create_cond_for_alias_checks): Same.
(vect_loop_versioning): Same.
* tree-vect-loop.c (vect_determine_vf_for_stmt): Same.
(vect_inner_phi_in_double_reduction_p): Same.
(vect_analyze_scalar_cycles_1): Same.
(vect_fixup_scalar_cycles_with_patterns): Same.
(vect_get_loop_niters): Same.
(bb_in_loop_p): Same.
(vect_get_max_nscalars_per_iter): Same.
(vect_verify_full_masking): Same.
(vect_compute_single_scalar_iteration_cost): Same.
(vect_analyze_loop_form_1): Same.
(vect_analyze_loop_form): Same.
(vect_active_double_reduction_p): Same.
(vect_analyze_loop_operations): Same.
(neutral_op_for_slp_reduction): Same.
(vect_is_simple_reduction): Same.
(vect_model_reduction_cost): Same.
(get_initial_def_for_reduction): Same.
(get_initial_defs_for_reduction): Same.
(vect_create_epilog_for_reduction): Same.
(vectorize_fold_left_reduction): Same.
(vectorizable_reduction): Same.
(vectorizable_induction): Same.
(vectorizable_live_operation): Same.
(loop_niters_no_overflow): Same.
(vect_get_loop_mask): Same.
(vect_transform_loop_stmt): Same.
(vect_transform_loop): Same.
* tree-vect-patterns.c (vect_reassociating_reduction_p): Same.
(vect_determine_precisions): Same.
(vect_pattern_recog_1): Same.
* tree-vect-slp.c (vect_analyze_slp_instance): Same.
* tree-vect-stmts.c (stmt_vectype): Same.
(process_use): Same.
(vect_init_vector_1): Same.
(vect_truncate_gather_scatter_offset): Same.
(get_group_load_store_type): Same.
(vect_build_gather_load_calls): Same.
(vect_get_strided_load_store_ops): Same.
(vectorizable_simd_clone_call): Same.
(vectorizable_store): Same.
(permute_vec_elements): Same.
(vectorizable_load): Same.
(vect_transform_stmt): Same.
(supportable_widening_operation): Same.
* tree-vectorizer.c (vec_info::replace_stmt): Same.
(vec_info::free_stmt_vec_info): Same.
(vect_free_loop_info_assumptions): Same.
(vect_loop_vectorized_call): Same.
(set_uid_loop_bbs): Same.
(vectorize_loops): Same.
* tree-vectorizer.h (STMT_VINFO_BB_VINFO): Same.
* tree.c (add_tree_to_fld_list): Same.
(fld_type_variant_equal_p): Same.
(fld_decl_context): Same.
(fld_incomplete_type_of): Same.
(free_lang_data_in_binfo): Same.
(need_assembler_name_p): Same.
(find_decls_types_r): Same.
(get_eh_types_for_runtime): Same.
(find_decls_types_in_eh_region): Same.
(find_decls_types_in_node): Same.
(assign_assembler_name_if_needed): Same.
* value-prof.c (stream_out_histogram_value): Same.
* value-prof.h: Same.
* var-tracking.c (use_narrower_mode): Same.
(prepare_call_arguments): Same.
(vt_expand_loc_callback): Same.
(resolve_expansions_pending_recursion): Same.
(vt_expand_loc): Same.
* varasm.c (const_hash_1): Same.
(compare_constant): Same.
(tree_output_constant_def): Same.
(simplify_subtraction): Same.
(get_pool_constant): Same.
(output_constant_pool_2): Same.
(output_constant_pool_1): Same.
(mark_constants_in_pattern): Same.
(mark_constant_pool): Same.
(get_section_anchor): Same.
* vr-values.c (compare_range_with_value): Same.
(vr_values::extract_range_from_phi_node): Same.
* vr-values.h: Same.
* web.c (unionfind_union): Same.
* wide-int.h: Same.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/auto-profile.c
trunk/gcc/basic-block.h
trunk/gcc/bitmap.c
trunk/gcc/bitmap.h
trunk/gcc/builtins.c
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-opts.c
trunk/gcc/c-family/c-pretty-print.h
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-decl.c
trunk/gcc/c/c-parser.c
trunk/gcc/c/c-tree.h
trunk/gcc/c/gimple-parser.c
trunk/gcc/caller-save.c
trunk/gcc/cfg.c
trunk/gcc/cfg.h
trunk/gcc/cfganal.h
trunk/gcc/cfgexpand.c
trunk/gcc/cfghooks.c
trunk/gcc/cfghooks.h
trunk/gcc/cfgloop.c
trunk/gcc/cfgloop.h
trunk/gcc/cfgloopanal.c
trunk/gcc/cfgloopmanip.c
trunk/gcc/cfgloopmanip.h
trunk/gcc/cgraph.h
trunk/gcc/cgraphbuild.c
trunk/gcc/combine.c
trunk/gcc/config/i386/i386-features.c
trunk/gcc/config/i386/i386-features.h
trunk/gcc/config/i386/i386.c
trunk/gcc/configure.ac
trunk/gcc/coretypes.h
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/search.c
trunk/gcc/cp/semantics.c
trunk/gcc/data-streamer-in.c
trunk/gcc/data-streamer.h
trunk/gcc/ddg.c
trunk/gcc/df-core.c
trunk/gcc/df-problems.c
trunk/gcc/df-scan.c
trunk/gcc/df.h
trunk/gcc/doc/tm.texi
trunk/gcc/dse.c
trunk/gcc/dumpfile.h
trunk/gcc/emit-rtl.c
trunk/gcc/emit-rtl.h
trunk/gcc/except.c
trunk/gcc/explow.c
trunk/gcc/expmed.c
trunk/gcc/expr.c
trunk/gcc/flags.h
trunk/gcc/function.c
trunk/gcc/function.h
trunk/gcc/fwprop.c
trunk/gcc/gcc-rich-location.h
trunk/gcc/gcov.c
trunk/gcc/genattrtab.c
trunk/gcc/genextract.c
trunk/gcc/genmatch.c
trunk/gcc/genoutput.c
trunk/gcc/genpreds.c
trunk/gcc/genrecog.c
trunk/gcc/gensupport.c
trunk/gcc/ggc-page.c
trunk/gcc/gimple-loop-interchange.cc
trunk/gcc/gimple-loop-jam.c
trunk/gcc/gimple-loop-versioning.cc
trunk/gcc/gimple-ssa-evrp-analyze.c
trunk/gcc/gimple-ssa-store-merging.c
trunk/gcc/gimple-ssa-strength-reduction.c
trunk/gcc/gimple-ssa-warn-alloca.c
trunk/gcc/gimple-streamer-in.c
trunk/gcc/gimple-streamer.h
trunk/gcc/godump.c
trunk/gcc/graph.c
trunk/gcc/hard-reg-set.h
trunk/gcc/hsa-brig.c
trunk/gcc/hsa-common.h
trunk/gcc/hsa-dump.c
trunk/gcc/hsa-gen.c
trunk/gcc/hsa-regalloc.c
trunk/gcc/input.c
trunk/gcc/input.h
trunk/gcc/internal-fn.c
trunk/gcc/ipa-cp.c
trunk/gcc/ipa-devirt.c
trunk/gcc/ipa-fnsummary.c
trunk/gcc/ipa-fnsummary.h
trunk/gcc/ipa-hsa.c
trunk/gcc/ipa-icf-gimple.c
trunk/gcc/ipa-icf.c
trunk/gcc/ipa-inline-analysis.c
trunk/gcc/ipa-inline.c
trunk/gcc/ipa-polymorphic-call.c
trunk/gcc/ipa-predicate.c
trunk/gcc/ipa-predicate.h
trunk/gcc/ipa-profile.c
trunk/gcc/ipa-prop.c
trunk/gcc/ipa-prop.h
trunk/gcc/ipa-pure-const.c
trunk/gcc/ipa-ref.h
trunk/gcc/ipa-reference.c
trunk/gcc/ipa-split.c
trunk/gcc/ira-build.c
trunk/gcc/ira-color.c
trunk/gcc/ira-int.h
trunk/gcc/ira.c
trunk/gcc/loop-doloop.c
trunk/gcc/loop-init.c
trunk/gcc/loop-invariant.c
trunk/gcc/loop-iv.c
trunk/gcc/loop-unroll.c
trunk/gcc/lra-eliminations.c
trunk/gcc/lra-int.h
trunk/gcc/lra-lives.c
trunk/gcc/lra-remat.c
trunk/gcc/lra-spills.c
trunk/gcc/lra.c
trunk/gcc/lto-cgraph.c
trunk/gcc/lto-section-in.c
trunk/gcc/lto-streamer-in.c
trunk/gcc/lto-streamer-out.c
trunk/gcc/lto-streamer.h
trunk/gcc/lto/ChangeLog
trunk/gcc/lto/lto-common.c
trunk/gcc/modulo-sched.c
trunk/gcc/omp-expand.c
trunk/gcc/omp-offload.c
trunk/gcc/omp-simd-clone.c
trunk/gcc/optabs-query.c
trunk/gcc/optabs.c
trunk/gcc/optabs.h
trunk/gcc/optinfo.h
trunk/gcc/poly-int.h
trunk/gcc/predict.c
trunk/gcc/predict.h
trunk/gcc/profile-count.c
trunk/gcc/profile-count.h
trunk/gcc/profile.c
trunk/gcc/regrename.c
trunk/gcc/regrename.h
trunk/gcc/reload.h
trunk/gcc/reload1.c
trunk/gcc/rtl.h
trunk/gcc/sanopt.c
trunk/gcc/sched-deps.c
trunk/gcc/sched-ebb.c
trunk/gcc/sched-int.h
trunk/gcc/sched-rgn.c
trunk/gcc/sel-sched-ir.c
trunk/gcc/sel-sched-ir.h
trunk/gcc/selftest.h
trunk/gcc/sese.c
trunk/gcc/sese.h
trunk/gcc/sreal.c
trunk/gcc/sreal.h
trunk/gcc/streamer-hooks.h
trunk/gcc/target-globals.c
trunk/gcc/target-globals.h
trunk/gcc/target.def
trunk/gcc/target.h
trunk/gcc/targhooks.c
trunk/gcc/targhooks.h
trunk/gcc/toplev.c
trunk/gcc/tree-affine.c
trunk/gcc/tree-affine.h
trunk/gcc/tree-cfg.c
trunk/gcc/tree-cfg.h
trunk/gcc/tree-chrec.c
trunk/gcc/tree-chrec.h
trunk/gcc/tree-core.h
trunk/gcc/tree-data-ref.c
trunk/gcc/tree-data-ref.h
trunk/gcc/tree-if-conv.c
trunk/gcc/tree-if-conv.h
trunk/gcc/tree-inline.c
trunk/gcc/tree-loop-distribution.c
trunk/gcc/tree-parloops.c
trunk/gcc/tree-pass.h
trunk/gcc/tree-predcom.c
trunk/gcc/tree-scalar-evolution.c
trunk/gcc/tree-scalar-evolution.h
trunk/gcc/tree-ssa-address.h
trunk/gcc/tree-ssa-dce.c
trunk/gcc/tree-ssa-dom.c
trunk/gcc/tree-ssa-live.c
trunk/gcc/tree-ssa-live.h
trunk/gcc/tree-ssa-loop-ch.c
trunk/gcc/tree-ssa-loop-im.c
trunk/gcc/tree-ssa-loop-ivcanon.c
trunk/gcc/tree-ssa-loop-ivopts.c
trunk/gcc/tree-ssa-loop-ivopts.h
trunk/gcc/tree-ssa-loop-manip.c
trunk/gcc/tree-ssa-loop-manip.h
trunk/gcc/tree-ssa-loop-niter.c
trunk/gcc/tree-ssa-loop-niter.h
trunk/gcc/tree-ssa-loop-prefetch.c
trunk/gcc/tree-ssa-loop-split.c
trunk/gcc/tree-ssa-loop-unswitch.c
trunk/gcc/tree-ssa-loop.c
trunk/gcc/tree-ssa-loop.h
trunk/gcc/tree-ssa-reassoc.c
trunk/gcc/tree-ssa-scopedtables.c
trunk/gcc/tree-ssa-scopedtables.h
trunk/gcc/tree-ssa-structalias.c
trunk/gcc/tree-ssa-threadupdate.c
trunk/gcc/tree-ssa-threadupdate.h
trunk/gcc/tree-streamer-in.c
trunk/gcc/tree-streamer.h
trunk/gcc/tree-switch-conversion.c
trunk/gcc/tree-vect-data-refs.c
trunk/gcc/tree-vect-loop-manip.c
trunk/gcc/tree-vect-loop.c
trunk/gcc/tree-vect-patterns.c
trunk/gcc/tree-vect-slp.c
trunk/gcc/tree-vect-stmts.c
trunk/gcc/tree-vectorizer.c
trunk/gcc/tree-vectorizer.h
trunk/gcc/tree.c
trunk/gcc/value-prof.c
trunk/gcc/value-prof.h
trunk/gcc/var-tracking.c
trunk/gcc/varasm.c
trunk/gcc/vr-values.c
trunk/gcc/vr-values.h
trunk/gcc/web.c
trunk/gcc/wide-int.h
trunk/libcpp/directives-only.c
trunk/libcpp/directives.c
trunk/libcpp/files.c
trunk/libcpp/include/cpplib.h
trunk/libcpp/include/line-map.h
trunk/libcpp/include/mkdeps.h
trunk/libcpp/init.c
trunk/libcpp/internal.h
trunk/libcpp/line-map.c
trunk/libcpp/mkdeps.c
>From gcc-bugs-return-648570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 18:40:35 2019
Return-Path: <gcc-bugs-return-648570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52975 invoked by alias); 9 Jul 2019 18:40: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 52894 invoked by uid 48); 9 Jul 2019 18:40:31 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91126] [10 regression] Incorrect constant propagation of BIT_FIELD_REF
Date: Tue, 09 Jul 2019 18:40: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: rguenth 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-91126-4-P9HcKHwOUD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00682.txt.bz2
Content-length: 623
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91126
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-07-09
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-648571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 19:01:20 2019
Return-Path: <gcc-bugs-return-648571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71995 invoked by alias); 9 Jul 2019 19:01: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 71936 invoked by uid 48); 9 Jul 2019 19:01:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91126] [10 regression] Incorrect constant propagation of BIT_FIELD_REF
Date: Tue, 09 Jul 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: 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: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91126-4-AAwKeWWi6W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00683.txt.bz2
Content-length: 768
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91126
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the issue is the usual GET_MODE_SIZE != ref->size. native_encode_int
encodes two 32bit numbers (but only 3 bytes from them, in big-endian) while VN
expects it to encode a 3-byte 24bit number. There's the possibility to disable
handling of non-mode precision entities or properly fix it (I think we "simply"
need to offset the encoding for big-endian). Note the issue is probably latent
for the other places VN uses native_encode_expr on non-mode precision entities.
There's already a guard on non-mode precision extracts but not for
mode-precision extracts of non-mode precision values which I think has the very
same issue.
>From gcc-bugs-return-648572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 19:03:18 2019
Return-Path: <gcc-bugs-return-648572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77886 invoked by alias); 9 Jul 2019 19:03: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 77845 invoked by uid 48); 9 Jul 2019 19:03:15 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91126] [10 regression] Incorrect constant propagation of BIT_FIELD_REF
Date: Tue, 09 Jul 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: 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-91126-4-cfPutCnEoU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00684.txt.bz2
Content-length: 420
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91126
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 46581
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46581&action=edit
patch
Untested patch that fixes the issue.
Value numbering stmt = _1 = BIT_FIELD_REF <a, 32, 0>;
Successfully combined 2 partial definitions
Setting value number of _1 to 4278124286 (changed)
>From gcc-bugs-return-648573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 19:18:49 2019
Return-Path: <gcc-bugs-return-648573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96836 invoked by alias); 9 Jul 2019 19:18: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 96799 invoked by uid 48); 9 Jul 2019 19:18:46 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91126] [10 regression] Incorrect constant propagation of BIT_FIELD_REF
Date: Tue, 09 Jul 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: 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: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91126-4-9UHfTnDMw0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00685.txt.bz2
Content-length: 407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91126
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Oh, and I think it's a pity we're trying to stay away from optimizing the
bitfield cases. I suppose we could also use encode_tree_to_bitpos from
the store-merging pass for this purpose, but while operating on byte
granularity encodes/interprets only we can use the simple offsetting.
>From gcc-bugs-return-648574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 22:20:33 2019
Return-Path: <gcc-bugs-return-648574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1274 invoked by alias); 9 Jul 2019 22:20: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 1227 invoked by uid 48); 9 Jul 2019 22:20:30 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67678] Nested class can be re-declared after definition
Date: Tue, 09 Jul 2019 22: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: 5.2.1
X-Bugzilla-Keywords: accepts-invalid
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 cf_known_to_fail
Message-ID: <bug-67678-4-d5wwL4jHKB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00686.txt.bz2
Content-length: 748
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67678
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-09
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |10.0, 5.1.0, 6.4.0, 7.3.0,
| |8.3.0, 9.1.0
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
I just ran into this myself. Confirmed for the missing diagnostic.
>From gcc-bugs-return-648575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 22:40:19 2019
Return-Path: <gcc-bugs-return-648575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39204 invoked by alias); 9 Jul 2019 22:40: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 38715 invoked by uid 48); 9 Jul 2019 22:40:14 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87256] hppa spends huge amount of time in synth_mult()
Date: Tue, 09 Jul 2019 22:40: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: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin 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-87256-4-71vYA8ZAgD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87256-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87256-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00687.txt.bz2
Content-length: 167
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87256
--- Comment #9 from John David Anglin <danglin at gcc dot gnu.org> ---
Also appears to occur building glusterfs.
>From gcc-bugs-return-648576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 22:52:26 2019
Return-Path: <gcc-bugs-return-648576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56193 invoked by alias); 9 Jul 2019 22:52: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 56185 invoked by uid 89); 9 Jul 2019 22:52:26 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: =?ISO-8859-1?Q?Yes, score=7.5 required=5.0 testsºYES_50,BODY_8BITS,FROM_LOCAL_NOVOWEL,GARBLED_BODY,HTML_FONT_SIZE_LARGE,HTML_MESSAGE,KAM_SHORT,MISSING_MID,RCVD_IN_RP_RNBL,RCVD_IN_XBL,T_REMOTE_IMAGE autolearn=no version=3.3.1 spammy•, H*RU:SKY-20150219JSJ, 请ç, H*r:SKY-20150219JSJ?X-HELO: jescy.com
Received: from Unknown (HELO jescy.com) (36.27.30.81) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 09 Jul 2019 22:52:25 +0000
Received: from SKY-20150219JSJ ([127.0.0.1]) by localhost via TCP with ESMTPA; Wed, 10 Jul 2019 06:52:07 +0800
MIME-Version: 1.0
From: skfszxcy <skfszxcy@jescy.com>
To: gcc-bugs@gcc.gnu.org
Date: Tue, 09 Jul 2019 22:52:00 -0000
Subject: =?utf-8?B?Z2NjLWJ1Z3NAZ2NjLmdudS5vcmd1enF3?Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-SW-Source: 2019-07/txt/msg00688.txt.bz2
Content-length: 456
5o+Q5L6b5ZCE56eN5Y+R56Wo5bm1OjEgMyA2OzkyMiAyNzUgOTXlvKDjgJAg
5pyJIOOAkeKGk+OAkDMlLTEzJeOAkeOAkCDlopcg44CR5ZCE44CQIOWPkSDj
gJEg44CQIOeomSDjgJHnp43jgJAg56WoIOOAkeOAkCDnqI4g44CR55yf44CQ
IOW5tSDjgJEgDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KIA0K5aaC5p6c5L2g
5LiN5oOzIOWGjeaUtuWIsOivpeS6p+WTgeeahOaOqOiNkOmCruS7tiwg6K+3
54K55Ye76L+Z6YeM6YCA6K6iDQo>From gcc-bugs-return-648577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 23:31:14 2019
Return-Path: <gcc-bugs-return-648577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42091 invoked by alias); 9 Jul 2019 23:31: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 42053 invoked by uid 48); 9 Jul 2019 23:31:11 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90989] [9 Regression] incorrrect strlen result after second strcpy into the same destination
Date: Tue, 09 Jul 2019 23:31: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: patch, 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: P2
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc cf_known_to_fail
Message-ID: <bug-90989-4-4Xj33mmx4L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90989-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90989-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00689.txt.bz2
Content-length: 664
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90989
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[9/10 Regression] |[9 Regression] incorrrect
|incorrrect strlen result |strlen result after second
|after second strcpy into |strcpy into the same
|the same destination |destination
Known to fail|10.0 |
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Fixed for GCC 10 in r273317.
>From gcc-bugs-return-648578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 03:01:13 2019
Return-Path: <gcc-bugs-return-648578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130290 invoked by alias); 10 Jul 2019 03:01: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 130246 invoked by uid 48); 10 Jul 2019 03:01:08 -0000
From: "skunk at iskunk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/55930] [7/8/9/10 Regression] libatomic build failure if configured with --disable-dependency-tracking
Date: Wed, 10 Jul 2019 03:01: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: 4.8.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: minor
X-Bugzilla-Who: skunk at iskunk dot 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-55930-4-WdxTQG4UyW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55930-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55930-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00690.txt.bz2
Content-length: 1824
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55930
Daniel Richard G. <skunk at iskunk dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |skunk at iskunk dot org
--- Comment #10 from Daniel Richard G. <skunk at iskunk dot org> ---
Confirmed that this issue persists in 9.1.0:
libtool: compile: /tmp/gcc-9.1.0.build/./gcc/xgcc
-B/tmp/gcc-9.1.0.build/./gcc/ -B/opt/gnu/x86_64-pc-linux-gnu/bin/
-B/opt/gnu/x86_64-pc-linux-gnu/lib/ -isystem
/opt/gnu/x86_64-pc-linux-gnu/include -isystem
/opt/gnu/x86_64-pc-linux-gnu/sys-include -fchecking=1 -DHAVE_CONFIG_H
-I/home/src/gcc/gcc-9.1.0/libatomic/config/x86
-I/home/src/gcc/gcc-9.1.0/libatomic/config/posix
-I/home/src/gcc/gcc-9.1.0/libatomic -I. -Wall -Werror -pthread -g -O2 -MT
load_1_.lo -MD -MP -MF .deps/load_1_.lo.Ppo -DN=1 -c
/home/src/gcc/gcc-9.1.0/libatomic/load_n.c -fPIC -DPIC -o load_1_.o
/home/src/gcc/gcc-9.1.0/libatomic/load_n.c:115:1: fatal error: opening
dependency file .deps/load_1_.lo.Ppo: No such file or directory
115 | EXPORT_ALIAS (SIZE(load));
| ^~~~~~~~~~~~
compilation terminated.
gmake[4]: *** [load_1_.lo] Error 1
gmake[4]: Leaving directory
`/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libatomic'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory
`/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libatomic'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libatomic'
gmake[1]: *** [all-target-libatomic] Error 2
gmake[1]: Leaving directory `/tmp/gcc-9.1.0.build'
gmake: *** [bootstrap-lean] Error 2
I'd like to echo Mr. Purdie's "We pass this option in globally to anything
using automake" as the approach my site uses as well.
>From gcc-bugs-return-648579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 03:13:30 2019
Return-Path: <gcc-bugs-return-648579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18626 invoked by alias); 10 Jul 2019 03:13: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 18595 invoked by uid 48); 10 Jul 2019 03:13:21 -0000
From: "skunk at iskunk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/58638] libstdc++ builds as non-PIC when --with-pic is specified
Date: Wed, 10 Jul 2019 03:13: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: 4.8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: skunk at iskunk dot 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-58638-4-TrC0QGmy8j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58638-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58638-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00691.txt.bz2
Content-length: 2867
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58638
--- Comment #12 from Daniel Richard G. <skunk at iskunk dot org> ---
This issue appears to persist in 9.1.0, where it prevents bootstrap from
completing:
[...]
libtool: link: /tmp/gcc-9.1.0.build/./gcc/xg++ -B/tmp/gcc-9.1.0.build/./gcc/
-nostdinc++ -nostdinc++
-I/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu
-I/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/include
-I/home/src/gcc/gcc-9.1.0/libstdc++-v3/libsupc++
-I/home/src/gcc/gcc-9.1.0/libstdc++-v3/include/backward
-I/home/src/gcc/gcc-9.1.0/libstdc++-v3/testsuite/util
-L/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/src
-L/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-B/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/opt/gnu/x86_64-pc-linux-gnu/bin/ -B/opt/gnu/x86_64-pc-linux-gnu/lib/
-isystem /opt/gnu/x86_64-pc-linux-gnu/include -isystem
/opt/gnu/x86_64-pc-linux-gnu/sys-include -fchecking=1 -fPIC -DPIC -shared
-nostdlib /usr/lib/../lib64/crti.o /tmp/gcc-9.1.0.build/./gcc/crtbeginS.o
.libs/findcomp.o .libs/libcc1.o .libs/libcp1.o .libs/names.o .libs/callbacks.o
.libs/connection.o .libs/marshall.o
-L/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/src
-L/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-L/tmp/gcc-9.1.0.build/./gcc -L/lib/../lib64 -L/usr/lib/../lib64
/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a -lm
-lc -lgcc /tmp/gcc-9.1.0.build/./gcc/crtendS.o /usr/lib/../lib64/crtn.o
-static-libstdc++ -static-libgcc ../libiberty/pic/libiberty.a -Wl,-soname
-Wl,libcc1.so.0 -Wl,-retain-symbols-file
-Wl,/home/src/gcc/gcc-9.1.0/libcc1/libcc1.sym -o .libs/libcc1.so.0.0.0
/usr/bin/ld:
/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a(class_type_info.o):
relocation R_X86_64_32S against `_ZTVN10__cxxabiv117__class_type_infoE' can not
be used when making a shared object; recompile with -fPIC
/tmp/gcc-9.1.0.build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.a:
could not read symbols: Bad value
collect2: error: ld returned 1 exit status
gmake[3]: *** [libcc1.la] Error 1
gmake[3]: Leaving directory `/tmp/gcc-9.1.0.build/libcc1'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/tmp/gcc-9.1.0.build/libcc1'
gmake[1]: *** [all-libcc1] Error 2
gmake[1]: Leaving directory `/tmp/gcc-9.1.0.build'
gmake: *** [bootstrap-lean] Error 2
(This tree was configured with --disable-shared
--enable-version-specific-runtime-libs --with-pic)
I have confirmed that Alec's workaround (in comment #11) still does the trick.
>From gcc-bugs-return-648580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 04:11:25 2019
Return-Path: <gcc-bugs-return-648580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102724 invoked by alias); 10 Jul 2019 04: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 102678 invoked by uid 48); 10 Jul 2019 04:11:21 -0000
From: "frankhb1989 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91127] New: Incorrect checking of nonnull attribute with argument to a constructor of class with a virtual base
Date: Wed, 10 Jul 2019 04: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: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frankhb1989 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-91127-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00692.txt.bz2
Content-length: 1360
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91127
Bug ID: 91127
Summary: Incorrect checking of nonnull attribute with argument
to a constructor of class with a virtual base
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: frankhb1989 at gmail dot com
Target Milestone: ---
Case:
struct B
{};
struct C : virtual B
{
__attribute__((nonnull(2))) C(const char*);
};
a.cc:6:43: warning: 'nonnull' attribute argument value '2' refers to parameter
type 'int' [-Wattributes]
6 | __attribute__((nonnull(2))) C(const char*);
| ^
Removal of `virtual` makes it works. Use of `__attribute__((nonnull))` (with no
argument `2`) also works.
Clang++ 8 seems OK with or without `virtual`.
Note it is worse in old versions of the compiler, e.g. with G++ 7.1:
a.cc:6:43: error: nonnull argument references non-pointer operand (argument 1,
operand 2)
__attribute__((nonnull(2))) C(const char*);
^
The change in PR 87541 has made the diagnostics more explicit. Not sure whether
the change from error to warning is intended, though.
>From gcc-bugs-return-648581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 08:17:19 2019
Return-Path: <gcc-bugs-return-648581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114536 invoked by alias); 10 Jul 2019 08:17: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 114492 invoked by uid 48); 10 Jul 2019 08:17:15 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91127] Incorrect checking of nonnull attribute with argument to a constructor of class with a virtual base
Date: Wed, 10 Jul 2019 08: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: 9.1.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: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-91127-4-avawU3U7bJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91127-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91127-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00693.txt.bz2
Content-length: 1261
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91127
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-10
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I hate hate hate the fact that the nonnull attribute counts implicit arguments.
The 'this' pointer must always be nonnull, so there's no benefit to including
it, and other implicit arguments (like the int here for an in-charge
constructor?) just complicate things and require users to understand details of
a leaky abstraction.
This bug should just be fixed to ignore the int, but counting the 'this'
pointer can't be fixed without introducing a new attribute with sensible
behaviour for member functions and constructors.
</rant>
I'll let Martin comment on whether changing handle_nonnull_attribute from
giving an error to a warning was intended.
>From gcc-bugs-return-648582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 08:21:25 2019
Return-Path: <gcc-bugs-return-648582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124898 invoked by alias); 10 Jul 2019 08:21: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 124862 invoked by uid 48); 10 Jul 2019 08:21:21 -0000
From: "dragan.mladjenovic@rt-rk.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89245] [MIPS] v1 is assigned in jalr delay slot for later use at -Os
Date: Wed, 10 Jul 2019 08:21: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dragan.mladjenovic@rt-rk.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-89245-4-QcG5GSbSRJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89245-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89245-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00694.txt.bz2
Content-length: 246
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89245
--- Comment #2 from Dragan Mladjenovic <dragan.mladjenovic@rt-rk.com> ---
Fixed by r273314. Sorry for the inconvenience. I did not put a proper
back-reference to this issue in the change log.
>From gcc-bugs-return-648583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 08:44:18 2019
Return-Path: <gcc-bugs-return-648583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50545 invoked by alias); 10 Jul 2019 08:44: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 50490 invoked by uid 48); 10 Jul 2019 08:44:14 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/55930] [7/8/9/10 Regression] libatomic build failure if configured with --disable-dependency-tracking
Date: Wed, 10 Jul 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: other
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: minor
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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55930-4-98uHbaVrRF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55930-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55930-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00695.txt.bz2
Content-length: 297
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55930
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I still think the solution is "don't do that for gcc" but in any case, the
patch still hasn't been sent to the mailing list so isn't going to get reviewed
let alone applied.
>From gcc-bugs-return-648584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 09:05:37 2019
Return-Path: <gcc-bugs-return-648584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94900 invoked by alias); 10 Jul 2019 09:05: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 94046 invoked by uid 48); 10 Jul 2019 09:05:31 -0000
From: "featherrain26 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91128] New: Incomplete fix of heap overflow in cp-demangle.c
Date: Wed, 10 Jul 2019 09: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: 5.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: featherrain26 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-91128-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00696.txt.bz2
Content-length: 5103
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91128
Bug ID: 91128
Summary: Incomplete fix of heap overflow in cp-demangle.c
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: featherrain26 at gmail dot com
Target Milestone: ---
Created attachment 46582
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46582&action=edit
Poc input
Reference link:
https://sourceware.org/bugzilla/show_bug.cgi?id=24791
Hi, there.
There is a heap overflow caused by the incomplete fix of the cp-demangle.c
This is the newest patch I have tried:
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=270258
System information:
Description: Ubuntu 16.04.6 LTS
Release: 16.04
Codename: xenial
gcc version: 5.4
The Binutils version is release 2.32 or 2.33(HEAD)
To reproduce the issue, the compile flag is:
CFLAGS="-g -O0 -m32 -fsanitize=address,undefined" ./configure;make
then,
nm-new -C -a -l --synthetic input
Here are the details reported by ASAN:
==178966==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xf4e02883
at pc 0x085d6167 bp 0xffe086d8 sp 0xffe086c8
READ of size 1 at 0xf4e02883 thread T0
#0 0x85d6166 in d_expression_1 cp-demangle.c:3356
#1 0x85d4f12 in d_expression_1 cp-demangle.c:3449
#2 0x85d4f12 in d_expression_1 cp-demangle.c:3449
#3 0x85d4f12 in d_expression_1 cp-demangle.c:3449
#4 0x85d4f12 in d_expression_1 cp-demangle.c:3449
#5 0x85d4f12 in d_expression_1 cp-demangle.c:3449
#6 0x85d4f12 in d_expression_1 cp-demangle.c:3449
#7 0x85d4f12 in d_expression_1 cp-demangle.c:3449
#8 0x85d4f12 in d_expression_1 cp-demangle.c:3449
#9 0x85c8395 in d_expression cp-demangle.c:3531
#10 0x85c8395 in d_array_type cp-demangle.c:3011
#11 0x85c8395 in cplus_demangle_type cp-demangle.c:2463
#12 0x85ca143 in d_parmlist cp-demangle.c:2908
#13 0x85d907c in d_bare_function_type cp-demangle.c:2962
#14 0x85d907c in d_encoding cp-demangle.c:1343
#15 0x85dc451 in cplus_demangle_mangled_name cp-demangle.c:1234
#16 0x85e29ed in d_demangle_callback cp-demangle.c:6292
#17 0x85e29ed in d_demangle cp-demangle.c:6343
#18 0x85e29ed in cplus_demangle_v3 cp-demangle.c:6500
#19 0x858e46c in cplus_demangle cplus-dem.c:165
#20 0x808ea57 in bfd_demangle
/mnt/data/playground/binutils-2.32-a/bfd/bfd.c:2254
#21 0x805f51f in print_symname
/mnt/data/playground/binutils-2.32-a/binutils/nm.c:423
#22 0x805f51f in print_symbol_info_bsd
/mnt/data/playground/binutils-2.32-a/binutils/nm.c:1565
#23 0x8053fcf in print_symbol
/mnt/data/playground/binutils-2.32-a/binutils/nm.c:903
#24 0x80571b5 in print_symbols
/mnt/data/playground/binutils-2.32-a/binutils/nm.c:1102
#25 0x80571b5 in display_rel_file
/mnt/data/playground/binutils-2.32-a/binutils/nm.c:1215
#26 0x805adb1 in display_file
/mnt/data/playground/binutils-2.32-a/binutils/nm.c:1335
#27 0x804f98a in main
/mnt/data/playground/binutils-2.32-a/binutils/nm.c:1816
#28 0xf7000636 in __libc_start_main (/lib/i386-linux-gnu/libc.so.6+0x18636)
#29 0x805154b
(/mnt/data/playground/binutils-2.32-a/binutils/nm-new+0x805154b)
0xf4e02883 is located 0 bytes to the right of 99-byte region
[0xf4e02820,0xf4e02883)
allocated by thread T0 here:
#0 0xf7239dee in malloc (/usr/lib32/libasan.so.2+0x96dee)
#1 0x80abadd in bfd_malloc
/mnt/data/playground/binutils-2.32-a/bfd/libbfd.c:275
SUMMARY: AddressSanitizer: heap-buffer-overflow cp-demangle.c:3356
d_expression_1
Shadow bytes around the buggy address:
0x3e9c04c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3e9c04d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3e9c04e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3e9c04f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3e9c0500: fa fa fa fa 00 00 00 00 00 00 00 00 00 00 00 00
=>0x3e9c0510:[03]fa fa fa fa fa fa fa fa fa 00 00 00 00 00 00
0x3e9c0520: 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa fa
0x3e9c0530: 00 00 00 00 00 00 00 00 00 00 00 00 00 fa fa fa
0x3e9c0540: fa fa fa fa fa fa 00 00 00 00 00 00 00 00 00 00
0x3e9c0550: 00 00 00 fa fa fa fa fa fa fa fa fa 00 00 00 00
0x3e9c0560: 00 00 00 00 00 00 00 00 04 fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Heap right redzone: fb
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack partial redzone: f4
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
==178966==ABORTING
The attachment is the POC input.
>From gcc-bugs-return-648585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 09:13:26 2019
Return-Path: <gcc-bugs-return-648585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52580 invoked by alias); 10 Jul 2019 09:13: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 52509 invoked by uid 48); 10 Jul 2019 09:13:23 -0000
From: "richard.purdie at linuxfoundation dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/55930] [7/8/9/10 Regression] libatomic build failure if configured with --disable-dependency-tracking
Date: Wed, 10 Jul 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: other
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: minor
X-Bugzilla-Who: richard.purdie at linuxfoundation dot 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55930-4-HnN0j6GY8j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55930-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55930-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00697.txt.bz2
Content-length: 324
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55930
--- Comment #12 from Richard Purdie <richard.purdie at linuxfoundation dot org> ---
I started to look at sorting out Yocto Project/Openembedded's gcc patches in
general and ran into a contribution agreement legal quagmire. I still haven't
been able to resolve that.
>From gcc-bugs-return-648586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 09:19:22 2019
Return-Path: <gcc-bugs-return-648586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68691 invoked by alias); 10 Jul 2019 09:19: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 68658 invoked by uid 48); 10 Jul 2019 09:19:18 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/81806] Split in pbds works in O(n) instead of O(log n)
Date: Wed, 10 Jul 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: libstdc++
X-Bugzilla-Version: 6.4.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-81806-4-LFX9NlcBpD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81806-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81806-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00698.txt.bz2
Content-length: 192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81806
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Feedback was provided: https://gcc.gnu.org/ml/gcc/2019-07/msg00082.html
>From gcc-bugs-return-648587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 09:22:49 2019
Return-Path: <gcc-bugs-return-648587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71457 invoked by alias); 10 Jul 2019 09:22: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 71404 invoked by uid 48); 10 Jul 2019 09:22:45 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/55930] [7/8/9/10 Regression] libatomic build failure if configured with --disable-dependency-tracking
Date: Wed, 10 Jul 2019 09:22: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: 4.8.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: minor
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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55930-4-GwFUJDdm79@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55930-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55930-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00699.txt.bz2
Content-length: 229
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55930
--- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> ---
OK thanks for the update. I think your patch for this bug is trivial enough to
not require any paperwork.
>From gcc-bugs-return-648588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 10:21:51 2019
Return-Path: <gcc-bugs-return-648588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33900 invoked by alias); 10 Jul 2019 10:21: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 33860 invoked by uid 48); 10 Jul 2019 10:21:48 -0000
From: "Peter.Georg at physik dot uni-regensburg.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88907] Variadic template function deduction failure.
Date: Wed, 10 Jul 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: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Peter.Georg at physik dot uni-regensburg.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: version
Message-ID: <bug-88907-4-T7dMcv2lEf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88907-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88907-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00700.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88907
Peter Georg <Peter.Georg at physik dot uni-regensburg.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|8.2.1 |10.0
--- Comment #1 from Peter Georg <Peter.Georg at physik dot uni-regensburg.de> ---
All versions tested (6-9, and trunk) are affected.
>From gcc-bugs-return-648589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 10:36:17 2019
Return-Path: <gcc-bugs-return-648589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51267 invoked by alias); 10 Jul 2019 10:36: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 51200 invoked by uid 48); 10 Jul 2019 10:36:13 -0000
From: "Peter.Georg at physik dot uni-regensburg.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91129] New: Implicit casts fail for modulo operator
Date: Wed, 10 Jul 2019 10:36: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: Peter.Georg at physik dot uni-regensburg.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-91129-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00701.txt.bz2
Content-length: 1384
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91129
Bug ID: 91129
Summary: Implicit casts fail for modulo operator
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: Peter.Georg at physik dot uni-regensburg.de
Target Milestone: ---
Created attachment 46583
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46583&action=edit
Code to reproduce bug
GCC fails to compile the following code due to being unable to implicitely cast
Constant<int, 1> to int, despite the conversion operator being defined.
```
class Constant
{
public:
constexpr operator T() const { return v; }
constexpr auto operator()() const {return v;}
};
template<class T, int N>
class Array
{
};
class Test
{
public:
template<int C>
using Cores = Array<int, C % Constant<int, 6>{}>;
};
int main()
{
}
```
The code is also attacged or see: https://godbolt.org/z/UJHdqb
Array and Constant can be replaced by std::array and std::integral_constant,
the error is the same.
It only fails when using the modulo operator, any other tested binary
arithmetic operator works. When adding an explicit cast, the code compiles
without any errors as well.
First version affected: GCC 9
>From gcc-bugs-return-648590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 10:58:17 2019
Return-Path: <gcc-bugs-return-648590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98888 invoked by alias); 10 Jul 2019 10: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 98834 invoked by uid 48); 10 Jul 2019 10:58:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91126] [10 regression] Incorrect constant propagation of BIT_FIELD_REF
Date: Wed, 10 Jul 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: 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: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91126-4-ETGIb8mOk4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00702.txt.bz2
Content-length: 588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91126
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Testcase that fails for a longer time already:
struct S
{
int a : 24;
int b : 8;
} s;
int
main()
{
s.a = 0xfefefe;
s.b = 0xfe;
unsigned char c;
c = ((unsigned char *)&s)[0];
if (c != 0xfe)
__builtin_abort ();
c = ((unsigned char *)&s)[1];
if (c != 0xfe)
__builtin_abort ();
c = ((unsigned char *)&s)[2];
if (c != 0xfe)
__builtin_abort ();
c = ((unsigned char *)&s)[3];
if (c != 0xfe)
__builtin_abort ();
return 0;
}
>From gcc-bugs-return-648591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 11:00:39 2019
Return-Path: <gcc-bugs-return-648591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101148 invoked by alias); 10 Jul 2019 11:00: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 101044 invoked by uid 48); 10 Jul 2019 11:00:35 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91124] [10 regression] gcc.target/i386/avx512vl-vpshldvd-2.c etc. FAIL
Date: Wed, 10 Jul 2019 11:00: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: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cc assigned_to
Message-ID: <bug-91124-4-fZbcAkdkJp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00703.txt.bz2
Content-length: 586
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91124
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
Status|NEW |ASSIGNED
CC| |jakub at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'll have a look.
>From gcc-bugs-return-648592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 11:04:11 2019
Return-Path: <gcc-bugs-return-648592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118330 invoked by alias); 10 Jul 2019 11: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 118285 invoked by uid 48); 10 Jul 2019 11:04:08 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91126] [7/8/9/10 regression] Incorrect constant propagation of BIT_FIELD_REF
Date: Wed, 10 Jul 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: 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: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cf_known_to_work target_milestone short_desc cf_known_to_fail
Message-ID: <bug-91126-4-cesK1Stwy4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00704.txt.bz2
Content-length: 837
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91126
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Known to work| |4.6.3
Target Milestone|10.0 |7.5
Summary|[10 regression] Incorrect |[7/8/9/10 regression]
|constant propagation of |Incorrect constant
|BIT_FIELD_REF |propagation of
| |BIT_FIELD_REF
Known to fail| |4.7.4
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the new testcase should fail since GCC 4.7.
>From gcc-bugs-return-648593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 11:23:04 2019
Return-Path: <gcc-bugs-return-648593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12944 invoked by alias); 10 Jul 2019 11:23: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 12857 invoked by uid 48); 10 Jul 2019 11:22:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91124] [10 regression] gcc.target/i386/avx512vl-vpshldvd-2.c etc. FAIL
Date: Wed, 10 Jul 2019 11: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: rejects-valid
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: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91124-4-PkNAGOfctC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00705.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91124
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Somehow the backend doesn't like to expand
__builtin_ia32_vpshldv_v4si_mask (_36, { 2, 3, 4, 5 }, { 1, 4, 7, 10 }, 185)
while it happily expands
__builtin_ia32_vpshldv_v4si_maskz (_24, _15, _14, 185);
and the error message is of course misleading (it complains about the
second vector constant).
leaving it to Jakub.
>From gcc-bugs-return-648594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 11:27:52 2019
Return-Path: <gcc-bugs-return-648594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40327 invoked by alias); 10 Jul 2019 11: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 40253 invoked by uid 48); 10 Jul 2019 11:27:48 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91124] [10 regression] gcc.target/i386/avx512vl-vpshldvd-2.c etc. FAIL
Date: Wed, 10 Jul 2019 11:27: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: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91124-4-JwArbcn3lT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00706.txt.bz2
Content-length: 224
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91124
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yeah, but that is just one thing, the other is execution failure, but most
likely bad expansion as well.
>From gcc-bugs-return-648595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 11:38:12 2019
Return-Path: <gcc-bugs-return-648595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60452 invoked by alias); 10 Jul 2019 11:38: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 60393 invoked by uid 48); 10 Jul 2019 11:38:09 -0000
From: "steve at sk2 dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/55930] [7/8/9/10 Regression] libatomic build failure if configured with --disable-dependency-tracking
Date: Wed, 10 Jul 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: other
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: minor
X-Bugzilla-Who: steve at sk2 dot 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55930-4-hjWtteI18q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55930-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55930-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00707.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55930
--- Comment #14 from Stephen Kitt <steve at sk2 dot org> ---
(In reply to Andrew Pinski from comment #5)
> But the bigger question is why are you passing --disable-dependency-tracking
> ?
I ran into this issue because Debian's debhelper's dh_auto_configure passes
--disable-dependency-tracking automatically. ("Know your build tools" is the
lesson here, I guess.)
>From gcc-bugs-return-648596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 11:42:54 2019
Return-Path: <gcc-bugs-return-648596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64966 invoked by alias); 10 Jul 2019 11: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 64945 invoked by uid 48); 10 Jul 2019 11:42:51 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91130] New: [9/10 Regression] -MF clashes with -flto on aarch64
Date: Wed, 10 Jul 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: 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: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-91130-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00708.txt.bz2
Content-length: 1063
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91130
Bug ID: 91130
Summary: [9/10 Regression] -MF clashes with -flto on aarch64
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
Starting from GCC 9.1.0 I see following problem:
$ gcc --version
gcc (SUSE Linux) 9.1.1 20190611 [gcc-9-branch revision 272147]
$ echo "int main() {}" > main.c && gcc -c -flto main.c && gcc -o a.out main.o
-flto -MMD -MF deps/a.d -MP
gcc: error: deps/a.d: No such file or directory
lto-wrapper: fatal error: gcc returned 1 exit status
compilation terminated.
/usr/lib64/gcc/aarch64-suse-linux/9/../../../../aarch64-suse-linux/bin/ld:
error: lto-wrapper failed
collect2: error: ld returned 1 exit status
$ echo "int main() {}" > main.c && gcc-8 -c -flto main.c && gcc-8 -o a.out
main.o -flto -MMD -MF deps/a.d -MP && echo OK
OK
>From gcc-bugs-return-648597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 11:43:23 2019
Return-Path: <gcc-bugs-return-648597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65735 invoked by alias); 10 Jul 2019 11:43: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 65711 invoked by uid 48); 10 Jul 2019 11:43:20 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91130] [9/10 Regression] -MF clashes with -flto on aarch64
Date: Wed, 10 Jul 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: target
X-Bugzilla-Version: 9.1.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: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget cf_reconfirmed_on cc cf_gcchost version target_milestone cf_gccbuild
Message-ID: <bug-91130-4-SRb66xppqx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91130-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91130-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00709.txt.bz2
Content-length: 687
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91130
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |aarch64-linux-gnu
Last reconfirmed| |2019-7-10
CC| |ktkachov at gcc dot gnu.org
Host| |aarch64-linux-gnu
Version|10.0 |9.1.0
Target Milestone|--- |9.2
Build| |aarch64-linux-gnu
>From gcc-bugs-return-648598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 11:48:48 2019
Return-Path: <gcc-bugs-return-648598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70446 invoked by alias); 10 Jul 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 70414 invoked by uid 48); 10 Jul 2019 11:48:45 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91130] [9/10 Regression] -MF clashes with -flto on aarch64
Date: Wed, 10 Jul 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: target
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: 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: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_known_to_work everconfirmed cf_known_to_fail
Message-ID: <bug-91130-4-vLrMlxoloN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91130-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91130-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00710.txt.bz2
Content-length: 521
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91130
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-bisection
Status|UNCONFIRMED |NEW
Known to work| |8.3.0
Ever confirmed|0 |1
Known to fail| |9.1.0
>From gcc-bugs-return-648599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 12:16:44 2019
Return-Path: <gcc-bugs-return-648599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23932 invoked by alias); 10 Jul 2019 12:16: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 23896 invoked by uid 48); 10 Jul 2019 12:16:40 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/89330] IPA inliner touches released cgraph_edges
Date: Wed, 10 Jul 2019 12:16: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: 9.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: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-89330-4-1gklJXMcNp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00711.txt.bz2
Content-length: 1520
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89330
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #45730|0 |1
is obsolete| |
Attachment #46544|0 |1
is obsolete| |
--- Comment #12 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Created attachment 46584
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46584&action=edit
Another WIP patch
Thanks for tracking that down, indeed we found that the speculation
was undoing inlining decisions which is something that is generally
unsupported by the inliner.
This patch fixes that and it indeed survives LTO bootstrap of all
languages (profiled LTO bootstrap is underway). Unfortunately, it
causes the following tests to fail:
FAIL: g++.dg/tree-prof/devirt.C scan-tree-dump-times tracer "folding virtual
function call to virtual unsigned int mozPersonalDictionary::_ZThn16" 1
FAIL: g++.dg/tree-prof/devirt.C scan-tree-dump-times tracer "folding virtual
function call to virtual unsigned int mozPersonalDictionary::AddRef" 1
So far all my attempts to quickly fix this without actually having to
understand what is going on in the testcase have failed. I'm afraid
I'll have to look deeper into it which will take time, so far I did
not even manage to reproduce the problem manually.
>From gcc-bugs-return-648600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 12:32:38 2019
Return-Path: <gcc-bugs-return-648600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71994 invoked by alias); 10 Jul 2019 12:32: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 71936 invoked by uid 48); 10 Jul 2019 12:32:34 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91115] stack-buffer-overflow on memset local variable when creating thread on ARM Linux
Date: Wed, 10 Jul 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: sanitizer
X-Bugzilla-Version: 8.3.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:
Message-ID: <bug-91115-4-Y47UYSD2Jd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91115-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91115-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00712.txt.bz2
Content-length: 754
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91115
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Fred Hsueh from comment #3)
> The actual SP and shadow byte location varies a bit between each run. Other
> than that, the signature looks very similar. Another thing to note is that
> the program has a high thread count, perhaps ~140.
That makes it very difficult to reproduce. Do you have any 2 runs that have the
'[f2]' shadow memory at the same location.
>
> Any tips, preferences, or good starting points to look at for creating the
> testcase? I can't find any in ASAN or ARM related pre-existing cases.
>
> thanks!
Is the reproducer an open-source software? I would somehow reduce # of threads.
>From gcc-bugs-return-648601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 13:10:20 2019
Return-Path: <gcc-bugs-return-648601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82545 invoked by alias); 10 Jul 2019 13:10: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 82518 invoked by uid 48); 10 Jul 2019 13:10:15 -0000
From: "pdj at knaldgas dot dk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91131] New: Bad bitfield coalescing
Date: Wed, 10 Jul 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: middle-end
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pdj at knaldgas dot dk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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
Message-ID: <bug-91131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00713.txt.bz2
Content-length: 2371
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91131
Bug ID: 91131
Summary: Bad bitfield coalescing
Product: gcc
Version: 8.3.0
URL: http://knaldgas.dk/~pdj/bitfields/
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: pdj at knaldgas dot dk
Target Milestone: ---
In both C and Ada, bitfield coalescing does not work right, or at least not
optimal. Since the issue manifests itself in the same way in both C and Ada
front-ends, and on ARM, AVR and X86_64 back-ends, I presume that that the issue
must lie somewhere in between. Please see past that C bitfields are defective
by definition; Ada's definition is pretty well-defined.
Seen on GCC version 4.9.3, 8.3.0 and reportedly also on 9.1.
The key point below is that all assignments have a data-width of less or equal
the machines data-width, and can be fully evaluated at compile time.
Pseudo-code:
type Rec_Type record
A: 3 bits
B: 1 bit
C: 4 bits
end (packed, 8-bit wide)
volatile Rec_A : Rec_Type
volatile Rec_B : Rec_Type
volatile Rec_C : Rec_Type
Rec_A := (A => 0, B => 1, C => 0)
results in one pre-calculated constant byte being assigned directly. This is
the way all such assignments should be.
Rec_B := (A => 1, B => 1, C => 1)
results in one pre-calculated value being stored in a memory location, which is
then ĺoaded and assigned to Rec_B. Unnecessary memory consumption.
Rec_C := (A => 0, B => 0, C => 0)
results in Read, Modify, Write for each field (3 times). Horrible, and may
cause defective execution if Reg_C is a peripheral register! Reading a register
does not always give the last value written to it. Also Writing bits in
"random" order may cause malfunction of the device.
In Ada the Reg_C problem can be mitigated by using pragma Atomic instead, this
still causes a memory location to be used for the evaluated constant that could
just as well be loaded as an immediate.
I've uploaded sources, preprocessed file and Makefile/GPR to this location:
http://knaldgas.dk/~pdj/bitfields/ - The c-file is just compiled with gcc
-O<whatever> -c main.c
Pretty odd that three similar assignments can give three different kinds of
code generation...
>From gcc-bugs-return-648602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 13:20:33 2019
Return-Path: <gcc-bugs-return-648602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83482 invoked by alias); 10 Jul 2019 13: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 83463 invoked by uid 48); 10 Jul 2019 13:20:29 -0000
From: "pdj at knaldgas dot dk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91131] Bad bitfield coalescing
Date: Wed, 10 Jul 2019 13:20: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: missed-optimization, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pdj at knaldgas dot dk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-91131-4-2uplcD3cIZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00714.txt.bz2
Content-length: 248
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91131
--- Comment #1 from Per Dalgas Jakobsen <pdj at knaldgas dot dk> ---
Created attachment 46585
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46585&action=edit
MWE: Preprocessed C-file
>From gcc-bugs-return-648603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 13:33:54 2019
Return-Path: <gcc-bugs-return-648603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130679 invoked by alias); 10 Jul 2019 13:33: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 130632 invoked by uid 48); 10 Jul 2019 13:33:50 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91125] -frepo can't build tramp3d
Date: Wed, 10 Jul 2019 13: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: 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 assigned_to everconfirmed
Message-ID: <bug-91125-4-rnR5BAR6fK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91125-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91125-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00715.txt.bz2
Content-length: 581
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91125
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|2019-07-09 00:00:00 |2019-07-10
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> ---
Lemme take it.
>From gcc-bugs-return-648604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 13:36:36 2019
Return-Path: <gcc-bugs-return-648604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2830 invoked by alias); 10 Jul 2019 13:36: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 2763 invoked by uid 48); 10 Jul 2019 13:36:32 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91132] New: New test gcc.dg/strlenopt-67.c in r273317 fails
Date: Wed, 10 Jul 2019 13:36: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-91132-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00716.txt.bz2
Content-length: 2722
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91132
Bug ID: 91132
Summary: New test gcc.dg/strlenopt-67.c in r273317 fails
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: ---
spawn -ignore SIGHUP /home/seurer/gcc/build/gcc-test2/gcc/xgcc
-B/home/seurer/gcc/build/gcc-test2/gcc/
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/strlenopt-67.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -O2 -Wall -fdump-tree-optimized -S -o strlenopt-67.s
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/strlenopt-67.c:62:5: error:
redefinition of 'f4'
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/strlenopt-67.c:10:5: note:
previous definition of 'f4' was here
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/strlenopt-67.c:76:5: error:
redefinition of 'f6'
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/strlenopt-67.c:24:5: note:
previous definition of 'f6' was here
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/strlenopt-67.c:90:5: error:
redefinition of 'f8'
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/strlenopt-67.c:38:5: note:
previous definition of 'f8' was here
compiler exited with status 1
FAIL: gcc.dg/strlenopt-67.c (test for excess errors)
Excess errors:
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/strlenopt-67.c:62:5: error:
redefinition of 'f4'
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/strlenopt-67.c:76:5: error:
redefinition of 'f6'
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/strlenopt-67.c:90:5: error:
redefinition of 'f8'
gcc.dg/strlenopt-67.c: dump file does not exist
UNRESOLVED: gcc.dg/strlenopt-67.c scan-tree-dump-times optimized "abort|strlen"
0
gcc.dg/strlenopt-67.c: dump file does not exist
UNRESOLVED: gcc.dg/strlenopt-67.c scan-tree-dump-times optimized "abort|strlen"
0
testcase /home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/dg.exp completed in 1
seconds
=== gcc Summary ===
# of unexpected failures 1
# of unresolved testcases 2
------------------------------------------------------------------------
r273317 | msebor | 2019-07-09 18:29:33 -0500 (Tue, 09 Jul 2019) | 14 lines
gcc/ChangeLog:
PR tree-optimization
* tree-ssa-strlen.c (handle_char_store): Constrain a single character
optimization to just single character stores.
gcc/testsuite/ChangeLog:
PR tree-optimization
* gcc.dg/strlenopt-26.c: Exit with test result status.
* gcc.dg/strlenopt-67.c: New test.
>From gcc-bugs-return-648605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 13:40:29 2019
Return-Path: <gcc-bugs-return-648605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6427 invoked by alias); 10 Jul 2019 13:40: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 6387 invoked by uid 48); 10 Jul 2019 13:40:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91126] [7/8/9 regression] Incorrect constant propagation of BIT_FIELD_REF
Date: Wed, 10 Jul 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: 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: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work short_desc
Message-ID: <bug-91126-4-uacz0zBqQp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00717.txt.bz2
Content-length: 648
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91126
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |10.0
Summary|[7/8/9/10 regression] |[7/8/9 regression]
|Incorrect constant |Incorrect constant
|propagation of |propagation of
|BIT_FIELD_REF |BIT_FIELD_REF
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk sofar.
>From gcc-bugs-return-648606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 13:40:47 2019
Return-Path: <gcc-bugs-return-648606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7268 invoked by alias); 10 Jul 2019 13:40: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 7211 invoked by uid 55); 10 Jul 2019 13:40:43 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91126] [7/8/9 regression] Incorrect constant propagation of BIT_FIELD_REF
Date: Wed, 10 Jul 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: 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: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91126-4-iQjtIqeV9r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91126-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00718.txt.bz2
Content-length: 721
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91126
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Wed Jul 10 13:40:12 2019
New Revision: 273355
URL: https://gcc.gnu.org/viewcvs?rev=273355&root=gcc&view=rev
Log:
2019-07-10 Richard Biener <rguenther@suse.de>
PR tree-optimization/91126
* tree-ssa-sccvn.c (n_walk_cb_data::push_partial_def): Adjust
native encoding offset for BYTES_BIG_ENDIAN.
(vn_reference_lookup_3): Likewise.
* gcc.dg/torture/pr91126.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/torture/pr91126.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-sccvn.c
>From gcc-bugs-return-648607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 13:45:53 2019
Return-Path: <gcc-bugs-return-648607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12982 invoked by alias); 10 Jul 2019 13:45: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 12940 invoked by uid 48); 10 Jul 2019 13:45:49 -0000
From: "castro8583bennett at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/90231] ivopts causes <optimized away> iterator in the loop
Date: Wed, 10 Jul 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: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: castro8583bennett at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amker at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-90231-4-MZGlOjVQaR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90231-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90231-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00719.txt.bz2
Content-length: 568
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90231
Carlo B. <castro8583bennett at gmx dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |castro8583bennett at gmx dot com
--- Comment #6 from Carlo B. <castro8583bennett at gmx dot com> ---
(In reply to Jakub Jelinek from comment #4)
> The point is that ivopts knows better
Hi Jakub so what do you suggest we should do about this?
Castro B,
https://voucher.co.id
>From gcc-bugs-return-648608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 13:51:00 2019
Return-Path: <gcc-bugs-return-648608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59074 invoked by alias); 10 Jul 2019 13:50: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 58446 invoked by uid 48); 10 Jul 2019 13:50:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91131] Bad bitfield coalescing
Date: Wed, 10 Jul 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: middle-end
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: missed-optimization, 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed cf_known_to_fail
Message-ID: <bug-91131-4-s40LG3LawL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00720.txt.bz2
Content-length: 1236
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91131
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-10
Ever confirmed|0 |1
Known to fail| |10.0, 8.3.0
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
So your complaint is that
struct Reg_T {
unsigned int a : 3;
unsigned int b : 1;
unsigned int c : 4;
} __attribute__((packed));
volatile struct Reg_T Reg_A;
...
Reg_A = (struct Reg_T){ .a = 0, .b = 0, .c = 0 };
does not yield a single store, correct?
The reason is how we gimplify this:
{
Reg_A.a = 0;
Reg_A.b = 0;
Reg_A.c = 0;
D.2005.a = 0;
D.2005.b = 1;
D.2005.c = 0;
Reg_B = D.2005;
D.2006.a = 7;
D.2006.b = 1;
D.2006.c = 15;
Reg_C = D.2006;
Reg_D = 0;
Reg_E = 255;
D.2007 = 0;
return D.2007;
}
see how for the zero-initializer we emit three volatile accesses.
>From gcc-bugs-return-648610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 13:56:51 2019
Return-Path: <gcc-bugs-return-648610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65515 invoked by alias); 10 Jul 2019 13:56: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 65491 invoked by uid 48); 10 Jul 2019 13:56:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91131] Bad bitfield coalescing
Date: Wed, 10 Jul 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: middle-end
X-Bugzilla-Version: 8.3.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: bug_status assigned_to
Message-ID: <bug-91131-4-WhuykGjipv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00722.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91131
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 #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-648609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 13:56:43 2019
Return-Path: <gcc-bugs-return-648609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64867 invoked by alias); 10 Jul 2019 13:56: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 64841 invoked by uid 48); 10 Jul 2019 13:56:38 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91131] Bad bitfield coalescing
Date: Wed, 10 Jul 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: middle-end
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: missed-optimization, 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91131-4-JMqAB0qVHH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00721.txt.bz2
Content-length: 964
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91131
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Index: gcc/gimplify.c
===================================================================
--- gcc/gimplify.c (revision 273355)
+++ gcc/gimplify.c (working copy)
@@ -5005,7 +5004,7 @@ gimplify_init_constructor (tree *expr_p,
one field to assign, initialize the target from a temporary. */
if (TREE_THIS_VOLATILE (object)
&& !TREE_ADDRESSABLE (type)
- && num_nonzero_elements > 0
+ && (num_nonzero_elements > 0 || !cleared)
&& vec_safe_length (elts) > 1)
{
tree temp = create_tmp_var (TYPE_MAIN_VARIANT (type));
note your use of packed might end up doing more than one store depending
on the architecture.
>From gcc-bugs-return-648611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 14:03:27 2019
Return-Path: <gcc-bugs-return-648611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79504 invoked by alias); 10 Jul 2019 14: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 79447 invoked by uid 48); 10 Jul 2019 14:03:15 -0000
From: "WisdomOfDarkness at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91133] New: Wrong "partial specialization is not more specialized than" error
Date: Wed, 10 Jul 2019 14: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: WisdomOfDarkness 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-91133-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00723.txt.bz2
Content-length: 1051
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91133
Bug ID: 91133
Summary: Wrong "partial specialization is not more specialized
than" error
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: WisdomOfDarkness at gmail dot com
Target Milestone: ---
The code under fails to compile with GCC 7, 8 and 9, and produces the following
error:
partial specialization 'struct A<T, int, X>' is not more specialized than
[-fpermissive] ...
template<typename T> struct Id
{
using type = T;
};
template<typename T, typename U, U X>
struct A
{
};
//template<int X>
template<typename T, typename Id<T>::type X>
struct A<T, int, X>
{
};
This is clearly wrong because the specialization is clearly specialized in its
second parameter.
godbolt: https://godbolt.org/z/wDp3B7
Works in GCC 6 and under. Also works in clang and MSVC.
>From gcc-bugs-return-648612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 14:24:03 2019
Return-Path: <gcc-bugs-return-648612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107256 invoked by alias); 10 Jul 2019 14:24: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 107183 invoked by uid 48); 10 Jul 2019 14:23:59 -0000
From: "pdj at knaldgas dot dk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91131] Bad bitfield coalescing
Date: Wed, 10 Jul 2019 14:24: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: missed-optimization, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pdj at knaldgas dot dk
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-91131-4-4DIg1l0ohu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00724.txt.bz2
Content-length: 692
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91131
--- Comment #5 from Per Dalgas Jakobsen <pdj at knaldgas dot dk> ---
(In reply to Richard Biener from comment #2)
> So your complaint is that
>
> struct Reg_T {
> unsigned int a : 3;
> unsigned int b : 1;
> unsigned int c : 4;
> } __attribute__((packed));
>
> volatile struct Reg_T Reg_A;
> ...
> Reg_A = (struct Reg_T){ .a = 0, .b = 0, .c = 0 };
>
> does not yield a single store, correct?
Primary complaint, Yes.
Secondary complaint is the use of RAM-memory locations for constants, where an
immediate would be more efficient. Especially on a microcontroller with 32
bytes of RAM...
>From gcc-bugs-return-648613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 14:37:02 2019
Return-Path: <gcc-bugs-return-648613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74442 invoked by alias); 10 Jul 2019 14:37: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 72115 invoked by uid 48); 10 Jul 2019 14:36:58 -0000
From: "frantisek at sumsal dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/91101] Possible performance regression in libasan with detect_stack_use_after_return=1
Date: Wed, 10 Jul 2019 14:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frantisek at sumsal dot cz
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
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-91101-4-Hbxnrurzmv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00725.txt.bz2
Content-length: 339
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91101
--- Comment #17 from Frantisek Sumsal <frantisek at sumsal dot cz> ---
Thanks a lot for the thorough debugging and explanation. I raised an issue on
the systemd bug tracker[0] so it can be properly discussed and resolved there.
[0] https://github.com/systemd/systemd/issues/12997
>From gcc-bugs-return-648614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 14:44:27 2019
Return-Path: <gcc-bugs-return-648614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128887 invoked by alias); 10 Jul 2019 14:44: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 128835 invoked by uid 48); 10 Jul 2019 14:44:23 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91124] [10 regression] gcc.target/i386/avx512vl-vpshldvd-2.c etc. FAIL
Date: Wed, 10 Jul 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: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-91124-4-HMs28KZ3G1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91124-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00726.txt.bz2
Content-length: 375
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91124
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 46586
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46586&action=edit
gcc10-pr91124.patch
Untested patch for the VBMI2/VNNI error: the last argument must be an 8-bit
immediate etc. issues, but not for the execution failures.
>From gcc-bugs-return-648615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 15:22:07 2019
Return-Path: <gcc-bugs-return-648615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66572 invoked by alias); 10 Jul 2019 15:22: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 66555 invoked by uid 48); 10 Jul 2019 15:22:02 -0000
From: "emil.fihlman at aalto dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjLzkxMTM0XSBOZXc6IENvbmZ1c2luZyBlcnJvciBtZXNzYWdlOiBl?= =?UTF-8?B?cnJvcjog4oCYKnNlcnZlcuKAmSBpcyBhIHBvaW50ZXI7IGRpZCB5b3UgbWVh?= =?UTF-8?B?biB0byB1c2Ug4oCYLT7igJk/IHdoZW4gLT4gaXMgdXNlZA==?Date: Wed, 10 Jul 2019 15:22: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: 6.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emil.fihlman at aalto 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-91134-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00727.txt.bz2
Content-length: 2996
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91134
Bug ID: 91134
Summary: Confusing error message: error: ‘*server’ is a
pointer; did you mean to use ‘->’? when -> is used
Product: gcc
Version: 6.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: emil.fihlman at aalto dot fi
Target Milestone: ---
gcc -Wall -Werror -Wextra -O3 -flto -o program program.c -lm
program.c: In function ‘setupFunction’:
program.c:Y:X: error: ‘*server’ is a pointer; did you mean to use ‘->’?
if(setupThing(&(*server->thing), MAX_THINGY)==~0UL)
^~
server is of type struct Server ** in this context
The error message should probably change in this context to suggesting
parentheses.
fiesh on #gcc@Freenode gave these ideas regarding this:
2019-07-10 18:11:03 +0300 < fiesh> I think that `server->thing` is probably
replaced by `(*server.thing)` since they are semantically equivalent at some
stage before the error is produced
2019-07-10 18:11:45 +0300 < fiesh> then the parser sees that *server is a
pointer type and you're trying to access its contents with ., so it tells you
that doesn't work
2019-07-10 18:12:52 +0300 < fiesh> by ((*server).thing)
Emil
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-18+deb9u1'
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --with-tune=generic --enable-checking=release
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)
>From gcc-bugs-return-648616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 15:29:46 2019
Return-Path: <gcc-bugs-return-648616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106510 invoked by alias); 10 Jul 2019 15:29: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 105193 invoked by uid 48); 10 Jul 2019 15:29:42 -0000
From: "emil.fihlman at aalto dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjLzkxMTM0XSBDb25mdXNpbmcgZXJyb3IgbWVzc2FnZTogZXJyb3I6?= =?UTF-8?B?IOKAmCpzZXJ2ZXLigJkgaXMgYSBwb2ludGVyOyBkaWQgeW91IG1lYW4gdG8g?= =?UTF-8?B?dXNlIOKAmC0+4oCZPyB3aGVuIC0+IGlzIHVzZWQ=?Date: Wed, 10 Jul 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: c
X-Bugzilla-Version: 6.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emil.fihlman at aalto 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:
Message-ID: <bug-91134-4-q0mczZUYfx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91134-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91134-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00728.txt.bz2
Content-length: 251
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91134
--- Comment #1 from Emil Fihlman <emil.fihlman at aalto dot fi> ---
The fix programming side is of course just wrapping *server in parentheses but
the error message should still be amended imho.
>From gcc-bugs-return-648618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 15:57:21 2019
Return-Path: <gcc-bugs-return-648618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99592 invoked by alias); 10 Jul 2019 15:57: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 99572 invoked by uid 48); 10 Jul 2019 15:57:18 -0000
From: "gcc at octaforge dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91135] New: __linux__ not defined with -mcall-aixdesc on 9.x and ppc64
Date: Wed, 10 Jul 2019 15:57: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gcc at octaforge 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-91135-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00730.txt.bz2
Content-length: 980
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91135
Bug ID: 91135
Summary: __linux__ not defined with -mcall-aixdesc on 9.x and
ppc64
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc at octaforge dot org
Target Milestone: ---
Since 9.x, using the `-mcall-aixdesc` makes gcc undefine `__linux__`. This
breaks compilation of the Linux kernel as it relies on the older behavior
(`-mcall-aixdesc` is used on BE, without it the kernel does not link and there
are several modules that check for `__linux__` being defined and break if it's
not).
The kernel claims it's a GCC bug:
https://bugzilla.kernel.org/show_bug.cgi?id=204125
Could someone confirm whether it is, so that it is known if this needs to be
fixed in gcc or in the kernel?
Thanks
>From gcc-bugs-return-648617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 15:57:09 2019
Return-Path: <gcc-bugs-return-648617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98892 invoked by alias); 10 Jul 2019 15:57: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 98859 invoked by uid 48); 10 Jul 2019 15:57:06 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjLzkxMTM0XSBDb25mdXNpbmcgZXJyb3IgbWVzc2FnZTogZXJyb3I6?= =?UTF-8?B?IOKAmCpzZXJ2ZXLigJkgaXMgYSBwb2ludGVyOyBkaWQgeW91IG1lYW4gdG8g?= =?UTF-8?B?dXNlIOKAmC0+4oCZPyB3aGVuIC0+IGlzIHVzZWQ=?Date: Wed, 10 Jul 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: 6.3.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: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-91134-4-XsW288Whog@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91134-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91134-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00729.txt.bz2
Content-length: 791
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91134
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-10
Ever confirmed|0 |1
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
struct X { int member; } x;
X* p = &x;
X** pp = &p;
int i = *pp->member;
91134.cc:4:14: error: request for member 'member' in '* pp', which is of
pointer type 'X*' (maybe you meant to use '->' ?)
4 | int i = *pp->member;
| ^~~~~~
>From gcc-bugs-return-648619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 16:00:50 2019
Return-Path: <gcc-bugs-return-648619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102915 invoked by alias); 10 Jul 2019 16:00: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 102848 invoked by uid 48); 10 Jul 2019 16:00:42 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjLzkxMTM0XSBDb25mdXNpbmcgZXJyb3IgbWVzc2FnZTogZXJyb3I6?= =?UTF-8?B?IOKAmCpzZXJ2ZXLigJkgaXMgYSBwb2ludGVyOyBkaWQgeW91IG1lYW4gdG8g?= =?UTF-8?B?dXNlIOKAmC0+4oCZPyB3aGVuIC0+IGlzIHVzZWQ=?Date: Wed, 10 Jul 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: 6.3.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-91134-4-k3XCzfirPn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91134-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91134-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00731.txt.bz2
Content-length: 1069
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91134
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Emil Fihlman from comment #0)
> fiesh on #gcc@Freenode gave these ideas regarding this:
>
> 2019-07-10 18:11:03 +0300 < fiesh> I think that `server->thing` is probably
> replaced by `(*server.thing)` since they are semantically equivalent at some
> stage before the error is produced
> 2019-07-10 18:11:45 +0300 < fiesh> then the parser sees that *server is a
> pointer type and you're trying to access its contents with ., so it tells
> you that doesn't work
> 2019-07-10 18:12:52 +0300 < fiesh> by ((*server).thing)
No I don't think that's what happens.
I think the error is given for any class member access expression where the
object expression has pointer type, i.e. `server->thing` is a member access
expression, and `server` is a pointer, so it gives that error.
What needs to happen is to check whether -> is already used, and in that case
suggest dereferencing the object expression first, i.e. `(*server)->thing`
>From gcc-bugs-return-648620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 16:07:26 2019
Return-Path: <gcc-bugs-return-648620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121127 invoked by alias); 10 Jul 2019 16: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 121085 invoked by uid 48); 10 Jul 2019 16:07:21 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91127] Incorrect checking of nonnull attribute with argument to a constructor of class with a virtual base
Date: Wed, 10 Jul 2019 16: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: 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:
Message-ID: <bug-91127-4-wVSIvMoATB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91127-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91127-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00732.txt.bz2
Content-length: 1349
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91127
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
The function that validates attribute positional arguments doesn't consider the
subtleties of C++ member functions so the diagnostic it gives in these cases is
confusing. I agree that the nonnull attribute doesn't make sense for the this
pointer. Clang gives an error when nonnull is applied to this, so changing GCC
to issue a warning (if not error) would seem appropriate.
Putting the implicit this argument in member functions at number 1 when in
non-members it refers to the first explicit argument seems like an unfortunate
design flaw. But it goes back many years so I also agree it wouldn't be safe
to change today.
I suspect the implicit int argument in ctors was never considered. I would
think it should be possible to skip without breaking too much code. Clang
handles the test case correctly and so should GCC.
The change from error for attribute nonnull to warning was just the result of
factoring the positional argument checking out of individual attribute handlers
and into a common function. Attributes alloc_align and alloc_size issued a
warning, and attribute nonnull an error, so I went with the former. Tightening
it to an error in GCC 10 to match Clang sounds like a good change.
>From gcc-bugs-return-648621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 16:07:46 2019
Return-Path: <gcc-bugs-return-648621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121964 invoked by alias); 10 Jul 2019 16:07: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 121892 invoked by uid 55); 10 Jul 2019 16:07:42 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91102] [9/10 Regression] aarch64 ICE on Linux kernel with -Os starting with r270266
Date: Wed, 10 Jul 2019 16: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: 9.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
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: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91102-4-3HgPlL9J7e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91102-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00733.txt.bz2
Content-length: 758
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91102
--- Comment #7 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
Author: vmakarov
Date: Wed Jul 10 16:07:10 2019
New Revision: 273357
URL: https://gcc.gnu.org/viewcvs?rev=273357&root=gcc&view=rev
Log:
2019-07-10 Vladimir Makarov <vmakarov@redhat.com>
PR target/91102
* lra-constraints.c (process_alt_operands): Don't match user
defined regs only if they are early clobbers.
2019-07-10 Vladimir Makarov <vmakarov@redhat.com>
PR target/91102
* gcc.target/aarch64/pr91102.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/aarch64/pr91102.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/lra-constraints.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-648622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 16:08:57 2019
Return-Path: <gcc-bugs-return-648622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123903 invoked by alias); 10 Jul 2019 16:08: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 123874 invoked by uid 48); 10 Jul 2019 16:08:54 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91135] __linux__ not defined with -mcall-aixdesc on 9.x and ppc64
Date: Wed, 10 Jul 2019 16: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: 9.1.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: 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-91135-4-DpHuh1d0ga@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91135-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91135-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00734.txt.bz2
Content-length: 617
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91135
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-07-10
CC| |segher at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Confimed.
Testcase:
:|gcc -E -dM - -mcall-aixdesc|grep linux
>From gcc-bugs-return-648623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 16:16:21 2019
Return-Path: <gcc-bugs-return-648623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15753 invoked by alias); 10 Jul 2019 16:16: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 15548 invoked by uid 48); 10 Jul 2019 16:16:17 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91132] New test gcc.dg/strlenopt-67.c in r273317 fails
Date: Wed, 10 Jul 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: testsuite
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: FIXED
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 resolution assigned_to
Message-ID: <bug-91132-4-rJ3lS3CtF4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91132-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91132-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00735.txt.bz2
Content-length: 518
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91132
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Fixed in r273358.
>From gcc-bugs-return-648624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 16:16:32 2019
Return-Path: <gcc-bugs-return-648624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16471 invoked by alias); 10 Jul 2019 16:16: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 16446 invoked by uid 55); 10 Jul 2019 16:16:29 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91132] New test gcc.dg/strlenopt-67.c in r273317 fails
Date: Wed, 10 Jul 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: testsuite
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: FIXED
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-91132-4-HV7AfJyjY3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91132-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91132-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-07/txt/msg00736.txt.bz2
Content-length: 505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91132
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Wed Jul 10 16:15:52 2019
New Revision: 273358
URL: https://gcc.gnu.org/viewcvs?rev=273358&root=gcc&view=rev
Log:
PR testsuite/91132 - test gcc.dg/strlenopt-67.c in r273317 fails
gcc/testsuite/ChangeLog:
* gcc.dg/strlenopt-67.c: Removed second copy of test.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/strlenopt-67.c
>From gcc-bugs-return-648625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jul 10 16:37:41 2019
Return-Path: <gcc-bugs-return-648625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66395 invoked by alias); 10 Jul 2019 16: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 66387 invoked by uid 89); 10 Jul 2019 16:37:41 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=0.8 required=5.0 testsºYES_50,HTML_MESSAGE,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=pricing, visitors, Trade, H*UA:15.0
X-HELO: n1nlsmtp02.shr.prod.ams1.secureserver.net
Received: from n1nlsmtp02.prod.ams1.secureserver.net (HELO n1nlsmtp02.shr.prod.ams1.secureserver.net) (188.121.43.194) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 10 Jul 2019 16:37:40 +0000
Received: from n3plcpnl0264.prod.ams3.secureserver.net ([160.153.155.20]) by : HOSTING RELAY : with ESMTP id lFa8hui7EteprlFa8hDyKW; Wed, 10 Jul 2019 09:36:36 -0700
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=universaldigitalehub.com; sÞfault; h=Content-Type:MIME-Version:Message-ID :Date:Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=K6K9y98zSdICX+OqgfREHv7oeJn7pBRLm4GddHgILgw=; b=rp00vO8Mk2GI2kULWAd4fPLcDD zb0QtgSx30jfp0f86zVOmRGwIWBCKdCB8zWWzEWqe9yULA52yWuY65Y96QP1lukAYehtUoiwgcPDM NEoZHw1OkpsmunlcrxsIK/mA+fjlAPMdLlKIr4nOVQIYoRHps31i+rr7TzBvTQsT7cjYhuBlPeyV+ +mTAYKXJY8YD0rkuD8vIl4L9d/syIpnu/lyzE5SjZdDwXtzEwOuW19/tSnrQkPW0ynFvDzrdLpOSi KNBi1O8YURw2asUvNigDDtVefFq8qOdt81/NlJwkEjZ6cUnR1HicjhnrtKPlpqbWSHHCMjYafHR8B WhByw0cQ==;
Received: from [95.211.162.11] (portW103 helo=WS98) by n3plcpnl0264.prod.ams3.secureserver.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <kathryn.watson@universaldigitalehub.com>) id 1hlF1Q-00Dv5k-EY for gcc-bugs@gcc.gnu.org; Wed, 10 Jul 2019 09:00:44 -0700
From: "Kathryn Watson" <kathryn.watson@universaldigitalehub.com>
To: <gcc-bugs@gcc.gnu.org>
Subject: Swim Collective Trade Show 2019
Date: Wed, 10 Jul 2019 16:37:00 -0000
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAOeQyroOCqRLgW/hRe1gF3jCgAAAEAAAAP5C7Fk3C7REpjkTNcitJLsBAAAAAA==@universaldigitalehub.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-SW-Source: 2019-07/txt/msg00737.txt.bz2
Content-length: 303
Hi,
We are providing the Attendees list of Swim Collective Trade Show 2019 with
9,950 visitors.
If you are interested, please let me know your thoughts, so that I can send
you the pricing for it.
Best Regards,
Kathryn Watson
Demand Generation
To be removed from my emails, please reply STOP.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (3 preceding siblings ...)
2019-07-05 1:51 ` dave.anglin at bell dot net
@ 2020-02-25 14:55 ` peter.bisroev at groundlabs dot com
2020-04-18 1:11 ` dave.anglin at bell dot net
` (74 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: peter.bisroev at groundlabs dot com @ 2020-02-25 14:55 UTC (permalink / raw)
To: gcc-bugs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 1891062 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #204 from Peter Bisroev <peter.bisroev at groundlabs dot com> ---
(In reply to dave.anglin from comment #203)
> On 2020-02-25 12:56 a.m., peter.bisroev at groundlabs dot com wrote:
> > Now looking at the main.o generated by gcc, the relocation seems to be as
> > expected but the relocation address seems to be off:
> > ------------------------------
> > 20: 04 00 00 00 01 00 [MLX] nop.m 0x0
> > 21: PCREL60B hello
> > 26: 00 00 00 00 00 00 brl.call.sptk.many b0=20 <main+0x20>
> > 2c: 08 00 00 d0
> > ------------------------------
> >
> > As can be seen above, GNU as is telling HP's ld to do the relocation at 0x21,
> > which falls into slot 1 and 0. However the relocation needs to be done at 0x26
> > to cover slots 2 and 1.
> Comparing with HP as, it looks to me like the relocation should be at 0x22
> and that's why
> the preceding nop.m instruction is being clobbered.
>
> Would you file a binutils bug report with the main.s gcc source? It looks
> like gcc doesn't
> generate brl branches and this never got tested. You can add me to the cc
> list.
Thank you Dave, you are 100% correct, it needs to be at 0x22. I was looking at
the same screen for too long yesterday.
Anyway, I have manually patched my object to use 0x22 as reloc offset as well
as another brl related offset to a weakfunc() and everything linked and worked
perfectly.
------------------------------
...
4000950: 04 00 00 00 01 00 [MLX] nop.m 0x0
4000956: 00 00 00 00 00 00 brl.call.sptk.many
b0=40009d0 <hello>
400095c: 88 00 00 d0
...
4000970: 04 00 00 00 01 00 [MLX] nop.m 0x0
4000976: 00 00 00 00 00 00 brl.call.sptk.many
b0=4000ac0 <func>
400097c: 58 01 00 d0
...
------------------------------
I will file a bug with binutils.
Thanks again for catching my offset mistake.
--peter
>From gcc-bugs-return-671345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 15:07:21 2020
Return-Path: <gcc-bugs-return-671345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62723 invoked by alias); 25 Feb 2020 15:07: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 62631 invoked by uid 55); 25 Feb 2020 15:07:08 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Tue, 25 Feb 2020 15:07: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93871-4-uzSwFd6hIq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02927.txt.bz2
Content-length: 1086
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #22 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Feb 25, 2020 at 07:32:31AM +0000, thenlich at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
>
> --- Comment #21 from Thomas Henlich <thenlich at gcc dot gnu.org> ---
> One should also ask: What is the least surprising way to implement the
> cotangent function?
>
> If someone uses a (non-standard) function bearing a name similar to "tangent",
> they probably expect a function similar in precision and runtime to the
> standard tangent function, and nothing which is more accurate in certain
> ranges, but which is also slower.
>
> For being able to use a construct like "y = a * cotan(x)" instead of "y = a /
> tan(x)" there should be no additional punishment aside from standard
> non-compliance.
>
Having spent considerable time implementing tanl() that
resides in FreeBSD's libm, I suspect no one is going to
do the work to ensure the max ULP of cotan is no worse
than max ULP of tan.
>From gcc-bugs-return-671347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 15:13:30 2020
Return-Path: <gcc-bugs-return-671347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70930 invoked by alias); 25 Feb 2020 15:13: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 70827 invoked by uid 48); 25 Feb 2020 15:13:17 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93106] [c++2a] Deleted move constructor is not selected when returning an automatic variable
Date: Tue, 25 Feb 2020 15: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.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: cc
Message-ID: <bug-93106-4-wKMyx6KzbX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02929.txt.bz2
Content-length: 448
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93106
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |barry.revzin at gmail dot com
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 93929 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-671346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 15:13:30 2020
Return-Path: <gcc-bugs-return-671346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70925 invoked by alias); 25 Feb 2020 15:13: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 70802 invoked by uid 48); 25 Feb 2020 15:13:17 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93929] In copy elision cases, fallback to lvalue even if rvalue overload resolution succeeds
Date: Tue, 25 Feb 2020 15: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: 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-93929-4-wQ72MYHh0z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93929-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02928.txt.bz2
Content-length: 498
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93929
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is a dup
*** This bug has been marked as a duplicate of bug 93106 ***
>From gcc-bugs-return-671348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 15:32:32 2020
Return-Path: <gcc-bugs-return-671348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65985 invoked by alias); 25 Feb 2020 15:32: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 65889 invoked by uid 48); 25 Feb 2020 15:32:18 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/53182] GNU C: attributes without underscores should be discouraged / no longer be documented e.g. as examples
Date: Tue, 25 Feb 2020 15: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: unknown
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: vincent-gcc at vinc17 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:
Message-ID: <bug-53182-4-Daql2Foo6p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53182-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53182-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02930.txt.bz2
Content-length: 1104
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53182
--- Comment #8 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
(In reply to Jonathan Wakely from comment #7)
> (In reply to Vincent Lefèvre from comment #6)
> > Also, note that identifiers that are not reserved should not be used,
> > because they could be defined as macros by the developer, who has not tested
> > his code with GCC (I'm saying GCC here, but this applies to any compiler).
>
> Should not be used by who?
by non-user code, but this applies in particular to what's inside
__attribute__.
Here's an example. In MPFR's mpfr.h file, we use:
#define __MPFR_SENTINEL_ATTR
#if defined (__GNUC__)
# if __GNUC__ >= 4
# undef __MPFR_SENTINEL_ATTR
# define __MPFR_SENTINEL_ATTR __attribute__ ((sentinel))
# endif
#endif
But if in my personal C code, I have
#define sentinel 1
before the #include's or, in a similar way, compile my program with -Dsentinel,
then I get a compilation failure. Here the end user is not supposed to know
that the identifier "sentinel" (which is not reserved) is used internally.
>From gcc-bugs-return-671349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 16:09:51 2020
Return-Path: <gcc-bugs-return-671349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10365 invoked by alias); 25 Feb 2020 16:09: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 10318 invoked by uid 48); 25 Feb 2020 16:09:46 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93761] ICE when compiling a standard header as a header unit
Date: Tue, 25 Feb 2020 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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan 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-93761-4-a4QV51k6fi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02931.txt.bz2
Content-length: 460
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93761
Nathan Sidwell <nathan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
There, I fixed it anyway :)
934fe9a30d2
>From gcc-bugs-return-671350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 16:13:26 2020
Return-Path: <gcc-bugs-return-671350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18403 invoked by alias); 25 Feb 2020 16:13: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 18316 invoked by uid 48); 25 Feb 2020 16:13:14 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92071] [10 regression][ARM] ice in gen_movsi, at config/arm/arm.md:5378
Date: Tue, 25 Feb 2020 16:13: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: needs-bisection, wrong-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: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92071-4-3UpzMSBzqZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92071-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92071-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02932.txt.bz2
Content-length: 262
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92071
--- Comment #11 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Eric Botcazou from comment #10)
> Fixing.
Over a month has gone by. I see no fix in trunk. Am I looking
in the wrong place ?
>From gcc-bugs-return-671351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 16:27:54 2020
Return-Path: <gcc-bugs-return-671351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60586 invoked by alias); 25 Feb 2020 16:27: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 60531 invoked by uid 48); 25 Feb 2020 16:27:50 -0000
From: "peter.bisroev at groundlabs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
Date: Tue, 25 Feb 2020 16:27: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: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: major
X-Bugzilla-Who: peter.bisroev at groundlabs 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-61577-4-rTpNA1nDDv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02933.txt.bz2
Content-length: 577
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #205 from Peter Bisroev <peter.bisroev at groundlabs dot com> ---
Hi Dave,
I have submitted bug 25599
(https://sourceware.org/bugzilla/show_bug.cgi?id=25599) to binutils with a
slightly simplified test case and CCed you as well.
Additionally, I was also able to verify that current binutils (2.34), can now
be compiled with our bootstrapped gcc 4.7.4 (I was not able to do so using aCC
before). So hopefully once the bug is fixed we can continue testing it here.
Thanks again for your help!
--peter
>From gcc-bugs-return-671352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 16:39:26 2020
Return-Path: <gcc-bugs-return-671352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121984 invoked by alias); 25 Feb 2020 16:39: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 121893 invoked by uid 48); 25 Feb 2020 16:39:22 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86827] [8 Regression] -Warray-bounds produces negative indicies
Date: Tue, 25 Feb 2020 16: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: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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: bug_status resolution
Message-ID: <bug-86827-4-5Oaw9hNDcC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86827-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86827-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02934.txt.bz2
Content-length: 567
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86827
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> ---
It was fixed in r268048 committed for bug 88273 into GCC 9 and backported to
GCC 8.
*** This bug has been marked as a duplicate of bug 88273 ***
>From gcc-bugs-return-671353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 16:39:27 2020
Return-Path: <gcc-bugs-return-671353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122085 invoked by alias); 25 Feb 2020 16:39: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 121920 invoked by uid 48); 25 Feb 2020 16:39:22 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88273] [8 Regression] warning: 'memcpy' offset [-527, -529] is out of the bounds [0, 16] of object 'vrsave' with type 'union <anonymous>' [-Warray-bounds]
Date: Tue, 25 Feb 2020 16: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: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88273-4-cc1uKmvKUf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88273-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88273-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02935.txt.bz2
Content-length: 437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88273
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |liuw at liuw dot name
--- Comment #16 from Martin Sebor <msebor at gcc dot gnu.org> ---
*** Bug 86827 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-671354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 16:52:00 2020
Return-Path: <gcc-bugs-return-671354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119269 invoked by alias); 25 Feb 2020 16:52: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 119214 invoked by uid 48); 25 Feb 2020 16:51:56 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93913] [10 regression] r10-6762 breaks gcc.target/powerpc/fold-vec-st-*.c test cases
Date: Tue, 25 Feb 2020 16: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: 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: bug_status bug_file_loc cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-93913-4-Lv1xMFryJ1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93913-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93913-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02936.txt.bz2
Content-length: 796
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93913
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
URL| |https://gcc.gnu.org/ml/gcc-
| |patches/2020-02/msg01398.ht
| |ml
Last reconfirmed| |2020-02-25
Assignee|unassigned at gcc dot gnu.org |bergner at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Peter Bergner <bergner at gcc dot gnu.org> ---
Confirmed. Patch submitted.
>From gcc-bugs-return-671355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 17:10:51 2020
Return-Path: <gcc-bugs-return-671355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23718 invoked by alias); 25 Feb 2020 17:10: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 23662 invoked by uid 48); 25 Feb 2020 17:10:46 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92267] [9 Regression] crash with a cppunit test case (built by GCC 9) and cpptest (built with GCC 8)
Date: Tue, 25 Feb 2020 17:10: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: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: romain.geissler at amadeus dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92267-4-FLuDTKRhAl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92267-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92267-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02937.txt.bz2
Content-length: 1220
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92267
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 Jonathan,
Sorry to jump back into this old bug, but isn't it a issue that this was
backported to gcc 9 after some releases of gcc 9 were in the wild yet ?
I mean, someone having built some binaries with gcc 9.1.0 or 9.2.0, mixing it
later with a binary built with the upcoming gcc 9.3.0 will also see a similar
crash, no ? I think (but I am not sure yet) this is actually happening to me
(although I am not using gcc releases, but directly compile from git from
gcc-9-branch, so I understand my right to complain is low, if not non legit at
all). What is advocated in this case, that all binaries build with gcc 9.1.0 or
9.2.0 shall be rebuilt as well ? Or is there any way that somehow the gcc 9
branch (and not gcc 10 one) can support both ABIs to cope with past mistakes ?
Cheers,
Romain
>From gcc-bugs-return-671356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 17:16:18 2020
Return-Path: <gcc-bugs-return-671356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75816 invoked by alias); 25 Feb 2020 17:16: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 74791 invoked by uid 48); 25 Feb 2020 17:15:41 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92267] [9 Regression] crash with a cppunit test case (built by GCC 9) and cpptest (built with GCC 8)
Date: Tue, 25 Feb 2020 17:16: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: ABI
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: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92267-4-dhFPM8hYVu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92267-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92267-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02938.txt.bz2
Content-length: 1422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92267
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Romain Geissler from comment #8)
> Sorry to jump back into this old bug, but isn't it a issue that this was
> backported to gcc 9 after some releases of gcc 9 were in the wild yet ?
Yes. The choice was to accept a break and say "starting with GCC 9 there's an
ABI break, nothing before 9 is compatible with anything after that" or to
consider 9.1.0 and 9.2.0 to be buggy and fix the mistake for 9.3.0.
> I mean, someone having built some binaries with gcc 9.1.0 or 9.2.0, mixing
> it later with a binary built with the upcoming gcc 9.3.0 will also see a
> similar crash, no ? I think (but I am not sure yet) this is actually
> happening to me (although I am not using gcc releases, but directly compile
> from git from gcc-9-branch, so I understand my right to complain is low, if
> not non legit at all). What is advocated in this case, that all binaries
> build with gcc 9.1.0 or 9.2.0 shall be rebuilt as well ? Or is there any way
> that somehow the gcc 9 branch (and not gcc 10 one) can support both ABIs to
> cope with past mistakes ?
I'm not aware of any way to make that work.
Once GCC 9.3.0 is released the solution is to upgrade to 9.3.0 and consider
9.1.0 and 9.2.0 to have a bug. If that bug affects you, you'll need to rebuild
code built with those versions.
>From gcc-bugs-return-671357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 17:41:18 2020
Return-Path: <gcc-bugs-return-671357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100883 invoked by alias); 25 Feb 2020 17: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 100815 invoked by uid 48); 25 Feb 2020 17:41:12 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92267] [9 Regression] crash with a cppunit test case (built by GCC 9) and cpptest (built with GCC 8)
Date: Tue, 25 Feb 2020 17:41: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: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: romain.geissler at amadeus dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92267-4-kwlbmVgyq3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92267-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92267-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02939.txt.bz2
Content-length: 482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92267
--- Comment #10 from Romain Geissler <romain.geissler at amadeus dot com> ---
Ok, I was not sure whether it was more important to have a given major branch
(ie all gcc 9 releases) consistent or favor compatibility with the biggest
number of gcc releases (cross branches). You replied to that.
Do you think this shall be somehow be listed as a known issue in the gcc 9
release notes https://gcc.gnu.org/gcc-9/changes.html ?
>From gcc-bugs-return-671358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 17:43:55 2020
Return-Path: <gcc-bugs-return-671358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104125 invoked by alias); 25 Feb 2020 17: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 104031 invoked by uid 48); 25 Feb 2020 17:43:51 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92071] [10 regression][ARM] ice in gen_movsi, at config/arm/arm.md:5378
Date: Tue, 25 Feb 2020 17: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: needs-bisection, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-92071-4-wCqoIwqDyO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92071-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92071-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02940.txt.bz2
Content-length: 268
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92071
--- Comment #12 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Over a month has gone by. I see no fix in trunk. Am I looking
> in the wrong place ?
Why do you think I put "fixing" instead of "fixed"? ;-)
>From gcc-bugs-return-671359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 17:44:43 2020
Return-Path: <gcc-bugs-return-671359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105102 invoked by alias); 25 Feb 2020 17:44: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 105064 invoked by uid 48); 25 Feb 2020 17:44:39 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92267] [9 Regression] crash with a cppunit test case (built by GCC 9) and cpptest (built with GCC 8)
Date: Tue, 25 Feb 2020 17:44: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: ABI
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: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92267-4-jjmeWAPqBY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92267-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92267-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02941.txt.bz2
Content-length: 149
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92267
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, I should add it there.
>From gcc-bugs-return-671360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 17:59:25 2020
Return-Path: <gcc-bugs-return-671360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17814 invoked by alias); 25 Feb 2020 17:59: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 17773 invoked by uid 48); 25 Feb 2020 17:59:21 -0000
From: "fredrik987 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93930] New: Unnecessary broadcast instructions for AVX512
Date: Tue, 25 Feb 2020 17:59: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.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fredrik987 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-93930-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02942.txt.bz2
Content-length: 3132
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93930
Bug ID: 93930
Summary: Unnecessary broadcast instructions for AVX512
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: fredrik987 at gmail dot com
Target Milestone: ---
Created attachment 47908
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47908&action=edit
Test case
The code below generates unnecessary broadcast instructions for AVX512,
compiled with "-Ofast -march=skylake-avx512". This occurs for gcc trunk and
9.2/8.3 but not 7.5.
Most constants are read from memory via vbroadcastss except two, which are read
as scalars and then broadcast within the loop. For gcc 7.5 all constants are
read via vbroadcastss.
The problem seems to be more frequent for larger functions.
---
Compiler output for gcc 9.2:
...
.L3:
vmovaps zmm0, ZMMWORD PTR [rdi]
add rdi, 64
vmovaps zmm3, zmm0
vmovaps zmm1, zmm0
vmulps zmm2, zmm0, zmm0
vfmadd132ps zmm3, zmm11, zmm12
vfmadd132ps zmm1, zmm13, zmm14
vmovaps zmm4, zmm0
vfmadd132ps zmm4, zmm7, zmm8
sub rsi, -128
vfmadd132ps zmm1, zmm3, zmm2
vmovaps zmm3, zmm0
vfmadd132ps zmm3, zmm9, zmm10
vfmadd132ps zmm3, zmm4, zmm2
vbroadcastss zmm4, xmm15 <--- Broadcast within loop
vmulps zmm3, zmm3, zmm1
vmovaps ZMMWORD PTR [rsi-128], zmm3
vbroadcastss zmm3, xmm16 <--- Broadcast within loop
vfmadd132ps zmm3, zmm4, zmm0
vfmadd132ps zmm0, zmm5, zmm6
vfmadd132ps zmm0, zmm3, zmm2
vmulps zmm1, zmm1, zmm0
vmovaps ZMMWORD PTR [rsi-64], zmm1
cmp rdi, rax
jne .L3
...
---
#include <immintrin.h>
static __m512 f(__m512 x)
{
__m512 a = _mm512_set1_ps(11);
__m512 b = _mm512_set1_ps(12);
__m512 c = _mm512_set1_ps(13);
__m512 d = _mm512_set1_ps(14);
__m512 y = _mm512_mul_ps(x, x);
return _mm512_fmadd_ps(y, _mm512_fmadd_ps(x, a, b), _mm512_fmadd_ps(x, c,
d));
}
static __m512 g(__m512 x)
{
__m512 a = _mm512_set1_ps(21);
__m512 b = _mm512_set1_ps(22);
__m512 c = _mm512_set1_ps(23);
__m512 d = _mm512_set1_ps(24);
__m512 y = _mm512_mul_ps(x, x);
return _mm512_fmadd_ps(y, _mm512_fmadd_ps(x, a, b), _mm512_fmadd_ps(x, c,
d));
}
static __m512 h(__m512 x)
{
__m512 a = _mm512_set1_ps(31);
__m512 b = _mm512_set1_ps(32);
__m512 c = _mm512_set1_ps(33);
__m512 d = _mm512_set1_ps(34);
__m512 y = _mm512_mul_ps(x, x);
return _mm512_fmadd_ps(y, _mm512_fmadd_ps(x, a, b), _mm512_fmadd_ps(x, c,
d));
}
void test(__m512 *x, __m512 *y, int n)
{
for (int i = 0; i < n; i++) {
__m512 u = *x++;
__m512 v = h(u);
*y++ = _mm512_mul_ps(f(u), v);
*y++ = _mm512_mul_ps(g(u), v);
}
}
>From gcc-bugs-return-671361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 18:22:21 2020
Return-Path: <gcc-bugs-return-671361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114067 invoked by alias); 25 Feb 2020 18:22: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 114033 invoked by uid 48); 25 Feb 2020 18:22:16 -0000
From: "Peter.Georg at physik dot uni-regensburg.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93931] New: ICE using lambda capture in openMP parallel for reduction
Date: Tue, 25 Feb 2020 18:22: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: Peter.Georg at physik dot uni-regensburg.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-93931-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02943.txt.bz2
Content-length: 1281
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93931
Bug ID: 93931
Summary: ICE using lambda capture in openMP parallel for
reduction
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: Peter.Georg at physik dot uni-regensburg.de
Target Milestone: ---
Created attachment 47909
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47909&action=edit
Source
The following (and attached) code fails to compile with any GCC >= 8 when
openMP is enabled. GCC compiles the code, but the result is wrong. Any tested
clang version compiles the code with no errors and the result is right.
#include <iostream>
int main()
{
int score = 0;
[&score]()
{
#pragma omp parallel for reduction(+ : score)
for(int i= 0; i < 1000; ++i)
{
score += i;
}
}();
std::cout << score << std::endl;
return score;
}
Error:
during RTL pass: expand
omp.cpp: In lambda function:
omp.cpp:6:9: internal compiler error: in make_decl_rtl, at varasm.c:1340
6 | #pragma omp parallel for reduction(+ : score)
|
>From gcc-bugs-return-671362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 18:29:56 2020
Return-Path: <gcc-bugs-return-671362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124827 invoked by alias); 25 Feb 2020 18:29: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 124775 invoked by uid 48); 25 Feb 2020 18:29:51 -0000
From: "ch3root at openwall dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93848] missing -Warray-bounds warning for array subscript 1 is outside array bounds
Date: Tue, 25 Feb 2020 18: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: diagnostic
X-Bugzilla-Severity: enhancement
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: cc
Message-ID: <bug-93848-4-Q9pH5YzHtC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02944.txt.bz2
Content-length: 2003
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93848
Alexander Cherepanov <ch3root at openwall dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ch3root at openwall dot com
--- Comment #7 from Alexander Cherepanov <ch3root at openwall dot com> ---
I agree that the original example exhibits UB. One of the violated norms that
was not yet mentioned is C11, 6.3.2.1p1:
"if an lvalue does not designate an object when it is evaluated, the behavior
is undefined"
To go further in this direction, let's compare arrays and structs:
char (*p)[2] = malloc(1); ... use (*p)[0]
struct { char x, y; } *q = malloc(1); ... use (*q).x
Are these valid? Do structs differ? DR 073[1], items A, B, C, F, G, H, says
that the . operator requires a complete structure as its left operand but fails
to address the issue with an array directly. IMHO arrays should not differ.
[1] http://open-std.org/jtc1/sc22/wg14/www/docs/dr_073.html
OTOH suppose that p[1] is not UB per se in the original example. What is the
result of its decay? C11, 6.3.2.1p3 says that it "points to the initial element
of the array object". But there is no array object here. Then, which operations
are allowed for this pointer? p[1]+0 is ok? Writing it as &p[1][0] is ok? What
about p[1]+1 or &p[1][1]? gcc doesn't warn about it:
----------------------------------------------------------------------
#include <stdio.h>
int main()
{
int a[1][4];
printf("%p\n", (void *)&a[1][1]);
}
----------------------------------------------------------------------
$ gcc -std=c11 -pedantic -Wall -Wextra -Warray-bounds=2 -O3 test.c && ./a.out
0x7ffc5904aa04
----------------------------------------------------------------------
gcc x86-64 version: gcc (GCC) 10.0.1 20200225 (experimental)
----------------------------------------------------------------------
>From gcc-bugs-return-671363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 19:20:55 2020
Return-Path: <gcc-bugs-return-671363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68336 invoked by alias); 25 Feb 2020 19:20: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 68287 invoked by uid 48); 25 Feb 2020 19:20:50 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/78993] False positive from -Wmaybe-uninitialized
Date: Tue, 25 Feb 2020 19:20: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: 7.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc assigned_to
Message-ID: <bug-78993-4-q7zR7LUOIp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78993-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78993-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02945.txt.bz2
Content-length: 2712
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78993
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |law at redhat dot com
Assignee|unassigned at gcc dot gnu.org |law at redhat dot com
--- Comment #6 from Jeffrey A. Law <law at redhat dot com> ---
Andrew, Manu, wrong. This is not a failing to handle logicals, threading
handles those just fine. It's code that tries to keep the cost of jump
threading down. Jump threading is expensive and scales poorly -- left to its
own devices it'd actually try to thread every potential path through the CFG
which is obviously undesirable.
The thread3 dump looks something like this:
;; basic block 2, loop depth 0
;; pred: ENTRY
j_6 = rand ();
if (i_3(D) >= j_6)
goto <bb 8>; [55.78%]
else
goto <bb 3>; [44.22%]
;; succ: 8
;; 3
;; basic block 3, loop depth 0
;; pred: 2
if (i_3(D) < 0)
goto <bb 4>; [13.00%]
else
goto <bb 5>; [87.00%]
;; succ: 4
;; 5
;; basic block 4, loop depth 0
;; pred: 3
;; 8
# j_26 = PHI <j_6(3), j_12(D)(8)>
# prephitmp_20 = PHI <0(3), 1(8)>
i_4 = rand ();
;; succ: 5
;; basic block 5, loop depth 0
;; pred: 4
;; 3
# i_5 = PHI <i_4(4), i_3(D)(3)>
# j_27 = PHI <j_26(4), j_6(3)>
# prephitmp_7 = PHI <prephitmp_20(4), 0(3)>
_16 = i_5 > 9;
_17 = _16 | prephitmp_7;
if (_17 != 0)
goto <bb 6>; [0.00%]
else
goto <bb 7>; [100.00%]
;; succ: 6
;; 7
;; basic block 6, loop depth 0
;; pred: 5
;; 8
;; succ: 7
;; basic block 7, loop depth 0
;; pred: 6
;; 5
# _1 = PHI <0(6), j_27(5)>
return _1;
;; succ: EXIT
;; basic block 8, loop depth 0
;; pred: 2
if (i_3(D) < 0)
goto <bb 4>; [35.41%]
else
goto <bb 6>; [64.59%]
;; succ: 4
;; 6
The path we want to thread is bb8->bb4->bb5 which will always result in
reaching bb6. But bb4 doesn't look interesting to the threader (it's got
statements with side effects (so it's not a forwarder) and it has a single
successor.
If we loosen the requirements for what looks interesting to the threader (say
by making everything interesting), then the threader will pick up this missed
jump thread and as a side effect of eliminating the infeasible path
(8->4->5->7) eliminates the false positive.
>From gcc-bugs-return-671364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 19:21:30 2020
Return-Path: <gcc-bugs-return-671364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69228 invoked by alias); 25 Feb 2020 19: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 69154 invoked by uid 48); 25 Feb 2020 19:21:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93820] [8/9/10 Regression] wrong code at -O3 on x86_64-linux-gnu since r9-1732
Date: Tue, 25 Feb 2020 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.1
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: P2
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 attachments.created
Message-ID: <bug-93820-4-qfvVlhsMs6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02946.txt.bz2
Content-length: 1185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93820
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 47910
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47910&action=edit
gcc10-pr93820.patch
Untested fix. For GCC11 we might as well perform some kind of quick DSE in the
store-merging pass (I mean, e.g. after sort_by_bitpos sorting, where the stores
are sorted by increasing bitpos and with the same bitpos by increasing order,
it shouldn't be that expensive for each store to check if it isn't fully
redundant through stores with higher order, mark them some way, create special
merged store for all of them that would emit nothing and just get those stores
deleted and move them at the end of m_store_info or temporarily away from it so
that coalesce_immediate_stores doesn't have to skip them).
>From gcc-bugs-return-671365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 19:22:22 2020
Return-Path: <gcc-bugs-return-671365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70312 invoked by alias); 25 Feb 2020 19:22: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 70252 invoked by uid 48); 25 Feb 2020 19:22:18 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93843] [10 Regression] wrong code at -O3 on x86_64-linux-gnu
Date: Tue, 25 Feb 2020 19: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: 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: bug_status assigned_to
Message-ID: <bug-93843-4-0PuuTVvMyR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02947.txt.bz2
Content-length: 500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93843
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 #8 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Testing a patch.
>From gcc-bugs-return-671366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 19:25:32 2020
Return-Path: <gcc-bugs-return-671366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72717 invoked by alias); 25 Feb 2020 19:25: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 72639 invoked by uid 48); 25 Feb 2020 19:25:28 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93820] [8/9/10 Regression] wrong code at -O3 on x86_64-linux-gnu since r9-1732
Date: Tue, 25 Feb 2020 19: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: 9.2.1
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: 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-93820-4-Nq9Celx84w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02948.txt.bz2
Content-length: 644
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93820
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
On the original testcase, the reason why dse3 doesn't help is we have:
a[4] = 1;
_4 = *c.0_1;
a[5] = _4;
a[3] = 1;
e = 0;
a[8] = 0;
MEM <vector(4) int> [(int *)&a + 16B] = { 0, 0, 0, 0 };
and c.0_1 might alias the a array, so dse3 removes a[5] store as redundant, but
only later cddce removes the _4 = *c.0_1 load and only then the a[4] = 1; store
could be also removed (i.e. it would require iteration, or performing some kind
of (cheap) dce in the dse pass after removing each store).
>From gcc-bugs-return-671367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 19:27:19 2020
Return-Path: <gcc-bugs-return-671367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79597 invoked by alias); 25 Feb 2020 19: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 79562 invoked by uid 48); 25 Feb 2020 19:27:14 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/71699] bogus -Wmaybe-uninitialized warning: gcc misses that non-NULL pointer + offset can never be NULL
Date: Tue, 25 Feb 2020 19:27: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: 7.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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 cc everconfirmed
Message-ID: <bug-71699-4-ZmR6NBjqw4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71699-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71699-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02949.txt.bz2
Content-length: 720
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71699
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-25
CC| |law at redhat dot com
Ever confirmed|0 |1
--- Comment #12 from Jeffrey A. Law <law at redhat dot com> ---
Confirming for -O0 we get the false positive, which isn't a huge surprise given
how little analysis we do for -O0, similarly for -Og.
For -Ox for x >= 1 the warning is suppressed.
>From gcc-bugs-return-671369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 19:43:26 2020
Return-Path: <gcc-bugs-return-671369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45456 invoked by alias); 25 Feb 2020 19:43: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 45432 invoked by uid 48); 25 Feb 2020 19:43:21 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93932] New: PowerPC vec_extract with variable element number has code regressions for V2DI/V2DF vectors
Date: Tue, 25 Feb 2020 19:43: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: meissner 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-93932-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02951.txt.bz2
Content-length: 1609
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93932
Bug ID: 93932
Summary: PowerPC vec_extract with variable element number has
code regressions for V2DI/V2DF vectors
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: meissner at gcc dot gnu.org
Target Milestone: ---
I've been looking at vec_extract recently, both in terms of support for the
-mcpu=future and to look at supporting PR target/93230 in GCC 11.
In some cases, if you have a vec_extract built-in function where the vector is
in a register, and the element is variable, the compiler decides store this
vector to memory, and then do the variable extract using a scalar load.
Unfortunately, this lead to a STORE-HIT-LOAD slowdown, as the scalar load will
likely have to wait for the vector store to finish.
The test cases are the fold-vect-extract-<type>.p{7,8,9}.c} files in the
gcc.target/powerpc directory, where <type> is 'char', 'short', 'int',
'longlong', 'float' and 'double', and the p7/p8/p9 indicates whether the test
is for -mcpu=power7, -mcpu=power8, or -mcpu=power9.
For -mcpu=power8, the regressions are:
fold-vect-extract-double.p8.c: GCC 9.x and current trunk
fold-vect-extract-longlong.p8.c: GCC 9.x and current trunk
For -mcpu=power9, the regressions are:
fold-vect-extract-double.p9.c: GCC 9.x (current trunk is ok)
fold-vect-extract-longlong.p9.c: GCC 9.x (current trunk is ok)
>From gcc-bugs-return-671368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 19:43:09 2020
Return-Path: <gcc-bugs-return-671368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44742 invoked by alias); 25 Feb 2020 19:43: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 44671 invoked by uid 48); 25 Feb 2020 19:43:04 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/67196] Another false positive from -Wmaybe-uninitialized
Date: Tue, 25 Feb 2020 19: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: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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-67196-4-HwmprdrYg9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67196-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67196-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02950.txt.bz2
Content-length: 703
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67196
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #2 from Jeffrey A. Law <law at redhat dot com> ---
I believe jump threading doesn't thread in this case because doing so is going
to muck up the loop structures. Essentially it has to thread from outside the
loop through the loop header to a point in the interior of the loop. Except
for a very limited number of circumstances that creates irreducible loops and
it's avoided.
>From gcc-bugs-return-671371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 19:44:19 2020
Return-Path: <gcc-bugs-return-671371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47591 invoked by alias); 25 Feb 2020 19:44: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 47472 invoked by uid 55); 25 Feb 2020 19:44:15 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89917] [8 Regression] ICE with lambda in variadic template hierarchy
Date: Tue, 25 Feb 2020 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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89917-4-2SuChZ3rbU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89917-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89917-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02953.txt.bz2
Content-length: 773
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89917
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:7ac251ee4fa84f5a7583c597fa0641278e3855fc
commit r8-10064-g7ac251ee4fa84f5a7583c597fa0641278e3855fc
Author: Jason Merrill <jason@redhat.com>
Date: Tue Feb 25 13:37:18 2020 -0500
PR c++/89917 - ICE with lambda in variadic mem-init.
A mem-initializer is not a type, and we don't want to turn autos within it
into packs.
gcc/cp/ChangeLog
2020-02-25 Jason Merrill <jason@redhat.com>
PR c++/89917 - ICE with lambda in variadic mem-init.
* pt.c (make_pack_expansion): Change type_pack_expansion_p to false.
>From gcc-bugs-return-671373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 19:44:41 2020
Return-Path: <gcc-bugs-return-671373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48749 invoked by alias); 25 Feb 2020 19: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 48368 invoked by uid 48); 25 Feb 2020 19:44:36 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93932] PowerPC vec_extract with variable element number has code regressions for V2DI/V2DF vectors
Date: Tue, 25 Feb 2020 19: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: meissner 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-93932-4-8uFUYjg099@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93932-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93932-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02955.txt.bz2
Content-length: 713
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93932
Michael Meissner <meissner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-25
CC| |dje at gcc dot gnu.org,
| |meissner at gcc dot gnu.org,
| |segher at gcc dot gnu.org,
| |wschmidt at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-671370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 19:44:07 2020
Return-Path: <gcc-bugs-return-671370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46702 invoked by alias); 25 Feb 2020 19:44: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 46646 invoked by uid 48); 25 Feb 2020 19:44:02 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89917] [8 Regression] ICE with lambda in variadic template hierarchy
Date: Tue, 25 Feb 2020 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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-89917-4-n8gCQlgzmO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89917-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89917-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02952.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89917
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 19:44:38 2020
Return-Path: <gcc-bugs-return-671372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48403 invoked by alias); 25 Feb 2020 19:44: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 48281 invoked by uid 48); 25 Feb 2020 19:44:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93930] [8/9/10 Regression] Unnecessary broadcast instructions for AVX512
Date: Tue, 25 Feb 2020 19: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: 9.2.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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-93930-4-IL6X4hEUX1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93930-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93930-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02954.txt.bz2
Content-length: 964
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93930
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-25
CC| |hubicka at gcc dot gnu.org,
| |jakub at gcc dot gnu.org
Target Milestone|--- |8.4
Summary|Unnecessary broadcast |[8/9/10 Regression]
|instructions for AVX512 |Unnecessary broadcast
| |instructions for AVX512
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Seems this has started with r8-3873-gc53c148c9155c1c26bf35b2763bf34d2ae26bc4b
>From gcc-bugs-return-671374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 19:49:30 2020
Return-Path: <gcc-bugs-return-671374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57136 invoked by alias); 25 Feb 2020 19:49: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 57068 invoked by uid 48); 25 Feb 2020 19:49:26 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93932] PowerPC vec_extract with variable element number has code regressions for V2DI/V2DF vectors
Date: Tue, 25 Feb 2020 19: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: meissner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: meissner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-93932-4-TMGsBwfRWG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93932-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93932-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02956.txt.bz2
Content-length: 1499
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93932
Michael Meissner <meissner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |meissner at gcc dot gnu.org
--- Comment #1 from Michael Meissner <meissner at gcc dot gnu.org> ---
I've discovered that the issue is the combined insn that does variable extract
where it handles both the register case and the memory case:
(define_insn_and_split "vsx_extract_<mode>_var"
[(set (match_operand:<VS_scalar> 0 "gpc_reg_operand" "=v,wa,r")
(unspec:<VS_scalar> [(match_operand:VSX_D 1 "input_operand" "v,Q,Q")
(match_operand:DI 2 "gpc_reg_operand" "r,r,r")]
UNSPEC_VSX_EXTRACT))
(clobber (match_scratch:DI 3 "=r,&b,&b"))
(clobber (match_scratch:V2DI 4 "=&v,X,X"))]
"VECTOR_MEM_VSX_P (<MODE>mode) && TARGET_DIRECT_MOVE_64BIT"
"#"
"&& reload_completed"
[(const_int 0)]
{
rs6000_split_vec_extract_var (operands[0], operands[1], operands[2],
operands[3], operands[4]);
DONE;
})
If I split the insn into two separate patterns, one that handles only the
register, and the other that only handles memory accesses. This way the
compiler doesn't create the store and does the variable extract in the
register.
>From gcc-bugs-return-671375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 20:14:35 2020
Return-Path: <gcc-bugs-return-671375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48808 invoked by alias); 25 Feb 2020 20: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 48757 invoked by uid 48); 25 Feb 2020 20:14:31 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93905] [8 Regression] Cannot use Derived type of Base containing both enum and protected destructor
Date: Tue, 25 Feb 2020 20: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: 8.3.1
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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-93905-4-HnSQBhn3SI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93905-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02957.txt.bz2
Content-length: 609
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93905
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 #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47911
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47911&action=edit
gcc8-pr93905.patch
Untested fix that I'm going to test tonight.
>From gcc-bugs-return-671376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:00:00 2020
Return-Path: <gcc-bugs-return-671376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91495 invoked by alias); 25 Feb 2020 21:00: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 91438 invoked by uid 48); 25 Feb 2020 20:59:56 -0000
From: "kreckel at ginac dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/29186] optimzation breaks floating point exception flag reading
Date: Tue, 25 Feb 2020 21: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: 4.1.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kreckel at ginac 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-29186-4-OZmhpgjJ4u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-29186-4@http.gcc.gnu.org/bugzilla/>
References: <bug-29186-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02958.txt.bz2
Content-length: 461
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29186
--- Comment #22 from Richard B. Kreckel <kreckel at ginac dot de> ---
I can't reproduce this bug any more, with any of the optimization settings on
x86 or x86_64 going back as far as GCC 4.9.2. Delighted to see that this has
been addressed in the meantime (even without supporting that pragma.)
I suppose this bug can just be closed. I don't know about 30568. (Don't
understand why it's related at all).
>From gcc-bugs-return-671377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:00:56 2020
Return-Path: <gcc-bugs-return-671377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93428 invoked by alias); 25 Feb 2020 21:00: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 93193 invoked by uid 48); 25 Feb 2020 21:00:13 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93933] New: [concepts] redeclaration of constrained template give error
Date: Tue, 25 Feb 2020 21:00: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: nathan 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-93933-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02959.txt.bz2
Content-length: 714
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93933
Bug ID: 93933
Summary: [concepts] redeclaration of constrained template give
error
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nathan at gcc dot gnu.org
Target Milestone: ---
Created attachment 47912
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47912&action=edit
testcase
I fell over this on the modules branch, but discovered it also occurring on
trunk. We consider all TYPE_ARGUMENT_PACKS different.
I have a patch.
>From gcc-bugs-return-671378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:01:05 2020
Return-Path: <gcc-bugs-return-671378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93790 invoked by alias); 25 Feb 2020 21:00: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 93454 invoked by uid 48); 25 Feb 2020 21:00:38 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93933] [concepts] redeclaration of constrained template give error
Date: Tue, 25 Feb 2020 21: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: nathan 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-93933-4-ToJ2RbYTeN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93933-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02960.txt.bz2
Content-length: 492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93933
Nathan Sidwell <nathan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-02-25
Assignee|unassigned at gcc dot gnu.org |nathan at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-671379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:17:55 2020
Return-Path: <gcc-bugs-return-671379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3908 invoked by alias); 25 Feb 2020 21:17: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 2871 invoked by uid 55); 25 Feb 2020 21:17:32 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/93912] typo: probablity
Date: Tue, 25 Feb 2020 21: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93912-4-ECUS3VbAHk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93912-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93912-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02961.txt.bz2
Content-length: 1306
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93912
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:9c3da8cc5d01dcccfd98cda20753081414f12877
commit r10-6857-g9c3da8cc5d01dcccfd98cda20753081414f12877
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Feb 25 22:10:48 2020 +0100
typo fix: Fix probablity, becuse, sucessor and destinarion typos [PR93912]
2020-02-25 Jakub Jelinek <jakub@redhat.com>
PR other/93912
* config/sh/sh.c (expand_cbranchdi4): Fix comment typo, probablity
-> probability.
* cfghooks.c (verify_flow_info): Likewise.
* predict.c (combine_predictions_for_bb): Likewise.
* bb-reorder.c (connect_better_edge_p): Likewise. Fix comment typo,
sucessor -> successor.
(find_traces_1_round): Fix comment typo, destinarion -> destination.
* omp-expand.c (expand_oacc_for): Fix comment typo, sucessors ->
successors.
* tree-ssa-loop-ch.c (should_duplicate_loop_header_p): Fix dump
message typo, sucessors -> successors.
c/
* gimple-parser.c (c_parser_gimple_parse_bb_spec_edge_probability):
Rename last argument from probablity to probability.
>From gcc-bugs-return-671380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:28:48 2020
Return-Path: <gcc-bugs-return-671380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13119 invoked by alias); 25 Feb 2020 21: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 13083 invoked by uid 48); 25 Feb 2020 21:28:44 -0000
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93933] [concepts] redeclaration of constrained template give error
Date: Tue, 25 Feb 2020 21: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: ppalka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: nathan at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93933-4-qbI5TuuIyx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93933-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02962.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93933
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ppalka at gcc dot gnu.org
--- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Perhaps related to PR93795?
>From gcc-bugs-return-671381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:35:54 2020
Return-Path: <gcc-bugs-return-671381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118485 invoked by alias); 25 Feb 2020 21:35: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 118415 invoked by uid 48); 25 Feb 2020 21:35:49 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/70024] [5/6 Regression] libffi ABI change w/o SONAME bump
Date: Tue, 25 Feb 2020 21:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libffi
X-Bugzilla-Version: 5.3.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-70024-4-NKIAdNYtxS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70024-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70024-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02963.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70024
Florian Weimer <fw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fw at gcc dot gnu.org
--- Comment #10 from Florian Weimer <fw at gcc dot gnu.org> ---
Was this an ABI change anywhere but on Mach-O targets?
FFI_EXEC_TRAMPOLINE_TABLE is 0 on GNU/Linux, right?
>From gcc-bugs-return-671382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:41:55 2020
Return-Path: <gcc-bugs-return-671382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124052 invoked by alias); 25 Feb 2020 21: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 123978 invoked by uid 48); 25 Feb 2020 21:41:51 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93932] PowerPC vec_extract with variable element number has code regressions for V2DI/V2DF vectors
Date: Tue, 25 Feb 2020 21:41: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: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: meissner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93932-4-iLPbZIzyi0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93932-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93932-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02964.txt.bz2
Content-length: 681
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93932
--- Comment #2 from Segher Boessenkool <segher at gcc dot gnu.org> ---
So the issue is that input_operand allows too much?
Other patterns that could use such a fix are float<QHI:mode><FP_ISA3:mode>2,
floatuns<QHI:mode><FP_ISA3:mode>2, movsd_store, movsd_load,
*vsx_le_permute_<mode>, vsx_set_v1ti, vsx_extract_<mode>_var,
vsx_extract_v4sf_var, vsx_extract_<mode>_var,
*vsx_extract_<mode>_<VS_scalar>mode_var, vsx_splat_<mode>.
A few of those are probably safe, the define_expand ones for example; but
those are all uses of input_operand in an insn that isn't a movM (which
is the only place this predicate should be used).
>From gcc-bugs-return-671383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:42:48 2020
Return-Path: <gcc-bugs-return-671383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125713 invoked by alias); 25 Feb 2020 21:42: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 125654 invoked by uid 55); 25 Feb 2020 21:42:44 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92745] [8/9 Regression] Initializing array with vec4 results in compile error
Date: Tue, 25 Feb 2020 21: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: 8.3.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92745-4-zY8HjJ98W5@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: 2020-02/txt/msg02965.txt.bz2
Content-length: 2770
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92745
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:a955c8f0a0aacd9271876ddc5ca8f0ccaca18ac7
commit r8-10065-ga955c8f0a0aacd9271876ddc5ca8f0ccaca18ac7
Author: Marek Polacek <polacek@redhat.com>
Date: Fri Dec 20 23:30:04 2019 +0000
PR c++/92745 - bogus error when initializing array of vectors.
In r268428 I changed reshape_init_r in such a way that when it sees
a nested { } in a CONSTRUCTOR with missing braces, it just returns
the initializer:
+ else if (COMPOUND_LITERAL_P (stripped_init)
...
+ ++d->cur;
+ gcc_assert (!BRACE_ENCLOSED_INITIALIZER_P (stripped_init));
+ return init;
But as this test shows, that's incorrect: if TYPE is an array, we need
to proceed to reshape_init_array_1 which will iterate over the array
initializers:
6006 /* Loop until there are no more initializers. */
6007 for (index = 0;
6008 d->cur != d->end && (!sized_array_p || index <=
max_index_cst);
6009 ++index)
6010 {
and update d.cur accordingly. In other words, when reshape_init gets
{{col[0][0], col[1][0], col[2][0], col[3][0]},
{col[0][1], col[1][1], col[2][1], col[3][1]},
{col[0][2], col[1][2], col[2][2], col[3][2]},
{col[0][3], col[1][3], col[2][3], col[3][3]}}
we recurse on the first element:
{col[0][0], col[1][0], col[2][0], col[3][0]}
and we can't just move d.cur to point to
{col[0][1], col[1][1], col[2][1], col[3][1]}
and return; we need to iterate, so that d.cur ends up being properly
updated, and after all initializers have been seen, points to d.end.
Currently we skip the loop, wherefore we hit this:
6502 /* Make sure all the element of the constructor were used.
Otherwise,
6503 issue an error about exceeding initializers. */
6504 if (d.cur != d.end)
6505 {
6506 if (complain & tf_error)
6507 error ("too many initializers for %qT", type);
6508 return error_mark_node;
6509 }
gcc/cp/ChangeLog
2020-02-25 Marek Polacek <polacek@redhat.com>
PR c++/92745 - bogus error when initializing array of vectors.
* decl.c (reshape_init_r): For a nested compound literal, do
call reshape_init_{class,array,vector}.
gcc/testsuite/ChangeLog
2020-02-25 Marek Polacek <polacek@redhat.com>
Jakub Jelinek <jakub@redhat.com>
PR c++/92745
* g++.dg/cpp0x/initlist118.C: New test.
* g++.dg/cpp0x/initlist118.C: Add -Wno-psabi -w to dg-options.
>From gcc-bugs-return-671384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:42:58 2020
Return-Path: <gcc-bugs-return-671384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126430 invoked by alias); 25 Feb 2020 21:42: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 126384 invoked by uid 55); 25 Feb 2020 21:42:54 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87770] [8 Regression] ICE in type_dependent_expression_p, at cp/pt.c:25230
Date: Tue, 25 Feb 2020 21: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.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: aoliva at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87770-4-ljL1kfOdHy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87770-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87770-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02966.txt.bz2
Content-length: 1518
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87770
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:d2221c1179354ad71c4944ea0cc634803aae98f1
commit r8-10066-gd2221c1179354ad71c4944ea0cc634803aae98f1
Author: Alexandre Oliva <aoliva@redhat.com>
Date: Tue Feb 5 06:11:25 2019 +0000
c++: test partial specializations for type dependence [PR87770]
When instantiating a partial specialization of a template member
function for a full specialization of a class template, we test
whether the context of variables local to the partial specialization,
i.e., the partial specialization itself, is dependent, and this ICEs
in type_dependent_expression_p, when checking that the function type
isn't type-dependent because it is not in a type-dependent scope.
We shouldn't have got that far: the previous block in
type_dependent_expression_p catches cases in which the function itself
takes template arguments of its own, but it only did so for primary
templates, not for partial specializations. This patch fixes that.
gcc/cp/ChangeLog
2019-02-05 Alexandre Oliva <aoliva@redhat.com>
PR c++/87770
* pt.c (instantiates_primary_template_p): New.
(type_dependent_expression_p): Use it.
gcc/testsuite/ChangeLog
2019-02-05 Alexandre Oliva <aoliva@redhat.com>
PR c++/87770
* g++.dg/pr87770.C: New.
>From gcc-bugs-return-671385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:43:42 2020
Return-Path: <gcc-bugs-return-671385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127486 invoked by alias); 25 Feb 2020 21:43: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 127402 invoked by uid 48); 25 Feb 2020 21:43:37 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87770] [8 Regression] ICE in type_dependent_expression_p, at cp/pt.c:25230
Date: Tue, 25 Feb 2020 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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: aoliva at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-87770-4-96A7u1T1Iw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87770-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87770-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02967.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87770
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
CC| |jason at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #11 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:45:44 2020
Return-Path: <gcc-bugs-return-671386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129888 invoked by alias); 25 Feb 2020 21:45: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 128985 invoked by uid 48); 25 Feb 2020 21:45:28 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92745] [9 Regression] Initializing array with vec4 results in compile error
Date: Tue, 25 Feb 2020 21: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: 8.3.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc
Message-ID: <bug-92745-4-d8Ud6Exmwl@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: 2020-02/txt/msg02968.txt.bz2
Content-length: 667
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92745
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
Summary|[8/9 Regression] |[9 Regression] Initializing
|Initializing array with |array with vec4 results in
|vec4 results in compile |compile error
|error |
--- Comment #11 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4 as well.
>From gcc-bugs-return-671389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:58:13 2020
Return-Path: <gcc-bugs-return-671389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34034 invoked by alias); 25 Feb 2020 21:58: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 33113 invoked by uid 48); 25 Feb 2020 21:58:08 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93933] [concepts] redeclaration of constrained template give error
Date: Tue, 25 Feb 2020 21: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: nathan at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93933-4-7b6fhNS7dZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93933-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02971.txt.bz2
Content-length: 451
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93933
Nathan Sidwell <nathan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |plexando at protonmail dot com
--- Comment #2 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
*** Bug 93795 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-671387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:58:02 2020
Return-Path: <gcc-bugs-return-671387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32389 invoked by alias); 25 Feb 2020 21: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 32267 invoked by uid 48); 25 Feb 2020 21:57:57 -0000
From: "vajdaz at protonmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93934] New: Unnecessary fld of uninitialized float stack variable results in ub of valid C++ code
Date: Tue, 25 Feb 2020 21: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: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vajdaz at protonmail 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-93934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02969.txt.bz2
Content-length: 5041
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93934
Bug ID: 93934
Summary: Unnecessary fld of uninitialized float stack variable
results in ub of valid C++ code
Product: gcc
Version: 7.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: vajdaz at protonmail dot com
Target Milestone: ---
Valid C++ code is compiled to assembly that seems to be buggy. Below source
code and assembly output of the compiler.
Contents of source file float.cc:
extern void foo();
extern void bar();
double func(int size, double d, bool b) {
double result;
for(int i = 0; i < size; ++i) {
if (i == 0) {
foo();
if(b) result = d;
}
else {
bar();
if(b) result = 42.0;
}
}
return b && size > 0 ? result : 7.0;
}
I assume that this is valid C++ code. On C++ level there is no way to access an
uninitialized variable. The variable result is only used as a return value if
size is greater than zero, and b is true, in which case result will be
initialized before, for sure.
Create assembly:
$ g++ -m32 -O2 -fno-pic -fno-omit-frame-pointer -S float.cc
Output is:
.file "float.cc"
.text
.p2align 4,,15
.globl _Z4funcidb
.type _Z4funcidb, @function
_Z4funcidb:
.LFB0:
.cfi_startproc
pushl %ebp
.cfi_def_cfa_offset 8
.cfi_offset 5, -8
movl %esp, %ebp
.cfi_def_cfa_register 5
pushl %edi
pushl %esi
pushl %ebx
subl $44, %esp
.cfi_offset 7, -12
.cfi_offset 6, -16
.cfi_offset 3, -20
movl 8(%ebp), %ebx
movl 20(%ebp), %eax
fldl 12(%ebp)
testl %ebx, %ebx
fstpl -48(%ebp)
movl %eax, -36(%ebp)
jle .L2
movl %eax, %esi
xorl %edi, %edi
.p2align 4,,10
.p2align 3
.L5:
testl %edi, %edi
je .L16
call _Z3barv
movl %esi, %eax
testb %al, %al
je .L4
flds .LC0
fstpl -32(%ebp)
.L4:
addl $1, %edi
cmpl %edi, %ebx
jne .L5
cmpb $0, -36(%ebp)
fldl -32(%ebp)
je .L17
addl $44, %esp
popl %ebx
.cfi_remember_state
.cfi_restore 3
popl %esi
.cfi_restore 6
popl %edi
.cfi_restore 7
popl %ebp
.cfi_restore 5
.cfi_def_cfa 4, 4
ret
.p2align 4,,10
.p2align 3
.L17:
.cfi_restore_state
fstp %st(0)
.L2:
flds .LC1
addl $44, %esp
popl %ebx
.cfi_remember_state
.cfi_restore 3
popl %esi
.cfi_restore 6
popl %edi
.cfi_restore 7
popl %ebp
.cfi_restore 5
.cfi_def_cfa 4, 4
ret
.p2align 4,,10
.p2align 3
.L16:
.cfi_restore_state
call _Z3foov
fldl -48(%ebp)
movl %esi, %eax
testb %al, %al
fldl -32(%ebp)
fcmovne %st(1), %st
fstp %st(1)
fstpl -32(%ebp)
jmp .L4
.cfi_endproc
.LFE0:
.size _Z4funcidb, .-_Z4funcidb
.section .rodata.cst4,"aM",@progbits,4
.align 4
.LC0:
.long 1109917696
.align 4
.LC1:
.long 1088421888
.ident "GCC: (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0"
.section .note.GNU-stack,"",@progbits
Following things happen in the assembly code when size is 1 and b is true for
example.
* The value of size is stored into %ebx
* The value of b is stored into %eax and -36(%ebp), later in %esi
* The value of d is loaded into the fpu register stack and stored into
-48(%ebp)
We continue straight to the line with "je .L16" and jump to the label .L16. And
here comes the interesting part:
.L16:
.cfi_restore_state
call _Z3foov
fldl -48(%ebp) <-- loading value of d into fpu
movl %esi, %eax
testb %al, %al <-- testing if b is true (for fcmovne below)
fldl -32(%ebp) <-- loading uninitialized stack variable result
fcmovne %st(1), %st <-- choosing which value to put back into result
fstp %st(1)
fstpl -32(%ebp)
jmp .L4
Why we have here a combination of two fldl instructions and a fcmovne? This
causes a possible fpu exception if the value of the uninitialized variable
named result is accidentally a SNaN value. Which means, the behavior of this
code is unpredictable.
This can be reproduced with any GCC since 4.4.7, if the -march option is set to
something that supports fcmov instructions. I used GCC 7.4.0.
Is this a bug, or do I miss something?
>From gcc-bugs-return-671388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 21:58:12 2020
Return-Path: <gcc-bugs-return-671388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33885 invoked by alias); 25 Feb 2020 21:58: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 33049 invoked by uid 48); 25 Feb 2020 21:58:08 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93795] Out-of-line definition of class member template with 'requires std::invocable<T>' constraint fails to compile
Date: Tue, 25 Feb 2020 21:58: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: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan 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-93795-4-az14DP0GF2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93795-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93795-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02970.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93795
Nathan Sidwell <nathan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |nathan at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #2 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
dup of 93933, but different testcase
*** This bug has been marked as a duplicate of bug 93933 ***
>From gcc-bugs-return-671390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 22:00:28 2020
Return-Path: <gcc-bugs-return-671390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36474 invoked by alias); 25 Feb 2020 22:00: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 36213 invoked by uid 48); 25 Feb 2020 22:00:05 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/93935] New: [9/10 regression] gcc.dg/vect/bb-slp-over-widen-2.c fails starting with r262371 (r10-6856)
Date: Tue, 25 Feb 2020 22:00: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: 9.2.1
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-93935-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02972.txt.bz2
Content-length: 2971
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93935
Bug ID: 93935
Summary: [9/10 regression] gcc.dg/vect/bb-slp-over-widen-2.c
fails starting with r262371 (r10-6856)
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
git g:68f8763d57ab6e90f9d78ec0b0e6b71241676a5c, r10-6856
This is probably a similar issue on power 7 for
gcc.dg/vect/bb-slp-over-widen-2.c as for gcc.dg/vect/bb-slp-over-widen-1.c in
pr87304. r267528 was a fix for gcc.dg/vect/bb-slp-over-widen-1.c. Occurs in
gcc 9 and trunk.
Sorry I missed this.
make -k check-gcc RUNTESTFLAGS=vect.exp="gcc.dg/vect/bb-slp-over-widen-*.c"
# of expected passes 16
# of unexpected failures 2
Executing on host: /home/seurer/gcc/git/build/gcc-9-test2/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-9-test2/gcc/
/home/seurer/gcc/git/gcc-9-test2/gcc/testsuite/gcc.dg/vect/bb-slp-over-widen-2.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -maltivec -mvsx -mno-allow-movmisalign
-ftree-vectorize -fno-vect-cost-model -fno-common -O2 -fdump-tree-slp-details
-lm -o ./bb-slp-over-widen-2.exe (timeout = 300)
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-9-test2/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-9-test2/gcc/
/home/seurer/gcc/git/gcc-9-test2/gcc/testsuite/gcc.dg/vect/bb-slp-over-widen-2.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -maltivec -mvsx -mno-allow-movmisalign
-ftree-vectorize -fno-vect-cost-model -fno-common -O2 -fdump-tree-slp-details
-lm -o ./bb-slp-over-widen-2.exe
PASS: gcc.dg/vect/bb-slp-over-widen-2.c (test for excess errors)
Setting LD_LIBRARY_PATH to
:/home/seurer/gcc/git/build/gcc-9-test2/gcc::/home/seurer/gcc/git/build/gcc-9-test2/gcc:/home/seurer/gcc/git/build/gcc-9-test2/./gmp/.libs:/home/seurer/gcc/git/build/gcc-9-test2/./prev-gmp/.libs:/home/seurer/gcc/git/build/gcc-9-test2/./mpfr/src/.libs:/home/seurer/gcc/git/build/gcc-9-test2/./prev-mpfr/src/.libs:/home/seurer/gcc/git/build/gcc-9-test2/./mpc/src/.libs:/home/seurer/gcc/git/build/gcc-9-test2/./prev-mpc/src/.libs:/home/seurer/gcc/git/build/gcc-9-test2/./isl/.libs:/home/seurer/gcc/git/build/gcc-9-test2/./prev-isl/.libs
Execution timeout is: 300
spawn [open ...]
PASS: gcc.dg/vect/bb-slp-over-widen-2.c execution test
PASS: gcc.dg/vect/bb-slp-over-widen-2.c scan-tree-dump slp2 "demoting int to
signed short"
PASS: gcc.dg/vect/bb-slp-over-widen-2.c scan-tree-dump slp2 "demoting int to
unsigned short"
gcc.dg/vect/bb-slp-over-widen-2.c: pattern found 0 times
FAIL: gcc.dg/vect/bb-slp-over-widen-2.c scan-tree-dump-times slp2 "basic block
vectorized" 2
The second failure is similar.
>From gcc-bugs-return-671391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 22:14:14 2020
Return-Path: <gcc-bugs-return-671391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54676 invoked by alias); 25 Feb 2020 22:14: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 54649 invoked by uid 48); 25 Feb 2020 22:14:10 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93934] Unnecessary fld of uninitialized float stack variable results in ub of valid C++ code
Date: Tue, 25 Feb 2020 22: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: 7.4.0
X-Bugzilla-Keywords: missed-optimization
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 cf_gcctarget component
Message-ID: <bug-93934-4-X4qzE7R8jj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02973.txt.bz2
Content-length: 635
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93934
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target| |i?86-*-*
Component|c++ |target
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Looks correct on aarch64 so it might be only a i?86 issue with stack variables.
Most likely been here since x86/x87 support was added to GCC.
>From gcc-bugs-return-671392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 22:46:08 2020
Return-Path: <gcc-bugs-return-671392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104393 invoked by alias); 25 Feb 2020 22:46: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 104244 invoked by uid 48); 25 Feb 2020 22:45:48 -0000
From: "stephane.goujet at wanadoo dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93910] -Waddress-of-packed-member triggered without actual access to a member or the address of a member
Date: Tue, 25 Feb 2020 22: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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: stephane.goujet at wanadoo 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: bug_status resolution
Message-ID: <bug-93910-4-kXqFoIKdGi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93910-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93910-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02974.txt.bz2
Content-length: 2982
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93910
stephane.goujet at wanadoo dot fr changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #9 from stephane.goujet at wanadoo dot fr ---
Re-opening until some action is decided or conclusion is reached on the
following items:
1. There is a documentation problem for the attribute 'packed'. The fact that
this attribute modifies not only the 'internal' padding but also the 'external'
alignment should be clearly stated. It may be obvious to you, but for the
reader it is not, and this behaviour is not particularly expected/natural. I
made a few experiments with clang (8) and Microsoft compiler (2019), they do
not seem to change the external alignment, they align packed structs like
regular structs. GCC behaviour is a bit of an outlier, hence the need for an
explicit specification.
2. There are inconsistencies in the Warning:
2.a A packed struct declared with a "#pragma pack" does not trigger the warning
(a similar thing has apparently been reported in bug
<https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90452> 9 months ago but was
ignored), despite having the same apparent effect on the structure 'external'
alignment.
2.b A packed struct inside an array does not trigger the warning.
I could add a:
1.b #pragma pack is said to mimic MSVC behaviour, however by modifying
'external' alignment, it behaves a bit differently than my (only) experiment
with MSVC.
Example code:
---------------------------------
# 1 "inconsistent.c"
# 1 "<built-in>"
# 1 "<command-line>"
# 31 "<command-line>"
# 1 "/usr/include/stdc-predef.h" 1 3 4
# 32 "<command-line>" 2
# 1 "inconsistent.c"
struct __attribute__((packed)) S {
char a;
int b;
};
#pragma pack(push, 1)
struct S2 {
char a;
int b;
};
#pragma pack(pop)
int main(void) {
struct S s;
struct S a[10];
int *ps = (int *) &s;
int *pa0 = (int *) &a[0];
int *pa1 = (int *) &a[1];
struct S2 s2;
struct S2 a2[10];
int *ps2 = (int *) &s2;
int *pa20 = (int *) &a2[0];
int *pa21 = (int *) &a2[1];
return 0;
}
-------------------------
Result (it only warns on the case we saw previously, not on the others):
-------------------------
~/test/c/gcc9packed $LC_ALL=C gcc -Wextra inconsistent.c -o inconsistent_gcc
-save-temps
inconsistent.c: In function 'main':
inconsistent.c:17:2: warning: converting a packed 'struct S' pointer (alignment
1) to a 'int' pointer (alignment 4) may result in an unaligned pointer value
[-Waddress-of-packed-member]
17 | int *ps = (int *) &s;
| ^~~
inconsistent.c:1:32: note: defined here
1 | struct __attribute__((packed)) S {
| ^
-------------------------
(PS: thanks for having dealt with the small translation mistake.)
>From gcc-bugs-return-671393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 22:58:35 2020
Return-Path: <gcc-bugs-return-671393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120316 invoked by alias); 25 Feb 2020 22:58: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 120236 invoked by uid 48); 25 Feb 2020 22:58:28 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92721] checking ICE on attribute access redeclaration
Date: Tue, 25 Feb 2020 22: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: ice-on-valid-code, 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords component short_desc
Message-ID: <bug-92721-4-FuBvnxWUmm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02975.txt.bz2
Content-length: 727
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92721
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
Component|c++ |middle-end
Summary|ICE: canonical types differ |checking ICE on attribute
|for identical types |access redeclaration
|'int(void*, void*)' and |
|'int(void*, void*)' |
--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2020-02/msg01431.html
>From gcc-bugs-return-671394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 23:06:34 2020
Return-Path: <gcc-bugs-return-671394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2278 invoked by alias); 25 Feb 2020 23:06: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 2250 invoked by uid 48); 25 Feb 2020 23:06:29 -0000
From: "eric.niebler at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93936] New: [ranges] std::ranges::split_view<...>::_OuterIter<...>::__current() is private within this context
Date: Tue, 25 Feb 2020 23: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eric.niebler 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-93936-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02976.txt.bz2
Content-length: 1794
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93936
Bug ID: 93936
Summary: [ranges]
std::ranges::split_view<...>::_OuterIter<...>::__curre
nt() is private within this context
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: eric.niebler at gmail dot com
Target Milestone: ---
The following program fails to compile with -std=c++2a on gcc-trunk:
#include <ranges>
#include <string>
#include <vector>
#include <iterator>
#include <algorithm>
#include <iostream>
inline constexpr auto as_string = [](std::ranges::view auto rng) {
auto in = rng | std::views::common;
return std::string(in.begin(), in.end());
};
int main() {
namespace views = std::views;
std::string str = "Now is the time for all good men to come to the aid of
their county.";
auto rng = str | views::split(' ') | views::transform(as_string) |
views::common;
std::vector<std::string> words(rng.begin(), rng.end());
std::ranges::copy(words,
std::ostream_iterator<std::string>{std::cout,","});
}
The error is:
/opt/compiler-explorer/gcc-trunk-20200225/include/c++/10.0.1/ranges:2828:31:
error: 'constexpr auto& std::ranges::split_view<_Vp,
_Pattern>::_OuterIter<_Const>::__current() const [with bool _Const = true; _Vp
= std::ranges::ref_view<std::__cxx11::basic_string<char> >; _Pattern =
std::ranges::single_view<char>]' is private within this context
2828 | { return __x._M_i.__current() == __y._M_i.__current(); }
| ~~~~~~~~~~~~~~~~~~^~
Obligatory godbolt link: https://godbolt.org/z/B4tZPx
>From gcc-bugs-return-671395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 23:10:04 2020
Return-Path: <gcc-bugs-return-671395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7562 invoked by alias); 25 Feb 2020 23:10: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 7441 invoked by uid 48); 25 Feb 2020 23:09:59 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93932] PowerPC vec_extract with variable element number has code regressions for V2DI/V2DF vectors
Date: Tue, 25 Feb 2020 23:10: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: meissner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: meissner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93932-4-nZCkL1pi2D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93932-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93932-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02977.txt.bz2
Content-length: 808
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93932
--- Comment #3 from Michael Meissner <meissner at gcc dot gnu.org> ---
While I agree that in general, we should only use input_operand for moves and
define_expands, I tend to think in the short term (GCC 10) we should just fix
the case we know about. As you point out, this is used in every single place
where we fold sign/zero/float extension into a load.
In looking at gcc 8 and gcc 9, the variable extract patterns are mostly the
same, except gcc 8 uses 'ww', etc. constraints, while gcc 9/10 uses the 'isa'
attribute to eliminate the cases using power9 instructions on power8.
I don't know why only V2DI/V2DF shows it up, when V4SF/V4SI/V8HI/V16QI use the
same construct, and why -mcpu=power9 compiles it ok on trunk, but not gcc 9.
>From gcc-bugs-return-671396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Feb 25 23:18:24 2020
Return-Path: <gcc-bugs-return-671396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21187 invoked by alias); 25 Feb 2020 23:18: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 21127 invoked by uid 48); 25 Feb 2020 23:18:17 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/29186] optimzation breaks floating point exception flag reading
Date: Tue, 25 Feb 2020 23: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: 4.1.2
X-Bugzilla-Keywords:
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-29186-4-Y9Gu8lgYti@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-29186-4@http.gcc.gnu.org/bugzilla/>
References: <bug-29186-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02978.txt.bz2
Content-length: 588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29186
--- Comment #23 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Richard B. Kreckel from comment #22)
> I can't reproduce this bug any more,
I think you are just lucky, I am sure it hasn't been fixed and gcc will still
happily swap FP operations with function calls like fetestexcept. You still
need something like volatile to protect your operation, and even then the
compiler could theoretically move some unrelated FP op just before
fetestexcept, which would set more flags than the operation you wanted to test.
>From gcc-bugs-return-671397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 00:39:01 2020
Return-Path: <gcc-bugs-return-671397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85261 invoked by alias); 26 Feb 2020 00: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 85197 invoked by uid 48); 26 Feb 2020 00:38:56 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93848] missing -Warray-bounds warning for array subscript 1 is outside array bounds
Date: Wed, 26 Feb 2020 00: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: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
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:
Message-ID: <bug-93848-4-4UJmdJ3oHM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02979.txt.bz2
Content-length: 1127
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93848
--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
In
int i[4];
int (*p)[4] = &i;
bar_aux (p[1]);
p[0] points to i and p[1] to (char*)&i + sizeof (i) (which is the same as
&i[4]). The latter is a pointer just past the end of i. Evaluating
past-the-end pointers is well-defined, as is all pointer arithmetic on them,
just as long as the result is also a valid pointer to the same object (or just
past its end). The only way past-the-end pointers differ from others is that
the former cannot be dereferenced (by any means, either the * operator, or []
or ->).
In
int a[1][4];
printf("%p\n", (void *)&a[1][1]);
on the other hand, the reference to a[1][1] is undefined because a[1] is not a
reference to an element in a but rather just past the end of a, and so it can
be neither dereferenced nor used to obtain pointers other than to a or just
past it. &a[1] alone is valid (it's equivalent to (char*)&a + sizeof a) and
points just past the end of a, but &a[1][1] is equivalent to (char*)&a + sizeof
a + 1 which is not valid.
>From gcc-bugs-return-671398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 00:59:10 2020
Return-Path: <gcc-bugs-return-671398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94537 invoked by alias); 26 Feb 2020 00:59: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 94434 invoked by uid 48); 26 Feb 2020 00:59:05 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93937] New: Variable vector extract & zero extend insn can never match
Date: Wed, 26 Feb 2020 00:59: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: meissner 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-93937-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02980.txt.bz2
Content-length: 1846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93937
Bug ID: 93937
Summary: Variable vector extract & zero extend insn can never
match
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: meissner at gcc dot gnu.org
Target Milestone: ---
In looking at the variable vector extract code, the insns that attempt to merge
a zero extend with a variable extract of a vector element will never match:
(define_insn_and_split "*vsx_extract_<mode>_<VS_scalar>mode_var"
[(set (match_operand:<VS_scalar> 0 "gpc_reg_operand" "=r,r,r")
(zero_extend:<VS_scalar>
(unspec:<VSX_EXTRACT_I:VS_scalar>
[(match_operand:VSX_EXTRACT_I 1 "input_operand" "v,v,Q")
(match_operand:DI 2 "gpc_reg_operand" "r,r,r")]
UNSPEC_VSX_EXTRACT)))
(clobber (match_scratch:DI 3 "=r,r,&b"))
(clobber (match_scratch:V2DI 4 "=X,&v,X"))]
"VECTOR_MEM_VSX_P (<VSX_EXTRACT_I:MODE>mode) && TARGET_DIRECT_MOVE_64BIT"
"#"
"&& reload_completed"
[(const_int 0)]
{
machine_mode smode = <VS_scalar>mode;
rs6000_split_vec_extract_var (gen_rtx_REG (smode, REGNO (operands[0])),
operands[1], operands[2],
operands[3], operands[4]);
DONE;
}
[(set_attr "isa" "p9v,*,*")])
It will never match, because the compiler will never generate code of the form:
(set (reg:SI)
(zero_extend:SI
(unspec:SI [(reg:V4SI)
(reg:DI)] UNSPEC_VSX_EXTRACT)))
I.e. the zero_extend type should be DImode. Obviously the issue with PR
target/93932 (using input_operand) will also apply to this insn, once the modes
are fixed.
>From gcc-bugs-return-671401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 00:59:36 2020
Return-Path: <gcc-bugs-return-671401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96955 invoked by alias); 26 Feb 2020 00: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 96640 invoked by uid 48); 26 Feb 2020 00:59:32 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Wed, 26 Feb 2020 00:59: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93871-4-8tr1hGZAiP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02983.txt.bz2
Content-length: 2451
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #24 from kargl at gcc dot gnu.org ---
(In reply to kargl from comment #23)
> Created attachment 47913 [details]
> Diff that replaces handling of degree trig functions.
Fritz,
I have attached a patch that completely replaces how you handled
the various degree trig functions. This patch brings these
functions into alignment with how all other functions are handled.
The patch fixes a number of ICE issues with simplification.
Ironically, I did not include Thomas's patch that started me down
this path, so you'll want to revisit his patch. A simplify ChangeLog
follows.
* gfortran.h (GFC_ISYM_ACOSD,GFC_ISYM_ASIND, GFC_ISYM_ATAN2D,
GFC_ISYM_ATAND, GFC_ISYM_COSD, GFC_ISYM_COTAND, GFC_ISYM_SIND,
GFC_ISYM_TAND): New enum values.
* intrinsic.c (add_functions): Associate acosd, asind, atand, atan2d,
cosd, cotand, sind, and tand with its enum value, and give each
routine a simplification routine.
* intrinsic.c (add_functions): Connect cotan to gfc_simplify_cotan
(do_simplify): Remove special casing of DEC math functions.
* intrinsic.h: New prototypes for gfc_simplify_acosd,
gfc_simplify_asind, gfc_simplify_atand, gfc_simplify_cosd,
gfc_simplify_cotand, gfc_simplify_sind, gfc_simplify_tand.
Remove prototypes for deleted functions gfc_simplify_atrigd,
gfc_simplify_trigd, gfc_resolve_cotan, gfc_resolve_trigd
gfc_resolve_atrigd
* iresolve.c (is_trig_resolved, copy_replace_function_shallow,
gfc_resolve_cotan, get_radians, get_degrees, resolve_trig_call,
gfc_resolve_trigd, gfc_resolve_atrigd, gfc_resolve_atan2d): Deleted
functions.
* simplify.c (gfc_simplify_acosd, gfc_simplify_asind,
gfc_simplify_atand, gfc_simplify_atan2d, gfc_simplify_cosd,
gfc_simplify_sind, gfc_simplify_tand, gfc_simplify_cotand): New
function for, well, simplification.
* simplify.c (gfc_simplify_asinh): Fix error message.
* simplify.c (simplify_trig_call, radians_f, gfc_simplify_atrigd):
Delete function.
* trans-intrinsic.c (rad2deg, deg2rad, gfc_conv_intrinsic_atrigd,
gfc_conv_intrinsic_trigd, gfc_conv_intrinsic_cotan,
gfc_conv_intrinsic_atan2d): New function.
(gfc_conv_intrinsic_function): Use new enum values to select a new
function.
>From gcc-bugs-return-671400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 00:59:24 2020
Return-Path: <gcc-bugs-return-671400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95850 invoked by alias); 26 Feb 2020 00:59: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 95828 invoked by uid 48); 26 Feb 2020 00:59:20 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93937] Variable vector extract & zero extend insn can never match
Date: Wed, 26 Feb 2020 00: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: meissner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: meissner 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-93937-4-wSgFTGzknH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93937-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93937-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02981.txt.bz2
Content-length: 498
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93937
Michael Meissner <meissner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-02-26
Assignee|unassigned at gcc dot gnu.org |meissner at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-671399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 00:59:10 2020
Return-Path: <gcc-bugs-return-671399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94545 invoked by alias); 26 Feb 2020 00:59: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 94443 invoked by uid 48); 26 Feb 2020 00:59:05 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Wed, 26 Feb 2020 00:59: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-93871-4-HQ0jLbpNPN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02982.txt.bz2
Content-length: 258
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #23 from kargl at gcc dot gnu.org ---
Created attachment 47913
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47913&action=edit
Diff that replaces handling of degree trig functions.
>From gcc-bugs-return-671402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 01:17:27 2020
Return-Path: <gcc-bugs-return-671402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128915 invoked by alias); 26 Feb 2020 01:17: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 128878 invoked by uid 48); 26 Feb 2020 01:17:21 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93877] [9/10 Regression] [SH] webkit2gtk fails to build with "internal compiler error: in extract_constrain_insn, at recog.c:2211"
Date: Wed, 26 Feb 2020 01: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: 9.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: olegendo 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 everconfirmed
Message-ID: <bug-93877-4-T7SH6NWI5W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02984.txt.bz2
Content-length: 675
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93877
Oleg Endo <olegendo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-26
Ever confirmed|0 |1
--- Comment #9 from Oleg Endo <olegendo at gcc dot gnu.org> ---
The "movsf_ie" insn doesn't allow FP reg -> GP reg moves in its constraints,
but it allows it in its predicates "general_movdst_operand" and
"general_movsrc_operand". I will have a look and try to correct it.
>From gcc-bugs-return-671403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 01:22:52 2020
Return-Path: <gcc-bugs-return-671403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 900 invoked by alias); 26 Feb 2020 01:22: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 866 invoked by uid 55); 26 Feb 2020 01:22:48 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Wed, 26 Feb 2020 01:22: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93871-4-j1AzPyyY4I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02985.txt.bz2
Content-length: 623
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #25 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Wed, Feb 26, 2020 at 12:59:31AM +0000, kargl at gcc dot gnu.org wrote:
>
> * trans-intrinsic.c (rad2deg, deg2rad, gfc_conv_intrinsic_atrigd,
> gfc_conv_intrinsic_trigd, gfc_conv_intrinsic_cotan,
> gfc_conv_intrinsic_atan2d): New function.
> (gfc_conv_intrinsic_function): Use new enum values to select a new
> function.
>
Looks like gfc_conv_intrinsic_cotan isn't handling complex
as I expected. Need to look at this a bit more closely.
>From gcc-bugs-return-671404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 01:26:10 2020
Return-Path: <gcc-bugs-return-671404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5258 invoked by alias); 26 Feb 2020 01:26: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 5137 invoked by uid 48); 26 Feb 2020 01:26:03 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55212] [SH] Switch to LRA
Date: Wed, 26 Feb 2020 01: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: olegendo 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-55212-4-6YI1LbpSuv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55212-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55212-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02986.txt.bz2
Content-length: 1223
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #121 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to John Paul Adrian Glaubitz from comment #120)
>
> That's a huge task which is why I prefer fixing issues on the fly.
I thought this is almost fully automated?
You can apply this patch to GCC to enable LRA by default for SH
--- sh.opt.orig 2019-03-04 10:09:09.244521000 +0900
+++ sh.opt 2020-02-26 10:19:55.414340269 +0900
@@ -299,5 +299,5 @@
Enable the use of the fsrra instruction.
mlra
-Target Report Var(sh_lra_flag) Init(0) Save
+Target Report Var(sh_lra_flag) Init(1) Save
Use LRA instead of reload (transitional).
Then let it rebuild everything.
>
> We are going to switch over anyway with GCC-12 or GCC-13, so I'm not sure
> what we are gaining if we continue to wait.
I don't get it. You want to enable LRA by default for your distro, but you
don't want to rebuild all the packages with that modification? It's like ..
shipping a distro with a new compiler, which potentially can't compile the
distro packages (correctly), so instead we secretly use an older compiler to
build the packages .... ? Is that normal practice? Sorry, sounds like a mess
to me.
>From gcc-bugs-return-671405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 01:54:51 2020
Return-Path: <gcc-bugs-return-671405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64957 invoked by alias); 26 Feb 2020 01: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 64930 invoked by uid 48); 26 Feb 2020 01:54:46 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93938] New: ICE in validate, at analyzer/region-model.cc:231
Date: Wed, 26 Feb 2020 01:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
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: dmalcolm 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-93938-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02987.txt.bz2
Content-length: 3226
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93938
Bug ID: 93938
Summary: ICE in validate, at analyzer/region-model.cc:231
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
gcc-10.0.1-alpha20200223 snapshot (g:3133bed5d0327e8a9cd0a601b7ecdb9de4fc825d)
ICEs when compiling gcc/testsuite/gcc.dg/pr70022.c w/ -O1 -fanalyzer:
% gcc-10.0.1 -O1 -fanalyzer -c gcc/testsuite/gcc.dg/pr70022.c
during IPA pass: analyzer
gcc/testsuite/gcc.dg/pr70022.c: In function 'foo':
gcc/testsuite/gcc.dg/pr70022.c:9:11: internal compiler error: in validate, at
analyzer/region-model.cc:231
9 | return v[~0UL];
| ~^~~~~~
0x71c9d4 ana::region_id::validate(ana::region_model const&) const
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/region-model.cc:231
0x71cca0 ana::region_id::validate(ana::region_model const&) const
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/region-model.cc:201
0x71cca0 ana::region::validate(ana::region_model const*) const
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/region-model.cc:1368
0x11023fe ana::region_model::validate() const
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/region-model.cc:3712
0x1106b3f ana::region_model::purge_unused_svalues(ana::purge_stats*,
ana::region_model_context*, ana::svalue_id*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/region-model.cc:6261
0x10fb236 ana::program_state::prune_for_point(ana::exploded_graph&,
ana::program_point const&, ana::state_change*) const
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/program-state.cc:923
0x10e7dca ana::exploded_graph::get_or_create_node(ana::program_point const&,
ana::program_state const&, ana::state_change*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/engine.cc:1885
0x10eadf2 ana::exploded_graph::process_node(ana::exploded_node*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/engine.cc:2509
0x10eb5ca ana::exploded_graph::process_worklist()
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/engine.cc:2310
0x10ebcf9 ana::impl_run_checkers(ana::logger*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/engine.cc:3670
0x10ec79c ana::run_checkers()
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/engine.cc:3727
0x10e1ef8 execute
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/analyzer-pass.cc:84
>From gcc-bugs-return-671406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 02:23:58 2020
Return-Path: <gcc-bugs-return-671406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48288 invoked by alias); 26 Feb 2020 02:23: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 48240 invoked by uid 48); 26 Feb 2020 02:23:53 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93806] Wrong optimization: instability of floating-point results with -funsafe-math-optimizations leads to nonsense
Date: Wed, 26 Feb 2020 02: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vincent-gcc at vinc17 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:
Message-ID: <bug-93806-4-80zroKTNqV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93806-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93806-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02988.txt.bz2
Content-length: 1658
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93806
--- Comment #33 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
I couldn't find a failing test with FP contraction, but this seems to be
because GCC doesn't optimize as much as it could. Still, the following example
could be interesting in the future or as a non-regression test:
#include <stdio.h>
#define A 0x0.ffffffffffffp25
#define C -0x1.p50
int main (void)
{
volatile double a = A;
double b = a, c = C;
int i;
#if 0
double x = b * b;
printf ("%a\n", x);
#endif
// if (b == A && c == C)
{
i = b * b + c;
printf ("%d\n", i);
if (b == A && c == C)
{
// i = b * b + c;
printf ("%d\n", i == -7);
}
}
return 0;
}
By "GCC doesn't optimize as much as it could", I mean that the comparison with
-7 is generated, even though the result of this comparison is known at compile
time. Note that this is shown by the fact that uncommenting the second "i = b *
b + c;" does not change anything: a comparison with -7 is still generated.
With contraction enabled, one currently gets:
-7
1
(which is correct). If one uncomments the first "if (b == A && c == C)", one
gets:
-8
0
(still correct) showing that contraction is disabled at compile time.
Changing the "#if 0" to "#if 1" allows one to avoid contraction at run time.
Such a change can be useful if the rule at compile time changes in the future,
say: contraction is not used at run time, but at compile time, the optimization
bug might have the effect to re-evaluate i with contraction, yielding
inconsistent output.
>From gcc-bugs-return-671407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 02:53:38 2020
Return-Path: <gcc-bugs-return-671407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102323 invoked by alias); 26 Feb 2020 02: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 102293 invoked by uid 48); 26 Feb 2020 02:53:28 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93939] New: missing optimization for floating-point expression converted to integer whose result is known at compile time
Date: Wed, 26 Feb 2020 02:53: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: 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93939-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02989.txt.bz2
Content-length: 1319
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93939
Bug ID: 93939
Summary: missing optimization for floating-point expression
converted to integer whose result is known at compile
time
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: vincent-gcc at vinc17 dot net
Target Milestone: ---
Consider the following example.
#include <stdio.h>
typedef double T;
int main (void)
{
volatile T a = 8;
T b = a;
int i;
i = 3 * b;
printf ("%d\n", (int) i);
if (b == 8)
{
i = 3 * b;
printf ("%d\n", i == 24);
}
return 0;
}
Even if one compiles it with -O3, a comparison instruction for i == 24 is
generated, while its result 1 is known at compile time.
If I change T to int, or change the type of i to double, or comment out the
first printf (so that the first i is not used), then the i == 24 is optimized
as expected.
Tested under Debian/unstable / x86_64 with:
gcc-10 (Debian 10-20200222-1) 10.0.1 20200222 (experimental) [master revision
01af7e0a0c2:487fe13f218:e99b18cf7101f205bfdd9f0f29ed51caaec52779]
>From gcc-bugs-return-671408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 03:25:42 2020
Return-Path: <gcc-bugs-return-671408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108538 invoked by alias); 26 Feb 2020 03:25: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 108474 invoked by uid 48); 26 Feb 2020 03:25:37 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93940] New: crazy codegen bug on Og with builtin_constant_p, coverage, and pthread
Date: Wed, 26 Feb 2020 03: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: 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-93940-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02990.txt.bz2
Content-length: 2723
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93940
Bug ID: 93940
Summary: crazy codegen bug on Og with builtin_constant_p,
coverage, and pthread
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: ---
This holds for gcc 8.x, 9.x, and trunk. The following program (thanks,
creduce):
using uint16_t = unsigned short;
struct a {
uint16_t b = 0;
};
struct c {
short d;
};
class e {
public:
void f();
void init_session(c);
};
#ifdef ADD_CONSTEXPR
#define CONSTEXPR constexpr
#else
#define CONSTEXPR
#endif
auto htons = [](uint16_t s) {
if CONSTEXPR (__builtin_constant_p(s)) {
return uint16_t(uint16_t(s >> 8) | uint16_t(s << 8));
} else {
return uint16_t(uint16_t(s >> 8) | uint16_t(s << 8));
}
};
struct g {
e h;
void i(a k) {
h.f();
auto j = c();
j.d = htons(k.b);
h.init_session(j);
}
};
void test() {
g().i({});
}
The htons lambda is mimicking the htons macro, which leads with the
__builtin_constant_p check before doing either a different builtin or direct
asm. In this case, the __builtin_constant_p appears to be significant but the
rest not so much.
When compiling the above with -std=c++17 -Og -pthread --coverage, the generated
asm for test() is:
test():
sub rsp, 24
lock add QWORD PTR __gcov0.test()[rip], 1
lock add QWORD PTR __gcov0._ZN1g1iE1a[rip], 1
lea rdi, [rsp+15]
call e::f()
That's it. It only calls f(), there is no call to init_session().
On the other hand, when compiling the above with -std=c++17 -Og -pthread
--coverage -DADD_CONSTEXPR, the generated asm for test() is:
test():
sub rsp, 24
lock add QWORD PTR __gcov0.test()[rip], 1
lock add QWORD PTR __gcov0._ZN1g1iE1a[rip], 1
lea rdi, [rsp+15]
call e::f()
lock add QWORD PTR __gcov0._ZN1g1iE1a[rip+8], 1
mov esi, 0
lea rdi, [rsp+15]
call e::init_session(c)
lock add QWORD PTR __gcov0._ZN1g1iE1a[rip+16], 1
lock add QWORD PTR __gcov0.test()[rip+8], 1
add rsp, 24
ret
It seems that this whole combination of flags (-Og, pthread, coverage) is
significant, as is the fact that htons is a lambda and not a function, as are
all sorts of other things. I have no idea.
Link to compiler explorer: https://godbolt.org/z/6pgLF_
>From gcc-bugs-return-671409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 03:28:56 2020
Return-Path: <gcc-bugs-return-671409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117349 invoked by alias); 26 Feb 2020 03:28: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 117306 invoked by uid 48); 26 Feb 2020 03:28:52 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93940] crazy codegen bug on Og with builtin_constant_p, coverage, and pthread
Date: Wed, 26 Feb 2020 03: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: 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:
Message-ID: <bug-93940-4-kLZw4MjKAv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02991.txt.bz2
Content-length: 173
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93940
--- Comment #1 from Barry Revzin <barry.revzin at gmail dot com> ---
gcc 7.x has the same behavior. gcc 6.x work fine.
>From gcc-bugs-return-671410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:23:37 2020
Return-Path: <gcc-bugs-return-671410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127749 invoked by alias); 26 Feb 2020 04:23: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 127465 invoked by uid 55); 26 Feb 2020 04:23:29 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88394] [8 Regression] g++ ICE (Segmentation fault) in insert_capture_proxy
Date: Wed, 26 Feb 2020 04:23: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.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88394-4-JoyLgkbiFc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88394-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88394-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02992.txt.bz2
Content-length: 861
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88394
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:bf2fe5d49627ca757123f4425a029bd92c50fc05
commit r8-10068-gbf2fe5d49627ca757123f4425a029bd92c50fc05
Author: Jason Merrill <jason@redhat.com>
Date: Tue Feb 25 21:29:03 2020 -0500
PR c++/88394 - ICE with VLA init-capture.
We mostly use is_normal_capture_proxy to decide whether or not to use
DECL_CAPTURED_VARIABLE; we could just check whether it's set. VLA capture
is still mostly broken, but this fixes this ICE.
gcc/cp/ChangeLog
2020-02-25 Jason Merrill <jason@redhat.com>
PR c++/88394 - ICE with VLA init-capture.
* lambda.c (is_normal_capture_proxy): Check DECL_CAPTURED_VARIABLE.
>From gcc-bugs-return-671411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:23:40 2020
Return-Path: <gcc-bugs-return-671411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128224 invoked by alias); 26 Feb 2020 04:23: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 127719 invoked by uid 55); 26 Feb 2020 04:23:34 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87480] [8 Regression] SFINAE constructor not matched, only in templated function
Date: Wed, 26 Feb 2020 04:23: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: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87480-4-2zIeJJ3BkA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87480-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87480-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02993.txt.bz2
Content-length: 1191
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87480
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:2dcdcda91921b512b978f7223c530352fd61b91b
commit r8-10069-g2dcdcda91921b512b978f7223c530352fd61b91b
Author: Jason Merrill <jason@redhat.com>
Date: Tue Feb 25 21:29:03 2020 -0500
PR c++/87480 - decltype of member access in default template arg
The issue here is that declval<T>().d is considered instantiation-dependent
within a template, as the access to 'd' might depend on the particular
specialization. But when we're deducing template arguments for a call, we
know that the call and the arguments are non-dependent, so we can do the
substitution as though we aren't in a template. Which strictly speaking we
aren't, since the default argument is considered a separate definition.
gcc/cp/ChangeLog
2020-02-25 Jason Merrill <jason@redhat.com>
PR c++/87480 - decltype of member access in default template arg
* pt.c (type_unification_real): Accept a dependent result in
template context.
>From gcc-bugs-return-671417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:25:02 2020
Return-Path: <gcc-bugs-return-671417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130891 invoked by alias); 26 Feb 2020 04:24: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 130607 invoked by uid 55); 26 Feb 2020 04:24:08 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86747] [8 Regression] rejects-valid with redundant friend declaration
Date: Wed, 26 Feb 2020 04: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.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: aoliva at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86747-4-cvkamVHjC1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02996.txt.bz2
Content-length: 1493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86747
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:3d99aab56d7237bb8260653ed07ca8b182fbf975
commit r8-10073-g3d99aab56d7237bb8260653ed07ca8b182fbf975
Author: Alexandre Oliva <aoliva@redhat.com>
Date: Tue Feb 25 21:29:03 2020 -0500
c++: tsubst friend tpl ctxt before looking it up for dupes [PR86747]
When a member template is redeclared as a friend, we enter the context
of the member before looking it up, and then we check that the decls
are compatible. However, when the member template references template
types of the enclosing context, say an enclosing template class, the
compare fails because the friend decl is already tsubsted, whereas the
looked up name isn't.
The problem is that the enclosing context is taken from the friend
declaration before tsubsting it, so we look up in the context of the
generic template instead of that of the tsubsted one we're
specializing. The solution is to tsubst the enclosing context when
it's a non-namespace scope.
gcc/cp/ChangeLog
2020-02-25 Alexandre Oliva <aoliva@redhat.com>
PR c++/86747
* pt.c (tsubst_friend_class): Enter tsubsted class context.
gcc/testsuite/ChangeLog
2020-02-25 Alexandre Oliva <aoliva@redhat.com>
PR c++/86747
* g++.dg/pr86747.C: New.
>From gcc-bugs-return-671415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:24:58 2020
Return-Path: <gcc-bugs-return-671415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130639 invoked by alias); 26 Feb 2020 04:24: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 129994 invoked by uid 55); 26 Feb 2020 04:23:55 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87327] [8 Regression] Calling member functions on captured constexpr variables "is not a constant expression"
Date: Wed, 26 Feb 2020 04: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.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87327-4-Zz6FwloX1J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87327-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87327-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02999.txt.bz2
Content-length: 1123
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87327
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:6470e8caa2bd331fb6e21524d6c14662531cfa9b
commit r8-10072-g6470e8caa2bd331fb6e21524d6c14662531cfa9b
Author: Jason Merrill <jason@redhat.com>
Date: Tue Feb 25 21:29:03 2020 -0500
PR c++/86429 - constexpr variable in lambda.
When we refer to a captured variable from a constant-expression context
inside a lambda, the closure (like any function parameter) is not constant
because we aren't in a call, so we don't have an argument. So the capture
is non-constant. But if the captured variable is constant, we might be
able
to use it directly in constexpr evaluation.
gcc/cp/ChangeLog
2020-02-25 Jason Merrill <jason@redhat.com>
PR c++/86429 - constexpr variable in lambda.
PR c++/82643
PR c++/87327
* constexpr.c (cxx_eval_constant_expression): In a lambda function,
try evaluating the captured variable directly.
>From gcc-bugs-return-671413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:23:51 2020
Return-Path: <gcc-bugs-return-671413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129346 invoked by alias); 26 Feb 2020 04:23: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 128824 invoked by uid 55); 26 Feb 2020 04:23:45 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87748] [8 Regression] G++-8 treats SFINAE as error
Date: Wed, 26 Feb 2020 04: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.1.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87748-4-HfhQdhjfmQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87748-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87748-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02998.txt.bz2
Content-length: 1101
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87748
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:ac5e28911abdfb8d9bf6bea980223e199bbcf28d
commit r8-10070-gac5e28911abdfb8d9bf6bea980223e199bbcf28d
Author: Jason Merrill <jason@redhat.com>
Date: Tue Feb 25 21:29:03 2020 -0500
PR c++/87748 - substitution failure error with decltype.
This issue is similar to PR 87480; in both cases we were doing
non-dependent
substitution with processing_template_decl set, leading to member access
expressions seeming still instantiation-dependent, and therefore decltype
not being simplified to its actual type. And as in that PR, the fix is to
clear processing_template_decl while substituting a default template
argument.
gcc/cp/ChangeLog
2020-02-25 Jason Merrill <jason@redhat.com>
PR c++/87748 - substitution failure error with decltype.
* pt.c (most_specialized_partial_spec): Clear
processing_template_decl.
>From gcc-bugs-return-671412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:23:49 2020
Return-Path: <gcc-bugs-return-671412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129113 invoked by alias); 26 Feb 2020 04:23: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 128464 invoked by uid 55); 26 Feb 2020 04:23:42 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87480] [8 Regression] SFINAE constructor not matched, only in templated function
Date: Wed, 26 Feb 2020 04: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87480-4-XWHc7AXULW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87480-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87480-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02995.txt.bz2
Content-length: 1101
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87480
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:ac5e28911abdfb8d9bf6bea980223e199bbcf28d
commit r8-10070-gac5e28911abdfb8d9bf6bea980223e199bbcf28d
Author: Jason Merrill <jason@redhat.com>
Date: Tue Feb 25 21:29:03 2020 -0500
PR c++/87748 - substitution failure error with decltype.
This issue is similar to PR 87480; in both cases we were doing
non-dependent
substitution with processing_template_decl set, leading to member access
expressions seeming still instantiation-dependent, and therefore decltype
not being simplified to its actual type. And as in that PR, the fix is to
clear processing_template_decl while substituting a default template
argument.
gcc/cp/ChangeLog
2020-02-25 Jason Merrill <jason@redhat.com>
PR c++/87748 - substitution failure error with decltype.
* pt.c (most_specialized_partial_spec): Clear
processing_template_decl.
>From gcc-bugs-return-671416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:25:01 2020
Return-Path: <gcc-bugs-return-671416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130719 invoked by alias); 26 Feb 2020 04: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 130100 invoked by uid 55); 26 Feb 2020 04:23:56 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82643] lambda capture breaks constexpr-ness of non-static const constexpr member call on non-constexpr value/variable
Date: Wed, 26 Feb 2020 04: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: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82643-4-I51VRFmqMa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82643-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82643-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02997.txt.bz2
Content-length: 1123
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82643
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:6470e8caa2bd331fb6e21524d6c14662531cfa9b
commit r8-10072-g6470e8caa2bd331fb6e21524d6c14662531cfa9b
Author: Jason Merrill <jason@redhat.com>
Date: Tue Feb 25 21:29:03 2020 -0500
PR c++/86429 - constexpr variable in lambda.
When we refer to a captured variable from a constant-expression context
inside a lambda, the closure (like any function parameter) is not constant
because we aren't in a call, so we don't have an argument. So the capture
is non-constant. But if the captured variable is constant, we might be
able
to use it directly in constexpr evaluation.
gcc/cp/ChangeLog
2020-02-25 Jason Merrill <jason@redhat.com>
PR c++/86429 - constexpr variable in lambda.
PR c++/82643
PR c++/87327
* constexpr.c (cxx_eval_constant_expression): In a lambda function,
try evaluating the captured variable directly.
>From gcc-bugs-return-671414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:24:11 2020
Return-Path: <gcc-bugs-return-671414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130592 invoked by alias); 26 Feb 2020 04:24: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 129858 invoked by uid 55); 26 Feb 2020 04:23:54 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86429] [8 Regression] lambda capture breaks constexpr-ness
Date: Wed, 26 Feb 2020 04: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86429-4-fpNvRx1XyF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86429-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86429-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg02994.txt.bz2
Content-length: 1123
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86429
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:6470e8caa2bd331fb6e21524d6c14662531cfa9b
commit r8-10072-g6470e8caa2bd331fb6e21524d6c14662531cfa9b
Author: Jason Merrill <jason@redhat.com>
Date: Tue Feb 25 21:29:03 2020 -0500
PR c++/86429 - constexpr variable in lambda.
When we refer to a captured variable from a constant-expression context
inside a lambda, the closure (like any function parameter) is not constant
because we aren't in a call, so we don't have an argument. So the capture
is non-constant. But if the captured variable is constant, we might be
able
to use it directly in constexpr evaluation.
gcc/cp/ChangeLog
2020-02-25 Jason Merrill <jason@redhat.com>
PR c++/86429 - constexpr variable in lambda.
PR c++/82643
PR c++/87327
* constexpr.c (cxx_eval_constant_expression): In a lambda function,
try evaluating the captured variable directly.
>From gcc-bugs-return-671418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:26:04 2020
Return-Path: <gcc-bugs-return-671418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5363 invoked by alias); 26 Feb 2020 04:25: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 4669 invoked by uid 48); 26 Feb 2020 04:25:53 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93940] crazy codegen bug on Og with builtin_constant_p, coverage, and pthread
Date: Wed, 26 Feb 2020 04:25: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: wrong-code
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:
Message-ID: <bug-93940-4-3EbxQH7j9B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03000.txt.bz2
Content-length: 175
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93940
--- Comment #2 from Barry Revzin <barry.revzin at gmail dot com> ---
Slightly more reduced: https://godbolt.org/z/5R9A5g
>From gcc-bugs-return-671419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:31:41 2020
Return-Path: <gcc-bugs-return-671419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48601 invoked by alias); 26 Feb 2020 04:31: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 48444 invoked by uid 48); 26 Feb 2020 04:30:54 -0000
From: "qrzhang at gatech dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93941] New: gcc generates wrong debug information at -O2
Date: Wed, 26 Feb 2020 04:31: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: qrzhang at gatech dot 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93941-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03001.txt.bz2
Content-length: 1342
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93941
Bug ID: 93941
Summary: gcc generates wrong debug information at -O2
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: qrzhang at gatech dot edu
Target Milestone: ---
It appears to be a recent regression.
My bisect points to g:82e8e335f917b9ce40801838c (needs double check).
$ gcc-trunk -v
gcc version 10.0.1 20200225 (experimental) [master revision
2473c81cb2d:31b6c240eeb:81c833b311b16cfd87a947374d5ffbbd48facd03] (GCC)
## correct output
$ gcc abc.c ; ./a.out
10
## wrong value (i=1) at -O2
$ gcc-trunk -g -O2 abc.c
$ gdb -x cmds -batch a.out
Breakpoint 1 at 0x400451: file abc.c, line 15.
Breakpoint 1, main () at abc.c:15
15 printf("%d\n", i);
$1 = 1
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 2788) killed]
$ cat abc.c
volatile int a;
char b[10][10][1];
int c;
int main() {
int i, d;
i = 0;
for (; i < 10; i++) {
c = 0;
for (; c < 10; c++) {
d = 0;
for (; d < 1; d++)
a = b[i][c][d];
}
}
printf("%d\n", i);
}
$ cat cmds
b abc.c:15
r
p i
kill
q
>From gcc-bugs-return-671420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:31:49 2020
Return-Path: <gcc-bugs-return-671420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49696 invoked by alias); 26 Feb 2020 04:31: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 49091 invoked by uid 48); 26 Feb 2020 04:31:40 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93940] crazy codegen bug on Og with builtin_constant_p, coverage, and pthread
Date: Wed, 26 Feb 2020 04: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: wrong-code
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-93940-4-OCsT2N8ZRV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03002.txt.bz2
Content-length: 451
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93940
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
j.d = 0;
__builtin_unreachable ();
Considering void g::i(a)/4 with 31 size
to be inlined into void test()/5 in t6777.cc:40
Estimated badness is -1.161290, frequency 1.00.
Introduced new external node (void __builtin_unreachable()/23).
New minimal size reached: 40
node context cache: 1 hits, 0 misses, 1 initializations
>From gcc-bugs-return-671421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:36:25 2020
Return-Path: <gcc-bugs-return-671421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59447 invoked by alias); 26 Feb 2020 04:36: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 59413 invoked by uid 48); 26 Feb 2020 04:36:20 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93940] [8/9/10 Regression] crazy codegen bug on Og with builtin_constant_p, coverage, and pthread
Date: Wed, 26 Feb 2020 04:36: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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 component target_milestone short_desc everconfirmed
Message-ID: <bug-93940-4-w8Y69xwQrN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03003.txt.bz2
Content-length: 1653
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93940
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-26
CC| |marxin at gcc dot gnu.org
Component|middle-end |ipa
Target Milestone|--- |8.4
Summary|crazy codegen bug on Og |[8/9/10 Regression] crazy
|with builtin_constant_p, |codegen bug on Og with
|coverage, and pthread |builtin_constant_p,
| |coverage, and pthread
Ever confirmed|0 |1
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Take:
using uint16_t = unsigned short;
struct a {
uint16_t b = 0;
};
struct c {
short d;
};
class e {
public:
void f();
void init_session(c);
};
auto htons = [](uint16_t s) {
if (__builtin_constant_p(s)) {
return uint16_t(uint16_t(s >> 8) | uint16_t(s << 8));
}
return uint16_t(uint16_t(s >> 8) | uint16_t(s << 8));
};
struct g {
e h;
void i(a k) {
h.f();
auto j = c();
j.d = htons(k.b);
h.init_session(j);
}
};
void test() {
g().i({});
}
---- CUT ----
This is to remove __builtin_unreachable being emitted from the front-end.
__builtin_unreachable is only added by the inliner.
I have not looked into why though.
>From gcc-bugs-return-671423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:55:12 2020
Return-Path: <gcc-bugs-return-671423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110557 invoked by alias); 26 Feb 2020 04:55: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 110037 invoked by uid 55); 26 Feb 2020 04:55:05 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87685] [8 Regression] Calling a static method from inside a generic lambda requires to capture 'this'
Date: Wed, 26 Feb 2020 04: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: 8.1.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87685-4-BbyRxgDh1S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87685-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87685-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03005.txt.bz2
Content-length: 1001
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87685
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:b6136084ea86ab0d3fac54be83e50817a3db74a9
commit r8-10075-gb6136084ea86ab0d3fac54be83e50817a3db74a9
Author: Jason Merrill <jason@redhat.com>
Date: Tue Feb 25 13:37:18 2020 -0500
PR c++/87685 - generic lambda 'this' capture error.
The standard says that in a generic lambda we should speculatively capture
'this' if we see a call to an overload set that contains a non-static
member
function, but it seems wrong to reject the program if we can't capture,
since it might not actually be needed.
gcc/cp/ChangeLog
2020-02-25 Jason Merrill <jason@redhat.com>
PR c++/87685 - generic lambda 'this' capture error.
* lambda.c (lambda_expr_this_capture): Change add_capture_p to int.
(maybe_generic_this_capture): Pass -1.
>From gcc-bugs-return-671422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:55:05 2020
Return-Path: <gcc-bugs-return-671422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110029 invoked by alias); 26 Feb 2020 04:55: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 109732 invoked by uid 55); 26 Feb 2020 04:55:00 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87554] [8 Regression] internal compiler error: in record_reference, at cgraphbuild.c:64
Date: Wed, 26 Feb 2020 04: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: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87554-4-rOaxow6BuJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87554-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87554-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03004.txt.bz2
Content-length: 898
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87554
--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:a57528b33be33d4428ac62901d04cf39807d624e
commit r8-10074-ga57528b33be33d4428ac62901d04cf39807d624e
Author: Jason Merrill <jason@redhat.com>
Date: Tue Feb 25 13:37:18 2020 -0500
PR c++/87554 - ICE with extern template and reference member.
The removed code ended up setting DECL_INITIAL to the INIT_EXPR returned by
split_nonconstant_init, which makes no sense. This code was added back in
1996, so any rationale is long lost.
gcc/cp/ChangeLog
2020-02-25 Jason Merrill <jason@redhat.com>
PR c++/87554 - ICE with extern template and reference member.
* decl.c (cp_finish_decl): Don't set DECL_INITIAL of external vars.
>From gcc-bugs-return-671425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:55:25 2020
Return-Path: <gcc-bugs-return-671425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111729 invoked by alias); 26 Feb 2020 04:55: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 111408 invoked by uid 55); 26 Feb 2020 04:55:19 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89831] [8 Regression] passing 'const ...' as 'this' argument discards qualifiers
Date: Wed, 26 Feb 2020 04: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.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89831-4-42932FMPFt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03007.txt.bz2
Content-length: 963
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89831
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:2b6565dd2d07d3f2f706795f800d0cc2ff8f2f68
commit r8-10077-g2b6565dd2d07d3f2f706795f800d0cc2ff8f2f68
Author: Jason Merrill <jason@redhat.com>
Date: Tue Feb 25 13:37:18 2020 -0500
PR c++/89831 - error with qualified-id in const member function.
Since the fix for 15272 we were remembering the wrong function to use at
instantiation time, because the type of the SCOPE_REF didn't reflect the
cv-quals of 'this'. Conveniently, we can fix this by simplifying the code.
gcc/cp/ChangeLog
2020-02-25 Jason Merrill <jason@redhat.com>
PR c++/89831 - error with qualified-id in const member function.
* semantics.c (finish_non_static_data_member): Use object cv-quals
in scoped case, too.
>From gcc-bugs-return-671424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 04:55:22 2020
Return-Path: <gcc-bugs-return-671424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111473 invoked by alias); 26 Feb 2020 04:55: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 111092 invoked by uid 55); 26 Feb 2020 04:55:15 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88380] [8 Regression] Sequence of not-explicitly initialised, initialised, variable length generates no initialiser
Date: Wed, 26 Feb 2020 04: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.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88380-4-4cnhU8oxMv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88380-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88380-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03006.txt.bz2
Content-length: 1000
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88380
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:b9bfe25d3a7f925754df3a557e3b1743d21d0c4d
commit r8-10076-gb9bfe25d3a7f925754df3a557e3b1743d21d0c4d
Author: Jason Merrill <jason@redhat.com>
Date: Tue Feb 25 13:37:18 2020 -0500
PR c++/88380 - wrong-code with flexible array and NSDMI.
Here 'skipped' was set to -1 to force an explicit initializer for 'uninit'
before the initializer for 'initialized', and so we also tried to emit an
explicit initializer for the flexible array, for which build_zero_init
returns error_mark_node. We should ignore flexarrays even when
skipped < 0.
gcc/cp/ChangeLog
2020-02-25 Jason Merrill <jason@redhat.com>
PR c++/88380 - wrong-code with flexible array and NSDMI.
* typeck2.c (process_init_constructor_record): Skip flexarrays.
>From gcc-bugs-return-671426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 05:01:53 2020
Return-Path: <gcc-bugs-return-671426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123258 invoked by alias); 26 Feb 2020 05: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 121814 invoked by uid 48); 26 Feb 2020 05:01:38 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93940] [8/9/10 Regression] crazy codegen bug on Og with builtin_constant_p, coverage, and pthread
Date: Wed, 26 Feb 2020 05:01: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-93940-4-lYXBkOR0Lr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03008.txt.bz2
Content-length: 226
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93940
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
__atomic_fetch_add_8 (&__gcov0._ZN1g1iE1a[2], 1, 0);
I wonder what the type of __gcov0._ZN1g1iE1a is.
>From gcc-bugs-return-671427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 05:38:10 2020
Return-Path: <gcc-bugs-return-671427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84745 invoked by alias); 26 Feb 2020 05:37: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 84547 invoked by uid 55); 26 Feb 2020 05:37:29 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90546] [9/10 Regression] Incorrect template argument deduction for conversion functions
Date: Wed, 26 Feb 2020 05: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.1.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90546-4-TBnzGP1Dod@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90546-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90546-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03009.txt.bz2
Content-length: 1161
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90546
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:c93117eea148326a718ae1e413bc85f4fa257d8f
commit r8-10079-gc93117eea148326a718ae1e413bc85f4fa257d8f
Author: Jason Merrill <jason@redhat.com>
Date: Wed Feb 26 00:33:52 2020 -0500
c++: Allow template rvalue-ref conv to bind to lvalue ref.
When I implemented the [over.match.ref] rule that a reference conversion
function needs to match l/rvalue of the target reference type it changed
our
handling of this testcase. It seems to me that our current behavior is
what
the standard says, but it doesn't seem desirable, and all the other
compilers have our old behavior. So let's limit the change to
non-templates
until there's some clarification from the committee.
gcc/cp/ChangeLog
2020-02-26 Jason Merrill <jason@redhat.com>
PR c++/90546
* call.c (build_user_type_conversion_1): Allow a template conversion
returning an rvalue reference to bind directly to an lvalue.
>From gcc-bugs-return-671428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 05:38:16 2020
Return-Path: <gcc-bugs-return-671428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85252 invoked by alias); 26 Feb 2020 05:38: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 84815 invoked by uid 55); 26 Feb 2020 05:37:50 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90998] [9 Regression] ICE (segfault) in gcc/cp/call.c compare_ics() with -std=c++17
Date: Wed, 26 Feb 2020 05: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: 9.1.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
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-90998-4-JVLvqGbccE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90998-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90998-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03013.txt.bz2
Content-length: 1638
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90998
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:f52ec6bc163af837cd13e234b7c2eab6bc456e12
commit r8-10081-gf52ec6bc163af837cd13e234b7c2eab6bc456e12
Author: Marek Polacek <polacek@redhat.com>
Date: Wed Feb 26 00:33:52 2020 -0500
PR c++/90998 - ICE with copy elision in init by ctor and -Wconversion.
After r269667 which introduced joust_maybe_elide_copy, in C++17 we can
elide
a constructor if it uses a conversion function that returns a prvalue, and
use the conversion function in its stead.
This eliding means that if we have a candidate that previously didn't have
->second_conv, it can have it after the elision. This confused the
-Wconversion warning because it was assuming that if cand1->second_conv is
non-null, so is cand2->second_conv. Here cand1->second_conv was non-null
but cand2->second_conv remained null, so it crashed in compare_ics.
I checked with clang that both compilers call A::operator B() in C++17 and
B::B(A const &) otherwise.
gcc/cp/ChangeLog
2020-02-26 Marek Polacek <polacek@redhat.com>
PR c++/90998 - ICE with copy elision in init by ctor and -Wconversion.
* call.c (joust): Don't attempt to warn if ->second_conv is null.
gcc/testsuite/ChangeLog
2020-02-26 Marek Polacek <polacek@redhat.com>
PR c++/90998 - ICE with copy elision in init by ctor and -Wconversion.
* g++.dg/cpp0x/overload-conv-4.C: New test.
>From gcc-bugs-return-671431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 05:38:20 2020
Return-Path: <gcc-bugs-return-671431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85794 invoked by alias); 26 Feb 2020 05:38: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 84855 invoked by uid 55); 26 Feb 2020 05:37:54 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86521] [8 Regression] GCC 8 selects incorrect overload of ref-qualified conversion operator template
Date: Wed, 26 Feb 2020 05: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: 8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86521-4-e9vIhbwiU2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03012.txt.bz2
Content-length: 1925
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86521
--- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:f93784da474823ad563a9dfd6fd535a017b4bc9f
commit r8-10078-gf93784da474823ad563a9dfd6fd535a017b4bc9f
Author: Jason Merrill <jason@redhat.com>
Date: Wed Feb 26 00:33:52 2020 -0500
PR c++/86521 - wrong overload resolution with ref-qualifiers.
Here we were wrongly treating binding a const lvalue ref to an xvalue as
direct binding, which is wrong under [dcl.init.ref] and [over.match.ref].
gcc/cp/ChangeLog
2020-02-26 Jason Merrill <jason@redhat.com>
PR c++/86521 - wrong overload resolution with ref-qualifiers.
* call.c (build_user_type_conversion_1): Don't use a conversion to a
reference of the wrong rvalueness for direct binding.
--- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:32988aac5be4fa472823e21d2d0eb877faca5667
commit r8-10080-g32988aac5be4fa472823e21d2d0eb877faca5667
Author: Jason Merrill <jason@redhat.com>
Date: Wed Feb 26 00:33:52 2020 -0500
PR c++/86521 - C++17 copy elision in initialization by constructor.
This is an overlooked case in C++17 mandatory copy elision: We want
overload
resolution to reflect that initializing an object from a prvalue does not
involve a copy or move constructor even when [over.match.ctor] says that
only constructors are candidates. Here I implement that by looking through
the copy/move constructor in joust.
gcc/cp/ChangeLog
2020-02-26 Jason Merrill <jason@redhat.com>
PR c++/86521 - C++17 copy elision in initialization by constructor.
* call.c (joust_maybe_elide_copy): New.
(joust): Call it.
>From gcc-bugs-return-671430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 05:38:20 2020
Return-Path: <gcc-bugs-return-671430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85676 invoked by alias); 26 Feb 2020 05:38: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 84986 invoked by uid 55); 26 Feb 2020 05:38:09 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86521] [8 Regression] GCC 8 selects incorrect overload of ref-qualified conversion operator template
Date: Wed, 26 Feb 2020 05: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: 8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86521-4-DH7iluVz7z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03010.txt.bz2
Content-length: 1064
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86521
--- Comment #16 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:32988aac5be4fa472823e21d2d0eb877faca5667
commit r8-10080-g32988aac5be4fa472823e21d2d0eb877faca5667
Author: Jason Merrill <jason@redhat.com>
Date: Wed Feb 26 00:33:52 2020 -0500
PR c++/86521 - C++17 copy elision in initialization by constructor.
This is an overlooked case in C++17 mandatory copy elision: We want
overload
resolution to reflect that initializing an object from a prvalue does not
involve a copy or move constructor even when [over.match.ctor] says that
only constructors are candidates. Here I implement that by looking through
the copy/move constructor in joust.
gcc/cp/ChangeLog
2020-02-26 Jason Merrill <jason@redhat.com>
PR c++/86521 - C++17 copy elision in initialization by constructor.
* call.c (joust_maybe_elide_copy): New.
(joust): Call it.
>From gcc-bugs-return-671429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 05:38:17 2020
Return-Path: <gcc-bugs-return-671429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85387 invoked by alias); 26 Feb 2020 05: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 84738 invoked by uid 55); 26 Feb 2020 05:37:43 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86521] [8 Regression] GCC 8 selects incorrect overload of ref-qualified conversion operator template
Date: Wed, 26 Feb 2020 05: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: 8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86521-4-UbZKpHaoiD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03011.txt.bz2
Content-length: 914
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86521
--- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:f93784da474823ad563a9dfd6fd535a017b4bc9f
commit r8-10078-gf93784da474823ad563a9dfd6fd535a017b4bc9f
Author: Jason Merrill <jason@redhat.com>
Date: Wed Feb 26 00:33:52 2020 -0500
PR c++/86521 - wrong overload resolution with ref-qualifiers.
Here we were wrongly treating binding a const lvalue ref to an xvalue as
direct binding, which is wrong under [dcl.init.ref] and [over.match.ref].
gcc/cp/ChangeLog
2020-02-26 Jason Merrill <jason@redhat.com>
PR c++/86521 - wrong overload resolution with ref-qualifiers.
* call.c (build_user_type_conversion_1): Don't use a conversion to a
reference of the wrong rvalueness for direct binding.
>From gcc-bugs-return-671432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 06:24:48 2020
Return-Path: <gcc-bugs-return-671432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116715 invoked by alias); 26 Feb 2020 06:24: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 116651 invoked by uid 48); 26 Feb 2020 06:24:43 -0000
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/93935] [9/10 regression] gcc.dg/vect/bb-slp-over-widen-2.c fails starting with r262371 (r10-6856)
Date: Wed, 26 Feb 2020 06:24: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: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-93935-4-c4SRkLiwFK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93935-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03014.txt.bz2
Content-length: 715
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93935
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-02-26
Ever confirmed|0 |1
--- Comment #1 from Kewen Lin <linkw at gcc dot gnu.org> ---
Indeed, those two test cases are similar, both of them require misaligned
vector access support. Although the case with -mvsx, it can't use unaligned vsx
insns due to -mno-allow-movmisalign.
The patch has been sent for review which allows r267528.
>From gcc-bugs-return-671433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 06:46:40 2020
Return-Path: <gcc-bugs-return-671433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62934 invoked by alias); 26 Feb 2020 06:46: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 62870 invoked by uid 48); 26 Feb 2020 06:46:35 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55212] [SH] Switch to LRA
Date: Wed, 26 Feb 2020 06: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.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-55212-4-eMGM18YIDl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55212-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55212-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03015.txt.bz2
Content-length: 2172
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #122 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Oleg Endo from comment #121)
> (In reply to John Paul Adrian Glaubitz from comment #120)
> >
> > That's a huge task which is why I prefer fixing issues on the fly.
>
> I thought this is almost fully automated?
The build process is. Fixing broken packages isn't.
> You can apply this patch to GCC to enable LRA by default for SH
>
> --- sh.opt.orig 2019-03-04 10:09:09.244521000 +0900
> +++ sh.opt 2020-02-26 10:19:55.414340269 +0900
> @@ -299,5 +299,5 @@
> Enable the use of the fsrra instruction.
>
> mlra
> -Target Report Var(sh_lra_flag) Init(0) Save
> +Target Report Var(sh_lra_flag) Init(1) Save
> Use LRA instead of reload (transitional).
>
> Then let it rebuild everything.
Everything is around 13.000 source packages.
> > We are going to switch over anyway with GCC-12 or GCC-13, so I'm not sure
> > what we are gaining if we continue to wait.
>
> I don't get it. You want to enable LRA by default for your distro, but you
> don't want to rebuild all the packages with that modification? It's like ..
> shipping a distro with a new compiler, which potentially can't compile the
> distro packages (correctly), so instead we secretly use an older compiler to
> build the packages .... ? Is that normal practice? Sorry, sounds like a
> mess to me.
Debian/sh4 is not a release target, so it's not being shipped and there is no
warranty anyway.
I also don't have the possibility to rebuild the whole archive in a separate
project. There is only unstable. If am doing a complete rebuild now, I will be
busy for the next weeks or months (there are new packages coming in every day)
looking at issues because there might be a lot of failing packages, also for
other reasons.
It's simply not practical from my perspective. I'm doing this as a hobby, not
as a full time job, so I can't take care of all issues all-day long.
And, finally, the buildd capacity is limited on sh4. If this was POWER or
SPARC, we would have plenty of resources for a complete rebuild.
>From gcc-bugs-return-671434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 07:59:22 2020
Return-Path: <gcc-bugs-return-671434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75166 invoked by alias); 26 Feb 2020 07:59: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 68377 invoked by uid 55); 26 Feb 2020 07:59:17 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93820] [8/9/10 Regression] wrong code at -O3 on x86_64-linux-gnu since r9-1732
Date: Wed, 26 Feb 2020 07: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: 9.2.1
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: 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-93820-4-6Nn7AdaqCa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03016.txt.bz2
Content-length: 1177
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93820
--- Comment #7 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 25 Feb 2020, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93820
>
> --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> On the original testcase, the reason why dse3 doesn't help is we have:
> a[4] = 1;
> _4 = *c.0_1;
> a[5] = _4;
> a[3] = 1;
> e = 0;
> a[8] = 0;
> MEM <vector(4) int> [(int *)&a + 16B] = { 0, 0, 0, 0 };
> and c.0_1 might alias the a array, so dse3 removes a[5] store as redundant, but
> only later cddce removes the _4 = *c.0_1 load and only then the a[4] = 1; store
> could be also removed (i.e. it would require iteration, or performing some kind
> of (cheap) dce in the dse pass after removing each store).
A simple immediate-use / worklist based DCE would be possible after each
DSE but then this always felt like too ad-hoc to me ...
It would also have hidden this bug in store-merging (which is also
why I prefer the GIMPLE testcase at least for the affected function
since there's 100s of passes before store-merging)
>From gcc-bugs-return-671435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 08:03:58 2020
Return-Path: <gcc-bugs-return-671435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87572 invoked by alias); 26 Feb 2020 08:03: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 87515 invoked by uid 55); 26 Feb 2020 08:03:52 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93905] [8 Regression] Cannot use Derived type of Base containing both enum and protected destructor
Date: Wed, 26 Feb 2020 08: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: 8.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93905-4-rKlaXbJ0ZU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93905-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03017.txt.bz2
Content-length: 1477
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93905
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:f4335f978249a2991620f38e118adf790e677968
commit r8-10082-gf4335f978249a2991620f38e118adf790e677968
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Feb 26 09:02:05 2020 +0100
c++: Fix rejects-valid bug in cxx_eval_outermost_constant_expr [PR93905]
The following testcase is rejected in 8.3, but was accepted in 8.2 and
is in 9.x. This started with my PR87934
* constexpr.c (cxx_eval_constant_expression) <case CONSTRUCTOR>: Do
re-process TREE_CONSTANT CONSTRUCTORs if they aren't reduced constant
expressions.
backport, where the NSDMI CONSTRUCTOR that contains CONST_DECLs is now
constexpr evaluated so that it doesn't contain them. The difference from
9.x is that 9.x doesn't call get_target_expr if we got a CONSTRUCTOR for a
class type for something that has been originally a CONSTRUCTOR too.
This patch cherry-picks just that hunk of the r9-3835 change.
2020-02-26 Jakub Jelinek <jakub@redhat.com>
PR c++/93905
Backported from mainline
2018-11-04 Jason Merrill <jason@redhat.com>
* constexpr.c (cxx_eval_outermost_constant_expr): Don't wrap a
CONSTRUCTOR if one was passed in.
* g++.dg/cpp0x/pr93905.C: New test.
>From gcc-bugs-return-671437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 08:04:31 2020
Return-Path: <gcc-bugs-return-671437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88411 invoked by alias); 26 Feb 2020 08:04: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 88369 invoked by uid 48); 26 Feb 2020 08:04:24 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93939] missing optimization for floating-point expression converted to integer whose result is known at compile time
Date: Wed, 26 Feb 2020 08:04: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: missed-optimization
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-93939-4-gGLEnmq4D1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93939-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03019.txt.bz2
Content-length: 418
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93939
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
typedef long T;
also generates a comparison with 24.
The main issue is that b is used outside of the branch controlled by if(b==8),
so a naive substitution misses it. Repeating 3*b in the branch is useless, we
CSE it anyway. Still, DOM manages the optimization for int, so there is hope.
>From gcc-bugs-return-671436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 08:04:30 2020
Return-Path: <gcc-bugs-return-671436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88390 invoked by alias); 26 Feb 2020 08:04: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 88335 invoked by uid 48); 26 Feb 2020 08:04:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/29186] optimzation breaks floating point exception flag reading
Date: Wed, 26 Feb 2020 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: 4.1.2
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:
Message-ID: <bug-29186-4-cQdRMAtv8I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-29186-4@http.gcc.gnu.org/bugzilla/>
References: <bug-29186-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03018.txt.bz2
Content-length: 697
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29186
--- Comment #24 from Richard Biener <rguenth at gcc dot gnu.org> ---
For the division when GCC doesn't know the divident is not zero I think we
actually fixed the bug but yes, in general FP operation reordering wrt FP
env access isn't fixed.
But GCC needs to consider that feclear/testexcept exit the program and since
the division may trap it cannot hoist it before the feclearexcept call.
It might move it after the fetestexcept call though (delaying traps is OK).
As soon as we start to put more knowledge about feclearexcept into GCC this
will break again. Oh - we actually do know this since GCC 8 ...
So you're just lucky indeed ...
>From gcc-bugs-return-671438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 08:06:18 2020
Return-Path: <gcc-bugs-return-671438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90713 invoked by alias); 26 Feb 2020 08:06: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 90674 invoked by uid 55); 26 Feb 2020 08:06:14 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93905] [8 Regression] Cannot use Derived type of Base containing both enum and protected destructor
Date: Wed, 26 Feb 2020 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: 8.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93905-4-rXRyQ0e0EZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93905-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03020.txt.bz2
Content-length: 658
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93905
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:5de338f001eb2a821f40e599bd55119d43e0ae7e
commit r10-6859-g5de338f001eb2a821f40e599bd55119d43e0ae7e
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Feb 26 09:04:44 2020 +0100
c++: Fix rejects-valid bug in cxx_eval_outermost_constant_expr [PR93905]
Add testcase for a bug that has been just on the 8 branch.
2020-02-26 Jakub Jelinek <jakub@redhat.com>
PR c++/93905
* g++.dg/cpp0x/pr93905.C: New test.
>From gcc-bugs-return-671439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 08:07:22 2020
Return-Path: <gcc-bugs-return-671439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91978 invoked by alias); 26 Feb 2020 08:07: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 91919 invoked by uid 55); 26 Feb 2020 08:07:16 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93905] [8 Regression] Cannot use Derived type of Base containing both enum and protected destructor
Date: Wed, 26 Feb 2020 08: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: 8.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93905-4-XRzuUPTwEz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93905-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03021.txt.bz2
Content-length: 665
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93905
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:c6b81c451983f1b9a6e184f137819abf4978eddd
commit r9-8280-gc6b81c451983f1b9a6e184f137819abf4978eddd
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Feb 26 09:04:44 2020 +0100
c++: Fix rejects-valid bug in cxx_eval_outermost_constant_expr [PR93905]
Add testcase for a bug that has been just on the 8 branch.
2020-02-26 Jakub Jelinek <jakub@redhat.com>
PR c++/93905
* g++.dg/cpp0x/pr93905.C: New test.
>From gcc-bugs-return-671440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 08:19:10 2020
Return-Path: <gcc-bugs-return-671440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126528 invoked by alias); 26 Feb 2020 08:19: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 126462 invoked by uid 48); 26 Feb 2020 08:19:04 -0000
From: "markeggleston at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93835] [9/10 Regression] ICE in simplify_findloc_nodim, at fortran/simplify.c:5513
Date: Wed, 26 Feb 2020 08: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: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: markeggleston at gcc dot gnu.org
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: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93835-4-k4mX69j4oP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03022.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93835
markeggleston at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from markeggleston at gcc dot gnu.org ---
committed
>From gcc-bugs-return-671441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 08:21:58 2020
Return-Path: <gcc-bugs-return-671441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1780 invoked by alias); 26 Feb 2020 08:21: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 940 invoked by uid 48); 26 Feb 2020 08:21:53 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93907] [10 Regression] internal compiler error: in hashtab_chk_error, at hash-table.c:137
Date: Wed, 26 Feb 2020 08: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: ice-on-valid-code
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_known_to_work short_desc cf_known_to_fail
Message-ID: <bug-93907-4-7FgOA5OlDg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93907-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93907-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03023.txt.bz2
Content-length: 5050
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93907
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-reduction |
Known to work| |9.2.0
Summary|internal compiler error: in |[10 Regression] internal
|hashtab_chk_error, at |compiler error: in
|hash-table.c:137 |hashtab_chk_error, at
| |hash-table.c:137
Known to fail| |10.0
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
creduce yielded the following, which compiles with gcc 9 and -fconcepts.
ICEs with gcc 10 and -std=gnu++2a
template <int a> struct c {
static constexpr int d = a;
typedef c e;
};
template <typename> struct f;
template <typename b> using g = typename f<b>::e;
struct b;
template <typename b> struct f { using e = b; };
template <typename ai> struct m { typedef g<ai> aj; };
template <typename b> class n { typedef typename m<b>::aj e; };
template <typename b> using an = typename n<b>::e;
template <typename> constexpr bool ao = c<true>::d;
template <typename> constexpr bool i = c<1>::d;
template <typename> concept bb = i<b>;
using cc = __int128;
template <typename> concept cd = bb<cc>;
template <typename bt> concept ce = requires { requires cd<bt>; };
template <typename bt> concept h = ce<bt>;
template <typename bt> concept l = h<bt>;
template <typename> concept cl = ao<b>;
template <typename b> concept cp = requires(b j) {
requires h<an<decltype(j.begin())>>;
};
struct o {
template <cl b> requires cp<b> auto operator()(b) {}
};
template <typename b> using cm = decltype(o{}(b()));
template <typename bt> concept ct = l<bt>;
template <typename da> concept dd = ct<cm<da>>;
template <typename da> concept de = dd<da>;
struct {
template <de da, typename b> void operator()(da, b);
} di;
class p {
void begin();
};
template <typename> using df = p;
template <int> void q() {
df<int> k;
int d;
di(k, d);
}
hash table checking failed: equal operator returns true for a pair of values
with a different hash value
constrained.cc: In instantiation of ‘void<unnamed struct>::operator()(da, b)
[with da = p; b = int]’:
constrained.cc:41:10: required from here
constrained.cc:17:57: internal compiler error: in hashtab_chk_error, at
hash-table.c:137
17 | template <typename bt> concept ce = requires { requires cd<bt>; };
| ~~~~~~~~~^~~~~~
0x8ec130 hashtab_chk_error()
/home/jwakely/src/gcc/gcc/gcc/hash-table.c:137
0x94efd3 hash_table<sat_hasher, false, xcallocator>::verify(sat_entry* const&,
unsigned int)
/home/jwakely/src/gcc/gcc/gcc/hash-table.h:1033
0x94f5cf hash_table<sat_hasher, false,
xcallocator>::find_slot_with_hash(sat_entry* const&, unsigned int,
insert_option)
/home/jwakely/src/gcc/gcc/gcc/hash-table.h:968
0x94b9b3 hash_table<sat_hasher, false, xcallocator>::find_slot(sat_entry*
const&, insert_option)
/home/jwakely/src/gcc/gcc/gcc/hash-table.h:435
0x94b9b3 save_satisfaction
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2304
0x94c042 satisfaction_cache::save(tree_node*)
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2338
0x94c042 satisfy_atom
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2552
0x94c042 satisfy_constraint_r
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2579
0x94cb38 satisfy_constraint
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2599
0x94ce27 tsubst_nested_requirement
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2006
0x94ce27 tsubst_requirement
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2027
0x94ce27 tsubst_requirement_body
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2043
0x94ce27 tsubst_requires_expr(tree_node*, tree_node*, int, tree_node*)
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2159
0xa8674a tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
/home/jwakely/src/gcc/gcc/gcc/cp/pt.c:20336
0xa794c7 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
/home/jwakely/src/gcc/gcc/gcc/cp/pt.c:18597
0x94bdaa satisfy_atom
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2523
0x94bdaa satisfy_constraint_r
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2579
0x94cb38 satisfy_constraint
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2599
0x94e627 satisfy_declaration_constraints
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2698
0x94e627 constraint_satisfaction_value
/home/jwakely/src/gcc/gcc/gcc/cp/constraint.cc:2733
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-671442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 08:35:40 2020
Return-Path: <gcc-bugs-return-671442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36970 invoked by alias); 26 Feb 2020 08:35: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 36902 invoked by uid 55); 26 Feb 2020 08:35:35 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93820] [8/9/10 Regression] wrong code at -O3 on x86_64-linux-gnu since r9-1732
Date: Wed, 26 Feb 2020 08: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: 9.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93820-4-bk5rAc7URH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03024.txt.bz2
Content-length: 4513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93820
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:4d213bf6011ed2b30b9d0ca70069a5dbc294b5d7
commit r10-6860-g4d213bf6011ed2b30b9d0ca70069a5dbc294b5d7
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Feb 26 09:33:48 2020 +0100
store-merging: Fix coalesce_immediate_stores [PR93820]
The following testcase is miscompiled in 8+.
The problem is that check_no_overlap has a special case for INTEGER_CST
marked stores (i.e. stores of constants), if both all currenly merged
stores
and the one under consideration for merging with them are marked that way,
it anticipates that other INTEGER_CST marked stores that overlap with those
and precede those (have smaller info->order) could be merged with those and
doesn't punt for them.
In PR86844 and PR87859 fixes I've then added quite large code that is
performed after check_no_overlap and tries to find out if we need and can
merge further INTEGER_CST marked stores, or need to punt.
Unfortunately, that code is there only in the overlapping case code and
the testcase below shows that we really need it even in the adjacent store
case. After sort_by_bitpos we have:
bitpos width order rhs_code
96 32 3 INTEGER_CST
128 32 1 INTEGER_CST
128 128 2 INTEGER_CST
192 32 0 MEM_REF
Because of the missing PR86844/PR87859-ish code in the adjacent store
case, we merge the adjacent (memory wise) stores 96/32/3 and 128/32/1,
and then we consider the 128-bit store which is in program-order in between
them, but in this case we punt, because the merging would extend the
merged store region from bitpos 96 and 64-bits to bitpos 96 and 160-bits
and that has an overlap with an incompatible store (the MEM_REF one).
The problem is that we can't really punt this way, because the 128-bit
store is in between those two we've merged already, so either we manage
to merge even that one together with the others, or would need to avoid
already merging the 96/32/3 and 128/32/1 stores together.
Now, rather than copying around the PR86844/PR87859 code to the other spot,
we can actually just use the overlapping code, merge_overlapping is really
a superset of merge_into, so that is what the patch does. If doing
adjacent store merge for rhs_code other than INTEGER_CST, I believe the
current code is already fine, check_no_overlap in that case doesn't make
the exception and will punt if there is some earlier (smaller order)
non-mergeable overlapping store. There is just one case that could be
problematic, if the merged_store has BIT_INSERT_EXPRs in them and the
new store is a constant store (INTEGER_CST rhs_code), then check_no_overlap
would do the exception and still would allow the special case. But we
really shouldn't have the special case in that case, so this patch also
changes check_no_overlap to just have a bool whether we should have the
special case or not.
Note, as I said in the PR, for GCC11 we could consider performing some kind
of cheap DSE during the store merging (perhaps guarded with flag_tree_dse).
And another thing to consider is only consider as problematic non-mergeable
stores that not only have order smaller than last_order as currently, but
also have order larger than first_order, as in this testcase if we actually
ignored (not merged with anything at all) the 192/32/0 store, because it is
not in between the other stores we'd merge, it would be fine to merge the
other 3 stores, though of course the testcase can be easily adjusted by
putting the 192/32 store after the 128/32 store and then this patch would
be
still needed. Though, I think I'd need more time thinking this over.
2020-02-26 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/93820
* gimple-ssa-store-merging.c (check_no_overlap): Change RHS_CODE
argument to ALL_INTEGER_CST_P boolean.
(imm_store_chain_info::try_coalesce_bswap): Adjust caller.
(imm_store_chain_info::coalesce_immediate_stores): Likewise. Handle
adjacent INTEGER_CST store into merged_store->only_constants like
overlapping one.
* gcc.dg/pr93820.c: New test.
>From gcc-bugs-return-671443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 08:43:31 2020
Return-Path: <gcc-bugs-return-671443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45193 invoked by alias); 26 Feb 2020 08: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 45118 invoked by uid 55); 26 Feb 2020 08:43:25 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93820] [8/9/10 Regression] wrong code at -O3 on x86_64-linux-gnu since r9-1732
Date: Wed, 26 Feb 2020 08: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.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93820-4-edicysDxCD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03025.txt.bz2
Content-length: 4520
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93820
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:d0eff1793dc844c2a9532d8ef1a07ba137cfb4e6
commit r9-8281-gd0eff1793dc844c2a9532d8ef1a07ba137cfb4e6
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Feb 26 09:33:48 2020 +0100
store-merging: Fix coalesce_immediate_stores [PR93820]
The following testcase is miscompiled in 8+.
The problem is that check_no_overlap has a special case for INTEGER_CST
marked stores (i.e. stores of constants), if both all currenly merged
stores
and the one under consideration for merging with them are marked that way,
it anticipates that other INTEGER_CST marked stores that overlap with those
and precede those (have smaller info->order) could be merged with those and
doesn't punt for them.
In PR86844 and PR87859 fixes I've then added quite large code that is
performed after check_no_overlap and tries to find out if we need and can
merge further INTEGER_CST marked stores, or need to punt.
Unfortunately, that code is there only in the overlapping case code and
the testcase below shows that we really need it even in the adjacent store
case. After sort_by_bitpos we have:
bitpos width order rhs_code
96 32 3 INTEGER_CST
128 32 1 INTEGER_CST
128 128 2 INTEGER_CST
192 32 0 MEM_REF
Because of the missing PR86844/PR87859-ish code in the adjacent store
case, we merge the adjacent (memory wise) stores 96/32/3 and 128/32/1,
and then we consider the 128-bit store which is in program-order in between
them, but in this case we punt, because the merging would extend the
merged store region from bitpos 96 and 64-bits to bitpos 96 and 160-bits
and that has an overlap with an incompatible store (the MEM_REF one).
The problem is that we can't really punt this way, because the 128-bit
store is in between those two we've merged already, so either we manage
to merge even that one together with the others, or would need to avoid
already merging the 96/32/3 and 128/32/1 stores together.
Now, rather than copying around the PR86844/PR87859 code to the other spot,
we can actually just use the overlapping code, merge_overlapping is really
a superset of merge_into, so that is what the patch does. If doing
adjacent store merge for rhs_code other than INTEGER_CST, I believe the
current code is already fine, check_no_overlap in that case doesn't make
the exception and will punt if there is some earlier (smaller order)
non-mergeable overlapping store. There is just one case that could be
problematic, if the merged_store has BIT_INSERT_EXPRs in them and the
new store is a constant store (INTEGER_CST rhs_code), then check_no_overlap
would do the exception and still would allow the special case. But we
really shouldn't have the special case in that case, so this patch also
changes check_no_overlap to just have a bool whether we should have the
special case or not.
Note, as I said in the PR, for GCC11 we could consider performing some kind
of cheap DSE during the store merging (perhaps guarded with flag_tree_dse).
And another thing to consider is only consider as problematic non-mergeable
stores that not only have order smaller than last_order as currently, but
also have order larger than first_order, as in this testcase if we actually
ignored (not merged with anything at all) the 192/32/0 store, because it is
not in between the other stores we'd merge, it would be fine to merge the
other 3 stores, though of course the testcase can be easily adjusted by
putting the 192/32 store after the 128/32 store and then this patch would
be
still needed. Though, I think I'd need more time thinking this over.
2020-02-26 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/93820
* gimple-ssa-store-merging.c (check_no_overlap): Change RHS_CODE
argument to ALL_INTEGER_CST_P boolean.
(imm_store_chain_info::try_coalesce_bswap): Adjust caller.
(imm_store_chain_info::coalesce_immediate_stores): Likewise. Handle
adjacent INTEGER_CST store into merged_store->only_constants like
overlapping one.
* gcc.dg/pr93820.c: New test.
>From gcc-bugs-return-671444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 08:50:56 2020
Return-Path: <gcc-bugs-return-671444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7622 invoked by alias); 26 Feb 2020 08:50: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 7552 invoked by uid 48); 26 Feb 2020 08:50:50 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93934] Unnecessary fld of uninitialized float stack variable results in ub of valid C++ code
Date: Wed, 26 Feb 2020 08: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: 7.4.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov 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 cc resolution
Message-ID: <bug-93934-4-x1ufdYkixK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03026.txt.bz2
Content-length: 830
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93934
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |amonakov at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #2 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
fcmov can only raise an x87 fpu exception on x87 stack underflow, which cannot
happen here.
Even if it did raise FE_INVALID for SNaNs, note that GCC does not support SNaNs
by default; -fsignaling-nans can be specified to request that, but note that
documentation says the support is incomplete.
No bug here afaict.
>From gcc-bugs-return-671445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 08:51:44 2020
Return-Path: <gcc-bugs-return-671445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8895 invoked by alias); 26 Feb 2020 08:51: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 8809 invoked by uid 55); 26 Feb 2020 08:51:38 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93820] [8/9/10 Regression] wrong code at -O3 on x86_64-linux-gnu since r9-1732
Date: Wed, 26 Feb 2020 08: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: 9.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93820-4-ZpYAnb7Wfw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03027.txt.bz2
Content-length: 4522
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93820
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:8edd406bd7515833905d6bba8fb9195af392008c
commit r8-10083-g8edd406bd7515833905d6bba8fb9195af392008c
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Feb 26 09:33:48 2020 +0100
store-merging: Fix coalesce_immediate_stores [PR93820]
The following testcase is miscompiled in 8+.
The problem is that check_no_overlap has a special case for INTEGER_CST
marked stores (i.e. stores of constants), if both all currenly merged
stores
and the one under consideration for merging with them are marked that way,
it anticipates that other INTEGER_CST marked stores that overlap with those
and precede those (have smaller info->order) could be merged with those and
doesn't punt for them.
In PR86844 and PR87859 fixes I've then added quite large code that is
performed after check_no_overlap and tries to find out if we need and can
merge further INTEGER_CST marked stores, or need to punt.
Unfortunately, that code is there only in the overlapping case code and
the testcase below shows that we really need it even in the adjacent store
case. After sort_by_bitpos we have:
bitpos width order rhs_code
96 32 3 INTEGER_CST
128 32 1 INTEGER_CST
128 128 2 INTEGER_CST
192 32 0 MEM_REF
Because of the missing PR86844/PR87859-ish code in the adjacent store
case, we merge the adjacent (memory wise) stores 96/32/3 and 128/32/1,
and then we consider the 128-bit store which is in program-order in between
them, but in this case we punt, because the merging would extend the
merged store region from bitpos 96 and 64-bits to bitpos 96 and 160-bits
and that has an overlap with an incompatible store (the MEM_REF one).
The problem is that we can't really punt this way, because the 128-bit
store is in between those two we've merged already, so either we manage
to merge even that one together with the others, or would need to avoid
already merging the 96/32/3 and 128/32/1 stores together.
Now, rather than copying around the PR86844/PR87859 code to the other spot,
we can actually just use the overlapping code, merge_overlapping is really
a superset of merge_into, so that is what the patch does. If doing
adjacent store merge for rhs_code other than INTEGER_CST, I believe the
current code is already fine, check_no_overlap in that case doesn't make
the exception and will punt if there is some earlier (smaller order)
non-mergeable overlapping store. There is just one case that could be
problematic, if the merged_store has BIT_INSERT_EXPRs in them and the
new store is a constant store (INTEGER_CST rhs_code), then check_no_overlap
would do the exception and still would allow the special case. But we
really shouldn't have the special case in that case, so this patch also
changes check_no_overlap to just have a bool whether we should have the
special case or not.
Note, as I said in the PR, for GCC11 we could consider performing some kind
of cheap DSE during the store merging (perhaps guarded with flag_tree_dse).
And another thing to consider is only consider as problematic non-mergeable
stores that not only have order smaller than last_order as currently, but
also have order larger than first_order, as in this testcase if we actually
ignored (not merged with anything at all) the 192/32/0 store, because it is
not in between the other stores we'd merge, it would be fine to merge the
other 3 stores, though of course the testcase can be easily adjusted by
putting the 192/32 store after the 128/32 store and then this patch would
be
still needed. Though, I think I'd need more time thinking this over.
2020-02-26 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/93820
* gimple-ssa-store-merging.c (check_no_overlap): Change RHS_CODE
argument to ALL_INTEGER_CST_P boolean.
(imm_store_chain_info::try_coalesce_bswap): Adjust caller.
(imm_store_chain_info::coalesce_immediate_stores): Likewise. Handle
adjacent INTEGER_CST store into merged_store->only_constants like
overlapping one.
* gcc.dg/pr93820.c: New test.
>From gcc-bugs-return-671446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 08:52:49 2020
Return-Path: <gcc-bugs-return-671446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9977 invoked by alias); 26 Feb 2020 08:52: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 9886 invoked by uid 48); 26 Feb 2020 08:52:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93820] [8/9/10 Regression] wrong code at -O3 on x86_64-linux-gnu since r9-1732
Date: Wed, 26 Feb 2020 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.1
X-Bugzilla-Keywords: wrong-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: P2
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 resolution
Message-ID: <bug-93820-4-C3CqK9RADU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03028.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93820
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:01:55 2020
Return-Path: <gcc-bugs-return-671447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117722 invoked by alias); 26 Feb 2020 09:01: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 117675 invoked by uid 48); 26 Feb 2020 09:01:51 -0000
From: "vajdaz at protonmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93934] Unnecessary fld of uninitialized float stack variable results in ub of valid C++ code
Date: Wed, 26 Feb 2020 09: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: 7.4.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vajdaz at protonmail 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_status resolution
Message-ID: <bug-93934-4-dR0plTQzbd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03029.txt.bz2
Content-length: 958
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93934
Zoltan Vajda <vajdaz at protonmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #3 from Zoltan Vajda <vajdaz at protonmail dot com> ---
(In reply to Alexander Monakov from comment #2)
> fcmov can only raise an x87 fpu exception on x87 stack underflow, which
> cannot happen here.
>
> Even if it did raise FE_INVALID for SNaNs, note that GCC does not support
> SNaNs by default; -fsignaling-nans can be specified to request that, but
> note that documentation says the support is incomplete.
>
> No bug here afaict.
The problem is not the fcmov instruction, but the "fldl -32(%ebp)". It loads an
uninitialized value from the variable result, which may be a SNaN.
>From gcc-bugs-return-671448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:07:32 2020
Return-Path: <gcc-bugs-return-671448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5077 invoked by alias); 26 Feb 2020 09:07: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 5033 invoked by uid 48); 26 Feb 2020 09:07:27 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93930] [8/9/10 Regression] Unnecessary broadcast instructions for AVX512
Date: Wed, 26 Feb 2020 09: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: 9.2.0
X-Bugzilla-Keywords: 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: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget priority
Message-ID: <bug-93930-4-ITRsF7GQaq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93930-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93930-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03030.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93930
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target| |x86_64-*-*, i?86-*-*
Priority|P3 |P2
>From gcc-bugs-return-671449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:12:45 2020
Return-Path: <gcc-bugs-return-671449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8678 invoked by alias); 26 Feb 2020 09:12: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 8635 invoked by uid 48); 26 Feb 2020 09:12:40 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93934] Unnecessary fld of uninitialized float stack variable results in ub of valid C++ code
Date: Wed, 26 Feb 2020 09: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: 7.4.0
X-Bugzilla-Keywords: wrong-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
Message-ID: <bug-93934-4-t9Vt14EHz8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03031.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93934
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|missed-optimization |wrong-code
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
But does the load trap? I would expect fcmov also to not trap on sNaNs since
it's a move instruction?
>From gcc-bugs-return-671450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:13:19 2020
Return-Path: <gcc-bugs-return-671450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9886 invoked by alias); 26 Feb 2020 09: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 9839 invoked by uid 48); 26 Feb 2020 09:13:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/93935] [9/10 regression] gcc.dg/vect/bb-slp-over-widen-2.c fails starting with r262371 (r10-6856)
Date: Wed, 26 Feb 2020 09:13: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: 9.2.1
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: P2
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone
Message-ID: <bug-93935-4-qzLSQYHOl7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93935-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03032.txt.bz2
Content-length: 345
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93935
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Target Milestone|--- |9.3
>From gcc-bugs-return-671451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:15:05 2020
Return-Path: <gcc-bugs-return-671451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11367 invoked by alias); 26 Feb 2020 09:15: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 11260 invoked by uid 48); 26 Feb 2020 09:14:58 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/89164] can construct vector with non-copyable-but-trivially-copyable elements
Date: Wed, 26 Feb 2020 09:15: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.0
X-Bugzilla-Keywords: accepts-invalid, 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: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-89164-4-r6nw8cHjg3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89164-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89164-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03033.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89164
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I'm not going to backport this to gcc-8 so closing as fixed.
>From gcc-bugs-return-671452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:20:26 2020
Return-Path: <gcc-bugs-return-671452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15641 invoked by alias); 26 Feb 2020 09:20: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 15538 invoked by uid 48); 26 Feb 2020 09:20:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93939] missing optimization for floating-point expression converted to integer whose result is known at compile time
Date: Wed, 26 Feb 2020 09:20: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: 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: 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-93939-4-BecA5zzSgc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93939-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03034.txt.bz2
Content-length: 765
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93939
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-26
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
It needs "backward propagation" of conditional equivalence information which we
do for very limited numbers and sets of operations. In VN the additional issue
is that we don't record conditional equivalences at all (we just record known
predicates) because that doesn't fit in nicely.
>From gcc-bugs-return-671453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:26:56 2020
Return-Path: <gcc-bugs-return-671453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21244 invoked by alias); 26 Feb 2020 09:26: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 19796 invoked by uid 48); 26 Feb 2020 09:25:57 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87544] alloc-size-larger-than incorrectly triggered
Date: Wed, 26 Feb 2020 09:26: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: 8.2.1
X-Bugzilla-Keywords: diagnostic
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-87544-4-68Utxtl0k9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87544-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87544-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03035.txt.bz2
Content-length: 528
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87544
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.0
--- Comment #21 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for GCC 9, I'm not going to backport it to GCC 8.
>From gcc-bugs-return-671454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:28:55 2020
Return-Path: <gcc-bugs-return-671454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22436 invoked by alias); 26 Feb 2020 09: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 21488 invoked by uid 48); 26 Feb 2020 09:26:56 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87544] alloc-size-larger-than incorrectly triggered
Date: Wed, 26 Feb 2020 09:27: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: 8.2.1
X-Bugzilla-Keywords: diagnostic
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87544-4-44R0kB6ICq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87544-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87544-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03036.txt.bz2
Content-length: 221
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87544
--- Comment #22 from Jonathan Wakely <redi at gcc dot gnu.org> ---
N.B. in case somebody does want to backport it, the fix for this depends on the
fix for PR 78448.
>From gcc-bugs-return-671455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:38:12 2020
Return-Path: <gcc-bugs-return-671455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29819 invoked by alias); 26 Feb 2020 09:38: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 29692 invoked by uid 48); 26 Feb 2020 09:37:56 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90281] utf-8 encoded std::filesystem::path can not be converted to utf-16.
Date: Wed, 26 Feb 2020 09: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: 8.3.0
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: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-90281-4-IlMeJJOvjf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90281-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90281-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03037.txt.bz2
Content-length: 547
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90281
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.0
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I no longer plan to backport this to the gcc-8 branch, so closing as fixed.
>From gcc-bugs-return-671456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:43:19 2020
Return-Path: <gcc-bugs-return-671456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97029 invoked by alias); 26 Feb 2020 09:43: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 96948 invoked by uid 48); 26 Feb 2020 09:43:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93940] [8/9/10 Regression] crazy codegen bug on Og with builtin_constant_p, coverage, and pthread
Date: Wed, 26 Feb 2020 09: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: 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: cc
Message-ID: <bug-93940-4-lHQz3oyKeX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03038.txt.bz2
Content-length: 1252
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93940
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org,
| |jakub at gcc dot gnu.org
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This happens in edge_set_predicate:
271 if (predicate && *predicate == false
272 /* When handling speculative edges, we need to do the redirection
273 just once. Do it always on the direct edge, so we do not
274 attempt to resolve speculation while duplicating the edge. */
275 && (!e->speculative || e->callee))
276 e = redirect_to_unreachable (e);
I bet the inliner assumes that __builtin_constant_p will evaluate to true,
D.2273.b = 0;
k = D.2273;
...
_8 = k.b;
_9 = __builtin_constant_p (_8);
but while fre3 with -O2 propagates the 0 into __builtin_constant_p and folds it
to 1, with -Og we do fewer optimizations and don't propagate the constant to
it.
With -O2 -fno-tree-fre it will fail the same way.
>From gcc-bugs-return-671457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:44:04 2020
Return-Path: <gcc-bugs-return-671457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98363 invoked by alias); 26 Feb 2020 09:44: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 98298 invoked by uid 48); 26 Feb 2020 09:43:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93940] [8/9/10 Regression] crazy codegen bug on Og with builtin_constant_p, coverage, and pthread
Date: Wed, 26 Feb 2020 09:44: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: 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-93940-4-A25bMGDmvN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03039.txt.bz2
Content-length: 3765
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93940
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #5)
> __atomic_fetch_add_8 (&__gcov0._ZN1g1iE1a[2], 1, 0);
>
> I wonder what the type of __gcov0._ZN1g1iE1a is.
It's correct.
<var_decl 0x7ffff698d360 __gcov0._ZN1g1iE1a
type <array_type 0x7ffff6990150
type <integer_type 0x7ffff682b738 long int public DI
size <integer_cst 0x7ffff680de28 constant 64>
unit-size <integer_cst 0x7ffff680de40 constant 8>
align:64 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff682b738 precision:64 min <integer_cst 0x7ffff682f0c0
-9223372036854775808> max <integer_cst 0x7ffff682f0d8 9223372036854775807>
pointer_to_this <pointer_type 0x7ffff683c540>>
BLK
size <integer_cst 0x7ffff682f198 constant 256>
unit-size <integer_cst 0x7ffff682f288 constant 32>
align:64 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff6990150
domain <integer_type 0x7ffff69900a8 type <integer_type 0x7ffff682b000
sizetype>
DI size <integer_cst 0x7ffff680de28 64> unit-size <integer_cst
0x7ffff680de40 8>
align:64 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff69900a8 precision:64 min <integer_cst 0x7ffff680de58 0> max <integer_cst
0x7ffff698c270 3>>>
addressable nothrow static BLK <built-in>:0:0 size <integer_cst
0x7ffff682f198 256> unit-size <integer_cst 0x7ffff682f288 32>
align:256 warn_if_not_align:0>
I think the issue is with inliner predicates. The unreachable is added via
#1 0x00000000010e52c3 in redirect_to_unreachable (
e=<cgraph_edge* 0x7ffff69910d0 (<cgraph_node * 0x7ffff680f708 "i"/4> ->
<cgraph_node * 0x7ffff680f9d8 "__atomic_fetch_add_8"/13>)>)
at /space/rguenther/src/gcc-9-branch/gcc/ipa-fnsummary.c:236
#2 0x00000000010e53fe in edge_set_predicate (
e=<cgraph_edge* 0x7ffff69910d0 (<cgraph_node * 0x7ffff680f708 "i"/4> ->
<cgraph_node * 0x7ffff680f9d8 "__atomic_fetch_add_8"/13>)>,
predicate=0x7fffffffc350)
at /space/rguenther/src/gcc-9-branch/gcc/ipa-fnsummary.c:267
#3 0x00000000010ee97b in remap_edge_summaries (
inlined_edge=<cgraph_edge* 0x7ffff6818a28 (<cgraph_node * 0x7ffff680f870
"test"/5> -> <cgraph_node * 0x7ffff680f708 "i"/4>)>,
node=<cgraph_node * 0x7ffff680f708 "i"/4>, info=0x7ffff69917b8,
callee_info=0x7ffff6991820, operand_map=..., offset_map=...,
possible_truths=0, toplev_predicate=0x7fffffffc490)
at /space/rguenther/src/gcc-9-branch/gcc/ipa-fnsummary.c:2951
#4 0x00000000010ef369 in ipa_merge_fn_summary_after_inlining (
edge=<cgraph_edge* 0x7ffff6818a28 (<cgraph_node * 0x7ffff680f870 "test"/5>
-> <cgraph_node * 0x7ffff680f708 "i"/4>)>)
at /space/rguenther/src/gcc-9-branch/gcc/ipa-fnsummary.c:3101
#5 0x0000000002257d95 in inline_call (
new_edges=0x7fffffffd6a8, overall_size=0x339e5b0 <overall_size>,
update_overall_summary=true, callee_removed=0x0)
at /space/rguenther/src/gcc-9-branch/gcc/ipa-inline-transform.c:448
#6 0x0000000002248e5b in inline_small_functions ()
at /space/rguenther/src/gcc-9-branch/gcc/ipa-inline.c:2074
#7 0x000000000224a8a0 in ipa_inline ()
at /space/rguenther/src/gcc-9-branch/gcc/ipa-inline.c:2536
#8 0x000000000224b74d in (anonymous namespace)::pass_ipa_inline::execute (
this=0x33fa340) at /space/rguenther/src/gcc-9-branch/gcc/ipa-inline.c:2944
for
$1 = <cgraph_edge* 0x7ffff69910d0 (<cgraph_node * 0x7ffff680f708 "i"/4> ->
<cgraph_node * 0x7ffff680f9d8 "__atomic_fetch_add_8"/13>)>
and likely the __builtin_constant_p handling.
Something for Honza to debug. Honza?
>From gcc-bugs-return-671458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:44:40 2020
Return-Path: <gcc-bugs-return-671458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99318 invoked by alias); 26 Feb 2020 09:44: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 99261 invoked by uid 48); 26 Feb 2020 09:44:36 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93940] [8/9/10 Regression] crazy codegen bug on Og with builtin_constant_p, coverage, and pthread
Date: Wed, 26 Feb 2020 09:44: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: 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: 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
Message-ID: <bug-93940-4-Lmx7aTKcwO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93940-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03040.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93940
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
>From gcc-bugs-return-671459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:46:15 2020
Return-Path: <gcc-bugs-return-671459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114177 invoked by alias); 26 Feb 2020 09: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 107391 invoked by uid 48); 26 Feb 2020 09:46:09 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93934] Unnecessary fld of uninitialized float stack variable results in ub of valid C++ code
Date: Wed, 26 Feb 2020 09: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: 7.4.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov 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-93934-4-OuOfXwfnNc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03041.txt.bz2
Content-length: 677
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93934
--- Comment #5 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Ah, indeed. fld won't raise FE_INVALID for 80-bit long double, but here
'result' is stored on the stack in 64-bit format.
So: fcmov and 80-bit fldt don't trap, 32-bit flds and 64-bit fldl do.
Somehow RTL if-conversion would have to check "-fsignaling-nans is requested
and the target may raise FE_INVALID on loads" among other reason to reject a
speculative load.
I am afraid though that several other optimizations do not anticipate that x87
fp loads can raise exceptions on SNaNs either, making -fsignaling-nans
difficult to implement in full.
>From gcc-bugs-return-671460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:51:23 2020
Return-Path: <gcc-bugs-return-671460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38221 invoked by alias); 26 Feb 2020 09:51: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 38164 invoked by uid 48); 26 Feb 2020 09:51:19 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93941] gcc generates wrong debug information at -O2
Date: Wed, 26 Feb 2020 09:51: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: 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 cc version everconfirmed
Message-ID: <bug-93941-4-iaoNDyiBkf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93941-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93941-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03042.txt.bz2
Content-length: 1165
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93941
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-26
CC|rguenther at suse dot de |jakub at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Version|unknown |10.0
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. Bisection is likely wrong (-O2 doesn't do vectorization) and rather
it's probably related to
# DEBUG i => (int) ((ivtmp.22_29 - (unsigned long) &b) /[ex] 10) + 1
somehow breaking down leaving us with some other choice for i from
# DEBUG i => 0
or
# DEBUG i => (int) ((ivtmp.22_29 - (unsigned long) &b) /[ex] 10)
rather than dropping to a debug reset. GCC 9 had <optimized out> here
since we didn't have the above "fancy" debug expression for i.
>From gcc-bugs-return-671461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:56:16 2020
Return-Path: <gcc-bugs-return-671461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110800 invoked by alias); 26 Feb 2020 09:56: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 97115 invoked by uid 48); 26 Feb 2020 09:56:11 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93934] Unnecessary fld of uninitialized float stack variable results in ub of valid C++ code
Date: Wed, 26 Feb 2020 09: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: 7.4.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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-93934-4-8fTFyV7433@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03043.txt.bz2
Content-length: 1575
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93934
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-26
Ever confirmed|0 |1
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #5)
> Ah, indeed. fld won't raise FE_INVALID for 80-bit long double, but here
> 'result' is stored on the stack in 64-bit format.
>
> So: fcmov and 80-bit fldt don't trap, 32-bit flds and 64-bit fldl do.
>
> Somehow RTL if-conversion would have to check "-fsignaling-nans is requested
> and the target may raise FE_INVALID on loads" among other reason to reject a
> speculative load.
>
> I am afraid though that several other optimizations do not anticipate that
> x87 fp loads can raise exceptions on SNaNs either, making -fsignaling-nans
> difficult to implement in full.
I suppose a fldt followed by "truncation" to 32/64 bit would then trap at
the truncation step?
But yes, this will be difficult to handle. We'd have to mark all loads
from not must-initialized memory as possibly trapping and thus not eligible
for if-conversion. And this applies to possibly uninitialized registers
as well which might be spilled or allocated to the stack.
So confirmed at least. It's also more a middle-end issue affecting a
subset of targets only.
>From gcc-bugs-return-671462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:58:56 2020
Return-Path: <gcc-bugs-return-671462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32718 invoked by alias); 26 Feb 2020 09:58: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 32413 invoked by uid 48); 26 Feb 2020 09:58:50 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93934] Unnecessary fld of uninitialized float stack variable results in ub of valid C++ code
Date: Wed, 26 Feb 2020 09:58: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: 7.4.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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93934-4-838KH7Xy68@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03044.txt.bz2
Content-length: 244
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93934
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Or the issue is in regstack handling all stack vars as 80bit and thus
introducing the conversion step in the first place.
>From gcc-bugs-return-671463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:59:10 2020
Return-Path: <gcc-bugs-return-671463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33409 invoked by alias); 26 Feb 2020 09:59: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 33376 invoked by uid 48); 26 Feb 2020 09:59:05 -0000
From: "frederic.recoules@univ-grenoble-alpes.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/93942] New: [Extended-Asm] Last code snippet in 6.47.2.3 Output Operands is unsafe
Date: Wed, 26 Feb 2020 09:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frederic.recoules@univ-grenoble-alpes.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-93942-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03045.txt.bz2
Content-length: 891
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93942
Bug ID: 93942
Summary: [Extended-Asm] Last code snippet in 6.47.2.3 Output
Operands is unsafe
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: web
Assignee: unassigned at gcc dot gnu.org
Reporter: frederic.recoules@univ-grenoble-alpes.fr
Target Milestone: ---
The following code snippet is wrong because the compiler can choose memory "m"
constraint for both d and *e.
uint32_t c = 1;
uint32_t d;
uint32_t *e = &c;
asm ("mov %[e], %[d]"
: [d] "=rm" (d)
: [e] "rm" (*e));
The correct version should use a multi-alternative and it might be a good place
to introduce this notion.
asm ("movl %[e], %[d]"
: [d] "=r,m" (d)
: [e] "g,ri" (*e));
>From gcc-bugs-return-671464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 09:59:31 2020
Return-Path: <gcc-bugs-return-671464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34255 invoked by alias); 26 Feb 2020 09:59: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 34169 invoked by uid 55); 26 Feb 2020 09:59:26 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93820] [8/9/10 Regression] wrong code at -O3 on x86_64-linux-gnu since r9-1732
Date: Wed, 26 Feb 2020 09: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: 9.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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-93820-4-lWhsb2fbdK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03046.txt.bz2
Content-length: 614
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93820
--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:ce25177f505ea75b3c0833c3f3f0072b97ee1b44
commit r10-6861-gce25177f505ea75b3c0833c3f3f0072b97ee1b44
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Feb 26 10:58:13 2020 +0100
testsuite: Add a -O2 -fgimple testcase next to the -O2 -fno-tree-dse one
[PR93820]
2020-02-26 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/93820
* gcc.dg/pr93820-2.c: New test.
>From gcc-bugs-return-671465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 10:09:59 2020
Return-Path: <gcc-bugs-return-671465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59206 invoked by alias); 26 Feb 2020 10:09: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 59110 invoked by uid 48); 26 Feb 2020 10:09:45 -0000
From: "frederic.recoules@univ-grenoble-alpes.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93903] invalid input constraint in __asm__
Date: Wed, 26 Feb 2020 10:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frederic.recoules@univ-grenoble-alpes.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-93903-4-IL53bqQnaM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93903-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93903-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03047.txt.bz2
Content-length: 939
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93903
Frédéric Recoules <frederic.recoules@univ-grenoble-alpes.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |frederic.recoules@univ-gren
| |oble-alpes.fr
--- Comment #1 from Frédéric Recoules <frederic.recoules@univ-grenoble-alpes.fr> ---
I am pretty sure the error comes from the space you left in "r ".
Yet, in the "Simple-Constraints" documentation, it is said that space are
ignored
to allow visual alignment but, in fact, I realized a while ago it generates an
error.
I think it would not be a big change to either update the documentation at
https://gcc.gnu.org/onlinedocs/gcc/Simple-Constraints.html#Simple-Constraints
or to make the parser ignore the blank.
>From gcc-bugs-return-671466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 10:16:16 2020
Return-Path: <gcc-bugs-return-671466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85449 invoked by alias); 26 Feb 2020 10:16: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 63908 invoked by uid 48); 26 Feb 2020 10:15:58 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93934] Unnecessary fld of uninitialized float stack variable results in ub of valid C++ code
Date: Wed, 26 Feb 2020 10: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: 7.4.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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93934-4-bXghKuWBlu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03048.txt.bz2
Content-length: 929
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93934
--- Comment #8 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
I think regstack is fine as x87 only supports computations in its native 80-bit
format and conversions to/from ieee float/double happen only on memory
loads/stores.
> I suppose a fldt followed by "truncation" to 32/64 bit would then trap at
the truncation step?
Such "truncation" can only be implemented via a spill/reload on x87, so, yes.
> We'd have to mark all loads from not must-initialized memory as possibly
> trapping and thus not eligible for if-conversion.
(except long double)
> And this applies to possibly uninitialized registers
> as well which might be spilled or allocated to the stack.
Ideally registers should be always spilled in their native 80-bit format, for
which the problem does not arise. For C with -fexcess-precision=standard this
should already be the case.
>From gcc-bugs-return-671467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 10:23:11 2020
Return-Path: <gcc-bugs-return-671467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49371 invoked by alias); 26 Feb 2020 10:23: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 49285 invoked by uid 55); 26 Feb 2020 10:23:05 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93047] frename-registers does not work well with __builtin_return
Date: Wed, 26 Feb 2020 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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: guojiufu at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93047-4-UF7MctLPbr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93047-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93047-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03049.txt.bz2
Content-length: 1137
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93047
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jiu Fu Guo
<guojiufu@gcc.gnu.org>:
https://gcc.gnu.org/g:0ce89ea10d93a583854f02bc115e05cfd9d818e4
commit r9-8282-g0ce89ea10d93a583854f02bc115e05cfd9d818e4
Author: Jiufu Guo <guojiufu@linux.ibm.com>
Date: Mon Feb 17 10:48:39 2020 +0800
rs6000: mark clobber for registers changed by untpyed_call
As PR93047 said, __builtin_apply/__builtin_return does not work well with
-frename-registers. This is caused by return register(e.g. r3) is used to
rename another register, before return register is stored to stack.
This patch fix this issue by emitting clobber for those egisters which
maybe changed by untyped call.
gcc/
2020-02-26 Jiufu Guo <guojiufu@linux.ibm.com>
PR target/93047
* config/rs6000/rs6000.md (untyped_call): Add emit_clobber.
gcc/testsuite
2020-02-26 Jiufu Guo <guojiufu@linux.ibm.com>
PR target/93047
* gcc.dg/torture/stackalign/builtin-return-2.c: New test case.
>From gcc-bugs-return-671469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 10:31:36 2020
Return-Path: <gcc-bugs-return-671469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88988 invoked by alias); 26 Feb 2020 10:31: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 88335 invoked by uid 48); 26 Feb 2020 10:31:12 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93942] [Extended-Asm] Last code snippet in 6.47.2.3 Output Operands is unsafe
Date: Wed, 26 Feb 2020 10:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: unknown
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: keywords component
Message-ID: <bug-93942-4-MR8hzv0lLy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93942-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93942-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03051.txt.bz2
Content-length: 622
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93942
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |documentation
Component|web |inline-asm
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I don;t think this is wrong per-say. There could be target where mov accepts
operands as both mem. The manual in this location says more examples, and not
an i386 specific example here.
>From gcc-bugs-return-671468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 10:31:12 2020
Return-Path: <gcc-bugs-return-671468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88274 invoked by alias); 26 Feb 2020 10:31: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 88203 invoked by uid 48); 26 Feb 2020 10:31:03 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55212] [SH] Switch to LRA
Date: Wed, 26 Feb 2020 10:31: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: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.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-55212-4-cxIsjMp0ZB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55212-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55212-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03050.txt.bz2
Content-length: 904
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #123 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Oleg Endo from comment #121)
> (In reply to John Paul Adrian Glaubitz from comment #120)
> >
> > That's a huge task which is why I prefer fixing issues on the fly.
>
> I thought this is almost fully automated?
>
> You can apply this patch to GCC to enable LRA by default for SH
>
> --- sh.opt.orig 2019-03-04 10:09:09.244521000 +0900
> +++ sh.opt 2020-02-26 10:19:55.414340269 +0900
> @@ -299,5 +299,5 @@
> Enable the use of the fsrra instruction.
>
> mlra
> -Target Report Var(sh_lra_flag) Init(0) Save
> +Target Report Var(sh_lra_flag) Init(1) Save
> Use LRA instead of reload (transitional).
I will just do that for the default kernel now. But I won't trigger a full
archive rebuild. Just report issues once I see them.
>From gcc-bugs-return-671470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 10:31:46 2020
Return-Path: <gcc-bugs-return-671470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89814 invoked by alias); 26 Feb 2020 10:31: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 89686 invoked by uid 48); 26 Feb 2020 10:31:41 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55212] [SH] Switch to LRA
Date: Wed, 26 Feb 2020 10:31: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: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.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-55212-4-UuYxOzOdht@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55212-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55212-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03052.txt.bz2
Content-length: 370
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #124 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to John Paul Adrian Glaubitz from comment #123)
> I will just do that for the default kernel now. But I won't trigger a full
> archive rebuild. Just report issues once I see them.
Compiler, of course. Not kernel.
>From gcc-bugs-return-671471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 10:46:16 2020
Return-Path: <gcc-bugs-return-671471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118712 invoked by alias); 26 Feb 2020 10: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 118634 invoked by uid 48); 26 Feb 2020 10:46:10 -0000
From: "frederic.recoules@univ-grenoble-alpes.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93942] [Extended-Asm] Last code snippet in 6.47.2.3 Output Operands is unsafe
Date: Wed, 26 Feb 2020 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frederic.recoules@univ-grenoble-alpes.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:
Message-ID: <bug-93942-4-7vmAonAQ75@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93942-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93942-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03053.txt.bz2
Content-length: 407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93942
--- Comment #2 from Frédéric Recoules <frederic.recoules@univ-grenoble-alpes.fr> ---
You are right, it is not strictly speaking wrong per-say but, I would say the
context is a little bit misleading.
Yet, I may be too x86 oriented... as a matter of personal curiosity, do you
known an architecture that allows such dual memory constraint?
>From gcc-bugs-return-671472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 10:53:05 2020
Return-Path: <gcc-bugs-return-671472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 883 invoked by alias); 26 Feb 2020 10:53: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 859 invoked by uid 48); 26 Feb 2020 10:53:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93943] New: IRA/LRA happily rematerialize (un-CSEs) loads without register pressure
Date: Wed, 26 Feb 2020 10:53: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: 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-93943-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03054.txt.bz2
Content-length: 1235
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93943
Bug ID: 93943
Summary: IRA/LRA happily rematerialize (un-CSEs) loads without
register pressure
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
long a[1024], b[512], c[512];
void foo ()
{
for (int i = 0; i < 256; ++i)
{
b[2*i] = a[4*i];
b[2*i+1] = a[4*i+2];
c[2*i] = a[4*i+1];
c[2*i+1] = a[4*i+3];
}
}
at -O3 is vectorized with SSE2 V2DImode vectors doing two vector loads,
two shuffles and two vector stores. But we then emit
.L2:
movdqa a(%rax,%rax), %xmm0
movdqa %xmm0, %xmm1
punpckhqdq a+16(%rax,%rax), %xmm0
punpcklqdq a+16(%rax,%rax), %xmm1
addq $16, %rax
movaps %xmm1, b-16(%rax)
movaps %xmm0, c-16(%rax)
cmpq $4096, %rax
jne .L2
so took advantage of the memory op variant of the punpck instructions
enlarging the code and using more load uops.
>From gcc-bugs-return-671473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 10:57:12 2020
Return-Path: <gcc-bugs-return-671473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40302 invoked by alias); 26 Feb 2020 10:57: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 40270 invoked by uid 48); 26 Feb 2020 10:57:07 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93943] IRA/LRA happily rematerialize (un-CSEs) loads without register pressure
Date: Wed, 26 Feb 2020 10: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: 10.0
X-Bugzilla-Keywords: missed-optimization, ra
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
Message-ID: <bug-93943-4-2s36KAFzQU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93943-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93943-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03055.txt.bz2
Content-length: 773
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93943
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization, ra
Target| |x86_64-*-*
CC| |uros at gcc dot gnu.org,
| |vmakarov at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
To me it looks like IRA allocated memory for r83 here for whatever reason.
Well, for a cost reason:
a3(r83,l1) costs: SSE_REGS:19800,19800 MEM:11880,11880
not sure why though?
>From gcc-bugs-return-671474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 11:06:33 2020
Return-Path: <gcc-bugs-return-671474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46136 invoked by alias); 26 Feb 2020 11:06: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 46066 invoked by uid 48); 26 Feb 2020 11:06:20 -0000
From: "frederic.recoules@univ-grenoble-alpes.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93944] New: Undocumented side effect in operand evaluations
Date: Wed, 26 Feb 2020 11:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frederic.recoules@univ-grenoble-alpes.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-93944-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03056.txt.bz2
Content-length: 1606
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93944
Bug ID: 93944
Summary: Undocumented side effect in operand evaluations
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: inline-asm
Assignee: unassigned at gcc dot gnu.org
Reporter: frederic.recoules@univ-grenoble-alpes.fr
Target Milestone: ---
I would have said that I read somewhere that concurrent side effect in the
operands is an undefined behavior, but, I read the documentation
(Extended-Asm.html) again and I did not see any mention of this.
Here is a simple motivation example, it is the worst I can produce:
int *f (int *v, const char m[])
{
puts(m);
return v;
}
int main (int argc, char * argv[])
{
__asm__ ("leal 1(%2), %0" "\n\t"
"leal 2(%3), %1"
: "=&r" (*f(&argc, "0")),
"=r" (*f(&argc, "1"))
: "r" (*f(&argc, "2")),
"r" (*f(&argc, "3")));
return argc;
}
Here is what I could think for stdout:
- the behavior is totally undefined and the compiler will make demon fly out of
my nose
- inputs are evaluated before outputs (it could make sense) such 2 and 3 always
appear before 0 and 1 but the rest is undefined
- evaluation order is well defined and leads to "0123", the actual result with
gcc 9.2 (but I don't like it)
But also, lvalue argc takes "supposedly" the value of %0 and %1. I would think
it is an undefined behavior that will depend on compiler final register
allocation, it is?
>From gcc-bugs-return-671475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 11:09:01 2020
Return-Path: <gcc-bugs-return-671475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47668 invoked by alias); 26 Feb 2020 11:09: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 47610 invoked by uid 48); 26 Feb 2020 11:08:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93945] New: [9/10 Regression] memset of non-zero constant followed by bitfield read big-endian miscompilation since r9-547
Date: Wed, 26 Feb 2020 11:09: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: 9.2.1
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-93945-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03057.txt.bz2
Content-length: 1135
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93945
Bug ID: 93945
Summary: [9/10 Regression] memset of non-zero constant followed
by bitfield read big-endian miscompilation since
r9-547
Product: gcc
Version: 9.2.1
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: ---
I think since r9-547-gb72feab889cd7925fab59771269638fcc88bc195 we miscompile
following testcase on big-endian (verified on powerpc64-linux) at -O2:
union U { char a[8]; struct S { unsigned int b : 8, c : 13, d : 11; } e; } u;
__attribute__((noipa)) int
foo (void)
{
__builtin_memset (&u.a, 0xf4, sizeof (u.a));
return u.e.c;
}
__attribute__((noipa)) int
bar (void)
{
asm volatile ("" : : "g" (&u) : "memory");
return u.e.c;
}
int
main ()
{
int a = foo ();
__builtin_memset (&u.a, 0xf4, sizeof (u.a));
int b = bar ();
if (a != b)
__builtin_abort ();
return 0;
}
>From gcc-bugs-return-671476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 11:11:52 2020
Return-Path: <gcc-bugs-return-671476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49571 invoked by alias); 26 Feb 2020 11:11: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 49542 invoked by uid 48); 26 Feb 2020 11:11:46 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93942] [Extended-Asm] Last code snippet in 6.47.2.3 Output Operands is unsafe
Date: Wed, 26 Feb 2020 11:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.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-93942-4-gAB8hlCyMu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93942-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93942-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03058.txt.bz2
Content-length: 150
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93942
--- Comment #3 from Andreas Schwab <schwab@linux-m68k.org> ---
M68K has memory to memory moves.
>From gcc-bugs-return-671477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 11:13:26 2020
Return-Path: <gcc-bugs-return-671477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51770 invoked by alias); 26 Feb 2020 11:13: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 51730 invoked by uid 48); 26 Feb 2020 11:13:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93945] [9/10 Regression] memset of non-zero constant followed by bitfield read big-endian miscompilation since r9-547
Date: Wed, 26 Feb 2020 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: 9.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: keywords priority target_milestone
Message-ID: <bug-93945-4-eylASy7wJy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03059.txt.bz2
Content-length: 779
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93945
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Priority|P3 |P2
Target Milestone|--- |9.3
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
For 9.x, I think we need to require for that case that ref->size is a multiple
of BITS_PER_UNIT (and I must say I'm a little bit worried that for this
native_interpret_expr case we don't require that known_eq (ref->size,
maxsize)).
For the trunk, I'm actually working on support for arbitrary bitfield reads.
>From gcc-bugs-return-671478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 11:19:49 2020
Return-Path: <gcc-bugs-return-671478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95792 invoked by alias); 26 Feb 2020 11:19: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 95498 invoked by uid 48); 26 Feb 2020 11:19:35 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93945] [9/10 Regression] memset of non-zero constant followed by bitfield read big-endian miscompilation since r9-547
Date: Wed, 26 Feb 2020 11: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: 9.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-93945-4-Imw2GCs9BQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03060.txt.bz2
Content-length: 1942
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93945
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-26
CC| |pinskia at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
My bet is there missing the following somewhere:
+ if (BYTES_BIG_ENDIAN)
+ bitpos = TYPE_PRECISION (type) - bitpos - bitsize;
I have not looked where though. I do know BIT_INSERT_EXPR is broken with that
respect.
The following patch fixes that:
commit 7490f8e4f52d38d1ae265bec50ab518e86a53d19
Author: Andrew Pinski <apinski@marvell.com>
Date: Tue Dec 17 03:54:46 2019 +0000
Fix big-endian constant folding of BIT_INSERT_EXPR
Big-endian has a different idea of what bit order
should be compared to little-endian. This fixes
it by correcting the shift/mask to be in the correct
order.
Change-Id: I3e4ba3c27d62a20affd08100083cee5f921edc7d
Signed-off-by: Andrew Pinski <apinski@marvell.com>
diff --git a/gcc/fold-const.c b/gcc/fold-const.c
index aefa91666e2..f515d776c57 100644
--- a/gcc/fold-const.c
+++ b/gcc/fold-const.c
@@ -12506,6 +12506,8 @@ fold_ternary_loc (location_t loc, enum tree_code code,
tree type,
{
unsigned HOST_WIDE_INT bitpos = tree_to_uhwi (op2);
unsigned bitsize = TYPE_PRECISION (TREE_TYPE (arg1));
+ if (BYTES_BIG_ENDIAN)
+ bitpos = TYPE_PRECISION (type) - bitpos - bitsize;
wide_int tem = (wi::to_wide (arg0)
& wi::shifted_mask (bitpos, bitsize, true,
TYPE_PRECISION (type)));
>From gcc-bugs-return-671479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 11:20:09 2020
Return-Path: <gcc-bugs-return-671479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96599 invoked by alias); 26 Feb 2020 11:20: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 96440 invoked by uid 48); 26 Feb 2020 11:19:56 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93942] [Extended-Asm] Last code snippet in 6.47.2.3 Output Operands is unsafe
Date: Wed, 26 Feb 2020 11:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: unknown
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-93942-4-HPyRP4y94T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93942-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93942-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03061.txt.bz2
Content-length: 419
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93942
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Frédéric Recoules from comment #2)
> Yet, I may be too x86 oriented... as a matter of personal curiosity, do you
> known an architecture that allows such dual memory constraint?
Yes s390, mvc instruction:
http://www.simotime.com/asmins01.htm#MVC
Which GCC does emit even.
>From gcc-bugs-return-671480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 11:22:51 2020
Return-Path: <gcc-bugs-return-671480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98872 invoked by alias); 26 Feb 2020 11:22: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 98734 invoked by uid 48); 26 Feb 2020 11:22:38 -0000
From: "frederic.recoules@univ-grenoble-alpes.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93942] [Extended-Asm] Last code snippet in 6.47.2.3 Output Operands is unsafe
Date: Wed, 26 Feb 2020 11:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frederic.recoules@univ-grenoble-alpes.fr
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-93942-4-SG6K7yhGKn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93942-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93942-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03062.txt.bz2
Content-length: 498
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93942
Frédéric Recoules <frederic.recoules@univ-grenoble-alpes.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #5 from Frédéric Recoules <frederic.recoules@univ-grenoble-alpes.fr> ---
Thank you both.
>From gcc-bugs-return-671481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 11:25:42 2020
Return-Path: <gcc-bugs-return-671481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101163 invoked by alias); 26 Feb 2020 11:25: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 101020 invoked by uid 48); 26 Feb 2020 11:25:28 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93945] [9/10 Regression] memset of non-zero constant followed by bitfield read big-endian miscompilation since r9-547
Date: Wed, 26 Feb 2020 11: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: 9.2.1
X-Bugzilla-Keywords: 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: 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-93945-4-Wv1KtstFRh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03063.txt.bz2
Content-length: 406
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93945
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
For 9.x all we need is add && multiple_p (ref->size, BITS_PER_UNIT) because the
code doesn't attempt to handle loads or stores that aren't byte aligned and
whole byte sized.
I found this by code inspection when trying to add trunk support for arbitrary
load bit offset or ref->size.
>From gcc-bugs-return-671482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 11:27:06 2020
Return-Path: <gcc-bugs-return-671482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104671 invoked by alias); 26 Feb 2020 11:27: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 104637 invoked by uid 48); 26 Feb 2020 11:27:01 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93944] Undocumented side effect in operand evaluations
Date: Wed, 26 Feb 2020 11:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: accepts-invalid, documentation
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-93944-4-PaoYIZxQpI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93944-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93944-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03064.txt.bz2
Content-length: 963
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93944
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I think you could say there is no sequence points in the inline-asm; just as
there is none with most things in C. There for it is unspecified the order of
evulations of the function calls. Therefor the code is undefined. I don't
think we need to warn here (it is hard to warn due to the function call).
I don't think we need to document this either. The main reason because of the
sequence points and concurrent side effects in C is also undefined. Think of
an inline-asm as one statement and it goes to the same effect as that.
>From gcc-bugs-return-671483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 11:44:47 2020
Return-Path: <gcc-bugs-return-671483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116135 invoked by alias); 26 Feb 2020 11:44: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 116073 invoked by uid 48); 26 Feb 2020 11:44:34 -0000
From: "kito at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90811] [nvptx] ptxas error on OpenMP offloaded code
Date: Wed, 26 Feb 2020 11: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: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kito 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: cc
Message-ID: <bug-90811-4-rXdAuep8Cp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03065.txt.bz2
Content-length: 1601
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90811
Kito Cheng <kito at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kito at gcc dot gnu.org,
| |wilson at gcc dot gnu.org
--- Comment #15 from Kito Cheng <kito at gcc dot gnu.org> ---
RISC-V got fail after g:26d7a5e690169ac04acde90070b0092c41b71c7e for
gfortran.dg/pr45636.f90
It seems like because alignment change cause simplify_builtin_call can't
simplify memset to load/store.
The story for RISC-V here:
- simplify_builtin_call call can_store_by_pieces check it's OK to store by
pieces?
- can_store_by_pieces call targetm.use_by_pieces_infrastructure_p to ask
back-end
- targetm.use_by_pieces_infrastructure_p call by_pieces_ninsns to calculate how
many instruction needed, it was 1 for RV64*, because alignment is changed to 8
bits from 64 bits for char array due to this patch
g:26d7a5e690169ac04acde90070b0092c41b71c7e.
- by_pieces_ninsns got 4 instead of 1, and large than MOVE_RATIO, failed to
simplify memset to load/store.
- ARM (aarch32) seems like same story too.
* Configure option for RV64: --target=riscv64-unknown-linux-gnu
--with-arch=rv64gc --with-abi=lp64
Analysis:
- align_local_variable changed policy, only ask alignment info (SET_DECL_ALIGN)
from back-end only when expanding (expand pass).
- So that's cause cost measurement changed, because some cost measurement are
depend on the alignment.
>From gcc-bugs-return-671484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 11:52:01 2020
Return-Path: <gcc-bugs-return-671484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11119 invoked by alias); 26 Feb 2020 11:52: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 11042 invoked by uid 48); 26 Feb 2020 11:51:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90811] [nvptx] ptxas error on OpenMP offloaded code
Date: Wed, 26 Feb 2020 11: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: 8.3.1
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90811-4-M0Uc39zBIf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03066.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90811
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
estimate_stack_frame_size is definitely the wrong spot to change DECL_ALIGN of
variables, that is a routine for inlining heuristics and shouldn't have such
side-effects.
It can be done in some other pass of course, but for offloading to work
properly, that needs to be after IPA.
>From gcc-bugs-return-671485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 12:36:54 2020
Return-Path: <gcc-bugs-return-671485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104019 invoked by alias); 26 Feb 2020 12:36: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 103975 invoked by uid 48); 26 Feb 2020 12:36:49 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93681] Wrong optimization: instability of x87 floating-point results leads to nonsense
Date: Wed, 26 Feb 2020 12: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:
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-93681-4-w0kiFZQMOU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93681-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93681-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03067.txt.bz2
Content-length: 263
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93681
--- Comment #4 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
Instead of "-m32 -march=i686", one can also compile with "-mfpmath=387". This
is useful if one does not have the 32-bit libs.
>From gcc-bugs-return-671486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 12:39:13 2020
Return-Path: <gcc-bugs-return-671486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106870 invoked by alias); 26 Feb 2020 12:39: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 106830 invoked by uid 48); 26 Feb 2020 12:39:05 -0000
From: "stephane.goujet at wanadoo dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93910] -Waddress-of-packed-member triggered without actual access to a member or the address of a member
Date: Wed, 26 Feb 2020 12: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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: stephane.goujet at wanadoo 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:
Message-ID: <bug-93910-4-aA2oi7nt2K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93910-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93910-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03068.txt.bz2
Content-length: 1822
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93910
--- Comment #10 from stephane.goujet at wanadoo dot fr ---
(In reply to stephane.goujet from comment #9)
> 2. There are inconsistencies in the Warning:
Another inconsistency:
2.c The documentation of the packed attribute says "This attribute, attached to
a struct, [...] is equivalent to specifying the packed attribute on each of the
members." Well, guess what? Waddress-of-packed-member is triggered when the
attribute is at the struct level, but is not triggered when it is at members
level.
Example code:
---------------------------
# 1 "indiv2.c"
# 1 "<built-in>"
# 1 "<command-line>"
# 31 "<command-line>"
# 1 "/usr/include/stdc-predef.h" 1 3 4
# 32 "<command-line>" 2
# 1 "indiv2.c"
struct __attribute__((packed)) Sw {
char a;
int b;
};
struct Si {
char a __attribute__((packed));
int b __attribute__((packed));
};
int main(void) {
struct Sw sw;
struct Si si;
int * pw = (int *) &sw;
int * pi = (int *) &si;
return 0;
}
---------------------------
Compilation result (setting aside the Wattributes warning,
Waddress-of-packed-member warns for Sw, not for Si):
---------------------------
~/test/c/gcc9packed $LC_ALL=C gcc -Wextra indiv2.c -o indiv2_gcc -save-temps
indiv2.c:10:2: warning: 'packed' attribute ignored for field of type 'char'
[-Wattributes]
10 | char a __attribute__((packed));
| ^~~~
indiv2.c: In function 'main':
indiv2.c:18:2: warning: converting a packed 'struct Sw' pointer (alignment 1)
to a 'int' pointer (alignment 4) may result in an unaligned pointer value
[-Waddress-of-packed-member]
18 | int * pw = (int *) &sw;
| ^~~
indiv2.c:3:32: note: defined here
3 | struct __attribute__((packed)) Sw {
| ^~
---------------------------
>From gcc-bugs-return-671487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 12:49:23 2020
Return-Path: <gcc-bugs-return-671487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29638 invoked by alias); 26 Feb 2020 12: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 29343 invoked by uid 55); 26 Feb 2020 12:48:05 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93843] [10 Regression] wrong code at -O3 on x86_64-linux-gnu
Date: Wed, 26 Feb 2020 12: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93843-4-UwNhs4F63F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03069.txt.bz2
Content-length: 1251
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93843
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>:
https://gcc.gnu.org/g:b6268016bf46dd63227dcbb73d13c30a3b4b9d2a
commit r10-6863-gb6268016bf46dd63227dcbb73d13c30a3b4b9d2a
Author: Richard Sandiford <richard.sandiford@arm.com>
Date: Tue Feb 25 19:20:58 2020 +0000
optabs: Don't use scalar conversions for vectors [PR93843]
In this PR we had a conversion between two integer vectors that
both had scalar integer modes. We then tried to implement the
conversion using the scalar optab for those modes, instead of
doing the conversion elementwise.
I wondered about letting through scalar modes for single-element
vectors, but I don't have any evidence that that's useful/necessary,
so it seemed better to keep things simple.
2020-02-26 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR middle-end/93843
* optabs-tree.c (supportable_convert_operation): Reject types with
scalar modes.
gcc/testsuite/
PR middle-end/93843
* gcc.dg/vect/pr93843-1.c: New test.
* gcc.dg/vect/pr93843-2.c: Likewise.
>From gcc-bugs-return-671488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 12:50:46 2020
Return-Path: <gcc-bugs-return-671488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32862 invoked by alias); 26 Feb 2020 12:50: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 32759 invoked by uid 48); 26 Feb 2020 12:50:32 -0000
From: "frederic.recoules@univ-grenoble-alpes.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93944] Undocumented side effect in operand evaluations
Date: Wed, 26 Feb 2020 12:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: accepts-invalid, documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frederic.recoules@univ-grenoble-alpes.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_status resolution
Message-ID: <bug-93944-4-a25GJmXkBh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93944-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93944-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03070.txt.bz2
Content-length: 1541
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93944
Frédéric Recoules <frederic.recoules@univ-grenoble-alpes.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #2 from Frédéric Recoules <frederic.recoules@univ-grenoble-alpes.fr> ---
Let me disagree with you because, except if the documentation is intentionally
hard to avoid inexperienced people to use inline assembly, I would think that
omitting an "obvious" information despite the fact that somebody ask for it
seems to be against the purpose of a documentation.
That said, in C, I know 3 operators that introduce a sequence point: logical
and (&&), logical or (||) and comma (,).
The comma is particularly misleading because it is also used, at least, to
separate function parameters or compound values initializer where it don't
introduce sequence point.
Yet, an inline assembly statement uses both comas (,) and colons (:) and, as
far as I know, the latter are not used for a similar purpose in the C.
I feel it would be legitimate to ask the question of how they interact between
them since it is documented nowhere.
But hopefully, it will change, isn't it?
Disclaimer: I totally understand your point as I was thinking of it as a
function call anyway, but I hope you will forgive me for playing the devil's
advocate here.
>From gcc-bugs-return-671490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 12:51:06 2020
Return-Path: <gcc-bugs-return-671490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34179 invoked by alias); 26 Feb 2020 12:51: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 33568 invoked by uid 48); 26 Feb 2020 12:50:58 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93919] [10 Regression] vectorization of 18 char to char16_t conversion is miscompiled
Date: Wed, 26 Feb 2020 12:51: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: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo 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: bug_status resolution
Message-ID: <bug-93919-4-AUVglYujx0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93919-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93919-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03072.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93919
Bug 93919 depends on bug 93843, which changed state.
Bug 93843 Summary: [10 Regression] wrong code at -O3 on x86_64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93843
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-671489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 12:51:01 2020
Return-Path: <gcc-bugs-return-671489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33697 invoked by alias); 26 Feb 2020 12:51: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 33527 invoked by uid 48); 26 Feb 2020 12:50:56 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93843] [10 Regression] wrong code at -O3 on x86_64-linux-gnu
Date: Wed, 26 Feb 2020 12: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: 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-93843-4-G92afBxa2l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03071.txt.bz2
Content-length: 460
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93843
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 12:53:43 2020
Return-Path: <gcc-bugs-return-671491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50244 invoked by alias); 26 Feb 2020 12: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 50215 invoked by uid 48); 26 Feb 2020 12:53:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93946] New: Bogus redundant store removal
Date: Wed, 26 Feb 2020 12: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:
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-93946-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03073.txt.bz2
Content-length: 962
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93946
Bug ID: 93946
Summary: Bogus redundant store removal
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: ---
union U { long long i; long f; };
struct a {union U u;};
struct aa {struct a a;};
struct b {union U u;};
struct bb {struct b b;};
long
foo (struct bb *bv, void *ptr)
{
struct aa *a = ptr;
struct bb *b = ptr;
bv->b.u.f = 1;
a->a.u.i = 0;
b->b.u.f = 0;
return bv->b.u.f;
}
int
main ()
{
union C {struct aa aa; struct bb bb;} v;
if (foo (&v.bb, &v) != 0)
__builtin_abort ();
return 0;
}
we treat b->b.u.f = 0 as redundant because the alias-set of that and the
a->a.u.i = 0 store are actually the same.
>From gcc-bugs-return-671492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 12:55:02 2020
Return-Path: <gcc-bugs-return-671492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60304 invoked by alias); 26 Feb 2020 12:55: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 60128 invoked by uid 48); 26 Feb 2020 12:54:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93946] Bogus redundant store removal
Date: Wed, 26 Feb 2020 12: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:
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 cf_reconfirmed_on assigned_to everconfirmed cf_known_to_fail
Message-ID: <bug-93946-4-xWo1E8okAr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93946-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93946-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03074.txt.bz2
Content-length: 644
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93946
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-02-26
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |10.0, 4.8.5, 7.5.0, 9.2.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-671493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 12:58:29 2020
Return-Path: <gcc-bugs-return-671493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66169 invoked by alias); 26 Feb 2020 12:58: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 66116 invoked by uid 48); 26 Feb 2020 12:58:24 -0000
From: "thenlich at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Wed, 26 Feb 2020 12:58: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: thenlich at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-93871-4-MBJfS0fJtA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03075.txt.bz2
Content-length: 2248
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #26 from Thomas Henlich <thenlich at gcc dot gnu.org> ---
Created attachment 47914
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47914&action=edit
Demonstration of range reduction
There is a danger of some inaccuracy in the degree trigonometric functions
(sind, cosd, tand, cotand) because a full period of 360 degrees can not be
expressed accurately in radians.
This can be circumvented by using some trigonometric identities to reduce the
range and also place the inaccurate x range to where |dy/dx|→min, and away from
y values near zero toward high y values so that the error is mostly cancelled.
This is a best effort to still be able to use the standard library functions
but also get an increased accuracy expected from the degree functions.
Thus:
1. Calculate cosd(x) = sind(90 - x)
2. Calculate cotand(x) = tand(90 - x)
3. Reduce range of sind() argument from (0...360) further to x-360 if it is
above 270, and to 180-x if it is above 90
Considering the demonstration program:
$ gf10 -fdec-math periods.f90 && ./a.exe
cos( 90.0000000 )= -4.37113883E-08 0.00000000
sin( 180.000000 )= -8.74227766E-08 0.00000000
cos( 270.000000 )= 1.19248806E-08 0.00000000
sin( -360.000000 )= -0.00000000 0.00000000
sin( 36000000.0 )= 0.00000000 0.00000000
sin( 36000180.0 )= -8.74227766E-08 0.00000000
cotan( 90.0000000 )= -4.37113883E-08 0.00000000
$ gf10 -fdec-math -fdefault-real-8 periods.f90 && ./a.exe
cos( 90.000000000000000 )= 6.1230317691118863E-017 0.0000000000000000
sin( 180.00000000000000 )= 1.2246063538223773E-016 0.0000000000000000
cos( 270.00000000000000 )= -1.8369095307335659E-016 0.0000000000000000
sin( -360.00000000000000 )= -0.0000000000000000 0.0000000000000000
sin( 36000000.000000000 )= 0.0000000000000000 0.0000000000000000
sin( 36000180.000000000 )= 1.2246063538223773E-016 0.0000000000000000
cotan( 90.000000000000000 )= 6.1230317691118863E-017 0.0000000000000000
showing that values for all multiples of 90 degrees can be computed to be
exactly zero.
>From gcc-bugs-return-671494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 13:01:35 2020
Return-Path: <gcc-bugs-return-671494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69082 invoked by alias); 26 Feb 2020 13:01: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 68732 invoked by uid 48); 26 Feb 2020 13:01:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93945] [9/10 Regression] memset of non-zero constant followed by bitfield read big-endian miscompilation since r9-547
Date: Wed, 26 Feb 2020 13: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: 9.2.1
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: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-93945-4-KSuYFRBXDN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03076.txt.bz2
Content-length: 587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93945
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 #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47915
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47915&action=edit
gcc10-pr93945.patch
Untested trunk patch.
>From gcc-bugs-return-671495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 13:04:47 2020
Return-Path: <gcc-bugs-return-671495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73353 invoked by alias); 26 Feb 2020 13:04: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 73307 invoked by uid 48); 26 Feb 2020 13:04:42 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93947] New: ICE: Segmentation fault (in symtab_node::ultimate_alias_target)
Date: Wed, 26 Feb 2020 13:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
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: dmalcolm 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-93947-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03077.txt.bz2
Content-length: 3233
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93947
Bug ID: 93947
Summary: ICE: Segmentation fault (in
symtab_node::ultimate_alias_target)
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
gcc-10.0.1-alpha20200223 snapshot (g:3133bed5d0327e8a9cd0a601b7ecdb9de4fc825d)
ICEs when compiling the following testcase, reduced from
gcc/testsuite/gcc.target/arm/thumb1-ual-1.c, w/ -O1 -fanalyzer:
struct pf {
unsigned int iu : 2;
};
enum {
qr, jv, vm, mz,
};
int uh;
void
w9 (struct pf *x2)
{
switch (x2->iu)
{
case qr:
case jv:
case vm:
uh = 0;
break;
case mz:
break;
default:
__builtin_abort ();
}
}
% gcc-10.0.1 -O1 -fanalyzer -c tsdnvtnl.c
during IPA pass: analyzer
tsdnvtnl.c: In function 'w9':
tsdnvtnl.c:25:5: internal compiler error: Segmentation fault
25 | default:
| ^~~~~~~
0xd8ba2f crash_signal
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/toplev.c:328
0x110d1c1 symtab_node::ultimate_alias_target(availability*, symtab_node*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/cgraph.h:3242
0x110d1c1 cgraph_node::ultimate_alias_target(availability*, symtab_node*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/cgraph.h:3263
0x110d1c1 ana::region_model::get_fndecl_for_call(gcall const*,
ana::region_model_context*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/region-model.cc:6713
0x11113fb ana::region_model::on_call_pre(gcall const*,
ana::region_model_context*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/region-model.cc:4175
0x10eab58 ana::exploded_node::on_stmt(ana::exploded_graph&, ana::supernode
const*, gimple const*, ana::program_state*, ana::state_change*) const
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/engine.cc:1068
0x10eb0e1 ana::exploded_graph::process_node(ana::exploded_node*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/engine.cc:2492
0x10eb5ca ana::exploded_graph::process_worklist()
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/engine.cc:2310
0x10ebcf9 ana::impl_run_checkers(ana::logger*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/engine.cc:3670
0x10ec79c ana::run_checkers()
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/engine.cc:3727
0x10e1ef8 execute
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/analyzer/analyzer-pass.cc:84
>From gcc-bugs-return-671496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 13:10:24 2020
Return-Path: <gcc-bugs-return-671496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26413 invoked by alias); 26 Feb 2020 13:10: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 11039 invoked by uid 55); 26 Feb 2020 13:10:17 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/81091] libstdc++ not built with large file support
Date: Wed, 26 Feb 2020 13:10: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81091-4-3Lq72TMCGd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81091-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81091-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03078.txt.bz2
Content-length: 1907
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81091
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:56b6c2ba3a45c768a33f726b130a56fc19cca650
commit r8-10084-g56b6c2ba3a45c768a33f726b130a56fc19cca650
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Jan 9 13:38:43 2020 +0000
Build filesystem library with large file support
Enable AC_SYS_LARGEFILE to set the macros needed for large file APIs to
be used by default. We do not want to define those macros in the
public headers that users include. The values of the macros are copied
to a separate file that is only included by the filesystem sources
during the build, and then the macros in <bits/c++config.h> are renamed
so that they don't have any effect in user code including our headers.
Also use larger type for result of filesystem::file_size to avoid
truncation of large values on 32-bit systems (PR 91947).
Backport from mainlne
2019-10-04 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/81091
PR libstdc++/91947
* configure.ac: Use AC_SYS_LARGEFILE to enable 64-bit file APIs.
* config.h.in: Regenerate:
* configure: Regenerate:
* include/Makefile.am (${host_builddir}/largefile-config.h): New
target to generate config header for filesystem library.
(${host_builddir}/c++config.h): Rename macros for large file support.
* include/Makefile.in: Regenerate.
* src/c++17/fs_dir.cc: Include new config header.
* src/c++17/fs_ops.cc: Likewise.
(filesystem::file_size): Use uintmax_t for size.
* src/filesystem/dir.cc: Include new config header.
* src/filesystem/ops.cc: Likewise.
(experimental::filesystem::file_size): Use uintmax_t for size.
>From gcc-bugs-return-671500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 13:10:46 2020
Return-Path: <gcc-bugs-return-671500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28554 invoked by alias); 26 Feb 2020 13:10: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 27578 invoked by uid 55); 26 Feb 2020 13:10:32 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/78552] std::locale::classic() Needless Race
Date: Wed, 26 Feb 2020 13:10: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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-78552-4-7eZEIIWqLt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78552-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78552-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03082.txt.bz2
Content-length: 774
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78552
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:26b070a3f6e5c7ccee7491fb758dba4c72bd7026
commit r8-10086-g26b070a3f6e5c7ccee7491fb758dba4c72bd7026
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Feb 26 09:43:59 2020 +0000
PR libstdc++/78552 only construct std::locale for C locale once
Backport from mainline
2019-10-09 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/78552
* src/c++98/locale_init.cc (locale::classic()): Do not construct a new
locale object for every call.
(locale::_S_initialize_once()): Construct C locale here.
>From gcc-bugs-return-671498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 13:10:28 2020
Return-Path: <gcc-bugs-return-671498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26998 invoked by alias); 26 Feb 2020 13:10: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 26155 invoked by uid 55); 26 Feb 2020 13:10:23 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/91947] std::filesystem::file_size will return wrong value on 32bit platforms with large files support
Date: Wed, 26 Feb 2020 13:10: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: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91947-4-Up5fK5Z2VD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91947-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03079.txt.bz2
Content-length: 1291
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91947
--- Comment #21 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:761696abfe0a772315449e3d2b57de76756f5953
commit r8-10085-g761696abfe0a772315449e3d2b57de76756f5953
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Fri Jan 24 11:13:55 2020 +0000
libstdc++: Simplify makefile rule for largefile-config.h (PR91947)
The previous rule could leave an incomplete file if the build was
interrupted, which would then not be remade if make was run again.
This makes the rule more robust by writing to a temporary file and only
moving it into place as the final step. It also simplifies the rule so
that only the essential macro definitions are written to the file, not
the explanatory comments and commented out #undef lines.
Also, the macro for enabling LFS on Mac OS X 10.5 is now set
unconditionally, which is a bug fix from upstream autoconf.
Backport from mainline
2020-01-23 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/91947
* include/Makefile.am (${host_builddir}/largefile-config.h): Simplify
rule.
* include/Makefile.in: Regenerate.
>From gcc-bugs-return-671497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 13:10:24 2020
Return-Path: <gcc-bugs-return-671497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26427 invoked by alias); 26 Feb 2020 13:10: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 11246 invoked by uid 55); 26 Feb 2020 13:10:17 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/91947] std::filesystem::file_size will return wrong value on 32bit platforms with large files support
Date: Wed, 26 Feb 2020 13:10: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: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91947-4-Sl2pE7VH6K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91947-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03081.txt.bz2
Content-length: 1908
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91947
--- Comment #20 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:56b6c2ba3a45c768a33f726b130a56fc19cca650
commit r8-10084-g56b6c2ba3a45c768a33f726b130a56fc19cca650
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Jan 9 13:38:43 2020 +0000
Build filesystem library with large file support
Enable AC_SYS_LARGEFILE to set the macros needed for large file APIs to
be used by default. We do not want to define those macros in the
public headers that users include. The values of the macros are copied
to a separate file that is only included by the filesystem sources
during the build, and then the macros in <bits/c++config.h> are renamed
so that they don't have any effect in user code including our headers.
Also use larger type for result of filesystem::file_size to avoid
truncation of large values on 32-bit systems (PR 91947).
Backport from mainlne
2019-10-04 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/81091
PR libstdc++/91947
* configure.ac: Use AC_SYS_LARGEFILE to enable 64-bit file APIs.
* config.h.in: Regenerate:
* configure: Regenerate:
* include/Makefile.am (${host_builddir}/largefile-config.h): New
target to generate config header for filesystem library.
(${host_builddir}/c++config.h): Rename macros for large file support.
* include/Makefile.in: Regenerate.
* src/c++17/fs_dir.cc: Include new config header.
* src/c++17/fs_ops.cc: Likewise.
(filesystem::file_size): Use uintmax_t for size.
* src/filesystem/dir.cc: Include new config header.
* src/filesystem/ops.cc: Likewise.
(experimental::filesystem::file_size): Use uintmax_t for size.
>From gcc-bugs-return-671499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 13:10:45 2020
Return-Path: <gcc-bugs-return-671499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28418 invoked by alias); 26 Feb 2020 13:10: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 28384 invoked by uid 48); 26 Feb 2020 13:10:40 -0000
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93936] [ranges] std::ranges::split_view<...>::_OuterIter<...>::__current() is private within this context
Date: Wed, 26 Feb 2020 13:10: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: ppalka at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ppalka 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-93936-4-Z8ylcCsli5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93936-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03080.txt.bz2
Content-length: 561
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93936
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-26
CC| |ppalka at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |ppalka at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-671501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 13:16:21 2020
Return-Path: <gcc-bugs-return-671501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89151 invoked by alias); 26 Feb 2020 13:16: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 89111 invoked by uid 48); 26 Feb 2020 13:16:10 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93944] Undocumented side effect in operand evaluations
Date: Wed, 26 Feb 2020 13:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: accepts-invalid, documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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 cc resolution
Message-ID: <bug-93944-4-Qo2sGbLoge@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93944-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93944-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03083.txt.bz2
Content-length: 877
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93944
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |jakub at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The way sequence points are defined in C, it needs to be explicitly said where
there is a sequence point, and as we don't say anything for the inline asm
operands, that means there is no sequence point in between them.
It really doesn't matter what token is used to separate the operands, in C/C++
it is the comma operator which has a sequence point in between the two
expression.
>From gcc-bugs-return-671502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 13:44:15 2020
Return-Path: <gcc-bugs-return-671502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92671 invoked by alias); 26 Feb 2020 13:44: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 92656 invoked by uid 48); 26 Feb 2020 13:44:06 -0000
From: "thenlich at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93948] New: Surprising option processing of -fdec and -fdec-math in combination with -std
Date: Wed, 26 Feb 2020 13: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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: thenlich 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-93948-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03084.txt.bz2
Content-length: 1202
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93948
Bug ID: 93948
Summary: Surprising option processing of -fdec and -fdec-math
in combination with -std
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: thenlich at gcc dot gnu.org
Target Milestone: ---
It is surprising that the -std option leads to the -fdec-math option to be
silently ignored, while the -fdec option is honoured.
This makes it hard to enforce standard-compliant code while allowing only the
small subset of the DEC math extensions.
For example
====
program dec1
print "(g0)", sind(0.)
end program
====
$ gf10 -std=f2008 dec1.f90 && ./a.exe
cco91hFa.o:dec1.f90:(.text+0x57): undefined reference to `sind_'
$ gf10 -std=f2008 -fdec dec1.f90 && ./a.exe
0.00000000
$ gf10 -std=f2008 -fdec-math dec1.f90 && ./a.exe
cc6E3irl.o:dec1.f90:(.text+0x57): undefined reference to `sind_'
collect2.exe: error: ld returned 1 exit status
$ gf10 -fdec-math dec1.f90 && ./a.exe
0.00000000
>From gcc-bugs-return-671503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 13:44:43 2020
Return-Path: <gcc-bugs-return-671503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93457 invoked by alias); 26 Feb 2020 13:44: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 93419 invoked by uid 48); 26 Feb 2020 13:44:39 -0000
From: "thenlich at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93948] Surprising option processing of -fdec and -fdec-math in combination with -std
Date: Wed, 26 Feb 2020 13: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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: thenlich 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-93948-4-XFqhwwsIcA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93948-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93948-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03085.txt.bz2
Content-length: 296
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93948
Thomas Henlich <thenlich at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |minor
>From gcc-bugs-return-671504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:00:46 2020
Return-Path: <gcc-bugs-return-671504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73803 invoked by alias); 26 Feb 2020 14:00: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 73501 invoked by uid 48); 26 Feb 2020 14:00:20 -0000
From: "frederic.recoules@univ-grenoble-alpes.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93944] Undocumented side effect in operand evaluations
Date: Wed, 26 Feb 2020 14:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: accepts-invalid, documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frederic.recoules@univ-grenoble-alpes.fr
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-93944-4-17J8PBypAu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93944-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93944-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03086.txt.bz2
Content-length: 335
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93944
--- Comment #4 from Frédéric Recoules <frederic.recoules@univ-grenoble-alpes.fr> ---
I do apologise for the inconvenience, but I am still really convinced that an
explicit note wouldn't hurt so much.
At least I've learned something today and I am thankful for that.
>From gcc-bugs-return-671505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:09:45 2020
Return-Path: <gcc-bugs-return-671505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115185 invoked by alias); 26 Feb 2020 14:09: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 115143 invoked by uid 48); 26 Feb 2020 14:09:40 -0000
From: "joel.hutton at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92922] [10 regression] [ilp32] FAIL: gcc.target/aarch64/sve/acle/asm/ldnt1_u32.c -stdÉ0 -O1 -g -DTEST_FULL (internal compiler error)
Date: Wed, 26 Feb 2020 14:09: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: joel.hutton at arm 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92922-4-ep5eaVKI45@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92922-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92922-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03087.txt.bz2
Content-length: 414
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92922
Joel Hutton <joel.hutton at arm dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |joel.hutton at arm dot com
--- Comment #1 from Joel Hutton <joel.hutton at arm dot com> ---
This appears to be fixed on trunk.
>From gcc-bugs-return-671506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:14:46 2020
Return-Path: <gcc-bugs-return-671506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118142 invoked by alias); 26 Feb 2020 14: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 118061 invoked by uid 48); 26 Feb 2020 14:14:27 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93938] ICE in validate, at analyzer/region-model.cc:231
Date: Wed, 26 Feb 2020 14:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-93938-4-gu1D4eozOd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93938-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93938-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03088.txt.bz2
Content-length: 497
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93938
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-02-26
Ever confirmed|0 |1
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Confirmed; thanks.
>From gcc-bugs-return-671507-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:21:00 2020
Return-Path: <gcc-bugs-return-671507-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124307 invoked by alias); 26 Feb 2020 14:20: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 124216 invoked by uid 55); 26 Feb 2020 14:20:44 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/78552] std::locale::classic() Needless Race
Date: Wed, 26 Feb 2020 14:20: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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-78552-4-R70Q3zMpO5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78552-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78552-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03089.txt.bz2
Content-length: 773
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78552
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:84a5534ce2f8233e6fe9c957ec51a2328bfe60e3
commit r9-8283-g84a5534ce2f8233e6fe9c957ec51a2328bfe60e3
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Feb 26 14:00:07 2020 +0000
PR libstdc++/78552 only construct std::locale for C locale once
Backport from mainline
2019-10-09 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/78552
* src/c++98/locale_init.cc (locale::classic()): Do not construct a new
locale object for every call.
(locale::_S_initialize_once()): Construct C locale here.
>From gcc-bugs-return-671508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:26:23 2020
Return-Path: <gcc-bugs-return-671508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6214 invoked by alias); 26 Feb 2020 14:26: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 6173 invoked by uid 48); 26 Feb 2020 14:26:19 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/78552] std::locale::classic() Needless Race
Date: Wed, 26 Feb 2020 14:26: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:
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: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-78552-4-hseHhryJPL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78552-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78552-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03090.txt.bz2
Content-length: 385
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78552
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|10.0 |8.4
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Also fixed for 8.4 and 9.3
>From gcc-bugs-return-671509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:29:13 2020
Return-Path: <gcc-bugs-return-671509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10234 invoked by alias); 26 Feb 2020 14: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 10188 invoked by uid 48); 26 Feb 2020 14:29:05 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93808] [9 Regression] [SH] Ruby crashes with 'Illegal Instruction' with -fcrossjumping
Date: Wed, 26 Feb 2020 14: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: olegendo 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:
Message-ID: <bug-93808-4-TerMbnjTwb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93808-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93808-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03091.txt.bz2
Content-length: 205
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93808
--- Comment #24 from Oleg Endo <olegendo at gcc dot gnu.org> ---
Adrian, have you had a chance to apply the test patch in comment #22 and re-run
it?
>From gcc-bugs-return-671510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:32:58 2020
Return-Path: <gcc-bugs-return-671510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31416 invoked by alias); 26 Feb 2020 14:32: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 31360 invoked by uid 48); 26 Feb 2020 14:32:50 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93808] [9 Regression] [SH] Ruby crashes with 'Illegal Instruction' with -fcrossjumping
Date: Wed, 26 Feb 2020 14:32: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.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: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93808-4-zRJOxZEBFd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93808-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93808-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03092.txt.bz2
Content-length: 333
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93808
--- Comment #25 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Oleg Endo from comment #24)
> Adrian, have you had a chance to apply the test patch in comment #22 and
> re-run it?
I hadn't seen this patch, sorry. I will try that tonight.
>From gcc-bugs-return-671511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:33:56 2020
Return-Path: <gcc-bugs-return-671511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32943 invoked by alias); 26 Feb 2020 14:33: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 32874 invoked by uid 48); 26 Feb 2020 14:33:52 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89831] [8 Regression] passing 'const ...' as 'this' argument discards qualifiers
Date: Wed, 26 Feb 2020 14: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.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-89831-4-yEoW6rIN8T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03093.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89831
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:33:59 2020
Return-Path: <gcc-bugs-return-671512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33331 invoked by alias); 26 Feb 2020 14:33: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 32793 invoked by uid 55); 26 Feb 2020 14:33:45 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92376] [8/9 Regression] bootstrap fails with --disable-hosted-libstdcxx
Date: Wed, 26 Feb 2020 14:33: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: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92376-4-qGqgRejnEs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92376-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92376-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03094.txt.bz2
Content-length: 1045
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92376
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:1b522a79133037f04c8ffcdfbe6c885ccb3ddcd3
commit r9-8284-g1b522a79133037f04c8ffcdfbe6c885ccb3ddcd3
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Feb 26 14:20:55 2020 +0000
libstdc++: Fix freestanding build (PR 92376)
In a freestanding library we don't install the <pstl/pstl_config.h>
header, so don't try to include it unless it exists.
Explicitly declare aligned alloc functions for freestanding, because
<cstdlib> doesn't declare them.
Backport from mainline
2020-01-17 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/92376
* include/bits/c++config: Only do PSTL config when the header is
present, to fix freestanding.
* libsupc++/new_opa.cc [!_GLIBCXX_HOSTED]: Declare allocation
functions if they were detected by configure.
>From gcc-bugs-return-671513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:36:06 2020
Return-Path: <gcc-bugs-return-671513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40121 invoked by alias); 26 Feb 2020 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 40065 invoked by uid 48); 26 Feb 2020 14:36:01 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55212] [SH] Switch to LRA
Date: Wed, 26 Feb 2020 14:36: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: normal
X-Bugzilla-Who: olegendo 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-55212-4-adbBgjnreE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55212-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55212-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03095.txt.bz2
Content-length: 892
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #125 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to John Paul Adrian Glaubitz from comment #122)
>
> The build process is. Fixing broken packages isn't.
>
> Everything is around 13.000 source packages.
>
> And, finally, the buildd capacity is limited on sh4. If this was POWER or
> SPARC, we would have plenty of resources for a complete rebuild.
Can you at least please try to check if the kernel builds & runs OK?
As for the other packages, is there a way to let it just try to rebuild
everything and get a list of the packages that failed to build. We don't need
to sit down and fix all issues one by one for now. At least we can compare the
list against the current list of non-building packages. If the difference is
not too big, we can consider turning on LRA by default from GCC 10 on.
>From gcc-bugs-return-671514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:37:54 2020
Return-Path: <gcc-bugs-return-671514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69602 invoked by alias); 26 Feb 2020 14:37: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 63127 invoked by uid 48); 26 Feb 2020 14:37:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93905] [8 Regression] Cannot use Derived type of Base containing both enum and protected destructor
Date: Wed, 26 Feb 2020 14: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: 8.3.1
X-Bugzilla-Keywords: rejects-valid
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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93905-4-H811QRyLJR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93905-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03096.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93905
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.4+.
>From gcc-bugs-return-671515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:40:55 2020
Return-Path: <gcc-bugs-return-671515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126742 invoked by alias); 26 Feb 2020 14:40: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 126634 invoked by uid 48); 26 Feb 2020 14:40:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93059] char and char8_t does not talk with each other with memcpy. std::copy std::copy_n, std::fill, std::fill_n, std::uninitialized_copy std::uninitialized_copy_n, std::fill, std::uninitialized_fill_n fails to convert to memxxx functions
Date: Wed, 26 Feb 2020 14:40: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: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-93059-4-PbO5DIwFf0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03097.txt.bz2
Content-length: 1658
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93059
--- Comment #35 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Bernd Edlinger from comment #26)
> (In reply to fdlbxtqi from comment #2)
> > Also find a bug of __memmove
> >
> > /*
> > * A constexpr wrapper for __builtin_memmove.
> > * @param __num The number of elements of type _Tp (not bytes).
> > */
> > template<bool _IsMove, typename _Tp>
> > _GLIBCXX14_CONSTEXPR
> > inline void*
> > __memmove(_Tp* __dst, const _Tp* __src, size_t __num)
> > {
> > #ifdef __cpp_lib_is_constant_evaluated
> > if (std::is_constant_evaluated())
> > {
> > for(; __num > 0; --__num)
> > {
> > if constexpr (_IsMove)
> > *__dst = std::move(*__src);
> > else
> > *__dst = *__src;
> > ++__src;
> > ++__dst;
> > }
> > return __dst;
> > }
> > else
> > #endif
> > return __builtin_memmove(__dst, __src, sizeof(_Tp) * __num);
> > return __dst;
> > }
> >
> > The last 2nd line return __dst is wrong. It should not exist.
>
> Sorry, I don't know what this function is all about.
> But to me the code in the ifdef looks totally bogus.
> First it returns __dst+__num, while memmove is sopposed
> to return __dst, and is is somehow clear that
> __dst and __src do not overlap?
Yes, it was only used by std::copy and std::move and they require that __dst is
not in the range [__src, __src+__num). It's allowed for __dst+__num to be in
that range, but the function works correctly in that case anyway.
The return value wasn't used.
But I've removed the entire function, so it doesn't matter now.
>From gcc-bugs-return-671516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:44:49 2020
Return-Path: <gcc-bugs-return-671516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4249 invoked by alias); 26 Feb 2020 14:44: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 3612 invoked by uid 48); 26 Feb 2020 14:44:40 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93947] ICE: Segmentation fault (in symtab_node::ultimate_alias_target)
Date: Wed, 26 Feb 2020 14:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-93947-4-GzXZ9qCydJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93947-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03098.txt.bz2
Content-length: 497
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93947
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-02-26
Ever confirmed|0 |1
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Confirmed; thanks.
>From gcc-bugs-return-671517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:47:47 2020
Return-Path: <gcc-bugs-return-671517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7037 invoked by alias); 26 Feb 2020 14:46: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 6770 invoked by uid 48); 26 Feb 2020 14:46:27 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93877] [9/10 Regression] [SH] webkit2gtk fails to build with "internal compiler error: in extract_constrain_insn, at recog.c:2211"
Date: Wed, 26 Feb 2020 14: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: 9.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: olegendo 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:
Message-ID: <bug-93877-4-DoS0nWc36y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03099.txt.bz2
Content-length: 304
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93877
--- Comment #10 from Oleg Endo <olegendo at gcc dot gnu.org> ---
I can't reproduce the first case with a standalone sh-elf compiler (GCC 9).
The compile flags mention
-specs=/usr/share/dpkg/pie-compile.specs
... what's in that specs file?
>From gcc-bugs-return-671518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:49:24 2020
Return-Path: <gcc-bugs-return-671518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8722 invoked by alias); 26 Feb 2020 14:48: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 7618 invoked by uid 48); 26 Feb 2020 14:47:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92376] [8/9 Regression] bootstrap fails with --disable-hosted-libstdcxx
Date: Wed, 26 Feb 2020 14:48: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: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92376-4-WXDfsizuQW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92376-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92376-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03100.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92376
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for 8.4 and 9.3 too.
>From gcc-bugs-return-671519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:49:54 2020
Return-Path: <gcc-bugs-return-671519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11229 invoked by alias); 26 Feb 2020 14:49: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 9187 invoked by uid 55); 26 Feb 2020 14:48:55 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92376] [8/9 Regression] bootstrap fails with --disable-hosted-libstdcxx
Date: Wed, 26 Feb 2020 14:49: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: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92376-4-jDYht3wbav@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92376-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92376-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03101.txt.bz2
Content-length: 805
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92376
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:499ea2e31fba0ff6e4492f0a62e3ffb2bdba465e
commit r8-10087-g499ea2e31fba0ff6e4492f0a62e3ffb2bdba465e
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Feb 26 14:20:55 2020 +0000
libstdc++: Fix freestanding build (PR 92376)
Explicitly declare aligned alloc functions for freestanding, because
<cstdlib> doesn't declare them.
Backport from mainline
2020-01-17 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/92376
* libsupc++/new_opa.cc [!_GLIBCXX_HOSTED]: Declare allocation
functions if they were detected by configure.
>From gcc-bugs-return-671520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:50:39 2020
Return-Path: <gcc-bugs-return-671520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12768 invoked by alias); 26 Feb 2020 14:50: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 12680 invoked by uid 48); 26 Feb 2020 14:50:32 -0000
From: "jrtc27 at jrtc27 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93877] [9/10 Regression] [SH] webkit2gtk fails to build with "internal compiler error: in extract_constrain_insn, at recog.c:2211"
Date: Wed, 26 Feb 2020 14: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: 9.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jrtc27 at jrtc27 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.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93877-4-uQcI85WHfL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03102.txt.bz2
Content-length: 645
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93877
--- Comment #11 from James Clarke <jrtc27 at jrtc27 dot com> ---
(In reply to Oleg Endo from comment #10)
> I can't reproduce the first case with a standalone sh-elf compiler (GCC 9).
>
> The compile flags mention
>
> -specs=/usr/share/dpkg/pie-compile.specs
>
> ... what's in that specs file?
(sid-sh4-sbuild)root@sh4-gandi-02:~# cat /usr/share/dpkg/pie-compile.specs
*self_spec:
+
%{!r:%{!fpie:%{!fPIE:%{!fpic:%{!fPIC:%{!fno-pic:%{!fno-PIE:%{!no-pie:-fPIE}}}}}}}}
So, since -fPIC is provided on the command line already, it shouldn't be doing
anything.
>From gcc-bugs-return-671521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:51:24 2020
Return-Path: <gcc-bugs-return-671521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13635 invoked by alias); 26 Feb 2020 14:51: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 13553 invoked by uid 48); 26 Feb 2020 14:51:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93812] [9/10 Regression] ICE in get_constant, at c-family/c-format.c:325
Date: Wed, 26 Feb 2020 14: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: 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: P2
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-93812-4-VpxNEEI0Al@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03103.txt.bz2
Content-length: 545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93812
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> ---
__attribute__((__format__(__printf__, 1, 2))) void foo ();
void foo (void);
void
bar (void)
{
foo ();
}
ICEs too, no need for nested prototypes or recursive calls.
>From gcc-bugs-return-671522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:55:02 2020
Return-Path: <gcc-bugs-return-671522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49656 invoked by alias); 26 Feb 2020 14: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 49357 invoked by uid 48); 26 Feb 2020 14:54:57 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86521] [8 Regression] GCC 8 selects incorrect overload of ref-qualified conversion operator template
Date: Wed, 26 Feb 2020 14: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: 8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86521-4-xR86nfYdlW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03104.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86521
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #17 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4+.
>From gcc-bugs-return-671523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:55:03 2020
Return-Path: <gcc-bugs-return-671523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49703 invoked by alias); 26 Feb 2020 14: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 49388 invoked by uid 48); 26 Feb 2020 14:54:58 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90546] [9/10 Regression] Incorrect template argument deduction for conversion functions
Date: Wed, 26 Feb 2020 14:55: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.1.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-90546-4-n9OSt6QKYJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90546-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90546-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03105.txt.bz2
Content-length: 521
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90546
Bug 90546 depends on bug 86521, which changed state.
Bug 86521 Summary: [8 Regression] GCC 8 selects incorrect overload of ref-qualified conversion operator template
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86521
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-671524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 14:57:04 2020
Return-Path: <gcc-bugs-return-671524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92997 invoked by alias); 26 Feb 2020 14:57: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 92918 invoked by uid 48); 26 Feb 2020 14:56:57 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88380] [8 Regression] Sequence of not-explicitly initialised, initialised, variable length generates no initialiser
Date: Wed, 26 Feb 2020 14: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: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88380-4-F1nr9EB7zN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88380-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88380-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03106.txt.bz2
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88380
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4+.
>From gcc-bugs-return-671525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:00:44 2020
Return-Path: <gcc-bugs-return-671525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38451 invoked by alias); 26 Feb 2020 15:00: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 35977 invoked by uid 48); 26 Feb 2020 15:00:00 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93059] char and char8_t does not talk with each other with memcpy. std::copy std::copy_n, std::fill, std::fill_n, std::uninitialized_copy std::uninitialized_copy_n, std::fill, std::uninitialized_fill_n fails to convert to memxxx functions
Date: Wed, 26 Feb 2020 15:00: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: missed-optimization
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 everconfirmed
Message-ID: <bug-93059-4-0zVGsnBa7B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03107.txt.bz2
Content-length: 1116
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93059
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-26
Ever confirmed|0 |1
--- Comment #36 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Patches should be sent to the mailing list, and a copyright assignment (or
public domain disclaimer) would be needed for a patch of this size. Otherwise,
leave it to me to do once we start the GCC 11 dev phase.
Adding checks for types satisfying contiguous_iterator looks worthwhile, but
should be a separate patch.
I think the condition for using memmove should be something like:
__are_same<_ValueTypeI, _ValueTypeO>::__value
|| (__is_integer<_ValueTypeI>::__value
&& __is_integer<_ValueTypeo>::__value
&& sizeof(_ValueTypeI) == sizeof(_ValueTypeO))
>From gcc-bugs-return-671526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:02:07 2020
Return-Path: <gcc-bugs-return-671526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39880 invoked by alias); 26 Feb 2020 15:02: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 39839 invoked by uid 48); 26 Feb 2020 15:02:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93059] char and char8_t does not talk with each other with memcpy. std::copy std::copy_n, std::fill, std::fill_n, std::uninitialized_copy std::uninitialized_copy_n, std::fill, std::uninitialized_fill_n fails to convert to memxxx functions
Date: Wed, 26 Feb 2020 15:02: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: missed-optimization
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: 11.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget target_milestone
Message-ID: <bug-93059-4-M1dvwJXeui@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03108.txt.bz2
Content-length: 342
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93059
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|gcc 10.0 |
Target Milestone|--- |11.0
>From gcc-bugs-return-671527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:03:05 2020
Return-Path: <gcc-bugs-return-671527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41419 invoked by alias); 26 Feb 2020 15:03: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 41360 invoked by uid 55); 26 Feb 2020 15:03:01 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93803] [10 Regression] ICE: segmentation fault with constant initialization of class having a [[no_unique_address]] field
Date: Wed, 26 Feb 2020 15: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: ice-on-valid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93803-4-uCWd5lhs8E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03109.txt.bz2
Content-length: 1682
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93803
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:
https://gcc.gnu.org/g:d6ff22074126d38829f25981de9d6940cd2a234c
commit r10-6865-gd6ff22074126d38829f25981de9d6940cd2a234c
Author: Marek Polacek <polacek@redhat.com>
Date: Mon Feb 24 09:19:01 2020 -0500
c++: Fix ICE with constexpr init and [[no_unique_address]] [PR93803]
Here we crash when constexpr-initializing a class member of empty class
type with [[no_unique_address]]. Without the attribute we would have
a ctor (that initializes bar) of the form
{ .D.2173 = { .x = {} } }
but with the attribute reduced_constant_expression_p gets
{ .x = {} }
That means that "idx != field" is true for the latter and we see that
foo, the base class of bar, is an empty class, so we want to look at
the next initializable field (since empty class fields may not have an
initializer). But in this case there are no more, therefore accessing
DECL_CHAIN (field) crashes. Long story short, we need to avoid a crash
on a null field when we're initializing a class that only contains an
empty base class.
While poking into this I discovered c++/93898, but that's a different
problem.
2020-02-26 Marek Polacek <polacek@redhat.com>
PR c++/93803 - ICE with constexpr init and [[no_unique_address]].
* constexpr.c (reduced_constant_expression_p): Don't crash on a null
field.
* g++.dg/cpp2a/constexpr-init16.C: New test.
* g++.dg/cpp2a/constexpr-init17.C: New test.
>From gcc-bugs-return-671528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:06:44 2020
Return-Path: <gcc-bugs-return-671528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62902 invoked by alias); 26 Feb 2020 15:06: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 56477 invoked by uid 48); 26 Feb 2020 15:06:38 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93803] [10 Regression] ICE: segmentation fault with constant initialization of class having a [[no_unique_address]] field
Date: Wed, 26 Feb 2020 15: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, 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: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93803-4-xOpo2S9TFg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03110.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93803
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:07:26 2020
Return-Path: <gcc-bugs-return-671529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22785 invoked by alias); 26 Feb 2020 15: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 11919 invoked by uid 48); 26 Feb 2020 15:07:18 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93877] [9/10 Regression] [SH] webkit2gtk fails to build with "internal compiler error: in extract_constrain_insn, at recog.c:2211"
Date: Wed, 26 Feb 2020 15: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: 9.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: olegendo 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-93877-4-ZAQ8n3sjxF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03111.txt.bz2
Content-length: 3052
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93877
Oleg Endo <olegendo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vmakarov at gcc dot gnu.org
--- Comment #12 from Oleg Endo <olegendo at gcc dot gnu.org> ---
This looks to be an LRA related issue (checking with GCC 10). Without -mlra it
actually compiles fine. Adding -mlra causes some issues:
sh-elf-g++ -m4 -ml -matomic-model=soft-gusa -O2 -fno-strict-aliasing
-fno-exceptions -fno-rtti -fPIC -fstack-protector-strong -std=c++17 -mlra
../Source/ThirdParty/ANGLE/src/compiler/translator/IntermNode.cpp: In static
member function 'static sh::TConstantUnion*
sh::TIntermConstantUnion::FoldAggregateBuiltIn(sh::TIntermAggregate*,
sh::TDiagnostics*)':
../Source/ThirdParty/ANGLE/src/compiler/translator/IntermNode.cpp:3747:1:
error: insn does not satisfy its constraints:
(insn 9652 9651 3240 388 (parallel [
(set (reg:SF 66 fr2 [orig:662 _764 ] [662])
(reg:SF 0 r0 [3347]))
(use (reg:SI 154 fpscr0))
(clobber (scratch:SI))
])
"../Source/ThirdParty/ANGLE/src/compiler/translator/IntermNode.cpp":3568:60 214
{movsf_ie}
(expr_list:REG_DEAD (reg:SF 0 r0 [3347])
(nil)))
during RTL pass: cprop_hardreg
../Source/ThirdParty/ANGLE/src/compiler/translator/IntermNode.cpp:3747:1:
internal compiler error: in extract_constrain_insn, at recog.c:2195
0x5dee99 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
../../gcc/gcc/rtl-error.c:108
0x5deec2 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
../../gcc/gcc/rtl-error.c:118
0xe46907 extract_constrain_insn(rtx_insn*)
../../gcc/gcc/recog.c:2195
0xe4a204 copyprop_hardreg_forward_1
../../gcc/gcc/regcprop.c:802
0xe4b212 execute
../../gcc/gcc/regcprop.c:1367
sh-elf-g++ -m4 -ml -matomic-model=soft-gusa -O2 -std=c++17 -mlra
during RTL pass: reload
../Source/ThirdParty/ANGLE/src/compiler/translator/IntermNode.cpp: In member
function 'sh::TConstantUnion*
sh::TIntermConstantUnion::foldUnaryComponentWise(TOperator,
sh::TDiagnostics*)':
../Source/ThirdParty/ANGLE/src/compiler/translator/IntermNode.cpp:3047:1:
internal compiler error: in lra_set_insn_recog_data, at lra.c:1000
0xd1f5f1 lra_set_insn_recog_data(rtx_insn*)
../../gcc/gcc/lra.c:998
0xd2218f lra_get_insn_recog_data
../../gcc/gcc/lra-int.h:488
0xd2218f remove_scratches_1
../../gcc/gcc/lra.c:2058
0xd22247 lra_emit_move(rtx_def*, rtx_def*)
../../gcc/gcc/lra.c:503
0xd399bb curr_insn_transform
../../gcc/gcc/lra-constraints.c:4434
0xd3b20d lra_constraints(bool)
../../gcc/gcc/lra-constraints.c:5025
0xd227d4 lra(_IO_FILE*)
../../gcc/gcc/lra.c:2437
0xcd20c9 do_reload
../../gcc/gcc/ira.c:5523
0xcd20c9 execute
../../gcc/gcc/ira.c:5709
Vlad, maybe you have some hint where to look?
>From gcc-bugs-return-671530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:18:39 2020
Return-Path: <gcc-bugs-return-671530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60932 invoked by alias); 26 Feb 2020 15:18: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 60126 invoked by uid 48); 26 Feb 2020 15:18:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93812] [9/10 Regression] ICE in get_constant, at c-family/c-format.c:325
Date: Wed, 26 Feb 2020 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: 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: 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-93812-4-NA67upxnTP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03112.txt.bz2
Content-length: 1149
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93812
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The problem is that c-format.c assumes that when the "format" attribute is
present, handle_format_attribute has already verified it and it was ok.
Unfortunately, that is not the case, because if the attribute appears on a
!prototype_p function declaration, then fewer checks are performed on it
compared to when it appears on a prototype_p function, and if the !prototype_p
function decl is then merged with a prototype_p function decl, nothing performs
the checking.
So, one way out of this is drop the validated_p stuff and always validate,, it
will then behave similarly to how:
__attribute__((nonnull(2))) void foo (void);
warns and doesn't add the attribute, but
__attribute__((nonnull(2))) void bar ();
void bar (void);
adds it silently (but in this case I believe it doesn't ICE when actually using
the attribute).
Another possibility would be to repeat the checking of the attributes which
need positional_argument (nonnull, format*, alloc_size, alloc_align) when
merging a !prototype_p decl with prototype_p one.
>From gcc-bugs-return-671531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:20:02 2020
Return-Path: <gcc-bugs-return-671531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63199 invoked by alias); 26 Feb 2020 15:20: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 62673 invoked by uid 55); 26 Feb 2020 15:19:57 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93862] [10 Regression] ICE on static_cast of rvalue-reference-to-array of unknown bound [P0338] to its known static bound
Date: Wed, 26 Feb 2020 15: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: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93862-4-S8iFN3HaKG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03113.txt.bz2
Content-length: 1248
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93862
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:
https://gcc.gnu.org/g:4a305fa2fd4c9d553b26efa00f868aa1e4416a9f
commit r10-6867-g4a305fa2fd4c9d553b26efa00f868aa1e4416a9f
Author: Marek Polacek <polacek@redhat.com>
Date: Mon Feb 24 14:43:48 2020 -0500
c++: Fix ICE with static_cast when converting from int[] [PR93862]
This ICEs since my patch for P0388, which allowed conversions to arrays
of unknown bound, but not the reverse, so these two static_casts are
ill-formed.
[expr.static.cast]/3 says that "cv1 T1" and "cv2 T2" have to be
reference-compatible and the comment in build_static_cast_1 says it too
but then we actually use reference_related_p... Fixed thus.
2020-02-26 Marek Polacek <polacek@redhat.com>
PR c++/93862 - ICE with static_cast when converting from int[].
* call.c (reference_compatible_p): No longer static.
* cp-tree.h (reference_compatible_p): Declare.
* typeck.c (build_static_cast_1): Use reference_compatible_p instead
of reference_related_p.
* g++.dg/cpp0x/rv-cast7.C: New test.
>From gcc-bugs-return-671532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:22:52 2020
Return-Path: <gcc-bugs-return-671532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73484 invoked by alias); 26 Feb 2020 15:22: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 73425 invoked by uid 55); 26 Feb 2020 15:22:47 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93562] [8/9 Regression] unique_ptr::swap incorrectly uses generic std::swap
Date: Wed, 26 Feb 2020 15:22: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: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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:
Message-ID: <bug-93562-4-KyCKQLOsVe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93562-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93562-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03114.txt.bz2
Content-length: 1145
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93562
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:30cb4c78ea6563177c43f897e480d9993c38c0ed
commit r9-8285-g30cb4c78ea6563177c43f897e480d9993c38c0ed
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Feb 26 15:04:53 2020 +0000
libstdc++: Fix regressions in unique_ptr::swap (PR 93562)
The requirements for this function are only that the deleter is
swappable, but we incorrectly require that the element type is complete
and that the deleter can be swapped using std::swap (which requires it
to be move cosntructible and move assignable).
The fix is to add __uniq_ptr_impl::swap which swaps the pointer and
deleter individually, instead of using the generic std::swap on the
tuple containing them.
PR libstdc++/93562
* include/bits/unique_ptr.h (__uniq_ptr_impl::swap): Define.
(unique_ptr::swap, unique_ptr<T[], D>::swap): Call it.
* testsuite/20_util/unique_ptr/modifiers/93562.cc: New test.
>From gcc-bugs-return-671533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:24:03 2020
Return-Path: <gcc-bugs-return-671533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74668 invoked by alias); 26 Feb 2020 15:24: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 74587 invoked by uid 48); 26 Feb 2020 15:23:58 -0000
From: "tydeman at tybor dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93949] New: Register const local var will not compile
Date: Wed, 26 Feb 2020 15:24: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: tydeman at tybor 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-93949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03115.txt.bz2
Content-length: 530
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93949
Bug ID: 93949
Summary: Register const local var will not compile
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: tydeman at tybor dot com
Target Milestone: ---
This valid code will not compile.
int main(void){
register const double d[3] = { 0., 1., 2. };
return 0;
}
>From gcc-bugs-return-671534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:25:59 2020
Return-Path: <gcc-bugs-return-671534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77676 invoked by alias); 26 Feb 2020 15:25: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 77577 invoked by uid 55); 26 Feb 2020 15:25:48 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93936] [ranges] std::ranges::split_view<...>::_OuterIter<...>::__current() is private within this context
Date: Wed, 26 Feb 2020 15: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ppalka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93936-4-dvXsJZBBVG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93936-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03116.txt.bz2
Content-length: 976
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93936
--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:
https://gcc.gnu.org/g:8ce13842b50cbd2676f2e322995182af20df31fe
commit r10-6871-g8ce13842b50cbd2676f2e322995182af20df31fe
Author: Patrick Palka <ppalka@redhat.com>
Date: Wed Feb 26 08:38:06 2020 -0500
libstdc++: Fix use of inaccessible private member in split_view (PR93936)
We are calling _OuterIter::__current from _InnerIter::operator==, but the
former
is private within this non-member friend. Fix this by calling
_OuterIter::operator== instead, which does the right thing here.
libstdc++-v3/ChangeLog:
PR libstdc++/93936
* include/std/ranges (split_view::_InnerIter::operator==): Compare
the operands' _M_i rather than their _M_i.current().
* testsuite/std/ranges/adaptors/split.cc: Augment test.
>From gcc-bugs-return-671535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:26:22 2020
Return-Path: <gcc-bugs-return-671535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78495 invoked by alias); 26 Feb 2020 15:26: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 78466 invoked by uid 48); 26 Feb 2020 15:26:18 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93862] [10 Regression] ICE on static_cast of rvalue-reference-to-array of unknown bound [P0338] to its known static bound
Date: Wed, 26 Feb 2020 15: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: 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: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93862-4-bZMHYCtP08@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03117.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93862
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:34:03 2020
Return-Path: <gcc-bugs-return-671536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93286 invoked by alias); 26 Feb 2020 15:33: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 92460 invoked by uid 48); 26 Feb 2020 15:33:45 -0000
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93950] New: ICE: in make_region_for_unexpected_tree_code, at analyzer/region-model.cc:4786 with -fanalyzer
Date: Wed, 26 Feb 2020 15:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zsojka at seznam dot cz
X-Bugzilla-Status: UNCONFIRMED
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcchost attachments.created
Message-ID: <bug-93950-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03118.txt.bz2
Content-length: 4110
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93950
Bug ID: 93950
Summary: ICE: in make_region_for_unexpected_tree_code, at
analyzer/region-model.cc:4786 with -fanalyzer
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: zsojka at seznam dot cz
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Created attachment 47916
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47916&action=edit
reduced testcase (from OpenTTD sources)
Compiler output:
$ x86_64-pc-linux-gnu-g++ testcase.C -fanalyzer
during IPA pass: analyzer
testcase.C:10:11: internal compiler error: in
make_region_for_unexpected_tree_code, at analyzer/region-model.cc:4786
10 | void *j = nullptr;
| ^
0x8b188d
ana::region_model::make_region_for_unexpected_tree_code(ana::region_model_context*,
tree_node*, dump_location_t const&)
/repo/gcc-trunk/gcc/analyzer/region-model.cc:4786
0x8b188d
ana::region_model::make_region_for_unexpected_tree_code(ana::region_model_context*,
tree_node*, dump_location_t const&)
/repo/gcc-trunk/gcc/analyzer/region-model.cc:4782
0x169f0cd ana::region_model::get_lvalue_1(ana::path_var,
ana::region_model_context*)
/repo/gcc-trunk/gcc/analyzer/region-model.cc:4650
0x169f6c3 ana::region_model::get_lvalue(ana::path_var,
ana::region_model_context*)
/repo/gcc-trunk/gcc/analyzer/region-model.cc:4811
0x1e8852d ana::state_change_event::get_lvalue(tree_node*) const
/repo/gcc-trunk/gcc/analyzer/checker-path.h:206
0x1e8852d ana::diagnostic_manager::prune_for_sm_diagnostic(ana::checker_path*,
ana::state_machine const*, tree_node*, unsigned int) const
/repo/gcc-trunk/gcc/analyzer/diagnostic-manager.cc:1160
0x1e8876e ana::diagnostic_manager::prune_path(ana::checker_path*,
ana::state_machine const*, tree_node*, unsigned int) const
/repo/gcc-trunk/gcc/analyzer/diagnostic-manager.cc:1056
0x1e88a2f ana::diagnostic_manager::emit_saved_diagnostic(ana::exploded_graph
const&, ana::saved_diagnostic const&, ana::exploded_path const&, gimple const*,
int)
/repo/gcc-trunk/gcc/analyzer/diagnostic-manager.cc:520
0x1e894ce ana::dedupe_winners::emit_best(ana::diagnostic_manager*,
ana::exploded_graph const&)
/repo/gcc-trunk/gcc/analyzer/diagnostic-manager.cc:446
0x1e894ce ana::diagnostic_manager::emit_saved_diagnostics(ana::exploded_graph
const&)
/repo/gcc-trunk/gcc/analyzer/diagnostic-manager.cc:489
0x1681248 ana::impl_run_checkers(ana::logger*)
/repo/gcc-trunk/gcc/analyzer/engine.cc:3807
0x1681fcc ana::run_checkers()
/repo/gcc-trunk/gcc/analyzer/engine.cc:3850
0x16766e8 execute
/repo/gcc-trunk/gcc/analyzer/analyzer-pass.cc:84
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.
$ x86_64-pc-linux-gnu-g++ -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-g++
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-20200226101433-gb9934ad88d6-checking-yes-rtl-df-extra-nobootstrap-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/10.0.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--disable-bootstrap --with-cloog --with-ppl --with-isl
--build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
--target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-20200226101433-gb9934ad88d6-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.0.1 20200226 (experimental) (GCC)
>From gcc-bugs-return-671537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:35:20 2020
Return-Path: <gcc-bugs-return-671537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96093 invoked by alias); 26 Feb 2020 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 95992 invoked by uid 55); 26 Feb 2020 15:35:12 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93676] [8/9/10 Regression] crash in build_value_init
Date: Wed, 26 Feb 2020 15: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: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93676-4-SlGhmg3NQ8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93676-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93676-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03119.txt.bz2
Content-length: 1015
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93676
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:
https://gcc.gnu.org/g:38e1002657828150b2cda9f80c1f752184286e80
commit r10-6872-g38e1002657828150b2cda9f80c1f752184286e80
Author: Marek Polacek <polacek@redhat.com>
Date: Wed Feb 19 15:59:33 2020 -0500
c++: Fix value-init crash in template [PR93676]
Since <https://gcc.gnu.org/ml/gcc-patches/2015-02/msg00556.html> we
attempt to value-initialize in build_vec_init even when there's no
initializer but the type has a constexpr default constructor. But
build_value_init doesn't work in templates, and build_vec_init
creates a lot of garbage that would not be used anyway, so don't
call it in a template.
PR c++/93676 - value-init crash in template.
* init.c (build_new_1): Don't call build_vec_init in a template.
* g++.dg/cpp0x/nsdmi-template19.C: New test.
>From gcc-bugs-return-671538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:35:56 2020
Return-Path: <gcc-bugs-return-671538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96957 invoked by alias); 26 Feb 2020 15: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 96910 invoked by uid 48); 26 Feb 2020 15:35:47 -0000
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93936] [ranges] std::ranges::split_view<...>::_OuterIter<...>::__current() is private within this context
Date: Wed, 26 Feb 2020 15:35: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: ppalka at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ppalka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93936-4-c9p0oYobCB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93936-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03120.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93936
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Patrick Palka <ppalka at gcc dot gnu.org> ---
This should be fixed now.
>From gcc-bugs-return-671539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:38:45 2020
Return-Path: <gcc-bugs-return-671539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104092 invoked by alias); 26 Feb 2020 15:38: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 104012 invoked by uid 48); 26 Feb 2020 15:38:41 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93676] [8/9 Regression] crash in build_value_init
Date: Wed, 26 Feb 2020 15: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-valid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-93676-4-vPRgUEOwYj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93676-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93676-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03121.txt.bz2
Content-length: 473
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93676
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[8/9/10 Regression] crash |[8/9 Regression] crash in
|in build_value_init |build_value_init
--- Comment #8 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed on trunk so far.
>From gcc-bugs-return-671541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:39:36 2020
Return-Path: <gcc-bugs-return-671541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105771 invoked by alias); 26 Feb 2020 15:39: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 105688 invoked by uid 55); 26 Feb 2020 15:39:32 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93562] [8/9 Regression] unique_ptr::swap incorrectly uses generic std::swap
Date: Wed, 26 Feb 2020 15:39: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: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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: bug_status resolution
Message-ID: <bug-93562-4-YdDjpS28WO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93562-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93562-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03123.txt.bz2
Content-length: 1542
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93562
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for 8.4 and 9.3 as well.
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:e47c9cd77f5e60780f054aacb096315b1fcca8bb
commit r8-10088-ge47c9cd77f5e60780f054aacb096315b1fcca8bb
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Feb 26 15:04:53 2020 +0000
libstdc++: Fix regressions in unique_ptr::swap (PR 93562)
The requirements for this function are only that the deleter is
swappable, but we incorrectly require that the element type is complete
and that the deleter can be swapped using std::swap (which requires it
to be move cosntructible and move assignable).
The fix is to add __uniq_ptr_impl::swap which swaps the pointer and
deleter individually, instead of using the generic std::swap on the
tuple containing them.
PR libstdc++/93562
* include/bits/unique_ptr.h (__uniq_ptr_impl::swap): Define.
(unique_ptr::swap, unique_ptr<T[], D>::swap): Call it.
* testsuite/20_util/unique_ptr/modifiers/93562.cc: New test.
>From gcc-bugs-return-671540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:39:36 2020
Return-Path: <gcc-bugs-return-671540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105766 invoked by alias); 26 Feb 2020 15:39: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 105668 invoked by uid 48); 26 Feb 2020 15:39:31 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93562] [8/9 Regression] unique_ptr::swap incorrectly uses generic std::swap
Date: Wed, 26 Feb 2020 15:39: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: rejects-valid
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: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93562-4-aM1KRd6dIX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93562-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93562-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03122.txt.bz2
Content-length: 449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93562
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for 8.4 and 9.3 as well.
>From gcc-bugs-return-671543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:43:18 2020
Return-Path: <gcc-bugs-return-671543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111576 invoked by alias); 26 Feb 2020 15:43: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 111527 invoked by uid 55); 26 Feb 2020 15:43:10 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93325] libstdc++ wrongly uses direct clock_gettime syscall on non-glibc, breaks time64
Date: Wed, 26 Feb 2020 15:43: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: cvs-commit 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93325-4-fGxpk3dSaJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93325-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93325-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03125.txt.bz2
Content-length: 1217
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93325
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:655434f5ae93a4222a48c39c37a3a6fe0bdfc071
commit r8-10089-g655434f5ae93a4222a48c39c37a3a6fe0bdfc071
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Feb 26 15:32:34 2020 +0000
libstdc++: Replace glibc-specific check for clock_gettime (PR 93325)
It's wrong to assume that clock_gettime is unavailable on any *-*-linux*
target that doesn't have glibc 2.17 or later. Use a generic test instead
of using __GLIBC_PREREQ. Only do that test when is_hosted=yes so that we
don't get an error for cross targets without a working linker.
This ensures that C library's clock_gettime will be used on non-glibc
targets, instead of an incorrect syscall to SYS_clock_gettime.
Backport from mainline
2020-01-28 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/93325
* acinclude.m4 (GLIBCXX_ENABLE_LIBSTDCXX_TIME): Use AC_SEARCH_LIBS for
clock_gettime instead of explicit glibc version check.
* configure: Regenerate.
>From gcc-bugs-return-671542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:43:05 2020
Return-Path: <gcc-bugs-return-671542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110876 invoked by alias); 26 Feb 2020 15:43: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 110824 invoked by uid 55); 26 Feb 2020 15:43:00 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93325] libstdc++ wrongly uses direct clock_gettime syscall on non-glibc, breaks time64
Date: Wed, 26 Feb 2020 15:43: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: cvs-commit 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93325-4-V8V2gxoxeV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93325-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93325-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03124.txt.bz2
Content-length: 1216
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93325
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:08a70a65670ee801d4190ec122d42aa4a9a997a9
commit r9-8286-g08a70a65670ee801d4190ec122d42aa4a9a997a9
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Feb 26 15:32:34 2020 +0000
libstdc++: Replace glibc-specific check for clock_gettime (PR 93325)
It's wrong to assume that clock_gettime is unavailable on any *-*-linux*
target that doesn't have glibc 2.17 or later. Use a generic test instead
of using __GLIBC_PREREQ. Only do that test when is_hosted=yes so that we
don't get an error for cross targets without a working linker.
This ensures that C library's clock_gettime will be used on non-glibc
targets, instead of an incorrect syscall to SYS_clock_gettime.
Backport from mainline
2020-01-28 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/93325
* acinclude.m4 (GLIBCXX_ENABLE_LIBSTDCXX_TIME): Use AC_SEARCH_LIBS for
clock_gettime instead of explicit glibc version check.
* configure: Regenerate.
>From gcc-bugs-return-671544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:44:25 2020
Return-Path: <gcc-bugs-return-671544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112627 invoked by alias); 26 Feb 2020 15: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 112553 invoked by uid 48); 26 Feb 2020 15:44:14 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93325] libstdc++ wrongly uses direct clock_gettime syscall on non-glibc, breaks time64
Date: Wed, 26 Feb 2020 15:44: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: FIXED
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: bug_status resolution target_milestone
Message-ID: <bug-93325-4-i2JgssRW7O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93325-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93325-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03126.txt.bz2
Content-length: 521
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93325
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |8.4
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for 8.4 and 9.3 too. Thanks for the report.
>From gcc-bugs-return-671545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:56:47 2020
Return-Path: <gcc-bugs-return-671545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14538 invoked by alias); 26 Feb 2020 15:56: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 14413 invoked by uid 48); 26 Feb 2020 15:56:34 -0000
From: "guillaume at morinfr dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93951] New: ICE with '-flto -femit-struct-debug-baseonly'
Date: Wed, 26 Feb 2020 15:56: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: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: guillaume at morinfr 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-93951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03127.txt.bz2
Content-length: 2482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93951
Bug ID: 93951
Summary: ICE with '-flto -femit-struct-debug-baseonly'
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: guillaume at morinfr dot org
Target Milestone: ---
Created attachment 47917
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47917&action=edit
reproducer
This program ICEs with '-g -flto -femit-struct-debug-baseonly -std=gnu++2a'
with gcc 9.2 and 8.3 (seems to work on the trunk). Remove any of -g, -flto,
-femit-struct-debug-only and it builds fine.
#include <variant>
struct S1 {
bool fct() const;
};
struct S2 {
bool fct() const;
};
struct V {
bool visit() const {
auto visitor = [](auto&& s) -> bool { return s.fct(); };
return std::visit(visitor, v);
}
using Variant = std::variant<S1, S2>;
Variant v;
};
#0 htab_hash_string (p=0x0) at ../../src/libiberty/hashtab.c:838
#1 0x000000000085acad in external_ref_hasher::hash (r=<synthetic pointer>) at
../../src/gcc/dwarf2out.c:8917
#2 hash_table<external_ref_hasher, false, xcallocator>::find_slot
(insert=INSERT, value=<optimized out>, this=0x206fa40) at
../../src/gcc/hash-table.h:423
#3 lookup_external_ref (map=map@entry=0x206fa40, die=0x7ffff58f93c0) at
../../src/gcc/dwarf2out.c:8945
#4 0x000000000085ad6f in optimize_external_refs_1 (die=0x7ffff58f9370,
map=0x206fa40) at ../../src/gcc/dwarf2out.c:8983
#5 0x000000000085ad40 in optimize_external_refs_1 (die=0x7ffff58f9320,
map=0x206fa40) at ../../src/gcc/dwarf2out.c:8987
#6 0x000000000085ad40 in optimize_external_refs_1 (die=0x7ffff58f92d0,
map=0x206fa40) at ../../src/gcc/dwarf2out.c:8987
#7 0x000000000085ae59 in optimize_external_refs (die=die@entry=0x7ffff58f92d0)
at ../../src/gcc/dwarf2out.c:9036
#8 0x0000000000860ac8 in output_comp_unit (die=0x7ffff58f92d0,
output_if_empty=<optimized out>, dwo_id=0x0) at ../../src/gcc/dwarf2out.c:11055
#9 0x000000000088caa4 in dwarf2out_early_finish (filename=0x7fffffffd76d
"g++9_lto_crash.cc") at ../../src/gcc/dwarf2out.c:32264
#10 0x0000000000801025 in symbol_table::finalize_compilation_unit
(this=0x7ffff665f100) at ../../src/gcc/cgraphunit.c:2860
#11 0x0000000000b69cbd in compile_file () at ../../src/gcc/toplev.c:481
>From gcc-bugs-return-671546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:58:17 2020
Return-Path: <gcc-bugs-return-671546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19162 invoked by alias); 26 Feb 2020 15: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 17814 invoked by uid 48); 26 Feb 2020 15:58:10 -0000
From: "ch3root at openwall dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93848] missing -Warray-bounds warning for array subscript 1 is outside array bounds
Date: Wed, 26 Feb 2020 15: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: enhancement
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-93848-4-0bQaG5TTU8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03128.txt.bz2
Content-length: 2206
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93848
--- Comment #9 from Alexander Cherepanov <ch3root at openwall dot com> ---
(In reply to Martin Sebor from comment #8)
> In
>
> int i[4];
> int (*p)[4] = &i;
> bar_aux (p[1]);
>
> p[0] points to i and p[1] to (char*)&i + sizeof (i) (which is the same as
> &i[4]).
It seems we start to differ here. p[1] itself doesn't point anywhere. It's an
array, it has type int[4], its size is 4*sizeof(int). (That's easy to check.)
It's an lvalue that "potentially designates an object". Given that there is no
real object here, its evaluation is UB (C11, 6.3.2.1p1).
IOW there is no pointer here, UB happens before we get a pointer.
> The latter is a pointer just past the end of i. Evaluating
> past-the-end pointers is well-defined, as is all pointer arithmetic on them,
> just as long as the result is also a valid pointer to the same object (or
> just past its end). The only way past-the-end pointers differ from others
> is that the former cannot be dereferenced (by any means, either the *
> operator, or [] or ->).
Right, but this is applicable to p+1, not to p[1]. Indeed, p+1 is a
past-the-end pointer, it points past the end of the array consisting of one
element (i). In particular, you can add 0 and -1 to it to roam over the array.
And you are right that you cannot apply * to it. That is, there is *(p+0) (it's
i) but there is no *(p+1). And p[1] is *(p+1) by definition, so evaluating it
is UB.
> In
> int a[1][4];
> printf("%p\n", (void *)&a[1][1]);
>
> on the other hand, the reference to a[1][1] is undefined because a[1] is not
> a reference to an element in a but rather just past the end of a, and so it
> can be neither dereferenced nor used to obtain pointers other than to a or
> just past it.
Sorry I don't quite understand. Are you saying that a[1]-1 is valid? And the
result is a?
> &a[1] alone is valid (it's equivalent to (char*)&a + sizeof
> a) and points just past the end of a, but &a[1][1] is equivalent to
> (char*)&a + sizeof a + 1 which is not valid.
So we at least agree that &a[1][1] is UB and should give a warning and that
-Warray-bounds doesn't work as intended here?
>From gcc-bugs-return-671547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:59:30 2020
Return-Path: <gcc-bugs-return-671547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97473 invoked by alias); 26 Feb 2020 15:59: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 95906 invoked by uid 48); 26 Feb 2020 15:59:15 -0000
From: "przemyslaw.wirkus at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93320] internal compiler error: in is_base_type, at dwarf2out.c:12987
Date: Wed, 26 Feb 2020 15: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: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: przemyslaw.wirkus 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93320-4-9uSK2N1r2l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93320-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93320-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03129.txt.bz2
Content-length: 536
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93320
Przemyslaw Wirkus <przemyslaw.wirkus at arm dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |przemyslaw.wirkus at arm dot com
--- Comment #6 from Przemyslaw Wirkus <przemyslaw.wirkus at arm dot com> ---
Hi,
I was able to reduce your testcase to this code:
template <typename> class a;
class {
void b(a... c);
}
/Przemyslaw
>From gcc-bugs-return-671548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 15:59:51 2020
Return-Path: <gcc-bugs-return-671548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98322 invoked by alias); 26 Feb 2020 15:59: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 98270 invoked by uid 48); 26 Feb 2020 15:59:42 -0000
From: "frederic.recoules@univ-grenoble-alpes.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93952] New: Giving an array in an operand
Date: Wed, 26 Feb 2020 15:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ABI, accepts-invalid, documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frederic.recoules@univ-grenoble-alpes.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 keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93952-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03130.txt.bz2
Content-length: 1736
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93952
Bug ID: 93952
Summary: Giving an array in an operand
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: ABI, accepts-invalid, documentation
Severity: normal
Priority: P3
Component: inline-asm
Assignee: unassigned at gcc dot gnu.org
Reporter: frederic.recoules@univ-grenoble-alpes.fr
Target Milestone: ---
I am trying to understand the meaning of giving an array in an operand of an
inline assembly statement.
Please consider the following small snippet of code:
int main (int argc, char * argv[])
{
char t[] = "abc";
int x;
__asm__ ("movl %1, %0"
: "=r" (x)
: "r" (t));
return x;
}
Here are my observation and my understanding:
The object t that has type "array of char" is converted to an expression with
type "pointer to char" that points to the initial element of t.
It is equivalent to: x = (int) &t[0];
If we change the constraint "r" to "m", the result is different.
Here is the limit of my understanding and it is only speculation:
The constraint "m" take the address of t, but as it is an array, it actually
returns it unchanged and then it access to the value pointed by.
It is like: x = (int) *(/*&*/(&t[0]));
Now I wonder if the code where we replace the constraint by "rm" is valid
because the returned value depends of the constraint the compiler have chosen.
In my mind, I would have expected that "m" constraint pass the same value but
in a way it is accessible through memory, that is: char *p = t; x = (int)
*(&p);
Could someone point me out where I am going wrong here?
>From gcc-bugs-return-671549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:02:36 2020
Return-Path: <gcc-bugs-return-671549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103343 invoked by alias); 26 Feb 2020 16:02: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 103236 invoked by uid 55); 26 Feb 2020 16:02:24 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Wed, 26 Feb 2020 16:02: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93871-4-ZusHsIdO8Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03131.txt.bz2
Content-length: 2091
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #27 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Wed, Feb 26, 2020 at 12:58:21PM +0000, thenlich at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
>
> --- Comment #26 from Thomas Henlich <thenlich at gcc dot gnu.org> ---
> Created attachment 47914
> --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47914&action=edit
> Demonstration of range reduction
>
> There is a danger of some inaccuracy in the degree trigonometric functions
> (sind, cosd, tand, cotand) because a full period of 360 degrees can not be
> expressed accurately in radians.
>
> This can be circumvented by using some trigonometric identities to reduce the
> range and also place the inaccurate x range to where |dy/dx|→min, and away from
> y values near zero toward high y values so that the error is mostly cancelled.
I implemented FreeBSD's cosl, sinl, and tanl, did the legwork to produce
all of the sincos family of functions, and have implemented sinpi and
friends for FreeBSD . I'm well aware of argument reduction and ULPs. If
you're going to go this route, then you'll need to write functions that
can be called from libgfortran.
My patch rewrites the special handling of degree trig functions to bring
these functions into the general framework that gfortran uses for all other
intrinsic routines (except a few in IEEE_ARITHEMETIC).
> This is a best effort to still be able to use the standard library functions
> but also get an increased accuracy expected from the degree functions.
>
> Thus:
> 1. Calculate cosd(x) = sind(90 - x)
> 2. Calculate cotand(x) = tand(90 - x)
> 3. Reduce range of sind() argument from (0...360) further to x-360 if it is
> above 270, and to 180-x if it is above 90
>
(snip)
> $ gf10 -fdec-math -fdefault-real-8 periods.f90 && ./a.exe
Any result that uses -fdefault-real-8 will be ingored by me.
That option should have been removed years ago. I even posted
a patch that removed it. It was not well-received.
>From gcc-bugs-return-671551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:03:45 2020
Return-Path: <gcc-bugs-return-671551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15063 invoked by alias); 26 Feb 2020 16: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 3068 invoked by uid 48); 26 Feb 2020 16:03:41 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93012] PPC: inefficient 64-bit constant generation (upper = lower)
Date: Wed, 26 Feb 2020 16:03: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: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93012-4-qDHLa4BZjh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93012-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93012-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03133.txt.bz2
Content-length: 466
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93012
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Fixed on trunk. No backport planned.
>From gcc-bugs-return-671550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:03:31 2020
Return-Path: <gcc-bugs-return-671550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110907 invoked by alias); 26 Feb 2020 16: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 104385 invoked by uid 48); 26 Feb 2020 16:03:22 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93877] [9/10 Regression] [SH] webkit2gtk fails to build with "internal compiler error: in extract_constrain_insn, at recog.c:2211"
Date: Wed, 26 Feb 2020 16:03: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
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.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: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93877-4-aribLIwAsP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03132.txt.bz2
Content-length: 1974
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93877
--- Comment #13 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
Indeed, this seems to be related to LRA.
I just tried to build gcc-9 with LRA enabled by default and the build fails
when trying to build gnat with:
checking for shl_load in -ldld... s-gearop.adb: In function
'Ada.Numerics.Complex_Arrays.Back_Substitute.Sub_Row':
s-gearop.adb:124:11: error: insn does not satisfy its constraints:
(insn 463 462 465 5 (parallel [
(set (reg:SF 65 fr1 [343])
(reg:SF 0 r0 [344]))
(use (reg:SI 154 fpscr0))
(clobber (scratch:SI))
]) "a-ngcoty.adb":68:10 214 {movsf_ie}
(expr_list:REG_DEAD (reg:SF 0 r0 [344])
(nil)))
+===========================GNAT BUG DETECTED==============================+
| 9.2.1 20191130 (sh4-linux-gnu) in extract_constrain_insn, at recog.c:2211|
| Error detected around s-gearop.adb:124:11 |
| Please submit a bug report; see https://gcc.gnu.org/bugs/ . |
| Use a subject line meaningful to you and us to track the bug. |
| Include the entire contents of this bug box in the report. |
| Include the exact command that you entered. |
| Also include sources listed below. |
+==========================================================================+
Please include these source files with error report
Note that list may not be accurate in some cases,
so please double check that the problem can still
be reproduced with the set of files listed.
Consider also -gnatd.n switch (see debug.adb).
>From gcc-bugs-return-671552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:08:16 2020
Return-Path: <gcc-bugs-return-671552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127605 invoked by alias); 26 Feb 2020 16:08: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 126721 invoked by uid 48); 26 Feb 2020 16:08:02 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93950] ICE: in make_region_for_unexpected_tree_code, at analyzer/region-model.cc:4786 with -fanalyzer
Date: Wed, 26 Feb 2020 16:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-93950-4-3NTEJmD2YK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93950-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03134.txt.bz2
Content-length: 513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93950
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-02-26
Ever confirmed|0 |1
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Confirmed; thanks for filing this.
>From gcc-bugs-return-671554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:32:24 2020
Return-Path: <gcc-bugs-return-671554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113516 invoked by alias); 26 Feb 2020 16:32: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 112763 invoked by uid 55); 26 Feb 2020 16:32:19 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93205] std::discrete_distribution's operator>> causes OOM
Date: Wed, 26 Feb 2020 16: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: 7.5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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:
Message-ID: <bug-93205-4-6GxbqAkdcP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93205-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93205-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03136.txt.bz2
Content-length: 1526
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93205
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:a29236a23c03fe08998b81a0ef1f67e7ea185ba3
commit r9-8289-ga29236a23c03fe08998b81a0ef1f67e7ea185ba3
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Feb 26 16:31:19 2020 +0000
libstdc++: Fix undefined behaviour in random dist serialization (PR93205)
The deserialization functions for random number distributions fail to
check the stream state before using the extracted values. In some cases
this leads to using indeterminate values to resize a vector, and then
filling that vector with indeterminate values.
No values that affect control flow should be used without checking that a
good value was read from the stream.
Additionally, where reasonable to do so, defer modifying any state in
the distribution until all values have been successfully read, to avoid
modifying some of the distribution's parameters and leaving others
unchanged.
Backport from mainline
2020-01-09 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/93205
* include/bits/random.h (operator>>): Check stream operation succeeds.
* include/bits/random.tcc: (operator>>): Likewise.
(__extract_params): New function to fill a vector from a stream.
* testsuite/26_numerics/random/pr60037-neg.cc: Adjust dg-error line.
>From gcc-bugs-return-671553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:32:19 2020
Return-Path: <gcc-bugs-return-671553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112800 invoked by alias); 26 Feb 2020 16:32: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 112708 invoked by uid 55); 26 Feb 2020 16:32:14 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92886] Inappropriate comment for std::ios_base::trunc
Date: Wed, 26 Feb 2020 16: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: cvs-commit 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:
Message-ID: <bug-92886-4-EFT6c15hjK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92886-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92886-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03135.txt.bz2
Content-length: 653
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92886
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:7a7ef79651abd20b95d1f76479887d1ea008a62f
commit r9-8288-g7a7ef79651abd20b95d1f76479887d1ea008a62f
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Feb 26 16:31:19 2020 +0000
libstdc++: Fix description of std::ios::trunc (PR 92886)
Backport from mainline
2019-12-10 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/92886
* include/bits/ios_base.h (std::ios_base::trunc): Fix comment.
>From gcc-bugs-return-671556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:33:52 2020
Return-Path: <gcc-bugs-return-671556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16637 invoked by alias); 26 Feb 2020 16:33: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 16569 invoked by uid 48); 26 Feb 2020 16:33:47 -0000
From: "joel.hutton at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92922] [10 regression] [ilp32] FAIL: gcc.target/aarch64/sve/acle/asm/ldnt1_u32.c -stdÉ0 -O1 -g -DTEST_FULL (internal compiler error)
Date: Wed, 26 Feb 2020 16:33: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: joel.hutton at arm 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92922-4-M2JCGhIASg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92922-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92922-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03138.txt.bz2
Content-length: 364
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92922
--- Comment #2 from Joel Hutton <joel.hutton at arm dot com> ---
This was fixed by Richard Sandiford's patch.
commit fb15e2bab5267213b8706fa6a29eeef94f62a524
Author: Richard Sandiford <richard.sandiford@arm.com>
Date: Mon Jan 20 19:29:25 2020 +0000
aarch64: Fix SVE ACLE handling of SImode pointers
>From gcc-bugs-return-671555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:33:32 2020
Return-Path: <gcc-bugs-return-671555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15786 invoked by alias); 26 Feb 2020 16:33: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 15733 invoked by uid 48); 26 Feb 2020 16:33:22 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92886] Inappropriate comment for std::ios_base::trunc
Date: Wed, 26 Feb 2020 16:33: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: RESOLVED
X-Bugzilla-Resolution: FIXED
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-92886-4-U1124pnL6t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92886-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92886-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03137.txt.bz2
Content-length: 291
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92886
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|10.0 |8.4
>From gcc-bugs-return-671558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:42:27 2020
Return-Path: <gcc-bugs-return-671558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28790 invoked by alias); 26 Feb 2020 16:42: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 28745 invoked by uid 48); 26 Feb 2020 16:42:22 -0000
From: "sudi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92922] [10 regression] [ilp32] FAIL: gcc.target/aarch64/sve/acle/asm/ldnt1_u32.c -stdÉ0 -O1 -g -DTEST_FULL (internal compiler error)
Date: Wed, 26 Feb 2020 16: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sudi 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 cc resolution
Message-ID: <bug-92922-4-56b6YAPR0X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92922-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92922-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03140.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92922
sudi at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |sudi at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #3 from sudi at gcc dot gnu.org ---
Fixed as commented
>From gcc-bugs-return-671557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:42:16 2020
Return-Path: <gcc-bugs-return-671557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28086 invoked by alias); 26 Feb 2020 16:42: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 27985 invoked by uid 48); 26 Feb 2020 16:42:08 -0000
From: "wjwray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93862] [10 Regression] ICE on static_cast of rvalue-reference-to-array of unknown bound [P0338] to its known static bound
Date: Wed, 26 Feb 2020 16: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wjwray at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93862-4-z2GS5hJABR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03139.txt.bz2
Content-length: 1096
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93862
--- Comment #6 from Will Wray <wjwray at gmail dot com> ---
Thanks for the quick work.
However, I'm not sure that (2) and (3) _are_ invalid.
(Sorry, I didn't have time to follow the email thread).
I should have provided this link to an exchange with Richard Smith.
I'd waited for his response before filing the bug. He says:
"In both cases, it's valid to use static_cast to recover the original type."
https://cpplang.slack.com/archives/C2PQKRWJU/p1579186047347300
zygoloid Feb 20
Lifetime extension applies; the lifetime extension rules don't care about
qualification conversions. Another example: const int *const &r =
static_cast<int*&&>(nullptr); performs lifetime extension even though the type
of the temporary object (int*) has been lost (mutability-erased) in the
reference binding.
zygoloid Feb 20
In both cases, it's valid to use static_cast to recover the original type.
willw Feb 20
Thanks for the confirmation. That makes sense.
willw Feb 21
I filed the gcc bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93862
>From gcc-bugs-return-671559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:44:31 2020
Return-Path: <gcc-bugs-return-671559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31359 invoked by alias); 26 Feb 2020 16:44: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 31244 invoked by uid 48); 26 Feb 2020 16:44:26 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93205] std::discrete_distribution's operator>> causes OOM
Date: Wed, 26 Feb 2020 16:44: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: 7.5.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: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93205-4-RTpUlDf58Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93205-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93205-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03141.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93205
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for 8.4 and 9.3
>From gcc-bugs-return-671561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:44:52 2020
Return-Path: <gcc-bugs-return-671561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32809 invoked by alias); 26 Feb 2020 16:44: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 32712 invoked by uid 55); 26 Feb 2020 16:44:42 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93205] std::discrete_distribution's operator>> causes OOM
Date: Wed, 26 Feb 2020 16:44: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: 7.5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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:
Message-ID: <bug-93205-4-fDC3vxauSa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93205-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93205-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03143.txt.bz2
Content-length: 1527
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93205
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:f80c40f93f9e8781b14f1a8301467f117fd24051
commit r8-10091-gf80c40f93f9e8781b14f1a8301467f117fd24051
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Feb 26 16:09:52 2020 +0000
libstdc++: Fix undefined behaviour in random dist serialization (PR93205)
The deserialization functions for random number distributions fail to
check the stream state before using the extracted values. In some cases
this leads to using indeterminate values to resize a vector, and then
filling that vector with indeterminate values.
No values that affect control flow should be used without checking that a
good value was read from the stream.
Additionally, where reasonable to do so, defer modifying any state in
the distribution until all values have been successfully read, to avoid
modifying some of the distribution's parameters and leaving others
unchanged.
Backport from mainline
2020-01-09 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/93205
* include/bits/random.h (operator>>): Check stream operation succeeds.
* include/bits/random.tcc: (operator>>): Likewise.
(__extract_params): New function to fill a vector from a stream.
* testsuite/26_numerics/random/pr60037-neg.cc: Adjust dg-error line.
>From gcc-bugs-return-671560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:44:36 2020
Return-Path: <gcc-bugs-return-671560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31915 invoked by alias); 26 Feb 2020 16:44: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 31361 invoked by uid 55); 26 Feb 2020 16:44:31 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92886] Inappropriate comment for std::ios_base::trunc
Date: Wed, 26 Feb 2020 16:44: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: cvs-commit 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92886-4-pZHTOPM7OU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92886-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92886-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03142.txt.bz2
Content-length: 654
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92886
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:a13dd21c3f4fe405980b469c544a00c4356d7006
commit r8-10090-ga13dd21c3f4fe405980b469c544a00c4356d7006
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Feb 26 15:46:27 2020 +0000
libstdc++: Fix description of std::ios::trunc (PR 92886)
Backport from mainline
2019-12-10 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/92886
* include/bits/ios_base.h (std::ios_base::trunc): Fix comment.
>From gcc-bugs-return-671562-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 16:48:48 2020
Return-Path: <gcc-bugs-return-671562-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35772 invoked by alias); 26 Feb 2020 16:48: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 35672 invoked by uid 48); 26 Feb 2020 16:48:38 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93862] [10 Regression] ICE on static_cast of rvalue-reference-to-array of unknown bound [P0338] to its known static bound
Date: Wed, 26 Feb 2020 16: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93862-4-0Ob5IGKCqW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03144.txt.bz2
Content-length: 180
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93862
--- Comment #7 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Oof, curious. Could you please create a new PR for that?
>From gcc-bugs-return-671563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 17:12:26 2020
Return-Path: <gcc-bugs-return-671563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94120 invoked by alias); 26 Feb 2020 17:12: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 94067 invoked by uid 48); 26 Feb 2020 17:12:21 -0000
From: "wjwray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93862] [10 Regression] ICE on static_cast of rvalue-reference-to-array of unknown bound [P0338] to its known static bound
Date: Wed, 26 Feb 2020 17: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wjwray at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93862-4-jeaOdKcTla@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03145.txt.bz2
Content-length: 248
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93862
--- Comment #8 from Will Wray <wjwray at gmail dot com> ---
OK. I'll try to get full confirmation and clarification on legality,
with links to wording if possible, then open a new bug if valid.
>From gcc-bugs-return-671564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 17:21:19 2020
Return-Path: <gcc-bugs-return-671564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106258 invoked by alias); 26 Feb 2020 17:21: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 106225 invoked by uid 48); 26 Feb 2020 17:21:11 -0000
From: "frederic.recoules@univ-grenoble-alpes.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93952] Giving an array in an operand
Date: Wed, 26 Feb 2020 17:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ABI, accepts-invalid, documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frederic.recoules@univ-grenoble-alpes.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:
Message-ID: <bug-93952-4-FOtbcK4isb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93952-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93952-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03146.txt.bz2
Content-length: 587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93952
--- Comment #1 from Frédéric Recoules <frederic.recoules@univ-grenoble-alpes.fr> ---
(In reply to Frédéric Recoules from comment #0)
> Now I wonder if the code where we replace the constraint by "rm" is valid
> because the returned value depends of the constraint the compiler have
> chosen.
Ok, it seems that if the compiler have the choice between "r" and "m", it
returns the same result whatever it chooses.
I do shake my head a bit because I don't understand why solo "m" is treated in
a different way.
>From gcc-bugs-return-671565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 17:54:36 2020
Return-Path: <gcc-bugs-return-671565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29018 invoked by alias); 26 Feb 2020 17:54: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 28937 invoked by uid 48); 26 Feb 2020 17:54:29 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87685] [8 Regression] Calling a static method from inside a generic lambda requires to capture 'this'
Date: Wed, 26 Feb 2020 17: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: 8.1.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87685-4-jNlMO41SsN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87685-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87685-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03147.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87685
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 17:55:41 2020
Return-Path: <gcc-bugs-return-671566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35816 invoked by alias); 26 Feb 2020 17:55: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 31107 invoked by uid 48); 26 Feb 2020 17:55:37 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87554] [8 Regression] internal compiler error: in record_reference, at cgraphbuild.c:64
Date: Wed, 26 Feb 2020 17: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: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87554-4-PWa4jBbaZ4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87554-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87554-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03148.txt.bz2
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87554
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #13 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 17:56:47 2020
Return-Path: <gcc-bugs-return-671568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44662 invoked by alias); 26 Feb 2020 17:56: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 44556 invoked by uid 48); 26 Feb 2020 17:56:37 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86429] [8 Regression] lambda capture breaks constexpr-ness
Date: Wed, 26 Feb 2020 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.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86429-4-9IH3PxrwuC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86429-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86429-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03150.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86429
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 17:56:31 2020
Return-Path: <gcc-bugs-return-671567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43915 invoked by alias); 26 Feb 2020 17:56: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 43863 invoked by uid 48); 26 Feb 2020 17:56:27 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87327] [8 Regression] Calling member functions on captured constexpr variables "is not a constant expression"
Date: Wed, 26 Feb 2020 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: 8.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87327-4-2M5Z0WL6B7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87327-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87327-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03149.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87327
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 17:56:47 2020
Return-Path: <gcc-bugs-return-671569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44696 invoked by alias); 26 Feb 2020 17: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 44579 invoked by uid 48); 26 Feb 2020 17:56:37 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54367] [meta-bug] lambda expressions
Date: Wed, 26 Feb 2020 17:56: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: jason 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-54367-4-5TfWVvKXqA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-54367-4@http.gcc.gnu.org/bugzilla/>
References: <bug-54367-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03151.txt.bz2
Content-length: 477
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54367
Bug 54367 depends on bug 86429, which changed state.
Bug 86429 Summary: [8 Regression] lambda capture breaks constexpr-ness
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86429
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-671570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 17:57:48 2020
Return-Path: <gcc-bugs-return-671570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46678 invoked by alias); 26 Feb 2020 17: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 46618 invoked by uid 48); 26 Feb 2020 17:57:44 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87480] [8 Regression] SFINAE constructor not matched, only in templated function
Date: Wed, 26 Feb 2020 17: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87480-4-tLvKkTIYUe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87480-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87480-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03152.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87480
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 17:58:20 2020
Return-Path: <gcc-bugs-return-671571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47539 invoked by alias); 26 Feb 2020 17:58: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 47499 invoked by uid 48); 26 Feb 2020 17:58:16 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87748] [8 Regression] G++-8 treats SFINAE as error
Date: Wed, 26 Feb 2020 17: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.1.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87748-4-FdnrIwUgfI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87748-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87748-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03153.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87748
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 17:59:21 2020
Return-Path: <gcc-bugs-return-671572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48440 invoked by alias); 26 Feb 2020 17:59: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 48403 invoked by uid 48); 26 Feb 2020 17:59:16 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88394] [8 Regression] g++ ICE (Segmentation fault) in insert_capture_proxy
Date: Wed, 26 Feb 2020 17: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: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88394-4-XXVGNpketj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88394-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88394-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03154.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88394
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 18:02:28 2020
Return-Path: <gcc-bugs-return-671573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71285 invoked by alias); 26 Feb 2020 18:02: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 71229 invoked by uid 55); 26 Feb 2020 18:02:23 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93913] [10 regression] r10-6762 breaks gcc.target/powerpc/fold-vec-st-*.c test cases
Date: Wed, 26 Feb 2020 18:02: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: cvs-commit 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-93913-4-6tdXCQ8gEI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93913-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93913-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03155.txt.bz2
Content-length: 825
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93913
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Peter Bergner <bergner@gcc.gnu.org>:
https://gcc.gnu.org/g:051b9873e78fe1acb1a3fecd0c6e5685b6c12fb3
commit r10-6874-g051b9873e78fe1acb1a3fecd0c6e5685b6c12fb3
Author: Peter Bergner <bergner@linux.ibm.com>
Date: Wed Feb 26 11:58:08 2020 -0600
rs6000: Fix more testsuite fallout from rs6000_legitimate_address_p() fix.
[PR93913]
PR target/93913
* gcc.target/powerpc/fold-vec-st-char.c (scan-assembler-times): Allow
stxv and stxvx instructions as well.
* gcc.target/powerpc/fold-vec-st-float.c: Likewise.
* gcc.target/powerpc/fold-vec-st-int.c: Likewise.
* gcc.target/powerpc/fold-vec-st-short.c: Likewise.
>From gcc-bugs-return-671576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 18:22:41 2020
Return-Path: <gcc-bugs-return-671576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16667 invoked by alias); 26 Feb 2020 18:22: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 16457 invoked by uid 48); 26 Feb 2020 18:22:31 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86747] [8 Regression] rejects-valid with redundant friend declaration
Date: Wed, 26 Feb 2020 18: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: 8.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: aoliva at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-86747-4-QVx52Vn6uj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03158.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86747
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
CC| |jason at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 18:22:41 2020
Return-Path: <gcc-bugs-return-671574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16605 invoked by alias); 26 Feb 2020 18:22: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 16535 invoked by uid 48); 26 Feb 2020 18:22:32 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87652] [8 Regression] inner class template of outer class template can't access friend's protected data member
Date: Wed, 26 Feb 2020 18:22: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: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason 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: bug_status resolution
Message-ID: <bug-87652-4-IHKT8dfBd1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87652-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87652-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03156.txt.bz2
Content-length: 490
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87652
Bug 87652 depends on bug 86747, which changed state.
Bug 86747 Summary: [8 Regression] rejects-valid with redundant friend declaration
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86747
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-671575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 18:22:41 2020
Return-Path: <gcc-bugs-return-671575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16646 invoked by alias); 26 Feb 2020 18:22: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 16502 invoked by uid 48); 26 Feb 2020 18:22:32 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87651] [8 Regression] inner class with template template friend declaration of same name fails to compile
Date: Wed, 26 Feb 2020 18:22: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: 8.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason 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: bug_status resolution
Message-ID: <bug-87651-4-bThWp0fggt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03157.txt.bz2
Content-length: 490
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87651
Bug 87651 depends on bug 86747, which changed state.
Bug 86747 Summary: [8 Regression] rejects-valid with redundant friend declaration
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86747
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-671577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 18:23:31 2020
Return-Path: <gcc-bugs-return-671577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18829 invoked by alias); 26 Feb 2020 18:23: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 18765 invoked by uid 48); 26 Feb 2020 18:23:27 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87651] [8 Regression] inner class with template template friend declaration of same name fails to compile
Date: Wed, 26 Feb 2020 18:23: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.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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: bug_status resolution
Message-ID: <bug-87651-4-SQw8xPTLOh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03159.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87651
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 18:24:49 2020
Return-Path: <gcc-bugs-return-671578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19932 invoked by alias); 26 Feb 2020 18:24: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 19750 invoked by uid 48); 26 Feb 2020 18:24:18 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87652] [8 Regression] inner class template of outer class template can't access friend's protected data member
Date: Wed, 26 Feb 2020 18: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.2.0
X-Bugzilla-Keywords: ice-on-valid-code, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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: bug_status cc resolution
Message-ID: <bug-87652-4-6BsErllLji@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87652-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87652-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03160.txt.bz2
Content-length: 505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87652
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |jason at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #8 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4.
>From gcc-bugs-return-671579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 18:37:37 2020
Return-Path: <gcc-bugs-return-671579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92838 invoked by alias); 26 Feb 2020 18:37: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 92753 invoked by uid 48); 26 Feb 2020 18:37:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93949] [8/9/10 Regression] Register const local var will not compile since r0-58166
Date: Wed, 26 Feb 2020 18: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:
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 target_milestone short_desc everconfirmed
Message-ID: <bug-93949-4-dhHDKtrBiY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03161.txt.bz2
Content-length: 1362
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93949
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-26
CC| |jakub at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Target Milestone|--- |8.4
Summary|Register const local var |[8/9/10 Regression]
|will not compile |Register const local var
| |will not compile since
| |r0-58166
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r0-58166-g6de9cd9a886ea695aa892c3c7c07818a7b7e9e6f.
The problem is in the
/* If a const aggregate variable is being initialized, then it
should never be a lose to promote the variable to be static. */
optimization. Either we shouldn't do that optimization if DECL_REGISTER is
set, or we should clear DECL_REGISTER. If the latter, we should still punt on
DECL_HARD_REGISTER.
>From gcc-bugs-return-671580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 19:00:47 2020
Return-Path: <gcc-bugs-return-671580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125591 invoked by alias); 26 Feb 2020 19: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 125516 invoked by uid 48); 26 Feb 2020 19:00:42 -0000
From: "stilor at att dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93751] -g1 does not behave per manual
Date: Wed, 26 Feb 2020 19:00: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: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: stilor at att 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:
Message-ID: <bug-93751-4-qnfvHOMBy0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03162.txt.bz2
Content-length: 129
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93751
--- Comment #12 from Alexey Neyman <stilor at att dot net> ---
Patch ping.
>From gcc-bugs-return-671581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 19:16:00 2020
Return-Path: <gcc-bugs-return-671581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112044 invoked by alias); 26 Feb 2020 19:15: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 111786 invoked by uid 48); 26 Feb 2020 19:15:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93901] [10 Regression] noexcept specifier on ctor does not work with constexpr variable or expression since r10-4394
Date: Wed, 26 Feb 2020 19: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:
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-93901-4-R9HUp3L9ce@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93901-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93901-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03163.txt.bz2
Content-length: 278
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93901
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
It is the
* pt.c (maybe_instantiate_noexcept): Only update clones if we
instantiated.
part of that commit that breaks this, but I'm afraid I have no idea why.
>From gcc-bugs-return-671582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 19:25:52 2020
Return-Path: <gcc-bugs-return-671582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3636 invoked by alias); 26 Feb 2020 19: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 3547 invoked by uid 55); 26 Feb 2020 19:25:47 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92852] [8/9/10 Regression] location references block not in block tree
Date: Wed, 26 Feb 2020 19: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: 9.2.0
X-Bugzilla-Keywords: ice-checking
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92852-4-XI15c7kEev@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92852-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92852-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03164.txt.bz2
Content-length: 807
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92852
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:b6678d67c4b7471c25130b6c60a9087e02f31179
commit r9-8290-gb6678d67c4b7471c25130b6c60a9087e02f31179
Author: Jason Merrill <jason@redhat.com>
Date: Wed Feb 26 13:03:23 2020 -0500
c++: Preserve location in maybe_constant_value.
If cxx_eval_outermost_constant_expr doesn't change the argument, we really
shouldn't unshare it when we try to fold it again.
gcc/cp/ChangeLog
2020-02-26 Jason Merrill <jason@redhat.com>
PR c++/92852
* constexpr.c (maybe_constant_value): Don't unshare if the cached
value is the same as the argument.
>From gcc-bugs-return-671583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 19:25:59 2020
Return-Path: <gcc-bugs-return-671583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4279 invoked by alias); 26 Feb 2020 19:25: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 3693 invoked by uid 55); 26 Feb 2020 19:25:52 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93140] [8/9 Regression] Segfault in cc1plus on incorrect decltype among function args
Date: Wed, 26 Feb 2020 19: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: 9.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93140-4-2Mmpb2Sw0l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03165.txt.bz2
Content-length: 844
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93140
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:1a8996b0a7b238180f4a10b19b1e90b33e5b2df0
commit r9-8291-g1a8996b0a7b238180f4a10b19b1e90b33e5b2df0
Author: Jason Merrill <jason@redhat.com>
Date: Wed Feb 26 13:03:23 2020 -0500
c++: Fix decltype of empty pack expansion of parm.
In unevaluated context, we only substitute a single PARM_DECL, not the
entire chain, but the handling of an empty pack expansion was missing that
check.
gcc/cp/ChangeLog
2020-02-26 Jason Merrill <jason@redhat.com>
PR c++/93140
* pt.c (tsubst_decl) [PARM_DECL]: Check cp_unevaluated_operand in
handling of TREE_CHAIN for empty pack.
>From gcc-bugs-return-671584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 19:26:12 2020
Return-Path: <gcc-bugs-return-671584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5208 invoked by alias); 26 Feb 2020 19:26: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 4419 invoked by uid 55); 26 Feb 2020 19:25:59 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90951] [8/9 Regression] error initializing a constexpr array of a struct with const member
Date: Wed, 26 Feb 2020 19: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: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90951-4-WhYl7D6pQB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03166.txt.bz2
Content-length: 864
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90951
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:c51ac41714469104ee6120db3eedfb0964290502
commit r9-8292-gc51ac41714469104ee6120db3eedfb0964290502
Author: Jason Merrill <jason@redhat.com>
Date: Wed Feb 26 13:03:23 2020 -0500
c++: Fix constexpr vs. omitted aggregate init.
Value-initialization is importantly different from {}-initialization for
this testcase, where the former calls the deleted S constructor and the
latter initializes S happily.
gcc/cp/ChangeLog
2020-02-26 Jason Merrill <jason@redhat.com>
PR c++/90951
* constexpr.c (cxx_eval_array_reference): {}-initialize missing
elements instead of value-initializing them.
>From gcc-bugs-return-671585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 19:26:12 2020
Return-Path: <gcc-bugs-return-671585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5229 invoked by alias); 26 Feb 2020 19:26: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 5070 invoked by uid 55); 26 Feb 2020 19:26:05 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92003] [8/9 Regression] constexpr-ness of char const* doesn't propagate
Date: Wed, 26 Feb 2020 19: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: patch, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92003-4-EBSkcyZdX9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92003-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92003-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03168.txt.bz2
Content-length: 930
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92003
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:f2f70af7c52720a0905a455425de0d6ca4fb1dc4
commit r9-8293-gf2f70af7c52720a0905a455425de0d6ca4fb1dc4
Author: Jason Merrill <jason@redhat.com>
Date: Wed Feb 26 13:03:23 2020 -0500
cgraph: A COMDAT decl always has non-zero address.
We should be able to assume that a template instantiation or other COMDAT
has non-zero address even if MAKE_DECL_ONE_ONLY for the target sets
DECL_WEAK and we haven't yet decided to emit a definition in this
translation unit.
gcc/ChangeLog
2020-02-26 Jason Merrill <jason@redhat.com>
PR c++/92003
* symtab.c (symtab_node::nonzero_address): A DECL_COMDAT decl has
non-zero address even if weak and not yet defined.
>From gcc-bugs-return-671586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 19:26:18 2020
Return-Path: <gcc-bugs-return-671586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5941 invoked by alias); 26 Feb 2020 19: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 5231 invoked by uid 55); 26 Feb 2020 19:26:12 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92745] [9 Regression] Initializing array with vec4 results in compile error
Date: Wed, 26 Feb 2020 19: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: 8.3.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92745-4-TryyGs0RMi@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: 2020-02/txt/msg03167.txt.bz2
Content-length: 2819
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92745
--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:c890c9650f3c4b1be1f39eabb74b438c033a8c08
commit r9-8294-gc890c9650f3c4b1be1f39eabb74b438c033a8c08
Author: Marek Polacek <polacek@redhat.com>
Date: Fri Dec 20 23:30:04 2019 +0000
PR c++/92745 - bogus error when initializing array of vectors.
In r268428 I changed reshape_init_r in such a way that when it sees
a nested { } in a CONSTRUCTOR with missing braces, it just returns
the initializer:
+ else if (COMPOUND_LITERAL_P (stripped_init)
...
+ ++d->cur;
+ gcc_assert (!BRACE_ENCLOSED_INITIALIZER_P (stripped_init));
+ return init;
But as this test shows, that's incorrect: if TYPE is an array, we need
to proceed to reshape_init_array_1 which will iterate over the array
initializers:
6006 /* Loop until there are no more initializers. */
6007 for (index = 0;
6008 d->cur != d->end && (!sized_array_p || index <=
max_index_cst);
6009 ++index)
6010 {
and update d.cur accordingly. In other words, when reshape_init gets
{{col[0][0], col[1][0], col[2][0], col[3][0]},
{col[0][1], col[1][1], col[2][1], col[3][1]},
{col[0][2], col[1][2], col[2][2], col[3][2]},
{col[0][3], col[1][3], col[2][3], col[3][3]}}
we recurse on the first element:
{col[0][0], col[1][0], col[2][0], col[3][0]}
and we can't just move d.cur to point to
{col[0][1], col[1][1], col[2][1], col[3][1]}
and return; we need to iterate, so that d.cur ends up being properly
updated, and after all initializers have been seen, points to d.end.
Currently we skip the loop, wherefore we hit this:
6502 /* Make sure all the element of the constructor were used.
Otherwise,
6503 issue an error about exceeding initializers. */
6504 if (d.cur != d.end)
6505 {
6506 if (complain & tf_error)
6507 error ("too many initializers for %qT", type);
6508 return error_mark_node;
6509 }
gcc/cp/ChangeLog
2019-12-19 Marek Polacek <polacek@redhat.com>
PR c++/92745 - bogus error when initializing array of vectors.
* decl.c (reshape_init_r): For a nested compound literal, do
call reshape_init_{class,array,vector}.
gcc/testsuite/ChangeLog
2019-12-19 Marek Polacek <polacek@redhat.com>
Jakub Jelinek <jakub@redhat.com>
PR c++/92745 - bogus error when initializing array of vectors.
* g++.dg/cpp0x/initlist118.C: New test.
* g++.dg/cpp0x/initlist118.C: Add -Wno-psabi -w to dg-options.
>From gcc-bugs-return-671587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 19:43:38 2020
Return-Path: <gcc-bugs-return-671587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117007 invoked by alias); 26 Feb 2020 19:43: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 116976 invoked by uid 48); 26 Feb 2020 19:43:34 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93953] New: ice during during GIMPLE pass: vect
Date: Wed, 26 Feb 2020 19: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: 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 attachments.created
Message-ID: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03169.txt.bz2
Content-length: 1161
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93953
Bug ID: 93953
Summary: ice during during GIMPLE pass: vect
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: ---
Created attachment 47918
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47918&action=edit
C source code
For the attached C code, with recent gcc trunk
and compiler flag -O3, does this:
during GIMPLE pass: vect
../../../cl_screen.c: In function ‘CL_UpdateScreen’:
../../../cl_screen.c:2697:6: internal compiler error: Segmentation fault
0xee9b17 crash_signal
../../trunk.git/gcc/toplev.c:328
0x11c46b7 slp_copy_subtree
../../trunk.git/gcc/tree-vect-slp.c:1786
0x11c46ae slp_copy_subtree
../../trunk.git/gcc/tree-vect-slp.c:1785
0x11c46ae slp_copy_subtree
../../trunk.git/gcc/tree-vect-slp.c:1785
I'll have my usual go at finding a range where the problem
first starts and reducing the code.
>From gcc-bugs-return-671588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 19:47:26 2020
Return-Path: <gcc-bugs-return-671588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130521 invoked by alias); 26 Feb 2020 19:47: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 130485 invoked by uid 48); 26 Feb 2020 19:47:21 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93953] ice during during GIMPLE pass: vect
Date: Wed, 26 Feb 2020 19: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: 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:
Message-ID: <bug-93953-4-a6BrdLaapn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03170.txt.bz2
Content-length: 229
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93953
--- Comment #1 from David Binderman <dcb314 at hotmail dot com> ---
The bug first seems to occur sometime between 20200224 and 20200225.
That is yesterday and the day before.
>From gcc-bugs-return-671590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 20:01:46 2020
Return-Path: <gcc-bugs-return-671590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58164 invoked by alias); 26 Feb 2020 20:01: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 58113 invoked by uid 48); 26 Feb 2020 20:01:42 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93953] [10 Regression] ice during during GIMPLE pass: vect since r10-6838
Date: Wed, 26 Feb 2020 20: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: 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: keywords priority cc
Message-ID: <bug-93953-4-XppidNh9dU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03172.txt.bz2
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93953
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Priority|P3 |P1
CC| |rguenth at gcc dot gnu.org
>From gcc-bugs-return-671589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 20:01:26 2020
Return-Path: <gcc-bugs-return-671589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57334 invoked by alias); 26 Feb 2020 20:01: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 57287 invoked by uid 48); 26 Feb 2020 20:01:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93953] [10 Regression] ice during during GIMPLE pass: vect since r10-6838
Date: Wed, 26 Feb 2020 20: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:
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 cc component target_milestone short_desc everconfirmed
Message-ID: <bug-93953-4-pxY9eOTNhd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03171.txt.bz2
Content-length: 948
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93953
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-26
CC| |jakub at gcc dot gnu.org
Component|c |tree-optimization
Target Milestone|--- |10.0
Summary|ice during during GIMPLE |[10 Regression] ice during
|pass: vect |during GIMPLE pass: vect
| |since r10-6838
Ever confirmed|0 |1
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Indeed, started with r10-6838-g81c833b311b16cfd87a947374d5ffbbd48facd03
>From gcc-bugs-return-671591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 20:11:10 2020
Return-Path: <gcc-bugs-return-671591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9767 invoked by alias); 26 Feb 2020 20: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 9641 invoked by uid 48); 26 Feb 2020 20:11:06 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93948] Surprising option processing of -fdec and -fdec-math in combination with -std
Date: Wed, 26 Feb 2020 20:11: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:
X-Bugzilla-Severity: minor
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-93948-4-Xbw0KKrmhA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93948-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93948-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03173.txt.bz2
Content-length: 1075
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93948
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 ---
Thomas, the -std= options will cause gfortran to ignore all
nonstandard intrinsic subprograms. If you want nonstandard
intrinsic subprograms and use -std=f2008, then you need to
use the -fall-intrinsics option. For your example, I see
% gfcx -o z -std=f2008 -fall-intrinsics d.f90
/usr/local/bin/ld: /tmp/cceHxuCs.o: in function `MAIN__':
d.f90:(.text+0x5f): undefined reference to `sind_'
collect2: error: ld returned 1 exit status
% gfcx -o z -std=f2008 -fall-intrinsics -fdec d.f90
% ./z
0.00000000
% gfcx -o z -std=f2008 -fall-intrinsics -fdec-math d.f90
% ./z
0.00000000
We should probably consider removing -fdec-math option,
and handle the degree trig function like any other
nonstandard intrinsic subprogram.
>From gcc-bugs-return-671593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 20:17:47 2020
Return-Path: <gcc-bugs-return-671593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18765 invoked by alias); 26 Feb 2020 20:17: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 18707 invoked by uid 48); 26 Feb 2020 20:17:34 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93751] -g1 does not behave per manual
Date: Wed, 26 Feb 2020 20:17: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: documentation
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93751-4-10Rw75emNy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03175.txt.bz2
Content-length: 351
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93751
--- Comment #13 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
See https://gcc.gnu.org/contribute.html for the procedure. The patch is small
so you can probably skip the legal prerequisites, but you must post it on the
mailing list gcc-patches@gcc.gnu.org in order to get it approved.
>From gcc-bugs-return-671592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 20:17:05 2020
Return-Path: <gcc-bugs-return-671592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16861 invoked by alias); 26 Feb 2020 20: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 16816 invoked by uid 48); 26 Feb 2020 20:17:01 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93953] [10 Regression] ice during during GIMPLE pass: vect since r10-6838
Date: Wed, 26 Feb 2020 20: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93953-4-nVq4S34ebe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03174.txt.bz2
Content-length: 376
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93953
--- Comment #3 from David Binderman <dcb314 at hotmail dot com> ---
The results from creduce, lightly hand modified to add
some implied types, is
int *b;
int c;
float d, e;
void h() {
int f, g;
for (; f; ++f) {
float a = -(0 > g);
e += a * b[4 * (g + c * f)];
d += a * b[4 * (g + c * f) + 1];
}
}
>From gcc-bugs-return-671594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 20:20:16 2020
Return-Path: <gcc-bugs-return-671594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22727 invoked by alias); 26 Feb 2020 20:20: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 22619 invoked by uid 48); 26 Feb 2020 20:20:11 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93953] [10 Regression] ice during during GIMPLE pass: vect since r10-6838
Date: Wed, 26 Feb 2020 20: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-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-93953-4-ERW3DtjQWV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03176.txt.bz2
Content-length: 467
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93953
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reduced testcase:
/* PR tree-optimization/93953 */
/* { dg-do compile } */
/* { dg-options "-O3 --param=ggc-min-expand=0 --param=ggc-min-heapsize=0" } */
int *b, c, e;
float d, g, f;
void
foo (int l)
{
for (; l; ++l)
{
float a = g > l;
d += a * b[4 * (l + c * e)];
f += a * b[4 * (l + c * e) + 1];
}
}
>From gcc-bugs-return-671595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 20:25:59 2020
Return-Path: <gcc-bugs-return-671595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34585 invoked by alias); 26 Feb 2020 20:25: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 34533 invoked by uid 48); 26 Feb 2020 20:25:54 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93812] [9/10 Regression] ICE on redeclaration of an attribute format function without protoype
Date: Wed, 26 Feb 2020 20: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: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
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: bug_status assigned_to short_desc
Message-ID: <bug-93812-4-GKiakR25GY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03177.txt.bz2
Content-length: 2310
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93812
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
Summary|[9/10 Regression] ICE in |[9/10 Regression] ICE on
|get_constant, at |redeclaration of an
|c-family/c-format.c:325 |attribute format function
| |without protoype
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
I'm not sure it makes sense to accept attribute format on functions without a
prototype. It certainly doesn't make sense to keep it after a declaration to
which it can't be applied has been seen. The only other kind of a declaration
that the attribute can meaningfully be applied is a variadic one but such is
not accepted after one without a prototype.
GCC 8 does accept the attribute on functions without a prototype and even seems
to do behave sensibly for "sensible" calls with the format argument in the
right place, but without -Wformat-nonliteral it doesn't do anything useful if
the format argument is not of the right type (e.g., because it's misplaced)
such as in:
__attribute__((__format__(__printf__, 1, 2))) void foo ();
void bar (void)
{
foo (1, "%s", 2); // no warning
}
(As an aside, not diagnosing at least the call if not the declaration seems
like a bug because GCC doesn't accept attribute format on variadic functions
where the format doesn't have a declared type compatible with char* and where
the first-to-check argument isn't the position of the ellipsis (i.e., it can't
be an arbitrary position within the variable argument list).)
A simple solution is to simply drop the attribute from functions without a
prototype with a warning like Clang does:
warning: '__format__' attribute only applies to Objective-C
methods, blocks, and non-K&R-style functions [-Wignored-attributes]
A slightly more involved but less intrusive (to user code) solution is to drop
it when a redeclaration is seen with a prototype.
>From gcc-bugs-return-671596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 20:46:47 2020
Return-Path: <gcc-bugs-return-671596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74458 invoked by alias); 26 Feb 2020 20:46: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 74425 invoked by uid 48); 26 Feb 2020 20:46:43 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93789] [8/9/10 Regression] internal compiler error: in tree_to_uhwi, at tree.c:7361
Date: Wed, 26 Feb 2020 20: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: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-93789-4-jZJvTOfnjo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93789-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93789-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03178.txt.bz2
Content-length: 421
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93789
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
https://gcc.gnu.org/ml/gcc-patches/2020-02/msg01494.html
>From gcc-bugs-return-671597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 21:21:49 2020
Return-Path: <gcc-bugs-return-671597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117549 invoked by alias); 26 Feb 2020 21:21: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 117495 invoked by uid 48); 26 Feb 2020 21:21:44 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92745] [9 Regression] Initializing array with vec4 results in compile error
Date: Wed, 26 Feb 2020 21: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: 8.3.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92745-4-tbDqPdVBOL@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: 2020-02/txt/msg03179.txt.bz2
Content-length: 430
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92745
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #13 from Jason Merrill <jason at gcc dot gnu.org> ---
And for 9.3.
>From gcc-bugs-return-671598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 21:22:35 2020
Return-Path: <gcc-bugs-return-671598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119497 invoked by alias); 26 Feb 2020 21:22: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 119431 invoked by uid 48); 26 Feb 2020 21:22:31 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90951] [8/9 Regression] error initializing a constexpr array of a struct with const member
Date: Wed, 26 Feb 2020 21: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.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-90951-4-b9FArtY7wg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03180.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90951
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jason Merrill <jason at gcc dot gnu.org> ---
And 8.4 and 9.3.
>From gcc-bugs-return-671599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 21:23:24 2020
Return-Path: <gcc-bugs-return-671599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120427 invoked by alias); 26 Feb 2020 21:23: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 120379 invoked by uid 48); 26 Feb 2020 21:23:20 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92003] [8/9 Regression] constexpr-ness of char const* doesn't propagate
Date: Wed, 26 Feb 2020 21:23: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: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92003-4-hhwNeenjXq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92003-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92003-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03181.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92003
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jason Merrill <jason at gcc dot gnu.org> ---
And 8.4 and 9.3.
>From gcc-bugs-return-671600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 21:51:16 2020
Return-Path: <gcc-bugs-return-671600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100383 invoked by alias); 26 Feb 2020 21:51: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 100156 invoked by uid 48); 26 Feb 2020 21:51:11 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93140] [8/9 Regression] Segfault in cc1plus on incorrect decltype among function args
Date: Wed, 26 Feb 2020 21: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.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93140-4-v25vWtaWmd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03182.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93140
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for 8.4/9.3.
>From gcc-bugs-return-671601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 22:02:28 2020
Return-Path: <gcc-bugs-return-671601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118236 invoked by alias); 26 Feb 2020 22:02: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 118205 invoked by uid 48); 26 Feb 2020 22:02:22 -0000
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93936] [ranges] std::ranges::split_view<...>::_OuterIter<...>::__current() is private within this context
Date: Wed, 26 Feb 2020 22:02: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: ppalka at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ppalka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-93936-4-s6192iqNSF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93936-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93936-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03183.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93936
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-671602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 22:52:01 2020
Return-Path: <gcc-bugs-return-671602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116633 invoked by alias); 26 Feb 2020 22:52: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 116581 invoked by uid 48); 26 Feb 2020 22:51:56 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93812] [9/10 Regression] ICE on redeclaration of an attribute format function without protoype
Date: Wed, 26 Feb 2020 22: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, patch
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: keywords
Message-ID: <bug-93812-4-b7XemkzL5E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03184.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93812
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2020-02/msg01503.html
>From gcc-bugs-return-671603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 26 23:22:48 2020
Return-Path: <gcc-bugs-return-671603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32952 invoked by alias); 26 Feb 2020 23:22: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 32910 invoked by uid 55); 26 Feb 2020 23:22:44 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91276] Doc typos in __builtin_crypto_vpmsum*
Date: Wed, 26 Feb 2020 23:22: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: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-91276-4-GMFQQHEctQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91276-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91276-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03185.txt.bz2
Content-length: 1205
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91276
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Carl Love <carll@gcc.gnu.org>:
https://gcc.gnu.org/g:15fc2e04a592f8bfcc3eafead71d0313566d8372
commit r10-6877-g15fc2e04a592f8bfcc3eafead71d0313566d8372
Author: Carl Love <carll@us.ibm.com>
Date: Wed Feb 26 17:21:20 2020 -0600
PPC64, fix documentation for __builtin_crypto_vpmsum* builtin functions.
PR target/91276 - Doc typos in __builtin_crypto_vpmsum*
gcc/ChangeLog:
2020-02-26 Carl Love <cel@us.ibm.com>
PR target/91276
* doc/extend.texi (PowerPC AltiVec Built-in Functions available on
ISA 3.0): The builtin-function name __builtin_crypto_vpmsumb is only
for the vector unsigned short arguments. It is also listed as the
name of the built-in for arguments vector unsigned short,
vector unsigned int and vector unsigned long long built-ins. The
name of the builtins for these arguments should be:
__builtin_crypto_vpmsumh, __builtin_crypto_vpmsumw and
__builtin_crypto_vpmsumd respectively.
Signed-off-by: Carl Love <carll@us.ibm.com>
>From gcc-bugs-return-671604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 00:14:00 2020
Return-Path: <gcc-bugs-return-671604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77059 invoked by alias); 27 Feb 2020 00:14: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 76989 invoked by uid 55); 27 Feb 2020 00:13:55 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91276] Doc typos in __builtin_crypto_vpmsum*
Date: Thu, 27 Feb 2020 00: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: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-91276-4-HHcs6Ql724@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91276-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91276-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03186.txt.bz2
Content-length: 1065
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91276
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Carl Love <carll@gcc.gnu.org>:
https://gcc.gnu.org/g:f551b0889f56d2a89529e8cfce87f763f1a0bee9
commit r8-10092-gf551b0889f56d2a89529e8cfce87f763f1a0bee9
Author: Carl Love <carll@us.ibm.com>
Date: Wed Feb 26 18:12:17 2020 -0600
PR target/91276 - Doc typos in __builtin_crypto_vpmsum*
gcc/ChangeLog:
2020-02-26 Carl Love <cel@us.ibm.com>
PR target/91276
* doc/extend.texi (PowerPC AltiVec Built-in Functions): The
builtin-function name __builtin_crypto_vpmsumb is only for the
vector unsigned short arguments. It is also listed as the name of
the built-in for arguments vector unsigned short,
vector unsigned int and vector unsigned long long built-ins. The
name of the builtins for these arguments should be:
__builtin_crypto_vpmsumh, __builtin_crypto_vpmsumw and
__builtin_crypto_vpmsumd respectively.
>From gcc-bugs-return-671605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 00:23:57 2020
Return-Path: <gcc-bugs-return-671605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97098 invoked by alias); 27 Feb 2020 00:23: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 97044 invoked by uid 55); 27 Feb 2020 00:23:52 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91276] Doc typos in __builtin_crypto_vpmsum*
Date: Thu, 27 Feb 2020 00: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: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-91276-4-igJKEmhIFD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91276-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91276-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03187.txt.bz2
Content-length: 1163
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91276
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Carl Love <carll@gcc.gnu.org>:
https://gcc.gnu.org/g:526fadb010978c63dd06c0a85da3c4e1b5b1c63d
commit r9-8298-g526fadb010978c63dd06c0a85da3c4e1b5b1c63d
Author: Carl Love <carll@us.ibm.com>
Date: Wed Feb 26 18:22:46 2020 -0600
PPC64, fix documentation for __builtin_crypto_vpmsum* builtin functions.
PR target/91276 - Doc typos in __builtin_crypto_vpmsum*
gcc/ChangeLog:
2020-02-26 Carl Love <cel@us.ibm.com>
PR target/91276
* doc/extend.texi (PowerPC AltiVec Built-in Functions available on
ISA 3.0): The builtin-function name __builtin_crypto_vpmsumb is only
for the vector unsigned short arguments. It is also listed as the
name of the built-in for arguments vector unsigned short,
vector unsigned int and vector unsigned long long built-ins. The
name of the builtins for these arguments should be:
__builtin_crypto_vpmsumh, __builtin_crypto_vpmsumw and
__builtin_crypto_vpmsumd respectively.
>From gcc-bugs-return-671606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 00:25:26 2020
Return-Path: <gcc-bugs-return-671606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100082 invoked by alias); 27 Feb 2020 00:25: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 100002 invoked by uid 55); 27 Feb 2020 00:25:19 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Thu, 27 Feb 2020 00:25: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93871-4-ZDI48MZQ0z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03188.txt.bz2
Content-length: 2186
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #28 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Wed, Feb 26, 2020 at 04:02:23PM +0000, sgk at troutmask dot
apl.washington.edu wrote:
>
> > This is a best effort to still be able to use the standard library functions
> > but also get an increased accuracy expected from the degree functions.
> >
> > Thus:
> > 1. Calculate cosd(x) = sind(90 - x)
> > 2. Calculate cotand(x) = tand(90 - x)
> > 3. Reduce range of sind() argument from (0...360) further to x-360 if it is
> > above 270, and to 180-x if it is above 90
> >
>
Exhaustive testing in the domain [2**(-8),720] for REAL(4) gives
troutmask:sgk[347] gfcx -o z -O2 -fdec e.f90 && ./z
Total values tested: 146014209
ulp > 1.5 max ulp x at max ulp
WIP Patch[1]: 6558266 4331134.9 359.999969
fcn below[2]: 717 1.6212178 1.79070497
[1] Work in progress has implemented range reduction in the
interval [0,360], but does not fold the reduced range
as is done in fcn(x). The reference solution in the
ulp computation is fcn(x) converted to double precision.
[2] Only 9 exceed a max ulp of 1.6.
! Compute SIND(x) where x is in degrees.
function fcn(x) result(f)
real(sp) f
real(sp), intent(in) :: x
integer sgn
real(sp) arg
real(sp), parameter :: deg2rad = atan(1._sp) / 45
!
! Required for sin(-x) = - sin(x)
!
sgn = 1
if (x < 0) sgn = -1
arg = abs(x)
! 0 <= arg < 360
arg = modulo(arg, 360._sp)
! Fold into [0,90] range
if (arg <= 180) then
if (arg > 90) arg = 180 - arg
else
sgn = -sgn
arg = arg - 180
if (arg > 90) arg = 180 - arg
end if
if (arg == 180) then
f = sign(0._sp, real(sgn,sp))
else
f = sgn * sin(arg * deg2rad)
end if
end function fcn
Probably need to punt the above into libgfortran. Note,
for x < 2**(-8) we can do sin(x) ~ x
>From gcc-bugs-return-671607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 00:26:59 2020
Return-Path: <gcc-bugs-return-671607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101252 invoked by alias); 27 Feb 2020 00:26: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 101195 invoked by uid 48); 27 Feb 2020 00:26:54 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93848] missing -Warray-bounds warning for array subscript 1 is outside array bounds
Date: Thu, 27 Feb 2020 00:26: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: enhancement
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:
Message-ID: <bug-93848-4-Gwv6zuPIIF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03189.txt.bz2
Content-length: 722
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93848
--- Comment #10 from Martin Sebor <msebor at gcc dot gnu.org> ---
An array is implicitly converted to a pointer; it's not an lvalue. But I think
we're splitting hairs. I agree we want a warning for passing past-the-end
pointers to functions that might inadvertently dereference it; I plan to
implement it for GCC 11.
The reference in
int a[1][4];
printf("%p\n", (void *)&a[1][1]);
is of course undefined, but when the warning sees the address-of operator it
allows off-by-one indices. That's necessary only for the rightmost index but
not otherwise. The missing warning here is the subject of pr84079. I have a
simple fix that handles this case.
>From gcc-bugs-return-671608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 00:44:21 2020
Return-Path: <gcc-bugs-return-671608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40996 invoked by alias); 27 Feb 2020 00:44: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 40962 invoked by uid 48); 27 Feb 2020 00:44:17 -0000
From: "qrzhang at gatech dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93954] New: gcc generates wrong debug information at -O3
Date: Thu, 27 Feb 2020 00:44: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: qrzhang at gatech dot 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93954-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03190.txt.bz2
Content-length: 1152
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93954
Bug ID: 93954
Summary: gcc generates wrong debug information at -O3
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: qrzhang at gatech dot edu
Target Milestone: ---
It appears to be a regression in gcc-8. The code is pretty self-explanatory.
Bisection points to g:bd2b9f1e2d67ec8e88c977154ecfee
$ gcc-trunk -v
gcc version 10.0.1 20200226 (experimental) [master revision
4d213bf6011:5d3c19b2ec6:ce25177f505ea75b3c0833c3f3f0072b97ee1b44] (GCC)
#It incorrectly prints i = 2580636200
$ gcc-trunk -g-O3 abc.c
$ gdb -x cmds -batch a.out
Breakpoint 1 at 0x4003a0: file abc.c, line 4.
Breakpoint 1, main () at abc.c:4
4 ;// b here
$1 = 2580636200
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 17508) killed]
$ cat abc.c
int main() {
unsigned i = 2580636200;
i--;
;// b here
}
$ cat cmds
b abc.c:4
r
p i
kill
q
>From gcc-bugs-return-671609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 00:52:00 2020
Return-Path: <gcc-bugs-return-671609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111241 invoked by alias); 27 Feb 2020 00:51: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 111137 invoked by uid 48); 27 Feb 2020 00:51:56 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93954] gcc generates wrong debug information at -O3
Date: Thu, 27 Feb 2020 00:51: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: 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-93954-4-J41FAIU4bY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93954-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93954-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03191.txt.bz2
Content-length: 386
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93954
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>Bisection points to g:bd2b9f1e2d67ec8e88c977154ecfee
My bet is if you put a break point at "i--;" you would get the incorrect answer
before that patch.
Since the function just has one instruction at -O3, there is not an instruction
to place both lines there.
>From gcc-bugs-return-671610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 01:16:15 2020
Return-Path: <gcc-bugs-return-671610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93482 invoked by alias); 27 Feb 2020 01:16: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 93390 invoked by uid 48); 27 Feb 2020 01:16:05 -0000
From: "qrzhang at gatech dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93954] gcc generates wrong debug information at -O3
Date: Thu, 27 Feb 2020 01:16: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: qrzhang at gatech dot 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-93954-4-8GWPd0zTV6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93954-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93954-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03192.txt.bz2
Content-length: 903
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93954
--- Comment #2 from Qirun Zhang <qrzhang at gatech dot edu> ---
(In reply to Andrew Pinski from comment #1)
> >Bisection points to g:bd2b9f1e2d67ec8e88c977154ecfee
>
> My bet is if you put a break point at "i--;" you would get the incorrect
> answer before that patch.
> Since the function just has one instruction at -O3, there is not an
> instruction to place both lines there.
Break at "i--;" (at line 3) does give the same incorrect result.
However, before that patch, gcc works fine. I tested
g:6d3aa24cd6535dcfc9f0701579eca53aa1917
It gives me:
$ bin/bin/gcc -g -O3 abc.c
$ gdb -x cmds -batch a.out
Breakpoint 1 at 0x4003a0: file abc.c, line 3.
Breakpoint 1, main () at abc.c:4
4 ;// b here
$1 = 2580636199
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 19052) killed]
>From gcc-bugs-return-671611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 02:04:23 2020
Return-Path: <gcc-bugs-return-671611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5090 invoked by alias); 27 Feb 2020 02:04: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 5031 invoked by uid 55); 27 Feb 2020 02:04:19 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93947] ICE: Segmentation fault (in symtab_node::ultimate_alias_target)
Date: Thu, 27 Feb 2020 02:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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:
Message-ID: <bug-93947-4-jsFn7guWeZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93947-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03193.txt.bz2
Content-length: 1503
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93947
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:
https://gcc.gnu.org/g:0ba70d1b5ae8df6406a880b2d23e4710b393e8c9
commit r10-6879-g0ba70d1b5ae8df6406a880b2d23e4710b393e8c9
Author: David Malcolm <dmalcolm@redhat.com>
Date: Wed Feb 26 09:43:57 2020 -0500
analyzer: fix ICE on unreachable calls [PR 93947]
PR analyzer/93947 reports an ICE at -O1 when attempting to analyze a
call that has been optimized away as unreachable.
The root cause is a NULL dereference due to the fndecl having a NULL
cgraph_node: the cgraph_node was created by
pass_build_cgraph_edges::execute, but was later removed by
symbol_table::remove_unreachable_nodes before the analyzer pass.
This patch fixes it by checking for NULL before handling the
cgraph_node.
The reproducer demonstrates a weakness in the analyzer's constraint
handling, where region_model::apply_constraints_for_gswitch fails
to spot when the cases fully cover the data type, and thus make the
default impossible. For now this is xfail-ed in the testcase.
gcc/analyzer/ChangeLog:
PR analyzer/93947
* region-model.cc (region_model::get_fndecl_for_call): Gracefully
fail for fn_decls that don't have a cgraph_node.
gcc/testsuite/ChangeLog:
PR analyzer/93947
* gcc.dg/analyzer/torture/pr93947.c: New test.
>From gcc-bugs-return-671613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 02:07:05 2020
Return-Path: <gcc-bugs-return-671613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24932 invoked by alias); 27 Feb 2020 02:07: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 23512 invoked by uid 55); 27 Feb 2020 02:06:59 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93544] ICE in get_lvalue_1, at analyzer/region-model.cc:4613
Date: Thu, 27 Feb 2020 02:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93544-4-gVNFO0JAuA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93544-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93544-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03195.txt.bz2
Content-length: 1447
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93544
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:
https://gcc.gnu.org/g:71b633aaea3aac2d983da7b1b99da8c9a8c80d1a
commit r10-6880-g71b633aaea3aac2d983da7b1b99da8c9a8c80d1a
Author: David Malcolm <dmalcolm@redhat.com>
Date: Wed Feb 26 16:32:16 2020 -0500
analyzer: fix ICE with -Wanalyzer-null-dereference [PR 93950]
PR analyzer/93950 reports an ICE when pruning the path of a
-Wanalyzer-null-dereference diagnostic.
The root cause is a bug in the state-tracking code, in which the
variable of interest is tracked from the callee to a "nullptr" param
at the caller, whereupon we have an INTEGER_CST "variable", and
the attempt to look up its lvalue fails.
This code could use a rewrite; in the meantime this patch extends
the bulletproofing from g:8525d1f5f57b11fe04a97674cc2fc2b7727621d0
for PR analyzer/93544 to all of the various places where var can
be updated, fixing the ICE.
gcc/analyzer/ChangeLog:
PR analyzer/93950
* diagnostic-manager.cc
(diagnostic_manager::prune_for_sm_diagnostic): Assert that var is
either NULL or not a constant. When updating var, bulletproof
against constant values.
gcc/testsuite/ChangeLog:
PR analyzer/93950
* g++.dg/analyzer/pr93950.C: New test.
>From gcc-bugs-return-671612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 02:07:04 2020
Return-Path: <gcc-bugs-return-671612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24860 invoked by alias); 27 Feb 2020 02:07: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 23489 invoked by uid 55); 27 Feb 2020 02:06:59 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93950] ICE: in make_region_for_unexpected_tree_code, at analyzer/region-model.cc:4786 with -fanalyzer
Date: Thu, 27 Feb 2020 02:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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:
Message-ID: <bug-93950-4-QkncdKvCK5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93950-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03194.txt.bz2
Content-length: 1447
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93950
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:
https://gcc.gnu.org/g:71b633aaea3aac2d983da7b1b99da8c9a8c80d1a
commit r10-6880-g71b633aaea3aac2d983da7b1b99da8c9a8c80d1a
Author: David Malcolm <dmalcolm@redhat.com>
Date: Wed Feb 26 16:32:16 2020 -0500
analyzer: fix ICE with -Wanalyzer-null-dereference [PR 93950]
PR analyzer/93950 reports an ICE when pruning the path of a
-Wanalyzer-null-dereference diagnostic.
The root cause is a bug in the state-tracking code, in which the
variable of interest is tracked from the callee to a "nullptr" param
at the caller, whereupon we have an INTEGER_CST "variable", and
the attempt to look up its lvalue fails.
This code could use a rewrite; in the meantime this patch extends
the bulletproofing from g:8525d1f5f57b11fe04a97674cc2fc2b7727621d0
for PR analyzer/93544 to all of the various places where var can
be updated, fixing the ICE.
gcc/analyzer/ChangeLog:
PR analyzer/93950
* diagnostic-manager.cc
(diagnostic_manager::prune_for_sm_diagnostic): Assert that var is
either NULL or not a constant. When updating var, bulletproof
against constant values.
gcc/testsuite/ChangeLog:
PR analyzer/93950
* g++.dg/analyzer/pr93950.C: New test.
>From gcc-bugs-return-671614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 02:09:45 2020
Return-Path: <gcc-bugs-return-671614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34241 invoked by alias); 27 Feb 2020 02:09: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 34208 invoked by uid 48); 27 Feb 2020 02:09:27 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93947] ICE: Segmentation fault (in symtab_node::ultimate_alias_target)
Date: Thu, 27 Feb 2020 02:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
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: bug_status resolution
Message-ID: <bug-93947-4-HXHzcLSFfS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93947-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03196.txt.bz2
Content-length: 459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93947
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Should be fixed by the above commit.
>From gcc-bugs-return-671615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 02:10:08 2020
Return-Path: <gcc-bugs-return-671615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35196 invoked by alias); 27 Feb 2020 02:10: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 35145 invoked by uid 48); 27 Feb 2020 02:10:03 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93950] ICE: in make_region_for_unexpected_tree_code, at analyzer/region-model.cc:4786 with -fanalyzer
Date: Thu, 27 Feb 2020 02:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
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: bug_status resolution
Message-ID: <bug-93950-4-VZPt7VtrGB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93950-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03197.txt.bz2
Content-length: 459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93950
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Should be fixed by the above commit.
>From gcc-bugs-return-671616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 02:36:53 2020
Return-Path: <gcc-bugs-return-671616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31084 invoked by alias); 27 Feb 2020 02:36: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 30399 invoked by uid 48); 27 Feb 2020 02:36:43 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/80635] [8/9/10 regression] std::optional and bogus -Wmaybe-uninitialized warning
Date: Thu, 27 Feb 2020 02: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: 8.2.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason 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-80635-4-Ru7Vs9lcpN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80635-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80635-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03198.txt.bz2
Content-length: 1114
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80635
--- Comment #43 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #42)
> I suspect the V_C_E inhibits tree-ssa-uninit.c code to avoid false
> positives. If we know the range of the V_C_E operand is narrow enough that
> it fits into the type of the result of the V_C_E, could we optimize the
> V_C_E into a NOP_EXPR? We'd then forward propagate away the NOP_EXPR and
> the result is something the suppression code in tree-ssa-uninit.c can
> analyze better.
Looks like the V_C_E comes from sra_modify_assign:
if (!useless_type_conversion_p (TREE_TYPE (lhs), TREE_TYPE (rhs)))
{
=> rhs = fold_build1_loc (loc, VIEW_CONVERT_EXPR, TREE_TYPE (lhs),
rhs);
Here rhs (the scalar replacement variable) has unsigned QI type and lhs has
type bool.
Changing the type of 'live' to unsigned char avoids the V_C_E and thus indeed
the warning. This also works with the libstdc++ optional.
This seems like an SRA problem with fields of type bool.
>From gcc-bugs-return-671617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 02:47:26 2020
Return-Path: <gcc-bugs-return-671617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86825 invoked by alias); 27 Feb 2020 02:47: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 86796 invoked by uid 48); 27 Feb 2020 02:47:22 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93955] New: detect conversion from pointer type to arithmetic type in constexpr
Date: Thu, 27 Feb 2020 02: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: 10.0
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-93955-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03199.txt.bz2
Content-length: 828
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93955
Bug ID: 93955
Summary: detect conversion from pointer type to arithmetic type
in constexpr
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mpolacek at gcc dot gnu.org
Target Milestone: ---
constexpr long int
foo ()
{
return (long int) "foo"
#ifdef FOO
- 1
#endif
;
}
constexpr long int l = foo ();
is currently accepted with -DFOO but rejected otherwise. It should be rejected
even in the -DFOO case: converting a pointer to an integral type must be done
via a reinterpret_cast and that can't be part of a core constant expression.
>From gcc-bugs-return-671618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 02:49:21 2020
Return-Path: <gcc-bugs-return-671618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94431 invoked by alias); 27 Feb 2020 02:49: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 94410 invoked by uid 48); 27 Feb 2020 02:49:16 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93955] detect conversion from pointer type to arithmetic type in constexpr
Date: Thu, 27 Feb 2020 02: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: accepts-invalid
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: keywords
Message-ID: <bug-93955-4-sgGXAGE3hv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93955-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93955-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03200.txt.bz2
Content-length: 1102
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93955
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |accepts-invalid
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
The problem is that
/* Technically we should check this for all subexpressions, but that
runs into problems with our internal representation of pointer
subtraction and the 5.19 rules are still in flux. */
if (CONVERT_EXPR_CODE_P (TREE_CODE (r))
&& ARITHMETIC_TYPE_P (TREE_TYPE (r))
&& TREE_CODE (TREE_OPERAND (r, 0)) == ADDR_EXPR)
{
if (!allow_non_constant)
error ("conversion from pointer type %qT "
"to arithmetic type %qT in a constant expression",
TREE_TYPE (TREE_OPERAND (r, 0)), TREE_TYPE (r));
non_constant_p = true;
}
only works on the outermost expression, as the comment says.
Looks like a GCC 11 project.
>From gcc-bugs-return-671619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 02:58:38 2020
Return-Path: <gcc-bugs-return-671619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120696 invoked by alias); 27 Feb 2020 02:58: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 120655 invoked by uid 55); 27 Feb 2020 02:58:34 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93789] [8/9/10 Regression] internal compiler error: in tree_to_uhwi, at tree.c:7361
Date: Thu, 27 Feb 2020 02: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: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93789-4-bqResifZLt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93789-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93789-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03201.txt.bz2
Content-length: 1818
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93789
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:
https://gcc.gnu.org/g:1231f71f96a4e461f94394b4fb8cfa25587fbd96
commit r10-6881-g1231f71f96a4e461f94394b4fb8cfa25587fbd96
Author: Marek Polacek <polacek@redhat.com>
Date: Wed Feb 26 15:02:25 2020 -0500
c++: Fix ICE with invalid array bounds [PR93789]
r7-2111 introduced maybe_constant_value in cp_fully_fold.
maybe_constant_value uses cxx_eval_outermost_constant_expr, which
can clear TREE_CONSTANT:
6510 else if (non_constant_p && TREE_CONSTANT (r))
[...]
6529 TREE_CONSTANT (r) = false;
In this test the array size is '(long int) "h"'. This used to be
TREE_CONSTANT but given the change above, the flag will be cleared
when we cp_fully_fold the array size in compute_array_index_type_loc.
That means we don't emit an error in the
10391 else if (TREE_CONSTANT (size)
block in the same function, and we go on. Then we compute ITYPE
using cp_build_binary_op and use maybe_constant_value on it and
suddenly we have something that's TREE_CONSTANT again. And then we
crash in reshape_init_array_1 in tree_to_uhwi, because what we have
doesn't fit in an unsigned HWI.
icc accepts this code, but since we used to reject it, I see no desire
to make this work, so don't use the folded result when we've lost
the TREE_CONSTANT flag while evaluating the size.
2020-02-26 Marek Polacek <polacek@redhat.com>
PR c++/93789 - ICE with invalid array bounds.
* decl.c (compute_array_index_type_loc): Don't use the folded
size when folding cleared TREE_CONSTANT.
* g++.dg/ext/vla22.C: New test.
>From gcc-bugs-return-671620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 02:59:59 2020
Return-Path: <gcc-bugs-return-671620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121957 invoked by alias); 27 Feb 2020 02:59: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 121928 invoked by uid 48); 27 Feb 2020 02:59:55 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93789] [8/9/10 Regression] internal compiler error: in tree_to_uhwi, at tree.c:7361
Date: Thu, 27 Feb 2020 02: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: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code, 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: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93789-4-G1mXBRoai5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93789-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93789-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03202.txt.bz2
Content-length: 508
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93789
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed for GCC 10. Since it's ice-on-invalid, I'm not planning to backport the
fix.
>From gcc-bugs-return-671621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 03:23:36 2020
Return-Path: <gcc-bugs-return-671621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24382 invoked by alias); 27 Feb 2020 03:23: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 24362 invoked by uid 48); 27 Feb 2020 03:23:31 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/84079] missing -Warray-bounds taking the address of a multidimensional array element
Date: Thu, 27 Feb 2020 03: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: 8.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: bug_status cf_reconfirmed_on everconfirmed cf_known_to_fail
Message-ID: <bug-84079-4-RVduBZmFft@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84079-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84079-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03203.txt.bz2
Content-length: 575
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84079
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-27
Ever confirmed|0 |1
Known to fail|8.0 |10.0, 8.2.0, 9.2.0
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed based on bug 93848 comment 9.
>From gcc-bugs-return-671623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 03:25:52 2020
Return-Path: <gcc-bugs-return-671623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38294 invoked by alias); 27 Feb 2020 03:25: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 38270 invoked by uid 48); 27 Feb 2020 03:25:48 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/84079] missing -Warray-bounds taking the address of a multidimensional array element
Date: Thu, 27 Feb 2020 03: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: 8.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: 11.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to target_milestone
Message-ID: <bug-84079-4-J68oWBbUfE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84079-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84079-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03205.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84079
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
Target Milestone|--- |11.0
>From gcc-bugs-return-671622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 03:25:04 2020
Return-Path: <gcc-bugs-return-671622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25894 invoked by alias); 27 Feb 2020 03:25: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 25624 invoked by uid 48); 27 Feb 2020 03:25:00 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/84079] missing -Warray-bounds taking the address of a multidimensional array element
Date: Thu, 27 Feb 2020 03: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: 8.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: attachments.created
Message-ID: <bug-84079-4-laN4hExsZn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84079-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84079-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03204.txt.bz2
Content-length: 290
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84079
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Created attachment 47919
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47919&action=edit
Tested patch for GCC 11.
The attached patch adds the missing warning.
>From gcc-bugs-return-671624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 03:39:43 2020
Return-Path: <gcc-bugs-return-671624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10619 invoked by alias); 27 Feb 2020 03:39: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 10562 invoked by uid 48); 27 Feb 2020 03:39:39 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89550] [8/9/10 Regression] Spurious array-bounds warning when using __PRETTY_FUNCTION__ as a string_view
Date: Thu, 27 Feb 2020 03: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: 8.2.1
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: 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-89550-4-2pjWSEuxvB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89550-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89550-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03206.txt.bz2
Content-length: 530
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89550
--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
GCC 10 doesn't warn on the submitted test case so it looks like the change in
r269485 suppressed it. The patch was submitted here:
https://gcc.gnu.org/ml/gcc-patches/2019-03/msg00321.html
There's no test case in the commit and from the description on gcc-patches it's
not clear if the patch was supposed to be a fix for this bug or just some
general fix. Jakub, should this be resolved as fixed or what?
>From gcc-bugs-return-671625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 03:42:28 2020
Return-Path: <gcc-bugs-return-671625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12208 invoked by alias); 27 Feb 2020 03: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 12164 invoked by uid 48); 27 Feb 2020 03:42:19 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/86833] missing warning for out-of-bounds array access without optimization
Date: Thu, 27 Feb 2020 03: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: unknown
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: cf_reconfirmed_on cf_known_to_fail
Message-ID: <bug-86833-4-PhqWib3r6K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86833-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03207.txt.bz2
Content-length: 446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86833
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2019-02-11 00:00:00 |2020-2-26
Known to fail| |10.0, 9.2.0
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
No progress in GCC 10.
>From gcc-bugs-return-671626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 03:54:33 2020
Return-Path: <gcc-bugs-return-671626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31306 invoked by alias); 27 Feb 2020 03:54: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 31284 invoked by uid 55); 27 Feb 2020 03:54:29 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90467] Documentation: many warning options that are enabled by default are documented in the -Woption form, not -Wno-option
Date: Thu, 27 Feb 2020 03: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: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-90467-4-4MWYekhK6O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90467-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90467-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03208.txt.bz2
Content-length: 1177
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90467
--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Sandra Loosemore <sandra@gcc.gnu.org>:
https://gcc.gnu.org/g:cf70bb0fbd7fb0f4bca99c53a36d0a389dcc2fc5
commit r10-6882-gcf70bb0fbd7fb0f4bca99c53a36d0a389dcc2fc5
Author: Sandra Loosemore <sandra@codesourcery.com>
Date: Wed Feb 26 19:51:06 2020 -0800
Document negative form of warning options enabled by default [PR90467].
2020-02-26 Sandra Loosemore <sandra@codesourcery.com>
PR c++/90467
gcc/
* doc/invoke.texi (Option Summary): Re-alphabetize warnings in
C++ Language Options, Warning Options, and Static Analyzer
Options lists. Document negative form of options enabled by
default. Move some things around to more accurately sort
warnings by category.
(C++ Dialect Options, Warning Options, Static Analyzer
Options): Document negative form of options when enabled by
default. Move some things around to more accurately sort
warnings by category. Add some missing index entries.
Light copy-editing.
>From gcc-bugs-return-671627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 06:51:06 2020
Return-Path: <gcc-bugs-return-671627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128571 invoked by alias); 27 Feb 2020 06:51: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 128548 invoked by uid 48); 27 Feb 2020 06:51:02 -0000
From: "mscfd at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93956] New: Wrong array creation with p => array_dt(1:n)%component
Date: Thu, 27 Feb 2020 06:51: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.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mscfd at gmx 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-93956-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03209.txt.bz2
Content-length: 1414
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93956
Bug ID: 93956
Summary: Wrong array creation with p => array_dt(1:n)%component
Product: gcc
Version: 9.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: mscfd at gmx dot net
Target Milestone: ---
The following code (compiled without any options) prints "15000, 10000" for the
second call to foo, instead of the expected "20000, 10000". The first call to
foo gives the expected result. This is also reproducible with gfortran-10
branch.
This code is a variation of the one reported in bug 93918 to further understand
temporary array creation.
program array_temps
implicit none
type :: tt
integer :: u = 1
integer :: v = 2
end type tt
type(tt), dimension(:), pointer :: r
integer :: n
integer, dimension(:), pointer :: p
allocate(r(1:n))
call foo(r(:)%v, n)
p => get(r(:))
call foo(p, n)
deallocate(r)
contains
subroutine foo(a, n)
integer, dimension(:), intent(in) :: a
integer, intent(in) :: n
print *, sum(a(1:n)), n
end subroutine foo
function get(x) result(q)
type(tt), dimension(:), target, intent(in) :: x
integer, dimension(:), pointer :: q
q => x(:)%v
end function get
end program array_temps
>From gcc-bugs-return-671628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 06:57:52 2020
Return-Path: <gcc-bugs-return-671628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18493 invoked by alias); 27 Feb 2020 06:57: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 18396 invoked by uid 48); 27 Feb 2020 06:57:46 -0000
From: "zhroma at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92410] Invalid access to df->insns[] in regstat_bb_compute_calls_crossed (caught by hwasan)
Date: Thu, 27 Feb 2020 06: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: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zhroma at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: matmal01 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92410-4-xZoa8hroeG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92410-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92410-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03210.txt.bz2
Content-length: 646
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92410
Roman Zhuykov <zhroma at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zhroma at gcc dot gnu.org
--- Comment #10 from Roman Zhuykov <zhroma at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #3)
> Confirmed also with r247015 (GCC 7 branch point).
(In reply to Martin Liška from comment #9)
> I would close this as fixed.
Asked about backporting, see
https://gcc.gnu.org/ml/gcc-patches/2020-02/msg01523.html
>From gcc-bugs-return-671629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 06:59:32 2020
Return-Path: <gcc-bugs-return-671629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25996 invoked by alias); 27 Feb 2020 06:59: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 25936 invoked by uid 48); 27 Feb 2020 06:59:27 -0000
From: "kito at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90811] [nvptx] ptxas error on OpenMP offloaded code
Date: Thu, 27 Feb 2020 06: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: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kito 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: attachments.created
Message-ID: <bug-90811-4-13uUO7CJO6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03211.txt.bz2
Content-length: 589
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90811
--- Comment #17 from Kito Cheng <kito at gcc dot gnu.org> ---
Created attachment 47920
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47920&action=edit
update-local-align-pass.patch
Hi Jakub:
I got your point, and I agree with your point, estimate_stack_frame_size not
the right place to update alignment.
I write a patch to add a new pass to update the data alignment, executed at
begging of pass_all_early_optimizations, PoC patch attached, it's not fully
tested yet, how do you think about this approach?
Thanks :)
>From gcc-bugs-return-671630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 07:31:58 2020
Return-Path: <gcc-bugs-return-671630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60328 invoked by alias); 27 Feb 2020 07: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 60198 invoked by uid 48); 27 Feb 2020 07:31:45 -0000
From: "thenlich at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Thu, 27 Feb 2020 07:31: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: thenlich at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93871-4-8gFIm6YDc5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03212.txt.bz2
Content-length: 334
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #29 from Thomas Henlich <thenlich at gcc dot gnu.org> ---
(In reply to Steve Kargl from comment #28)
> ! Fold into [0,90] range
...
> if (arg == 180) then
I don't understand how (arg == 180) could be true after folding into [0,90]
range.
>From gcc-bugs-return-671631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 07:46:32 2020
Return-Path: <gcc-bugs-return-671631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70418 invoked by alias); 27 Feb 2020 07:46: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 70344 invoked by uid 48); 27 Feb 2020 07:46:28 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90811] [nvptx] ptxas error on OpenMP offloaded code
Date: Thu, 27 Feb 2020 07: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: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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:
Message-ID: <bug-90811-4-ig4IuqJnP7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03213.txt.bz2
Content-length: 712
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90811
--- Comment #18 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Kito Cheng from comment #17)
> Created attachment 47920 [details]
> update-local-align-pass.patch
>
> Hi Jakub:
>
> I got your point, and I agree with your point, estimate_stack_frame_size not
> the right place to update alignment.
>
> I write a patch to add a new pass to update the data alignment, executed at
> begging of pass_all_early_optimizations, PoC patch attached, it's not fully
> tested yet, how do you think about this approach?
Could you change pass_data_ipa_increase_alignment instead? Which does a
similar thing except for global variables.
>From gcc-bugs-return-671632-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 08:28:03 2020
Return-Path: <gcc-bugs-return-671632-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31082 invoked by alias); 27 Feb 2020 08:28: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 30972 invoked by uid 48); 27 Feb 2020 08:27:58 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90811] [nvptx] ptxas error on OpenMP offloaded code
Date: Thu, 27 Feb 2020 08: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: 8.3.1
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90811-4-UAQlrnKsLh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03214.txt.bz2
Content-length: 971
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90811
--- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Kito Cheng from comment #17)
> Created attachment 47920 [details]
> update-local-align-pass.patch
>
> Hi Jakub:
>
> I got your point, and I agree with your point, estimate_stack_frame_size not
> the right place to update alignment.
>
> I write a patch to add a new pass to update the data alignment, executed at
> begging of pass_all_early_optimizations, PoC patch attached, it's not fully
> tested yet, how do you think about this approach?
The placement is definitely wrong.
For OpenMP/OpenACC offloading, it needs to be after
/* These passes are run after IPA passes on every function that is being
output to the assembler file. */
INSERT_PASSES_AFTER (all_passes)
because before that the IL is used for both host and offloading targets, and
both might have different local variable alignment preferences.
>From gcc-bugs-return-671633-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 08:48:44 2020
Return-Path: <gcc-bugs-return-671633-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82670 invoked by alias); 27 Feb 2020 08:48: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 82480 invoked by uid 48); 27 Feb 2020 08:48:00 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93955] detect conversion from pointer type to arithmetic type in constexpr
Date: Thu, 27 Feb 2020 08: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: 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-93955-4-pPxNammeHN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93955-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93955-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03215.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93955
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-27
Ever confirmed|0 |1
>From gcc-bugs-return-671634-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 09:14:36 2020
Return-Path: <gcc-bugs-return-671634-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55518 invoked by alias); 27 Feb 2020 09:14: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 55362 invoked by uid 55); 27 Feb 2020 09:14:26 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93945] [9/10 Regression] memset of non-zero constant followed by bitfield read big-endian miscompilation since r9-547
Date: Thu, 27 Feb 2020 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: 9.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93945-4-CVvnjNQcKA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03216.txt.bz2
Content-length: 1407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93945
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:5f9cd512c4278621435cce486dd00248ea2e821c
commit r10-6885-g5f9cd512c4278621435cce486dd00248ea2e821c
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Feb 27 10:12:52 2020 +0100
sccvn: Handle non-byte aligned offset or size for memset (, 123, )
[PR93945]
The following is the last spot in vn_reference_lookup_3 that didn't allow
non-byte aligned offsets or sizes. To be precise, it did allow size that
wasn't multiple of byte size and that caused a wrong-code issue on
big-endian, as the pr93945.c testcase shows, so for GCC 9 we should add
&& multiple_p (ref->size, BITS_PER_UNIT) check instead.
For the memset with SSA_NAME middle-argument, it still requires
byte-aligned
offset, as we'd otherwise need to rotate the value at runtime.
2020-02-27 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/93582
PR tree-optimization/93945
* tree-ssa-sccvn.c (vn_reference_lookup_3): Handle memset with
non-zero INTEGER_CST second argument and ref->offset or ref->size
not a multiple of BITS_PER_UNIT.
* gcc.dg/tree-ssa/pr93582-9.c: New test.
* gcc.c-torture/execute/pr93945.c: New test.
>From gcc-bugs-return-671635-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 09:14:37 2020
Return-Path: <gcc-bugs-return-671635-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55523 invoked by alias); 27 Feb 2020 09:14: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 55406 invoked by uid 55); 27 Feb 2020 09:14:30 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93582] [10 Regression] -Warray-bounds gives error: array subscript 0 is outside array bounds of struct E[1]
Date: Thu, 27 Feb 2020 09:14: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, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93582-4-faRhokPTaa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93582-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93582-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03217.txt.bz2
Content-length: 1408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93582
--- Comment #33 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:5f9cd512c4278621435cce486dd00248ea2e821c
commit r10-6885-g5f9cd512c4278621435cce486dd00248ea2e821c
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Feb 27 10:12:52 2020 +0100
sccvn: Handle non-byte aligned offset or size for memset (, 123, )
[PR93945]
The following is the last spot in vn_reference_lookup_3 that didn't allow
non-byte aligned offsets or sizes. To be precise, it did allow size that
wasn't multiple of byte size and that caused a wrong-code issue on
big-endian, as the pr93945.c testcase shows, so for GCC 9 we should add
&& multiple_p (ref->size, BITS_PER_UNIT) check instead.
For the memset with SSA_NAME middle-argument, it still requires
byte-aligned
offset, as we'd otherwise need to rotate the value at runtime.
2020-02-27 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/93582
PR tree-optimization/93945
* tree-ssa-sccvn.c (vn_reference_lookup_3): Handle memset with
non-zero INTEGER_CST second argument and ref->offset or ref->size
not a multiple of BITS_PER_UNIT.
* gcc.dg/tree-ssa/pr93582-9.c: New test.
* gcc.c-torture/execute/pr93945.c: New test.
>From gcc-bugs-return-671636-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 09:16:01 2020
Return-Path: <gcc-bugs-return-671636-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57410 invoked by alias); 27 Feb 2020 09:15: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 57382 invoked by uid 48); 27 Feb 2020 09:15:54 -0000
From: "thenlich at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93948] Surprising option processing of -fdec and -fdec-math in combination with -std
Date: Thu, 27 Feb 2020 09:15: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:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: thenlich 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-93948-4-q2264iDlWk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93948-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93948-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03218.txt.bz2
Content-length: 1055
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93948
--- Comment #2 from Thomas Henlich <thenlich at gcc dot gnu.org> ---
-fall-intrinsics is a nice workaround, but it also enables more than I want.
I just find it not intuitive, that -fdec apparently has the same effect as
-fall-intrinsics for some intrinsics, but -fdec-math (an option to actually
enable some intrinsics) does not.
As documented:
"-fall-intrinsics
This option causes all intrinsic procedures (including the GNU-specific
extensions) to be accepted."
Just not those which require -fdec or -fdec-math.
"-fdec-math
Enable legacy math intrinsics such as COTAN and degree-valued trigonometric
functions (e.g. TAND, ATAND, etc...) for compatability with older code."
Requiring one of -fdec or -fall-intrinsics, if -std is specified. Is redundant
in the first case.
Any plan for action regarding this option should probably consider the fact
that decimal trigonometry functions are on the work list for Fortran 202X,
which if passed would leave only COTAN as a non-standard function.
>From gcc-bugs-return-671637-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 09:17:01 2020
Return-Path: <gcc-bugs-return-671637-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68964 invoked by alias); 27 Feb 2020 09:16: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 68920 invoked by uid 48); 27 Feb 2020 09:16:55 -0000
From: "jrfsousa at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93957] New: ICE (regression) passing assumed rank arrays with bind(c)
Date: Thu, 27 Feb 2020 09:16: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: jrfsousa 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-93957-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03219.txt.bz2
Content-length: 730
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93957
Bug ID: 93957
Summary: ICE (regression) passing assumed rank arrays with
bind(c)
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jrfsousa at gmail dot com
Target Milestone: ---
Created attachment 47921
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47921&action=edit
Code triggering ICE
Hi all!
ICE regression probably introduced by the patch to PR92123 in:
GNU Fortran (GCC) 10.0.1 20200224 (experimental)
Best regards,
José Rui
>From gcc-bugs-return-671638-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 09:34:45 2020
Return-Path: <gcc-bugs-return-671638-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54275 invoked by alias); 27 Feb 2020 09:34: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 53727 invoked by uid 48); 27 Feb 2020 09:34:36 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93949] [8/9/10 Regression] Register const local var will not compile since r0-58166
Date: Thu, 27 Feb 2020 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.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: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority
Message-ID: <bug-93949-4-BMFMKm5keh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03220.txt.bz2
Content-length: 355
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93949
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Priority|P3 |P2
>From gcc-bugs-return-671639-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 09:46:53 2020
Return-Path: <gcc-bugs-return-671639-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81842 invoked by alias); 27 Feb 2020 09:46: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 81658 invoked by uid 55); 27 Feb 2020 09:46:49 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93949] [8/9/10 Regression] Register const local var will not compile since r0-58166
Date: Thu, 27 Feb 2020 09: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: 9.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-93949-4-J1MJCP0iBB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03221.txt.bz2
Content-length: 1416
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93949
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:1956773cc655dfcba8d310066d3f6585dd4b8972
commit r10-6886-g1956773cc655dfcba8d310066d3f6585dd4b8972
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Feb 27 10:45:30 2020 +0100
gimplify: Don't optimize register const vars to static [PR93949]
The following testcase is rejected, while it was accepted in 3.4 and
earlier
(before tree-ssa merge).
The problem is that we decide to promote the const variable to TREE_STATIC,
but TREE_STATIC DECL_REGISTER VAR_DECLs may only be the global register
vars
and so assemble_variable/make_decl_rtl diagnoses it.
Either we do what the following patch does, where we could consider
register as a hint the user doesn't want such optimization, because if
something is forced static, it is not "register" anymore and register
static
is not valid in C either, or we could clear DECL_REGISTER instead, but
would
still need to punt at least on DECL_HARD_REGISTER cases.
2020-02-27 Jakub Jelinek <jakub@redhat.com>
PR c/93949
* gimplify.c (gimplify_init_constructor): Don't promote readonly
DECL_REGISTER variables to TREE_STATIC.
* gcc.c-torture/compile/pr93949.c: New test.
>From gcc-bugs-return-671640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 10:16:33 2020
Return-Path: <gcc-bugs-return-671640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77444 invoked by alias); 27 Feb 2020 10:16: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 76408 invoked by uid 48); 27 Feb 2020 10:15:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93953] [10 Regression] ice during during GIMPLE pass: vect since r10-6838
Date: Thu, 27 Feb 2020 10:16: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: bug_status assigned_to
Message-ID: <bug-93953-4-2RfdJJI5vV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03222.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93953
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 #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-671641-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 10:18:10 2020
Return-Path: <gcc-bugs-return-671641-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81841 invoked by alias); 27 Feb 2020 10:18: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 81190 invoked by uid 48); 27 Feb 2020 10:17:43 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93951] ICE with '-flto -g -femit-struct-debug-baseonly'
Date: Thu, 27 Feb 2020 10:18: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: 9.2.1
X-Bugzilla-Keywords: 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc cf_known_to_work everconfirmed cf_known_to_fail
Message-ID: <bug-93951-4-0RHrEkHeGD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03223.txt.bz2
Content-length: 842
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93951
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-bisection
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-27
CC| |marxin at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Known to work| |10.0
Ever confirmed|0 |1
Known to fail| |9.2.1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. Wonder what fixed it on trunk.
>From gcc-bugs-return-671642-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 10:26:44 2020
Return-Path: <gcc-bugs-return-671642-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120471 invoked by alias); 27 Feb 2020 10: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 117059 invoked by uid 55); 27 Feb 2020 10:24:23 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93945] [9/10 Regression] memset of non-zero constant followed by bitfield read big-endian miscompilation since r9-547
Date: Thu, 27 Feb 2020 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: 9.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93945-4-UHB6PlD1qd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03224.txt.bz2
Content-length: 960
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93945
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:a460bf38dc3582ce1f559cc84084ca27e429b34c
commit r9-8299-ga460bf38dc3582ce1f559cc84084ca27e429b34c
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Feb 27 11:21:52 2020 +0100
sccvn: Punt on ref->size not multiple of 8 for memset (, 123, ) in 9.x
[PR93945]
And here is the corresponding 9.x change where we the patch just punts if
ref->size is not whole bytes, like we already punt if offseti is not byte
aligned.
2020-02-27 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/93945
* tree-ssa-sccvn.c (vn_reference_lookup_3): For memset with non-zero
second operand, require ref->size to be a multiple of BITS_PER_UNIT.
* gcc.c-torture/execute/pr93945.c: New test.
>From gcc-bugs-return-671643-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 10:28:46 2020
Return-Path: <gcc-bugs-return-671643-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126481 invoked by alias); 27 Feb 2020 10:27: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 123684 invoked by uid 55); 27 Feb 2020 10:26:43 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93949] [8/9/10 Regression] Register const local var will not compile since r0-58166
Date: Thu, 27 Feb 2020 10: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: 9.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-93949-4-M9EPeVN1QD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03225.txt.bz2
Content-length: 1423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93949
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:b51057817d9a1aee4f24372f8c97f81f372c0a21
commit r9-8300-gb51057817d9a1aee4f24372f8c97f81f372c0a21
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Feb 27 10:45:30 2020 +0100
gimplify: Don't optimize register const vars to static [PR93949]
The following testcase is rejected, while it was accepted in 3.4 and
earlier
(before tree-ssa merge).
The problem is that we decide to promote the const variable to TREE_STATIC,
but TREE_STATIC DECL_REGISTER VAR_DECLs may only be the global register
vars
and so assemble_variable/make_decl_rtl diagnoses it.
Either we do what the following patch does, where we could consider
register as a hint the user doesn't want such optimization, because if
something is forced static, it is not "register" anymore and register
static
is not valid in C either, or we could clear DECL_REGISTER instead, but
would
still need to punt at least on DECL_HARD_REGISTER cases.
2020-02-27 Jakub Jelinek <jakub@redhat.com>
PR c/93949
* gimplify.c (gimplify_init_constructor): Don't promote readonly
DECL_REGISTER variables to TREE_STATIC.
* gcc.c-torture/compile/pr93949.c: New test.
>From gcc-bugs-return-671644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 10:31:48 2020
Return-Path: <gcc-bugs-return-671644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2501 invoked by alias); 27 Feb 2020 10: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 130085 invoked by uid 48); 27 Feb 2020 10:28:43 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93954] gcc generates wrong debug information at -O3
Date: Thu, 27 Feb 2020 10:29: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: wrong-debug
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: keywords bug_status cf_reconfirmed_on version everconfirmed
Message-ID: <bug-93954-4-PygMYtpRuk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93954-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93954-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03226.txt.bz2
Content-length: 1732
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93954
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-debug
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-27
Version|unknown |10.0
Ever confirmed|0 |1
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
So with GCC 7 we just have line number 5 and always print the value after
the decrement. With GCC 9 we claim we actually have sth at line 4
(but not earlier).
(gdb) start
Temporary breakpoint 1 at 0x4003a0: file t.c, line 4.
Starting program: /tmp/a.out
Temporary breakpoint 1, main () at t.c:4
4 ;// b here
(gdb) p i
$1 = 2580636200
(gdb) disassemble
Dump of assembler code for function main:
=> 0x00000000004003a0 <+0>: xor %eax,%eax
0x00000000004003a2 <+2>: retq
End of assembler dump.
(gdb) si
0x00000000004003a2 4 ;// b here
(gdb) p i
$2 = 2580636199
so now we have both values but with bogus line numbers for the pre-decrement
point. .optimized GIMPLE:
main ()
{
<bb 2> [local count: 1073741824]:
[t.c:2:3] # DEBUG BEGIN_STMT
[t.c:2:12] # DEBUG i => 2580636200
[t.c:3:3] # DEBUG BEGIN_STMT
[t.c:3:4] # DEBUG i => 2580636199
[t.c:4:3] # DEBUG BEGIN_STMT
[<built-in>:0:0] return 0;
which looks sensible. Not sure if a producer or consumer issue but not
having an instruction at line 3 makes things difficult (and value
2580636200 at line 4 is certainly wrong).
>From gcc-bugs-return-671645-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 10:32:18 2020
Return-Path: <gcc-bugs-return-671645-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4910 invoked by alias); 27 Feb 2020 10:30: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 498 invoked by uid 48); 27 Feb 2020 10:29:09 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93945] [9/10 Regression] memset of non-zero constant followed by bitfield read big-endian miscompilation since r9-547
Date: Thu, 27 Feb 2020 10: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: 9.2.1
X-Bugzilla-Keywords: wrong-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: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93945-4-zlwJzRtgST@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93945-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03227.txt.bz2
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93945
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 9.3+.
>From gcc-bugs-return-671646-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 10:43:50 2020
Return-Path: <gcc-bugs-return-671646-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57760 invoked by alias); 27 Feb 2020 10:41: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 52354 invoked by uid 48); 27 Feb 2020 10:39:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93953] [10 Regression] ice during during GIMPLE pass: vect since r10-6838
Date: Thu, 27 Feb 2020 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: 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-93953-4-DU1VLGD2xU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03228.txt.bz2
Content-length: 141
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93953
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Doh. Testing fix.
>From gcc-bugs-return-671647-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 10:56:47 2020
Return-Path: <gcc-bugs-return-671647-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90390 invoked by alias); 27 Feb 2020 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 82480 invoked by uid 48); 27 Feb 2020 10:49:55 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93957] [10 Regression] ICE (regression) passing assumed rank arrays with bind(c)
Date: Thu, 27 Feb 2020 10:53: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: UNCONFIRMED
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: keywords priority target_milestone short_desc
Message-ID: <bug-93957-4-8yeEr0l6H1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93957-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93957-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03229.txt.bz2
Content-length: 683
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93957
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Priority|P3 |P4
Target Milestone|--- |10.0
Summary|ICE (regression) passing |[10 Regression] ICE
|assumed rank arrays with |(regression) passing
|bind(c) |assumed rank arrays with
| |bind(c)
>From gcc-bugs-return-671649-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 12:46:28 2020
Return-Path: <gcc-bugs-return-671649-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36847 invoked by alias); 27 Feb 2020 12:46: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 36811 invoked by uid 55); 27 Feb 2020 12:46:22 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93953] [10 Regression] ice during during GIMPLE pass: vect since r10-6838
Date: Thu, 27 Feb 2020 12: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: cvs-commit 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-93953-4-ZQPZpNPOPf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03231.txt.bz2
Content-length: 786
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93953
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Guenther <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:e840185b31e40466e1575507200e1600e2343454
commit r10-6890-ge840185b31e40466e1575507200e1600e2343454
Author: Richard Biener <rguenther@suse.de>
Date: Thu Feb 27 13:42:56 2020 +0100
tree-optimization/93953 - avoid reference into hash-map
When possibly expanding a hash-map avoid keeping a reference to an
entry.
2020-02-27 Richard Biener <rguenther@suse.de>
PR tree-optimization/93953
* tree-vect-slp.c (slp_copy_subtree): Avoid keeping a reference
to the hash-map entry.
* gcc.dg/pr93953.c: New testcase.
>From gcc-bugs-return-671648-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 12:46:00 2020
Return-Path: <gcc-bugs-return-671648-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35983 invoked by alias); 27 Feb 2020 12:46: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 35540 invoked by uid 48); 27 Feb 2020 12:45:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93953] [10 Regression] ice during during GIMPLE pass: vect since r10-6838
Date: Thu, 27 Feb 2020 12: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-93953-4-V6QBKc4Qlr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93953-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03230.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93953
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671650-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 12:49:15 2020
Return-Path: <gcc-bugs-return-671650-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43421 invoked by alias); 27 Feb 2020 12:49: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 43380 invoked by uid 55); 27 Feb 2020 12:49:05 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93508] VN doesn't handle _chk functions or valueize their length
Date: Thu, 27 Feb 2020 12: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93508-4-qDe6eegKRt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93508-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93508-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03232.txt.bz2
Content-length: 996
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93508
--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Guenther <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:e431546ff9f1367538ed1307a1c98fa32fec7a8a
commit r10-6891-ge431546ff9f1367538ed1307a1c98fa32fec7a8a
Author: Richard Biener <rguenther@suse.de>
Date: Thu Feb 27 13:46:34 2020 +0100
tree-optimization/93508 - make VN translate through _chk and valueize
length
Value-numbering failed to handle __builtin_{memcpy,memset,...}_chk
variants when removing abstraction and also failed to use the
value-numbering lattice when requiring the length argument of the
call to be constant.
2020-02-27 Richard Biener <rguenther@suse.de>
PR tree-optimization/93508
* tree-ssa-sccvn.c (vn_reference_lookup_3): Handle _CHK like
non-_CHK variants. Valueize their length arguments.
* gcc.dg/tree-ssa/ssa-fre-85.c: New testcase.
>From gcc-bugs-return-671652-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 12:53:50 2020
Return-Path: <gcc-bugs-return-671652-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48673 invoked by alias); 27 Feb 2020 12: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 48497 invoked by uid 48); 27 Feb 2020 12:53: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: Thu, 27 Feb 2020 12:53: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-HsmQmfkoxm@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: 2020-02/txt/msg03234.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
Bug 92645 depends on bug 93508, which changed state.
Bug 93508 Summary: VN doesn't handle _chk functions or valueize their length
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93508
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-671651-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 12:53:50 2020
Return-Path: <gcc-bugs-return-671651-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48542 invoked by alias); 27 Feb 2020 12:53: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 48476 invoked by uid 48); 27 Feb 2020 12:53:42 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93508] VN doesn't handle _chk functions or valueize their length
Date: Thu, 27 Feb 2020 12:53: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: 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-93508-4-pf9ayrL6De@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93508-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93508-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03233.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93508
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-671653-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 13:32:14 2020
Return-Path: <gcc-bugs-return-671653-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86414 invoked by alias); 27 Feb 2020 13: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 86376 invoked by uid 48); 27 Feb 2020 13:32:09 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93191] Conversions to arrays of unknown bound P0388 Fails for variadic args
Date: Thu, 27 Feb 2020 13: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: 10.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: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-93191-4-FEzPmtoiZm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93191-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93191-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03235.txt.bz2
Content-length: 1455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93191
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Will Wray from comment #4)
> Any follow-up from CWG?
Yes, thanks to Richard Smith. Regarding
int g(auto(&a)[]);
int test_g = g("");
int f(auto(*a)[]);
int test_f = f(&"");
"I think the wording has a bug here, in the reference case.
The 'f' case appears to be valid: per [temp.deduct.call]/4.2, "The
transformed A can be a[nother] pointer or pointer-to-member type that can
be converted to the deduced A via a function pointer conversion (7.3.13)
and/or qualification conversion (7.3.5)." (Aside: why "another"?)
The 'g' case *should* be valid, but [temp.deduct.call]/4.1 says only "If
the original P is a reference type, the deduced A (i.e., the type referred
to by the reference) can be more cv-qualified than the transformed A."
... which doesn't cover this kind of qualification conversion. We should
presumably allow anything reference-compatible, not only "more
cv-qualified" cases. (We'd need to be careful to make the reference part of
/4.3, which is the other reference-compatible case, still work properly.)"
So, confirmed, but I think it's GCC 11 material.
>From gcc-bugs-return-671654-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 13:35:50 2020
Return-Path: <gcc-bugs-return-671654-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88698 invoked by alias); 27 Feb 2020 13:35: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 88675 invoked by uid 48); 27 Feb 2020 13:35:41 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93958] New: gcc trunk supports -std=c++20 but not -std=gnu++20
Date: Thu, 27 Feb 2020 13:35: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: 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93958-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03236.txt.bz2
Content-length: 916
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93958
Bug ID: 93958
Summary: gcc trunk supports -std=c++20 but not -std=gnu++20
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: romain.geissler at amadeus dot com
Target Milestone: ---
Hi,
Quite simple (and not important) "bug" report, recently Jason added the support
of -std=c++20 (instead of -std=c++2a), but it looks like the gnu counter part
-std=gnu++20 is not allowed.
# This works:
g++ -std=c++20 -o /dev/null -x c++ -c - <<<""
# This doesn't:
g++ -std=gnu++20 -o /dev/null -x c++ -c - <<<""
g++: error: unrecognized command-line option ‘-std=gnu++20’; did you mean
‘-std=gnu++2a’?
Cheers,
Romain
>From gcc-bugs-return-671655-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 13:38:59 2020
Return-Path: <gcc-bugs-return-671655-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94933 invoked by alias); 27 Feb 2020 13:38: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 94882 invoked by uid 48); 27 Feb 2020 13:38:54 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93958] gcc trunk supports -std=c++20 but not -std=gnu++20
Date: Thu, 27 Feb 2020 13: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:
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: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-93958-4-lu7UIazgsD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93958-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93958-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03237.txt.bz2
Content-length: 748
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93958
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-02-27
CC| |mpolacek at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed. The fix should be part of a larger cxx2a -> cxx20 transformation.
I'm willing to do that.
>From gcc-bugs-return-671656-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 13:50:20 2020
Return-Path: <gcc-bugs-return-671656-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102147 invoked by alias); 27 Feb 2020 13:50: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 102114 invoked by uid 48); 27 Feb 2020 13:50:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93946] Bogus redundant store removal
Date: Thu, 27 Feb 2020 13: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:
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: cc
Message-ID: <bug-93946-4-zV5Grlf5eT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93946-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93946-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03238.txt.bz2
Content-length: 670
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93946
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at gcc dot gnu.org
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Ick. And DSEs "new" redundant store removal code is completely buggy in this
regard as well... adding noipa to foo makes the testcase still fail when FRE
is fixed. So fixing that as well... (and then there's still DOM as well,
with -fno-tree-dse which would delete the dead store).
>From gcc-bugs-return-671657-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 14:11:25 2020
Return-Path: <gcc-bugs-return-671657-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40703 invoked by alias); 27 Feb 2020 14: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 40641 invoked by uid 48); 27 Feb 2020 14:11:19 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92152] [10 Regression] Wrong code (Resurrection of PR53663)
Date: Thu, 27 Feb 2020 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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka 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-92152-4-Naj1Gax5YI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92152-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92152-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03239.txt.bz2
Content-length: 595
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92152
--- Comment #15 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
The following testcase:
union U { long long i; long f; };
struct a {union U u;};
struct aa {struct a a;};
struct b {union U u;};
struct bb {struct b b;};
long
foo (struct bb *bv, void *ptr)
{
struct aa *a = ptr;
struct bb *b = ptr;
bv->b.u.f = 1;
a->a.u.i = 0;
b->b.u.f = 0;
return bv->b.u.f;
}
int
main ()
{
union C {struct aa aa; struct bb bb;} v;
if (foo (&v.bb, &v) != 0)
__builtin_abort ();
return 0;
}
is misoptimized since GCC 4.6
>From gcc-bugs-return-671658-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 14:20:21 2020
Return-Path: <gcc-bugs-return-671658-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35594 invoked by alias); 27 Feb 2020 14:20: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 35520 invoked by uid 48); 27 Feb 2020 14:20:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93946] Bogus redundant store removal
Date: Thu, 27 Feb 2020 14: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:
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: attachments.created
Message-ID: <bug-93946-4-jmECH5sKBd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93946-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93946-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03240.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93946
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 47922
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47922&action=edit
patch I am testing
This is what I have now. Got to factor out that alias set. In VN consider
passing ao_ref everywhere, the order of set, base-set is easy to get wrong
since there's no type safety.
>From gcc-bugs-return-671659-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 14:42:45 2020
Return-Path: <gcc-bugs-return-671659-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22688 invoked by alias); 27 Feb 2020 14: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 21298 invoked by uid 48); 27 Feb 2020 14:42:40 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92152] [10 Regression] Wrong code (Resurrection of PR53663)
Date: Thu, 27 Feb 2020 14: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: 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-92152-4-jkCWykFWF1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92152-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92152-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03241.txt.bz2
Content-length: 720
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92152
--- Comment #16 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #15)
> The following testcase:
> union U { long long i; long f; };
> struct a {union U u;};
> struct aa {struct a a;};
> struct b {union U u;};
> struct bb {struct b b;};
>
> long
> foo (struct bb *bv, void *ptr)
> {
> struct aa *a = ptr;
> struct bb *b = ptr;
> bv->b.u.f = 1;
> a->a.u.i = 0;
> b->b.u.f = 0;
> return bv->b.u.f;
> }
>
> int
> main ()
> {
> union C {struct aa aa; struct bb bb;} v;
> if (foo (&v.bb, &v) != 0)
> __builtin_abort ();
> return 0;
> }
>
> is misoptimized since GCC 4.6
That is PR93946
>From gcc-bugs-return-671660-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 15:09:48 2020
Return-Path: <gcc-bugs-return-671660-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122047 invoked by alias); 27 Feb 2020 15:09: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 121955 invoked by uid 48); 27 Feb 2020 15:09:36 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93870] [8/9/10 Regression] User-defined conversion function not working in evaluation of template argument
Date: Thu, 27 Feb 2020 15: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: 7.1.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: 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-93870-4-r6o1zSSA2W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03242.txt.bz2
Content-length: 1024
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93870
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-27
CC| |mpolacek at gcc dot gnu.org
Target Milestone|--- |8.4
Summary|User-defined conversion |[8/9/10 Regression]
|function not working in |User-defined conversion
|evaluation of template |function not working in
|argument |evaluation of template
| |argument
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed. Started with r7-4012-g16b61424dd309f61326f577a6deb8487c6c1f291.
>From gcc-bugs-return-671661-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 15:16:28 2020
Return-Path: <gcc-bugs-return-671661-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130443 invoked by alias); 27 Feb 2020 15:16: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 130243 invoked by uid 48); 27 Feb 2020 15:16:24 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93959] New: g++.dg/analyzer/malloc.C FAILs
Date: Thu, 27 Feb 2020 15:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
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: dmalcolm 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_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-93959-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03243.txt.bz2
Content-length: 1977
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93959
Bug ID: 93959
Summary: g++.dg/analyzer/malloc.C FAILs
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
Target Milestone: ---
Host: *-*-solaris2.11
Target: *-*-solaris2.11
Build: *-*-solaris2.11
Since its introduction, the g++.dg/analyzer/malloc.C test FAILs on Solaris
(both SPARC and x86, 32 and 64-bit):
+FAIL: g++.dg/analyzer/malloc.C -std=c++14 (test for warnings, line 17)
+FAIL: g++.dg/analyzer/malloc.C -std=c++14 (test for warnings, line 23)
+FAIL: g++.dg/analyzer/malloc.C -std=c++14 (test for warnings, line 24)
+FAIL: g++.dg/analyzer/malloc.C -std=c++14 (test for warnings, line 8)
+FAIL: g++.dg/analyzer/malloc.C -std=c++17 (test for warnings, line 17)
+FAIL: g++.dg/analyzer/malloc.C -std=c++17 (test for warnings, line 23)
+FAIL: g++.dg/analyzer/malloc.C -std=c++17 (test for warnings, line 24)
+FAIL: g++.dg/analyzer/malloc.C -std=c++17 (test for warnings, line 8)
+FAIL: g++.dg/analyzer/malloc.C -std=c++2a (test for warnings, line 17)
+FAIL: g++.dg/analyzer/malloc.C -std=c++2a (test for warnings, line 23)
+FAIL: g++.dg/analyzer/malloc.C -std=c++2a (test for warnings, line 24)
+FAIL: g++.dg/analyzer/malloc.C -std=c++2a (test for warnings, line 8)
+FAIL: g++.dg/analyzer/malloc.C -std=c++98 (test for warnings, line 17)
+FAIL: g++.dg/analyzer/malloc.C -std=c++98 (test for warnings, line 23)
+FAIL: g++.dg/analyzer/malloc.C -std=c++98 (test for warnings, line 24)
+FAIL: g++.dg/analyzer/malloc.C -std=c++98 (test for warnings, line 8)
There's no compiler output for the testcase at all, warning or otherwise.
gcc-testresults doesn't show the failure on any other target.
>From gcc-bugs-return-671663-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 15:17:20 2020
Return-Path: <gcc-bugs-return-671663-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1603 invoked by alias); 27 Feb 2020 15: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 1412 invoked by uid 48); 27 Feb 2020 15:17:16 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93959] g++.dg/analyzer/malloc.C FAILs
Date: Thu, 27 Feb 2020 15:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
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: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-93959-4-actRf1ZIJk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93959-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93959-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03245.txt.bz2
Content-length: 286
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93959
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-671662-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 15:17:03 2020
Return-Path: <gcc-bugs-return-671662-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 686 invoked by alias); 27 Feb 2020 15: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 584 invoked by uid 55); 27 Feb 2020 15:16:58 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93948] Surprising option processing of -fdec and -fdec-math in combination with -std
Date: Thu, 27 Feb 2020 15: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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
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-93948-4-YrBZuw6qSj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93948-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93948-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03244.txt.bz2
Content-length: 1275
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93948
--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Feb 27, 2020 at 09:15:53AM +0000, thenlich at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93948
>
> --- Comment #2 from Thomas Henlich <thenlich at gcc dot gnu.org> ---
> -fall-intrinsics is a nice workaround, but it also enables more than I want.
>
It's not a workaround given the wording of the Fortran stanard.
A processor is allowed to provide additional intrinsic subprograms
not specified in the standard. However, if a program uses the
nonstandard subprograms that program is nonconforming. With a
-std= option, one is requested conformance to the Fortran standard,
which leads to a catch 22. When I introduced -fall-intrinsics, it
was suggested that we have -fintrinsics=cotan,sind to allow only
cotan and sind to be added to the set in Fortran standard. I did not
and still do not see how to do this given the number of nonstandard
intrinsics.
>
> Requiring one of -fdec or -fall-intrinsics, if -std is specified. Is redundant
> in the first case.
As I stated earlier, I think -fdec-math should go away and
these routines would be handled just like, for example,
etime().
>From gcc-bugs-return-671664-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 15:21:49 2020
Return-Path: <gcc-bugs-return-671664-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17723 invoked by alias); 27 Feb 2020 15:21: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 17668 invoked by uid 48); 27 Feb 2020 15:21:45 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93960] New: std::to_address doesn't work with past-the-end Debug Mode iterators
Date: Thu, 27 Feb 2020 15:21: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: 10.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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93960-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03246.txt.bz2
Content-length: 1899
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93960
Bug ID: 93960
Summary: std::to_address doesn't work with past-the-end Debug
Mode iterators
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
// -std=gnu++2a
#define _GLIBCXX_DEBUG
#include <vector>
int main()
{
std::vector<int> v{1, 2, 3};
(void) std::to_address(v.end());
}
This aborts:
/home/jwakely/gcc/10/include/c++/10.0.1/debug/safe_iterator.h:311:
In function:
__gnu_debug::_Safe_iterator<_Iterator, _Sequence, _Category>::pointer
__gnu_debug::_Safe_iterator<_Iterator, _Sequence,
_Category>::operator->() const [with _Iterator =
__gnu_cxx::__normal_iterator<int*, std::__cxx1998::vector<int,
std::allocator<int> > >; _Sequence = std::__debug::vector<int>;
_Category = std::forward_iterator_tag;
__gnu_debug::_Safe_iterator<_Iterator, _Sequence, _Category>::pointer =
int*]
Error: attempt to dereference a past-the-end iterator.
Objects involved in the operation:
iterator "this" @ 0x0x7ffca2d5b330 {
type = __gnu_cxx::__normal_iterator<int*, std::__cxx1998::vector<int,
std::allocator<int> > > (mutable iterator);
state = past-the-end;
references sequence with type 'std::__debug::vector<int,
std::allocator<int> >' @ 0x0x7ffca2d5b2e0
}
Aborted (core dumped)
We probably do want to be able to assert in operator-> so that we catch things
like end->foo() but we also need std::to_address to work.
The solution might be to overload std::to_address for our safe iterators, so
that it returns the _Base::operator->() pointer without doing the assertions.
>From gcc-bugs-return-671665-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 15:24:48 2020
Return-Path: <gcc-bugs-return-671665-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21665 invoked by alias); 27 Feb 2020 15:24: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 21517 invoked by uid 48); 27 Feb 2020 15:24:30 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93870] [8/9/10 Regression] User-defined conversion function not working in evaluation of template argument
Date: Thu, 27 Feb 2020 15: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.1.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: 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-93870-4-k61iDNj2bR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03247.txt.bz2
Content-length: 340
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93870
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Clearly we're trying to take the address of a TARGET_EXPR:
TARGET_EXPR <D.2381, operator~ (0)>
That's bad and we've had PRs about this in the past, e.g. Bug 87145. I suspect
the fix might be along the same lines.
>From gcc-bugs-return-671666-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 15:28:59 2020
Return-Path: <gcc-bugs-return-671666-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30538 invoked by alias); 27 Feb 2020 15:28: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 30462 invoked by uid 48); 27 Feb 2020 15:28:54 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93961] New: gnat.dg/lto24.adb FAILs
Date: Thu, 27 Feb 2020 15:28: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: 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_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-93961-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03248.txt.bz2
Content-length: 2300
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93961
Bug ID: 93961
Summary: gnat.dg/lto24.adb FAILs
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: ebotcazou at gcc dot gnu.org
Target Milestone: ---
Host: *-*-solaris2.11
Target: *-*-solaris2.11
Build: *-*-solaris2.11
The new gnat.dg/lto24.adb test ICEs on Solaris (both SPARC and x86, 32 and
64-bit):
+FAIL: gnat.dg/lto24.adb (internal compiler error)
+FAIL: gnat.dg/lto24.adb (test for excess errors)
+FAIL: gnat.dg/lto24.adb 8 blank line(s) in output
/vol/gcc/src/hg/master/local/gcc/testsuite/gnat.dg/lto24_pkg1.ads: In function
'lto24_pkg1__recEQ':
/vol/gcc/src/hg/master/local/gcc/testsuite/gnat.dg/lto24_pkg1.ads:9:8: error:
type mismatch in 'component_ref'
lto24_pkg1__rec___b___XVN
lto24_pkg1__rec___b___XVN
_10 = &y_4(D)->b___XVN.S1.a;
/vol/gcc/src/hg/master/local/gcc/testsuite/gnat.dg/lto24_pkg1.ads:9:8: error:
type mismatch in 'component_ref'
lto24_pkg1__rec___b___XVN
lto24_pkg1__rec___b___XVN
_11 = &x_15(D)->b___XVN.S1.a;
/vol/gcc/src/hg/master/local/gcc/testsuite/gnat.dg/lto24_pkg1.ads:9:8: error:
type mismatch in 'component_ref'
lto24_pkg1__rec___b___XVN
lto24_pkg1__rec___b___XVN
# VUSE <.MEM_16(D)>
_13 = x_15(D)->b___XVN.O.empty;
/vol/gcc/src/hg/master/local/gcc/testsuite/gnat.dg/lto24_pkg1.ads:9:8: error:
type mismatch in 'component_ref'
lto24_pkg1__rec___b___XVN
lto24_pkg1__rec___b___XVN
# VUSE <.MEM_16(D)>
_14 = y_4(D)->b___XVN.O.empty;
during GIMPLE pass: fixup_cfg
/vol/gcc/src/hg/master/local/gcc/testsuite/gnat.dg/lto24_pkg1.ads:9:8: internal
compiler error: verify_gimple failed
0x9090271 verify_gimple_in_cfg(function*, bool)
/vol/gcc/src/hg/master/local/gcc/tree-cfg.c:5459
0x8f576b7 execute_function_todo
/vol/gcc/src/hg/master/local/gcc/passes.c:1985
0x8f584ce do_per_function
/vol/gcc/src/hg/master/local/gcc/passes.c:1640
0x8f584ce execute_todo
/vol/gcc/src/hg/master/local/gcc/passes.c:2039
gcc-testresults shows the failure on no other target so far.
>From gcc-bugs-return-671667-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 15:29:25 2020
Return-Path: <gcc-bugs-return-671667-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31323 invoked by alias); 27 Feb 2020 15:29: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 31271 invoked by uid 48); 27 Feb 2020 15:29:21 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93961] gnat.dg/lto24.adb FAILs
Date: Thu, 27 Feb 2020 15: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: 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-93961-4-vlqgIiFKMz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93961-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03249.txt.bz2
Content-length: 286
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93961
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-671668-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 15:30:40 2020
Return-Path: <gcc-bugs-return-671668-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33304 invoked by alias); 27 Feb 2020 15:30: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 32822 invoked by uid 48); 27 Feb 2020 15:30:19 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93870] [8/9/10 Regression] User-defined conversion function not working in evaluation of template argument
Date: Thu, 27 Feb 2020 15: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: 7.1.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: priority
Message-ID: <bug-93870-4-YzLCOH0bHx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03250.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93870
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
>From gcc-bugs-return-671669-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 16:07:30 2020
Return-Path: <gcc-bugs-return-671669-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116205 invoked by alias); 27 Feb 2020 16:07: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 116123 invoked by uid 48); 27 Feb 2020 16:07:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93582] [10 Regression] -Warray-bounds gives error: array subscript 0 is outside array bounds of struct E[1]
Date: Thu, 27 Feb 2020 16:07: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, 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-93582-4-r6pAUHDQrH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93582-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93582-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03251.txt.bz2
Content-length: 380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93582
--- Comment #34 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47923
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47923&action=edit
gcc10-pr93582-wip.patch
WIP patch that fixes the original regression (handling of lookup through masked
loads).
Still need to create some further testcases.
>From gcc-bugs-return-671670-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 16:25:42 2020
Return-Path: <gcc-bugs-return-671670-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35795 invoked by alias); 27 Feb 2020 16:25: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 35759 invoked by uid 48); 27 Feb 2020 16:25:38 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93870] [8/9/10 Regression] User-defined conversion function not working in evaluation of template argument
Date: Thu, 27 Feb 2020 16: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: 7.1.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:
Message-ID: <bug-93870-4-9Xukj4A6H0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03252.txt.bz2
Content-length: 645
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93870
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Completely untested:
--- a/gcc/cp/pt.c
+++ b/gcc/cp/pt.c
@@ -7082,7 +7082,7 @@ convert_nontype_argument (tree type, tree expr,
tsubst_flags_t complain)
create a TARGET_EXPR, but in a template we can't
use AGGR_INIT_EXPR, and the TARGET_EXPR would lead
to a bogus error. */
- || (val_dep_p && MAYBE_CLASS_TYPE_P (type))))
+ || val_dep_p))
{
expr = build1 (IMPLICIT_CONV_EXPR, type, expr);
IMPLICIT_CONV_EXPR_NONTYPE_ARG (expr) = true;
>From gcc-bugs-return-671671-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 16:28:51 2020
Return-Path: <gcc-bugs-return-671671-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57070 invoked by alias); 27 Feb 2020 16:28: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 57041 invoked by uid 48); 27 Feb 2020 16:28:47 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93870] [8/9/10 Regression] User-defined conversion function not working in evaluation of template argument
Date: Thu, 27 Feb 2020 16: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: 7.1.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:
Message-ID: <bug-93870-4-EUq9uKuvuf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03253.txt.bz2
Content-length: 214
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93870
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Actually perhaps we should create an IMPLICIT_CONV_EXPR for *any*
value-dependent argument.
>From gcc-bugs-return-671672-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 16:36:21 2020
Return-Path: <gcc-bugs-return-671672-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79695 invoked by alias); 27 Feb 2020 16:36: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 79634 invoked by uid 48); 27 Feb 2020 16:36:17 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93564] [10 Regression] 470.lbm regresses by 25% on znver2 with -Ofast -march=native LTO and PGO since r10-6384-g2a07345c4f8dabc2
Date: Thu, 27 Feb 2020 16: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: ra
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-93564-4-HvyeRVp5N6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93564-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93564-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03254.txt.bz2
Content-length: 263
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93564
--- Comment #3 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
I checked the new results
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=288.240.0
It seems the patch solved the problem.
>From gcc-bugs-return-671673-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 17:12:45 2020
Return-Path: <gcc-bugs-return-671673-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79230 invoked by alias); 27 Feb 2020 17:12: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 79174 invoked by uid 48); 27 Feb 2020 17:12:41 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90467] Documentation: many warning options that are enabled by default are documented in the -Woption form, not -Wno-option
Date: Thu, 27 Feb 2020 17: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: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sandra 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 cc resolution
Message-ID: <bug-90467-4-tqwtr9GrPH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90467-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90467-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03255.txt.bz2
Content-length: 867
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90467
sandra at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |sandra at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #2 from sandra at gcc dot gnu.org ---
I've made a pass through all the warning options to try to fix this, plus
fixing alphabetization of the option summary sections, making sure the options
are documented in the section corresponding to where they are listed in the
option summary, all the C++ warnings are grouped together, etc. This section
of the manual is still a mess, though -- I'll try to do some more work on it as
I have time.
>From gcc-bugs-return-671674-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 17:20:16 2020
Return-Path: <gcc-bugs-return-671674-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89978 invoked by alias); 27 Feb 2020 17:20: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 89677 invoked by uid 48); 27 Feb 2020 17:20:10 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93959] g++.dg/analyzer/malloc.C FAILs
Date: Thu, 27 Feb 2020 17:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm 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-93959-4-6McnZYEzqQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93959-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93959-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03256.txt.bz2
Content-length: 887
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93959
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-02-27
Ever confirmed|0 |1
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Confirmed on sparc-sun-solaris2.11 (gcc211.fsffrance.org)
-fdump-ipa-analyzer shows it's failing to match "free" because it's using
std::free, not free:
test_1 (void * ptr)
{
<bb 2> :
std::free (ptr_2(D));
std::free (ptr_2(D));
return;
}
stdlib.h has "using std::free;" which presumably is what's pulling things in.
Explicitly prefixing with "::" doesn't help.
Converting to __builtin_free does.
>From gcc-bugs-return-671675-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 17:26:33 2020
Return-Path: <gcc-bugs-return-671675-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99144 invoked by alias); 27 Feb 2020 17:26: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 99088 invoked by uid 55); 27 Feb 2020 17:26:21 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Thu, 27 Feb 2020 17:26: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93871-4-HGNJQuvVhf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03257.txt.bz2
Content-length: 1499
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #30 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Feb 27, 2020 at 07:31:43AM +0000, thenlich at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
>
> --- Comment #29 from Thomas Henlich <thenlich at gcc dot gnu.org> ---
> (In reply to Steve Kargl from comment #28)
> > ! Fold into [0,90] range
> ...
> > if (arg == 180) then
>
> I don't understand how (arg == 180) could be true after folding into [0,90]
> range.
>
Whoops. I quickly threw that code together to
investigate the symmetry needed to fold [0,360]
into [0:90]. My guess is that I did a last
minute edit and moved the (arg == 180) condition
without checking or there is a subtle rounding
issue with (180 - nearest(180,+-1)). That code
certainly isn't production quality as there is
no special handling of +-Inf or NaN or tiny x.
We should also consider the upper normal x
limit where x > xmax=2**(p-e) where p is the
precision and e is some value where modulo(x,360)
is always integral. This is similar to the
radian sin(x) for REAL x and x > 2.**22.
I suppose that the point is that it is likely that
gfortran should not in-line the sind(x) function.
Creating the if-statement is doable in trans-intrinsic.c,
but may drive someone nuts to get right. For cosd(x),
your suggestion of cosd(x) = sind(90 - module(x,360))
looks promising and could be in-lined.
>From gcc-bugs-return-671676-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 17:38:08 2020
Return-Path: <gcc-bugs-return-671676-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76548 invoked by alias); 27 Feb 2020 17:38: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 76481 invoked by uid 55); 27 Feb 2020 17:38:02 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92152] [10 Regression] Wrong code (Resurrection of PR53663)
Date: Thu, 27 Feb 2020 17: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: cvs-commit 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-92152-4-hWEq7YpGcI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92152-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92152-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03258.txt.bz2
Content-length: 7365
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92152
--- Comment #17 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jan Hubicka <hubicka@gcc.gnu.org>:
https://gcc.gnu.org/g:9640ff5a88f25fc9bf581136fb25d1c2f756d5d4
commit r10-6903-g9640ff5a88f25fc9bf581136fb25d1c2f756d5d4
Author: Jan Hubicka <jh@suse.cz>
Date: Thu Feb 27 18:36:39 2020 +0100
middle-end: Fix wrong code caused by disagreemed between FRE and access
path oracle [PR 92152]
FRE is checking stores for equivalence based on their address, value and
base+ref alias sets. Because ref alias set is not always the alias set of
innermost type, but it may be one of refs in the access path (as decided by
component_uses_parent_alias_set_from) it means that we can not really rely
on
the remaining part of access path to be meaningful in any way except for
offset+size computation.
The patch makes alias (which is used by FRE to validate transform) and
tree-ssa-alias to share same logic for ending the access path relevant for
TBAA. tree-ssa-alias previously ended access paths on VIEW_CONVERT_EXPR and
BIT_FIELD_REF so it is not hard to wire in common predicate. However it
led to
additional issues (I tried to read the code quite carefully for possible
extra
fun, so I hope I found it all):
1) alias_component_refs_walk compares base and reference sizes to see
if one access path may continue by another. This check can be
confused
by an union containing structure with zero sized array. In this case
we
no longer see the refernece to zero sized array and think that ref
size
is 0.
In an access path there can be at most one (valid) trailing/zero sized
array access, so the sizes in the access path are decreasing with the
this exception. This is already handled by the logic, however the
access
is not expected to happen past the end of TBAA segment. I suppose
this
was kind of latent problem before because one can think of access path
doing traling array past VIEW_CONVERT_EXPR, but since in C code we
don't
VCE and in non-C we don't do trailing arrays, we did not hit the
problem.
I fixed this by tracking if the trailing array references appearing
after
the end of TBAA access path and mostly punt in the second case
(because we
need to support kind of all type puning here). I do not think we can
assume
much of sanity here, in particular, we no longer know there is only
one
because FRE may mix things up.
An exception is the walk that looks for occurence of basetype of path1
within TBAA relevant part of path2. Here we realy care about TBAA
relevant parts of paths and thus do not need to give up.
I broke out the logic into ends_tbaa_access_path_p to avoid
duplication and
to let me stick some detailed comments. This became much more complex
than I originally imagined (still it is useful to make oracle both
faster
and more precise).
Note that logic in aliasing_component_refs_walk is safe since it works
on TBAA relevant segments of paths only.
2) nonoverlapping_refs_since_match_p is using TBAA only in the corner
case
that the paths got out of sync and re-synchronize of types of same
size
are found. I thus extended it to whole paths (not only TBAA relevant
parts) and track if the TBAA part can be used by counting of number of
TBAA relevant res on the stack.
I have noticed that in one case we call
nonoverlapping_refs_since_match_p
before checking for view converting MEM_REFs and in others we check
after. I think we want to just disable TBAA part if view convert
is in there but still disambiguate. I will do this incrementaly.
3) nonoverlapping_component_refs_p uses TBAA so it needs to punt on
end of TBAA path. It deals with no sizes and thus there is not the
issue
as in 1).
I am also attaching one (most probably) valid C++ testcase (by Mark
Williams)
where we incorrectly disambiguated while the code is valid by the common
initial sequence rule. This happens to be fixed by same patch. Here one
access
goes through union and follows by access path trhough one filed, while
other
access path start by different field of the union with common initial
sequence.
This made aliasing_component_refs_p to not find the overlapping type
(because
there is none) and disambiguate. Now we cut the first access path by the
union
reference and this makes us to find the path continuation in
alias_component_refs_walk.
If FRE is ever made more careful about access paths past the fist union
reference (I think that would be good idea since unions are quite common in
C++
and we throw away quite useful info) then we will need to teach access path
oracle about the common initial sequence rule (which, as Mark pointed out,
is
part of both C and C++ standards).
Only argument that can possibly invalidate this testcase is that I do not
see
that stadnard is clear about the situation where one access path contains
the
union but other starts after the union.
Clearly if both start after the union reference we are right to
disambiguate
(since there is no union unvolved). If both starts before union then there
is
common initial sequence and by standard it is defined. This case works on
current
trunk because aliasing_component_refs_p resorts to base+offset after
finding
the match. But even that is more or less an accident I would say.
I had to xfail three testcases. While alias-access-path ones are
artificial
and odd, 20030807-7 is derived from gcc and shows that we give up on
disambiguations of tree_node union, so this patch disables useful transform
in real world code.
I am still planning to collect some data on the effect of this change to
TBAA,
but unless we want to reorganize FRE, I do not think there is better
solution.
gcc/ChangeLog:
2020-02-26 Jan Hubicka <hubicka@ucw.cz>
PR middle-end/92152
* alias.c (ends_tbaa_access_path_p): Break out from ...
(component_uses_parent_alias_set_from): ... here.
* alias.h (ends_tbaa_access_path_p): Declare.
* tree-ssa-alias.c (access_path_may_continue_p): Break out from ...;
handle trailing arrays past end of tbaa access path.
(aliasing_component_refs_p): ... here; likewise.
(nonoverlapping_refs_since_match_p): Track TBAA segment of the access
path; disambiguate also past end of it.
(nonoverlapping_component_refs_p): Use only TBAA segment of the access
path.
gcc/testsuite/ChangeLog:
2020-02-26 Jan Hubicka <hubicka@ucw.cz>
PR middle-end/92152
* gcc.dg/tree-ssa/alias-access-path-12.c: New testcase.
* g++.dg/torture/pr92152.C: New testcase.
* gcc.dg/torture/pr92152.c: New testcase.
* gcc.dg/tree-ssa/20030807-7.c: xfail.
* gcc.dg/tree-ssa/alias-access-path-4.c: xfail one case.
* gcc.dg/tree-ssa/alias-access-path-5.c: xfail one case.
>From gcc-bugs-return-671678-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 17:47:50 2020
Return-Path: <gcc-bugs-return-671678-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92336 invoked by alias); 27 Feb 2020 17: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 91909 invoked by uid 55); 27 Feb 2020 17:47:45 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93913] [10 regression] r10-6762 breaks gcc.target/powerpc/fold-vec-st-*.c test cases
Date: Thu, 27 Feb 2020 17: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: cvs-commit 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-93913-4-Uc3TclqTqi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93913-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93913-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03260.txt.bz2
Content-length: 920
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93913
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Peter Bergner
<bergner@gcc.gnu.org>:
https://gcc.gnu.org/g:98529e6d7408e896cb74c327ae60b3ccea055d9c
commit r9-8301-g98529e6d7408e896cb74c327ae60b3ccea055d9c
Author: Peter Bergner <bergner@linux.ibm.com>
Date: Wed Feb 26 11:58:08 2020 -0600
rs6000: Fix more testsuite fallout from rs6000_legitimate_address_p() fix.
[PR93913]
Backport from trunk
2020-02-26 Peter Bergner <bergner@linux.ibm.com>
PR target/93913
* gcc.target/powerpc/fold-vec-st-char.c (scan-assembler-times): Allow
stxv and stxvx instructions as well.
* gcc.target/powerpc/fold-vec-st-float.c: Likewise.
* gcc.target/powerpc/fold-vec-st-int.c: Likewise.
* gcc.target/powerpc/fold-vec-st-short.c: Likewise.
>From gcc-bugs-return-671677-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 17:47:13 2020
Return-Path: <gcc-bugs-return-671677-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90343 invoked by alias); 27 Feb 2020 17:47: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 90099 invoked by uid 55); 27 Feb 2020 17:46:58 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93707] ICE in perlbench from SPEC2017
Date: Thu, 27 Feb 2020 17: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: fxue at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93707-4-1JLGrEftRN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93707-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93707-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03259.txt.bz2
Content-length: 1026
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93707
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Jambor <jamborm@gcc.gnu.org>:
https://gcc.gnu.org/g:cfeef9acd2cec93ed6338cc0d9fad98bdc0f7599
commit r10-6904-gcfeef9acd2cec93ed6338cc0d9fad98bdc0f7599
Author: Martin Jambor <mjambor@suse.cz>
Date: Thu Feb 27 18:43:05 2020 +0100
ipa-cp: Avoid an ICE processing self-recursive cloned edges (PR 93707)
2020-02-27 Martin Jambor <mjambor@suse.cz>
Feng Xue <fxue@os.amperecomputing.com>
PR ipa/93707
* ipa-cp.c (same_node_or_its_all_contexts_clone_p): Replaced with
new function calls_same_node_or_its_all_contexts_clone_p.
(cgraph_edge_brings_value_p): Use it.
(cgraph_edge_brings_value_p): Likewise.
(self_recursive_pass_through_p): Return false if caller is a clone.
(self_recursive_agg_pass_through_p): Likewise.
testsuite/
* gcc.dg/ipa/pr93707.c: New test.
>From gcc-bugs-return-671679-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 17:49:36 2020
Return-Path: <gcc-bugs-return-671679-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93876 invoked by alias); 27 Feb 2020 17:49: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 93817 invoked by uid 48); 27 Feb 2020 17:49:15 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93913] [10 regression] r10-6762 breaks gcc.target/powerpc/fold-vec-st-*.c test cases
Date: Thu, 27 Feb 2020 17: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
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-93913-4-HwEAR1Lu9b@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93913-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93913-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03261.txt.bz2
Content-length: 446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93913
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Peter Bergner <bergner at gcc dot gnu.org> ---
Fixed on trunk and gcc 9.
>From gcc-bugs-return-671680-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 17:53:46 2020
Return-Path: <gcc-bugs-return-671680-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97776 invoked by alias); 27 Feb 2020 17:53: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 97690 invoked by uid 48); 27 Feb 2020 17:53:38 -0000
From: "thenlich at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Thu, 27 Feb 2020 17:53: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: thenlich at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93871-4-jIdGbOyUGW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03262.txt.bz2
Content-length: 320
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #31 from Thomas Henlich <thenlich at gcc dot gnu.org> ---
I wonder, if some "correct" rounding could further increase accuracy: We know
the sign and "real" magnitude of the difference deg2rad-Ï€/180 and can round the
result of sin() accordingly.
>From gcc-bugs-return-671682-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:24:53 2020
Return-Path: <gcc-bugs-return-671682-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5898 invoked by alias); 27 Feb 2020 18:24: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 5848 invoked by uid 48); 27 Feb 2020 18:24:49 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93923] [10 Regression] std::is_copy_constructible raises compilation error
Date: Thu, 27 Feb 2020 18:24: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: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93923-4-XHlDUT9nhL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03264.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93923
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #4 from Jeffrey A. Law <law at redhat dot com> ---
So, Jon your position would be NOTABUG?
>From gcc-bugs-return-671681-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:24:35 2020
Return-Path: <gcc-bugs-return-671681-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4016 invoked by alias); 27 Feb 2020 18:24: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 3680 invoked by uid 48); 27 Feb 2020 18:24:03 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93926] [10 Regression] ICE: verify_cgraph_node failed (error: malloc attribute should be used for a function that returns a pointer)
Date: Thu, 27 Feb 2020 18:24: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: ice-checking, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-93926-4-fKaP1emDYt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03263.txt.bz2
Content-length: 522
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93926
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-27
CC| |law at redhat dot com
Ever confirmed|0 |1
>From gcc-bugs-return-671683-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:25:32 2020
Return-Path: <gcc-bugs-return-671683-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7162 invoked by alias); 27 Feb 2020 18:25: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 6998 invoked by uid 48); 27 Feb 2020 18:25:28 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93877] [9/10 Regression] [SH] webkit2gtk fails to build with "internal compiler error: in extract_constrain_insn, at recog.c:2211"
Date: Thu, 27 Feb 2020 18: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: 9.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
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 cc
Message-ID: <bug-93877-4-SJ0VBClQ5Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03265.txt.bz2
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93877
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
CC| |law at redhat dot com
>From gcc-bugs-return-671684-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:25:59 2020
Return-Path: <gcc-bugs-return-671684-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8008 invoked by alias); 27 Feb 2020 18:25: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 7959 invoked by uid 48); 27 Feb 2020 18:25:53 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93829] [10 Regression] bogus -Wstringop-overflow on memcpy of a struct with a pointer member from another with a long string
Date: Thu, 27 Feb 2020 18:25: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, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-93829-4-sRSCm0o99e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03266.txt.bz2
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93829
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |law at redhat dot com
>From gcc-bugs-return-671685-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:30:50 2020
Return-Path: <gcc-bugs-return-671685-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11931 invoked by alias); 27 Feb 2020 18: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 11772 invoked by uid 48); 27 Feb 2020 18:30:42 -0000
From: "spop at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92692] Saving off the callee saved register between ldxr/stxr (caused by shrink wrapping improvements)
Date: Thu, 27 Feb 2020 18:30: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: wrong-code
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: spop at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: wilco at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92692-4-i3vC8YUbZL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92692-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92692-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03267.txt.bz2
Content-length: 1193
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92692
Sebastian Pop <spop at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |spop at gcc dot gnu.org
--- Comment #21 from Sebastian Pop <spop at gcc dot gnu.org> ---
It looks like this hunk from the trunk version of the patch is missing on gcc-9
branch:
diff --git a/gcc/config/aarch64/atomics.md b/gcc/config/aarch64/atomics.md
index cabcc58f1a0..1458bc00095 100644
--- a/gcc/config/aarch64/atomics.md
+++ b/gcc/config/aarch64/atomics.md
@@ -104,7 +104,7 @@
(clobber (match_scratch:SI 7 "=&r"))]
""
"#"
- "&& reload_completed"
+ "&& epilogue_completed"
[(const_int 0)]
{
aarch64_split_compare_and_swap (operands);
With this hunk applied my bootstrap passes on the gcc-9 branch on an
aarch64-linux graviton2.
Without this hunk I see an error in thread sanitizers.
I also have checked gcc-8 release branch and it seems that the patch is not
missing any hunks in that branch.
Could somebody apply the missing hunk to the gcc-9 release branch? Thanks!
>From gcc-bugs-return-671686-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:36:29 2020
Return-Path: <gcc-bugs-return-671686-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23937 invoked by alias); 27 Feb 2020 18:36: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 23886 invoked by uid 48); 27 Feb 2020 18:36:18 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93961] gnat.dg/lto24.adb FAILs
Date: Thu, 27 Feb 2020 18:36: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: ebotcazou 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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-93961-4-DbSBY3EY6X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93961-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03268.txt.bz2
Content-length: 527
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93961
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2020-02-27
Ever confirmed|0 |1
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Please check that it is really compiled at -O1.
>From gcc-bugs-return-671687-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:39:05 2020
Return-Path: <gcc-bugs-return-671687-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117023 invoked by alias); 27 Feb 2020 18:39: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 116960 invoked by uid 48); 27 Feb 2020 18:39:01 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92152] [10 Regression] Wrong code (Resurrection of PR53663)
Date: Thu, 27 Feb 2020 18: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: hubicka 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-92152-4-Kiw32hNPHd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92152-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92152-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03269.txt.bz2
Content-length: 425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92152
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #18 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671688-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:48:32 2020
Return-Path: <gcc-bugs-return-671688-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18074 invoked by alias); 27 Feb 2020 18:48: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 17914 invoked by uid 48); 27 Feb 2020 18:48:13 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93870] [8/9/10 Regression] User-defined conversion function not working in evaluation of template argument
Date: Thu, 27 Feb 2020 18: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: 7.1.0
X-Bugzilla-Keywords: 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: P2
X-Bugzilla-Assigned-To: mpolacek 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-93870-4-tGWDnxp4mW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03270.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93870
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Mine but it occurs to me I should get back to bug 91465 before attacking this
one. This one might even be fixed for free by the previous one.
>From gcc-bugs-return-671689-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:52:43 2020
Return-Path: <gcc-bugs-return-671689-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26825 invoked by alias); 27 Feb 2020 18:52: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 26541 invoked by uid 55); 27 Feb 2020 18:52:38 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93933] [concepts] redeclaration of constrained template give error
Date: Thu, 27 Feb 2020 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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: nathan at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93933-4-94VbK7YOPi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93933-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03271.txt.bz2
Content-length: 991
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93933
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>:
https://gcc.gnu.org/g:9d2d283367a407c1ba9ecdb8590f9295828e25f8
commit r10-6907-g9d2d283367a407c1ba9ecdb8590f9295828e25f8
Author: Nathan Sidwell <nathan@acm.org>
Date: Thu Feb 27 10:50:36 2020 -0800
Compare ARGUMENT_PACKS [pr93933]
This implements Jason's suggested approach: 'I'd think that the bug is
that we're treating them as types in the first place; they aren't
types, so they shouldn't reach comptypes. I'd lean toward adding an
assert to that effect and fixing the caller to use
e.g. template_args_equal.'
PR c++/93933
* pt.c (template_args_equal): Pass ARGUMENT_PACKS through to
cp_tree_equal.
* tree.c (cp_tree_equal): Compare ARGUMENT_PACKS here,
* typeck.c (comptypes): Assert we don't get any argument packs.
>From gcc-bugs-return-671690-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:54:09 2020
Return-Path: <gcc-bugs-return-671690-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29257 invoked by alias); 27 Feb 2020 18: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 29225 invoked by uid 48); 27 Feb 2020 18:54:06 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93933] [concepts] redeclaration of constrained template give error
Date: Thu, 27 Feb 2020 18: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: nathan at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93933-4-pbXEwXr6Jv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93933-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03272.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93933
Nathan Sidwell <nathan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
Fixed 9d2d283367a
>From gcc-bugs-return-671692-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:56:07 2020
Return-Path: <gcc-bugs-return-671692-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32676 invoked by alias); 27 Feb 2020 18: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 32575 invoked by uid 55); 27 Feb 2020 18:55:49 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Thu, 27 Feb 2020 18:55: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93871-4-T0laHPiEVL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03274.txt.bz2
Content-length: 1245
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #32 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Feb 27, 2020 at 05:53:38PM +0000, thenlich at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
>
> --- Comment #31 from Thomas Henlich <thenlich at gcc dot gnu.org> ---
> I wonder, if some "correct" rounding could further increase
> accuracy: We know the sign and "real" magnitude of the
> difference deg2rad-Ï€/180 and can round the result of sin()
> accordingly.
I think we can exploit a table-driven method. Once x is
folded into [0,90], x is split by x = n + dx where
n = 0, 1, ..., 90 and dx is in [0.,1.).
sin(x) = sin(n+d) = sin(n) * cos(d) + cos(n) * sin(d)
The table contains a high,low decomposition of {sin(1),cos(1)},
{sin(3),cos(3)}, ..., {sin(90),cos(90)}. Denote the decomposition
with shi(n), slo(n), chi(n), clo(n), and both C(d) = cos(d) and
S(d) * sin(d) are minimax polynomials. So, we have
if (x == n) /* Integral value of x. */
sin(x) = shi(n) + slo(n) ! Is addition needed.
else
sin(x) = shi(n)*C(d) + slo(n)*C(d) + chi(n)*S(d) + clo(n)*S(d)
The else-branch summation can be done with Kahan summation.
>From gcc-bugs-return-671691-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:55:02 2020
Return-Path: <gcc-bugs-return-671691-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30557 invoked by alias); 27 Feb 2020 18:55: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 30285 invoked by uid 48); 27 Feb 2020 18:54:58 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93800] [9/10 Regression] GCC adds unwanted nops to align loops on powerpc 8xx
Date: Thu, 27 Feb 2020 18: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: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
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 cc
Message-ID: <bug-93800-4-t81YduRLKm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93800-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93800-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03273.txt.bz2
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93800
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |law at redhat dot com
>From gcc-bugs-return-671693-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 18:59:35 2020
Return-Path: <gcc-bugs-return-671693-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36054 invoked by alias); 27 Feb 2020 18:59: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 35935 invoked by uid 48); 27 Feb 2020 18:59:26 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93745] Redundant store not eliminated with intermediate instruction
Date: Thu, 27 Feb 2020 18: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: law at redhat 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc
Message-ID: <bug-93745-4-2y2y3UUBEu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03275.txt.bz2
Content-length: 804
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93745
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
Summary|[8/9/10 Regression] |Redundant store not
|Redundant store not |eliminated with
|eliminated with |intermediate instruction
|intermediate instruction |
--- Comment #10 from Jeffrey A. Law <law at redhat dot com> ---
Dropping regression markers, but keeping open pending a decision on whether or
not we could some way to mark the dynamic type and ultimately allow us to
optimize this case.
>From gcc-bugs-return-671694-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:00:29 2020
Return-Path: <gcc-bugs-return-671694-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37389 invoked by alias); 27 Feb 2020 19:00: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 37155 invoked by uid 48); 27 Feb 2020 19:00:08 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93738] [9/10 regression] test case gcc.target/powerpc/20050603-3.c fails
Date: Thu, 27 Feb 2020 19:00: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: law at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
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 cc
Message-ID: <bug-93738-4-shgaY8TaPD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03276.txt.bz2
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93738
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |law at redhat dot com
>From gcc-bugs-return-671695-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:02:26 2020
Return-Path: <gcc-bugs-return-671695-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39566 invoked by alias); 27 Feb 2020 19: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 39490 invoked by uid 48); 27 Feb 2020 19:02:15 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/93731] [10 regression] asan tests cause kernel panic on Darwin 11
Date: Thu, 27 Feb 2020 19:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
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 cc
Message-ID: <bug-93731-4-B5BTgEVQKF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03277.txt.bz2
Content-length: 464
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93731
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
CC| |law at redhat dot com
--- Comment #6 from Jeffrey A. Law <law at redhat dot com> ---
Only affecting EOL systems, moving to P4.
>From gcc-bugs-return-671696-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:05:35 2020
Return-Path: <gcc-bugs-return-671696-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88857 invoked by alias); 27 Feb 2020 19: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 88808 invoked by uid 48); 27 Feb 2020 19:05:31 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93720] [10 Regression] vector creation from two parts of two vectors produces TBL rather than ins
Date: Thu, 27 Feb 2020 19: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-93720-4-uP0KPkrkKl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03278.txt.bz2
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93720
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |law at redhat dot com
>From gcc-bugs-return-671697-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:06:44 2020
Return-Path: <gcc-bugs-return-671697-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90037 invoked by alias); 27 Feb 2020 19: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 89978 invoked by uid 48); 27 Feb 2020 19:06:40 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93674] [8/9/10 Regression] GCC eliminates conditions it should not, when strict-enums is on
Date: Thu, 27 Feb 2020 19:06: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.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-93674-4-bVnixEN5i0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93674-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93674-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03279.txt.bz2
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93674
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
CC| |law at redhat dot com
>From gcc-bugs-return-671698-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:07:18 2020
Return-Path: <gcc-bugs-return-671698-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91745 invoked by alias); 27 Feb 2020 19:07: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 91700 invoked by uid 48); 27 Feb 2020 19:07:13 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93582] [10 Regression] -Warray-bounds gives error: array subscript 0 is outside array bounds of struct E[1]
Date: Thu, 27 Feb 2020 19:07: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, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-93582-4-Wk3EGtsUmH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93582-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93582-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03280.txt.bz2
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93582
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |law at redhat dot com
>From gcc-bugs-return-671699-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:08:34 2020
Return-Path: <gcc-bugs-return-671699-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114543 invoked by alias); 27 Feb 2020 19: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 114435 invoked by uid 48); 27 Feb 2020 19:08:30 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93564] [10 Regression] 470.lbm regresses by 25% on znver2 with -Ofast -march=native LTO and PGO since r10-6384-g2a07345c4f8dabc2
Date: Thu, 27 Feb 2020 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: ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: bug_status cc resolution
Message-ID: <bug-93564-4-h18elu30di@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93564-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93564-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03281.txt.bz2
Content-length: 492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93564
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |law at redhat dot com
Resolution|--- |FIXED
--- Comment #4 from Jeffrey A. Law <law at redhat dot com> ---
Per c#3.
>From gcc-bugs-return-671700-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:08:34 2020
Return-Path: <gcc-bugs-return-671700-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114585 invoked by alias); 27 Feb 2020 19: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 114477 invoked by uid 48); 27 Feb 2020 19:08:31 -0000
From: "law at redhat dot com" <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: Thu, 27 Feb 2020 19:08: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: law at redhat 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 resolution
Message-ID: <bug-26163-4-in1LfeiMYa@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: 2020-02/txt/msg03282.txt.bz2
Content-length: 551
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 93564, which changed state.
Bug 93564 Summary: [10 Regression] 470.lbm regresses by 25% on znver2 with -Ofast -march=native LTO and PGO since r10-6384-g2a07345c4f8dabc2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93564
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-671701-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:12:46 2020
Return-Path: <gcc-bugs-return-671701-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32131 invoked by alias); 27 Feb 2020 19:12: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 32079 invoked by uid 55); 27 Feb 2020 19:12:41 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93961] gnat.dg/lto24.adb FAILs
Date: Thu, 27 Feb 2020 19:12: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: ro at CeBiTec dot Uni-Bielefeld.DE
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-93961-4-8XH9lMPrKu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93961-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03283.txt.bz2
Content-length: 323
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93961
--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Please check that it is really compiled at -O1.
It is: no optimization option beside -O is used.
>From gcc-bugs-return-671702-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:20:54 2020
Return-Path: <gcc-bugs-return-671702-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39560 invoked by alias); 27 Feb 2020 19: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 39449 invoked by uid 48); 27 Feb 2020 19:20:44 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93435] [8/9/10 Regression] Hang with -O2 on innocuous looking code with GCC 8.3
Date: Thu, 27 Feb 2020 19: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: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: cc
Message-ID: <bug-93435-4-Tv1SJv08F5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93435-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93435-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03284.txt.bz2
Content-length: 926
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93435
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #5 from Jeffrey A. Law <law at redhat dot com> ---
Yea, we end up with ~260k stores in the key block.
The rate limiters in tree/gimple DSE are the number of queries we make per
store and the size of object for which we'll do byte tracking.
Clearly with hundreds of thousands of stores we may want another limiter --
obviously a user could write code that triggers this problem directly. I'll
figure out a reasonable limiter for DSE.
It also seems like SRA went a little bananas here and that's probably more
important to fix since it's taking fairly sensible code and exploding it beyone
sensibility.
>From gcc-bugs-return-671703-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:26:36 2020
Return-Path: <gcc-bugs-return-671703-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1456 invoked by alias); 27 Feb 2020 19:26: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 1384 invoked by uid 48); 27 Feb 2020 19:26:31 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93055] [10 Regression] accumulation loops in stepanov_vector benchmark use more instruction level parpallelism
Date: Thu, 27 Feb 2020 19:26: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: law at redhat dot com
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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-93055-4-cDzrvLQW1w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93055-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93055-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03285.txt.bz2
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93055
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |law at redhat dot com
>From gcc-bugs-return-671704-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:27:25 2020
Return-Path: <gcc-bugs-return-671704-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5449 invoked by alias); 27 Feb 2020 19:27: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 5357 invoked by uid 48); 27 Feb 2020 19:27:19 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93007] [10 regression] pr77698.c testcase fails due to block commoning
Date: Thu, 27 Feb 2020 19: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-93007-4-YyVp1SEv64@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03286.txt.bz2
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93007
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |law at redhat dot com
>From gcc-bugs-return-671705-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:37:56 2020
Return-Path: <gcc-bugs-return-671705-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32030 invoked by alias); 27 Feb 2020 19:37: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 31967 invoked by uid 48); 27 Feb 2020 19:37:52 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92658] x86 lacks vector extend / truncate
Date: Thu, 27 Feb 2020 19:37: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: ubizjak at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-92658-4-1EDRkDYtVQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03287.txt.bz2
Content-length: 891
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |ubizjak at gmail dot com
--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
Created attachment 47924
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47924&action=edit
Prototype patch
Prototype patch that introduces missing expanders to generate PMOVZX and PMOVSX
packed moves. For the testcase in Comment #0, we generate (-O3 -mavx):
bar:
vpmovzxbw (%rsi), %xmm0
vmovdqa %xmm0, (%rdi)
ret
foo:
vpmovzxbw %xmm0, %xmm0
vmovdqa %xmm0, (%rdi)
ret
>From gcc-bugs-return-671706-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:42:55 2020
Return-Path: <gcc-bugs-return-671706-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41263 invoked by alias); 27 Feb 2020 19:42: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 41200 invoked by uid 55); 27 Feb 2020 19:42:48 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93932] PowerPC vec_extract with variable element number has code regressions for V2DI/V2DF vectors
Date: Thu, 27 Feb 2020 19: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: meissner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93932-4-3tXRYqYGCl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93932-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93932-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03288.txt.bz2
Content-length: 1503
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93932
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Michael Meissner <meissner@gcc.gnu.org>:
https://gcc.gnu.org/g:75c299acc47b19fd6c445a6931798325a54e6fb4
commit r10-6908-g75c299acc47b19fd6c445a6931798325a54e6fb4
Author: Michael Meissner <meissner@gcc.gnu.org>
Date: Thu Feb 27 14:41:39 2020 -0500
Fix PR target/93932
[gcc]
2020-02-27 Michael Meissner <meissner@linux.ibm.com>
PR target/93932
* config/rs6000/vsx.md (vsx_extract_<mode>_var, VSX_D iterator):
Split the insn into two parts. This insn only does variable
extract from a register.
(vsx_extract_<mode>_var_load, VSX_D iterator): New insn, do
variable extract from memory.
(vsx_extract_v4sf_var): Split the insn into two parts. This insn
only does variable extract from a register.
(vsx_extract_v4sf_var_load): New insn, do variable extract from
memory.
(vsx_extract_<mode>_var, VSX_EXTRACT_I iterator): Split the insn
into two parts. This insn only does variable extract from a
register.
(vsx_extract_<mode>_var_load, VSX_EXTRACT_I iterator): New insn,
do variable extract from memory.
[gcc/testsuite]
2020-02-27 Michael Meissner <meissner@linux.ibm.com>
PR target/93932
* gcc.target/powerpc/fold-vec-extract-longlong.p8.c: Adjust
instruction counts.
>From gcc-bugs-return-671707-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:50:50 2020
Return-Path: <gcc-bugs-return-671707-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57365 invoked by alias); 27 Feb 2020 19:50: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 57327 invoked by uid 48); 27 Feb 2020 19:50:46 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93926] [10 Regression] ICE: verify_cgraph_node failed (error: malloc attribute should be used for a function that returns a pointer)
Date: Thu, 27 Feb 2020 19: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: ice-checking, ice-on-invalid-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: bug_status cc assigned_to
Message-ID: <bug-93926-4-FeQShWDdql@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03289.txt.bz2
Content-length: 1711
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93926
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |msebor at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
The bug here is in the mismatch between the permissive way the front-end
validates declarations of built-ins and the more restrictive validation done by
the middle-end.
The front-end silently accepts as valid redeclarations whose number of
arguments and their modes (as well as the mode of the return type) match the
built-in, even if types are different. So 'long malloc(int)' is treated as a
built-in.
But the middle-end validation looks like this:
if (DECL_IS_MALLOC (decl)
&& !POINTER_TYPE_P (TREE_TYPE (TREE_TYPE (decl))))
{
error ("malloc attribute should be used for a function that "
"returns a pointer");
error_found = true;
}
DECL_IS_MALLOC(decl) is set but the return type is wrong.
I think incompatible redeclarations should be diagnosed regardless of whether
their type modes match; they could still keep being accepted as built-ins
because it helps find bugs in their use. The middle-end checking would then
need to change to match the front-end. It seems that abstracting the checking
into a common function used by both would help keep the two from getting out of
sync. Let me look into making that happen.
>From gcc-bugs-return-671708-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:52:55 2020
Return-Path: <gcc-bugs-return-671708-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58719 invoked by alias); 27 Feb 2020 19:52: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 58673 invoked by uid 48); 27 Feb 2020 19:52:49 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93926] [10 Regression] ICE: verify_cgraph_node failed (error: malloc attribute should be used for a function that returns a pointer)
Date: Thu, 27 Feb 2020 19:52: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: ice-checking, ice-on-invalid-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-93926-4-lnrSC4iK5T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03290.txt.bz2
Content-length: 247
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93926
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
For reference, the ICE is the result of the fix for PR 93583. It's getting
hard not to fix an ICE without introducing another.
>From gcc-bugs-return-671709-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:55:59 2020
Return-Path: <gcc-bugs-return-671709-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60911 invoked by alias); 27 Feb 2020 19:55: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 60871 invoked by uid 48); 27 Feb 2020 19:55:54 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93919] [10 Regression] vectorization of 18 char to char16_t conversion is miscompiled
Date: Thu, 27 Feb 2020 19:55: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot 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-93919-4-MJDDMsIWpe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93919-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93919-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03291.txt.bz2
Content-length: 460
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93919
Matthias Kretz (Vir) <kretz at kde dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Matthias Kretz (Vir) <kretz at kde dot org> ---
this is fixed after PR93843 was fixed
>From gcc-bugs-return-671710-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:56:19 2020
Return-Path: <gcc-bugs-return-671710-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61805 invoked by alias); 27 Feb 2020 19:56: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 61706 invoked by uid 48); 27 Feb 2020 19:56:15 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93919] [10 Regression] vectorization of 18 char to char16_t conversion is miscompiled
Date: Thu, 27 Feb 2020 19:56: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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: resolution
Message-ID: <bug-93919-4-VDTyfaCzrH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93919-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93919-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03292.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93919
Matthias Kretz (Vir) <kretz at kde dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |DUPLICATE
--- Comment #6 from Matthias Kretz (Vir) <kretz at kde dot org> ---
*** This bug has been marked as a duplicate of bug 93843 ***
>From gcc-bugs-return-671711-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 19:56:19 2020
Return-Path: <gcc-bugs-return-671711-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61809 invoked by alias); 27 Feb 2020 19:56: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 61725 invoked by uid 48); 27 Feb 2020 19:56:15 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93843] [10 Regression] wrong code at -O3 on x86_64-linux-gnu
Date: Thu, 27 Feb 2020 19: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: kretz at kde dot 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:
Message-ID: <bug-93843-4-nWjyZdlMIs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03293.txt.bz2
Content-length: 185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93843
--- Comment #11 from Matthias Kretz (Vir) <kretz at kde dot org> ---
*** Bug 93919 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-671712-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 20:02:10 2020
Return-Path: <gcc-bugs-return-671712-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80842 invoked by alias); 27 Feb 2020 20: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 80777 invoked by uid 48); 27 Feb 2020 20:02:01 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93926] [10 Regression] ICE: verify_cgraph_node failed (error: malloc attribute should be used for a function that returns a pointer)
Date: Thu, 27 Feb 2020 20:02: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: ice-checking, ice-on-invalid-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-93926-4-hBBTKM2smp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03294.txt.bz2
Content-length: 610
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93926
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
I should have said without -Wextra the incompatible return type is silently
accepted. With -Wextra there is a warning:
$ gcc -S -Wall -Wextra -m32 pr93926.c
pr93926.c:1:10: warning: mismatch in return type of built-in function ‘malloc’;
expected ‘void *’ [-Wbuiltin-declaration-mismatch]
1 | long int malloc (int);
| ^~~~~~
pr93926.c:6:1: error: malloc attribute should be used for a function that
returns a pointer
6 | }
| ^
>From gcc-bugs-return-671713-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 20:07:56 2020
Return-Path: <gcc-bugs-return-671713-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106237 invoked by alias); 27 Feb 2020 20:07: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 106207 invoked by uid 48); 27 Feb 2020 20:07:46 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90993] simd integer division not optimized
Date: Thu, 27 Feb 2020 20: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot 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-90993-4-icucEhPP0p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90993-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90993-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03295.txt.bz2
Content-length: 1226
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90993
--- Comment #3 from Matthias Kretz (Vir) <kretz at kde dot org> ---
IIUC, AVX512 only allows overriding the rounding-mode from div instructions. So
that wouldn't help.
What standard requires that "integer division is not permitted to raise the
"inexact" exception flag"? C++ points to C which says:
"Certain programming conventions support the intended model of use for the
floating-point environment:
— a function call does not alter its caller’s floating-point control modes,
clear its caller’s floating-point status flags, nor depend on the state of its
caller’s floating-point status flags unless the function is so documented;
— a function call is assumed to require default floating-point control modes,
unless its documentation promises otherwise;
— a function call is assumed to have the potential for raising floating-point
exceptions, unless its documentation promises otherwise." [§7.6 p3]
Thus it's a valid implementation to use floating point division for a SIMD type
library, but not valid for auto-vectorization of integer division? (For
vector_size(N) types the spec is up to you, no?)
>From gcc-bugs-return-671714-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 20:11:35 2020
Return-Path: <gcc-bugs-return-671714-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129644 invoked by alias); 27 Feb 2020 20:11: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 129504 invoked by uid 48); 27 Feb 2020 20:11:27 -0000
From: "damian at sourceryinstitute dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/83118] [8/9/10 Regression] Bad intrinsic assignment of class(*) array component of derived type
Date: Thu, 27 Feb 2020 20:11: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: damian at sourceryinstitute dot org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83118-4-zKWszMXFcW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83118-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83118-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03296.txt.bz2
Content-length: 203
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83118
--- Comment #29 from Damian Rouson <damian at sourceryinstitute dot org> ---
Hi Paul,
The test case works with your patch applied. Thanks!
Damian
>From gcc-bugs-return-671715-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 20:15:59 2020
Return-Path: <gcc-bugs-return-671715-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8329 invoked by alias); 27 Feb 2020 20:15: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 8127 invoked by uid 48); 27 Feb 2020 20:15:52 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93923] [10 Regression] std::is_copy_constructible raises compilation error
Date: Thu, 27 Feb 2020 20:15: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: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93923-4-XmUoiGvGwc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03297.txt.bz2
Content-length: 201
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93923
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I'm unsure. What the standard allows here might not be very helpful for users.
>From gcc-bugs-return-671716-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 20:19:37 2020
Return-Path: <gcc-bugs-return-671716-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19250 invoked by alias); 27 Feb 2020 20:19: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 19159 invoked by uid 48); 27 Feb 2020 20:19:33 -0000
From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/93962] New: [10 regression] bootstrap fails with gcc/value-prof.c:268:28 : error: format '%lld' expects argument of type 'long long int', but argument 3 hastype 'int'
Date: Thu, 27 Feb 2020 20:19: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: gerald at pfeifer 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 cf_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-93962-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03298.txt.bz2
Content-length: 1873
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93962
Bug ID: 93962
Summary: [10 regression] bootstrap fails with
gcc/value-prof.c:268:28 : error: format '%lld' expects
argument of type 'long long int', but argument 3
hastype 'int'
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: gerald at pfeifer dot com
CC: hubicka at gcc dot gnu.org, mliska at suse dot cz
Target Milestone: ---
Host: i386-unknown-freebsd11.3
Target: i386-unknown-freebsd11.3
Build: i386-unknown-freebsd11.3
/scratch/tmp/gerald/gcc10-devel-work/gcc-10-20200223/gcc/value-prof.c: In
function 'void dump_histogram_value(FILE*, histogram_value)':
/scratch/tmp/gerald/gcc10-devel-work/gcc-10-20200223/gcc/value-prof.c:268:28
: error: format '%lld' expects argument of type 'long long int', but
argument 3 has type 'int' [-Werror=format=]
268 | fprintf (dump_file, " all: %" PRId64 "%s, values: ",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
269 | abs ((int64_t) hist->hvalue.counters[0]),
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
| int
I believe this may be caused by 2020-02-18 Martin Liska <mliska@suse.cz>
PR ipa/92924
* common.opt: Add -fprofile-reproducibility.
* doc/invoke.texi: Document it.
* value-prof.c (dump_histogram_value):
Document and support behavior for counters[0]
being a negative value.
(get_nth_most_common_value): Handle negative
counters[0] in respect to flag_profile_reproducible.
>From gcc-bugs-return-671717-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 20:23:28 2020
Return-Path: <gcc-bugs-return-671717-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42127 invoked by alias); 27 Feb 2020 20:23: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 42087 invoked by uid 48); 27 Feb 2020 20:23:20 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92955] [10 regression] gcc.dg/vect/pr60505.c fails starting with r279392
Date: Thu, 27 Feb 2020 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: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: cc
Message-ID: <bug-92955-4-VLQ1FKrlMi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92955-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92955-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03299.txt.bz2
Content-length: 707
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92955
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #7 from Jeffrey A. Law <law at redhat dot com> ---
I think c#5 is over-reduced and a warning is warranted in both functions in
c#5. In those cases the loop iterates until it encounters a NUL in *p and can
trivially leave the bounds of the object.
The testcase in c#4 is far more interesting as we should be able to put limits
on the loop bounds because of the test before the loop.
>From gcc-bugs-return-671718-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 20:33:22 2020
Return-Path: <gcc-bugs-return-671718-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54831 invoked by alias); 27 Feb 2020 20: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 54767 invoked by uid 48); 27 Feb 2020 20:33:17 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/93962] [10 regression] bootstrap fails with gcc/value-prof.c:268:28 : error: format '%lld' expects argument of type 'long long int', but argument 3 hastype 'int'
Date: Thu, 27 Feb 2020 20:33: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-93962-4-P3VuhXmEpZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93962-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93962-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03300.txt.bz2
Content-length: 737
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93962
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-27
Ever confirmed|0 |1
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Wait I think this should have been std::abs rather than just abs :).
Can you try that and see if that fixes the issue?
on glibc targets abs is in the toplevel namespace for all types (I think) but
on FreeBSD only the overload for int is in the toplevel namespace.
>From gcc-bugs-return-671719-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 21:14:52 2020
Return-Path: <gcc-bugs-return-671719-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119083 invoked by alias); 27 Feb 2020 21: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 118965 invoked by uid 48); 27 Feb 2020 21:14:48 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/93962] [10 regression] bootstrap fails with gcc/value-prof.c:268:28 : error: format '%lld' expects argument of type 'long long int', but argument 3 hastype 'int'
Date: Thu, 27 Feb 2020 21: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-93962-4-igohujWcxJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93962-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93962-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03301.txt.bz2
Content-length: 242
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93962
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
See https://sourceware.org/ml/gdb-patches/2020-02/msg01014.html also for the
same reasoning but with gdb instead of GCC.
>From gcc-bugs-return-671720-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 21:16:44 2020
Return-Path: <gcc-bugs-return-671720-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120740 invoked by alias); 27 Feb 2020 21:16: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 120661 invoked by uid 48); 27 Feb 2020 21:16:40 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92342] [10 Regression] a small missed transformation into x?b:0
Date: Thu, 27 Feb 2020 21:16: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-92342-4-05xlBuQ8DV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03302.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92342
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |law at redhat dot com
--- Comment #11 from Jeffrey A. Law <law at redhat dot com> ---
Couldn't we just fix this kind of stuff in gimple?
>From gcc-bugs-return-671721-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 21:18:02 2020
Return-Path: <gcc-bugs-return-671721-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122389 invoked by alias); 27 Feb 2020 21:18: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 122286 invoked by uid 55); 27 Feb 2020 21:17:58 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93926] [10 Regression] ICE: verify_cgraph_node failed (error: malloc attribute should be used for a function that returns a pointer)
Date: Thu, 27 Feb 2020 21: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: ice-checking, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery 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:
Message-ID: <bug-93926-4-49XItQtZ7K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03303.txt.bz2
Content-length: 820
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93926
--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Some level of permissiveness for built-in functions may be historical,
arising from support for pre-C90 headers without prototypes or with
nonstandard types; that level of permissiveness is probably no longer
needed, headers should use the standard types now (modulo e.g. missing
restrict, but qualifiers on the type of an argument, as opposed to
qualifiers on the type pointed to by a pointer argument, don't affect type
compatibility for the function type). However, a certain amount of
permissiveness is still needed for cases where the built-in function uses
a typedef such as FILE for which the compiler does not know the underlying
type.
>From gcc-bugs-return-671722-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 22:19:07 2020
Return-Path: <gcc-bugs-return-671722-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96948 invoked by alias); 27 Feb 2020 22:19: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 96857 invoked by uid 48); 27 Feb 2020 22:19:03 -0000
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92656] The zero_extend insn can't be eliminated in the combine pass
Date: Thu, 27 Feb 2020 22: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: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: wilson 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-92656-4-cDxVCSVukA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92656-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92656-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03304.txt.bz2
Content-length: 2481
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92656
--- Comment #3 from Jim Wilson <wilson at gcc dot gnu.org> ---
Looking at this, I see that the problem occurs in record_value_for_reg where it
does
if (!insn
|| (value && rsp->last_set_table_tick >= label_tick_ebb_start))
rsp->last_set_invalid = 1;
last_set_table_tick is 2 and label_tick_ebb_start is 1 because this is the
first block of the function. This actually causes a lot of variables set in
the first block to be marked invalid if used in a successful combination two or
more times, which then prevents the nonzero bits info from being used for any
of them.
There seems to be a problem with how label_tick is used. In the very first
block in the body of the function, label_tick is 2 and label_tick_ebb_start is
1. This is because it is considered to be the second block in the ebb after
the entry block. In the second block in the body of the function, label_tick
is 3 and label_tick_ebb_start is 3. This means that every variable set in the
first block gets treated differently than in every block after the first.
If I add a little bit of code before the loop to force it to be the second
block, then I get correct output from combine. I just added this before the
loop
static int j = 0;
if (val)
j++;
This also explains why the problem only occurs with -mtune=sifive-7-series
because this enables the conditional move support that turns the loop into a
single block, and then the -funroll-loops option fully unrolls the loop,
turning the entire function into one block, which prevents combine from
handling many of the register sets correctly because everything is in the first
block now.
This also explains why the problem started when the 2->2 combination support
was added, as that causes more successful combinations, and hence more
registers getting invalidated in the first block.
So the question is why we need label_tick > label_tick_ebb_start for the first
block of the function. There is nothing set in the entry block other than hard
registers, and those could always be handled specially by just marking them as
invalid somehow before processing instructions.
Or alternatively, in record_value_for_reg, maybe we can add a check for a
pseudo reg only set once and not live in the prologue, and avoid marking it as
invalid when we process it a second time. There are already a lot of checks
like this scattered around the code.
>From gcc-bugs-return-671723-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 22:46:24 2020
Return-Path: <gcc-bugs-return-671723-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61444 invoked by alias); 27 Feb 2020 22:46: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 61410 invoked by uid 48); 27 Feb 2020 22:46:15 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93926] [10 Regression] ICE: verify_cgraph_node failed (error: malloc attribute should be used for a function that returns a pointer)
Date: Thu, 27 Feb 2020 22:46: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: ice-checking, ice-on-invalid-code, patch
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: keywords
Message-ID: <bug-93926-4-JfhQBoAPtB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03305.txt.bz2
Content-length: 716
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93926
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2020-02/msg01586.html
I think it should still handle gracefully the benign mismatches you
highlighted, Joseph. The gcc.dg/Wbuiltin-declaration-mismatch-[67].c pair of
tests make sure the stdio functions' signatures match whatever type is declared
in the headers so hopefully they adequately cover those cases.
>From gcc-bugs-return-671724-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 22:47:40 2020
Return-Path: <gcc-bugs-return-671724-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93258 invoked by alias); 27 Feb 2020 22: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 93214 invoked by uid 48); 27 Feb 2020 22:47:36 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92955] [10 regression] gcc.dg/vect/pr60505.c fails starting with r279392
Date: Thu, 27 Feb 2020 22: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: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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-92955-4-0ma4EcyHxf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92955-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92955-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03306.txt.bz2
Content-length: 3272
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92955
--- Comment #8 from Jeffrey A. Law <law at redhat dot com> ---
Just to be clear, it's not DOM or threading that introduces any out of bounds
accesses or overflows here.
So the testcase:
/* { dg-do compile } */
/* { dg-additional-options "-Wall -Werror" } */
void foo(char *in, char *out, int num)
{
int i;
char ovec[16] = {0};
for(i = 0; i < num ; ++i)
out[i] = (ovec[i] = in[i]);
out[num] = ovec[num/2];
}
Compiled for powerpc64-linux-gnu with:
./cc1 -O3 j.c -I./ -Wall -maltivec -fdump-tree-all-blocks-details
-fno-vect-cost-model
The first warning comes from this statement in block #5:
ovec[tmp.8_58] = _207;
The block looks like this in the .thread3 (ie, before dom3) dump:
;; basic block 5, loop depth 0, count 78839494 (estimated locally), maybe hot
;; prev block 4, next block 6, flags: (NEW, REACHABLE, VISITED)
;; pred: 4 [93.8% (guessed)] count:78839494 (estimated locally)
(FALSE_VALUE,EXECUTABLE)
_205 = (sizetype) tmp.8_58;
[ ... ]
ovec[tmp.8_58] = _207;
[ ... ]
THe definition of tmp.8_58 comes from bb#4:
;; basic block 4, loop depth 0, count 84095460 (estimated locally), maybe hot
;; prev block 3, next block 5, flags: (NEW, REACHABLE, VISITED)
;; pred: 3 [80.0% (guessed)] count:84095460 (estimated locally)
(TRUE_VALUE,EXECUTABLE)
bnd.6_56 = _10 >> 4;
[ ... ]
niters_vector_mult_vf.7_57 = bnd.6_56 << 4;
tmp.8_58 = (int) niters_vector_mult_vf.7_57;
if (_10 == niters_vector_mult_vf.7_57)
goto <bb 36>; [6.25%]
else
goto <bb 5>; [93.75%]
The definition of _10 comes from bb3:
;; basic block 3, loop depth 0, count 105119324 (estimated locally), maybe
hot
;; prev block 2, next block 4, flags: (NEW, VISITED)
;; pred: 2 [89.0% (guessed)] count:105119324 (estimated locally)
(TRUE_VALUE,EXECUTABLE)
_10 = (unsigned int) num_13(D);
[ ... ]
So let's compute tmp.8_58 :-) assuming that num_13 is an incoming parameter and
we have no information about it other than its type (int).
Visiting statement:
_10 = (unsigned int) num_13(D);
Intersecting
unsigned int [1, 2147483647]
and
unsigned int VARYING
Which feeds into:
Visiting statement:
bnd.6_56 = _10 >> 4;
Intersecting
unsigned int [1, 134217727]
and
unsigned int [1, 268435455]
to
unsigned int [1, 134217727]
So bnd.6_56 can have the value [1, 0x7ffffff] Which makes perfect sense. That
feeds into:
Visiting statement:
niters_vector_mult_vf.7_57 = bnd.6_56 << 4;
Intersecting
unsigned int [16, 2147483632]
and
unsigned int VARYING
to
unsigned int [16, 2147483632]
So ninters_vector_mult_vf.7_57 can have the values [16, 0x7ffffff0]. Which
also makes perfect sense and feeds into:
Visiting statement:
tmp.8_58 = (int) niters_vector_mult_vf.7_57;
Intersecting
int [16, 2147483632]
and
int VARYING
to
int [16, 2147483632]
So tmp.8_58 also has values in the range [16, 0x7ffffff0]
So when used in this statement:
ovec[tmp.8_58] = _207;
We get the out of bounds access. Pretty simple.
THis is caused either by vectorization or loop unrolling or the combination
thereof (most likely loop unrolling). DOM/threading have nothing to do with
what's going on in here.
>From gcc-bugs-return-671725-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 23:05:51 2020
Return-Path: <gcc-bugs-return-671725-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41594 invoked by alias); 27 Feb 2020 23: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 41370 invoked by uid 48); 27 Feb 2020 23:05:46 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92342] [10 Regression] a small missed transformation into x?b:0
Date: Thu, 27 Feb 2020 23: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92342-4-oXtM5SwHMM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03307.txt.bz2
Content-length: 300
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92342
--- Comment #12 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Gimple can help writing silly expressions like this in a more canonical
form (whatever we decide to use for that) at least, yeah. But you can
not do RTL's job in gimple ;-)
>From gcc-bugs-return-671726-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 23:19:50 2020
Return-Path: <gcc-bugs-return-671726-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73116 invoked by alias); 27 Feb 2020 23:19: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 72997 invoked by uid 48); 27 Feb 2020 23:19:46 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92656] The zero_extend insn can't be eliminated in the combine pass
Date: Thu, 27 Feb 2020 23: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: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: segher 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-92656-4-JKFeYA3l19@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92656-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92656-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03308.txt.bz2
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92656
--- Comment #4 from Segher Boessenkool <segher at gcc dot gnu.org> ---
The whole reg_stat thing cannot ever reliably track known bits. We need
some other mechanism to do this, something that *is* reliable, and does
not give different results if you try combinations in a different order.
Something quite like dataflow. This then could also be used in other
passes, of course.
>From gcc-bugs-return-671727-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 23:28:09 2020
Return-Path: <gcc-bugs-return-671727-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80986 invoked by alias); 27 Feb 2020 23: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 80939 invoked by uid 48); 27 Feb 2020 23:28:05 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93745] Redundant store not eliminated with intermediate instruction
Date: Thu, 27 Feb 2020 23: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: 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93745-4-AzovqW74bA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03309.txt.bz2
Content-length: 859
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93745
--- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> ---
Regarding the DECL_FIXED_DYNAMIC_TYPE flag: it seems like in C every DECL would
have it set, but in C++ none could (because placement new can change the
dynamic type of decls), and so GCC would not be able to optimize the example in
that language even though there the read via *p means that p cannot alias d.
If what's keeping GCC from optimizing the code is the fact that the middle-end
doesn't distinguish placement new from plain assignment, i.e., that it can't
tell that the original source didn't look like this:
double d;
void f (long *p)
{
long i = *p;
new (&d) double (3);
*p = i;
}
wouldn't the solution be to keep placement new around in some form and teach
the middle-end how to work with it?
>From gcc-bugs-return-671728-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 23:32:47 2020
Return-Path: <gcc-bugs-return-671728-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25754 invoked by alias); 27 Feb 2020 23:32: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 25693 invoked by uid 48); 27 Feb 2020 23:32:43 -0000
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92656] The zero_extend insn can't be eliminated in the combine pass
Date: Thu, 27 Feb 2020 23:32: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: enhancement
X-Bugzilla-Who: wilson 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-92656-4-U8r48frb22@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92656-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92656-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03310.txt.bz2
Content-length: 420
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92656
--- Comment #5 from Jim Wilson <wilson at gcc dot gnu.org> ---
A rewrite using dataflow would be better of course. I'm just trying to
understand the problem with this testcase better, and maybe find a simple
solution, but I don't think that there is one. The workarounds I see just make
the code more complicated and add more risk of something else going wrong.
>From gcc-bugs-return-671729-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 23:36:30 2020
Return-Path: <gcc-bugs-return-671729-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22309 invoked by alias); 27 Feb 2020 23:36: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 22223 invoked by uid 48); 27 Feb 2020 23:36:26 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92342] [10 Regression] a small missed transformation into x?b:0
Date: Thu, 27 Feb 2020 23: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92342-4-xAGkMbQADE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03311.txt.bz2
Content-length: 331
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92342
--- Comment #13 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note I don't remember where I found this originally. I found this code
somewhere back in May 2012 but I did not record where I found it though; It was
the opposite way around really for Octeon2/3 (MIPS64).
>From gcc-bugs-return-671730-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 23:51:06 2020
Return-Path: <gcc-bugs-return-671730-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59318 invoked by alias); 27 Feb 2020 23:51: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 59264 invoked by uid 48); 27 Feb 2020 23:50:58 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92539] [8/9/10 Regression] -Warray-bounds false positive (loop unroll?)
Date: Thu, 27 Feb 2020 23: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
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-92539-4-wIUs2IM3TQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92539-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92539-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03312.txt.bz2
Content-length: 2243
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92539
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #2 from Jeffrey A. Law <law at redhat dot com> ---
Am I reading the .einline dump wrong? It looks to me like early inlining
totally mucked up the saving of the "first" in eat_two when everything gets
inlined into main. The net result is we advance further through the input
array than we're supposed to.
;; basic block 5, loop depth 1, maybe hot
;; prev block 4, next block 6, flags: (NEW, REACHABLE, VISITED)
;; pred: 3 [11.0% (guessed)] (TRUE_VALUE,EXECUTABLE)
;; 8 [always] (FALLTHRU,DFS_BACK,EXECUTABLE)
# i_7 = PHI <0(3), i_12(8)>
# local_iterator_8 = PHI <"aa"(3), _11(8)>
if (i_7 == 3)
goto <bb 9>; [25.00%]
else
goto <bb 6>; [75.00%]
;; succ: 9 [25.0% (guessed)] (TRUE_VALUE,EXECUTABLE)
;; 6 [75.0% (guessed)] (FALSE_VALUE,EXECUTABLE)
;; basic block 6, loop depth 1, maybe hot
;; prev block 5, next block 7, flags: (NEW, REACHABLE, VISITED)
;; pred: 5 [75.0% (guessed)] (FALSE_VALUE,EXECUTABLE)
if (last_3 != local_iterator_8)
goto <bb 7>; [54.59%]
else
goto <bb 9>; [45.41%]
;; succ: 7 [54.6% (guessed)] (TRUE_VALUE,EXECUTABLE)
;; 9 [45.4% (guessed)] (FALSE_VALUE,EXECUTABLE)
;; basic block 7, loop depth 1, maybe hot
;; prev block 6, next block 8, flags: (NEW, REACHABLE, VISITED)
;; pred: 6 [54.6% (guessed)] (TRUE_VALUE,EXECUTABLE)
_10 = local_iterator_8 + 1;
if (last_3 != _10)
goto <bb 8>; [54.59%]
else
goto <bb 9>; [45.41%]
;; succ: 8 [54.6% (guessed)] (TRUE_VALUE,EXECUTABLE)
;; 9 [45.4% (guessed)] (FALSE_VALUE,EXECUTABLE)
;; basic block 8, loop depth 1, maybe hot
;; prev block 7, next block 9, flags: (NEW, REACHABLE, VISITED)
;; pred: 7 [54.6% (guessed)] (TRUE_VALUE,EXECUTABLE)
_11 = &MEM <const char> [(void *)local_iterator_8 + 2B];
i_12 = i_7 + 1;
goto <bb 5>; [100.00%]
>From gcc-bugs-return-671731-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Feb 27 23:53:50 2020
Return-Path: <gcc-bugs-return-671731-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63318 invoked by alias); 27 Feb 2020 23:53: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 63221 invoked by uid 48); 27 Feb 2020 23:53:41 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92342] [10 Regression] a small missed transformation into x?b:0
Date: Thu, 27 Feb 2020 23:53: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92342-4-cDWfIv4Tf5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03313.txt.bz2
Content-length: 347
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92342
--- Comment #14 from Jeffrey A. Law <law at redhat dot com> ---
That wouldn't be a big surprise Andrew.
My point is I think we could create some match.pd patterns to canonicalize the
form in gimple and it wouldn't matter nearly as much what combine did or didn't
do to this kind of code.
>From gcc-bugs-return-671732-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 00:08:10 2020
Return-Path: <gcc-bugs-return-671732-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19314 invoked by alias); 28 Feb 2020 00: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 19260 invoked by uid 48); 28 Feb 2020 00:08:06 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93923] [10 Regression] std::is_copy_constructible raises compilation error
Date: Fri, 28 Feb 2020 00:08: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: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93923-4-h0vhVpmAMt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03314.txt.bz2
Content-length: 780
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93923
--- Comment #6 from Jeffrey A. Law <law at redhat dot com> ---
ISTM that if the standard disallows, then we should as well. We could always
raise a DR if we think the standard ought to be updated to be more user
friendly in what it accepts.
I think I ran into maybe a half-dozen of these kind of things across all of
Fedora this cycle -- I was never able to analyze them all. I think you decided
one was a real bug (the fairly recent fix for ceph).
Anyway, you and Jason are the experts here and I'll support whatever decision
you make. I'm just trying to knock things off the TODO list for gcc-10, so
when you indicate the code isn't standards conforming, I'm going to jump on the
"CLOSED/INVALID" path quickly.
>From gcc-bugs-return-671733-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 00:10:48 2020
Return-Path: <gcc-bugs-return-671733-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23137 invoked by alias); 28 Feb 2020 00:10: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 23082 invoked by uid 48); 28 Feb 2020 00:10:43 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92906] [10 regression] FAIL: libstdc++-abi/abi_check
Date: Fri, 28 Feb 2020 00:10: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: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: cc
Message-ID: <bug-92906-4-vQVpn7vo1j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92906-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03315.txt.bz2
Content-length: 468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92906
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> ---
Jakub, I think your fix resolved this BZ. Correct? If so can you go ahead and
close this out?
>From gcc-bugs-return-671734-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 00:14:23 2020
Return-Path: <gcc-bugs-return-671734-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33881 invoked by alias); 28 Feb 2020 00:14: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 33821 invoked by uid 48); 28 Feb 2020 00:14:10 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91804] [10 regression] r265398 breaks gcc.target/powerpc/vec-rlmi-rlnm.c
Date: Fri, 28 Feb 2020 00: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: law at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-91804-4-IE3Q84oc0B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91804-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91804-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03316.txt.bz2
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91804
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P1 |P2
CC| |law at redhat dot com
>From gcc-bugs-return-671735-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 00:33:12 2020
Return-Path: <gcc-bugs-return-671735-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53223 invoked by alias); 28 Feb 2020 00:33: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 53132 invoked by uid 48); 28 Feb 2020 00:33:08 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93674] [8/9/10 Regression] GCC eliminates conditions it should not, when strict-enums is on
Date: Fri, 28 Feb 2020 00: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: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93674-4-qEd8SoGSwB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93674-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93674-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03317.txt.bz2
Content-length: 296
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93674
--- Comment #12 from Jeffrey A. Law <law at redhat dot com> ---
Definitely an IVOPTS problem of some kind. It shouldn't be using some_enum
types for the induction variables. It's probably a one-line fix for whomever
knows the code. Bin?
>From gcc-bugs-return-671736-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 02:01:28 2020
Return-Path: <gcc-bugs-return-671736-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4672 invoked by alias); 28 Feb 2020 02: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 3542 invoked by uid 48); 28 Feb 2020 02:01:19 -0000
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93674] [8/9/10 Regression] GCC eliminates conditions it should not, when strict-enums is on
Date: Fri, 28 Feb 2020 02: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: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amker at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: amker at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-93674-4-An9wJTxi2G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93674-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93674-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03318.txt.bz2
Content-length: 403
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93674
bin cheng <amker at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |amker at gcc dot gnu.org
--- Comment #13 from bin cheng <amker at gcc dot gnu.org> ---
Sorry for missing this.
>From gcc-bugs-return-671737-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 04:40:35 2020
Return-Path: <gcc-bugs-return-671737-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37121 invoked by alias); 28 Feb 2020 04:40: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 37072 invoked by uid 48); 28 Feb 2020 04:40:29 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90280] [9/10 Regression] ICE: in lra_assign, at lra-assigns.c:1650 with -O -fno-dce -fno-forward-propagate -fno-omit-frame-pointer
Date: Fri, 28 Feb 2020 04:40: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: law at redhat dot com
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: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-90280-4-EUSifePuSO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90280-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90280-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03319.txt.bz2
Content-length: 1127
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90280
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |law at redhat dot com
Resolution|--- |WORKSFORME
--- Comment #3 from Jeffrey A. Law <law at redhat dot com> ---
So I tried a variety of revisions from April 29, 2019, but was unable to
reproduce this problem. I also tried a subset of those revisions under
valgrind just in case there was an uninitialized read, memory corruption or the
like. Other than the well known issues with sparsesets, nothing triggered.
There are other ICEs from this gcc_unreachable that have been fixed, but from
my research a variety of issues in allocation/reloading can be caught by this
gcc_unreachable.
I'm going to close this as WORKSFORME.
Obviously if you can still reproduce, please reopen and we'll dig deeper.
As always, thanks for your reports.
Jeff
>From gcc-bugs-return-671738-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 05:04:46 2020
Return-Path: <gcc-bugs-return-671738-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10661 invoked by alias); 28 Feb 2020 05:04: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 10571 invoked by uid 48); 28 Feb 2020 05:04:41 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/92417] [10 Regression] gcc generates wrong debug information at -O2
Date: Fri, 28 Feb 2020 05:04: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: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92417-4-hBGthDwmNv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92417-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92417-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03320.txt.bz2
Content-length: 407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92417
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #3 from Jeffrey A. Law <law at redhat dot com> ---
Sounds like a WONTFIX to me. Jakub?
>From gcc-bugs-return-671740-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 08:43:53 2020
Return-Path: <gcc-bugs-return-671740-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71250 invoked by alias); 28 Feb 2020 08:43: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 65135 invoked by uid 48); 28 Feb 2020 08:43:47 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/89661] FAIL: gfortran.dg/class_61.f90 -O (internal compiler error)
Date: Fri, 28 Feb 2020 08:43: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: clyon 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-89661-4-lgE5HgvpSG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89661-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89661-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03322.txt.bz2
Content-length: 467
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89661
Christophe Lyon <clyon at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |clyon at gcc dot gnu.org
--- Comment #3 from Christophe Lyon <clyon at gcc dot gnu.org> ---
I've recently started to see this randomly with my cross-compilers for arm
(host x86)
>From gcc-bugs-return-671739-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 08:43:32 2020
Return-Path: <gcc-bugs-return-671739-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53675 invoked by alias); 28 Feb 2020 08:43: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 53630 invoked by uid 48); 28 Feb 2020 08:43:27 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92658] x86 lacks vector extend / truncate
Date: Fri, 28 Feb 2020 08: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92658-4-DekOiFCwcq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03321.txt.bz2
Content-length: 707
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
--- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
Richi, should the following test also vectorize?
--cut here--
typedef unsigned char v16qi __attribute__((vector_size (16)));
typedef unsigned int v4si __attribute__((vector_size (16)));
void
foo_u8_u32 (v4si * dst, v16qi * __restrict src)
{
unsigned int tem[4];
tem[0] = (*src)[0];
tem[1] = (*src)[1];
tem[2] = (*src)[2];
tem[3] = (*src)[3];
dst[0] = *(v4si *) tem;
}
void
bar_u8_u32 (v4si * dst, v16qi src)
{
unsigned int tem[4];
tem[0] = src[0];
tem[1] = src[1];
tem[2] = src[2];
tem[3] = src[3];
dst[0] = *(v4si *) tem;
}
--cut here--
>From gcc-bugs-return-671741-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 08:46:10 2020
Return-Path: <gcc-bugs-return-671741-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113015 invoked by alias); 28 Feb 2020 08: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 112963 invoked by uid 55); 28 Feb 2020 08:46:03 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92152] [10 Regression] Wrong code (Resurrection of PR53663)
Date: Fri, 28 Feb 2020 08: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: cvs-commit 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-92152-4-rermIQpAaW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92152-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92152-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03323.txt.bz2
Content-length: 737
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92152
--- Comment #19 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:5c3489a083b3d1f7085752045b99e429950c3906
commit r10-6913-g5c3489a083b3d1f7085752045b99e429950c3906
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Feb 28 09:44:53 2020 +0100
testsuite: Fix up g++.dg/torture/pr92152.C test for ilp32 targets
2020-02-28 Jakub Jelinek <jakub@redhat.com>
PR middle-end/92152
* g++.dg/torture/pr92152.C (size_t): Use decltype (sizeof (0)) instead
of hardcoding unsigned long.
(uint64_t): Use unsigned long long instead of unsigned long.
>From gcc-bugs-return-671742-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 09:00:46 2020
Return-Path: <gcc-bugs-return-671742-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2214 invoked by alias); 28 Feb 2020 09:00: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 2105 invoked by uid 48); 28 Feb 2020 09:00:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/92417] [10 Regression] gcc generates wrong debug information at -O2
Date: Fri, 28 Feb 2020 09:00: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: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92417-4-DpULgXoOt6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92417-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92417-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03324.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92417
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'm afraid yes, at least in the not too distant future.
>From gcc-bugs-return-671744-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 09:06:03 2020
Return-Path: <gcc-bugs-return-671744-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5487 invoked by alias); 28 Feb 2020 09:06: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 5408 invoked by uid 48); 28 Feb 2020 09:06:00 -0000
From: "jakub 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: Fri, 28 Feb 2020 09:06: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: 10.0
X-Bugzilla-Keywords: accepts-invalid
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-91985-4-fo5Q0TAhNS@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: 2020-02/txt/msg03326.txt.bz2
Content-length: 471
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91985
Bug 91985 depends on bug 92906, which changed state.
Bug 92906 Summary: [10 regression] FAIL: libstdc++-abi/abi_check
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92906
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-671743-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 09:06:03 2020
Return-Path: <gcc-bugs-return-671743-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5474 invoked by alias); 28 Feb 2020 09:06: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 5362 invoked by uid 48); 28 Feb 2020 09:05:59 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92906] [10 regression] FAIL: libstdc++-abi/abi_check
Date: Fri, 28 Feb 2020 09:06: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: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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: priority bug_status cc resolution assigned_to
Message-ID: <bug-92906-4-dTg7qTxny2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92906-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03325.txt.bz2
Content-length: 759
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92906
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|NEW |RESOLVED
CC| |danglin at gcc dot gnu.org
Resolution|--- |FIXED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yes, I think John needs to revert his
r10-5705-ga8497ec6102474365d4a7e92ccd5f392d8e96161 commit but otherwise we
should be all set.
>From gcc-bugs-return-671745-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 09:19:46 2020
Return-Path: <gcc-bugs-return-671745-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52510 invoked by alias); 28 Feb 2020 09:19: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 52412 invoked by uid 48); 28 Feb 2020 09:19:41 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92342] [10 Regression] a small missed transformation into x?b:0
Date: Fri, 28 Feb 2020 09: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: 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: P2
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-92342-4-UkmOEZLDZB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03327.txt.bz2
Content-length: 840
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92342
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
For this, I agree we should canonicalize the second form to the first one
(well, any commutative x & -boolean_range into boolean_range ? x : 0 because at
least in 95% of cases it will be written the former way, the latter form looks
like a cute trick trying to workaround compiler deficiencies.
If the x & -boolean_range form results in better code than boolean_range ? x :
0 on some target, we should make sure to expand the ?: that way somewhere in
RTL.
>From gcc-bugs-return-671746-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 09:30:32 2020
Return-Path: <gcc-bugs-return-671746-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62833 invoked by alias); 28 Feb 2020 09:30: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 62764 invoked by uid 48); 28 Feb 2020 09:30:25 -0000
From: "thenlich at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Fri, 28 Feb 2020 09: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: thenlich at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93871-4-IWWQ9fKPTM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03328.txt.bz2
Content-length: 688
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #33 from Thomas Henlich <thenlich at gcc dot gnu.org> ---
Going back one step, I wonder if it would be good enough to perform a correctly
rounded conversion from degrees to radians, and just use sin() as is.
...
f = sgn * sin(deg2rad(arg))
end function fcn
! Compute correctly rounded value of x * pi / 180 for x = 0 ... 90
function deg2rad(x) result(y)
real(sp) y
real(sp), intent(in) :: x
real(sp), parameter :: a = atan(1._4) / 45
real(sp), parameter :: b = atan(1._16) / 45 - a
y = a * x + b * x
end function deg2rad
(The exact values of a and b still need some work)
>From gcc-bugs-return-671747-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 09:42:55 2020
Return-Path: <gcc-bugs-return-671747-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79939 invoked by alias); 28 Feb 2020 09:42: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 79884 invoked by uid 48); 28 Feb 2020 09:42:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92342] [10 Regression] a small missed transformation into x?b:0
Date: Fri, 28 Feb 2020 09: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: 10.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: P2
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-92342-4-RUzhLjSVSa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03329.txt.bz2
Content-length: 913
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92342
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Seems on x86_64-linux we also used to give the same code in 3.4.6 and earlier,
but starting already with 4.0 (already r90000) we emit
cmpl %edx, %edi
movl $0, %eax
cmove %esi, %eax
for f and
xorl %eax, %eax
cmpl %edx, %edi
sete %al
negl %eax
andl %esi, %eax
for g. We do it even for -Os, where the f version is clearly a win, for -O2
I'm afraid it depends on how soon the cmove result is used. LLVM seems to use
cmove in both cases, ICC does roughly what gcc does (honor what user wrote).
Not sure if we can do this transformation in match.pd though, because for a ? b
: 0; the gimplifier doesn't emit a COND_EXPR, but GIMPLE_COND and PHI, I'm
afraid we can't create new bbs from within match.pd.
>From gcc-bugs-return-671748-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 09:43:51 2020
Return-Path: <gcc-bugs-return-671748-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80866 invoked by alias); 28 Feb 2020 09:43: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 80825 invoked by uid 48); 28 Feb 2020 09:43:47 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93961] gnat.dg/lto24.adb FAILs
Date: Fri, 28 Feb 2020 09: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: 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 assigned_to
Message-ID: <bug-93961-4-hHoS3lcXBc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93961-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03330.txt.bz2
Content-length: 471
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93961
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |ebotcazou at gcc dot gnu.org
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Investigating.
>From gcc-bugs-return-671749-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 10:07:12 2020
Return-Path: <gcc-bugs-return-671749-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52643 invoked by alias); 28 Feb 2020 10:07: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 52588 invoked by uid 48); 28 Feb 2020 10:07:07 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92342] [10 Regression] a small missed transformation into x?b:0
Date: Fri, 28 Feb 2020 10:07: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: 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: P2
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-92342-4-Fu3MsGHxkg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92342-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03331.txt.bz2
Content-length: 877
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92342
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Tried timing:
__attribute__((noipa)) int f(int a,int b, int c)
{
return a==c?b:0;
}
__attribute__((noipa)) int g(int a, int b, int c)
{
return b & -(a==c);
}
int
main (int argc, const char **argv)
{
unsigned int c = 0;
if (argv[1][0] == 'f')
{
for (int i = 0; i < 1000000000; i++)
c += f(1,1,i&1);
}
else
{
for (int i = 0; i < 1000000000; i++)
c += g(1,1,i&1);
}
asm volatile ("" : : "r" (c));
return 0;
}
and the same without the "i&", i.e. alternating results and always same, and
both functions are the same speed in both cases, and cmov is shorter.
Without cmov, such as with -m32 -O2 -march=i586, g seems to be faster, so we
probably should teach ifcvt.c to try it.
>From gcc-bugs-return-671750-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 10:27:09 2020
Return-Path: <gcc-bugs-return-671750-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3041 invoked by alias); 28 Feb 2020 10:27: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 3005 invoked by uid 48); 28 Feb 2020 10:27:05 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93707] ICE in perlbench from SPEC2017
Date: Fri, 28 Feb 2020 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: ice-on-valid-code
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: fxue at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93707-4-nTpW6amTYs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93707-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93707-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03332.txt.bz2
Content-length: 427
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93707
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671751-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 10:28:24 2020
Return-Path: <gcc-bugs-return-671751-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6811 invoked by alias); 28 Feb 2020 10:28: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 6755 invoked by uid 48); 28 Feb 2020 10:28:20 -0000
From: "jrfsousa at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93963] New: Select rank mishandling allocatable and pointer arguments with bind(c)
Date: Fri, 28 Feb 2020 10: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jrfsousa 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-93963-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03333.txt.bz2
Content-length: 770
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93963
Bug ID: 93963
Summary: Select rank mishandling allocatable and pointer
arguments with bind(c)
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jrfsousa at gmail dot com
Target Milestone: ---
Created attachment 47925
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47925&action=edit
Code demonstrating problems.
Hi all
Select rank mishandles allocatable and pointer arguments when using bind(c)
with:
GNU Fortran (GCC) 10.0.1 20200227 (experimental)
Best regards,
José Rui
>From gcc-bugs-return-671752-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 10:51:18 2020
Return-Path: <gcc-bugs-return-671752-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24735 invoked by alias); 28 Feb 2020 10:51: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 24713 invoked by uid 48); 28 Feb 2020 10:51:14 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93964] New: [8/9/10 Regression] [graphite] ICE in assign_parameter_index_in_region, at graphite-scop-detection.c:1104
Date: Fri, 28 Feb 2020 10: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
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-93964-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03334.txt.bz2
Content-length: 2592
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93964
Bug ID: 93964
Summary: [8/9/10 Regression] [graphite] ICE in
assign_parameter_index_in_region, at
graphite-scop-detection.c:1104
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-invalid-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.1 snapshot (g:3133bed5d0327e8a9cd0a601b7ecdb9de4fc825d) ICEs when
compiling the following testcase w/ -O1 -floop-nest-optimize:
int *
eo (void);
void
g4 (int *nt)
{
int dh, t2 = eo ();
for (dh = 0; dh < 2; ++dh)
{
int m7;
for (m7 = 0; m7 < t2; ++m7)
nt[m7] = 0;
}
}
% gcc-10.0.1 -O1 -floop-nest-optimize -w -c xerbsq4o.c
during GIMPLE pass: graphite
xerbsq4o.c: In function 'g4':
xerbsq4o.c:5:1: internal compiler error: in assign_parameter_index_in_region,
at graphite-scop-detection.c:1104
5 | g4 (int *nt)
| ^~
0x77656b assign_parameter_index_in_region
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/graphite-scop-detection.c:1104
0x77656b scan_tree_for_params
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/graphite-scop-detection.c:1155
0x16bc2f6 scan_tree_for_params
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/graphite-scop-detection.c:1143
0x16bfd19 before_dom_children
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/graphite-scop-detection.c:1497
0x16632b7 dom_walker::walk(basic_block_def*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/domwalk.c:309
0x16c0a7a build_scops(vec<scop*, va_heap, vl_ptr>*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/graphite-scop-detection.c:1620
0x16b3b24 graphite_transform_loops()
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/graphite.c:448
0x16b4f40 graphite_transforms
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/graphite.c:538
0x16b4f40 execute
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/graphite.c:615
>From gcc-bugs-return-671753-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 11:55:21 2020
Return-Path: <gcc-bugs-return-671753-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38397 invoked by alias); 28 Feb 2020 11:55: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 38357 invoked by uid 48); 28 Feb 2020 11:55:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93582] [10 Regression] -Warray-bounds gives error: array subscript 0 is outside array bounds of struct E[1]
Date: Fri, 28 Feb 2020 11:55: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, 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: P2
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-93582-4-XYcAQ47mrF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93582-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93582-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03335.txt.bz2
Content-length: 1161
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93582
--- Comment #35 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Unfortunately, it breaks miserably, e.g. miscompiles libcpp/macro.c.
Reduced testcase from that:
--- gcc/testsuite/gcc.c-torture/execute/pr93582.c.jj 2020-02-28
12:27:51.280925113 +0100
+++ gcc/testsuite/gcc.c-torture/execute/pr93582.c 2020-02-28
12:26:17.272332573 +0100
@@ -0,0 +1,22 @@
+/* PR tree-optimization/93582 */
+
+short a;
+int b, c;
+
+__attribute__((noipa)) void
+foo (void)
+{
+ b = c;
+ a &= 7;
+}
+
+int
+main ()
+{
+ c = 27;
+ a = 14;
+ foo ();
+ if (b != 27 || a != 6)
+ __builtin_abort ();
+ return 0;
+}
I believe the thing is that for the case with mask we need to completely avoid
the vn_reference_lookup_or_insert_for_pieces calls that finish method does, and
vn_reference_insert
call visit_reference_op_load does.
Probably instead of that we should call vn_nary_op_insert_stmt.
Now, I wonder if e.g. finish couldn't for the masked case just return the tree
itself rather than anything else, and let visit_reference_op_load not call
visit_reference_op_load if mask is non-NULL.
>From gcc-bugs-return-671754-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 11:58:06 2020
Return-Path: <gcc-bugs-return-671754-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47096 invoked by alias); 28 Feb 2020 11:58: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 47036 invoked by uid 48); 28 Feb 2020 11:58:01 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92785] expressions passed as real arguments to a dummy polymorphic argument fail with indexing error
Date: Fri, 28 Feb 2020 11:58: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc assigned_to attachments.created
Message-ID: <bug-92785-4-HY7i7cZGJd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92785-4@http.gcc.gnu.org/bugzilla/>
References: <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: 2020-02/txt/msg03336.txt.bz2
Content-length: 732
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92785
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
--- Comment #2 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 47926
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47926&action=edit
Patch for the PR
For some reason this renormalisation of the descriptors was not done here but
is present in gfc_conv_derived_to_class. I will commit tonight.
Cheers
Paul
>From gcc-bugs-return-671755-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 12:06:30 2020
Return-Path: <gcc-bugs-return-671755-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54371 invoked by alias); 28 Feb 2020 12:06: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 54315 invoked by uid 48); 28 Feb 2020 12:06:26 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92656] The zero_extend insn can't be eliminated in the combine pass
Date: Fri, 28 Feb 2020 12: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: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: segher 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-92656-4-o1XTJpfL1o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92656-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92656-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03337.txt.bz2
Content-length: 272
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92656
--- Comment #6 from Segher Boessenkool <segher at gcc dot gnu.org> ---
The is no simple solution, yeah. It may be possible to have a simple change
that results in better code on average, but that will be marginal :-/
>From gcc-bugs-return-671756-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 12:26:13 2020
Return-Path: <gcc-bugs-return-671756-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69061 invoked by alias); 28 Feb 2020 12: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 69032 invoked by uid 48); 28 Feb 2020 12:26:09 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92931] gfortran compiler errors
Date: Fri, 28 Feb 2020 12:26: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault 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 cc resolution
Message-ID: <bug-92931-4-0kwSiv88tI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92931-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92931-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03338.txt.bz2
Content-length: 599
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92931
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
CC| |pault at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #3 from Paul Thomas <pault at gcc dot gnu.org> ---
In the absence of a response to Steve's reply of 13th December, I marking this
as invalid and closing.
Paul
>From gcc-bugs-return-671757-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 12:37:20 2020
Return-Path: <gcc-bugs-return-671757-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75665 invoked by alias); 28 Feb 2020 12:37: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 75219 invoked by uid 48); 28 Feb 2020 12:37:15 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92658] x86 lacks vector extend / truncate
Date: Fri, 28 Feb 2020 12:37: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: ubizjak at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92658-4-oAhXfqpe1u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03339.txt.bz2
Content-length: 649
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
--- Comment #4 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Uroš Bizjak from comment #3)
> Richi, should the following test also vectorize?
It doesn't vectorize because supportable_convert_operation returns false for:
(gdb) p debug_generic_expr (vectype_out)
vector(4) unsigned int
$1 = void
(gdb) p debug_generic_expr (vectype_in)
vector(4) unsigned char
$2 = void
and TYPE_MODE for "vector(4) unsigned char" returns E_SImode:
(gdb) p m1
$3 = E_V4SImode
(gdb) p m2
$4 = E_SImode
and:
if (!VECTOR_MODE_P (m1) || !VECTOR_MODE_P (m2))
return false;
>From gcc-bugs-return-671758-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 12:42:43 2020
Return-Path: <gcc-bugs-return-671758-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82362 invoked by alias); 28 Feb 2020 12:42: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 82289 invoked by uid 48); 28 Feb 2020 12:42:38 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92658] x86 lacks vector extend / truncate
Date: Fri, 28 Feb 2020 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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-92658-4-WP3PT5V8Mx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03340.txt.bz2
Content-length: 687
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #47924|0 |1
is obsolete| |
--- Comment #5 from Uroš Bizjak <ubizjak at gmail dot com> ---
Created attachment 47927
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47927&action=edit
Prototype patch v2
A couple of typos fixed.
Still doesn't vectorize v4qi->v4si, v2qi->v2di, v2hi->v2di and v4qi->v4di.
Looks like tree-opt issue, as explained in Comment #4.
>From gcc-bugs-return-671760-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 12:51:23 2020
Return-Path: <gcc-bugs-return-671760-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93618 invoked by alias); 28 Feb 2020 12:51: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 93567 invoked by uid 48); 28 Feb 2020 12:51:19 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/93965] Problematic ld_date configure check
Date: Fri, 28 Feb 2020 12:51: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:
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-93965-4-VRPYqAOyIp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03342.txt.bz2
Content-length: 557
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93965
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-28
CC| |jakub at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-671759-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 12:51:00 2020
Return-Path: <gcc-bugs-return-671759-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92854 invoked by alias); 28 Feb 2020 12:51: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 92816 invoked by uid 48); 28 Feb 2020 12:50:55 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/93965] New: Problematic ld_date configure check
Date: Fri, 28 Feb 2020 12:51: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: 9.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 target_milestone
Message-ID: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03341.txt.bz2
Content-length: 1128
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93965
Bug ID: 93965
Summary: Problematic ld_date configure check
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
We're trying as SUSE to update binutils in our Factory and I noticed strange
configure detection. We've got the following version of ld:
$ ld -v
GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.34.0.20200216-385
which is then wrongly parsed in gcc/configure.ac:
ld_date=`echo $ld_ver | sed -n
's,^.*\([2-9][0-9][0-9][0-9]\)[-]*\([01][0-9]\)[-]*\([0-3][0-9]\).*$,\1\2\3,p'`
$ echo "GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.34.0.20200216-385" | sed
-n
's,^.*\([2-9][0-9][0-9][0-9]\)[-]*\([01][0-9]\)[-]*\([0-3][0-9]\).*$,\1\2\3,p'
20021638
Obvious fix would be removal of the '[-]*' parts of the regex.
Is there any ld that uses 2020-02-28 datetime format? The code is there for at
least 16 years.
>From gcc-bugs-return-671761-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 12:58:23 2020
Return-Path: <gcc-bugs-return-671761-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98404 invoked by alias); 28 Feb 2020 12:58: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 98359 invoked by uid 48); 28 Feb 2020 12:58:19 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92658] x86 lacks vector extend / truncate
Date: Fri, 28 Feb 2020 12:58: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: ubizjak at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92658-4-qsgMNbTcAh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03343.txt.bz2
Content-length: 555
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
--- Comment #6 from Uroš Bizjak <ubizjak at gmail dot com> ---
Created attachment 47928
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47928&action=edit
Test cases
sse4, avx2 and avx512bw test cases.
Fails:
FAIL: gcc.target/i386/pr92658-avx2.c scan-assembler-times pmovzxbq 2
FAIL: gcc.target/i386/pr92658-sse4.c scan-assembler-times pmovzxbd 2
FAIL: gcc.target/i386/pr92658-sse4.c scan-assembler-times pmovzxbq 2
FAIL: gcc.target/i386/pr92658-sse4.c scan-assembler-times pmovzxwq 2
>From gcc-bugs-return-671762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 13:03:50 2020
Return-Path: <gcc-bugs-return-671762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103878 invoked by alias); 28 Feb 2020 13:03: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 103845 invoked by uid 48); 28 Feb 2020 13:03:46 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92658] x86 lacks vector extend / truncate
Date: Fri, 28 Feb 2020 13:03: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: ubizjak at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92658-4-LBLneYjSGL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03344.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |richard.sandiford at arm dot com
--- Comment #7 from Uroš Bizjak <ubizjak at gmail dot com> ---
CC author of the generic functionality part.
>From gcc-bugs-return-671763-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 13:05:30 2020
Return-Path: <gcc-bugs-return-671763-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106224 invoked by alias); 28 Feb 2020 13:05: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 106173 invoked by uid 48); 28 Feb 2020 13:05:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/93965] Problematic ld_date configure check
Date: Fri, 28 Feb 2020 13:05: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:
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-93965-4-6xRyKlMIJa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03345.txt.bz2
Content-length: 300
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93965
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Dunno, but wouldn't it be better to require either no -s or both, but not just
one?
So
sed -n
's,^.*\([2-9][0-9][0-9][0-9]\)\([-]*\)\([01][0-9]\)\2\([0-3][0-9]\).*$,\1\3\4,p'
?
>From gcc-bugs-return-671764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 13:09:27 2020
Return-Path: <gcc-bugs-return-671764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111146 invoked by alias); 28 Feb 2020 13: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 110438 invoked by uid 48); 28 Feb 2020 13:09:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/93965] Problematic ld_date configure check
Date: Fri, 28 Feb 2020 13:09: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:
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-93965-4-O4szOfAuRq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03346.txt.bz2
Content-length: 239
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93965
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I don't see the point of [-]* btw, could be just -* or maybe better -\? (though
not sure if that is portable enough).
>From gcc-bugs-return-671765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 13:09:45 2020
Return-Path: <gcc-bugs-return-671765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115468 invoked by alias); 28 Feb 2020 13:09: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 113205 invoked by uid 48); 28 Feb 2020 13:09:40 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93966] New: -fcf-protection -flto -g don't work togeter
Date: Fri, 28 Feb 2020 13:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools 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-93966-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03347.txt.bz2
Content-length: 974
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93966
Bug ID: 93966
Summary: -fcf-protection -flto -g don't work togeter
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: marxin at gcc dot gnu.org, rguenth at gcc dot gnu.org
Target Milestone: ---
[hjl@gnu-cfl-2 tmp]$ cat x.c
#include <stdio.h>
int
main ()
{
printf ("hello\n");
return 0;
}
[hjl@gnu-cfl-2 tmp]$ gcc -flto -c x.c
[hjl@gnu-cfl-2 tmp]$ gcc x.o -Wl,-z,cet-report=error -fcf-protection
[hjl@gnu-cfl-2 tmp]$ gcc -flto -c x.c -g
[hjl@gnu-cfl-2 tmp]$ gcc x.o -Wl,-z,cet-report=error -fcf-protection -g
/usr/local/bin/ld: /tmp/cchkKahV.debug.temp.o: error: missing IBT and SHSTK
properties
collect2: error: ld returned 1 exit status
[hjl@gnu-cfl-2 tmp]$
>From gcc-bugs-return-671766-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 13:28:10 2020
Return-Path: <gcc-bugs-return-671766-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58783 invoked by alias); 28 Feb 2020 13: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 57146 invoked by uid 48); 28 Feb 2020 13:27:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93674] [8/9/10 Regression] GCC eliminates conditions it should not, when strict-enums is on
Date: Fri, 28 Feb 2020 13:27: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.1
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: P2
X-Bugzilla-Assigned-To: amker at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-93674-4-cgdvOG5jO4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93674-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93674-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03348.txt.bz2
Content-length: 289
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93674
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P1 |P2
>From gcc-bugs-return-671767-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 13:54:06 2020
Return-Path: <gcc-bugs-return-671767-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120771 invoked by alias); 28 Feb 2020 13:54: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 120717 invoked by uid 48); 28 Feb 2020 13:54:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/93909] [10 regression] new test cases gcc.dg/ipa/pr93763.c and g++.dg/ipa/pr93763.C fail
Date: Fri, 28 Feb 2020 13:54: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: 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 cc resolution
Message-ID: <bug-93909-4-dpOYnT98MC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93909-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93909-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03349.txt.bz2
Content-length: 574
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93909
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |jakub at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This should have been fixed with
r10-6835-g103bc4db7665a03bf2390ccc8ceca0dc5a7a81b7
>From gcc-bugs-return-671768-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 14:03:17 2020
Return-Path: <gcc-bugs-return-671768-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4433 invoked by alias); 28 Feb 2020 14:03: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 4391 invoked by uid 48); 28 Feb 2020 14:03:11 -0000
From: "guillaume at morinfr dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93951] ICE with '-flto -g -femit-struct-debug-baseonly'
Date: Fri, 28 Feb 2020 14:03: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: 9.2.1
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: guillaume at morinfr dot 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-93951-4-CQETYJexqI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03350.txt.bz2
Content-length: 407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93951
--- Comment #2 from Guillaume Morin <guillaume at morinfr dot org> ---
fwiw the reproducer can be reduced further to:
#include <variant>
struct S1 {
bool fct() const;
};
struct V {
bool visit() const {
auto visitor = [](auto&& s) -> bool { return s.fct(); };
return std::visit(visitor, v);
}
std::variant<S1> v;
};
>From gcc-bugs-return-671769-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 14:37:35 2020
Return-Path: <gcc-bugs-return-671769-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72609 invoked by alias); 28 Feb 2020 14:37: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 72529 invoked by uid 48); 28 Feb 2020 14:37:30 -0000
From: "gcc at cookiesoft dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93967] New: switch on exhaustive enum gives control reaches end of non-void function
Date: Fri, 28 Feb 2020 14:37: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: gcc at cookiesoft 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-93967-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03351.txt.bz2
Content-length: 1019
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93967
Bug ID: 93967
Summary: switch on exhaustive enum gives control reaches end of
non-void function
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc at cookiesoft dot de
Target Milestone: ---
```
enum class A { X, Y, Z };
int foo(A a) {
switch (a) {
case A::X: return 1;
case A::Y: return 2;
case A::Z: return 3;
}
}
```
`g++ input.cpp`
```
<source>: In function 'int foo(A)':
<source>:9:1: warning: control reaches end of non-void function [-Wreturn-type]
9 | }
| ^
```
The switch is exhaustive and so there is no way that the function reaches the
code path after the switch. Clang does not emit a warning.
This happens on every version of gcc.
Godbolt: https://cpp.godbolt.org/z/Goii_K
>From gcc-bugs-return-671770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 14:37:46 2020
Return-Path: <gcc-bugs-return-671770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73293 invoked by alias); 28 Feb 2020 14:37: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 73247 invoked by uid 48); 28 Feb 2020 14:37:41 -0000
From: "gcc at cookiesoft dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93968] New: -Wswitch-default on exhaustive enum class gives warning
Date: Fri, 28 Feb 2020 14:37: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: gcc at cookiesoft 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-93968-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03352.txt.bz2
Content-length: 1059
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93968
Bug ID: 93968
Summary: -Wswitch-default on exhaustive enum class gives
warning
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc at cookiesoft dot de
Target Milestone: ---
```
enum class A { X, Y, Z };
int foo(A a) {
switch (a) {
case A::X: return 1;
case A::Y: return 2;
case A::Z: return 3;
}
}
```
`g++ -Wswitch-default input.cpp`
```
<source>: In function 'int foo(A)':
<source>:4:12: warning: switch missing default case [-Wswitch-default]
4 | switch (a) {
| ^
```
The switch is exhaustive and so there should no warning for a default case, but
when compiling it with `-Wswitch-default` it does emit a warning. Clang does
not.
This happens on every version of gcc.
Godbolt: https://cpp.godbolt.org/z/Goii_K
>From gcc-bugs-return-671771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 14:39:52 2020
Return-Path: <gcc-bugs-return-671771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74799 invoked by alias); 28 Feb 2020 14:39: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 74763 invoked by uid 48); 28 Feb 2020 14:39:47 -0000
From: "igusarov at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93969] New: Static data member cannot be initialized in place, if it is of a nested class type with a default argument in its constructor.
Date: Fri, 28 Feb 2020 14:39: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: igusarov at mail dot ru
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-93969-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03353.txt.bz2
Content-length: 2607
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93969
Bug ID: 93969
Summary: Static data member cannot be initialized in place, if
it is of a nested class type with a default argument
in its constructor.
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: igusarov at mail dot ru
Target Milestone: ---
Dear gcc developers,
x86_64-gcc-9.2 available online at godbolt.org, refuses to compile a sample
program which I believe is well-formed:
struct Outer
{
struct Inner
{
Inner(int arg = 23);
};
static inline Inner x{}; // (1)
};
If invoked with a sole "-std=c++17" command-line option, the compilation fails
at line marked (1) and the following error is reported:
error: call to 'Outer::Inner::Inner(int)'
uses the default argument for parameter 1,
which is not yet defined
The sample program looks well-formed to me because of the following reasoning:
(clause numbers are per N4659 C++17 draft at
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/n4659.pdf )
1) Class Outer::Inner is fully defined at its closing brace (12.2/p6) and
therefore is already a complete-type before Outer::x data member is declared;
2) The declaration of static inline data member Outer::x comes with a
brace-initializer (12.2/p8) which means that it is also the definition
(12.2.3.2/p3), also initializing-declaration and defining declaration
(11.6/p21);
3) Outer::x is direct-list-initialized (11.6/p16, 11.6/p17); the initializer
list is empty;
4) Class Outer::Inner has a user-defined constructor Outer::Inner::Inner(int).
That constructor is the default constructor because every formal parameter has
a corresponding default argument (15.1/p4);
5) Combination of points 3) and 4) means that Outer::x should be
default-initialized (11.6.4/p3.4, 11.6/p8.1);
6) Default initialization of Outer::x should be performed by calling its
matching constructor with an empty argument list (11.6/p7.1);
7) Each time the constructor is called with no arguments, default argument
should be evaluated for the corresponding parameter (11.3.6/p9);
8) Default argument to that constructor is an integral constant expression
which is already defined. So it seems that evaluation of the said default
argument should cause no problem.
----
P.S. clang-9.0.0 also reports a similar error.
>From gcc-bugs-return-671772-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 14:59:44 2020
Return-Path: <gcc-bugs-return-671772-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 131010 invoked by alias); 28 Feb 2020 14:59: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 130958 invoked by uid 55); 28 Feb 2020 14:59:39 -0000
From: "urbanjost at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92785] expressions passed as real arguments to a dummy polymorphic argument fail with indexing error
Date: Fri, 28 Feb 2020 14: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: 9.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: urbanjost at comcast dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92785-4-7ve8RdAXTx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92785-4@http.gcc.gnu.org/bugzilla/>
References: <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: 2020-02/txt/msg03354.txt.bz2
Content-length: 1205
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92785
--- Comment #3 from urbanjost at comcast dot net ---
Great! Looking forward to using polymorphic variables in more and more
applications and this problem had put a hold on that.
> On February 28, 2020 at 6:58 AM "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92785
>
> Paul Thomas <pault at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |pault at gcc dot gnu.org
> Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
>
> --- Comment #2 from Paul Thomas <pault at gcc dot gnu.org> ---
> Created attachment 47926
> --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47926&action=edit
> Patch for the PR
>
> For some reason this renormalisation of the descriptors was not done here but
> is present in gfc_conv_derived_to_class. I will commit tonight.
>
> Cheers
>
> Paul
>
> --
> You are receiving this mail because:
> You reported the bug.
>From gcc-bugs-return-671773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 15:17:20 2020
Return-Path: <gcc-bugs-return-671773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31065 invoked by alias); 28 Feb 2020 15: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 31019 invoked by uid 48); 28 Feb 2020 15:17:15 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93960] std::to_address doesn't work with past-the-end Debug Mode iterators
Date: Fri, 28 Feb 2020 15:17: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: redi 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-93960-4-eB4WYTkwIm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93960-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93960-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03355.txt.bz2
Content-length: 1540
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93960
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-02-28
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This seems to work:
--- a/libstdc++-v3/include/debug/safe_iterator.h
+++ b/libstdc++-v3/include/debug/safe_iterator.h
@@ -35,6 +35,9 @@
#include <debug/safe_base.h>
#include <bits/stl_pair.h>
#include <ext/type_traits.h>
+#if __cplusplus > 201703L
+# include <concepts>
+#endif
#define _GLIBCXX_DEBUG_VERIFY_OPERANDS(_Lhs, _Rhs, _BadMsgId, _DiffMsgId) \
_GLIBCXX_DEBUG_VERIFY(!_Lhs._M_singular() && !_Rhs._M_singular(), \
@@ -952,6 +955,13 @@ namespace __gnu_debug
__unsafe(const _Safe_iterator<_Iterator, _Sequence>& __it)
{ return __it.base(); }
+#if __cplusplus > 201703L && __cpp_lib_concepts
+ template<std::derived_from<_Safe_iterator_base> _Iter>
+ constexpr auto
+ __to_address(const _Iter& __iter) noexcept
+ { return std::__to_address(__iter.operator->()); }
+#endif
+
} // namespace __gnu_debug
#undef _GLIBCXX_DEBUG_VERIFY_DIST_OPERANDS
This overload is more constrained than the existing ones, so gets chosen by
overload resolution.
>From gcc-bugs-return-671774-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 15:20:53 2020
Return-Path: <gcc-bugs-return-671774-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36558 invoked by alias); 28 Feb 2020 15:20: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 36513 invoked by uid 55); 28 Feb 2020 15:20:48 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87612] Bad diagnostic for conflicting mcpu and march options on aarch64
Date: Fri, 28 Feb 2020 15:20: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-87612-4-DZjakBvB2G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87612-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87612-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03356.txt.bz2
Content-length: 897
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87612
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Joel Hutton <joelh@gcc.gnu.org>:
https://gcc.gnu.org/g:349297b6e69c5af74ed26a333488b1bf994dbcce
commit r10-6918-g349297b6e69c5af74ed26a333488b1bf994dbcce
Author: Joel Hutton <joel.hutton@arm.com>
Date: Fri Feb 28 14:46:26 2020 +0000
Fix misleading aarch64 mcpu/march warning string
The message for conflicting mcpu and march previously printed the
architecture of the CPU instead of the CPU name, as well as omitting the
extensions to the march string. This patch corrects both errors. This
patch fixes PR target/87612.
2020-02-27 Joel Hutton <Joel.Hutton@arm.com>
PR target/87612
* config/aarch64/aarch64.c (aarch64_override_options): Fix
misleading warning string.
>From gcc-bugs-return-671775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 15:28:03 2020
Return-Path: <gcc-bugs-return-671775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53077 invoked by alias); 28 Feb 2020 15:28: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 52288 invoked by uid 48); 28 Feb 2020 15:27:57 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92692] Saving off the callee saved register between ldxr/stxr (caused by shrink wrapping improvements)
Date: Fri, 28 Feb 2020 15: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: wrong-code
X-Bugzilla-Severity: blocker
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: wilco at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92692-4-CYSWoVNjb8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92692-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92692-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03357.txt.bz2
Content-length: 1160
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92692
--- Comment #22 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Sebastian Pop from comment #21)
> It looks like this hunk from the trunk version of the patch is missing on
> gcc-9 branch:
>
> diff --git a/gcc/config/aarch64/atomics.md b/gcc/config/aarch64/atomics.md
> index cabcc58f1a0..1458bc00095 100644
> --- a/gcc/config/aarch64/atomics.md
> +++ b/gcc/config/aarch64/atomics.md
> @@ -104,7 +104,7 @@
> (clobber (match_scratch:SI 7 "=&r"))]
> ""
> "#"
> - "&& reload_completed"
> + "&& epilogue_completed"
> [(const_int 0)]
> {
> aarch64_split_compare_and_swap (operands);
>
>
>
> With this hunk applied my bootstrap passes on the gcc-9 branch on an
> aarch64-linux graviton2.
>
> Without this hunk I see an error in thread sanitizers.
>
> I also have checked gcc-8 release branch and it seems that the patch is not
> missing any hunks in that branch.
>
> Could somebody apply the missing hunk to the gcc-9 release branch? Thanks!
I don't see anything like that on the gcc-9 branch - are you sure you don't
have an outstanding change somehow?
>From gcc-bugs-return-671776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 15:29:59 2020
Return-Path: <gcc-bugs-return-671776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56704 invoked by alias); 28 Feb 2020 15:29: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 56640 invoked by uid 48); 28 Feb 2020 15:29:56 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/80635] [8/9/10 regression] std::optional and bogus -Wmaybe-uninitialized warning
Date: Fri, 28 Feb 2020 15: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: 8.2.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-80635-4-mYGtoVaP9H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80635-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80635-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03358.txt.bz2
Content-length: 1006
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80635
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |law at redhat dot com
--- Comment #44 from Jeffrey A. Law <law at redhat dot com> ---
I suspect in the context where SRA creates the V_C_E we don't have enough
information to know that the range of the input object is constrained enough.
We base the decision solely on the types.
By the time we get into the middle end we can follow the use-def chain to the
PHI and realize the source object only has two possible values at runtime and
we can optimize the V_C_E into a NOP_EXPR.
I've contacted Eric B. offline on the semantics of V_C_E. I think the
agreement is in this kind of scenario we ought to be able to simplify it into a
NOP_EXPR which should be sufficient to eliminate the false positive.
>From gcc-bugs-return-671777-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 15:43:48 2020
Return-Path: <gcc-bugs-return-671777-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79588 invoked by alias); 28 Feb 2020 15:43: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 79541 invoked by uid 48); 28 Feb 2020 15:43:43 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93745] Redundant store not eliminated with intermediate instruction
Date: Fri, 28 Feb 2020 15: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93745-4-vv82CnyyQy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03359.txt.bz2
Content-length: 529
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93745
--- Comment #12 from Jeffrey A. Law <law at redhat dot com> ---
It would seem like C ought to be able to set the flag across the board. But
Richi would know best if this is going to run afoul of of the alias oracle
implementation & underlying gimple semantics.
I vaguely recall a discussion on the lists WRT how to represent placement-new.
I didn't follow it at the time. Without reviewing the thread it does seem
helpful if we could see the placement-new in the IL.
>From gcc-bugs-return-671778-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 15:55:14 2020
Return-Path: <gcc-bugs-return-671778-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86149 invoked by alias); 28 Feb 2020 15:55: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 86102 invoked by uid 48); 28 Feb 2020 15:55:10 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93966] -fcf-protection -flto -g don't work togeter
Date: Fri, 28 Feb 2020 15:55: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to attachments.created
Message-ID: <bug-93966-4-00hg2DCFWf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03360.txt.bz2
Content-length: 488
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93966
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |hjl.tools at gmail dot com
--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
Created attachment 47929
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47929&action=edit
A patch
>From gcc-bugs-return-671779-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 16:06:22 2020
Return-Path: <gcc-bugs-return-671779-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9640 invoked by alias); 28 Feb 2020 16:06: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 9589 invoked by uid 48); 28 Feb 2020 16:06:18 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87560] ICE in curr_insn_transform, at lra-constraints.c:3892
Date: Fri, 28 Feb 2020 16: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt 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-87560-4-qa1kXSLKJV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87560-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87560-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03361.txt.bz2
Content-length: 305
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87560
--- Comment #3 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
I expect the problem is still there somewhere, but it's gone latent. There
haven't been any changes to *xxspltib_<mode>_split since 2016. Will need to
look at gcc-9 branch to debug.
>From gcc-bugs-return-671780-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 16:07:57 2020
Return-Path: <gcc-bugs-return-671780-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13564 invoked by alias); 28 Feb 2020 16:07: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 13517 invoked by uid 48); 28 Feb 2020 16:07:52 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87560] ICE in curr_insn_transform, at lra-constraints.c:3892
Date: Fri, 28 Feb 2020 16: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt 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-87560-4-WP7IXdnTlv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87560-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87560-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03362.txt.bz2
Content-length: 234
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87560
--- Comment #4 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Although perhaps we've done a better job of sorting out these flags since then.
Segher, anything ring a bell?
>From gcc-bugs-return-671781-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 16:14:38 2020
Return-Path: <gcc-bugs-return-671781-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24319 invoked by alias); 28 Feb 2020 16:14: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 24133 invoked by uid 48); 28 Feb 2020 16:14:33 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/93965] Problematic ld_date configure check
Date: Fri, 28 Feb 2020 16:14: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:
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-93965-4-u4by2xbR2D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03363.txt.bz2
Content-length: 780
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93965
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #1)
> Dunno, but wouldn't it be better to require either no -s or both, but not
> just one?
> So
> sed -n
> 's,^.*\([2-9][0-9][0-9][0-9]\)\([-]*\)\([01][0-9]\)\2\([0-3][0-9]\).*$,
> \1\3\4,p'
> ?
Thank you Jakub. I like to suggested patch. I'm going to send it to the mailing
list.
>From gcc-bugs-return-671782-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 16:29:18 2020
Return-Path: <gcc-bugs-return-671782-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61959 invoked by alias); 28 Feb 2020 16:29: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 56052 invoked by uid 55); 28 Feb 2020 16:29:14 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93564] [10 Regression] 470.lbm regresses by 25% on znver2 with -Ofast -march=native LTO and PGO since r10-6384-g2a07345c4f8dabc2
Date: Fri, 28 Feb 2020 16:29: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
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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:
Message-ID: <bug-93564-4-Xxh9zUfqrK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93564-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93564-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03364.txt.bz2
Content-length: 719
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93564
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>:
https://gcc.gnu.org/g:f3ce088645e5305d932380c7520809181b2d2eb9
commit r10-6919-gf3ce088645e5305d932380c7520809181b2d2eb9
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date: Fri Feb 28 11:27:30 2020 -0500
One more patch for PR93564: Prefer smaller hard regno when we do not honor
reg alloc order.
2020-02-28 Vladimir Makarov <vmakarov@redhat.com>
PR rtl-optimization/93564
* ira-color.c (assign_hard_reg): Prefer smaller hard regno when we
do not honor reg alloc order.
>From gcc-bugs-return-671783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 16:54:50 2020
Return-Path: <gcc-bugs-return-671783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94899 invoked by alias); 28 Feb 2020 16:54: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 94848 invoked by uid 55); 28 Feb 2020 16:54:45 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/93965] Problematic ld_date configure check
Date: Fri, 28 Feb 2020 16:54: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93965-4-CQY24CAMfH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03365.txt.bz2
Content-length: 588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93965
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>:
https://gcc.gnu.org/g:08bf7bde9f2987b1c623d272cc71fc14a1622442
commit r10-6921-g08bf7bde9f2987b1c623d272cc71fc14a1622442
Author: Martin Liska <mliska@suse.cz>
Date: Fri Feb 28 17:52:57 2020 +0100
Improve detection of ld_date.
PR other/93965
* configure.ac: Improve detection of ld_date by requiring
either two dashes or none.
* configure: Regenerate.
>From gcc-bugs-return-671784-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 16:56:06 2020
Return-Path: <gcc-bugs-return-671784-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99763 invoked by alias); 28 Feb 2020 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 99723 invoked by uid 48); 28 Feb 2020 16:56:01 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/93965] Problematic ld_date configure check
Date: Fri, 28 Feb 2020 16:56: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:
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: cf_known_to_work cf_known_to_fail
Message-ID: <bug-93965-4-zf1pjHlUy6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03366.txt.bz2
Content-length: 452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93965
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |10.0
Known to fail| |8.3.0, 9.2.0
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed on trunk so far.
>From gcc-bugs-return-671785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 17:05:51 2020
Return-Path: <gcc-bugs-return-671785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59144 invoked by alias); 28 Feb 2020 17:05: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 59061 invoked by uid 48); 28 Feb 2020 17:05:46 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93970] New: load via restricted pointer not eliminated after a store via a restricted pointer of incompatible type
Date: Fri, 28 Feb 2020 17:05: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-93970-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03367.txt.bz2
Content-length: 1723
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93970
Bug ID: 93970
Summary: load via restricted pointer not eliminated after a
store via a restricted pointer of incompatible type
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: ---
In the test case below the test in f() is folded to false as expected, but the
similar test in g() is not folded, even though in both functions the pointers
are restricted and in g() they additionally point to incompatible types.
$ cat t.c && gcc -O2 -S -Wall -Wextra -fdump-tree-optimized=/dev/stdout t.c
void f (int *__restrict p, int *__restrict q)
{
int t = *q;
*p = 0;
if (t != *q) // folded to false
__builtin_abort ();
}
void g (int *__restrict p, double *__restrict q)
{
double t = *q;
*p = 0;
if (t != *q) // not folded
__builtin_abort ();
}
;; Function f (f, funcdef_no=0, decl_uid=1931, cgraph_uid=1, symbol_order=0)
f (int * restrict p, int * restrict q)
{
<bb 2> [local count: 1073741824]:
*p_3(D) = 0;
return;
}
;; Function g (g, funcdef_no=1, decl_uid=1936, cgraph_uid=2, symbol_order=1)
g (int * restrict p, double * restrict q)
{
double t;
<bb 2> [local count: 1073741824]:
t_3 = *q_2(D);
*p_4(D) = 0;
if (t_3 != t_3)
goto <bb 3>; [0.00%]
else
goto <bb 4>; [100.00%]
<bb 3> [count: 0]:
__builtin_abort ();
<bb 4> [local count: 1073741824]:
return;
}
>From gcc-bugs-return-671786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 17:07:21 2020
Return-Path: <gcc-bugs-return-671786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64662 invoked by alias); 28 Feb 2020 17:07: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 64646 invoked by uid 48); 28 Feb 2020 17:07:17 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93971] New: C++ containers considered to alias declared objects of incompatible types
Date: Fri, 28 Feb 2020 17:07: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-93971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03368.txt.bz2
Content-length: 2028
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93971
Bug ID: 93971
Summary: C++ containers considered to alias declared objects of
incompatible types
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: ---
Inspired by the discussion in pr93745 I tried the following to see if GCC was
able to eliminate the test: it isn't, not even after declaring
std::vector::_M_impl._M_start restrict.
In bug 49367 Jason points out a similar limitation except involving pointers of
the same type pointing to (potentially) allocated storage. Here it's clear
that _M_impl._M_start cannot point to x because x is accessed (i.e., first read
and then written) by an incompatible type. Another similar test case is in bug
49761.
Even declaring v __restrict doesn't help.
$ cat t.C && gcc -O2 -S -Wall -fdump-tree-optimized=/dev/stdout t.C
#include <vector>
double x;
void f (std::vector<int> &v)
{
double t = x;
v[0] = 0;
if (t != x)
__builtin_abort ();
}
;; Function f (_Z1fRSt6vectorIiSaIiEE, funcdef_no=880, decl_uid=16170,
cgraph_uid=169, symbol_order=170)
f (struct vector & v)
{
double t;
int * _4;
<bb 2> [local count: 1073741824]:
t_2 = x;
_4 = v_3(D)->D.17243._M_impl.D.16553._M_start;
MEM[(value_type &)_4] = 0;
if (t_2 != t_2)
goto <bb 3>; [0.00%]
else
goto <bb 4>; [100.00%]
<bb 3> [count: 0]:
__builtin_abort ();
<bb 4> [local count: 1073741824]:
return;
}
The roughly equivalent C test case is:
struct V { int *restrict p; };
double x;
void f (struct V * /* restrict */ p) // restrict here makes no difference
{
double t = x;
p->p[0] = 0;
if (t != x)
__builtin_abort ();
}
>From gcc-bugs-return-671787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 17:09:53 2020
Return-Path: <gcc-bugs-return-671787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68189 invoked by alias); 28 Feb 2020 17: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 68147 invoked by uid 48); 28 Feb 2020 17:09:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93968] -Wswitch-default on exhaustive enum class gives warning about missing default case
Date: Fri, 28 Feb 2020 17: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: unknown
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-93968-4-1bPlSb0RM2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93968-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03369.txt.bz2
Content-length: 656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93968
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> ---
(A)3 is a valid value for a and is not handled by the switch.
See http://eel.is/c++draft/dcl.enum#8
In your case, the underlying type is fixed int, and so a can have any int
value.
Even if you used just enum A { X, Y, Z }, (A)3 would still be within the valid
range of values.
>From gcc-bugs-return-671788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 17:29:34 2020
Return-Path: <gcc-bugs-return-671788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96869 invoked by alias); 28 Feb 2020 17:29: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 96830 invoked by uid 48); 28 Feb 2020 17:29:30 -0000
From: "stilor at att dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93751] -g1 does not behave per manual
Date: Fri, 28 Feb 2020 17:29: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: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: stilor at att 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: attachments.created
Message-ID: <bug-93751-4-SzuPwQ5MuR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03370.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93751
--- Comment #14 from Alexey Neyman <stilor at att dot net> ---
Created attachment 47930
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47930&action=edit
Patch, v3
In gcc-patches, there have been three votes for generating external variables'
DIEs without an additional option. Updated the patch to do that.
I'd be happy to see either of v2 or v3 of the patch picked up.
>From gcc-bugs-return-671789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 17:31:34 2020
Return-Path: <gcc-bugs-return-671789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101436 invoked by alias); 28 Feb 2020 17:31: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 100935 invoked by uid 48); 28 Feb 2020 17:31:27 -0000
From: "stilor at att dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93751] -g1 does not behave per manual
Date: Fri, 28 Feb 2020 17: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: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: stilor at att 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: attachments.isobsolete attachments.created
Message-ID: <bug-93751-4-Kbh0CEo2T1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03371.txt.bz2
Content-length: 509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93751
Alexey Neyman <stilor at att dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #47930|0 |1
is obsolete| |
--- Comment #15 from Alexey Neyman <stilor at att dot net> ---
Created attachment 47931
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47931&action=edit
Patch, v3
>From gcc-bugs-return-671790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 17:54:04 2020
Return-Path: <gcc-bugs-return-671790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56309 invoked by alias); 28 Feb 2020 17: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 56226 invoked by uid 55); 28 Feb 2020 17:53:59 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/93965] Problematic ld_date configure check
Date: Fri, 28 Feb 2020 17:54: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93965-4-Xs6ijXZrDx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03372.txt.bz2
Content-length: 698
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93965
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Martin Liska
<marxin@gcc.gnu.org>:
https://gcc.gnu.org/g:9179ae6a0df27e3d3830ee42f755dc7d76cb0423
commit r9-8303-g9179ae6a0df27e3d3830ee42f755dc7d76cb0423
Author: Martin Liska <mliska@suse.cz>
Date: Fri Feb 28 18:52:55 2020 +0100
Backport 08bf7bde9f2987b1c623d272cc71fc14a1622442
Backport from mainline
2020-02-28 Martin Liska <mliska@suse.cz>
PR other/93965
* configure.ac: Improve detection of ld_date by requiring
either two dashes or none.
* configure: Regenerate.
>From gcc-bugs-return-671791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 17:57:28 2020
Return-Path: <gcc-bugs-return-671791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60238 invoked by alias); 28 Feb 2020 17:57: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 60217 invoked by uid 48); 28 Feb 2020 17:57:24 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93972] New: ranges::lexicographical_compare gives wrong answer for signed integers
Date: Fri, 28 Feb 2020 17:57: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: 10.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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-93972-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03373.txt.bz2
Content-length: 861
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93972
Bug ID: 93972
Summary: ranges::lexicographical_compare gives wrong answer for
signed integers
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
CC: ppalka at gcc dot gnu.org
Target Milestone: ---
// -std=gnu++2a
#include <algorithm>
#include <assert.h>
int main()
{
int i[] = { -1 };
int j[] = { 1 };
assert( std::ranges::lexicographical_compare(i, j) );
}
a.out: range.cc:8: int main(): Assertion
`std::ranges::lexicographical_compare(i, j)' failed.
Aborted (core dumped)
It's not valid to use memcmp for signed integers.
>From gcc-bugs-return-671792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 18:21:22 2020
Return-Path: <gcc-bugs-return-671792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26424 invoked by alias); 28 Feb 2020 18:21: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 26344 invoked by uid 48); 28 Feb 2020 18:21:17 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87560] ICE in curr_insn_transform, at lra-constraints.c:3892
Date: Fri, 28 Feb 2020 18:21: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.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher 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-87560-4-2J6D0JoA6w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87560-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87560-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03374.txt.bz2
Content-length: 207
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87560
--- Comment #5 from Segher Boessenkool <segher at gcc dot gnu.org> ---
This code is unmodified since 2016, and we didn't change the flag handling
afair.
>From gcc-bugs-return-671794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 18:26:13 2020
Return-Path: <gcc-bugs-return-671794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31049 invoked by alias); 28 Feb 2020 18: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 30876 invoked by uid 48); 28 Feb 2020 18:26:09 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53479] Control flow analysis reports warnings in switch over an enum class even if all possible values have their branches
Date: Fri, 28 Feb 2020 18: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: 4.6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: minor
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: cc
Message-ID: <bug-53479-4-V69NpC70n2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53479-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53479-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03376.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53479
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gcc at cookiesoft dot de
--- Comment #21 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
*** Bug 93967 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-671793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 18:26:13 2020
Return-Path: <gcc-bugs-return-671793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30926 invoked by alias); 28 Feb 2020 18:26: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 30859 invoked by uid 48); 28 Feb 2020 18:26:09 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93967] switch on exhaustive enum gives control reaches end of non-void function
Date: Fri, 28 Feb 2020 18: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:
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-93967-4-KPNPwtaOJA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93967-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03375.txt.bz2
Content-length: 558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93967
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> ---
See PR 53479 and others.
Basically A(3) is a valid value for the enum.
*** This bug has been marked as a duplicate of bug 53479 ***
>From gcc-bugs-return-671795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 18:27:00 2020
Return-Path: <gcc-bugs-return-671795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32454 invoked by alias); 28 Feb 2020 18:27: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 32362 invoked by uid 48); 28 Feb 2020 18:26:56 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93968] -Wswitch-default on exhaustive enum class gives warning about missing default case
Date: Fri, 28 Feb 2020 18: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: 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-93968-4-FpdV9onc2T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93968-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03377.txt.bz2
Content-length: 568
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93968
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
See dup bug, PR 53479. As mentioned by Jakub, A(3) is valid value of the enum.
*** This bug has been marked as a duplicate of bug 53479 ***
>From gcc-bugs-return-671796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 18:27:01 2020
Return-Path: <gcc-bugs-return-671796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32510 invoked by alias); 28 Feb 2020 18:27: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 32389 invoked by uid 48); 28 Feb 2020 18:26:57 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53479] Control flow analysis reports warnings in switch over an enum class even if all possible values have their branches
Date: Fri, 28 Feb 2020 18: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: 4.6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: minor
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-53479-4-e1d0j6bj7D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53479-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53479-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03378.txt.bz2
Content-length: 184
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53479
--- Comment #22 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
*** Bug 93968 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-671797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 18:29:51 2020
Return-Path: <gcc-bugs-return-671797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35066 invoked by alias); 28 Feb 2020 18:29: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 35017 invoked by uid 55); 28 Feb 2020 18:29:47 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93937] Variable vector extract & zero extend insn can never match
Date: Fri, 28 Feb 2020 18: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: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: meissner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93937-4-JLmnFVdmji@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93937-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93937-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03379.txt.bz2
Content-length: 635
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93937
--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Michael Meissner <meissner@gcc.gnu.org>:
https://gcc.gnu.org/g:ab2f2e19111bfdd013697fdfd0cded5ab291a7a1
commit r10-6923-gab2f2e19111bfdd013697fdfd0cded5ab291a7a1
Author: Michael Meissner <meissner@gcc.gnu.org>
Date: Fri Feb 28 13:28:45 2020 -0500
Fix target/93937
2020-02-28 Michael Meissner <meissner@linux.ibm.com>
PR target/93937
* config/rs6000/vsx.md (vsx_extract_<mode>_<VS_scalar>mode_var):
Delete, the insn will never work.
>From gcc-bugs-return-671798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 18:31:04 2020
Return-Path: <gcc-bugs-return-671798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36738 invoked by alias); 28 Feb 2020 18: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 36454 invoked by uid 48); 28 Feb 2020 18:30:56 -0000
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93972] ranges::lexicographical_compare gives wrong answer for signed integers
Date: Fri, 28 Feb 2020 18:31: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: ppalka at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ppalka 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-93972-4-iZt6dgTQ4G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93972-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93972-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03380.txt.bz2
Content-length: 896
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93972
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-28
Assignee|unassigned at gcc dot gnu.org |ppalka at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Or for unsigned integral types wider than a byte...
#include <algorithm>
#include <assert.h>
int main()
{
unsigned i[] = { 1 };
unsigned j[] = { 256 };
assert( std::ranges::lexicographical_compare(i, j) );
}
Apparently I didn't consult the memcmp check that's used by
std::lexicographical_compare when writing the ranges version.
>From gcc-bugs-return-671799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 18:38:20 2020
Return-Path: <gcc-bugs-return-671799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60397 invoked by alias); 28 Feb 2020 18:38: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 60358 invoked by uid 48); 28 Feb 2020 18:38:16 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92785] expressions passed as real arguments to a dummy polymorphic argument fail with indexing error
Date: Fri, 28 Feb 2020 18: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: 9.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92785-4-ofi640H1l8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92785-4@http.gcc.gnu.org/bugzilla/>
References: <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: 2020-02/txt/msg03381.txt.bz2
Content-length: 491
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92785
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Paul Thomas <pault at gcc dot gnu.org> ---
Committed as revision r10-6924-g7485ace81de9ec9dd5c87edf67e359d31ce35a20
Paul
>From gcc-bugs-return-671800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 19:06:37 2020
Return-Path: <gcc-bugs-return-671800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116152 invoked by alias); 28 Feb 2020 19:06: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 113313 invoked by uid 48); 28 Feb 2020 19:06:32 -0000
From: "david.alvarez at bsc dot es" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93973] New: Wrong constexpr copy/move assignment operator allowed on non-literal type
Date: Fri, 28 Feb 2020 19: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: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: david.alvarez at bsc dot es
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-93973-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03382.txt.bz2
Content-length: 472
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93973
Bug ID: 93973
Summary: Wrong constexpr copy/move assignment operator allowed
on non-literal type
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: david.alvarez at bsc dot es
Target Milestone: ---
>From gcc-bugs-return-671801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 19:10:11 2020
Return-Path: <gcc-bugs-return-671801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121231 invoked by alias); 28 Feb 2020 19:10: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 121156 invoked by uid 48); 28 Feb 2020 19:10:05 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84490] [8/9/10 regression] 436.cactusADM regressed by 6-8% percent with -Ofast on Zen and Haswell, compared to gcc 7.2
Date: Fri, 28 Feb 2020 19:10: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: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm 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-84490-4-YiTVZzCmoa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84490-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84490-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03383.txt.bz2
Content-length: 1041
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84490
--- Comment #13 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #12)
> Wonder if we can have an update on this?
TL;DR: there still seems to be a regression, but smaller and difficult to pin
down.
The benchmark often goes up and down a bit:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=134.100.0&plot.1=37.100.0&plot.2=69.100.0&plot.3=248.100.0&plot.4=27.100.0&
Nevertheless, I recently got the following numbers at Ofast and
generic march (times, so lower is better):
| GCC 7.5 | 100.00% |
| GCC 8.3 | 102.07% |
| GCC 9.2 | 104.15% |
| trunk 17 Feb | 109.33% |
| trunk 24 Feb | 104.66% |
Zen2 based CPU
| GCC 7.5 | 100.00% |
| GCC 8.3 | 100.00% |
| GCC 9.2 | 110.06% |
| trunk 17 Feb | 111.32% |
| trunk 24 Feb | 105.66% |
OTOH, on zen2 GCC 9 and trunk are 23% better at -Ofast and native over GCC 8 or
7 (but those do not know znver2 and I did not try forcing 256bit vectors).
>From gcc-bugs-return-671802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 19:20:18 2020
Return-Path: <gcc-bugs-return-671802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6093 invoked by alias); 28 Feb 2020 19: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 6022 invoked by uid 48); 28 Feb 2020 19:20:14 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] New: [9/10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu
Date: Fri, 28 Feb 2020 19:20: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: 9.2.1
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
Message-ID: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03384.txt.bz2
Content-length: 1871
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
Bug ID: 93974
Summary: [9/10 Regression] ICE in decompose_normal_address, at
rtlanal.c:6403 on powerpc64le-linux-gnu
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at debian dot org
Target Milestone: ---
seen with trunk 20200228, on powerpc64le-linux-gnu, hardening flags and -fPIE
turned on by default.
$ cat lpe-extrude.ii
class a {
double b[2];
public:
a();
};
class c {
public:
typedef a d;
d m_fn1() {
a e;
return e;
}
};
template <typename f> void operator+(f, typename f::d);
void g() {
c connector;
for (;;) {
c cut;
a h = cut.m_fn1();
connector + h;
}
}
$ g++ -c -O3 lpe-extrude.ii
during RTL pass: reload
lpe-extrude.ii: In function ‘void g()’:
lpe-extrude.ii:23:1: internal compiler error: in decompose_normal_address, at
rtlanal.c:6384
23 | }
| ^
0x109c511f decompose_normal_address
../../src/gcc/rtlanal.c:6384
0x109c511f decompose_address(address_info*, rtx_def**, machine_mode, unsigned
char, rtx_code)
../../src/gcc/rtlanal.c:6461
0x1084499f process_address_1
../../src/gcc/lra-constraints.c:3363
0x10846d1b process_address
../../src/gcc/lra-constraints.c:3637
0x10846d1b curr_insn_transform
../../src/gcc/lra-constraints.c:3952
0x1084c7af lra_constraints(bool)
../../src/gcc/lra-constraints.c:5025
0x1083537f lra(_IO_FILE*)
../../src/gcc/lra.c:2437
0x107da43b do_reload
../../src/gcc/ira.c:5523
0x107da43b execute
../../src/gcc/ira.c:5709
Please submit a full bug report,
with preprocessed source if appropriate.
>From gcc-bugs-return-671803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 19:22:02 2020
Return-Path: <gcc-bugs-return-671803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21854 invoked by alias); 28 Feb 2020 19:22: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 21728 invoked by uid 48); 28 Feb 2020 19:21:57 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87560] ICE in curr_insn_transform, at lra-constraints.c:3892
Date: Fri, 28 Feb 2020 19:22: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.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt 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-87560-4-T6drth1WoZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87560-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87560-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03385.txt.bz2
Content-length: 212
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87560
--- Comment #6 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
OK, looks like the gimple has changed so we don't see the opportunity anymore
in GCC 10.
>From gcc-bugs-return-671804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 19:24:47 2020
Return-Path: <gcc-bugs-return-671804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26226 invoked by alias); 28 Feb 2020 19:24: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 26198 invoked by uid 48); 28 Feb 2020 19:24:43 -0000
From: "david.alvarez at bsc dot es" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93975] New: Wrong constexpr copy/move assignment operator allowed on non-literal type
Date: Fri, 28 Feb 2020 19:24: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: david.alvarez at bsc dot es
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-93975-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03386.txt.bz2
Content-length: 2898
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93975
Bug ID: 93975
Summary: Wrong constexpr copy/move assignment operator allowed
on non-literal type
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: david.alvarez at bsc dot es
Target Milestone: ---
Created attachment 47932
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47932&action=edit
Reproducer
Hi,
Note: I sent #93973 with the same title by mistake, sorry.
I am attaching file "bug.cc", that contains a testcase for the issue I'm
describing. GCC compiles the code correctly, but it _should not_ under
-std=c++17 and beyond. Clang-9 correctly detects the error and displays:
$ clang++ -std=c++17 -c bug.cc
bug.cc:9:3: error: defaulted definition of copy assignment operator is not
constexpr
constexpr Test& operator=(const Test &) = default;
^
1 error generated.
The issue is that the constexpr operator= is illegal in that context, and it is
not detected by GCC correctly. GCC 5.3 outputted the following error:
<source>:11:19: error: explicitly defaulted function 'constexpr Test&
Test::operator=(const Test&)' cannot be declared as constexpr because the
implicit declaration is not constexpr:
constexpr Test& operator=(const Test &) = default;
^
Which is correct. In the C++ 2017 standard, section 15.8.2 paragraph 10, it
says:
A copy/move assignment operator for a class X that is defaulted and not defined
as deleted is implicitly defined when it is odr-used (6.2) (e.g., when it is
selected by overload resolution to assign to an object of its class type) or
when it is explicitly defaulted after its first declaration. The
implicitly-defined copy/move assignment operator is constexpr if
(10.1) — X is a literal type, and
(10.2) — the assignment operator selected to copy/move each direct base class
subobject is a constexpr function, and
(10.3) — for each non-static data member of X that is of class type (or array
thereof), the assignment operator selected to copy/move that member is a
constexpr function.
The class Test in the example is not a literal type (and can be checked through
std::is_literal_type<Test>) because it has no constexpr constructors. GCC
detects the non-literality correctly, but fails to then mark the implicit
copy/move assginment operator as non-constexpr.
The issue was introduced in GCC 5.4 by patch: r236405 (git id
7c7bf2f86e5b9de752530a778909c11a596ed40a), which implemented support for
constexpr copy/move constructors but did not check for the restrictions defined
in the standard (but it does include a comment there as well with all the
conditions to check...).
Thanks!
>From gcc-bugs-return-671805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 19:33:37 2020
Return-Path: <gcc-bugs-return-671805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34838 invoked by alias); 28 Feb 2020 19:33: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 34808 invoked by uid 48); 28 Feb 2020 19:33:33 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93751] -g1 does not behave per manual
Date: Fri, 28 Feb 2020 19:33: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: documentation, patch
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: keywords bug_file_loc cc
Message-ID: <bug-93751-4-Su0kORtFpa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03387.txt.bz2
Content-length: 1172
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93751
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
URL| |https://gcc.gnu.org/ml/gcc-
| |patches/2020-02/msg00889.ht
| |ml
CC| |egallager at gcc dot gnu.org
--- Comment #16 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Alexey Neyman from comment #14)
> Created attachment 47930 [details]
> Patch, v3
>
> In gcc-patches, there have been three votes for generating external
> variables' DIEs without an additional option. Updated the patch to do that.
>
> I'd be happy to see either of v2 or v3 of the patch picked up.
This is the only discussion of the patch on gcc-patches I can find:
https://gcc.gnu.org/ml/gcc-patches/2020-02/msg00889.html
Could you point me to where the votes on other versions of it took place?
>From gcc-bugs-return-671806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 19:35:25 2020
Return-Path: <gcc-bugs-return-671806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38065 invoked by alias); 28 Feb 2020 19:35: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 37998 invoked by uid 48); 28 Feb 2020 19:35:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93975] Wrong constexpr copy/move assignment operator allowed on non-literal type
Date: Fri, 28 Feb 2020 19: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: 9.2.1
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-93975-4-K4LBIgmX3S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93975-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93975-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03388.txt.bz2
Content-length: 181
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93975
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
*** Bug 93973 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-671807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 19:35:26 2020
Return-Path: <gcc-bugs-return-671807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38070 invoked by alias); 28 Feb 2020 19:35: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 37978 invoked by uid 48); 28 Feb 2020 19:35:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93973] Wrong constexpr copy/move assignment operator allowed on non-literal type
Date: Fri, 28 Feb 2020 19: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: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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-93973-4-fSjbj0790x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93973-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93973-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03389.txt.bz2
Content-length: 560
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93973
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |jakub at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
.
*** This bug has been marked as a duplicate of bug 93975 ***
>From gcc-bugs-return-671808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 19:36:11 2020
Return-Path: <gcc-bugs-return-671808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39590 invoked by alias); 28 Feb 2020 19: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 39560 invoked by uid 48); 28 Feb 2020 19:36:06 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93751] -g1 does not behave per manual
Date: Fri, 28 Feb 2020 19:36: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: documentation, patch
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-93751-4-cOyFrs6v21@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03390.txt.bz2
Content-length: 803
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93751
--- Comment #17 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #16)
> (In reply to Alexey Neyman from comment #14)
> > Created attachment 47930 [details]
> > Patch, v3
> >
> > In gcc-patches, there have been three votes for generating external
> > variables' DIEs without an additional option. Updated the patch to do that.
> >
> > I'd be happy to see either of v2 or v3 of the patch picked up.
>
> This is the only discussion of the patch on gcc-patches I can find:
> https://gcc.gnu.org/ml/gcc-patches/2020-02/msg00889.html
> Could you point me to where the votes on other versions of it took place?
Wait never mind I found it:
https://gcc.gnu.org/ml/gcc-patches/2020-02/msg01129.html
>From gcc-bugs-return-671809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 19:50:29 2020
Return-Path: <gcc-bugs-return-671809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64180 invoked by alias); 28 Feb 2020 19:50: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 64102 invoked by uid 48); 28 Feb 2020 19:50:23 -0000
From: "spop at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92692] Saving off the callee saved register between ldxr/stxr (caused by shrink wrapping improvements)
Date: Fri, 28 Feb 2020 19: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: wrong-code
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: spop at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: wilco at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92692-4-7nS7uwJFLd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92692-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92692-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03391.txt.bz2
Content-length: 353
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92692
--- Comment #23 from Sebastian Pop <spop at gcc dot gnu.org> ---
> I don't see anything like that on the gcc-9 branch - are you sure you don't have an outstanding change somehow?
You are right, a part of the -moutline-atomics patch that I am working on
backporting to branch 9 added that change.
>From gcc-bugs-return-671810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 20:05:59 2020
Return-Path: <gcc-bugs-return-671810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124826 invoked by alias); 28 Feb 2020 20:05: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 124502 invoked by uid 48); 28 Feb 2020 20:05:55 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53479] Control flow analysis reports warnings in switch over an enum class even if all possible values have their branches
Date: Fri, 28 Feb 2020 20: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: 4.6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: minor
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:
Message-ID: <bug-53479-4-Mq9sTa3gDz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53479-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53479-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03392.txt.bz2
Content-length: 516
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53479
--- Comment #23 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #8)
>
> Perhaps I should add an entry to the FAQ summarizing the above (anyone feel
> free to beat me to it...)
The "Commonly-reported Non-bugs" page would be another good place for it
besides the FAQ, seeing as this keeps coming up:
https://gcc.gnu.org/bugs/#nonbugs
(searching for "enum" finds nothing on that page so far)
>From gcc-bugs-return-671811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 20:07:20 2020
Return-Path: <gcc-bugs-return-671811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20950 invoked by alias); 28 Feb 2020 20:07: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 20851 invoked by uid 48); 28 Feb 2020 20:07:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] [9/10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Fri, 28 Feb 2020 20:07: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.1
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: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-93974-4-BO0WlpkhOZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03393.txt.bz2
Content-length: 1132
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-28
CC| |jakub at gcc dot gnu.org
Target Milestone|--- |9.3
Summary|[9/10 Regression] ICE in |[9/10 Regression] ICE in
|decompose_normal_address, |decompose_normal_address,
|at rtlanal.c:6403 on |at rtlanal.c:6403 on
|powerpc64le-linux-gnu |powerpc64le-linux-gnu since
| |r10-6762
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r10-6762-ge6f24f824beb8ba6805702e287bbd6153b472488 on the trunk
(which makes me wonder if it doesn't ICE even in 8.x).
>From gcc-bugs-return-671812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 20:08:35 2020
Return-Path: <gcc-bugs-return-671812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25577 invoked by alias); 28 Feb 2020 20: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 25534 invoked by uid 48); 28 Feb 2020 20:08:30 -0000
From: "drikosev at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92785] expressions passed as real arguments to a dummy polymorphic argument fail with indexing error
Date: Fri, 28 Feb 2020 20:08: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: drikosev at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92785-4-MF7WUgXhVn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92785-4@http.gcc.gnu.org/bugzilla/>
References: <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: 2020-02/txt/msg03394.txt.bz2
Content-length: 420
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92785
--- Comment #5 from Ev Drikos <drikosev at gmail dot com> ---
(In reply to Paul Thomas from comment #4)
> Committed as revision r10-6924-g7485ace81de9ec9dd5c87edf67e359d31ce35a20
>
> Paul
Hello Mr. P. Thomas,
With fortran-8.2, the test case prints 'FAILED' but exits with return code 0.
So,
a regression in the future might go unnoticed.
Regards,
Ev. Drikos
>From gcc-bugs-return-671813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 20:16:28 2020
Return-Path: <gcc-bugs-return-671813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34334 invoked by alias); 28 Feb 2020 20: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 34233 invoked by uid 48); 28 Feb 2020 20:16:23 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] [8/9/10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Fri, 28 Feb 2020 20:16: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.1
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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-93974-4-nCJKztPmXS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03395.txt.bz2
Content-length: 788
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|9.3 |8.4
Summary|[9/10 Regression] ICE in |[8/9/10 Regression] ICE in
|decompose_normal_address, |decompose_normal_address,
|at rtlanal.c:6403 on |at rtlanal.c:6403 on
|powerpc64le-linux-gnu since |powerpc64le-linux-gnu since
|r10-6762 |r10-6762
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Indeed, current 8 branch ICEs too, which makes this an 8.4 release blocker.
>From gcc-bugs-return-671814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 20:19:27 2020
Return-Path: <gcc-bugs-return-671814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44757 invoked by alias); 28 Feb 2020 20:19: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 44680 invoked by uid 48); 28 Feb 2020 20:19:23 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93658] [9/10 Regression] infinite loop building ghostscript and icu with -O3 on powerpc64le-linux-gnu
Date: Fri, 28 Feb 2020 20:19: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: ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93658-4-d4e8AuLDMm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03396.txt.bz2
Content-length: 136
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93658
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Caused PR93974.
>From gcc-bugs-return-671815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 20:20:25 2020
Return-Path: <gcc-bugs-return-671815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53455 invoked by alias); 28 Feb 2020 20:20: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 51478 invoked by uid 48); 28 Feb 2020 20:20:21 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93898] [9/10 Regression] internal compiler error: in output_constructor_regular_field
Date: Fri, 28 Feb 2020 20: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-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-93898-4-WNRCtkSLv5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93898-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93898-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03397.txt.bz2
Content-length: 171
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93898
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Actually most likely this is a dup of bug 90432.
>From gcc-bugs-return-671816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 20:26:57 2020
Return-Path: <gcc-bugs-return-671816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64565 invoked by alias); 28 Feb 2020 20:26: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 64528 invoked by uid 48); 28 Feb 2020 20:26:53 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93971] C++ containers considered to alias declared objects of incompatible types
Date: Fri, 28 Feb 2020 20:26: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: alias, missed-optimization
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-93971-4-bdKvlaL80g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03398.txt.bz2
Content-length: 168
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93971
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
If x is NaN, you cannot simplify x!=x to false.
>From gcc-bugs-return-671817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 20:51:40 2020
Return-Path: <gcc-bugs-return-671817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125671 invoked by alias); 28 Feb 2020 20: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 125607 invoked by uid 55); 28 Feb 2020 20:51:34 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Fri, 28 Feb 2020 20:51: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93871-4-lq83jkcS3a@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03399.txt.bz2
Content-length: 2188
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #34 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Fri, Feb 28, 2020 at 09:30:25AM +0000, thenlich at gcc dot gnu.org wrote:
>
> Going back one step, I wonder if it would be good enough
> to perform a correctly rounded conversion from degrees to
> radians, and just use sin() as is.
>
> ...
> f = sgn * sin(deg2rad(arg))
> end function fcn
>
> ! Compute correctly rounded value of x * pi / 180 for x = 0 ... 90
> function deg2rad(x) result(y)
> real(sp) y
> real(sp), intent(in) :: x
> real(sp), parameter :: a = atan(1._4) / 45
> real(sp), parameter :: b = atan(1._16) / 45 - a
> y = a * x + b * x
> end function deg2rad
>
> (The exact values of a and b still need some work)
>
The only way I know of that will get the correctly rounded
value without punting to a higher precision is to decompose
the scaling and argumet to high and low precision, and then
do the multiplcation.
shi = high_bits_of(pi/180) ! # of bits = half of precision
slo = pi/180 - shi
xhi = high_bits_of(arg)
xlo = arg - xhi
You then do
value = slo * xlo + slo * xhi + shi * xlo + shi * xhi
The last term is exact, and the summation is accumulated
from smallest terms to largest (ie., you get correct
rounding).
For float precision (and little endian), I use
static const float
deg2rad(float ax)
{
/* Split pi/180 into 12 high bits and 24 low bits. */
static const float pihi = 1.74560547e-02f, pilo =-2.76216747e-06f;
float lo, hi;
/* Need union to allow the clearly of low bits. */
union {
unsigned int u;
float e;
} v;
v.e = ax;
v.u = (v.u >> 12) << 12; /* 12 high bits. */
hi = v.e;
lo = ax - hi; /* low part.
return (lo * pilo + lo * pihi + hi * pilo + hi * pihi);
}
Even this appears to have some irregularities as my exhaustive
test in the interval [1.e-8,1) with direct call to sinf() yields
count: 223622026
ulp > 1.0: 125
ulp > 1.5: 0
ulp > 1.6: 0
ulp > 1.7: 0
max_ulp: 1.321531
x at max: 0.447627
>From gcc-bugs-return-671818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:09:09 2020
Return-Path: <gcc-bugs-return-671818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3500 invoked by alias); 28 Feb 2020 22:09: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 3460 invoked by uid 48); 28 Feb 2020 22:09:05 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93926] [10 Regression] ICE: verify_cgraph_node failed (error: malloc attribute should be used for a function that returns a pointer)
Date: Fri, 28 Feb 2020 22:09: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: ice-checking, ice-on-invalid-code, patch
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:
Message-ID: <bug-93926-4-JKYrbi0Y7h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03400.txt.bz2
Content-length: 208
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93926
--- Comment #6 from Jeffrey A. Law <law at redhat dot com> ---
I wouldn't be surprised if the biggest need for permissiveness is for configure
tests :(
>From gcc-bugs-return-671819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:13:37 2020
Return-Path: <gcc-bugs-return-671819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8930 invoked by alias); 28 Feb 2020 22: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 8855 invoked by uid 48); 28 Feb 2020 22:13:34 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53479] Control flow analysis reports warnings in switch over an enum class even if all possible values have their branches
Date: Fri, 28 Feb 2020 22: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: 4.6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: minor
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-53479-4-uxTxTSUiKR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53479-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53479-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03401.txt.bz2
Content-length: 185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53479
--- Comment #24 from Jonathan Wakely <redi at gcc dot gnu.org> ---
It's at https://gcc.gnu.org/wiki/VerboseDiagnostics#enum_switch
>From gcc-bugs-return-671820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:14:03 2020
Return-Path: <gcc-bugs-return-671820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9721 invoked by alias); 28 Feb 2020 22:14: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 9643 invoked by uid 48); 28 Feb 2020 22:13:59 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93823] [10 Regression] ICE: in find_more_scalar_values_for_callers_subset, at ipa-cp.c:4709 due to -fipa-cp
Date: Fri, 28 Feb 2020 22: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93823-4-xpNuL8NEaX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93823-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03402.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93823
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #4 from Jeffrey A. Law <law at redhat dot com> ---
Per c#2
>From gcc-bugs-return-671821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:14:06 2020
Return-Path: <gcc-bugs-return-671821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9995 invoked by alias); 28 Feb 2020 22: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 9666 invoked by uid 48); 28 Feb 2020 22:14:00 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93968] -Wswitch-default on exhaustive enum class gives warning about missing default case
Date: Fri, 28 Feb 2020 22: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: unknown
X-Bugzilla-Keywords:
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:
Message-ID: <bug-93968-4-jqtdmr9Njl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93968-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03403.txt.bz2
Content-length: 184
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93968
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
And see https://gcc.gnu.org/wiki/VerboseDiagnostics#enum_switch
>From gcc-bugs-return-671822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:14:10 2020
Return-Path: <gcc-bugs-return-671822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10397 invoked by alias); 28 Feb 2020 22:14: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 9724 invoked by uid 48); 28 Feb 2020 22:14:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93967] switch on exhaustive enum gives control reaches end of non-void function
Date: Fri, 28 Feb 2020 22: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: unknown
X-Bugzilla-Keywords:
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:
Message-ID: <bug-93967-4-XdLyw9mIQa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93967-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03404.txt.bz2
Content-length: 184
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93967
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
And see https://gcc.gnu.org/wiki/VerboseDiagnostics#enum_switch
>From gcc-bugs-return-671823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:18:55 2020
Return-Path: <gcc-bugs-return-671823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19845 invoked by alias); 28 Feb 2020 22:18: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 15937 invoked by uid 48); 28 Feb 2020 22:18:50 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93823] [10 Regression] ICE: in find_more_scalar_values_for_callers_subset, at ipa-cp.c:4709 due to -fipa-cp
Date: Fri, 28 Feb 2020 22: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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-93823-4-d5UCb2y9OR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93823-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03405.txt.bz2
Content-length: 529
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93823
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #5 from Jeffrey A. Law <law at redhat dot com> ---
Per c#2. Actually change the status this time :-)
*** This bug has been marked as a duplicate of bug 93707 ***
>From gcc-bugs-return-671824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:18:55 2020
Return-Path: <gcc-bugs-return-671824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19883 invoked by alias); 28 Feb 2020 22:18: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 16691 invoked by uid 48); 28 Feb 2020 22:18:51 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93707] ICE in perlbench from SPEC2017
Date: Fri, 28 Feb 2020 22: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: fxue at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93707-4-WjV5GQ3Bgu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93707-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93707-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03406.txt.bz2
Content-length: 434
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93707
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zsojka at seznam dot cz
--- Comment #6 from Jeffrey A. Law <law at redhat dot com> ---
*** Bug 93823 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-671825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:22:18 2020
Return-Path: <gcc-bugs-return-671825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22486 invoked by alias); 28 Feb 2020 22:22: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 22447 invoked by uid 48); 28 Feb 2020 22:22:14 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93976] New: Implement P2082R1, Fixing CTAD for aggregates
Date: Fri, 28 Feb 2020 22:22: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 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 blocked target_milestone attachments.created
Message-ID: <bug-93976-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03407.txt.bz2
Content-length: 790
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93976
Bug ID: 93976
Summary: Implement P2082R1, Fixing CTAD for aggregates
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jason at gcc dot gnu.org
Blocks: 88323
Target Milestone: ---
Created attachment 47933
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47933&action=edit
beginning of implementation
Making the example in the paper work requires too much surgery to reshape_init
for stage 4.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88323
[Bug 88323] implement C++20 language features.
>From gcc-bugs-return-671826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:36:43 2020
Return-Path: <gcc-bugs-return-671826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54792 invoked by alias); 28 Feb 2020 22:36: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 54750 invoked by uid 48); 28 Feb 2020 22:36:39 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] [8/9/10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Fri, 28 Feb 2020 22: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.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: bergner 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-93974-4-uI32l1um4X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03408.txt.bz2
Content-length: 459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |bergner at gcc dot gnu.org
--- Comment #3 from Peter Bergner <bergner at gcc dot gnu.org> ---
Looking.
>From gcc-bugs-return-671827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:40:53 2020
Return-Path: <gcc-bugs-return-671827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60775 invoked by alias); 28 Feb 2020 22:40: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 60767 invoked by uid 48); 28 Feb 2020 22:40:50 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93977] New: missing -Wrestrict with sprintf with same format as destination
Date: Fri, 28 Feb 2020 22:40: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-93977-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03409.txt.bz2
Content-length: 1621
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93977
Bug ID: 93977
Summary: missing -Wrestrict with sprintf with same format as
destination
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: ---
-Wrestrict correctly detects the overlap in g() below but misses the trivial
overlap in h():
$ cat t.c && gcc -O2 -S -Wall t.c
void f (void*);
void g (void)
{
char a[] = "%s abc";
__builtin_sprintf (a, "%s abc", a); // -Wrestrict (good)
f (a);
}
void h (void)
{
char a[] = "%s abc";
__builtin_sprintf (a, a, a); // missing warning
f (a);
}
t.c: In function ‘g’:
t.c:6:29: warning: ‘ abc’ directive writing 4 bytes into a region of size 1
[-Wformat-overflow=]
6 | __builtin_sprintf (a, "%s abc", a); // -Wrestrict (good)
| ~^~~
t.c:6:3: note: ‘__builtin_sprintf’ output 11 bytes into a destination of size 7
6 | __builtin_sprintf (a, "%s abc", a); // -Wrestrict (good)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t.c:6:3: warning: ‘__builtin_sprintf’ argument 3 overlaps destination object
‘a’ [-Wrestrict]
t.c:5:8: note: destination object referenced by ‘restrict’-qualified argument 1
was declared here
5 | char a[] = "%s abc";
| ^
>From gcc-bugs-return-671828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:49:14 2020
Return-Path: <gcc-bugs-return-671828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67004 invoked by alias); 28 Feb 2020 22:49: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 66917 invoked by uid 48); 28 Feb 2020 22:49:09 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/80635] [8/9/10 regression] std::optional and bogus -Wmaybe-uninitialized warning
Date: Fri, 28 Feb 2020 22: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: 8.2.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80635-4-btwDWWj3DM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80635-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80635-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03410.txt.bz2
Content-length: 503
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80635
--- Comment #45 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #44)
> I suspect in the context where SRA creates the V_C_E we don't have enough
> information to know that the range of the input object is constrained
> enough. We base the decision solely on the types.
We SRA a bool field into a QItype variable and then think we need a VCE to get
back to bool. Could the SRA variable have type bool?
>From gcc-bugs-return-671829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:56:55 2020
Return-Path: <gcc-bugs-return-671829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75918 invoked by alias); 28 Feb 2020 22:56: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 75857 invoked by uid 48); 28 Feb 2020 22:56:50 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91890] [10 Regression] -Warray-bounds warning testing glibc not suppressed by pragma
Date: Fri, 28 Feb 2020 22: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-91890-4-WC9ztfjkhH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91890-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91890-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03411.txt.bz2
Content-length: 1700
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91890
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at redhat dot com,
| |law at redhat dot com
--- Comment #6 from Jeffrey A. Law <law at redhat dot com> ---
This really looks like a line mapping issue to me. I think Manu is totally
offbase.
At the time of the diagnostic we have 3 items in
context->classification_history. One for each of the ignored diagnostics and
one for the pop.
(gdb) p context->classification_history[2]
$32 = {location = 295618, option = 0, kind = DK_POP}
(gdb) p context->classification_history[1]
$33 = {location = 287426, option = 419, kind = DK_IGNORED}
(gdb) p context->classification_history[0]
$34 = {location = 283330, option = 669, kind = DK_IGNORED}
Now the diagnostic location looks like:
(gdb) p location
$35 = 2147483652
Now I can actually map that to a normal location by putting a breakpoint in
linemap_compare_locations :-) It happens to correspond to location 267552.
So as far as the compiler is concerned we're emitting a diagnostic for a
location which is *before* all the pragmas AFAICT. So it's no great surprise
that the pragmas have no effect on the diagnostic.
We initially set the location of the strcat call to 291583 which would work
beautifully. We then change the location via lower_stmt->gimple_set_block to a
rather inconvenient value that's outside the scope of the pragmas and thus the
pragmas have no effect.
>From gcc-bugs-return-671830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 22:59:47 2020
Return-Path: <gcc-bugs-return-671830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89692 invoked by alias); 28 Feb 2020 22:59: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 89645 invoked by uid 55); 28 Feb 2020 22:59:43 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93972] ranges::lexicographical_compare gives wrong answer for signed integers
Date: Fri, 28 Feb 2020 22:59: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: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ppalka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93972-4-P0RzOZBJqZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93972-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93972-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03412.txt.bz2
Content-length: 1271
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93972
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:
https://gcc.gnu.org/g:ce33801fe4c2272b31c64288b34c67a61529ce37
commit r10-6930-gce33801fe4c2272b31c64288b34c67a61529ce37
Author: Patrick Palka <ppalka@redhat.com>
Date: Fri Feb 28 14:16:06 2020 -0500
libstdc++: Fix bogus use of memcmp in ranges::lexicographical_compare (PR
93972)
We were enabling the memcmp optimization in ranges::lexicographical_compare
for
signed integral types and for integral types wider than a byte. But memcmp
gives the wrong answer for arrays of such types. This patch fixes this
issue by
refining the condition that enables the memcmp optimization. It's now
consistent with the corresponding condition used in
std::lexicographical_compare.
libstdc++-v3/ChangeLog:
PR libstdc++/93972
* include/bits/ranges_algo.h
(__lexicographical_compare_fn::operator()):
Fix condition for when to use memcmp, making it consistent with the
corresponding condition used in std::lexicographical_compare.
* testsuite/25_algorithms/lexicographical_compare/93972.cc: New test.
>From gcc-bugs-return-671831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 23:01:26 2020
Return-Path: <gcc-bugs-return-671831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91259 invoked by alias); 28 Feb 2020 23:01: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 91197 invoked by uid 48); 28 Feb 2020 23:01:22 -0000
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93972] ranges::lexicographical_compare gives wrong answer for signed integers
Date: Fri, 28 Feb 2020 23:01: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ppalka at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ppalka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status resolution target_milestone
Message-ID: <bug-93972-4-cM8HGh0rJa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93972-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93972-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03413.txt.bz2
Content-length: 539
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93972
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.0
--- Comment #3 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 23:14:57 2020
Return-Path: <gcc-bugs-return-671832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111413 invoked by alias); 28 Feb 2020 23:14: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 111378 invoked by uid 48); 28 Feb 2020 23:14:53 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91890] [10 Regression] -Warray-bounds warning testing glibc not suppressed by pragma
Date: Fri, 28 Feb 2020 23: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91890-4-5gLu0Dg7mi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91890-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91890-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03414.txt.bz2
Content-length: 1097
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91890
--- Comment #7 from Jeffrey A. Law <law at redhat dot com> ---
Another tidbit. It looks like the sprintf warning will at times ignore the
passed in location. I'm not suggesting this is necessarily the right fix, but
if we make gimple-ssa-warn-restrict honor the passed in location per this
change, then the pragmas work perfectly in this case.
diff --git a/gcc/gimple-ssa-warn-restrict.c b/gcc/gimple-ssa-warn-restrict.c
index 2c582a670eb..1449492798a 100644
--- a/gcc/gimple-ssa-warn-restrict.c
+++ b/gcc/gimple-ssa-warn-restrict.c
@@ -1754,7 +1754,7 @@ maybe_diag_access_bounds (location_t loc, gimple *call,
tree func, int strict,
|| (ref.ref && TREE_NO_WARNING (ref.ref)))
return false;
- if (EXPR_HAS_LOCATION (ref.ptr))
+ if (loc == UNKNOWN_LOCATION && EXPR_HAS_LOCATION (ref.ptr))
loc = EXPR_LOCATION (ref.ptr);
loc = expansion_point_location_if_in_system_header (loc);
Martin, do you recall the rationale behind extracting the location out of
ref.ptr when we were already passed in a location?
>From gcc-bugs-return-671833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 23:22:21 2020
Return-Path: <gcc-bugs-return-671833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116157 invoked by alias); 28 Feb 2020 23: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 116104 invoked by uid 48); 28 Feb 2020 23:22:17 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91799] [10 regression] r273245 breaks test case gcc.target/powerpc/pr88233.c
Date: Fri, 28 Feb 2020 23:22: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: law at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-91799-4-xMO24iXTx3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03415.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91799
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #2 from Jeffrey A. Law <law at redhat dot com> ---
Segher? Are you going to look at this?
>From gcc-bugs-return-671834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Feb 28 23:24:01 2020
Return-Path: <gcc-bugs-return-671834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117555 invoked by alias); 28 Feb 2020 23:24: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 117464 invoked by uid 48); 28 Feb 2020 23:23:57 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91797] [10 regression] r273240 breaks test case gcc.target/powerpc/pr68805.c
Date: Fri, 28 Feb 2020 23:24: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: law at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-91797-4-r2kcHsqsed@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03416.txt.bz2
Content-length: 513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91797
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #3 from Jeffrey A. Law <law at redhat dot com> ---
Segher? If these aren't important and we're not going to try and fix, can we
at least downgrade to P2 so that they're not release blockers?
>From gcc-bugs-return-671835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 00:13:47 2020
Return-Path: <gcc-bugs-return-671835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19909 invoked by alias); 29 Feb 2020 00:13: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 19864 invoked by uid 48); 29 Feb 2020 00:13:43 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93971] std::string considered to alias declared objects of incompatible types
Date: Sat, 29 Feb 2020 00: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: alias, 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: short_desc
Message-ID: <bug-93971-4-SaUkVFhAeh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03417.txt.bz2
Content-length: 1903
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93971
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|C++ containers considered |std::string considered to
|to alias declared objects |alias declared objects of
|of incompatible types |incompatible types
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Doh! After replacing double with long the vector case is optimized as
expected.
#include <vector>
long x;
void f (std::vector<int> &v)
{
long t = x;
v[0] = 0;
if (t != x)
__builtin_abort ();
}
;; Function f (_Z1fRSt6vectorIiSaIiEE, funcdef_no=880, decl_uid=16170,
cgraph_uid=169, symbol_order=170)
f (struct vector & v)
{
int * _3;
<bb 2> [local count: 1073741824]:
_3 = v_2(D)->D.17243._M_impl.D.16553._M_start;
MEM[(value_type &)_3] = 0;
return;
}
What isn't optimized as I would expect is the same test case but with
std::string, even with __restrict added to std::string::_M_dataplus._M_p and to
the function argument (i.e., with 'void f (std::string & __restrict)'). I'm
guessing that's because of bug 49761 or some variant of it. In my testing, a
std::string passed by reference is basically considered as aliasing anything in
the program:
#include <string>
#include <vector>
void f (std::vector<int> &v)
{
std::string s = "12345";
int t = s[0];
v[0] = 0;
if (t != s[0]) // folded to false
__builtin_abort ();
}
void g (std::string &s)
{
std::vector<int> v { 1, 2, 3, 4, 5 };
int t = v[0];
s[0] = 0;
if (t != v[0]) // not folded (unless s is restrict-qualified)
__builtin_abort ();
}
>From gcc-bugs-return-671836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 00:16:16 2020
Return-Path: <gcc-bugs-return-671836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21569 invoked by alias); 29 Feb 2020 00:16: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 21481 invoked by uid 48); 29 Feb 2020 00:16:08 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93971] std::string considered to alias declared objects of incompatible types
Date: Sat, 29 Feb 2020 00:16: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: alias, missed-optimization
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-93971-4-jLZNUZJOsu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03418.txt.bz2
Content-length: 517
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93971
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> ---
std::string uses char so yes that is expected ...
try std::wstring and you will see it works.
>From gcc-bugs-return-671837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 00:16:17 2020
Return-Path: <gcc-bugs-return-671837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21700 invoked by alias); 29 Feb 2020 00:16: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 21504 invoked by uid 48); 29 Feb 2020 00:16:11 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49774] [meta-bug] restrict qualification aliasing issues
Date: Sat, 29 Feb 2020 00: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.7.0
X-Bugzilla-Keywords: alias, meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-49774-4-WXa4aAeo8G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49774-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49774-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03419.txt.bz2
Content-length: 500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49774
Bug 49774 depends on bug 93971, which changed state.
Bug 93971 Summary: std::string considered to alias declared objects of incompatible types
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93971
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
>From gcc-bugs-return-671838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 00:21:11 2020
Return-Path: <gcc-bugs-return-671838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33612 invoked by alias); 29 Feb 2020 00:21: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 33547 invoked by uid 48); 29 Feb 2020 00:21:07 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/80635] [8/9/10 regression] std::optional and bogus -Wmaybe-uninitialized warning
Date: Sat, 29 Feb 2020 00: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: 8.2.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80635-4-VNlF9aLKVG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80635-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80635-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03420.txt.bz2
Content-length: 1087
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80635
--- Comment #46 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Jason Merrill from comment #45)
>
> We SRA a bool field into a QItype variable and then think we need a VCE to
> get back to bool. Could the SRA variable have type bool?
A semi-wild guess, would the following make SRA not invent the V_C_E (and do
what you want)?
diff --git a/gcc/tree-sra.c b/gcc/tree-sra.c
index 5561ea6f655..c3551b469f1 100644
--- a/gcc/tree-sra.c
+++ b/gcc/tree-sra.c
@@ -2515,7 +2515,7 @@ analyze_access_subtree (struct access *root, struct
access *parent,
/* Always create access replacements that cover the whole access.
For integral types this means the precision has to match.
Avoid assumptions based on the integral type kind, too. */
- if (INTEGRAL_TYPE_P (root->type)
+ if (false && INTEGRAL_TYPE_P (root->type)
&& (TREE_CODE (root->type) != INTEGER_TYPE
|| TYPE_PRECISION (root->type) != root->size)
/* But leave bitfield accesses alone. */
>From gcc-bugs-return-671839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 00:34:12 2020
Return-Path: <gcc-bugs-return-671839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41803 invoked by alias); 29 Feb 2020 00:34: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 41731 invoked by uid 48); 29 Feb 2020 00:34:08 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93971] std::string considered to alias declared objects of incompatible types
Date: Sat, 29 Feb 2020 00: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: alias, 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: bug_status resolution
Message-ID: <bug-93971-4-TnbW7HrAqu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03421.txt.bz2
Content-length: 762
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93971
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|WONTFIX |---
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
By definition, std::string (like most other C++ containers) doesn't alias
anything outside the storage it manages. It should be possible to express that
constraint somehow (e.g., via the restrict keyword or maybe an attribute), and
improve code generation that way. How about a little less arrogance and
viewing this report in that light?
>From gcc-bugs-return-671840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 00:34:13 2020
Return-Path: <gcc-bugs-return-671840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41914 invoked by alias); 29 Feb 2020 00:34: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 41748 invoked by uid 48); 29 Feb 2020 00:34:09 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49774] [meta-bug] restrict qualification aliasing issues
Date: Sat, 29 Feb 2020 00:34: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.7.0
X-Bugzilla-Keywords: alias, meta-bug
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-49774-4-6Xp7kYciCr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49774-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49774-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03422.txt.bz2
Content-length: 499
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49774
Bug 49774 depends on bug 93971, which changed state.
Bug 93971 Summary: std::string considered to alias declared objects of incompatible types
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93971
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|WONTFIX |---
>From gcc-bugs-return-671841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 00:45:49 2020
Return-Path: <gcc-bugs-return-671841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48555 invoked by alias); 29 Feb 2020 00:45: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 48264 invoked by uid 48); 29 Feb 2020 00:45:31 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/60712] "restrict" qualifier ignored on local variable or after inlining
Date: Sat, 29 Feb 2020 00: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: 4.8.2
X-Bugzilla-Keywords: 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: keywords cf_reconfirmed_on cc cf_known_to_fail
Message-ID: <bug-60712-4-55WVSuxqAC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03423.txt.bz2
Content-length: 2514
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60712
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Last reconfirmed|2014-03-31 00:00:00 |2020-2-28
CC| |msebor at gcc dot gnu.org
Known to fail| |10.0, 4.8.5, 4.9.4, 5.4.0,
| |6.4.0, 7.3.0, 8.3.0, 9.1.0
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
No change in GCC 10:
$ cat pr60712.c && gcc -O3 -S -Wall -fdump-tree-optimized=/dev/stdout pr60712.c
void sum(int *restrict a, int *restrict b) {
*a = 0;
for (int i=0; i<100; i++)
*a += *b;
}
int *global_a, *global_b;
void bug_when_inline() {
sum(global_a, global_b);
}
void bug_when_local_variable() {
int* restrict a = global_a;
int* restrict b = global_b;
*a = 0;
for (int i=0; i<100; i++)
*a += *b;
}
;; Function sum (sum, funcdef_no=0, decl_uid=1931, cgraph_uid=1,
symbol_order=0)
sum (int * restrict a, int * restrict b)
{
int _2;
int _13;
<bb 2> [local count: 10737416]:
_2 = *b_9(D);
_13 = _2 * 100;
*a_7(D) = _13;
return;
}
;; Function bug_when_inline (bug_when_inline, funcdef_no=1, decl_uid=1939,
cgraph_uid=2, symbol_order=3)
bug_when_inline ()
{
int * global_b.0_1;
int * global_a.1_2;
int _5;
int _12;
<bb 2> [local count: 10737416]:
global_b.0_1 = global_b;
global_a.1_2 = global_a;
_5 = *global_b.0_1;
_12 = _5 * 100;
*global_a.1_2 = _12;
return;
}
;; Function bug_when_local_variable (bug_when_local_variable, funcdef_no=2,
decl_uid=1941, cgraph_uid=3, symbol_order=4)
Removing basic block 5
bug_when_local_variable ()
{
int * restrict b;
int * restrict a;
int _2;
int _3;
unsigned int ivtmp_4;
unsigned int ivtmp_5;
int prephitmp_15;
<bb 2> [local count: 10737416]:
a_7 = global_a;
b_8 = global_b;
*a_7 = 0;
<bb 3> [local count: 1063004409]:
# prephitmp_15 = PHI <0(2), _3(3)>
# ivtmp_5 = PHI <100(2), ivtmp_4(3)>
_2 = *b_8;
_3 = _2 + prephitmp_15;
*a_7 = _3;
ivtmp_4 = ivtmp_5 + 4294967295;
if (ivtmp_4 != 0)
goto <bb 3>; [98.99%]
else
goto <bb 4>; [1.01%]
<bb 4> [local count: 10737416]:
return;
}
>From gcc-bugs-return-671842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 00:54:29 2020
Return-Path: <gcc-bugs-return-671842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120032 invoked by alias); 29 Feb 2020 00:54: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 115939 invoked by uid 48); 29 Feb 2020 00:54:25 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/41898] GCC ignores restrict on array
Date: Sat, 29 Feb 2020 00: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: 4.5.0
X-Bugzilla-Keywords: 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: cf_reconfirmed_on cc cf_known_to_fail
Message-ID: <bug-41898-4-ad4awwKF6B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-41898-4@http.gcc.gnu.org/bugzilla/>
References: <bug-41898-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03424.txt.bz2
Content-length: 1629
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41898
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2009-11-01 20:59:25 |2020-2-28
CC| |msebor at gcc dot gnu.org
Known to fail| |10.0, 4.5.3, 4.6.4, 4.7.4,
| |4.8.4, 4.9.4, 5.5.0, 6.4.0,
| |7.2.0, 8.0, 9.2.0
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
The test case in comment #0 is optimized, presumably thanks to r255093. The
test case in comment #2 is also optimized, but the test case in comment #1 is
still not. I assume this bug is still open because of that, so reconfirming.
$ cat pr41898.c && gcc -O2 -S -Wall -fdump-tree-optimized=/dev/stdout pr41898.c
int * __restrict__ a[1];
int * __restrict__ b[1];
extern void link_error (void);
int main()
{
a[0][0] = 0;
b[0][0] = 1;
if (a[0][0] != 0)
link_error ();
return 0;
}
;; Function main (main, funcdef_no=0, decl_uid=1933, cgraph_uid=1,
symbol_order=2) (executed once)
Removing basic block 5
main ()
{
int * _1;
int * _2;
int _3;
<bb 2> [local count: 1073741824]:
_1 = a[0];
*_1 = 0;
_2 = b[0];
*_2 = 1;
_3 = *_1;
if (_3 != 0)
goto <bb 3>; [33.00%]
else
goto <bb 4>; [67.00%]
<bb 3> [local count: 354334800]:
link_error ();
<bb 4> [local count: 1073741824]:
return 0;
}
>From gcc-bugs-return-671843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 01:45:53 2020
Return-Path: <gcc-bugs-return-671843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29749 invoked by alias); 29 Feb 2020 01:45: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 29686 invoked by uid 48); 29 Feb 2020 01:45:49 -0000
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93978] New: A snippet using views::join fails to compile with -O1, but succeeds with -O0
Date: Sat, 29 Feb 2020 01:45: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ppalka 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-93978-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03425.txt.bz2
Content-length: 5669
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93978
Bug ID: 93978
Summary: A snippet using views::join fails to compile with -O1,
but succeeds with -O0
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: ppalka at gcc dot gnu.org
Target Milestone: ---
$ cat join.cc
#include <ranges>
#include <vector>
namespace ranges = std::ranges;
namespace views = std::views;
void
test()
{
std::vector<std::string> x = {""};
auto i = std::counted_iterator(x.begin(), 1);
auto r = ranges::subrange{i, std::default_sentinel};
auto v = r | views::join;
}
$ g++ -std=c++2a -O0 join.cc
$ g++ -std=c++2a -O1 join.c
...
/home/patrick/code/gcc/libstdc++-v3/include/std/ranges:112:16: error: static
assertion failed
112 | static_assert(view<_Derived>);
| ^~~~~~~~~~~~~~
/home/patrick/code/gcc/libstdc++-v3/include/std/ranges:112:16: note:
constraints not satisfied
In file included from
/home/patrick/code/gcc/libstdc++-v3/include/std/string:54,
from
/home/patrick/code/gcc/libstdc++-v3/include/bits/locale_classes.h:40,
from
/home/patrick/code/gcc/libstdc++-v3/include/bits/ios_base.h:41,
from
/home/patrick/code/gcc/libstdc++-v3/include/std/streambuf:41,
from
/home/patrick/code/gcc/libstdc++-v3/include/bits/streambuf_iterator.h:35,
from
/home/patrick/code/gcc/libstdc++-v3/include/std/iterator:66,
from
/home/patrick/code/gcc/libstdc++-v3/include/std/ranges:44,
from join.cc:1:
/home/patrick/code/gcc/libstdc++-v3/include/bits/range_access.h:880:13:
required for the satisfaction of
‘range<std::ranges::join_view<std::ranges::subrange<std::counted_iterator<__gnu_cxx::__normal_iterator<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >*,
std::vector<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > > > >,
std::default_sentinel_t, std::ranges::subrange_kind::sized> > >’
/home/patrick/code/gcc/libstdc++-v3/include/bits/range_access.h:880:21: in
requirements with
‘std::ranges::join_view<std::ranges::subrange<std::counted_iterator<__gnu_cxx::__normal_iterator<std::__cxx11::basic_string<char>*,
std::vector<std::__cxx11::basic_string<char> > > >, std::default_sentinel_t,
std::ranges::subrange_kind::sized> >& __t’
/home/patrick/code/gcc/libstdc++-v3/include/bits/range_access.h:883:13: note:
the required expression ‘std::ranges::__cust::end(__t)’ is invalid
883 | ranges::end(__t);
| ~~~~~~~~~~~^~~~~
If we uncomment the code in constraint.cc that replays constraint satisfication
failures during diagnostics, it turns out that ranges::end(__t); is invalid
ultimately because
/home/patrick/code/gcc/libstdc++-v3/include/bits/range_access.h:437:26: error:
use of ‘constexpr auto std::ranges::join_view<_Vp>::end() [with _Vp =
std::ranges::subrange<std::counted_iterator<__gnu_cxx::__normal_iterator<std::__cxx11::basic_string<char>*,
std::vector<std::__cxx11::basic_string<char> > > >, std::default_sentinel_t,
std::ranges::subrange_kind::sized>]’ before deduction of ‘auto’
437 | { __decay_copy(__t.end()) }
| ~~~~~~~^~
Removing the static_assert(view<_Derived>); from view_interface::_M_derived()
fixes the compilation failure, but I'm not sure why.
>From gcc-bugs-return-671844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 02:07:30 2020
Return-Path: <gcc-bugs-return-671844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20612 invoked by alias); 29 Feb 2020 02:07: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 19519 invoked by uid 48); 29 Feb 2020 02:07:26 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91799] [10 regression] r273245 breaks test case gcc.target/powerpc/pr88233.c
Date: Sat, 29 Feb 2020 02:07: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: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91799-4-WPvM5J6A9Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03426.txt.bz2
Content-length: 1135
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91799
--- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> ---
commit 9b46c7543834c1a2004321dbf487fce29e015aae
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date: Wed Jul 10 21:58:36 2019 +0000
fix pr88233.c
diff --git a/gcc/testsuite/gcc.target/powerpc/pr88233.c
b/gcc/testsuite/gcc.targ
index c16235e..8e5f15b 100644
--- a/gcc/testsuite/gcc.target/powerpc/pr88233.c
+++ b/gcc/testsuite/gcc.target/powerpc/pr88233.c
@@ -1,5 +1,5 @@
/* { dg-do compile { target lp64 } } */
-/* { dg-options "-O2 -mcpu=power8" } */
+/* { dg-options "-O2 -mdejagnu-cpu=power8" } */
typedef struct { double a[2]; } A;
A
@@ -9,5 +9,6 @@ foo (const A *a)
}
/* { dg-final { scan-assembler-not {\mmtvsr} } } */
-/* { dg-final { scan-assembler-times {\mlxvd2x\M} 1 } } */
-/* { dg-final { scan-assembler-times {\mstxvd2x\M} 1 } } */
+/* { dg-final { scan-assembler-times {\mlxvd2x\M} 1 { target { be } } } } */
+/* { dg-final { scan-assembler-times {\mstxvd2x\M} 1 { target { be } } } } */
+/* { dg-final { scan-assembler-times {\mlfd\M} 2 { target { le } } } } */
>From gcc-bugs-return-671845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 02:08:19 2020
Return-Path: <gcc-bugs-return-671845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28916 invoked by alias); 29 Feb 2020 02:08: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 28729 invoked by uid 48); 29 Feb 2020 02:08:16 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91799] [10 regression] r273245 breaks test case gcc.target/powerpc/pr88233.c
Date: Sat, 29 Feb 2020 02:08: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: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91799-4-E0pQPX5GRW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03427.txt.bz2
Content-length: 206
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91799
--- Comment #4 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Apparently I missed committing the above. Will do later, when I am
awake again.
>From gcc-bugs-return-671846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 02:11:24 2020
Return-Path: <gcc-bugs-return-671846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16328 invoked by alias); 29 Feb 2020 02:11: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 16160 invoked by uid 48); 29 Feb 2020 02:11:20 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91797] [10 regression] r273240 breaks test case gcc.target/powerpc/pr68805.c
Date: Sat, 29 Feb 2020 02:11: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: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91797-4-9qL0wcbFTv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03428.txt.bz2
Content-length: 916
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91797
--- Comment #4 from Segher Boessenkool <segher at gcc dot gnu.org> ---
commit 6cad71cf330623d4a01cb1bb77d4398b1674c776
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date: Wed Jul 10 21:58:08 2019 +0000
fix pr68805.c
diff --git a/gcc/testsuite/gcc.target/powerpc/pr68805.c
b/gcc/testsuite/gcc.targ
index 8ef2e42..217a0ca 100644
--- a/gcc/testsuite/gcc.target/powerpc/pr68805.c
+++ b/gcc/testsuite/gcc.target/powerpc/pr68805.c
@@ -1,4 +1,4 @@
-/* { dg-do compile { target powerpc64le-*-* } } */
+/* { dg-do compile } */
/* { dg-options "-O2 -mdejagnu-cpu=power8" } */
typedef struct bar {
@@ -8,7 +8,4 @@ typedef struct bar {
void foo (TYPE *p, TYPE *q) { *p = *q; }
-/* { dg-final { scan-assembler-times {\mld\M} 2 } } */
-/* { dg-final { scan-assembler-times {\mstd\M} 2 } } */
/* { dg-final { scan-assembler-not "xxpermdi" } } */
-
>From gcc-bugs-return-671847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 02:12:40 2020
Return-Path: <gcc-bugs-return-671847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34497 invoked by alias); 29 Feb 2020 02:12: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 34436 invoked by uid 48); 29 Feb 2020 02:12:34 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91797] [10 regression] r273240 breaks test case gcc.target/powerpc/pr68805.c
Date: Sat, 29 Feb 2020 02:12: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: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91797-4-cWMpRB2ETF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03429.txt.bz2
Content-length: 182
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91797
--- Comment #5 from Segher Boessenkool <segher at gcc dot gnu.org> ---
This and PR88233 were lost somewhere behind the sofa ;-)
>From gcc-bugs-return-671848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 02:21:19 2020
Return-Path: <gcc-bugs-return-671848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95635 invoked by alias); 29 Feb 2020 02:21: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 95585 invoked by uid 48); 29 Feb 2020 02:21:15 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91797] [10 regression] r273240 breaks test case gcc.target/powerpc/pr68805.c
Date: Sat, 29 Feb 2020 02:21: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: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91797-4-8lxMHPOS1J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03430.txt.bz2
Content-length: 239
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91797
--- Comment #6 from Segher Boessenkool <segher at gcc dot gnu.org> ---
I don't think I marked this as P1, fwiw, I hardly ever prioritise bugs,
and I would never make a test tweak a P1.
>From gcc-bugs-return-671849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 03:28:28 2020
Return-Path: <gcc-bugs-return-671849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60562 invoked by alias); 29 Feb 2020 03: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 60549 invoked by uid 48); 29 Feb 2020 03:28:23 -0000
From: "f.heckenbach@fh-soft.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93979] New: missing context in error message due to inheriting template constructor
Date: Sat, 29 Feb 2020 03: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: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: f.heckenbach@fh-soft.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-93979-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03431.txt.bz2
Content-length: 1726
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93979
Bug ID: 93979
Summary: missing context in error message due to inheriting
template constructor
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: f.heckenbach@fh-soft.de
Target Milestone: ---
The following code:
template <typename T> void f (T) = delete;
struct A
{
template <typename T> A (T v) { f (v); }
};
struct B: A
{
using A::A;
};
int main ()
{
B (0);
}
gives this error message:
t.cpp: In instantiation of 'A::A(T) [with T = int]':
t.cpp:10:12: required from here
t.cpp:5:37: error: use of deleted function 'void f(T) [with T = int]'
t.cpp:1:28: note: declared here
The message itself is correct. However, its context includes 3 locations, but
not the one ultimately causing the problem (here, line 15).
In contrast, "A (0)" instead of "B (0)" gives this location:
t.cpp: In instantiation of 'A::A(T) [with T = int]':
t.cpp:15:7: required from here
t.cpp:5:37: error: use of deleted function 'void f(T) [with T = int]'
t.cpp:1:28: note: declared here
In my actual code, of course, the function ("f") is only deleted for a few
types of arguments. The function and both structs are declared in some header,
while the offending code (here, in main) is somewhere in some larger source
file and thus hard to find without that location in the message. (Basically
only by a dumb text search for "B" which occurs rather often, so I have to
manually check the arguments in each constructor call to find the bad one.)
>From gcc-bugs-return-671850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 08:01:54 2020
Return-Path: <gcc-bugs-return-671850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53321 invoked by alias); 29 Feb 2020 08: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 53286 invoked by uid 48); 29 Feb 2020 08:01:49 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93971] std::string considered to alias declared objects of incompatible types
Date: Sat, 29 Feb 2020 08: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: alias, missed-optimization
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-93971-4-KNNt2F5EgE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03432.txt.bz2
Content-length: 663
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93971
--- Comment #5 from Marc Glisse <glisse at gcc dot gnu.org> ---
It has never been very clear to me what restrict means on a struct member, but
I believe adding it to the pointer in vector means that in a function:
void f(vector*a, vector*b)
the compiler could assume that a->data and b->data don't alias even if b turns
out to be equal to a? (plus we would need to replace finish and end_of_storage
with lengths so they don't alias start)
The semantics we would want seem more like: pretend that the allocated region
is an extra member of the class, so they alias iff the class objects are the
same?
>From gcc-bugs-return-671851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 08:06:26 2020
Return-Path: <gcc-bugs-return-671851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55650 invoked by alias); 29 Feb 2020 08: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 55604 invoked by uid 55); 29 Feb 2020 08:06:22 -0000
From: "paul.richard.thomas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92785] expressions passed as real arguments to a dummy polymorphic argument fail with indexing error
Date: Sat, 29 Feb 2020 08: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.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paul.richard.thomas at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92785-4-yM4CMS3ONW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92785-4@http.gcc.gnu.org/bugzilla/>
References: <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: 2020-02/txt/msg03433.txt.bz2
Content-length: 851
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92785
--- Comment #6 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> ---
Thanks! I'll change to STOP 1.
Paul
On Fri, 28 Feb 2020 at 20:08, drikosev at gmail dot com
<gcc-bugzilla@gcc.gnu.org> wrote:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92785
>
> --- Comment #5 from Ev Drikos <drikosev at gmail dot com> ---
> (In reply to Paul Thomas from comment #4)
> > Committed as revision r10-6924-g7485ace81de9ec9dd5c87edf67e359d31ce35a20
> >
> > Paul
>
> Hello Mr. P. Thomas,
>
> With fortran-8.2, the test case prints 'FAILED' but exits with return code 0.
> So,
> a regression in the future might go unnoticed.
>
> Regards,
> Ev. Drikos
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You are the assignee for the bug.
>From gcc-bugs-return-671852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 09:40:08 2020
Return-Path: <gcc-bugs-return-671852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107901 invoked by alias); 29 Feb 2020 09:40: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 107841 invoked by uid 48); 29 Feb 2020 09:40:03 -0000
From: "uecker at eecs dot berkeley.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93949] [8/9/10 Regression] Register const local var will not compile since r0-58166
Date: Sat, 29 Feb 2020 09:40: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: uecker at eecs dot berkeley.edu
X-Bugzilla-Status: NEW
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: cc
Message-ID: <bug-93949-4-y12fgIIUcV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03434.txt.bz2
Content-length: 859
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93949
Martin Uecker <uecker at eecs dot berkeley.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |uecker at eecs dot berkeley.edu
--- Comment #4 from Martin Uecker <uecker at eecs dot berkeley.edu> ---
One other simply fix would be to simple remove the error in varasm.c.
This then allows also register variables without __asm
at file scope but does not seem to have any other
negative effect. Register at file scope is also already
diagnosed by the C FE when using --pedantic, so at some
point this was supposed to work I think.
There is a proposal for C2x which would allow
register at file scope:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2486.htm
>From gcc-bugs-return-671853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 11:08:51 2020
Return-Path: <gcc-bugs-return-671853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27354 invoked by alias); 29 Feb 2020 11:08: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 27316 invoked by uid 48); 29 Feb 2020 11:08:47 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93966] [9/10 Regression] -fcf-protection -flto -g don't work togeter
Date: Sat, 29 Feb 2020 11:08: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:
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: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on short_desc everconfirmed
Message-ID: <bug-93966-4-ZhoOmUErrq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03435.txt.bz2
Content-length: 686
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93966
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-02-29
Summary|-fcf-protection -flto -g |[9/10 Regression]
|don't work togeter |-fcf-protection -flto -g
| |don't work togeter
Ever confirmed|0 |1
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
Works with GCC 8.
>From gcc-bugs-return-671854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 11:14:40 2020
Return-Path: <gcc-bugs-return-671854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31738 invoked by alias); 29 Feb 2020 11: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 31657 invoked by uid 48); 29 Feb 2020 11:14:32 -0000
From: "sergeev917 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93980] New: use of lto breaks -Wl,--exclude-libs
Date: Sat, 29 Feb 2020 11:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sergeev917 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 attachments.created
Message-ID: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03436.txt.bz2
Content-length: 3366
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93980
Bug ID: 93980
Summary: use of lto breaks -Wl,--exclude-libs
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: sergeev917 at gmail dot com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Created attachment 47934
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47934&action=edit
source files and shell validation script
The apparent issue is that with LTO disabled -Wl,--exclude-libs,ALL works as
intended, but with -flto -- symbols from linked archives are not hidden
anymore.
Since this particular issue involves more than one translation unit, I'm not
sure about the appropriate submission format. The issue is easily reproduced
with about 10 lines of code with no std libs involved.
The reproducer consists of a static library "foo" and a shared library "bar"
that links with "foo" (and we would like to hide "foo" symbols in "bar").
foo.h:
#pragma once
__attribute__((visibility("default"))) int foo();
foo.cc:
#include "foo.h"
int foo() { return 100; }
bar.h:
#pragma once
__attribute__((visibility("default"))) int bar();
bar.cc:
#include "bar.h"
#include "foo.h"
int bar() { return foo(); }
Build commands:
g++ -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -flto -c foo.cc -o
.foo.o
ar qc .foo.a .foo.o
g++ -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -flto -c bar.cc -o
.bar.o
g++ -Wl,--exclude-libs,ALL -flto -shared -o libbar.so .bar.o .foo.a
readelf --dyn-syms --wide libbar.so | c++filt
The last commands produces both bar() and foo() -- that is, foo() is not
hidden. Replacing -flto with -fno-lto gives only bar().
--
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/9.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with:
/var/tmp/portage/sys-devel/gcc-9.2.0-r4/work/gcc-9.2.0/configure
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/9.2.0
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/9.2.0
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/9.2.0/man
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/9.2.0/info
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include/g++-v9
--with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/9.2.0/python
--enable-languages=c,c++,go,fortran --enable-obsolete --enable-secureplt
--disable-werror --with-system-zlib --disable-nls --enable-checking=release
--with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 9.2.0-r4 p5'
--disable-esp --enable-libstdcxx-time --with-build-config=bootstrap-lto
--disable-libstdcxx-pch --enable-shared --enable-threads=posix
--enable-__cxa_atexit --enable-clocale=gnu --disable-multilib
--with-multilib-list=m64 --disable-altivec --disable-fixed-point
--enable-targets=all --enable-libgomp --disable-libmudflap --disable-libssp
--disable-systemtap --enable-vtable-verify --enable-lto --without-isl
--enable-default-pie --enable-default-ssp
Thread model: posix
gcc version 9.2.0 (Gentoo 9.2.0-r4 p5)
>From gcc-bugs-return-671855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 12:05:58 2020
Return-Path: <gcc-bugs-return-671855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44312 invoked by alias); 29 Feb 2020 12: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 44282 invoked by uid 48); 29 Feb 2020 12:05:54 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92959] ICE in gfc_conv_associated, at fortran/trans-intrinsic.c:8634
Date: Sat, 29 Feb 2020 12:05: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: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc assigned_to attachments.created
Message-ID: <bug-92959-4-lSAS0i31qv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92959-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92959-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03437.txt.bz2
Content-length: 617
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92959
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
--- Comment #3 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 47935
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47935&action=edit
Patch for the PR
This will be posted in a few minutes
Paul
>From gcc-bugs-return-671856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 14:07:25 2020
Return-Path: <gcc-bugs-return-671856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85536 invoked by alias); 29 Feb 2020 14:07: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 85510 invoked by uid 48); 29 Feb 2020 14:07:19 -0000
From: "jwjagersma at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93981] New: No EH information generated for asm statements
Date: Sat, 29 Feb 2020 14:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jwjagersma 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-93981-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03438.txt.bz2
Content-length: 1464
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93981
Bug ID: 93981
Summary: No EH information generated for asm statements
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: inline-asm
Assignee: unassigned at gcc dot gnu.org
Reporter: jwjagersma at gmail dot com
Target Milestone: ---
No exception handling information is generated for asm statements:
```
$ cat unwind.cpp
void f()
{
try { asm ("nop #try"); }
catch (...) { asm ("nop #catch"); }
}
$ g++-9 -fnon-call-exceptions unwind.cpp -S -dA -o -
.file "unwind.cpp"
.text
.globl _Z1fv
.type _Z1fv, @function
_Z1fv:
.LFB0:
.cfi_startproc
# BLOCK 2 seq:0
# PRED: ENTRY (FALLTHRU)
pushq %rbp
.cfi_def_cfa_offset 16
.cfi_offset 6, -16
movq %rsp, %rbp
.cfi_def_cfa_register 6
#APP
# 3 "unwind.cpp" 1
nop #try
# 0 "" 2
#NO_APP
nop
popq %rbp
.cfi_def_cfa 7, 8
# SUCC: EXIT [always]
ret
.cfi_endproc
.LFE0:
.size _Z1fv, .-_Z1fv
.ident "GCC: (Ubuntu 9.2.1-17ubuntu1~18.04.1) 9.2.1 20191102"
.section .note.GNU-stack,"",@progbits
```
Since asms may contain trapping instructions, they should be covered by
an EH region in the unwind tables when compiling with
-fnon-call-exceptions.
>From gcc-bugs-return-671857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 14:18:22 2020
Return-Path: <gcc-bugs-return-671857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104844 invoked by alias); 29 Feb 2020 14: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 104262 invoked by uid 48); 29 Feb 2020 14:17:59 -0000
From: "jwjagersma at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93981] No EH information generated for asm statements
Date: Sat, 29 Feb 2020 14:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jwjagersma 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-93981-4-1MCiydgCLW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03439.txt.bz2
Content-length: 221
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93981
--- Comment #1 from jwjagersma at gmail dot com ---
Created attachment 47936
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47936&action=edit
proposed patch
>From gcc-bugs-return-671858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 15:11:46 2020
Return-Path: <gcc-bugs-return-671858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18865 invoked by alias); 29 Feb 2020 15:11: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 18798 invoked by uid 55); 29 Feb 2020 15:11:42 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/93731] [10 regression] asan tests cause kernel panic on Darwin 11
Date: Sat, 29 Feb 2020 15:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-93731-4-0u7fZzBZJq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03440.txt.bz2
Content-length: 1178
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93731
--- Comment #7 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
> Uni-Bielefeld.DE> ---
>> --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
[...
>> Of course, trying to workaround kernel bugs this way is weird, but if it isn't
>> supported anymore or Apple isn't willing to fix their bugs...
>
> Mac OS X 10.7 is almost 9 years old by now and long past support. I
> don't feel particularly inclined to reghunt which gcc/sanitizer change
> caused this, let alone debug the Darwin kernel either.
I've since experimented a bit more: 32-bit 10.7 is affected just the
same. Afterwards, I've copied both the 32 and 64-bit
alloca_big_alignment.exe and the corresponding libasan.6.dylib and
libgcc_s.1.dylib to a 10.8 VM where they run just fine, so this is
obviously 10.7-only issue.
While working on this, I've created VirtualBox VMs for every single
macOS release between 10.7 and 10.15, each with the latest updates and
last supported Xcode version installed and ready for experiments if
needed.
>From gcc-bugs-return-671859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 15:41:32 2020
Return-Path: <gcc-bugs-return-671859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1177 invoked by alias); 29 Feb 2020 15:41: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 1124 invoked by uid 48); 29 Feb 2020 15:41:28 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/93731] [10 regression] asan tests cause kernel panic on Darwin 11
Date: Sat, 29 Feb 2020 15:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-93731-4-DEzcQt4vaK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03441.txt.bz2
Content-length: 1960
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93731
--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #7)
> > --- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
> > Uni-Bielefeld.DE> ---
> >> --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> [...
> >> Of course, trying to workaround kernel bugs this way is weird, but if it isn't
> >> supported anymore or Apple isn't willing to fix their bugs...
> >
> > Mac OS X 10.7 is almost 9 years old by now and long past support. I
> > don't feel particularly inclined to reghunt which gcc/sanitizer change
> > caused this, let alone debug the Darwin kernel either.
>
> I've since experimented a bit more: 32-bit 10.7 is affected just the
> same. Afterwards, I've copied both the 32 and 64-bit
> alloca_big_alignment.exe and the corresponding libasan.6.dylib and
> libgcc_s.1.dylib to a 10.8 VM where they run just fine, so this is
> obviously 10.7-only issue.
Yeah, I'm just waiting for the x86_64-darwin13 run to finish with libsanitizer
disabled
(the fault repeats for me on 64b).
It's early low on my priority list to look at this with the current sanitiser
output, since that is emitting a different ABI for Darwin than clang does (so
the emitted code would be the first thing to fix).
> While working on this, I've created VirtualBox VMs for every single
> macOS release between 10.7 and 10.15, each with the latest updates and
> last supported Xcode version installed and ready for experiments if
> needed.
VB is more reliable for some versions than others (which might have little to
do with VB, of course ;) ). It's pretty hard to get anything < 10.6 to work
there, and obv. is no use of ppc.
----
Right now, I'm thinking to disable sanitzer by default for master <= 10.7 and
for 9.x for <= 10.6. I'll do that today or tomorrow since I want to make the
9.3 deadline.
>From gcc-bugs-return-671861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 16:19:29 2020
Return-Path: <gcc-bugs-return-671861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126200 invoked by alias); 29 Feb 2020 16:19: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 126127 invoked by uid 55); 29 Feb 2020 16:19:25 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92906] [10 regression] FAIL: libstdc++-abi/abi_check
Date: Sat, 29 Feb 2020 16:19: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: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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-92906-4-Zw0ojmWMdX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92906-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03443.txt.bz2
Content-length: 619
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92906
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by John David Anglin <danglin@gcc.gnu.org>:
https://gcc.gnu.org/g:d4912dc76662ab434c897ab454e3285fbb6ca6df
commit r10-6936-gd4912dc76662ab434c897ab454e3285fbb6ca6df
Author: John David Anglin <danglin@gcc.gnu.org>
Date: Sat Feb 29 16:13:23 2020 +0000
Fix baseline symbols on hppa-linux-gnu
2020-02-29 John David Anglin <danglin@gcc.gnu.org>
PR libstdc++/92906
* config/abi/post/hppa-linux-gnu/baseline_symbols.txt: Update.
>From gcc-bugs-return-671860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 16:19:14 2020
Return-Path: <gcc-bugs-return-671860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125367 invoked by alias); 29 Feb 2020 16:19: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 125334 invoked by uid 48); 29 Feb 2020 16:19:10 -0000
From: "nate at thatsmathematics dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93982] New: Assignment incorrectly omitted by -foptimize-strlen
Date: Sat, 29 Feb 2020 16: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nate at thatsmathematics 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 attachments.created
Message-ID: <bug-93982-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03442.txt.bz2
Content-length: 3173
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93982
Bug ID: 93982
Summary: Assignment incorrectly omitted by -foptimize-strlen
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: nate at thatsmathematics dot com
Target Milestone: ---
Created attachment 47937
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47937&action=edit
Reduced testcase
If the attached testcase is compiled with `-O1 -foptimize-strlen' on amd64, the
function foo is miscompiled: the assignment to res.target[1] is omitted. It
also happens with -O2, but not with -O1 alone or -O3.
This bug is somewhat similar to bug 93213. It is a regression from 9.2.0.
The generated assembly is:
foo:
subq $8, %rsp
call my_alloc
movq $.LC0, (%rax)
movq $.LC1, 16(%rax)
movq $.LC1, 24(%rax)
movq $.LC1, 32(%rax)
addq $8, %rsp
ret
Note the absence of `movq $.LC1, 8(%rax)'.
I tested with trunk, latest pull from git, revision 117baab8. In particular
the patch for bug 93213 (e13f37d9) is included. The program is compiled
correctly by gcc 9.2.0 with the same options (and all others I tried). I did a
git bisect and the offending commit is 34fcf41e.
The cast in foo() at first looked questionable from a strict aliasing
standpoint, but I believe the code is legal since the memory returned by calloc
has no declared type, and we never access this memory except as objects of type
`const char *'. Also, the miscompilation persists with -fno-strict-aliasing.
I am no gcc expert, but I dug into the source a little bit, out of curiosity.
It looks like the deletion happens in handle_store(), at
gcc/tree-ssa-strlen.c:5021. It seems that in this function, the code is being
treated as if the string "12345678" itself were being stored at address
res.target, rather than the address of the string; as if the code were
`strcpy(res.target, "12345678")'. In particular, it thinks the trailing null
was stored at address res.target+8. The following statement, `res.target[1] =
""', is likewise treated as if it were `strcpy(res.target+8, "")', which would
also just store a null byte at res.target+8, so it is seen as redundant and is
removed.
I would like to acknowledge StackOverflow user BrodieG for initially
discovering this bug and helping to investigate, as well as users KamilCuk and
John Bollinger for helpful comments. The original question is at
https://stackoverflow.com/q/60406042/634919.
Output of `gcc -v`:
Using built-in specs.
COLLECT_GCC=/home/nate/gcc/bin/gcc
COLLECT_LTO_WRAPPER=/home/nate/do-not-backup/gcc-inst/bin/../libexec/gcc/x86_64-pc-linux-gnu/10.0.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../configure --prefix=/home/nate/gcc --disable-bootstrap
--enable-languages=c
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.0.1 20200229 (experimental) (GCC)
>From gcc-bugs-return-671862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 16:22:47 2020
Return-Path: <gcc-bugs-return-671862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128382 invoked by alias); 29 Feb 2020 16:22: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 128337 invoked by uid 48); 29 Feb 2020 16:22:43 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93981] No EH information generated for asm statements
Date: Sat, 29 Feb 2020 16:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
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-93981-4-Vcds51wfzM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03444.txt.bz2
Content-length: 529
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93981
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |segher at gcc dot gnu.org
--- Comment #2 from Segher Boessenkool <segher at gcc dot gnu.org> ---
How do you propose the compiler can generate accurate asynchronous unwind
info for random inline assembler? (Answer: that is impossible).
>From gcc-bugs-return-671863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 16:25:35 2020
Return-Path: <gcc-bugs-return-671863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130326 invoked by alias); 29 Feb 2020 16:25: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 130241 invoked by uid 48); 29 Feb 2020 16:25:31 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91797] [10 regression] r273240 breaks test case gcc.target/powerpc/pr68805.c
Date: Sat, 29 Feb 2020 16:25: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: law at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91797-4-CpptnGrLEv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03445.txt.bz2
Content-length: 403
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91797
--- Comment #7 from Jeffrey A. Law <law at redhat dot com> ---
I didn't look at the history to see who marked it a P1. I did consider the
possibility that this was being kept open because the test failures, while
seemingly innocuous, were actually something much more serious.
Thanks in advance for taking care of them when you're awake again :-)
>From gcc-bugs-return-671864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 16:28:37 2020
Return-Path: <gcc-bugs-return-671864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1520 invoked by alias); 29 Feb 2020 16: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 1448 invoked by uid 48); 29 Feb 2020 16:28:33 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93974] [8/9/10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Sat, 29 Feb 2020 16: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: 9.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93974-4-tbvTCIMB9G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03446.txt.bz2
Content-length: 3855
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vmakarov at gcc dot gnu.org,
| |wschmidt at gcc dot gnu.org
--- Comment #4 from Peter Bergner <bergner at gcc dot gnu.org> ---
I'm CCing Vlad, since I need some guidance/help for some LRA questions.
So this looks similar to PR93658, in that my patch exposed a latent bug.
However, in this case, the bugs seems to be in the LRA constraints fixup
code.
Jakub, I would normally just think reverting the 3 commits used to fix
PR93658 in GCC 8 would be the best course of action here, but if we do
that, then we're just reexposing the bug from PR93658. But maybe that
is still preferable than applying an LRA fix (which we don't have yet)
that could affect all targets this late in the release process? Thoughts?
So onto my findings. After IRA, we have the following allocations and rtl:
Disposition:
6:r121 l0 mem 5:r124 l0 33 4:r125 l0 34 0:r128 l0 14
(insn 34 (set (reg:DI 128) (const_int -32)))
...
(insn 39 (set (reg:V2DF 121 [ D.3415 ])
(mem/c:V2DF (and:DI (plus:DI (reg/f:DI 110 sfp)
(reg:DI 128))
(const_int -16))))
(expr_list:REG_EQUIV (mem/c:V2DF (and:DI (plus:DI (reg/f:DI 110 sfp)
(reg:DI 128)) (const_int -16)))
(expr_list:REG_EQUAL (mem/c:V2DF (plus:DI (reg/f:DI 110 sfp) (const_int
-32))))))
...
(insn 15 (set (reg:DF 124)
(subreg:DF (reg:V2DF 121) 0)))
(insn 16 (set (reg:DF 125 [+8 ])
(subreg:DF (reg:V2DF 121) 8))
(expr_list:REG_DEAD (reg:V2DF 121)))
When LRA processes insn 15, it replaces the subreg: reg with the mem from
insn 39 and we get:
(insn 15 (set (reg:DF 124)
(mem/c:DF (and:DI (plus:DI (plus:DI (reg/f:DI 110 sfp)
(reg:DI 128))
(const_int 64 [0x40]))
(const_int -16)))))
This is not a valid address, so LRA in process_address(), we pass the
following address to decompose_address():
(and:DI (plus:DI (plus:DI (reg/f:DI 110 sfp)
(reg:DI 128))
(const_int 64))
(const_int -16))
Eventually, we end up with:
(insn 56 (set (reg:DI 136)
(plus:DI (reg/f:DI 110 sfp)
(const_int 64))))
(insn 57 (set (reg:DI 136)
(plus:DI (reg:DI 136)
(reg:DI 128))))
(insn 58 (set (reg:DI 136)
(and:DI (reg:DI 136)
(const_int -16))))
(insn 15 (set (reg:DF 124)
(mem/c:DF (reg:DI 136))))
This isn't ideal, but looks correct.
The problem comes when we process insn 16. It looks just like insn 15,
but its subreg is at an offset of 8. In decompose_address(), we're
passed an address that looks like:
(plus:DI (and:DI (plus:DI (plus:DI (reg/f:DI 110 sfp)
(reg:DI 128))
(const_int 64))
(const_int -16))
(const_int 8))
Now strip_address_mutations() seems to expect seeing a "(and: ..." type
address, but it is completely confused by seeing a PLUS wrapped around
it, which is what eventually causes us to ICE in decompose_normal_address
because it doesn't look like we have a base_term or index_term type addr.
Vlad, do you have some guidance on what should be done when we see
an address like the above? I tried hacking some changes to recognize
the extra PLUS, but ended up causing an infinite loop in LRA.
Do you have thoughts on how to fix this properly?
>From gcc-bugs-return-671865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 16:40:41 2020
Return-Path: <gcc-bugs-return-671865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50466 invoked by alias); 29 Feb 2020 16:40: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 50433 invoked by uid 48); 29 Feb 2020 16:40:37 -0000
From: "jwjagersma at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93981] No EH information generated for asm statements
Date: Sat, 29 Feb 2020 16:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jwjagersma 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-93981-4-5I3n5OSRqd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03447.txt.bz2
Content-length: 187
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93981
--- Comment #3 from jwjagersma at gmail dot com ---
I don't think it needs to. The user can do this manually with .cfi directives.
>From gcc-bugs-return-671866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 16:45:27 2020
Return-Path: <gcc-bugs-return-671866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59354 invoked by alias); 29 Feb 2020 16:45: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 59174 invoked by uid 48); 29 Feb 2020 16:45:00 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/93731] [10 regression] asan tests cause kernel panic on Darwin 11
Date: Sat, 29 Feb 2020 16:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-93731-4-x86vW1IvVf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03448.txt.bz2
Content-length: 873
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93731
--- Comment #9 from Iain Sandoe <iains at gcc dot gnu.org> ---
one additional point.
For earlier OS versions the 'atos' version installed is not sufficient to get
sensible output from the sanitizer (characterised by very long timeouts on
failed tests).
In that case, it is better to install llvm-symbolizer from a recentish LLVM and
to set ASAN_SYMBOLIZER_PATH=/path/to/llvm-symbolizer before running tests
(FWFW, I tend to do this about 50% of the time even on recent OS versions to
ensure that the fails seen are from the sanitiser not atos). atos is
closed-source so we can't fix/rebuild it.
Unfortunately, the llvm-symbolizer exe is not part of the Xcode distributions,
so it has to be built from source.
In the case of the x86_64-darwin11 kernel panics, this made no difference to
the observed fails.
>From gcc-bugs-return-671867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 17:17:00 2020
Return-Path: <gcc-bugs-return-671867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94198 invoked by alias); 29 Feb 2020 17:17: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 94142 invoked by uid 48); 29 Feb 2020 17:16:56 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] [8/9/10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Sat, 29 Feb 2020 17:17: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.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: component
Message-ID: <bug-93974-4-6l1hGn1xmF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03449.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|target |rtl-optimization
--- Comment #5 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Not a target bug. Andrew, please don't change classification unless you know
where the problem is.
>From gcc-bugs-return-671868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 17:32:14 2020
Return-Path: <gcc-bugs-return-671868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109418 invoked by alias); 29 Feb 2020 17:32: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 109375 invoked by uid 48); 29 Feb 2020 17:32:10 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93981] No EH information generated for asm statements
Date: Sat, 29 Feb 2020 17:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
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-93981-4-ZR14xn9TRs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03450.txt.bz2
Content-length: 324
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93981
--- Comment #4 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Pretending any asm can throw would be a pretty serious code degradation.
Any asm that is not volatile cannot throw (and be correct code). But
most volatile asm in the wild can never throw, either.
>From gcc-bugs-return-671869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 17:40:00 2020
Return-Path: <gcc-bugs-return-671869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113380 invoked by alias); 29 Feb 2020 17:39: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 113342 invoked by uid 48); 29 Feb 2020 17:39:56 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92976] [8/9/10 Regression][OOP] ICE in trans_associate_var, at fortran/trans-stmt.c:1963
Date: Sat, 29 Feb 2020 17:39: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: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc assigned_to
Message-ID: <bug-92976-4-BGPwDiAeJv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92976-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92976-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03451.txt.bz2
Content-length: 497
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92976
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
--- Comment #2 from Paul Thomas <pault at gcc dot gnu.org> ---
I just posted the fix to the list.
Paul
>From gcc-bugs-return-671870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 17:56:01 2020
Return-Path: <gcc-bugs-return-671870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21943 invoked by alias); 29 Feb 2020 17:56: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 21889 invoked by uid 48); 29 Feb 2020 17:55:57 -0000
From: "jwjagersma at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93981] No EH information generated for asm statements
Date: Sat, 29 Feb 2020 17:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jwjagersma 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-93981-4-sMpCUMg1zN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03452.txt.bz2
Content-length: 1679
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93981
--- Comment #5 from jwjagersma at gmail dot com ---
(In reply to Segher Boessenkool from comment #4)
> Pretending any asm can throw would be a pretty serious code degradation.
>
> Any asm that is not volatile cannot throw (and be correct code). But
> most volatile asm in the wild can never throw, either.
The intention is to only produce EH info for volatile asms, and only if
-fnon-call-exceptions is given. Asms that take volatile memory operands
should be covered too. There are multiple instances in the gcc code
that suggest this should be possible, but it seems it was never
implemented fully. For example this comment in stmt_could_throw_p:
```
/* The only statements that can throw an exception are assignments,
conditionals, calls, resx, and asms. */
```
And the fact that tree_could_trap_p, stmt_could_throw_p, may_trap_p_1
have cases that return true for asm.
Do note that the proposed patch is still incomplete, I ran into an ICE
while building libgcc with -fnon-call-exceptions:
```
during GIMPLE pass: ehcleanup
../../../gnu/gcc-9.2.0/libgcc/config/i386/sfp-exceptions.c: In function
'__sfp_handle_exceptions':
../../../gnu/gcc-9.2.0/libgcc/config/i386/sfp-exceptions.c:107:1: internal
compiler error: in mark_reachable_handlers, at tree-eh.c:3929
107 | }
| ^
libbacktrace could not find executable to open
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
```
However I am not knowledgable enough about gcc's inner workings to know
what exactly is missing. I'm hoping someone can help me out with this.
>From gcc-bugs-return-671871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 18:17:16 2020
Return-Path: <gcc-bugs-return-671871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76618 invoked by alias); 29 Feb 2020 18:17: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 70938 invoked by uid 48); 29 Feb 2020 18:17:12 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/83118] [8/9/10 Regression] Bad intrinsic assignment of class(*) array component of derived type
Date: Sat, 29 Feb 2020 18: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83118-4-ARcD23GpPA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83118-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83118-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03453.txt.bz2
Content-length: 375
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83118
--- Comment #30 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Damian Rouson from comment #29)
> Hi Paul,
>
> The test case works with your patch applied. Thanks!
>
> Damian
Hi Damian,
I need to digest https://gcc.gnu.org/ml/fortran/2019-11/msg00098.html before
this is ready to go.
Regards
Paul
>From gcc-bugs-return-671872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 18:42:25 2020
Return-Path: <gcc-bugs-return-671872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94355 invoked by alias); 29 Feb 2020 18:42: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 94311 invoked by uid 48); 29 Feb 2020 18:42:20 -0000
From: "lyberta at lyberta dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93983] New: std::filesystem::path is not concept-friendly
Date: Sat, 29 Feb 2020 18:42: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lyberta at lyberta 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-93983-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03454.txt.bz2
Content-length: 4680
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93983
Bug ID: 93983
Summary: std::filesystem::path is not concept-friendly
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: lyberta at lyberta dot net
Target Milestone: ---
#include <concepts>
#include <filesystem>
struct Foo
{
Foo(const std::filesystem::path& p);
};
static_assert(std::copyable<Foo>);
Error:
In file included from <source>:1:
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/bits/stl_iterator_base_types.h:
In instantiation of 'struct std::iterator_traits<Foo>':
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/bits/fs_path.h:84:11:
required by substitution of 'template<class _Iter, class _Iter_traits> using
__is_path_iter_src = std::__and_<std::__or_<std::is_same<typename
std::remove_const<typename _Iter_traits::value_type>::type, char>,
std::is_same<typename std::remove_const<typename
_Iter_traits::value_type>::type, char8_t>, std::is_same<typename
std::remove_const<typename _Iter_traits::value_type>::type, wchar_t>,
std::is_same<typename std::remove_const<typename
_Iter_traits::value_type>::type, char16_t>, std::is_same<typename
std::remove_const<typename _Iter_traits::value_type>::type, char32_t> >,
std::is_base_of<std::input_iterator_tag, typename
_Iter_traits::iterator_category> > [with _Iter = Foo; _Iter_traits =
std::iterator_traits<Foo>]'
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/bits/fs_path.h:91:5:
required by substitution of 'template<class _Iter>
std::filesystem::__cxx11::__detail::__is_path_iter_src<_Iter>
std::filesystem::__cxx11::__detail::__is_path_src(_Iter, int) [with _Iter =
Foo]'
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/bits/fs_path.h:115:29:
required from 'struct
std::filesystem::__cxx11::__detail::__constructible_from<Foo, void>'
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/type_traits:138:12:
required from 'struct std::__and_<std::__not_<std::is_void<Foo> >,
std::filesystem::__cxx11::__detail::__constructible_from<Foo, void> >'
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/type_traits:143:12:
required from 'struct std::__and_<std::__not_<std::is_same<Foo,
std::filesystem::__cxx11::path> >, std::__not_<std::is_void<Foo> >,
std::filesystem::__cxx11::__detail::__constructible_from<Foo, void> >'
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/bits/fs_path.h:119:11:
required by substitution of 'template<class _Tp1, class _Tp2> using _Path =
typename std::enable_if<std::__and_<std::__not_<std::is_same<typename
std::remove_cv< <template-parameter-1-1> >::type,
std::filesystem::__cxx11::path> >, std::__not_<std::is_void<typename
std::remove_pointer<_Tp>::type> >,
std::filesystem::__cxx11::__detail::__constructible_from<_Tp1, _Tp2> >::value,
std::filesystem::__cxx11::path>::type [with _Tp1 = Foo; _Tp2 = void]'
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/bits/fs_path.h:219:7:
required by substitution of 'template<class _Source, class _Require>
std::filesystem::__cxx11::path::path(const _Source&,
std::filesystem::__cxx11::path::format) [with _Source = Foo; _Require =
<missing>]'
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/type_traits:901:30:
required from 'struct std::__is_constructible_impl<Foo, Foo>'
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/type_traits:906:12:
required from 'struct std::is_constructible<Foo, Foo>'
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/type_traits:3107:25:
required from 'constexpr const bool std::is_constructible_v<Foo, Foo>'
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/concepts:139:30:
required from here
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/concepts:139:30:
error: the value of 'std::is_constructible_v<Foo, Foo>' is not usable in a
constant expression
139 | = destructible<_Tp> && is_constructible_v<_Tp, _Args...>;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/concepts:44,
from <source>:1:
/opt/compiler-explorer/gcc-trunk-20200229/include/c++/10.0.1/type_traits:3107:25:
note: 'std::is_constructible_v<Foo, Foo>' used in its own initializer
3107 | inline constexpr bool is_constructible_v =
| ^~~~~~~~~~~~~~~~~~
>From gcc-bugs-return-671873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 19:04:41 2020
Return-Path: <gcc-bugs-return-671873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122155 invoked by alias); 29 Feb 2020 19: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 122122 invoked by uid 48); 29 Feb 2020 19:04:37 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93983] std::filesystem::path is not concept-friendly
Date: Sat, 29 Feb 2020 19:04: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: 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: cc
Message-ID: <bug-93983-4-RPmj7LdOd4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93983-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93983-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03455.txt.bz2
Content-length: 994
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93983
Barry Revzin <barry.revzin at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |barry.revzin at gmail dot com
--- Comment #1 from Barry Revzin <barry.revzin at gmail dot com> ---
Here's a shorter reproduction without filesystem:
#include <concepts>
#include <iterator>
struct path {
template <typename Source,
typename = std::enable_if_t<
std::is_same_v<
std::iterator_traits<Source>::value_type,
char>>
>
path(Source const&);
};
struct Bar
{
Bar(const path& p);
};
#ifdef ADD_THIS
static_assert(!std::constructible_from<path, Bar>);
#endif
static_assert(std::copyable<Bar>);
If ADD_THIS isn't defined, the copyable check is a hard error. If it is
defined, compiles fine.
https://godbolt.org/z/FEoiwA
>From gcc-bugs-return-671874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 19:15:56 2020
Return-Path: <gcc-bugs-return-671874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26829 invoked by alias); 29 Feb 2020 19:15: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 26578 invoked by uid 48); 29 Feb 2020 19:15:51 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93983] std::filesystem::path is not concept-friendly
Date: Sat, 29 Feb 2020 19:15: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: 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:
Message-ID: <bug-93983-4-hZrGPfLVXK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93983-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93983-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03456.txt.bz2
Content-length: 152
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93983
--- Comment #2 from Barry Revzin <barry.revzin at gmail dot com> ---
(From Tim) This is LWG 3244.
>From gcc-bugs-return-671875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 19:24:46 2020
Return-Path: <gcc-bugs-return-671875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33214 invoked by alias); 29 Feb 2020 19:24: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 33148 invoked by uid 55); 29 Feb 2020 19:24:42 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92548] FAIL: gcc.dg/ipa/ipa-sra-12.c scan-ipa-dump-times sra "Will split parameter" 2
Date: Sat, 29 Feb 2020 19:24: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: cvs-commit 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:
Message-ID: <bug-92548-4-zaISDD3rjI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92548-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92548-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03457.txt.bz2
Content-length: 774
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92548
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by John David Anglin <danglin@gcc.gnu.org>:
https://gcc.gnu.org/g:38b1722d5d44c52e06a8694b8fa36793735e27d1
commit r10-6943-g38b1722d5d44c52e06a8694b8fa36793735e27d1
Author: John David Anglin <danglin@gcc.gnu.org>
Date: Sat Feb 29 19:23:02 2020 +0000
XFAIL IPA tests that are not supported on 32-bit hppa*-*-hpux*.
2020-02-29 John David Anglin <danglin@gcc.gnu.org>
PR ipa/92548
* gcc.dg/ipa/ipa-sra-12.c: xfail parameter split test on 32-bit
hppa*-*-hpux*.
* gcc.dg/ipa/ipa-sra-14.c: Likewise.
* gcc.dg/ipa/ipcp-agg-12.c: xfail adding extra caller test.
>From gcc-bugs-return-671876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 19:35:54 2020
Return-Path: <gcc-bugs-return-671876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74931 invoked by alias); 29 Feb 2020 19:35: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 74897 invoked by uid 48); 29 Feb 2020 19:35:50 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92548] FAIL: gcc.dg/ipa/ipa-sra-12.c scan-ipa-dump-times sra "Will split parameter" 2
Date: Sat, 29 Feb 2020 19:35: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: danglin 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-92548-4-KToWrMvoo0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92548-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92548-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03458.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92548
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from John David Anglin <danglin at gcc dot gnu.org> ---
Fixed on trunk.
>From gcc-bugs-return-671877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 20:37:55 2020
Return-Path: <gcc-bugs-return-671877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68921 invoked by alias); 29 Feb 2020 20:37: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 68887 invoked by uid 55); 29 Feb 2020 20:37:50 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/91100] [9,10 Regression] FAIL: gnat.dg/socket1.adb execution test
Date: Sat, 29 Feb 2020 20:37: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: cvs-commit 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:
Message-ID: <bug-91100-4-gpC3PmbSul@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91100-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91100-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03459.txt.bz2
Content-length: 605
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91100
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by John David Anglin <danglin@gcc.gnu.org>:
https://gcc.gnu.org/g:819852b98eb2451672b35bf4a35bcfd41071e26e
commit r10-6945-g819852b98eb2451672b35bf4a35bcfd41071e26e
Author: John David Anglin <danglin@gcc.gnu.org>
Date: Sat Feb 29 20:36:49 2020 +0000
Disable gnat.dg/socket1.adb on hppa*-*-hpux*.
2020-02-29 John David Anglin <danglin@gcc.gnu.org>
PR ada/91100
* gnat.dg/socket1.adb: Disable on hppa*-*-hpux*.
>From gcc-bugs-return-671878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 20:40:19 2020
Return-Path: <gcc-bugs-return-671878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70741 invoked by alias); 29 Feb 2020 20:40: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 70696 invoked by uid 55); 29 Feb 2020 20:40:14 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/91100] [9,10 Regression] FAIL: gnat.dg/socket1.adb execution test
Date: Sat, 29 Feb 2020 20:40: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: cvs-commit 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:
Message-ID: <bug-91100-4-gvI38oZE9S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91100-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91100-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03460.txt.bz2
Content-length: 610
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91100
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by John David Anglin
<danglin@gcc.gnu.org>:
https://gcc.gnu.org/g:11d93ca76c04f79e43b6e39ab8658b07c0475932
commit r9-8305-g11d93ca76c04f79e43b6e39ab8658b07c0475932
Author: John David Anglin <danglin@gcc.gnu.org>
Date: Sat Feb 29 20:39:09 2020 +0000
Disable gnat.dg/socket1.adb on hppa*-*-hpux*.
2020-02-29 John David Anglin <danglin@gcc.gnu.org>
PR ada/91100
* gnat.dg/socket1.adb: Disable on hppa*-*-hpux*.
>From gcc-bugs-return-671879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 20:49:15 2020
Return-Path: <gcc-bugs-return-671879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82828 invoked by alias); 29 Feb 2020 20: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 82792 invoked by uid 48); 29 Feb 2020 20:49:04 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/91100] [9,10 Regression] FAIL: gnat.dg/socket1.adb execution test
Date: Sat, 29 Feb 2020 20: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: danglin 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-91100-4-bfGBdMBekp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91100-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91100-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03461.txt.bz2
Content-length: 435
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91100
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from John David Anglin <danglin at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 21:12:23 2020
Return-Path: <gcc-bugs-return-671880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98913 invoked by alias); 29 Feb 2020 21:12: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 98868 invoked by uid 48); 29 Feb 2020 21:12:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] [8/9/10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Sat, 29 Feb 2020 21:12: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.1
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: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93974-4-YgF1XheJcg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03462.txt.bz2
Content-length: 369
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
My slight preference would be probably reversion, maybe even on both 8 and 9
branches, do the releases, fix on the trunk, give it two or three weeks to
settle and then backport again, but maybe I'm just trying to be too cautious
when ra is involved.
>From gcc-bugs-return-671881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 21:34:15 2020
Return-Path: <gcc-bugs-return-671881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107726 invoked by alias); 29 Feb 2020 21: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 107660 invoked by uid 48); 29 Feb 2020 21:34:12 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] [8/9/10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Sat, 29 Feb 2020 21: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: 9.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93974-4-dol62CUS11@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03463.txt.bz2
Content-length: 639
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
--- Comment #7 from Peter Bergner <bergner at gcc dot gnu.org> ---
Another option would be to release now without reverting. If we revert and
then release, then we're shipping a compiler with bug PR93658 in it. If we
release now without reverting, then PR93658 is fixed and we'll ship with this
bug in it. Both bugs fail with -O3 -mcpu=power8 -fstack-protector-strong and
both can be worked around using -O2. The only difference would be we either
ICE with this test case, or we go into an infinite loop in LRA. I guess as a
user, I'd prefer the ICE. Your choice though.
>From gcc-bugs-return-671882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 21:53:16 2020
Return-Path: <gcc-bugs-return-671882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128522 invoked by alias); 29 Feb 2020 21:53: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 128477 invoked by uid 48); 29 Feb 2020 21:53:12 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] [8/9/10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Sat, 29 Feb 2020 21:53: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.1
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: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93974-4-7zCmMEkXwP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03464.txt.bz2
Content-length: 525
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Well, there is a significant difference, the other PR has been there for more
than 2 years before somebody discovered it, while this one was discovered much
quicker and there is a possibility there could be other issues too.
With a reversion we get to a known state, keeping it we remain in far less
tested state, so unless one bug is much more severe than the other one, I'd go
for the known state.
>From gcc-bugs-return-671883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 22:07:17 2020
Return-Path: <gcc-bugs-return-671883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15986 invoked by alias); 29 Feb 2020 22:07: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 15939 invoked by uid 48); 29 Feb 2020 22:07:13 -0000
From: "xerofoify at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] [8/9/10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Sat, 29 Feb 2020 22:07: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.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: xerofoify at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93974-4-QpCEHNBDHj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03465.txt.bz2
Content-length: 1036
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
Nicholas Krause <xerofoify at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xerofoify at gmail dot com
--- Comment #9 from Nicholas Krause <xerofoify at gmail dot com> ---
Peter and Jakub,
Sorry if I'm misunderstanding the power code but is there a way to rewrite the
test to:
if (VECTOR_MEM_ALTIVEC(mode)
and another branch for VSX_P instructions.
I'm assuming that because its checking both we can get a infinite loop. I'm
assuming that in order to hand this off to the LRA we will need to
rewrite in to have two paths one for VSX_P and one for standard MEM_ALTIVEC.
Maybe Vlad as mentioned has a better idea about the LRA issues. But I'm very
suspicious of checking both VSX and non VSX_P instructions in the same way for
legitimate_address_p.
Maybe I'm misunderstanding the issue outside of backporting,
>From gcc-bugs-return-671884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 22:26:26 2020
Return-Path: <gcc-bugs-return-671884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23959 invoked by alias); 29 Feb 2020 22:26: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 23920 invoked by uid 55); 29 Feb 2020 22:26:22 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libbacktrace/91908] New libbacktrace tests fail to build
Date: Sat, 29 Feb 2020 22:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libbacktrace
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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:
Message-ID: <bug-91908-4-fZ3gdkMh5A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91908-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91908-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03466.txt.bz2
Content-length: 808
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91908
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by John David Anglin
<danglin@gcc.gnu.org>:
https://gcc.gnu.org/g:fa8a705d1f86ca9e576244eb9ae259ed63db4786
commit r9-8307-gfa8a705d1f86ca9e576244eb9ae259ed63db4786
Author: John David Anglin <danglin@gcc.gnu.org>
Date: Sat Feb 29 22:25:04 2020 +0000
Fix libbacktrace build on hppa-hpux.
2020-02-29 John David Anglin <danglin@gcc.gnu.org>
Backport from mainline
2019-09-26 Ian Lance Taylor <iant@golang.org>
PR libbacktrace/91908
* pecoff.c (backtrace_initialize): Explicitly cast unchecked
__sync_bool_compare_and_swap to void.
* xcoff.c (backtrace_initialize): Likewise.
>From gcc-bugs-return-671885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 22:32:40 2020
Return-Path: <gcc-bugs-return-671885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31494 invoked by alias); 29 Feb 2020 22:32: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 31455 invoked by uid 48); 29 Feb 2020 22:32:34 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93982] [10 Regression] Assignment incorrectly omitted by -foptimize-strlen since r10-2528
Date: Sat, 29 Feb 2020 22: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: 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: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to target_milestone short_desc everconfirmed
Message-ID: <bug-93982-4-J20dIR7fts@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93982-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93982-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03467.txt.bz2
Content-length: 1045
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93982
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-02-29
CC| |jakub at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Target Milestone|--- |10.0
Summary|Assignment incorrectly |[10 Regression] Assignment
|omitted by |incorrectly omitted by
|-foptimize-strlen |-foptimize-strlen since
| |r10-2528
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r10-2528-g34fcf41e30ff56155e996f5e04f6ca13948a19b6.
I'll have a look.
>From gcc-bugs-return-671886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 22:48:49 2020
Return-Path: <gcc-bugs-return-671886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54516 invoked by alias); 29 Feb 2020 22: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 54191 invoked by uid 48); 29 Feb 2020 22:48:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93982] [10 Regression] Assignment incorrectly omitted by -foptimize-strlen since r10-2528
Date: Sat, 29 Feb 2020 22: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: 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: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93982-4-GRX1dL6HWu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93982-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93982-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03468.txt.bz2
Content-length: 519
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93982
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Simplified testcase:
struct A { const char **a; };
const char *buf[5];
__attribute__((noipa)) struct A
foo (char *p)
{
struct A r = { (const char **) p };
r.a[0] = "12345678";
r.a[1] = "";
r.a[2] = "";
r.a[3] = "";
r.a[4] = "";
return r;
}
int
main ()
{
struct A r = foo ((char *) &buf[0]);
if (!r.a[1] || r.a[1][0] != '\0')
__builtin_abort ();
return 0;
}
>From gcc-bugs-return-671887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 22:57:18 2020
Return-Path: <gcc-bugs-return-671887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58615 invoked by alias); 29 Feb 2020 22:57: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 58563 invoked by uid 48); 29 Feb 2020 22:57:14 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] [8/9/10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Sat, 29 Feb 2020 22: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.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93974-4-xl6wB7SsAn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03469.txt.bz2
Content-length: 398
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
--- Comment #10 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #8)
> With a reversion we get to a known state, keeping it we remain in far less
> tested state, so unless one bug is much more severe than the other one, I'd
> go for the known state.
Ok, I pushed the reversions for both GCC 8 & 9.
>From gcc-bugs-return-671888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 23:02:56 2020
Return-Path: <gcc-bugs-return-671888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61019 invoked by alias); 29 Feb 2020 23: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 60988 invoked by uid 48); 29 Feb 2020 23:02:52 -0000
From: "stsp at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93984] New: spurious Wclass-conversion warning
Date: Sat, 29 Feb 2020 23: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: stsp at users dot sourceforge.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-93984-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03470.txt.bz2
Content-length: 1379
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93984
Bug ID: 93984
Summary: spurious Wclass-conversion warning
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: stsp at users dot sourceforge.net
Target Milestone: ---
#include <iostream>
struct D;
struct B {
virtual operator D() = 0;
};
struct D : B
{
operator D() override { std::cout << "conv" << std::endl; return D(); }
};
.
int main()
{
D obj;
B& br = obj;
(D)br; // calls D::operator D() through virtual dispatch
return 0;
}
$ LC_ALL=C g++ -Wall -o vconv vconv.cpp
vconv.cpp:9:5: warning: converting 'D' to the same type will never use a type
conversion operator [-Wclass-conversion]
9 | operator D() override { std::cout << "conv" << std::endl; return
D(); }
| ^~~~~~~~
$ ./vconv
conv
The example above shows that the warning
is spurious. Converting to the same type
will indeed never use the conversion
operator. But the above case converts
from B to D, so the warning does not apply.
It may be quite difficult to check properly,
but in this particular example the "override"
keyword is a clear hint that it is going
to be used via the virtual dispatch.
>From gcc-bugs-return-671889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 23:06:24 2020
Return-Path: <gcc-bugs-return-671889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62923 invoked by alias); 29 Feb 2020 23:06: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 62894 invoked by uid 48); 29 Feb 2020 23:06:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93982] [10 Regression] Assignment incorrectly omitted by -foptimize-strlen since r10-2528
Date: Sat, 29 Feb 2020 23:06: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: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93982-4-1gtE2ivmKT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93982-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93982-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03471.txt.bz2
Content-length: 1298
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93982
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
bool is_char_store = is_char_type (type);
if (!is_char_store && TREE_CODE (lhs) == MEM_REF)
{
/* To consider stores into char objects via integer types
other than char but not those to non-character objects,
determine the type of the destination rather than just
the type of the access. */
for (int i = 0; i != 2; ++i)
{
tree ref = TREE_OPERAND (lhs, i);
type = TREE_TYPE (ref);
if (TREE_CODE (type) == POINTER_TYPE)
type = TREE_TYPE (type);
if (TREE_CODE (type) == ARRAY_TYPE)
type = TREE_TYPE (type);
if (is_char_type (type))
{
is_char_store = true;
break;
}
}
}
is completely bogus. With pointer conversions being useless, the type of the
MEM_REF's first operand means nothing at all and the type of second MEM_REF
operand is for alias analysis, again nothing that should matter for how the
strlen pass optimizes code.
>From gcc-bugs-return-671890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Feb 29 23:26:39 2020
Return-Path: <gcc-bugs-return-671890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70306 invoked by alias); 29 Feb 2020 23:26: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 70249 invoked by uid 48); 29 Feb 2020 23:26:35 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] [8/9/10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Sat, 29 Feb 2020 23:26: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.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93974-4-Aslag9RNKc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-02/txt/msg03472.txt.bz2
Content-length: 1568
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
--- Comment #11 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Nicholas Krause from comment #9)
> Sorry if I'm misunderstanding the power code but is there a way to rewrite
> the test to:
> if (VECTOR_MEM_ALTIVEC(mode)
> and another branch for VSX_P instructions.
There's no need.
> I'm assuming that because its checking both we can get a infinite loop. I'm
> assuming that in order to hand this off to the LRA we will need to
> rewrite in to have two paths one for VSX_P and one for standard MEM_ALTIVEC.
No. We get into an infinite loop, because LRA passes us a valid Altivec type
address and rs6000_legitimate_address_p erroneously tells LRA, that it is
invalid. So LRA tries to spill it again. After a few iterations of that, the
address is simplified to just a register inside the (and: ...) and that is
trivially valid, but rs6000_legitimate_address_p continues to say it's invalid.
At this point, LRA replaces that one reg with a copy of the one reg. Again,
rs6000_legitimate_address_p says it's invalid, so around and around it goes.
The bug isn't that we cannot recognize the address as valid. It's that we have
a bogus test that uses VECTOR_MEM_ALTIVEC_P(), which only is true for vector
modes, when Altivec is enabled and VSX is disabled. When VSX is enabled (which
implies Altivec is enabled), VECTOR_MEM_ALTIVEC_P() return false. That is
because rs6000_vector_mem[<vector mode>] returns VECTOR_VSX rather than
VECTOR_ALTIVEC when VSX is enabled.
>From gcc-bugs-return-671891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 04:03:45 2020
Return-Path: <gcc-bugs-return-671891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57672 invoked by alias); 1 Mar 2020 04:03: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 57635 invoked by uid 48); 1 Mar 2020 04:03:40 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93980] use of lto breaks -Wl,--exclude-libs
Date: Sun, 01 Mar 2020 04:03: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: 9.2.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-93980-4-aHVU1eQAEG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00000.txt
Content-length: 155
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93980
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Does -fno-use-linker-plugin help?
>From gcc-bugs-return-671892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 07:15:40 2020
Return-Path: <gcc-bugs-return-671892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4434 invoked by alias); 1 Mar 2020 07:15: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 4370 invoked by uid 48); 1 Mar 2020 07:15:32 -0000
From: "sergeev917 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93980] use of lto breaks -Wl,--exclude-libs
Date: Sun, 01 Mar 2020 07:15: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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sergeev917 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-93980-4-vb6dfoUaYU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00001.txt
Content-length: 452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93980
--- Comment #2 from Alexander Sergeyev <sergeev917 at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> Does -fno-use-linker-plugin help?
It seems to work with fat lto objects, but I suspect that no actual lto is
performed in this case.
With -fno-fat-lto-objects -fno-use-linker-plugin:
.bar.o: plugin needed to handle lto object
.foo.a(.foo.o): plugin needed to handle lto object
>From gcc-bugs-return-671893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 12:50:05 2020
Return-Path: <gcc-bugs-return-671893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73770 invoked by alias); 1 Mar 2020 12:50: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 73710 invoked by uid 48); 1 Mar 2020 12:50:01 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93694] Inconsistent grammar in darwin.opt
Date: Sun, 01 Mar 2020 12: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: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: iains at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-93694-4-c6uAQLlrU4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00002.txt
Content-length: 4958
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93694
--- Comment #4 from Iain Sandoe <iains at gcc dot gnu.org> ---
Created attachment 47938
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47938&action=edit
Update darwin opts descriptions
Thanks for the comments.
As background, (most of) these options have ben present in the Darwin toolchain
since before my involvement - however they were never described; there is note
in the GCC manual suggesting that the user should use the man page.
The majority here are actually options passed on to the linker, and the details
can be quite complex - so that the user should still make use of the manage (so
I would not delete that statement from the GCC manual). The idea here is a
brief summary to serve as a reminder for a more detailed description. Perhaps
I should have left them undocumented ....
an example of the manpage:
https://www.manpagez.com/man/1/ld64/
In some cases (especially for determining which options are obsolete) several
versions of the man pages were consulted - and the linker source code itself.
====
I will apply a patch that makes the following changes in a few days if there
are no more comments (such comments are welcome):
> Loads all members of archive libraries
Load all members of archive libraries, rather than only those that satisfy
undefined symbols.
> The version of ld64 in use for this toolchain.
-mtarget-linker <version> Specify that ld64 <version> is the toolchain
linker for the current invocation.
> Produce an output file that will bind symbols on load, rather than lazily.
Generate an output executable that binds symbols on load, rather than lazily.
> Produce a Mach-O bundle (file type MH_BUNDLE)
Generate a Mach-O bundle (file type MH_BUNDLE).
> This will allow relocs
-read_only_relocs <treatment> Allow relocations in read-only pages (not
recommended).
>And a typo:
> exectuable
fixed.
>Unnecessarily unspecific wording:
> Allows setting the page 0 size to 4kb for certain special cases
>What exactly are "certain special cases"?
I don't think that can be reasonable answered in a brief option description, I
suggest what's below, it is the user's responsibility to know when the option
is required.
-pagezero_size <size> Allows setting the page 0 size (for example, to 4kb)
when required.
double space:
> architecture \"name\"
fixed.
> unnecessarily verbose:
> Specify that the output file should be generated for architecture "name"
> Why not simply: Generate output file for the named architecture.
-arch <name> Generate output for architecture <name>.
>anachronism:
> MacOS X
> Should that be macOS nowadays?
Changed throughout.
> off-by-one:
> must record a greater
> I think this should rather be "greater or equal".
Actually, the man page is quite confusing on this option, I've tried to make
this more specific:
-compatibility_version <number> Set the version for the client interface.
Client programs must record a value less than or equal to <number>, or the
binding will fail at runtime.
>double space:
> dyld will
fixed,
> <treatment> Provided
> (Obsolete after 10.3.9) Set
> Shouldn't there be a tab between the words instead of the space?
fixed.
> -pagezero_size size
> The other placeholders are written in <angle_brackets>, so should this one.
done, as per the comment above.
> (Obsolete, ld_classic only) -sectcreate segname sectname file
> segname, sectname and file should be marked as <placeholders>.
> (Obsolete, ld_classic only) -sectcreate segname sectname file
-sectcreate <segname> <sectname> <file> Create section <sectname> in segment
<segname> from the contents of <file>.
> -segprot <segname> max_prot init_prot\tThe protection values are
> This like only describes the syntax but doesn't lose a single word about the effect.
Indeed ...
-segprot <segname> <max_prot> <init_prot> The virtual memory protections
for segment <segname> are set to maximum and initial values <max_prot> and
<init_prot> respectively. The specified values may contain \"r\", \"w\", \"x\"
or \"-\" the latter meaning \"no access\".
> -segs_read_only_addr address
>Missing placeholder.
> space-tab.
-segs_read_only_addr <address> Specify that <address> is the base address of
the read-only segments of a dylib.
> Allows specifying
>I hope that this option actually _sets_ the address instead of only _allowing_ to set. (2 times)
done as per segs_read_only_addr above.
> Specifies content
> That's another case of very unspecific wording. As the German translator I have no idea what this could mean. This option is documented nowhere. It only appears in the ChangeLogs, darwin.h and darwin.opt.
As noted, the source for the information is outside the GCC tree - ld64 source
/ manages suggested change:
Add extra information to the executable that can speed up dynamic loading
(provided that dependent libraries are unchanged).
>From gcc-bugs-return-671894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 13:28:57 2020
Return-Path: <gcc-bugs-return-671894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1674 invoked by alias); 1 Mar 2020 13:28: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 1642 invoked by uid 48); 1 Mar 2020 13:28:52 -0000
From: "sagebar at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93985] New: Sub-optimal assembly for %st(0) constant loading with SSE enabled (x86_64)
Date: Sun, 01 Mar 2020 13:28: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sagebar at web 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-93985-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00003.txt
Content-length: 2849
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93985
Bug ID: 93985
Summary: Sub-optimal assembly for %st(0) constant loading with
SSE enabled (x86_64)
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: sagebar at web dot de
Target Milestone: ---
Created attachment 47939
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47939&action=edit
Inefficient code generation, similar working cases & work-around
With gcc for x86_64, where SSE is enabled by default, some situations exist
where legacy (fpu) math instructions (and their constraints) still have to be
used.
x86 offets a hand full of instructions to load specific floating point
constants more efficiently (including `1.0`).
As such, it would stand to reason to implement a function `atan()` as:
```c
double atan(double x) {
double result;
__asm__("fpatan"
: "=t" (result)
: "0" (1.0)
, "u" (x)
: "st(1)");
return result;
}
```
This code works perfectly on i386, where it compiles to:
```asm
fldl 4(%esp) # push(x)
fld1 # push(1.0)
fpatan
ret
```
However, on x86_64 it is compiled as:
```asm
movsd .LC0(%rip), %xmm1
movsd %xmm1, -8(%rsp)
fldl -8(%rsp) # push(1.0)
movsd %xmm0, -8(%rsp)
fldl -8(%rsp) # push(x)
fxch %st(1) # { x, 1.0 } -> { 1.0, x }
fpatan
fstpl -8(%rsp)
movsd -8(%rsp), %xmm0
ret
...
.LC0:
.long 0 # SSE constant: 1.0
.long 1072693248 # ...
```
When the optimal code would look like:
```asm
movsd %xmm0, -8(%rsp)
fldl -8(%rsp) # push(x)
fld1 # push(1.0)
fpatan
fstpl -8(%rsp)
movsd -8(%rsp), %xmm0
ret
```
Still though, it appears that GCC _is_ aware of the fld1 instruction for
encoding inline assembly operands, even when SSE is enabled (s.a.
`atan_reverse()` within the attached file).
So it would stand to reason that this is either a problem with how GCC weights
different encoding schemes, or a problem with how GCC decides if certain
encoding schemes are even possible at all (which seems quite likely, especially
considering that the x86_64 version contains an fxch-instruction which also
wouldn't be necessary if GCC had encoded the `1.0` _after_ pushing `x`
(ignoring the fact that `1.0` can be pushed using `fld1`))
NOTE: The attached file should be compiled as `gcc -O3 -S attached-file.c`
>From gcc-bugs-return-671895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 14:27:55 2020
Return-Path: <gcc-bugs-return-671895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112390 invoked by alias); 1 Mar 2020 14:27: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 112347 invoked by uid 48); 1 Mar 2020 14:27:49 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93986] New: [10 Regression] ICE in decompose, at wide-int.h:984
Date: Sun, 01 Mar 2020 14:27: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-93986-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00004.txt
Content-length: 4110
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93986
Bug ID: 93986
Summary: [10 Regression] ICE in decompose, at wide-int.h:984
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.1-alpha20200223 snapshot (g:3133bed5d0327e8a9cd0a601b7ecdb9de4fc825d)
ICEs when compiling the following testcase w/ -O1 -foptimize-strlen
-ftree-slp-vectorize:
int
dd (void);
void
ya (int cm)
{
char s2[cm];
s2[cm-12] = s2[cm-11] = s2[cm-10] = s2[cm-9] = s2[cm-8] = s2[cm-7] = s2[cm-6]
= s2[cm-5] = ' ';
if (dd ())
__builtin_exit (0);
}
% gcc-10.0.1 -O1 -foptimize-strlen -ftree-slp-vectorize -c ch4gpdst.c
during GIMPLE pass: strlen
ch4gpdst.c: In function 'ya':
ch4gpdst.c:5:1: internal compiler error: in decompose, at wide-int.h:984
5 | ya (int cm)
| ^~
0x5ee66a wi::int_traits<generic_wide_int<wide_int_storage> >::decompose(long*,
unsigned int, generic_wide_int<wide_int_storage> const&)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/wide-int.h:984
0x8d1f74 wi::int_traits<generic_wide_int<wide_int_storage> >::decompose(long*,
unsigned int, generic_wide_int<wide_int_storage> const&)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/wide-int.h:2456
0x8d1f74 wide_int_ref_storage<true,
false>::wide_int_ref_storage<generic_wide_int<wide_int_storage>
>(generic_wide_int<wide_int_storage> const&, unsigned int)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/wide-int.h:1034
0x8d1f74 generic_wide_int<wide_int_ref_storage<true, false>
>::generic_wide_int<generic_wide_int<wide_int_storage>
>(generic_wide_int<wide_int_storage> const&, unsigned int)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/wide-int.h:790
0x8d1f74 wi::binary_traits<generic_wide_int<wide_int_storage>,
generic_wide_int<wide_int_storage>,
wi::int_traits<generic_wide_int<wide_int_storage> >::precision_type,
wi::int_traits<generic_wide_int<wide_int_storage>
>::precision_type>::result_type wi::add<generic_wide_int<wide_int_storage>,
generic_wide_int<wide_int_storage> >(generic_wide_int<wide_int_storage> const&,
generic_wide_int<wide_int_storage> const&)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/wide-int.h:2425
0xf605cc generic_wide_int<wide_int_storage>&
generic_wide_int<wide_int_storage>::operator+=<generic_wide_int<wide_int_storage>
>(generic_wide_int<wide_int_storage> const&)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/wide-int.h:757
0xf605cc maybe_warn_overflow
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/tree-ssa-strlen.c:1977
0xf64ac8 maybe_warn_overflow
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/tree-ssa-strlen.c:2312
0xf64ac8 handle_store
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/tree-ssa-strlen.c:4976
0xf672a9 check_and_optimize_stmt
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/tree-ssa-strlen.c:5614
0xf672a9 strlen_dom_walker::before_dom_children(basic_block_def*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/tree-ssa-strlen.c:5791
0x1664567 dom_walker::walk(basic_block_def*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/domwalk.c:309
0xf5b75e printf_strlen_execute
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200223/work/gcc-10-20200223/gcc/tree-ssa-strlen.c:5857
>From gcc-bugs-return-671896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 14:35:11 2020
Return-Path: <gcc-bugs-return-671896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116313 invoked by alias); 1 Mar 2020 14: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 116283 invoked by uid 48); 1 Mar 2020 14:35:06 -0000
From: "gabriel at inconstante dot net.br" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93987] New: Regression (ICE) on gcc-9 branch
Date: Sun, 01 Mar 2020 14:35: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.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gabriel at inconstante dot net.br
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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 attachments.created
Message-ID: <bug-93987-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00005.txt
Content-length: 1406
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93987
Bug ID: 93987
Summary: Regression (ICE) on gcc-9 branch
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: gabriel at inconstante dot net.br
CC: bergner at vnet dot ibm.com
Target Milestone: ---
Target: powerpc64le-glibc-linux-gnu
Created attachment 47940
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47940&action=edit
Reproducer
Current pveclib (https://github.com/open-power-sdk/pveclib) tests fail to build
with the tip of the gcc-9 branch. I have bisected the problem, and it seems
that the following commit is to blame:
066184a282b622ac6880150eb4e42fe57881b606 is the first bad commit
commit 066184a282b622ac6880150eb4e42fe57881b606
Author: Peter Bergner <bergner@linux.ibm.com>
Date: Sun Feb 23 18:22:57 2020 -0600
rs6000: Fix infinite loop building ghostscript and icu [PR93658]
The testcases ("make check") in pveclib fail to build with GCC-9 in Debian
Unstable, and with a compiler built locally from that commit (I'm using glibc's
build-many-glibcs.py script).
I tried to reduce the testcase to a small standalone file, but I couldn't
reduce it further than the attachement
>From gcc-bugs-return-671897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 14:42:08 2020
Return-Path: <gcc-bugs-return-671897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66998 invoked by alias); 1 Mar 2020 14: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 66919 invoked by uid 55); 1 Mar 2020 14:42:04 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/93731] [10 regression] asan tests cause kernel panic on Darwin 11
Date: Sun, 01 Mar 2020 14:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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:
Message-ID: <bug-93731-4-aVIor21ffY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00006.txt
Content-length: 1025
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93731
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>:
https://gcc.gnu.org/g:63cc547f6d85819192afa795e9ade14f0800eda9
commit r10-6951-g63cc547f6d85819192afa795e9ade14f0800eda9
Author: Iain Sandoe <iain@sandoe.co.uk>
Date: Sun Mar 1 14:40:57 2020 +0000
Darwin, libsanitizer: Adjust minimum supported Darwin version (PR93731).
The current imported libsanitizer code produces kernel panics for
Darwin 11 (macOS 10.7) and is unsupported for earlier versions already.
It is not clear if the current sources are even intended to be supported
on Darwin 11, so this patch causes the default to be build without
sanitizers for Darwin <= 11.
2020-03-01 Iain Sandoe <iain@sandoe.co.uk>
PR sanitizer/93731
* configure.tgt (x86_64-*-darwin*, i?86-*-darwin*): Enable by
default only for Darwin versions greater than 12 (macOS 10.8).
>From gcc-bugs-return-671898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 14:43:17 2020
Return-Path: <gcc-bugs-return-671898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67993 invoked by alias); 1 Mar 2020 14:43: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 67942 invoked by uid 48); 1 Mar 2020 14:43:12 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93987] Regression (ICE) on gcc-9 branch
Date: Sun, 01 Mar 2020 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: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner 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-93987-4-smsSUyKV5J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93987-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93987-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00007.txt
Content-length: 607
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93987
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bergner at gcc dot gnu.org
--- Comment #1 from Peter Bergner <bergner at gcc dot gnu.org> ---
I actually just reverted that fix yesterday due to PR93974. Please pull new
sources and try again.
That said, does it also fail on trunk? If so, what compile options did you
use? And what was the failure? An ICE or ???
>From gcc-bugs-return-671899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 15:06:48 2020
Return-Path: <gcc-bugs-return-671899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125159 invoked by alias); 1 Mar 2020 15:06: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 125123 invoked by uid 48); 1 Mar 2020 15:06:43 -0000
From: "gabriel at inconstante dot net.br" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93987] Regression (ICE) on gcc-9 branch
Date: Sun, 01 Mar 2020 15: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: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gabriel at inconstante dot net.br
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-93987-4-TZULGeGn7v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93987-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93987-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00008.txt
Content-length: 1670
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93987
--- Comment #2 from Gabriel F. T. Gomes <gabriel at inconstante dot net.br> ---
Oh, I forgot to paste the output:
$
/home/debian/build/powerpc64le/tools/install/compilers/powerpc64le-linux-gnu/bin/powerpc64le-glibc-linux-gnu-gcc
-c -O2 ice.c
ice.c: In function ‘test_addcq’:
ice.c:128:1: error: insn does not satisfy its constraints:
128 | }
| ^
(insn 305 304 306 3 (set (reg:V1TI 80 3)
(rotate:V1TI (mem/u/c:V1TI (and:DI (reg/f:DI 29 29 [240])
(const_int -16 [0xfffffffffffffff0])) [0 S16 A128])
(const_int 64 [0x40]))) 1043 {*vsx_le_permute_v1ti}
(nil))
during RTL pass: cprop_hardreg
ice.c:128:1: internal compiler error: in extract_constrain_insn, at
recog.c:2211
0x1012c7ef _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/debian/build/powerpc64le/tools/src/gcc/gcc/rtl-error.c:108
0x1012c84b _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
/home/debian/build/powerpc64le/tools/src/gcc/gcc/rtl-error.c:118
0x106f4cd7 extract_constrain_insn(rtx_insn*)
/home/debian/build/powerpc64le/tools/src/gcc/gcc/recog.c:2211
0x106f9fbb copyprop_hardreg_forward_1
/home/debian/build/powerpc64le/tools/src/gcc/gcc/regcprop.c:817
0x106faf5f execute
/home/debian/build/powerpc64le/tools/src/gcc/gcc/regcprop.c:1385
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.
I'll check with trunk and with the tip of gcc-9, thanks!
>From gcc-bugs-return-671900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 15:15:02 2020
Return-Path: <gcc-bugs-return-671900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25503 invoked by alias); 1 Mar 2020 15:15: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 25389 invoked by uid 48); 1 Mar 2020 15:14:58 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/82798] Inconsistent descriptions for warning options in documentation
Date: Sun, 01 Mar 2020 15:15: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: 7.2.0
X-Bugzilla-Keywords: documentation
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: cc
Message-ID: <bug-82798-4-okf0PjrV7R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82798-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82798-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00009.txt
Content-length: 456
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82798
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandra at gcc dot gnu.org
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
Sandra has a big documentation patch that might address some of these
>From gcc-bugs-return-671901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 15:18:00 2020
Return-Path: <gcc-bugs-return-671901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27707 invoked by alias); 1 Mar 2020 15:18: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 27670 invoked by uid 48); 1 Mar 2020 15:17:57 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/71283] Inconsistent location for C++ warning options in the manual
Date: Sun, 01 Mar 2020 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: 6.1.0
X-Bugzilla-Keywords: documentation, easyhack
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: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-71283-4-MpJcazsUi2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71283-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71283-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00010.txt
Content-length: 546
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71283
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandra at gcc dot gnu.org
--- Comment #11 from Eric Gallager <egallager at gcc dot gnu.org> ---
Martin, did you want to stay the assignee for this? Sandra seemed to want to
address this bug here: https://gcc.gnu.org/ml/gcc-patches/2020-02/msg01522.html
>From gcc-bugs-return-671902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 15:28:54 2020
Return-Path: <gcc-bugs-return-671902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71712 invoked by alias); 1 Mar 2020 15:28: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 71660 invoked by uid 48); 1 Mar 2020 15:28:46 -0000
From: "ch3root at openwall dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93848] missing -Warray-bounds warning for array subscript 1 is outside array bounds
Date: Sun, 01 Mar 2020 15: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: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
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-93848-4-Bnh4fzCfAZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00011.txt
Content-length: 1673
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93848
--- Comment #11 from Alexander Cherepanov <ch3root at openwall dot com> ---
(In reply to Martin Sebor from comment #10)
> An array is implicitly converted to a pointer;
Sometimes converted, sometimes -- not.
> it's not an lvalue.
Why not? Take for example p[1] that we discussed. It's equivalent to *(p+1) and
the unary * operator is explicitly documented to yield an lvalue (C11,
6.5.3.2p4):
"If the operand points to a function, the result is a function designator; if
it points to an object, the result is an lvalue designating the object."
> But I
> think we're splitting hairs. I agree we want a warning for passing
> past-the-end pointers to functions that might inadvertently dereference it;
> I plan to implement it for GCC 11.
This is something more general and I'm not sure we want such a warning. You are
right that passing a past-the-end pointers to functions perfectly legal so
there would be false alarms. I cannot readily assess whether it's worth it.
OTOH the specific construction that started this PR is not legal and should
always give a warning, whether it's passed to an unknown function, printed
without additional dereferences or used in a computation.
> The reference in
>
> int a[1][4];
> printf("%p\n", (void *)&a[1][1]);
>
> is of course undefined, but when the warning sees the address-of operator it
> allows off-by-one indices. That's necessary only for the rightmost index
> but not otherwise. The missing warning here is the subject of pr84079. I
> have a simple fix that handles this case.
Great, here we agree. But does it cover &a[1][0]?
>From gcc-bugs-return-671903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 15:41:05 2020
Return-Path: <gcc-bugs-return-671903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87706 invoked by alias); 1 Mar 2020 15:41: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 81616 invoked by uid 48); 1 Mar 2020 15:41:01 -0000
From: "jwjagersma at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93981] No EH information generated for asm statements
Date: Sun, 01 Mar 2020 15:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jwjagersma 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.isobsolete attachments.created
Message-ID: <bug-93981-4-YZwK9jnrzt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00012.txt
Content-length: 823
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93981
jwjagersma at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #47936|0 |1
is obsolete| |
--- Comment #6 from jwjagersma at gmail dot com ---
Created attachment 47941
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47941&action=edit
patch v2
Small change; only call make_eh_edges for asm statements if the asm
could throw (is volatile).
This does not solve the ICE however, which is caused by a throwing
statement that appears before the end of a basic block. It seems that,
at some point, extra statements are added after the asm in a bb? But I
can't find where that happens.
>From gcc-bugs-return-671904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 15:48:04 2020
Return-Path: <gcc-bugs-return-671904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106162 invoked by alias); 1 Mar 2020 15:48: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 106045 invoked by uid 48); 1 Mar 2020 15:48:00 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93581] [9/10 Regression] ICE in gfc_get_dataptr_offset, at fortran/trans-array.c:6951
Date: Sun, 01 Mar 2020 15: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: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to attachments.created
Message-ID: <bug-93581-4-uOnPGtyUIe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93581-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93581-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00013.txt
Content-length: 695
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93581
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
--- Comment #5 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 47942
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47942&action=edit
Patch for the PR
Hi Gerhard,
I must applaud you on your efforts to look into every dark corner of gfortran.
I hope that you are not too disheartened by the slow pace at which we fix your
bugs.
Cheers
Paul
>From gcc-bugs-return-671905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 16:22:29 2020
Return-Path: <gcc-bugs-return-671905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80802 invoked by alias); 1 Mar 2020 16:22: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 74946 invoked by uid 48); 1 Mar 2020 16:22:26 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93980] use of lto breaks -Wl,--exclude-libs
Date: Sun, 01 Mar 2020 16:22: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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools 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-93980-4-vd3iMqXFna@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00014.txt
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93980
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl.tools at gmail dot com
--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
This seems a linker bug. Please open a binutils bug report.
>From gcc-bugs-return-671906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 16:26:47 2020
Return-Path: <gcc-bugs-return-671906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110095 invoked by alias); 1 Mar 2020 16:26: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 110046 invoked by uid 48); 1 Mar 2020 16:26:43 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93981] No EH information generated for asm statements
Date: Sun, 01 Mar 2020 16:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
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-93981-4-F4V8fqd4dH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00015.txt
Content-length: 1844
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93981
--- Comment #7 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to jwjagersma from comment #5)
> (In reply to Segher Boessenkool from comment #4)
> > Pretending any asm can throw would be a pretty serious code degradation.
> >
> > Any asm that is not volatile cannot throw (and be correct code). But
> > most volatile asm in the wild can never throw, either.
>
> The intention is to only produce EH info for volatile asms, and only if
> -fnon-call-exceptions is given. Asms that take volatile memory operands
> should be covered too.
Ah right, only for -fnon-call-exceptions, I missed that; that is implied
by stmt_can_throw_internal.
Why only volatile memory operands, btw? Can't *all* memory accesses throw?
Is that handled somewhere else, or does it need special-casing for asm?
> Do note that the proposed patch is still incomplete, I ran into an ICE
> while building libgcc with -fnon-call-exceptions:
>
> ```
> during GIMPLE pass: ehcleanup
> ../../../gnu/gcc-9.2.0/libgcc/config/i386/sfp-exceptions.c: In function
> '__sfp_handle_exceptions':
> ../../../gnu/gcc-9.2.0/libgcc/config/i386/sfp-exceptions.c:107:1: internal
> compiler error: in mark_reachable_handlers, at tree-eh.c:3929
> 107 | }
> | ^
> libbacktrace could not find executable to open
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <https://gcc.gnu.org/bugs/> for instructions.
> ```
>
> However I am not knowledgable enough about gcc's inner workings to know
> what exactly is missing. I'm hoping someone can help me out with this.
Please use trunk ("master") for development, not an older release?
I would think the problem here is caused by your modifications to tree-eh.c,
but that is not based on understanding this code at all ;-)
>From gcc-bugs-return-671907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 16:44:49 2020
Return-Path: <gcc-bugs-return-671907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3085 invoked by alias); 1 Mar 2020 16:44: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 3047 invoked by uid 48); 1 Mar 2020 16:44:45 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93984] spurious Wclass-conversion warning
Date: Sun, 01 Mar 2020 16: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: 9.2.1
X-Bugzilla-Keywords: diagnostic
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-93984-4-cNyC45tnnA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93984-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93984-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00016.txt
Content-length: 1195
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93984
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-03-01
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed, but clang++ warns too.
commit fce33808678df40cce69c15141926342f8a6f47e
Author: Marek Polacek <polacek@redhat.com>
Date: Wed Sep 19 16:59:51 2018 +0000
PR c++/87357 - missing -Wconversion warning
PR c++/87357 - missing -Wconversion warning
* decl.c (grok_op_properties): Remove diagnostic parts mentioning
a conversion to a reference to void. Use
same_type_ignoring_top_level_qualifiers_p rather than comparing
types
directly.
* g++.dg/warn/Wconversion5.C: New test.
From-SVN: r264425
>From gcc-bugs-return-671908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 16:45:54 2020
Return-Path: <gcc-bugs-return-671908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4500 invoked by alias); 1 Mar 2020 16:45: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 4470 invoked by uid 48); 1 Mar 2020 16:45:50 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93980] use of lto breaks -Wl,--exclude-libs
Date: Sun, 01 Mar 2020 16:45: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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools 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-93980-4-MGvuBzv9uV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00017.txt
Content-length: 570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93980
--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
This linker patch:
iff --git a/ld/plugin.c b/ld/plugin.c
index 47c053e5a0a..5960df65243 100644
--- a/ld/plugin.c
+++ b/ld/plugin.c
@@ -1242,6 +1242,8 @@ plugin_object_p (bfd *ibfd)
ibfd->plugin_format = bfd_plugin_yes;
ibfd->plugin_dummy_bfd = abfd;
bfd_make_readable (abfd);
+ if (ibfd->my_archive != NULL)
+ abfd->no_export = ibfd->my_archive->no_export;
return abfd->xvec;
}
else
fixes the testcase.
>From gcc-bugs-return-671909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 16:51:29 2020
Return-Path: <gcc-bugs-return-671909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20105 invoked by alias); 1 Mar 2020 16: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 20072 invoked by uid 48); 1 Mar 2020 16:51:25 -0000
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93988] New: invalid DWARF emitted for complex integer
Date: Sun, 01 Mar 2020 16:51: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tromey 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-93988-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00018.txt
Content-length: 1637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93988
Bug ID: 93988
Summary: invalid DWARF emitted for complex integer
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: tromey at gcc dot gnu.org
Target Milestone: ---
Consider this test case:
_Complex int x = 23i;
Compile with -g and examine the resulting DWARF:
<1><31>: Abbrev Number: 3 (DW_TAG_base_type)
<32> DW_AT_byte_size : 8
<33> DW_AT_encoding : 128 (HP_float80)
<34> DW_AT_name : (indirect string, offset: 0x0): complex int
I was surprised to see that "HP_float80" here, but it turns out
that this is just an artifact of dwarf.def claiming:
/* HP extensions. */
DW_ATE (DW_ATE_HP_float80, 0x80) /* Floating-point (80 bit). */
In reality what gcc is doing is just returning:
/* Dwarf2 doesn't know anything about complex ints, so use
a user defined type for it. */
case COMPLEX_TYPE:
if (TREE_CODE (TREE_TYPE (type)) == REAL_TYPE)
encoding = DW_ATE_complex_float;
else
encoding = DW_ATE_lo_user;
break;
There are a couple of ways this could be replaced. One would be to
give a complex base type its own DW_AT_type, holding the underlying
element type.
Another would be to pick a range, like 0xa0-0xaf, and emit
a value like 0xa0 | DW_ATE_signed.
I see in base_type_die that there are other cases that return
DW_ATE_lo_user. These are probably also bugs.
>From gcc-bugs-return-671910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 16:58:42 2020
Return-Path: <gcc-bugs-return-671910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24853 invoked by alias); 1 Mar 2020 16:58: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 24799 invoked by uid 48); 1 Mar 2020 16:58:37 -0000
From: "jwjagersma at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93981] No EH information generated for asm statements
Date: Sun, 01 Mar 2020 16:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jwjagersma 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-93981-4-zQoAfNVK6X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00019.txt
Content-length: 1401
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93981
--- Comment #8 from jwjagersma at gmail dot com ---
(In reply to Segher Boessenkool from comment #7)
> Ah right, only for -fnon-call-exceptions, I missed that; that is implied
> by stmt_can_throw_internal.
>
> Why only volatile memory operands, btw? Can't *all* memory accesses throw?
Memory access from a known valid pointer (eg. stack variables) can
reasonably be expected not to throw. So I didn't mean 'volatile' in the
literal sense but more in general, pointers that cannot be know to be
valid at compile-time.
> Is that handled somewhere else, or does it need special-casing for asm?
For general memory access I think this is checked in tree_could_trap_p.
The case for ASM_EXPR there would need to be expanded to check if any
of its operands could trap.
> Please use trunk ("master") for development, not an older release?
I was having trouble building a native (mingw-w64) compiler from git,
so I tried using 9.2.0 sources. I'm working on trunk now using an
Ubuntu VM.
> I would think the problem here is caused by your modifications to tree-eh.c,
> but that is not based on understanding this code at all ;-)
To me it seems that some part of the code does not realize that a
throwing asm must be kept at a bb boundary, and inserts statements
after it. That would need to be patched too, if I could find where that
happens.
>From gcc-bugs-return-671911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 17:01:01 2020
Return-Path: <gcc-bugs-return-671911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38393 invoked by alias); 1 Mar 2020 17:00: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 29060 invoked by uid 48); 1 Mar 2020 17:00:05 -0000
From: "sergeev917 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93980] use of lto breaks -Wl,--exclude-libs
Date: Sun, 01 Mar 2020 17:00: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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sergeev917 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-93980-4-1rHvos8zdo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00020.txt
Content-length: 306
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93980
--- Comment #5 from Alexander Sergeyev <sergeev917 at gmail dot com> ---
(In reply to H.J. Lu from comment #3)
> This seems a linker bug. Please open a binutils bug report.
The bug report is at https://sourceware.org/bugzilla/show_bug.cgi?id=25618
>From gcc-bugs-return-671912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 17:18:49 2020
Return-Path: <gcc-bugs-return-671912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73505 invoked by alias); 1 Mar 2020 17:18: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 73466 invoked by uid 48); 1 Mar 2020 17:18:45 -0000
From: "sergeev917 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93980] use of lto breaks -Wl,--exclude-libs
Date: Sun, 01 Mar 2020 17:18: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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sergeev917 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-93980-4-PPDkRpOCiR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00021.txt
Content-length: 248
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93980
--- Comment #6 from Alexander Sergeyev <sergeev917 at gmail dot com> ---
(In reply to H.J. Lu from comment #4)
> This linker patch:
Thank you! I've linked the patch to the binutils bug report.
>From gcc-bugs-return-671913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 17:55:54 2020
Return-Path: <gcc-bugs-return-671913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118623 invoked by alias); 1 Mar 2020 17:55: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 118600 invoked by uid 48); 1 Mar 2020 17:55:50 -0000
From: "clogged.drainpipe at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/91332] ICE: Segfault in gfortran when compiling massive subroutine with -O3
Date: Sun, 01 Mar 2020 17:55: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: 7.4.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clogged.drainpipe 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-91332-4-xh4528W9bU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91332-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91332-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00022.txt
Content-length: 155
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91332
--- Comment #3 from Madarpok . <clogged.drainpipe at gmail dot com> ---
Any movement regarding this?
>From gcc-bugs-return-671914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 18:14:44 2020
Return-Path: <gcc-bugs-return-671914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36683 invoked by alias); 1 Mar 2020 18: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 36604 invoked by uid 55); 1 Mar 2020 18:14:40 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91799] [10 regression] r273245 breaks test case gcc.target/powerpc/pr88233.c
Date: Sun, 01 Mar 2020 18:14: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: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91799-4-WB5nNrmM2d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00023.txt
Content-length: 556
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91799
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jeff Law <law@gcc.gnu.org>:
https://gcc.gnu.org/g:03a71208880e60f6d9c51423a50d9de9ae26d700
commit r10-6956-g03a71208880e60f6d9c51423a50d9de9ae26d700
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date: Sun Mar 1 11:13:18 2020 -0700
Fix test for pr88233.
PR testsuite/91799
* gcc.target/powerpc/pr88233.c: Update expected output and
add target selector.
>From gcc-bugs-return-671915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 18:15:03 2020
Return-Path: <gcc-bugs-return-671915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37515 invoked by alias); 1 Mar 2020 18:15: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 37387 invoked by uid 48); 1 Mar 2020 18:14:58 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91799] [10 regression] r273245 breaks test case gcc.target/powerpc/pr88233.c
Date: Sun, 01 Mar 2020 18:15: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: law at redhat dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91799-4-M8xysIkLwt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00024.txt
Content-length: 450
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91799
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jeffrey A. Law <law at redhat dot com> ---
I pushed Segher's patch to the trunk.
>From gcc-bugs-return-671916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 18:17:38 2020
Return-Path: <gcc-bugs-return-671916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40208 invoked by alias); 1 Mar 2020 18:17: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 40175 invoked by uid 48); 1 Mar 2020 18:17:34 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93986] [10 Regression] ICE in decompose, at wide-int.h:984 since r10-5451
Date: Sun, 01 Mar 2020 18: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: 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: priority bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-93986-4-8fuMy79Rxg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93986-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93986-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00025.txt
Content-length: 975
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93986
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-03-01
CC| |jakub at gcc dot gnu.org
Target Milestone|--- |10.0
Summary|[10 Regression] ICE in |[10 Regression] ICE in
|decompose, at |decompose, at
|wide-int.h:984 |wide-int.h:984 since
| |r10-5451
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r10-5451-gef29b12cfbb4979a89b3cbadbf485a77c8fd8fce.
>From gcc-bugs-return-671917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 18:18:34 2020
Return-Path: <gcc-bugs-return-671917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41535 invoked by alias); 1 Mar 2020 18:18: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 41480 invoked by uid 55); 1 Mar 2020 18:18:31 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91797] [10 regression] r273240 breaks test case gcc.target/powerpc/pr68805.c
Date: Sun, 01 Mar 2020 18:18: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: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91797-4-LHaJVpUV9W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00026.txt
Content-length: 524
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91797
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jeff Law <law@gcc.gnu.org>:
https://gcc.gnu.org/g:151bf47e78f5d919f6cc591d11cc1f6aff61078f
commit r10-6957-g151bf47e78f5d919f6cc591d11cc1f6aff61078f
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date: Sun Mar 1 11:17:30 2020 -0700
Fix test for pr68805.
PR testsuite/91797
* gcc.target/pwoerpc/pr68805.c: Update expected output.
>From gcc-bugs-return-671918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 18:19:22 2020
Return-Path: <gcc-bugs-return-671918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46463 invoked by alias); 1 Mar 2020 18:19: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 46376 invoked by uid 48); 1 Mar 2020 18:19:17 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91797] [10 regression] r273240 breaks test case gcc.target/powerpc/pr68805.c
Date: Sun, 01 Mar 2020 18:19: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: law at redhat dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91797-4-2ZZG77nSZ2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00027.txt
Content-length: 437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91797
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Jeffrey A. Law <law at redhat dot com> ---
I pushed Segher's patch.
>From gcc-bugs-return-671919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 18:21:49 2020
Return-Path: <gcc-bugs-return-671919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48506 invoked by alias); 1 Mar 2020 18:21: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 48465 invoked by uid 48); 1 Mar 2020 18:21:45 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93982] [10 Regression] Assignment incorrectly omitted by -foptimize-strlen since r10-2528
Date: Sun, 01 Mar 2020 18: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: law at redhat dot com
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: priority cc
Message-ID: <bug-93982-4-hMjAioozni@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93982-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93982-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00028.txt
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93982
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
CC| |law at redhat dot com
>From gcc-bugs-return-671920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 18:22:47 2020
Return-Path: <gcc-bugs-return-671920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49474 invoked by alias); 1 Mar 2020 18:22: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 49438 invoked by uid 48); 1 Mar 2020 18:22:43 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92535] [10 regression] ICF is relatively expensive and became less effective
Date: Sun, 01 Mar 2020 18:22: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: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-92535-4-KvzRWhytH5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92535-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92535-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00029.txt
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92535
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |law at redhat dot com
>From gcc-bugs-return-671921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 18:23:31 2020
Return-Path: <gcc-bugs-return-671921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50482 invoked by alias); 1 Mar 2020 18:23: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 50437 invoked by uid 48); 1 Mar 2020 18:23:27 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92303] [10 regression] gcc.target/sparc/ultrasp12.c times out
Date: Sun, 01 Mar 2020 18: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: compile-time-hog, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cc
Message-ID: <bug-92303-4-oyM6I3nLIf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92303-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92303-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00030.txt
Content-length: 411
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92303
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|WAITING |NEW
CC| |law at redhat dot com
>From gcc-bugs-return-671922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 19:34:39 2020
Return-Path: <gcc-bugs-return-671922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118454 invoked by alias); 1 Mar 2020 19:34: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 118395 invoked by uid 48); 1 Mar 2020 19:34:34 -0000
From: "jwjagersma at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93981] No EH information generated for asm statements
Date: Sun, 01 Mar 2020 19:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jwjagersma 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-93981-4-KUFEyrBaEA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00031.txt
Content-length: 3285
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93981
--- Comment #9 from jwjagersma at gmail dot com ---
ICE can be replicated with:
```
$ ./cc1plus -O -g -fnon-call-exceptions -I../../gcc/libgcc
../../gcc/libgcc/config/i386/sfp-exceptions.c
void __sfp_handle_exceptions(int)
Analyzing compilation unit
Performing interprocedural optimizations
<*free_lang_data> <visibility> <build_ssa_passes>
../../gcc/libgcc/config/i386/sfp-exceptions.c:107:1: error: statement marked
for throw in middle of block
107 | }
| ^
# VUSE <.MEM_31>
__asm__ __volatile__("fdivs %1" : "=t" f_32 : "m" g, "0" f_30);
../../gcc/libgcc/config/i386/sfp-exceptions.c:107:1: error: statement marked
for throw in middle of block
# VUSE <.MEM_46>
__asm__ __volatile__("fdivs %1" : "=t" f_47 : "m" g, "0" f_45);
during GIMPLE pass: ssa
../../gcc/libgcc/config/i386/sfp-exceptions.c:107:1: internal compiler error:
verify_gimple failed
```
The error message is different but it's the same problem.
When I break there in gdb:
```
(gdb) break tree-cfg.c:5439
Breakpoint 5 at 0xf93816: file ../../gcc/gcc/tree-cfg.c, line 5439.
(gdb) r
Starting program: D:\vmshare\gcc-build\gcc\cc1plus.exe -O -g
-fnon-call-exceptions -I../../gcc/libgcc
../../gcc/libgcc/config/i386/sfp-exceptions.c
void __sfp_handle_exceptions(int)
Analyzing compilation unit
Performing interprocedural optimizations
<*free_lang_data> <visibility> <build_ssa_passes>
Breakpoint 5, verify_gimple_in_cfg (fn=0x3b9e10b8,
verify_nothrow=verify_nothrow@entry=true) at ../../gcc/gcc/tree-cfg.c:5439
warning: Source file is more recent than executable.
5439 error ("statement marked for throw in middle of
block");
=> 0x0000000000f93816 <verify_gimple_in_cfg(function*, bool)+1249>: 48 8d
0d 83 44 1c 01 lea rcx,[rip+0x11c4483] #0x2157ca0 <(anonymous
namespace)::pass_data_call_cdce+14848>
0x0000000000f9381d <verify_gimple_in_cfg(function*, bool)+1256>: e8 86
00 de 00 call 0x1d738a8 <error(char const*, ...)>
(gdb) pp bb
<bb 10> :
# DEBUG BEGIN_STMT
f_30 = 1.0e+0;
# DEBUG f => f_30
g = 0.0;
# DEBUG BEGIN_STMT
__asm__ __volatile__("fdivs %1" : "=t" f_32 : "m" g, "0" f_30);
# DEBUG f => f_32
(gdb) c
Continuing.
../../gcc/libgcc/config/i386/sfp-exceptions.c:107:1: error: statement marked
for throw in middle of block
107 | }
| ^
# VUSE <.MEM_31>
__asm__ __volatile__("fdivs %1" : "=t" f_32 : "m" g, "0" f_30);
Breakpoint 5, verify_gimple_in_cfg (fn=0x3b9e10b8,
verify_nothrow=verify_nothrow@entry=true) at ../../gcc/gcc/tree-cfg.c:5439
5439 error ("statement marked for throw in middle of
block");
=> 0x0000000000f93816 <verify_gimple_in_cfg(function*, bool)+1249>: 48 8d
0d 83 44 1c 01 lea rcx,[rip+0x11c4483] #0x2157ca0 <(anonymous
namespace)::pass_data_call_cdce+14848>
0x0000000000f9381d <verify_gimple_in_cfg(function*, bool)+1256>: e8 86
00 de 00 call 0x1d738a8 <error(char const*, ...)>
(gdb) pp bb
<bb 23> :
# DEBUG BEGIN_STMT
f_45 = 1.0e+0;
# DEBUG f => f_45
g = 3.0e+0;
# DEBUG BEGIN_STMT
__asm__ __volatile__("fdivs %1" : "=t" f_47 : "m" g, "0" f_45);
# DEBUG f => f_47
```
So the problem is that DEBUG stmts are inserted after a throwing asm.
>From gcc-bugs-return-671923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 20:07:27 2020
Return-Path: <gcc-bugs-return-671923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34659 invoked by alias); 1 Mar 2020 20: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 34622 invoked by uid 48); 1 Mar 2020 20:07:23 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93985] Sub-optimal assembly for %st(0) constant loading with SSE enabled (x86_64)
Date: Sun, 01 Mar 2020 20: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: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
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-93985-4-Stejrhq1Z4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93985-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93985-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00032.txt
Content-length: 970
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93985
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
To prevent unwanted use of x87 registers, register allocator is prohibited from
freely allocating x87 registers without -mfpmath=387 for SFmode and DFmode. You
should use long double and 1.0L to get what you want, e.g:
--cut here--
double
atan (double x)
{
long double _x = x;
long double _res;
__asm__("fpatan"
: "=t" (_res)
: "0" (1.0L) , "u" (_x)
: "st(1)");
return _res;
}
--cut here--
Alternatively, you could use -mfpmath=387,sse to enable x87 regs and x87
instructions also for x86_64.
>From gcc-bugs-return-671924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 20:42:59 2020
Return-Path: <gcc-bugs-return-671924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96090 invoked by alias); 1 Mar 2020 20:42: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 96036 invoked by uid 48); 1 Mar 2020 20:42:55 -0000
From: "gabriel at inconstante dot net.br" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93987] Regression (ICE) on gcc-9 branch
Date: Sun, 01 Mar 2020 20: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: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gabriel at inconstante dot net.br
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-93987-4-tDgDhum5T8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93987-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93987-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00033.txt
Content-length: 274
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93987
--- Comment #3 from Gabriel F. T. Gomes <gabriel at inconstante dot net.br> ---
Update: with the tip of the gcc-9 branch (commit ID 4630b748e63c), as well as
with the tip of trunk (commit ID 151bf47e78f5), it works.
>From gcc-bugs-return-671925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 21:05:25 2020
Return-Path: <gcc-bugs-return-671925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115934 invoked by alias); 1 Mar 2020 21: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 115917 invoked by uid 48); 1 Mar 2020 21:05:21 -0000
From: "kingoipo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93989] New: [c++20] Error initializing trivial types in constexpr constructor
Date: Sun, 01 Mar 2020 21: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kingoipo 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-93989-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00034.txt
Content-length: 2366
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93989
Bug ID: 93989
Summary: [c++20] Error initializing trivial types in constexpr
constructor
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: kingoipo at gmail dot com
Target Milestone: ---
In trying to implement p0980r1, I encountered the following error when calling
the constexpr basic_string(const _Alloc& __a) constructor:
/home/oipo-unencrypted/Programming/gcc/libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/copy_assign_constexpr.cc:
In function ‘consteval void test01()’:
/home/oipo-unencrypted/Programming/gcc/libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/copy_assign_constexpr.cc:37:
error: ‘test_type{std::__cxx11::basic_string<char, std::char_traits<char>,
__gnu_test::constexpr_allocator<char>
>::_Alloc_hider{__gnu_test::constexpr_allocator<char>{1}, ((char*)(&
v1.std::__cxx11::basic_string<char, std::char_traits<char>,
__gnu_test::constexpr_allocator<char>
>::<anonymous>.std::__cxx11::basic_string<char, std::char_traits<char>,
__gnu_test::constexpr_allocator<char> >::<unnamed union>::_M_local_buf))}, 0,
std::__cxx11::basic_string<char, std::char_traits<char>,
__gnu_test::constexpr_allocator<char> >::<unnamed union>{char [16]{0}}}’ is not
a constant expression
/home/oipo-unencrypted/Programming/gcc/libstdc++-v3/testsuite/21_strings/basic_string/allocator/char/copy_assign_constexpr.cc:37:
error: ‘std::__cxx11::basic_string<char, std::char_traits<char>,
__gnu_test::constexpr_allocator<char> >(a1)’ is not a constant expression
because it refers to an incompletely initialized variable
This is reproducible by checking out the code from https://github.com/Oipo/gcc
and running the new libstdc++3 testcase
https://github.com/Oipo/gcc/blob/master/libstdc%2B%2B-v3/testsuite/21_strings/basic_string/allocator/char/copy_assign_constexpr.cc
. This can be done with "make -jN check-target-libstdc++-v3".
A noteworthy extra change is the introduction of a constexpr_allocator in
testsuite_allocator.h.
Apologies for not being able to make a smaller reproducible case.
>From gcc-bugs-return-671926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 21:09:14 2020
Return-Path: <gcc-bugs-return-671926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119698 invoked by alias); 1 Mar 2020 21:09: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 119666 invoked by uid 48); 1 Mar 2020 21:09:10 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93980] use of lto breaks -Wl,--exclude-libs
Date: Sun, 01 Mar 2020 21:09: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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: MOVED
X-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 see_also resolution
Message-ID: <bug-93980-4-KwoKAA6SNq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93980-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00035.txt
Content-length: 644
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93980
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
See Also| |https://sourceware.org/bugz
| |illa/show_bug.cgi?id=25618
Resolution|--- |MOVED
--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> ---
This is a linker bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=25618
>From gcc-bugs-return-671927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 21:11:48 2020
Return-Path: <gcc-bugs-return-671927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121130 invoked by alias); 1 Mar 2020 21: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 121095 invoked by uid 48); 1 Mar 2020 21:11:44 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93989] [c++20] Error initializing trivial types in constexpr constructor
Date: Sun, 01 Mar 2020 21: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: 10.0
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: cc
Message-ID: <bug-93989-4-b00tBRNMfB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93989-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93989-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00036.txt
Content-length: 457
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93989
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Could you compile that TU with -save-temps and post the .ii file here?
>From gcc-bugs-return-671928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 21:24:35 2020
Return-Path: <gcc-bugs-return-671928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14363 invoked by alias); 1 Mar 2020 21:24: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 14286 invoked by uid 48); 1 Mar 2020 21:24:15 -0000
From: "kingoipo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93989] [c++20] Error initializing trivial types in constexpr constructor
Date: Sun, 01 Mar 2020 21: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kingoipo 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-93989-4-aXp43O1WgY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93989-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93989-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00037.txt
Content-length: 258
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93989
--- Comment #2 from Michael de Lang <kingoipo at gmail dot com> ---
Created attachment 47943
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47943&action=edit
save-temps copy_assign_constexpr.ii
>From gcc-bugs-return-671929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 21:29:23 2020
Return-Path: <gcc-bugs-return-671929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20545 invoked by alias); 1 Mar 2020 21:29: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 19688 invoked by uid 48); 1 Mar 2020 21:29:19 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93983] std::filesystem::path is not concept-friendly
Date: Sun, 01 Mar 2020 21:29: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: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-93983-4-sNVV3x4c6T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93983-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93983-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00038.txt
Content-length: 935
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93983
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=93923
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is nothing to do with concepts:
#include <iterator>
struct path {
template <typename Source,
typename = std::enable_if_t<
std::is_same_v<
std::iterator_traits<Source>::value_type,
char>>
>
path(Source const&);
};
struct Bar
{
Bar(const path& p);
};
#ifdef ADD_THIS
static_assert(!std::is_constructible_v<path, Bar>);
#endif
static_assert(std::is_copy_constructible_v<Bar>);
See also PR 93923.
>From gcc-bugs-return-671930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 21:36:26 2020
Return-Path: <gcc-bugs-return-671930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27054 invoked by alias); 1 Mar 2020 21:36: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 26980 invoked by uid 48); 1 Mar 2020 21:36:22 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93970] load via restricted pointer not eliminated after a store via a restricted pointer of incompatible type
Date: Sun, 01 Mar 2020 21: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: alias, missed-optimization
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 blocked resolution
Message-ID: <bug-93970-4-qFoZqSXxeZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93970-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93970-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00039.txt
Content-length: 1630
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93970
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Blocks|49774 |
Resolution|--- |INVALID
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
The test case in comment #0 cannot be optimized as suggested because *q can be
equal to NaN. Replacing the (unfortunately chosen) double with some other type
like long shows that the expected optimization is done as expected.
$ cat pr93970.c && gcc -O2 -S -Wall -fdump-tree-optimized=/dev/stdout pr93970.c
void f (int *__restrict p, int *__restrict q)
{
int t = *q;
*p = 0;
if (t != *q) // folded to false
__builtin_abort ();
}
void g (int *__restrict p, long *__restrict q)
{
long t = *q;
*p = 0;
if (t != *q) // also folded as expected
__builtin_abort ();
}
;; Function f (f, funcdef_no=0, decl_uid=1931, cgraph_uid=1, symbol_order=0)
f (int * restrict p, int * restrict q)
{
<bb 2> [local count: 1073741824]:
*p_3(D) = 0;
return;
}
;; Function g (g, funcdef_no=3, decl_uid=1936, cgraph_uid=2, symbol_order=1)
g (int * restrict p, long int * restrict q)
{
<bb 2> [local count: 1073741824]:
*p_2(D) = 0;
return;
}
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49774
[Bug 49774] [meta-bug] restrict qualification aliasing issues
>From gcc-bugs-return-671931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 21:39:25 2020
Return-Path: <gcc-bugs-return-671931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28900 invoked by alias); 1 Mar 2020 21: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 28857 invoked by uid 48); 1 Mar 2020 21:39:21 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93989] [c++20] Error initializing trivial types in constexpr constructor
Date: Sun, 01 Mar 2020 21: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: 10.0
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:
Message-ID: <bug-93989-4-CQjmoIiwLP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93989-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93989-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00040.txt
Content-length: 296
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93989
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Unfortunately that generates literally hundreds of errors when compiled with
-std=c++20 so it's nearly impossible for me to analyze it and see if there's a
real problem.
>From gcc-bugs-return-671932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 22:47:32 2020
Return-Path: <gcc-bugs-return-671932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96736 invoked by alias); 1 Mar 2020 22:47: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 96725 invoked by uid 48); 1 Mar 2020 22:47:28 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93971] std::string considered to alias declared objects of incompatible types
Date: Sun, 01 Mar 2020 22: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: alias, 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:
Message-ID: <bug-93971-4-VOmgU7Ubxt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00041.txt
Content-length: 1633
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93971
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
As a baseline, I think it would be great to get std::string to enjoy the same
benefits as other containers WRT aliasing. Going a step further, I'd expect
users of all containers to benefit from the aliasing guarantee the containers
already provide: that modifying one doesn't change the other. E.g., here it
should be possible to eliminate the test:
#include <vector>
struct S { std::vector<int> a, b; };
void f (struct S &s)
{
int t = s.a[0];
s.b[0] = 0;
if (t != s.a[0]) // can be folded to false
__builtin_abort ();
}
I've been thinking of one of two kinds of annotation that wouldn't require
programs to change and would be sufficient if applied only to the definition of
the containers: (1) one that would make "std::string::ptr" on par with that of
any other pointer other than char (i.e., a char that's not allowed to be used
to access anything but a char object), and (2) another that could basically be
described as having the effect you suggest.
An example of the former would be an attribute "noalias" applicable only to
narrow character types. The latter could be done by applying the same
attribute (or some other) to the std::vector and std::basic_string templates.
It might take yet another extension to also express the same guarantee for
node-based containers.
Like you I'm not sure that just slapping restrict on
std::string::_M_dataplus._M_p would have the desired effect (even if GCC did
pay attention to restrict on struct members).
>From gcc-bugs-return-671933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 23:00:29 2020
Return-Path: <gcc-bugs-return-671933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102474 invoked by alias); 1 Mar 2020 23:00: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 102190 invoked by uid 48); 1 Mar 2020 23:00:02 -0000
From: "lloyd at randombit dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93990] New: [x86] Silly code generation for _addcarry_u32/_addcarry_u64
Date: Sun, 01 Mar 2020 23:00: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.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lloyd at randombit 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-93990-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00042.txt
Content-length: 2502
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93990
Bug ID: 93990
Summary: [x86] Silly code generation for
_addcarry_u32/_addcarry_u64
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: lloyd at randombit dot net
Target Milestone: ---
Bug 67317 has regressed, starting in GCC 6
Same test case as 67317:
#include <x86intrin.h>
#include <stdint.h>
unsigned long long testcarry(unsigned long long a, unsigned long long
b, unsigned long long c, unsigned long long d)
{
unsigned long long result0, result1;
_addcarry_u64(_addcarry_u64(0, a, c, &result0), b, d,
&result1);
return result0 ^ result1;
}
GCC 5.4.1 (only) produces the expected output
.cfi_startproc
addq %rdi, %rdx # a, tmp99
adcq %rsi, %rcx # b, tmp107
movq %rdx, %rax # tmp99, D.28638
xorq %rcx, %rax # tmp107, D.28638
ret
.cfi_endproc
GCC 6.4.1, 7.4.1, 8.3.0 and 9.2.0 all produce variations on this [GCC 9.2.0
output here]:
.cfi_startproc
subq $40, %rsp #,
.cfi_def_cfa_offset 48
# adx.cpp:5: {
movq %fs:40, %rax # MEM[(<address-space-1> long unsigned int
*)40B], tmp107
movq %rax, 24(%rsp) # tmp107, D.33144
xorl %eax, %eax # tmp107
# /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include/adxintrin.h:69: return
__builtin_ia32_addcarryx_u64 (__CF, __X, __Y, __P);
addq %rdx, %rdi # tmp105, tmp93
movq %rsi, %rax # tmp104, tmp104
setc %r8b #, _12
movq %rdi, 8(%rsp) # tmp93,
addb $-1, %r8b #, _12
adcq %rcx, %rax # tmp106, tmp104
movq %rax, 16(%rsp) # tmp97,
# adx.cpp:8: return result0 ^ result1;
xorq %rdi, %rax # tmp93, <retval>
# adx.cpp:9: }
movq 24(%rsp), %rdx # D.33144, tmp109
xorq %fs:40, %rdx # MEM[(<address-space-1> long unsigned int
*)40B], tmp109
jne .L5 #,
addq $40, %rsp #,
.cfi_remember_state
.cfi_def_cfa_offset 8
ret
All were compiled with -O3. I checked 9.2.0 output with -O and -O2 as well,
with no significant change.
>From gcc-bugs-return-671934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 23:07:19 2020
Return-Path: <gcc-bugs-return-671934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113421 invoked by alias); 1 Mar 2020 23:07: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 113388 invoked by uid 48); 1 Mar 2020 23:07:15 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93990] [x86] Silly code generation for _addcarry_u32/_addcarry_u64
Date: Sun, 01 Mar 2020 23: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: 9.2.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-93990-4-2JvArrvvZs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93990-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93990-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00043.txt
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93990
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This is already been fixed in GCC 10:
addq %rdx, %rdi
movq %rsi, %rax
adcq %rcx, %rax
xorq %rdi, %rax
ret
.ident "GCC: (GNU) 10.0.1 20200121 (experimental) [master revision
e0a5b313c1a:f4dc220f630:b313d3c49c2387b5e212df22a5e6ecc0c4e95c0a]"
>From gcc-bugs-return-671935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Mar 01 23:10:27 2020
Return-Path: <gcc-bugs-return-671935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118808 invoked by alias); 1 Mar 2020 23:10: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 118775 invoked by uid 48); 1 Mar 2020 23:10:23 -0000
From: "lloyd at randombit dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93990] [x86] Silly code generation for _addcarry_u32/_addcarry_u64
Date: Sun, 01 Mar 2020 23:10: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lloyd at randombit dot net
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-93990-4-V91wtNutMj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93990-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93990-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00044.txt
Content-length: 451
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93990
Jack Lloyd <lloyd at randombit dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Jack Lloyd <lloyd at randombit dot net> ---
Good enough for me, closing, thanks.
>From gcc-bugs-return-671936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 00:00:44 2020
Return-Path: <gcc-bugs-return-671936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19125 invoked by alias); 2 Mar 2020 00:00: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 18779 invoked by uid 48); 2 Mar 2020 00:00:28 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93991] New: FAIL: 22_locale/time_get/get_time/char/2.cc execution test - 'errorstate == ios_base::eofbit' failed
Date: Mon, 02 Mar 2020 00:00: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin 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_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-93991-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00045.txt
Content-length: 3317
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93991
Bug ID: 93991
Summary: FAIL: 22_locale/time_get/get_time/char/2.cc execution
test - 'errorstate == ios_base::eofbit' failed
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: danglin at gcc dot gnu.org
Target Milestone: ---
Host: hppa-unknown-linux-gnu
Target: hppa-unknown-linux-gnu
Build: hppa-unknown-linux-gnu
spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir/./gcc/xg++ -shared-libgcc
-B/home
/dave/gnu/gcc/objdir/./gcc -nostdinc++
-L/home/dave/gnu/gcc/objdir/hppa-linux-gn
u/libstdc++-v3/src
-L/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/src/.
libs -L/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/
home/dave/opt/gnu/gcc/gcc-10/hppa-linux-gnu/bin/
-B/home/dave/opt/gnu/gcc/gcc-10
/hppa-linux-gnu/lib/ -isystem
/home/dave/opt/gnu/gcc/gcc-10/hppa-linux-gnu/inclu
de -isystem /home/dave/opt/gnu/gcc/gcc-10/hppa-linux-gnu/sys-include
-fchecking=
1 -B/home/dave/gnu/gcc/objdir/hppa-linux-gnu/./libstdc++-v3/src/.libs
-fmessage-
length=0 -fno-show-column -ffunction-sections -fdata-sections -g -O2
-D_GNU_SOUR
CE -DLOCALEDIR="." -nostdinc++
-I/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstd
c++-v3/include/hppa-linux-gnu
-I/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc
++-v3/include -I/home/dave/gnu/gcc/gcc/libstdc++-v3/libsupc++
-I/home/dave/gnu/g
cc/gcc/libstdc++-v3/include/backward
-I/home/dave/gnu/gcc/gcc/libstdc++-v3/tests
uite/util
/home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/22_locale/time_get/get_t
ime/char/2.cc -include bits/stdc++.h -fno-diagnostics-show-caret
-fdiagnostics-c
olor=never -fdiagnostics-urls=never ./libtestc++.a -Wl,--gc-sections
-L/home/dav
e/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/src/filesystem/.libs -lm -o
./2.exe
PASS: 22_locale/time_get/get_time/char/2.cc (test for excess errors)
Setting LD_LIBRARY_PATH to
:/home/dave/gnu/gcc/objdir/gcc:/home/dave/gnu/gcc/obj
dir/hppa-linux-gnu/./libstdc++-v3/../libatomic/.libs:/home/dave/gnu/gcc/objdir/h
ppa-linux-gnu/./libstdc++-v3/../libgomp/.libs:/home/dave/gnu/gcc/objdir/hppa-lin
ux-gnu/./libstdc++-v3/src/.libs::/home/dave/gnu/gcc/objdir/gcc:/home/dave/gnu/gc
c/objdir/hppa-linux-gnu/./libstdc++-v3/../libatomic/.libs:/home/dave/gnu/gcc/obj
dir/hppa-linux-gnu/./libstdc++-v3/../libgomp/.libs:/home/dave/gnu/gcc/objdir/hpp
a-linux-gnu/./libstdc++-v3/src/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/li
bstdc++-v3/src/.libs:/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libssp/.libs:/home
/dave/gnu/gcc/objdir/hppa-linux-gnu/libgomp/.libs:/home/dave/gnu/gcc/objdir/hppa
-linux-gnu/libatomic/.libs:/home/dave/gnu/gcc/objdir/./gcc:/home/dave/gnu/gcc/ob
jdir/./prev-gcc
Execution timeout is: 300
spawn [open ...]
/home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/22_locale/time_get/get_time/char/2
.cc:62: void test02(): Assertion 'errorstate == ios_base::eofbit' failed.
FAIL: 22_locale/time_get/get_time/char/2.cc execution test
extra_tool_flags are:
-include bits/stdc++.h
This is with Debian unstable. There are several similar failures.
>From gcc-bugs-return-671937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 00:37:20 2020
Return-Path: <gcc-bugs-return-671937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46023 invoked by alias); 2 Mar 2020 00:37: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 45982 invoked by uid 55); 2 Mar 2020 00:37:16 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93829] [10 Regression] bogus -Wstringop-overflow on memcpy of a struct with a pointer member from another with a long string
Date: Mon, 02 Mar 2020 00:37: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, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93829-4-csTgXop6E0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00046.txt
Content-length: 812
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93829
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:
https://gcc.gnu.org/g:1e9369c5dcf301e090d3a83e2c210cd6b96ac08c
commit r10-6959-g1e9369c5dcf301e090d3a83e2c210cd6b96ac08c
Author: Martin Sebor <msebor@redhat.com>
Date: Sun Mar 1 17:35:49 2020 -0700
PR middle-end/93829 - bogus -Wstringop-overflow on memcpy of a struct with
a pointer member from another with a long string
gcc/testsuite/ChangeLog:
PR middle-end/93829
* gcc.dg/Wstringop-overflow-32.c: New test.
gcc/ChangeLog:
PR middle-end/93829
* tree-ssa-strlen.c (count_nonzero_bytes): Set the size to that
of a pointer in the outermost ADDR_EXPRs.
>From gcc-bugs-return-671938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 00:42:16 2020
Return-Path: <gcc-bugs-return-671938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51386 invoked by alias); 2 Mar 2020 00: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 51331 invoked by uid 48); 2 Mar 2020 00:42:11 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93971] std::string considered to alias declared objects of incompatible types
Date: Mon, 02 Mar 2020 00: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: alias, missed-optimization
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-93971-4-oopiJfhWI6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00047.txt
Content-length: 508
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93971
--- Comment #7 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #6)
> (1) one that would make "std::string::ptr" on par with
> that of any other pointer other than char (i.e., a char that's not allowed
> to be used to access anything but a char object),
Are you sure a user isn't allowed to use placement new to construct an int in
the middle of a string? Maybe we should just encourage the use of u8string...
>From gcc-bugs-return-671940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 00:43:46 2020
Return-Path: <gcc-bugs-return-671940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54541 invoked by alias); 2 Mar 2020 00: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 53938 invoked by uid 48); 2 Mar 2020 00:43:41 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93829] [10 Regression] bogus -Wstringop-overflow on memcpy of a struct with a pointer member from another with a long string
Date: Mon, 02 Mar 2020 00: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: 10.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
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-93829-4-lRT4ha7h5x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00049.txt
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93829
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 00:43:41 2020
Return-Path: <gcc-bugs-return-671939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53879 invoked by alias); 2 Mar 2020 00:43: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 53822 invoked by uid 55); 2 Mar 2020 00:43:36 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93812] [9/10 Regression] ICE on redeclaration of an attribute format function without protoype
Date: Mon, 02 Mar 2020 00: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: ice-on-valid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93812-4-GB5bHYINLX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00048.txt
Content-length: 728
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93812
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:
https://gcc.gnu.org/g:a499c2f899961f2c09db2dc33e60b66e8d770092
commit r10-6960-ga499c2f899961f2c09db2dc33e60b66e8d770092
Author: Martin Sebor <msebor@redhat.com>
Date: Sun Mar 1 17:41:45 2020 -0700
PR c/93812 - ICE on redeclaration of an attribute format function without
protoype
gcc/c/ChangeLog:
PR c/93812
* c-typeck.c (build_functype_attribute_variant): New function.
(composite_type): Call it.
gcc/testsuite/ChangeLog:
PR c/93812
* gcc.dg/format/proto.c: New test.
>From gcc-bugs-return-671941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 00:45:41 2020
Return-Path: <gcc-bugs-return-671941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58270 invoked by alias); 2 Mar 2020 00:45: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 57974 invoked by uid 48); 2 Mar 2020 00:45:36 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93812] [9/10 Regression] ICE on redeclaration of an attribute format function without protoype
Date: Mon, 02 Mar 2020 00: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: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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: bug_status resolution
Message-ID: <bug-93812-4-rw3aftaBOM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00050.txt
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93812
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 00:54:58 2020
Return-Path: <gcc-bugs-return-671942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18980 invoked by alias); 2 Mar 2020 00:54: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 15273 invoked by uid 55); 2 Mar 2020 00:54:52 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93926] [10 Regression] ICE: verify_cgraph_node failed (error: malloc attribute should be used for a function that returns a pointer)
Date: Mon, 02 Mar 2020 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: ice-checking, ice-on-invalid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93926-4-5NobUYygn3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00051.txt
Content-length: 852
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93926
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:
https://gcc.gnu.org/g:726e292d410fc29812a95eb6d88a2ceb82d9080d
commit r10-6961-g726e292d410fc29812a95eb6d88a2ceb82d9080d
Author: Martin Sebor <msebor@redhat.com>
Date: Sun Mar 1 17:52:44 2020 -0700
PR middle-end/93926 - ICE on a built-in redeclaration returning an integer
instead of a pointer
gcc/c/ChangeLog:
PR middle-end/93926
* c-decl.c (types_close_enough_to_match): New function.
(match_builtin_function_types):
(diagnose_mismatched_decls): Add missing inform call to a warning.
gcc/testsuite/ChangeLog:
PR middle-end/93926
* gcc.dg/Wbuiltin-declaration-mismatch-13.c: New test.
>From gcc-bugs-return-671943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 00:55:14 2020
Return-Path: <gcc-bugs-return-671943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22228 invoked by alias); 2 Mar 2020 00:55: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 22149 invoked by uid 48); 2 Mar 2020 00:55:09 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93927] ICE: 'verify_gimple' failed (error: invalid conversion in gimple call)
Date: Mon, 02 Mar 2020 00:55: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: ice-checking, ice-on-invalid-code
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-93927-4-LbmKO5tkZC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93927-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93927-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00052.txt
Content-length: 553
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93927
Bug 93927 depends on bug 93926, which changed state.
Bug 93926 Summary: [10 Regression] ICE: verify_cgraph_node failed (error: malloc attribute should be used for a function that returns a pointer)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93926
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-671944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 00:55:14 2020
Return-Path: <gcc-bugs-return-671944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22233 invoked by alias); 2 Mar 2020 00:55: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 22138 invoked by uid 48); 2 Mar 2020 00:55:09 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93926] [10 Regression] ICE: verify_cgraph_node failed (error: malloc attribute should be used for a function that returns a pointer)
Date: Mon, 02 Mar 2020 00:55: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: ice-checking, ice-on-invalid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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: bug_status resolution
Message-ID: <bug-93926-4-HRgZJUIqO4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93926-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00053.txt
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93926
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 00:59:55 2020
Return-Path: <gcc-bugs-return-671945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33701 invoked by alias); 2 Mar 2020 00:59: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 33667 invoked by uid 55); 2 Mar 2020 00:59:49 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92721] checking ICE on attribute access redeclaration
Date: Mon, 02 Mar 2020 00: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: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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:
Message-ID: <bug-92721-4-PEL873dUXB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00054.txt
Content-length: 846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92721
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:
https://gcc.gnu.org/g:649e174102a8ae2d570616d09aa336b712e1baae
commit r10-6962-g649e174102a8ae2d570616d09aa336b712e1baae
Author: Martin Sebor <msebor@redhat.com>
Date: Sun Mar 1 17:58:45 2020 -0700
PR middle-end/92721 - checking ICE on attribute access redeclaration
gcc/c-family/ChangeLog:
PR c++/92721
* c-attribs.c (append_access_attrs): Correctly handle attribute.
(handle_access_attribute): Same.
gcc/ChangeLog:
PR c++/92721
* calls.c (init_attr_rdwr_indices): Correctly handle attribute.
gcc/testsuite/ChangeLog:
PR c++/92721
g++.dg/ext/attr-access.C: New test.
>From gcc-bugs-return-671946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 01:00:34 2020
Return-Path: <gcc-bugs-return-671946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34873 invoked by alias); 2 Mar 2020 01:00: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 34843 invoked by uid 48); 2 Mar 2020 01:00:30 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92721] [10 Regression] checking ICE on attribute access redeclaration
Date: Mon, 02 Mar 2020 01:00: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: ice-on-valid-code, patch
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 short_desc
Message-ID: <bug-92721-4-kmEvIQHxao@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00055.txt
Content-length: 634
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92721
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Summary|checking ICE on attribute |[10 Regression] checking
|access redeclaration |ICE on attribute access
| |redeclaration
--- Comment #10 from Martin Sebor <msebor at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-671947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 01:17:56 2020
Return-Path: <gcc-bugs-return-671947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69789 invoked by alias); 2 Mar 2020 01:17: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 69724 invoked by uid 48); 2 Mar 2020 01:17:52 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/91799] [10 regression] r273245 breaks test case gcc.target/powerpc/pr88233.c
Date: Mon, 02 Mar 2020 01:17: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: segher at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: segher at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91799-4-TxzSkIkcMh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00056.txt
Content-length: 155
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91799
--- Comment #7 from Segher Boessenkool <segher at gcc dot gnu.org> ---
I hadn't fully tested it yet.
>From gcc-bugs-return-671948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 01:34:27 2020
Return-Path: <gcc-bugs-return-671948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96667 invoked by alias); 2 Mar 2020 01:34: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 96646 invoked by uid 48); 2 Mar 2020 01:34:22 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93991] FAIL: 22_locale/time_get/get_time/char/2.cc execution test - 'errorstate == ios_base::eofbit' failed
Date: Mon, 02 Mar 2020 01: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin 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-93991-4-PKZoXIYjsS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93991-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93991-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00057.txt
Content-length: 151
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93991
--- Comment #1 from John David Anglin <danglin at gcc dot gnu.org> ---
Revision 275589 was okay.
>From gcc-bugs-return-671949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 03:12:12 2020
Return-Path: <gcc-bugs-return-671949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94789 invoked by alias); 2 Mar 2020 03: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 94750 invoked by uid 48); 2 Mar 2020 03:12:07 -0000
From: "xerofoify at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93518] missing warning on a possible overflow by sprintf %s with an allocated argument
Date: Mon, 02 Mar 2020 03:12: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: xerofoify 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-93518-4-Rp7nxNC13F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93518-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93518-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00058.txt
Content-length: 838
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93518
Nicholas Krause <xerofoify at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xerofoify at gmail dot com
--- Comment #1 from Nicholas Krause <xerofoify at gmail dot com> ---
Hi Martin,
I'm not sure if my analysis is correct but it seems that:
int idx = get_stridx (src);
is only for string lengths and not POINTER_TYPE_P. There
are versions for ADDR expressions but don't seem to be
any for POINTER_TYPE_P. I'm wondering if we can implement
around version of stridx for this as it seems that the
line mentioned would need to call one for POINTER_P types
to fix the issue. Not sure how trivial it would be implement
that.
>From gcc-bugs-return-671950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 03:47:42 2020
Return-Path: <gcc-bugs-return-671950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32551 invoked by alias); 2 Mar 2020 03:47: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 32503 invoked by uid 48); 2 Mar 2020 03:47:36 -0000
From: "yawaraka.7-11.hemogurobin at ezweb dot ne.jp" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93992] New: faile to compile specialization of inner class with template template parameter pack
Date: Mon, 02 Mar 2020 03: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yawaraka.7-11.hemogurobin at ezweb dot ne.jp
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-93992-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00059.txt
Content-length: 12448
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93992
Bug ID: 93992
Summary: faile to compile specialization of inner class with
template template parameter pack
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: yawaraka.7-11.hemogurobin at ezweb dot ne.jp
Target Milestone: ---
// Source
#include <iostream>
#include <type_traits>
#include <typeinfo>
#include <array>
template<typename T, T... Value> class A {
};
template<typename T, template<T...> class, T...> struct args_union;
template<typename T, template<T...> class TemplateType, T Head, T... Tail>
struct args_union<T, TemplateType, Head, Tail...> {
template<T...> struct args_union_sub;
template<T Head2, T... Tail2> struct args_union_sub<Head2, Tail2...> {
template<T... Args> using template_type =
std::conditional_t<(Head2 < Head), TemplateType<Head2,
Args...>, // if (Head2 < Head) TemplateType<Head2, Args...>;
TemplateType<Head, Args...>>;
// else TemplateType<Head,
Args...>;
using type = std::conditional_t<Head == Head2,
// if (Head == Head2)
typename args_union<T, template_type,
Tail...>::template args_union_sub<Tail2...>::type, //
args_unionã€args_union_sub
std::conditional_t<(Head < Head2),
// else if (Head < Head2)
typename args_union<T, template_type,
Tail...>::template args_union_sub<Head2, Tail2...>::type, // args_union
// else
typename args_union<T, template_type, Head,
Tail...>::template args_union_sub<Tail2...>::type>>;// args_union_sub
};
template<> struct args_union_sub<> {
template<T... Args> using template_type = TemplateType<>;
using type = TemplateType<Head, Tail...>;
};
};
template<typename T, template<T...> class TemplateType> struct args_union<T,
TemplateType> {
template<T...> struct args_union_sub;
template<T Head2, T... Tail2> struct args_union_sub<Head2, Tail2...> {
template<T... Args> using template_type = TemplateType<Head2,
Tail2..., Args...>;
using type = TemplateType<Head2, Tail2...>;
};
template<> struct args_union_sub<> {
template<T... Args> using template_type = TemplateType<>;
using type = TemplateType<>;
};
};
template<typename T> struct Asub {
template<T... Value> using type = A<T, Value...>;
};
template<typename T, T... Value1, T... Value2> constexpr auto tmp_union(const
A<T, Value1...>&, const A<T, Value2...>&) {
return typename args_union<T, Asub<T>::template type,
Value1...>::template args_union_sub<Value2...>::type();
}
int main() {
A<int, 0, 1, 4, 6> a;
A<int, 1, 2, 4, 5> b;
std::cout << std::boolalpha << std::is_same_v<decltype(tmp_union(a, b)),
A<int, 0, 1, 2, 4, 5, 6>> << std::endl;
std::cout << typeid(tmp_union(a, b)).name() << std::endl;
}
// error message
Using built-in specs.
COLLECT_GCC=/opt/wandbox/gcc-head/bin/g++
COLLECT_LTO_WRAPPER=/opt/wandbox/gcc-head/libexec/gcc/x86_64-pc-linux-gnu/10.0.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../source/configure --prefix=/opt/wandbox/gcc-head
--enable-languages=c,c++ --disable-multilib --without-ppl --without-cloog-ppl
--enable-checking=release --disable-nls --enable-lto
LDFLAGS=-Wl,-rpath,/opt/wandbox/gcc-head/lib,-rpath,/opt/wandbox/gcc-head/lib64,-rpath,/opt/wandbox/gcc-head/lib32
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.0.1 20200229 (experimental) (GCC)
COLLECT_GCC_OPTIONS='-o' 'prog.exe' '-I' '/opt/wandbox/boost-sml/include' '-I'
'/opt/wandbox/boost-di/include' '-I' '/opt/wandbox/range-v3/include' '-I'
'/opt/wandbox/nlohmann-json/include' '-I' '/opt/wandbox/cmcstl2/include' '-I'
'/opt/wandbox/te/include' '-Wall' '-Wextra' '-O2' '-march=native' '-v'
'-std=gnu++2a' '-I' '/opt/wandbox/boost-1.72.0/gcc-head/include'
'-L/opt/wandbox/boost-1.72.0/gcc-head/lib' '-shared-libgcc'
/opt/wandbox/gcc-head/libexec/gcc/x86_64-pc-linux-gnu/10.0.1/cc1plus -quiet -v
-I /opt/wandbox/boost-sml/include -I /opt/wandbox/boost-di/include -I
/opt/wandbox/range-v3/include -I /opt/wandbox/nlohmann-json/include -I
/opt/wandbox/cmcstl2/include -I /opt/wandbox/te/include -I
/opt/wandbox/boost-1.72.0/gcc-head/include -imultiarch x86_64-linux-gnu
-D_GNU_SOURCE prog.cc -march=sandybridge -mmmx -mno-3dnow -msse -msse2 -msse3
-mssse3 -mno-sse4a -mcx16 -msahf -mno-movbe -maes -mno-sha -mpclmul -mpopcnt
-mno-abm -mno-lwp -mno-fma -mno-fma4 -mno-xop -mno-bmi -mno-sgx -mno-bmi2
-mno-pconfig -mno-wbnoinvd -mno-tbm -mavx -mno-avx2 -msse4.2 -msse4.1
-mno-lzcnt -mno-rtm -mno-hle -mno-rdrnd -mno-f16c -mno-fsgsbase -mno-rdseed
-mno-prfchw -mno-adx -mfxsr -mxsave -mxsaveopt -mno-avx512f -mno-avx512er
-mno-avx512cd -mno-avx512pf -mno-prefetchwt1 -mno-clflushopt -mno-xsavec
-mno-xsaves -mno-avx512dq -mno-avx512bw -mno-avx512vl -mno-avx512ifma
-mno-avx512vbmi -mno-avx5124fmaps -mno-avx5124vnniw -mno-clwb -mno-mwaitx
-mno-clzero -mno-pku -mno-rdpid -mno-gfni -mno-shstk -mno-avx512vbmi2
-mno-avx512vnni -mno-vaes -mno-vpclmulqdq -mno-avx512bitalg -mno-movdiri
-mno-movdir64b -mno-waitpkg -mno-cldemote -mno-ptwrite -mno-avx512bf16
-mno-enqcmd -mno-avx512vp2intersect --param l1-cache-size=32 --param
l1-cache-line-size=64 --param l2-cache-size=4096 -mtune=sandybridge -quiet
-dumpbase prog.cc -auxbase prog -O2 -Wall -Wextra -std=gnu++2a -version -o
/tmp/cczxYwwS.s
GNU C++17 (GCC) version 10.0.1 20200229 (experimental) (x86_64-pc-linux-gnu)
compiled by GNU C version 10.0.1 20200229 (experimental), GMP version
6.1.0, MPFR version 3.1.4, MPC version 1.0.3, isl version none
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu"
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory
"/opt/wandbox/gcc-head/lib/gcc/x86_64-pc-linux-gnu/10.0.1/../../../../x86_64-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/opt/wandbox/boost-sml/include
/opt/wandbox/boost-di/include
/opt/wandbox/range-v3/include
/opt/wandbox/nlohmann-json/include
/opt/wandbox/cmcstl2/include
/opt/wandbox/te/include
/opt/wandbox/boost-1.72.0/gcc-head/include
/opt/wandbox/gcc-head/lib/gcc/x86_64-pc-linux-gnu/10.0.1/../../../../include/c++/10.0.1
/opt/wandbox/gcc-head/lib/gcc/x86_64-pc-linux-gnu/10.0.1/../../../../include/c++/10.0.1/x86_64-pc-linux-gnu
/opt/wandbox/gcc-head/lib/gcc/x86_64-pc-linux-gnu/10.0.1/../../../../include/c++/10.0.1/backward
/opt/wandbox/gcc-head/lib/gcc/x86_64-pc-linux-gnu/10.0.1/include
/opt/wandbox/gcc-head/include
/opt/wandbox/gcc-head/lib/gcc/x86_64-pc-linux-gnu/10.0.1/include-fixed
/usr/include/x86_64-linux-gnu
/usr/include
End of search list.
GNU C++17 (GCC) version 10.0.1 20200229 (experimental) (x86_64-pc-linux-gnu)
compiled by GNU C version 10.0.1 20200229 (experimental), GMP version
6.1.0, MPFR version 3.1.4, MPC version 1.0.3, isl version none
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: 1af50902123577608ff32d1ca7d8f798
prog.cc:24:11: error: explicit specialization in non-namespace scope 'struct
args_union<T, TemplateType, Head, Tail ...>'
24 | template<> struct args_union_sub<> {
| ^
prog.cc:24:20: error: template parameters not deducible in partial
specialization:
24 | template<> struct args_union_sub<> {
| ^~~~~~~~~~~~~~~~
prog.cc:24:20: note: 'T'
prog.cc:24:20: note: 'template<T ...<anonymous> > class TemplateType'
prog.cc:24:20: note: 'Head'
prog.cc:24:20: note: 'Tail'
prog.cc:36:11: error: explicit specialization in non-namespace scope 'struct
args_union<T, TemplateType>'
36 | template<> struct args_union_sub<> {
| ^
prog.cc:36:20: error: template parameters not deducible in partial
specialization:
36 | template<> struct args_union_sub<> {
| ^~~~~~~~~~~~~~~~
prog.cc:36:20: note: 'T'
prog.cc:36:20: note: 'template<T ...<anonymous> > class TemplateType'
prog.cc: In instantiation of 'struct args_union<int, args_union<int,
args_union<int, args_union<int, Asub<int>::type, 0, 1, 4, 6>::args_union_sub<1,
2, 4, 5>::template_type, 1, 4, 6>::args_union_sub<2, 4, 5>::template_type, 4,
6>::args_union_sub<4, 5>::template_type, 6>::args_union_sub<5>':
prog.cc:17:9: recursively required from 'struct args_union<int,
args_union<int, Asub<int>::type, 0, 1, 4, 6>::args_union_sub<1, 2, 4,
5>::template_type, 1, 4, 6>::args_union_sub<2, 4, 5>'
prog.cc:17:9: required from 'struct args_union<int, Asub<int>::type, 0, 1, 4,
6>::args_union_sub<1, 2, 4, 5>'
prog.cc:47:104: required from 'constexpr auto tmp_union(const A<T, Value1
...>&, const A<T, Value2 ...>&) [with T = int; T ...Value1 = {0, 1, 4, 6}; T
...Value2 = {1, 2, 4, 5}]'
prog.cc:53:74: required from here
prog.cc:17:9: error: invalid use of incomplete type 'struct args_union<int,
args_union<int, args_union<int, args_union<int, args_union<int,
Asub<int>::type, 0, 1, 4, 6>::args_union_sub<1, 2, 4, 5>::template_type, 1, 4,
6>::args_union_sub<2, 4, 5>::template_type, 4, 6>::args_union_sub<4,
5>::template_type, 6>::args_union_sub<5>::template_type>::args_union_sub<>'
17 | using type = std::conditional_t<Head == Head2, // if
(Head == Head2)
| ^~~~
prog.cc:31:24: note: declaration of 'struct args_union<int, args_union<int,
args_union<int, args_union<int, args_union<int, Asub<int>::type, 0, 1, 4,
6>::args_union_sub<1, 2, 4, 5>::template_type, 1, 4, 6>::args_union_sub<2, 4,
5>::template_type, 4, 6>::args_union_sub<4, 5>::template_type,
6>::args_union_sub<5>::template_type>::args_union_sub<>'
31 | template<T...> struct args_union_sub;
| ^~~~~~~~~~~~~~
prog.cc: In function 'int main()':
prog.cc:53:41: error: template argument 1 is invalid
53 | std::cout << std::boolalpha << std::is_same_v<decltype(tmp_union(a,
b)), A<int, 0, 1, 2, 4, 5, 6>> << std::endl;
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
// command line
$ g++ prog.cc -Wall -Wextra -O2 -march=native -v
-I/opt/wandbox/boost-1.72.0/gcc-head/include -std=gnu++2a
// comment
compiled on Wandbox. URL: https://wandbox.org/permlink/7hblGLSOhTyVBK4V
Clang 11.0.0 and MSVC 16.4.5 compile this code successfully.
>From gcc-bugs-return-671951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 04:26:08 2020
Return-Path: <gcc-bugs-return-671951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122126 invoked by alias); 2 Mar 2020 04:26: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 122046 invoked by uid 48); 2 Mar 2020 04:26:03 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93993] New: ICE in make_region_for_unexpected_tree_code, at analyzer/region-model.cc:4786
Date: Mon, 02 Mar 2020 04:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
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: dmalcolm 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-93993-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00060.txt
Content-length: 4707
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93993
Bug ID: 93993
Summary: ICE in make_region_for_unexpected_tree_code, at
analyzer/region-model.cc:4786
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
gfortran-10.0.1-alpha20200301 snapshot
(g:151bf47e78f5d919f6cc591d11cc1f6aff61078f) ICEs when compiling the following
testcase w/ -O1 -fanalyzer:
module np
implicit none
integer, parameter :: za = selected_real_kind(15, 307)
end module np
module gg
use np
type et(real_kind)
integer, kind :: real_kind
end type et
contains
function hv (tm) result(ce)
type (et(real_kind=za)), allocatable, target :: tm
type (et(real_kind=za)), pointer :: ce
allocate (tm)
ce => tm
end function hv
end module gg
program a5
use np
use gg
implicit none
type (et(real_kind=za)), allocatable :: qb
type (et(real_kind=za)), pointer :: vt
vt => hv (qb)
end program a5
% powerpc-e300c3-linux-gnu-gfortran-10.0.1 -O1 -fanalyzer -w -c ineya7os.f90
during IPA pass: analyzer
ineya7os.f90:21:0:
21 | end function hv
|
internal compiler error: in make_region_for_unexpected_tree_code, at
analyzer/region-model.cc:4786
0x74c35f
ana::region_model::make_region_for_unexpected_tree_code(ana::region_model_context*,
tree_node*, dump_location_t const&)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/region-model.cc:4786
0x74c35f
ana::region_model::make_region_for_unexpected_tree_code(ana::region_model_context*,
tree_node*, dump_location_t const&)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/region-model.cc:4782
0x1271af6 ana::region_model::get_lvalue_1(ana::path_var,
ana::region_model_context*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/region-model.cc:4650
0x1272043 ana::region_model::get_lvalue(ana::path_var,
ana::region_model_context*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/region-model.cc:4811
0x17fb7d5 ana::state_change_event::get_lvalue(tree_node*) const
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/checker-path.h:206
0x17fb7d5 ana::diagnostic_manager::prune_for_sm_diagnostic(ana::checker_path*,
ana::state_machine const*, tree_node*, unsigned int) const
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/diagnostic-manager.cc:1161
0x17fba62 ana::diagnostic_manager::prune_path(ana::checker_path*,
ana::state_machine const*, tree_node*, unsigned int) const
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/diagnostic-manager.cc:1056
0x17fbd5c ana::diagnostic_manager::emit_saved_diagnostic(ana::exploded_graph
const&, ana::saved_diagnostic const&, ana::exploded_path const&, gimple const*,
int)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/diagnostic-manager.cc:520
0x17fc86a ana::dedupe_winners::emit_best(ana::diagnostic_manager*,
ana::exploded_graph const&)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/diagnostic-manager.cc:446
0x17fc86a ana::diagnostic_manager::emit_saved_diagnostics(ana::exploded_graph
const&)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/diagnostic-manager.cc:489
0x1253aaf ana::impl_run_checkers(ana::logger*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/engine.cc:3807
0x12548c1 ana::run_checkers()
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/engine.cc:3850
0x1248518 execute
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/analyzer-pass.cc:84
(While my target here is powerpc, the ICE is not target-specific.)
>From gcc-bugs-return-671952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 06:55:08 2020
Return-Path: <gcc-bugs-return-671952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8582 invoked by alias); 2 Mar 2020 06:55: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 8270 invoked by uid 48); 2 Mar 2020 06:55:01 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93994] New: ICE in get_or_create_mem_ref, at analyzer/region-model.cc:6599
Date: Mon, 02 Mar 2020 06:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
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: dmalcolm 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-93994-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00061.txt
Content-length: 3559
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93994
Bug ID: 93994
Summary: ICE in get_or_create_mem_ref, at
analyzer/region-model.cc:6599
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
g++-10.0.1-alpha20200301 snapshot (g:151bf47e78f5d919f6cc591d11cc1f6aff61078f)
ICEs when compiling
libstdc++-v3/testsuite/20_util/function_objects/mem_fn/adl.cc w/ -fanalyzer:
% g++-10.0.1 -fanalyzer -c
libstdc++-v3/testsuite/20_util/function_objects/mem_fn/adl.cc
during IPA pass: analyzer
In file included from
/usr/lib/gcc/x86_64-pc-linux-gnu/10.0.1/include/g++-v10/tuple:41,
from
/usr/lib/gcc/x86_64-pc-linux-gnu/10.0.1/include/g++-v10/functional:54,
from
libstdc++-v3/testsuite/20_util/function_objects/mem_fn/adl.cc:20:
/usr/lib/gcc/x86_64-pc-linux-gnu/10.0.1/include/g++-v10/bits/invoke.h: In
function 'constexpr _Res std::__invoke_impl(std::__invoke_memobj_ref,
_MemPtr&&, _Tp&&) [with _Res = int&&; _MemPtr = int n::X::*&; _Tp = n::X]':
/usr/lib/gcc/x86_64-pc-linux-gnu/10.0.1/include/g++-v10/bits/invoke.h:79:34:
internal compiler error: in get_or_create_mem_ref, at
analyzer/region-model.cc:6599
79 | { return __invfwd<_Tp>(__t).*__f; }
| ^~~
0x7dd077 ana::region_model::get_or_create_mem_ref(tree_node*, ana::svalue_id,
ana::svalue_id, ana::region_model_context*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/region-model.cc:6599
0x136366c ana::region_model::get_or_create_pointer_plus_expr(tree_node*,
ana::svalue_id, ana::svalue_id, ana::region_model_context*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/region-model.cc:6682
0x136366c ana::region_model::on_assignment(gassign const*,
ana::region_model_context*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/region-model.cc:4005
0x133c998 ana::exploded_node::on_stmt(ana::exploded_graph&, ana::supernode
const*, gimple const*, ana::program_state*, ana::state_change*) const
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/engine.cc:1006
0x133d3c1 ana::exploded_graph::process_node(ana::exploded_node*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/engine.cc:2517
0x133d8aa ana::exploded_graph::process_worklist()
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/engine.cc:2335
0x133dfd9 ana::impl_run_checkers(ana::logger*)
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/engine.cc:3793
0x133ea7c ana::run_checkers()
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/engine.cc:3850
0x1333908 execute
/var/tmp/portage/sys-devel/gcc-10.0.1_alpha20200301/work/gcc-10-20200301/gcc/analyzer/analyzer-pass.cc:84
>From gcc-bugs-return-671953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 07:08:38 2020
Return-Path: <gcc-bugs-return-671953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19953 invoked by alias); 2 Mar 2020 07:08: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 19899 invoked by uid 48); 2 Mar 2020 07:08:33 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93794] [8/9/10 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.c:2497
Date: Mon, 02 Mar 2020 07:08: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: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to attachments.created
Message-ID: <bug-93794-4-MbpZb7cIqZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93794-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93794-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00062.txt
Content-length: 771
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93794
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
--- Comment #2 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 47944
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47944&action=edit
Patch for the PR
The test below does the right thing and the code is as expected.
Paul
program p
type t
character(:), pointer :: a
end type
type(t) :: z
character(4), target :: c = 'abcd'
z%a => c
associate (y => z%a)
print *, y
end associate
end
>From gcc-bugs-return-671954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 07:43:25 2020
Return-Path: <gcc-bugs-return-671954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43557 invoked by alias); 2 Mar 2020 07:43: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 43505 invoked by uid 55); 2 Mar 2020 07:43:20 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93745] Redundant store not eliminated with intermediate instruction
Date: Mon, 02 Mar 2020 07: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: 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93745-4-qdrybOplKk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00063.txt
Content-length: 1519
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93745
--- Comment #13 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 27 Feb 2020, msebor at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93745
>
> --- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> ---
> Regarding the DECL_FIXED_DYNAMIC_TYPE flag: it seems like in C every DECL would
> have it set, but in C++ none could (because placement new can change the
> dynamic type of decls), and so GCC would not be able to optimize the example in
> that language even though there the read via *p means that p cannot alias d.
>
> If what's keeping GCC from optimizing the code is the fact that the middle-end
> doesn't distinguish placement new from plain assignment, i.e., that it can't
> tell that the original source didn't look like this:
>
> double d;
>
> void f (long *p)
> {
> long i = *p;
> new (&d) double (3);
> *p = i;
> }
>
> wouldn't the solution be to keep placement new around in some form and teach
> the middle-end how to work with it?
We had this and it didn't work (OK, we only kept it in GIMPLE but not RTL
which is of course a non-starter). Feel free to come up with a solid
proposal and implementation.
What would eventually work (but again not for the specific example TU)
is an IPA pass constraining the dynamic type of global variables. But
then that's then a natural extension of our lack of a flow-sensitive
[IPA] points-to analysis.
>From gcc-bugs-return-671955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 07:52:32 2020
Return-Path: <gcc-bugs-return-671955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48400 invoked by alias); 2 Mar 2020 07:52: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 48343 invoked by uid 55); 2 Mar 2020 07:52:28 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92658] x86 lacks vector extend / truncate
Date: Mon, 02 Mar 2020 07: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: 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: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92658-4-zHUyn7lX76@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00064.txt
Content-length: 1570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
--- Comment #8 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 28 Feb 2020, ubizjak at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
>
> --- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
> Richi, should the following test also vectorize?
In priciple yes. I see both cases "vectorized" to a store
from a CTOR but then my primitive pattern matching in forwprop
not applying because supportable_convert_operation is confused
about a vector(4) char type having SImode and bailing out at the
292 if (!VECTOR_MODE_P (m1) || !VECTOR_MODE_P (m2))
293 return false;
check. So it looks like with just SSE2 the backend doesn't
consider V4QImode a supported vector type. I'm not sure we
want to fix that but then this means regular optab checks
won't do it here.
Interesting cases nevertheless.
Would those conversions map to good assembly?
> --cut here--
> typedef unsigned char v16qi __attribute__((vector_size (16)));
> typedef unsigned int v4si __attribute__((vector_size (16)));
>
> void
> foo_u8_u32 (v4si * dst, v16qi * __restrict src)
> {
> unsigned int tem[4];
> tem[0] = (*src)[0];
> tem[1] = (*src)[1];
> tem[2] = (*src)[2];
> tem[3] = (*src)[3];
> dst[0] = *(v4si *) tem;
> }
>
> void
> bar_u8_u32 (v4si * dst, v16qi src)
> {
> unsigned int tem[4];
> tem[0] = src[0];
> tem[1] = src[1];
> tem[2] = src[2];
> tem[3] = src[3];
> dst[0] = *(v4si *) tem;
> }
> --cut here--
>From gcc-bugs-return-671956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 08:07:46 2020
Return-Path: <gcc-bugs-return-671956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65260 invoked by alias); 2 Mar 2020 08:07: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 64879 invoked by uid 55); 2 Mar 2020 08:07:41 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93582] [10 Regression] -Warray-bounds gives error: array subscript 0 is outside array bounds of struct E[1]
Date: Mon, 02 Mar 2020 08:07: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, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93582-4-yWEf5wkqWB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93582-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93582-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00065.txt
Content-length: 1604
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93582
--- Comment #36 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 28 Feb 2020, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93582
>
> --- Comment #35 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> Unfortunately, it breaks miserably, e.g. miscompiles libcpp/macro.c.
> Reduced testcase from that:
>
> --- gcc/testsuite/gcc.c-torture/execute/pr93582.c.jj 2020-02-28
> 12:27:51.280925113 +0100
> +++ gcc/testsuite/gcc.c-torture/execute/pr93582.c 2020-02-28
> 12:26:17.272332573 +0100
> @@ -0,0 +1,22 @@
> +/* PR tree-optimization/93582 */
> +
> +short a;
> +int b, c;
> +
> +__attribute__((noipa)) void
> +foo (void)
> +{
> + b = c;
> + a &= 7;
> +}
> +
> +int
> +main ()
> +{
> + c = 27;
> + a = 14;
> + foo ();
> + if (b != 27 || a != 6)
> + __builtin_abort ();
> + return 0;
> +}
>
> I believe the thing is that for the case with mask we need to completely avoid
> the vn_reference_lookup_or_insert_for_pieces calls that finish method does, and
> vn_reference_insert
> call visit_reference_op_load does.
> Probably instead of that we should call vn_nary_op_insert_stmt.
> Now, I wonder if e.g. finish couldn't for the masked case just return the tree
> itself rather than anything else, and let visit_reference_op_load not call
> visit_reference_op_load if mask is non-NULL.
Yeah, just add a insert_p flag to the lookup function and the context
struct, for lookups only valid under a mask we indeed may not record
those into the hash tables.
>From gcc-bugs-return-671957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 08:22:04 2020
Return-Path: <gcc-bugs-return-671957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79956 invoked by alias); 2 Mar 2020 08:22: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 79845 invoked by uid 55); 2 Mar 2020 08:21:59 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93745] Redundant store not eliminated with intermediate instruction
Date: Mon, 02 Mar 2020 08: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: 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93745-4-g6CrfiT2mM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00066.txt
Content-length: 1185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93745
--- Comment #14 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 28 Feb 2020, law at redhat dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93745
>
> --- Comment #12 from Jeffrey A. Law <law at redhat dot com> ---
> It would seem like C ought to be able to set the flag across the board. But
> Richi would know best if this is going to run afoul of of the alias oracle
> implementation & underlying gimple semantics.
>
> I vaguely recall a discussion on the lists WRT how to represent placement-new.
> I didn't follow it at the time. Without reviewing the thread it does seem
> helpful if we could see the placement-new in the IL.
Note for C++ placement new isn't required. At least older standards
simply talk about "reuse" of storage when POD types are involved.
Note a representation of "placement new" is awkward - it has to be
present in the virtual use-def chain since otherwise it's not
a barrier for alias purposes. In the end it will hinder more
optimizations than it will enable and you'll need to add it
before all POD stores because of the above mentioned issues.
>From gcc-bugs-return-671959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 08:24:39 2020
Return-Path: <gcc-bugs-return-671959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82616 invoked by alias); 2 Mar 2020 08:24: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 82202 invoked by uid 48); 2 Mar 2020 08:24:34 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93966] [9/10 Regression] -fcf-protection -flto -g don't work togeter
Date: Mon, 02 Mar 2020 08:24: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:
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: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-93966-4-2EOMHJDaNH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00068.txt
Content-length: 647
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93966
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.3
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Isn't this a linker bug? There's no code sections in the debug object.
Also you need to provide -fcf-protection at compile-time as well, not
only at link-time (technically only at compile-time). Otherwise success
is not guaranteed.
I'm not aware why it should work with GCC 8 btw.
>From gcc-bugs-return-671958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 08:24:36 2020
Return-Path: <gcc-bugs-return-671958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82235 invoked by alias); 2 Mar 2020 08:24: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 81965 invoked by uid 48); 2 Mar 2020 08:24:31 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92658] x86 lacks vector extend / truncate
Date: Mon, 02 Mar 2020 08: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: ubizjak at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92658-4-9G414LK90G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00067.txt
Content-length: 1561
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
--- Comment #9 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to rguenther@suse.de from comment #8)
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
> >
> > --- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> ---
> > Richi, should the following test also vectorize?
>
> In priciple yes. I see both cases "vectorized" to a store
> from a CTOR but then my primitive pattern matching in forwprop
> not applying because supportable_convert_operation is confused
> about a vector(4) char type having SImode and bailing out at the
>
> 292 if (!VECTOR_MODE_P (m1) || !VECTOR_MODE_P (m2))
> 293 return false;
>
> check. So it looks like with just SSE2 the backend doesn't
> consider V4QImode a supported vector type. I'm not sure we
> want to fix that but then this means regular optab checks
> won't do it here.
>
> Interesting cases nevertheless.
>
> Would those conversions map to good assembly?
Yes, please see attached test cases, especially pr92658-sse4.c. We have
pmovzxbd for v4qi->v4si, pmovzxbq for v2qi->v2di, and pmovzxwd for v2hi->v2di,
in addition to AVX2 pmovzxbq for v4qi->v4di. All testcases should vectorize
with a single instruction. It is also possible to introduce additional
conversions to 64bit vectors (e.g. v2qi->v2si) for TARGET_MMX_WITH_SSE targets.
Please note that there are similar sign_extend patterns and corresponding
truncate patterns with AVX512F, currently not covered by attached patch and
testcases.
>From gcc-bugs-return-671960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 08:47:52 2020
Return-Path: <gcc-bugs-return-671960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53686 invoked by alias); 2 Mar 2020 08:47: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 53654 invoked by uid 48); 2 Mar 2020 08:47:48 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93995] New: ICE in patch_jump_insn, at cfgrtl.c:1290 on riscv64-linux-gnu
Date: Mon, 02 Mar 2020 08:47: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
Message-ID: <bug-93995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00069.txt
Content-length: 2157
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93995
Bug ID: 93995
Summary: ICE in patch_jump_insn, at cfgrtl.c:1290 on
riscv64-linux-gnu
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: x86_64-linux-gnu
Target: riscv64-linux-gnu
I see the following ICE:
$ riscv64-linux-gnu-gcc
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr50310-2.c
-fno-trapping-math
during RTL pass: expand
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr50310-2.c: In function
‘main’:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr50310-2.c:47:1: internal
compiler error: in patch_jump_insn, at cfgrtl.c:1290
47 | }
| ^
0x5a247f patch_jump_insn
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-riscv64/build/gcc/cfgrtl.c:1290
0x7009be redirect_branch_edge
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-riscv64/build/gcc/cfgrtl.c:1317
0x700e42 rtl_redirect_edge_and_branch
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-riscv64/build/gcc/cfgrtl.c:1450
0x6ef219 redirect_edge_and_branch(edge_def*, basic_block_def*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-riscv64/build/gcc/cfghooks.c:373
0xf9fbdc try_forward_edges
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-riscv64/build/gcc/cfgcleanup.c:562
0xf9fbdc try_optimize_cfg
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-riscv64/build/gcc/cfgcleanup.c:2960
0xf9fbdc cleanup_cfg(int)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-riscv64/build/gcc/cfgcleanup.c:3174
0x6ecf11 execute
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-riscv64/build/gcc/cfgexpand.c:6670
>From gcc-bugs-return-671961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 08:49:31 2020
Return-Path: <gcc-bugs-return-671961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55891 invoked by alias); 2 Mar 2020 08: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 55773 invoked by uid 48); 2 Mar 2020 08:49:27 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93995] ICE in patch_jump_insn, at cfgrtl.c:1290 on riscv64-linux-gnu
Date: Mon, 02 Mar 2020 08: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: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on cc target_milestone
Message-ID: <bug-93995-4-joxfkSQV9j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00070.txt
Content-length: 503
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93995
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2020-3-2
CC| |kito at gcc dot gnu.org,
| |wilson at gcc dot gnu.org
Target Milestone|--- |10.0
>From gcc-bugs-return-671962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 08:52:36 2020
Return-Path: <gcc-bugs-return-671962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59165 invoked by alias); 2 Mar 2020 08:52: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 59092 invoked by uid 48); 2 Mar 2020 08:52:32 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93996] New: [10 Regression] ICE in lookup_page_table_entry
Date: Mon, 02 Mar 2020 08:52: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
Message-ID: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00071.txt
Content-length: 3065
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93996
Bug ID: 93996
Summary: [10 Regression] ICE in lookup_page_table_entry
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: x86_64-linux-gnu
Target: aarch64-linux-gnu
I see the following ICE:
$ aarch64-linux-gnu-gcc
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr65345-2.c
--param=ggc-min-heapsize=0 -O2 -fsched2-use-superblocks
--param=ggc-min-expand=0 -c
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr65345-2.c: In function
‘fn5’:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/pr65345-2.c:34:1: internal
compiler error: Segmentation fault
34 | }
| ^
0xb6d34f crash_signal
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-aarch64/build/gcc/toplev.c:328
0x7ffff78fff1f ???
/usr/src/debug/glibc-2.31-2.1.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x740003 lookup_page_table_entry
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-aarch64/build/gcc/ggc-page.c:630
0x740003 ggc_set_mark(void const*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-aarch64/build/gcc/ggc-page.c:1544
0x67f99f gt_ggc_mx_lang_tree_node(void*)
./gt-c-c-decl.h:49
0x680571 gt_ggc_mx_lang_tree_node(void*)
./gt-c-c-decl.h:397
0x926f34 gt_ggc_mx_rtx_def(void*)
/dev/shm/buildbot/builddir/gcc/gtype-desc.c:727
0x927c6e gt_ggc_mx_rtvec_def(void*)
/dev/shm/buildbot/builddir/gcc/gtype-desc.c:974
0x927c6e gt_ggc_mx_rtvec_def(void*)
/dev/shm/buildbot/builddir/gcc/gtype-desc.c:964
0x92707c gt_ggc_mx_rtx_def(void*)
/dev/shm/buildbot/builddir/gcc/gtype-desc.c:808
0x926968 gt_ggc_mx_rtx_def(void*)
/dev/shm/buildbot/builddir/gcc/gtype-desc.c:917
0x925bf9 gt_ggc_mx_basic_block_def(void*)
/dev/shm/buildbot/builddir/gcc/gtype-desc.c:1549
0x9287c9 gt_ggc_mx_control_flow_graph(void*)
/dev/shm/buildbot/builddir/gcc/gtype-desc.c:2251
0x9287c9 gt_ggc_mx_control_flow_graph(void*)
/dev/shm/buildbot/builddir/gcc/gtype-desc.c:2246
0x92a04b gt_ggc_mx_function(void*)
/dev/shm/buildbot/builddir/gcc/gtype-desc.c:1704
0x92a04b gt_ggc_mx_function(void*)
/dev/shm/buildbot/builddir/gcc/gtype-desc.c:1698
0x6806ca gt_ggc_mx_lang_tree_node(void*)
./gt-c-c-decl.h:290
0x925649 gt_ggc_mx_dw_fde_node(void*)
/dev/shm/buildbot/builddir/gcc/gtype-desc.c:2153
0x925649 gt_ggc_mx_dw_fde_node(void*)
/dev/shm/buildbot/builddir/gcc/gtype-desc.c:2148
0x7f742e void gt_ggc_mx<dw_fde_node*>(vec<dw_fde_node*, va_gc, vl_embed>*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-aarch64/build/gcc/vec.h:1325
>From gcc-bugs-return-671963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 08:53:01 2020
Return-Path: <gcc-bugs-return-671963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60087 invoked by alias); 2 Mar 2020 08:53: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 59991 invoked by uid 48); 2 Mar 2020 08:52:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/41898] GCC ignores restrict on array
Date: Mon, 02 Mar 2020 08:53: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: 4.5.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 assigned_to
Message-ID: <bug-41898-4-C4Mc1i9vnD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-41898-4@http.gcc.gnu.org/bugzilla/>
References: <bug-41898-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00072.txt
Content-length: 2368
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41898
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 #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Same for
int * __restrict__ *a;
int * __restrict__ *b;
extern void link_error (void);
int main()
{
a[0][0] = 0;
b[0][0] = 1;
if (a[0][0] != 0)
link_error ();
return 0;
}
the restrict-ness is attached to specific variable infos in PTA but here
the restrict pointers fall out from a dereference op which might be present
multiple times but would all need to pick up the same artificial restrict
varinfo. That's currently not supported in the data structures and/or
the constraint system and/or the graph solving.
For the int * __restrict__ a[1] case we fail to recognize it in
/* Mark global restrict qualified pointers. */
if ((POINTER_TYPE_P (TREE_TYPE (decl))
&& TYPE_RESTRICT (TREE_TYPE (decl)))
|| vi->only_restrict_pointers)
{
and vi->only_restrict_pointers is only ever set for aggregates which
we track field-wise (which arrays are not).
Possible fix below - it wouldn't handle int * __restrict a[2] optimally
since a[0] and a[1] would still alias.
diff --git a/gcc/tree-ssa-structalias.c b/gcc/tree-ssa-structalias.c
index 416a26c996c..dcc7fafc4b9 100644
--- a/gcc/tree-ssa-structalias.c
+++ b/gcc/tree-ssa-structalias.c
@@ -6128,8 +6128,11 @@ create_variable_info_for_1 (tree decl, const char *name,
bool add_id,
vi->fullsize = tree_to_uhwi (declsize);
vi->size = vi->fullsize;
vi->is_full_var = true;
- if (POINTER_TYPE_P (decl_type)
- && (TYPE_RESTRICT (decl_type) || add_restrict))
+ if ((POINTER_TYPE_P (decl_type)
+ && (TYPE_RESTRICT (decl_type) || add_restrict))
+ || (TREE_CODE (decl_type) == ARRAY_TYPE
+ && POINTER_TYPE_P (TREE_TYPE (decl_type))
+ && TYPE_RESTRICT (TREE_TYPE (decl_type))))
vi->only_restrict_pointers = 1;
if (vi->only_restrict_pointers
&& !type_contains_placeholder_p (TREE_TYPE (decl_type))
>From gcc-bugs-return-671964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 08:54:27 2020
Return-Path: <gcc-bugs-return-671964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61551 invoked by alias); 2 Mar 2020 08:54: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 61499 invoked by uid 48); 2 Mar 2020 08:54:23 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93996] [10 Regression] ICE in lookup_page_table_entry
Date: Mon, 02 Mar 2020 08: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, 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: bug_status cf_known_to_work keywords cf_reconfirmed_on cc everconfirmed target_milestone cf_known_to_fail
Message-ID: <bug-93996-4-C9JKabEZQm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00073.txt
Content-length: 802
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93996
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Known to work| |9.2.0
Keywords| |needs-bisection
Last reconfirmed| |2020-03-02
CC| |ktkachov at gcc dot gnu.org
Ever confirmed|0 |1
Target Milestone|--- |10.0
Known to fail| |10.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
I'm bisecting that.
>From gcc-bugs-return-671965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 08:55:21 2020
Return-Path: <gcc-bugs-return-671965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62906 invoked by alias); 2 Mar 2020 08:55: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 62861 invoked by uid 48); 2 Mar 2020 08:55:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93995] ICE in patch_jump_insn, at cfgrtl.c:1290 on riscv64-linux-gnu
Date: Mon, 02 Mar 2020 08: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, 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: keywords bug_status everconfirmed
Message-ID: <bug-93995-4-CGVeYS1uWr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00074.txt
Content-length: 537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93995
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-bisection
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
I guess it's a recent regression, I'm gonna bisect it.
>From gcc-bugs-return-671966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 09:00:56 2020
Return-Path: <gcc-bugs-return-671966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68224 invoked by alias); 2 Mar 2020 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 68168 invoked by uid 48); 2 Mar 2020 09:00:51 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93997] New: [10 Regression] ICE: maximum number of generated reload insns per insn achieved (90) since r10-2156-g82534f65d86d48da
Date: Mon, 02 Mar 2020 09:00: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 cc target_milestone
Message-ID: <bug-93997-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00075.txt
Content-length: 1591
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93997
Bug ID: 93997
Summary: [10 Regression] ICE: maximum number of generated
reload insns per insn achieved (90) since
r10-2156-g82534f65d86d48da
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
CC: ubizjak at gmail dot com
Target Milestone: ---
I see the following ICE since the mentioned revision:
$ gcc /home/marxin/Programming/gcc/gcc/testsuite/c-c++-common/vector-scalar.c
-m32 -march=athlon-4
during RTL pass: reload
/home/marxin/Programming/gcc/gcc/testsuite/c-c++-common/vector-scalar.c: In
function ‘f’:
/home/marxin/Programming/gcc/gcc/testsuite/c-c++-common/vector-scalar.c:10:1:
internal compiler error: maximum number of generated reload insns per insn
achieved (90)
10 | }
| ^
0xc99204 lra_constraints(bool)
/home/marxin/Programming/gcc/gcc/lra-constraints.c:4948
0xc86044 lra(_IO_FILE*)
/home/marxin/Programming/gcc/gcc/lra.c:2437
0xc3dcc1 do_reload
/home/marxin/Programming/gcc/gcc/ira.c:5523
0xc3dcc1 execute
/home/marxin/Programming/gcc/gcc/ira.c:5709
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-671967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 09:06:29 2020
Return-Path: <gcc-bugs-return-671967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74918 invoked by alias); 2 Mar 2020 09:06: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 74859 invoked by uid 48); 2 Mar 2020 09:06:25 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93996] [10 Regression] ICE in lookup_page_table_entry
Date: Mon, 02 Mar 2020 09: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: 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: 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 cc
Message-ID: <bug-93996-4-8teW42AR3I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00076.txt
Content-length: 503
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93996
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
CC| |wdijkstr at arm dot com
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r10-6038-ge5e07b68187b9aa334519746c45b8cffc5eb7e5c.
>From gcc-bugs-return-671968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 09:10:45 2020
Return-Path: <gcc-bugs-return-671968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78153 invoked by alias); 2 Mar 2020 09:10: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 78121 invoked by uid 48); 2 Mar 2020 09:10:41 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93997] [10 Regression] ICE: maximum number of generated reload insns per insn achieved (90) since r10-2156-g82534f65d86d48da
Date: Mon, 02 Mar 2020 09:10: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: 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 cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-93997-4-KUqoixEseG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93997-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93997-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00077.txt
Content-length: 621
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93997
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-03-02
Known to work| |9.2.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
>From gcc-bugs-return-671969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 09:29:07 2020
Return-Path: <gcc-bugs-return-671969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99973 invoked by alias); 2 Mar 2020 09:29: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 99918 invoked by uid 48); 2 Mar 2020 09:29:02 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93995] ICE in patch_jump_insn, at cfgrtl.c:1290 on riscv64-linux-gnu
Date: Mon, 02 Mar 2020 09: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: 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: keywords
Message-ID: <bug-93995-4-FlRemncufS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00078.txt
Content-length: 428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93995
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r10-6806-g9069e9484cec2ff981c87c75b226ad738847ca07.
>From gcc-bugs-return-671970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 09:30:02 2020
Return-Path: <gcc-bugs-return-671970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101133 invoked by alias); 2 Mar 2020 09:30: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 100927 invoked by uid 48); 2 Mar 2020 09:29:58 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93994] ICE in get_or_create_mem_ref, at analyzer/region-model.cc:6599
Date: Mon, 02 Mar 2020 09:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
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: dmalcolm 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-93994-4-5LeVtYxEHf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93994-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00079.txt
Content-length: 486
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93994
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-03-02
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-671971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 09:38:00 2020
Return-Path: <gcc-bugs-return-671971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112501 invoked by alias); 2 Mar 2020 09:38: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 112433 invoked by uid 55); 2 Mar 2020 09:37:56 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/93965] Problematic ld_date configure check
Date: Mon, 02 Mar 2020 09: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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-93965-4-rtbIL0Paud@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00080.txt
Content-length: 698
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93965
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Martin Liska
<marxin@gcc.gnu.org>:
https://gcc.gnu.org/g:0afd41f8e6530b13421679801cf73cb6bef55553
commit r8-10102-g0afd41f8e6530b13421679801cf73cb6bef55553
Author: Martin Liska <mliska@suse.cz>
Date: Mon Mar 2 10:34:35 2020 +0100
Backport 08bf7bde9f2987b1c623d272cc71fc14a1622442
Backport from mainline
2020-02-28 Martin Liska <mliska@suse.cz>
PR other/93965
* configure.ac: Improve detection of ld_date by requiring
either two dashes or none.
* configure: Regenerate.
>From gcc-bugs-return-671972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 09:39:17 2020
Return-Path: <gcc-bugs-return-671972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114090 invoked by alias); 2 Mar 2020 09:39: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 114064 invoked by uid 48); 2 Mar 2020 09:39:13 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93997] [10 Regression] ICE: maximum number of generated reload insns per insn achieved (90) since r10-2156-g82534f65d86d48da
Date: Mon, 02 Mar 2020 09:39: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: ubizjak at gmail 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93997-4-J7xcio4cQx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93997-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93997-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00081.txt
Content-length: 1477
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93997
--- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
Before my patch, the compiler generated this IR:
#(insn 42 291 43 2 (set (strict_low_part (mem/c:HI (plus:SI (reg/f:SI 6 bp)
# (const_int -40 [0xffffffffffffffd8])) [5 %sfp+-16 S2
A128]))
# (reg:HI 1 dx [orig:91 _14 ] [91])) "vector-scalar.c":9:17 83
{*movstricthi_1}
# (nil))
movw %dx, -40(%ebp) # 42 [c=4 l=4] *movstricthi_1/0
This is strict_low_part of a memory operand, which isn't valid according to
docs:
'(strict_low_part (subreg:M (reg:N R) 0))'
This expression code is used in only one context: as the
destination operand of a 'set' expression. In addition, the
operand of this expression must be a non-paradoxical 'subreg'
expression.
The presence of 'strict_low_part' says that the part of the
register which is meaningful in mode N, but is not part of mode M,
is not to be altered. Normally, an assignment to such a subreg is
allowed to have undefined effects on the rest of the register when
M is smaller than 'REGMODE_NATURAL_SIZE (N)'.
After the patch, we have:
(insn 42 41 43 2 (set (strict_low_part (subreg:HI (reg:TI 135) 0))
(reg:HI 91 [ _14 ])) "vector-scalar.c":9:17 83 {*movstricthi_1}
(nil))
but TImode is not valid for general regs.
Probably we have to reject TImode in case of 32bit targets from the expander.
>From gcc-bugs-return-671973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 09:46:51 2020
Return-Path: <gcc-bugs-return-671973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3200 invoked by alias); 2 Mar 2020 09: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 2947 invoked by uid 48); 2 Mar 2020 09:46:46 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/93965] Problematic ld_date configure check
Date: Mon, 02 Mar 2020 09:46: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:
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 cf_known_to_work resolution cf_known_to_fail
Message-ID: <bug-93965-4-LfPGZSGUbp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93965-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00082.txt
Content-length: 561
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93965
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Known to work| |8.3.1
Resolution|--- |FIXED
Known to fail|8.3.0 |
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed on all active branches.
>From gcc-bugs-return-671974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 09:53:07 2020
Return-Path: <gcc-bugs-return-671974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10992 invoked by alias); 2 Mar 2020 09:53: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 10955 invoked by uid 48); 2 Mar 2020 09:53:03 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/93993] ICE in make_region_for_unexpected_tree_code, at analyzer/region-model.cc:4786
Date: Mon, 02 Mar 2020 09:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: analyzer
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: dmalcolm 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-93993-4-anM8t9T84Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93993-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93993-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00083.txt
Content-length: 486
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93993
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-03-02
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-671975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:02:09 2020
Return-Path: <gcc-bugs-return-671975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29950 invoked by alias); 2 Mar 2020 10:02: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 29839 invoked by uid 48); 2 Mar 2020 10:02:00 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93997] [10 Regression] ICE: maximum number of generated reload insns per insn achieved (90) since r10-2156-g82534f65d86d48da
Date: Mon, 02 Mar 2020 10:02: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: ubizjak at gmail 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93997-4-hYrNK5BAWQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93997-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93997-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00084.txt
Content-length: 754
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93997
--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Uroš Bizjak from comment #1)
> Probably we have to reject TImode in case of 32bit targets from the expander.
Like this:
--cut here--
diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md
index 6c57500ae8ec..8e29dffafa6e 100644
--- a/gcc/config/i386/i386.md
+++ b/gcc/config/i386/i386.md
@@ -2778,7 +2778,7 @@
{
gcc_assert (SUBREG_P (operands[0]));
if ((TARGET_PARTIAL_REG_STALL && optimize_function_for_speed_p (cfun))
- || GET_MODE_CLASS (GET_MODE (SUBREG_REG (operands[0]))) != MODE_INT)
+ || !VALID_INT_MODE_P (GET_MODE (SUBREG_REG (operands[0]))))
FAIL;
})
--cut here--
>From gcc-bugs-return-671976-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:15:28 2020
Return-Path: <gcc-bugs-return-671976-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51377 invoked by alias); 2 Mar 2020 10:15: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 51065 invoked by uid 48); 2 Mar 2020 10:15:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] [10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Mon, 02 Mar 2020 10:15: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.1
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: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-93974-4-dsqiXBo2EK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00085.txt
Content-length: 714
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[8/9/10 Regression] ICE in |[10 Regression] ICE in
|decompose_normal_address, |decompose_normal_address,
|at rtlanal.c:6403 on |at rtlanal.c:6403 on
|powerpc64le-linux-gnu since |powerpc64le-linux-gnu since
|r10-6762 |r10-6762
--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reverted on release branches, so this only affects trunk.
>From gcc-bugs-return-671977-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:15:54 2020
Return-Path: <gcc-bugs-return-671977-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52460 invoked by alias); 2 Mar 2020 10:15: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 52353 invoked by uid 48); 2 Mar 2020 10:15:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93658] [8/9 Regression] infinite loop building ghostscript and icu with -O3 on powerpc64le-linux-gnu
Date: Mon, 02 Mar 2020 10:15: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: ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution short_desc
Message-ID: <bug-93658-4-LExFE8CQwF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00086.txt
Content-length: 747
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93658
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
Summary|[9/10 Regression] infinite |[8/9 Regression] infinite
|loop building ghostscript |loop building ghostscript
|and icu with -O3 on |and icu with -O3 on
|powerpc64le-linux-gnu |powerpc64le-linux-gnu
--- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The fixes have been reverted for 9.3/8.4.
>From gcc-bugs-return-671978-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:19:17 2020
Return-Path: <gcc-bugs-return-671978-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58757 invoked by alias); 2 Mar 2020 10:19: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 58704 invoked by uid 48); 2 Mar 2020 10:19:13 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93879] typo: frequency quality
Date: Mon, 02 Mar 2020 10: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: 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 everconfirmed
Message-ID: <bug-93879-4-3pcZT6iOZZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00087.txt
Content-length: 510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93879
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-03-02
Ever confirmed|0 |1
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
@Rolland: Please send the patch.
>From gcc-bugs-return-671979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:22:11 2020
Return-Path: <gcc-bugs-return-671979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61915 invoked by alias); 2 Mar 2020 10: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 61847 invoked by uid 48); 2 Mar 2020 10:22:06 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/93962] [10 regression] bootstrap fails with gcc/value-prof.c:268:28 : error: format '%lld' expects argument of type 'long long int', but argument 3 hastype 'int'
Date: Mon, 02 Mar 2020 10:22: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: rguenth 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 version target_milestone
Message-ID: <bug-93962-4-AAS2QJmKCZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93962-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93962-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00088.txt
Content-length: 400
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93962
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Version|unknown |10.0
Target Milestone|--- |10.0
>From gcc-bugs-return-671980-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:27:58 2020
Return-Path: <gcc-bugs-return-671980-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78288 invoked by alias); 2 Mar 2020 10:27: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 78229 invoked by uid 48); 2 Mar 2020 10:27:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93964] [8/9/10 Regression] [graphite] ICE in assign_parameter_index_in_region, at graphite-scop-detection.c:1104
Date: Mon, 02 Mar 2020 10:27: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
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 cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-93964-4-vtOd8DnsKN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93964-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00089.txt
Content-length: 1020
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93964
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-03-02
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> ---
Confirmed.
1104 gcc_assert (TREE_CODE (name) == SSA_NAME
1105 && INTEGRAL_TYPE_P (TREE_TYPE (name))
1106 && ! defined_in_sese_p (name, region->region));
the parameter has pointer type. Some disconnect between analyses predicates.
Ouch. It's from niters which niter analysis expanded that far.
(unsigned int) (long int) _1 + 4294967295
So we end up using _1 instead of _2 here which would have been fine :/
>From gcc-bugs-return-671982-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:28:22 2020
Return-Path: <gcc-bugs-return-671982-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79929 invoked by alias); 2 Mar 2020 10:28: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 79876 invoked by uid 48); 2 Mar 2020 10:28:18 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93964] [8/9/10 Regression] [graphite] ICE in assign_parameter_index_in_region, at graphite-scop-detection.c:1104
Date: Mon, 02 Mar 2020 10: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-invalid-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-93964-4-ImCN5ErutW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93964-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00091.txt
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93964
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.4
>From gcc-bugs-return-671981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:28:11 2020
Return-Path: <gcc-bugs-return-671981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79085 invoked by alias); 2 Mar 2020 10:28: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 79016 invoked by uid 48); 2 Mar 2020 10:28:06 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93951] ICE with '-flto -g -femit-struct-debug-baseonly'
Date: Mon, 02 Mar 2020 10:28: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: 9.2.1
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-93951-4-wIpp2aItFJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00090.txt
Content-length: 2143
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93951
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
On master it as fixed with:
r10-770-gd1137c020aa59c6e(31 May 2019
08:22)(thomas.de_schampheleire@nokia.com): [took: 0.647s] result: OK
re PR debug/86964 (Too many debug symbols included, especially for extern
globals)
2019-05-31 Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
PR debug/86964
* common.opt (feliminate-unused-debug-symbols): Enable by default.
* doc/invoke.texi (Debugging Options): Document new default of
-feliminate-unused-debug-symbols and remove restriction to 'stabs'.
* g++.dg/debug/dwarf2/fesd-any.C: Use
-fno-eliminate-unused-debug-symbols.
* g++.dg/debug/dwarf2/fesd-baseonly.C: Likewise.
* g++.dg/debug/dwarf2/fesd-none.C: Likewise.
* g++.dg/debug/dwarf2/fesd-reduced.C: Likewise.
* g++.dg/debug/dwarf2/fesd-sys.C: Likewise.
* g++.dg/debug/dwarf2/inline-var-1.C: Likewise.
* g++.dg/debug/enum-2.C: Likewise.
* gcc.dg/debug/dwarf2/fesd-any.c: Likewise.
* gcc.dg/debug/dwarf2/fesd-baseonly.c: Likewise.
* gcc.dg/debug/dwarf2/fesd-none.c: Likewise.
* gcc.dg/debug/dwarf2/fesd-reduced.c: Likewise.
* gcc.dg/debug/dwarf2/fesd-sys.c: Likewise.
and adding the -feliminate-unused-debug-symbols to command line it's fixed
since
r9-6697-g715e3349b08decc2(25 Mar 2019 15:19)(johan.karlsson@enea.com): [took:
0.621s] result: OK
re PR debug/86964 (Too many debug symbols included, especially for extern
globals)
PR debug/86964
* dwarf2out.c (premark_used_variables): New function.
(prune_unused_types_walk): Do not mark not premarked external
variables.
(prune_unused_types): Call premark_used_variables.
* gcc.dg/debug/dwarf2/pr86964.c: New testcase.
>From gcc-bugs-return-671983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:30:04 2020
Return-Path: <gcc-bugs-return-671983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82735 invoked by alias); 2 Mar 2020 10:30: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 81403 invoked by uid 48); 2 Mar 2020 10:29:59 -0000
From: "ostash at ostash dot kiev.ua" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93998] New: ICE in adjust_temp_type, at cp/constexpr.c:1426
Date: Mon, 02 Mar 2020 10:30: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: ostash at ostash dot kiev.ua
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-93998-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00092.txt
Content-length: 2206
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93998
Bug ID: 93998
Summary: ICE in adjust_temp_type, at cp/constexpr.c:1426
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ostash at ostash dot kiev.ua
Target Milestone: ---
Hello,
Following code
----
#define LIKELY(x) __builtin_expect(!!(x), 1)
class Code
{
public:
constexpr bool operator==(Code rhs) const noexcept { return value_ ==
rhs.value_; }
private:
int value_;
};
int func(const Code a, const Code b, bool cond)
{
return LIKELY(a == b || cond) ? 0 : 1;
}
----
causes an ICE with GCC:
----
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/prefix/libexec/gcc/x86_64-pc-linux-gnu/10.0.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-10-20200223/configure --disable-multiarch
--disable-libquadmath --disable-libquadmath-support --disable-libssp
--disable-libstdcxx-pch --disable-multilib --disable-nls
--enable-checking=release --enable-__cxa_atexit --enable-languages=c,c++
--enable-libstdcxx-debug --enable-lto --enable-plugin --enable-threads=posix
--enable-tls --with-build-config=bootstrap-lto
--with-default-libstdcxx-abi=gcc4-compatible --with-linker-hash-style=gnu
--with-system-zlib --with-zstd=no --with-stage1-libs=
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu
--target=x86_64-pc-linux-gnu --prefix=/prefix
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.0.1 20200223 (experimental) (GCC)
----
----
gccice.cpp: In function 'int func(Code, Code, bool)':
gccice.cpp:1:44: internal compiler error: in adjust_temp_type, at
cp/constexpr.c:1426
1 | #define LIKELY(x) __builtin_expect(!!(x), 1)
| ^
gccice.cpp:14:10: note: in expansion of macro 'LIKELY'
14 | return LIKELY(a == b || cond) ? 0 : 1;
|
Please submit a full bug report,
with preprocessed source if appropriate.
----
Optimization level doesn't matter and any C++ standard >= c++11 causes an ICE.
>From gcc-bugs-return-671984-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:33:25 2020
Return-Path: <gcc-bugs-return-671984-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92383 invoked by alias); 2 Mar 2020 10:33: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 92301 invoked by uid 48); 2 Mar 2020 10:33:21 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87560] ICE in curr_insn_transform, at lra-constraints.c:3892
Date: Mon, 02 Mar 2020 10:33: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.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:
Message-ID: <bug-87560-4-nVo4XKXh5l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87560-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87560-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00093.txt
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87560
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Bill Schmidt from comment #2)
> Hm, I can't reproduce this with current trunk. Does it still occur for you,
> Martin?
No, it's gone with current master.
>From gcc-bugs-return-671986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:37:35 2020
Return-Path: <gcc-bugs-return-671986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101926 invoked by alias); 2 Mar 2020 10:37: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 101836 invoked by uid 48); 2 Mar 2020 10:37:31 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93996] [10 Regression] ICE in lookup_page_table_entry
Date: Mon, 02 Mar 2020 10:37: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, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-93996-4-nzUrrwUNSW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00095.txt
Content-length: 327
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93996
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This has to be a latent bug.
Also it does not reproduce with a natively built compiler which is even more
interesting.
Reduced testcase:
_Atomic int i = 5, j = 2;
void fn5 (int a[++i][j = 10]) {}
>From gcc-bugs-return-671985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:37:17 2020
Return-Path: <gcc-bugs-return-671985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101080 invoked by alias); 2 Mar 2020 10:37: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 101039 invoked by uid 48); 2 Mar 2020 10:37:13 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93966] [9/10 Regression] -fcf-protection -flto -g don't work togeter
Date: Mon, 02 Mar 2020 10:37: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:
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: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget priority
Message-ID: <bug-93966-4-skXOybiK7U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00094.txt
Content-length: 362
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93966
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-*-*, i?86-*-*
Priority|P3 |P2
>From gcc-bugs-return-671987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:38:31 2020
Return-Path: <gcc-bugs-return-671987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103109 invoked by alias); 2 Mar 2020 10:38: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 103037 invoked by uid 55); 2 Mar 2020 10:38:26 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93951] ICE with '-flto -g -femit-struct-debug-baseonly'
Date: Mon, 02 Mar 2020 10:38: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: 9.2.1
X-Bugzilla-Keywords:
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93951-4-as1FemOjNY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00096.txt
Content-length: 698
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93951
--- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 2 Mar 2020, marxin at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93951
>
> Martin Liška <marxin at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Keywords|needs-bisection |
>
> --- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
> On master it as fixed with:
OK, that's not a fix so it probably reproduces still with
-fno-eliminate-unused-debug-symbols
>From gcc-bugs-return-671989-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:42:46 2020
Return-Path: <gcc-bugs-return-671989-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109510 invoked by alias); 2 Mar 2020 10:42: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 109455 invoked by uid 48); 2 Mar 2020 10:42:42 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93951] ICE with '-flto -g -femit-struct-debug-baseonly'
Date: Mon, 02 Mar 2020 10:42: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: 9.2.1
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work cf_known_to_fail
Message-ID: <bug-93951-4-vOBzutXSMl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00098.txt
Content-length: 549
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93951
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work|10.0 |
Known to fail| |10.0
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
>
> OK, that's not a fix so it probably reproduces still with
> -fno-eliminate-unused-debug-symbols
Yes, I forgot to test this.
>From gcc-bugs-return-671988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:42:14 2020
Return-Path: <gcc-bugs-return-671988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108658 invoked by alias); 2 Mar 2020 10:42: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 108586 invoked by uid 48); 2 Mar 2020 10:42:10 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93996] [10 Regression] ICE in lookup_page_table_entry
Date: Mon, 02 Mar 2020 10: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: ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-93996-4-QtF3i1PPW0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00097.txt
Content-length: 524
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93996
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The bad tree comes from the mem_attrs from (mem/v:SI (reg/f:DI 0 x0 [97]) [-1
S4 A32]) inside the following instruction:
$3 = (insn:TI 30 34 31 3 (set (reg:SI 1 x1 [98])
(unspec_volatile:SI [
(mem/v:SI (reg/f:DI 0 x0 [97]) [-1 S4 A32])
(const_int 5 [0x5])
] UNSPECV_LX)) "t1.c":2:17 3889 {aarch64_load_exclusivesi}
(nil))
---- CUT ----
>From gcc-bugs-return-671990-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:44:04 2020
Return-Path: <gcc-bugs-return-671990-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113664 invoked by alias); 2 Mar 2020 10:44: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 113600 invoked by uid 48); 2 Mar 2020 10:43:59 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93951] [8/9/10 Regression] ICE with '-flto -g -femit-struct-debug-baseonly'
Date: Mon, 02 Mar 2020 10:44: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: 9.2.1
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work short_desc
Message-ID: <bug-93951-4-T8fwCqK5OR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00099.txt
Content-length: 727
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93951
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |7.4.0
Summary|ICE with '-flto -g |[8/9/10 Regression] ICE
|-femit-struct-debug-baseonl |with '-flto -g
|y' |-femit-struct-debug-baseonl
| |y'
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
With -std=c++17 it started with r8-2599-g1ea85365b430b5ad. I'm gonna reduce a
test-case.
>From gcc-bugs-return-671991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:45:53 2020
Return-Path: <gcc-bugs-return-671991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116179 invoked by alias); 2 Mar 2020 10:45: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 116035 invoked by uid 48); 2 Mar 2020 10:45:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93971] std::string considered to alias declared objects of incompatible types
Date: Mon, 02 Mar 2020 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: alias, 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-93971-4-u4FTDs1XAw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93971-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00100.txt
Content-length: 677
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93971
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #6)
> I've been thinking of one of two kinds of annotation that wouldn't require
> programs to change and would be sufficient if applied only to the definition
> of the containers: (1) one that would make "std::string::ptr" on par with
> that of any other pointer other than char (i.e., a char that's not allowed
> to be used to access anything but a char object)
but then
std::string s;
char *p = s.c_str();
*p = '0';
s[0]
breaks? ISTR there's ways to get a char * to the std::string storage.
>From gcc-bugs-return-671993-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:46:58 2020
Return-Path: <gcc-bugs-return-671993-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121123 invoked by alias); 2 Mar 2020 10:46: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 121055 invoked by uid 48); 2 Mar 2020 10:46:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93974] [10 Regression] ICE in decompose_normal_address, at rtlanal.c:6403 on powerpc64le-linux-gnu since r10-6762
Date: Mon, 02 Mar 2020 10:46: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.1
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: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-93974-4-z8QEDn1bSH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93974-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00102.txt
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93974
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|8.4 |10.0
>From gcc-bugs-return-671992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:46:34 2020
Return-Path: <gcc-bugs-return-671992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119757 invoked by alias); 2 Mar 2020 10:46: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 119205 invoked by uid 48); 2 Mar 2020 10:46:28 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvODgyOTVdIElDRSBvbiAoaW52YWxpZCkgQysrMTEgY29kZTog?= =?UTF-8?B?dHJlZSBjaGVjazogZXhwZWN0ZWQgY2xhc3Mg4oCYZXhwcmVzc2lvbuKAmSwg?= =?UTF-8?B?aGF2ZSDigJhleGNlcHRpb25h4oCZIChhcmd1bWVudF9wYWNrX3NlbGVjdCkg?= =?UTF-8?B?aW4gdHJlZV9vcGVyYW5kX2NoZWNrLCBhdCB0cmVlLmg6MzY1Mg==?Date: Mon, 02 Mar 2020 10: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: 9.0
X-Bugzilla-Keywords: 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88295-4-oHQevBzcZ0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88295-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88295-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00101.txt
Content-length: 178
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88295
--- Comment #2 from Arseny Solokha <asolokha at gmx dot com> ---
Is it still an issue? I cannot reproduce the ICE anywhere.
>From gcc-bugs-return-671994-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:50:29 2020
Return-Path: <gcc-bugs-return-671994-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124554 invoked by alias); 2 Mar 2020 10: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 124518 invoked by uid 48); 2 Mar 2020 10:50:25 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93999] New: Maybe a misleading warning
Date: Mon, 02 Mar 2020 10:50: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: 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-93999-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00103.txt
Content-length: 2155
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93999
Bug ID: 93999
Summary: Maybe a misleading warning
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
We may emit a misleading warning based on:
https://github.com/godotengine/godot/pull/36393
$ cat grid.ii
class A;
template <class T, class... P>
void call_with_variant_args_helper(void (T::*p_method)(), int p_args) {
A *p_instance;
(p_instance->*p_method)(P(p_args)...);
}
template <class T> void call_with_variant_args(void (T::*)()) {
call_with_variant_args_helper<A>;
}
template <class T> class CallableCustomMethodPointer {
struct {
void (T::*method)();
} data;
public:
virtual void m_fn1() { call_with_variant_args(data.method); }
CallableCustomMethodPointer(A *, void (T::*)()) {}
};
template <class T>
void create_custom_callable_function_pointer(A *p_instance, const char *,
void (T::*p_method)()) {
CallableCustomMethodPointer(p_instance, p_method);
}
class A {
void m_fn2();
A();
};
A::A() { create_custom_callable_function_pointer(this, "", &A::m_fn2); }
$ g++ grid.ii -c -Wunused-but-set-parameter -Werror -std=c++17 -fmax-errors=1
grid.ii: In instantiation of ‘void call_with_variant_args_helper(void (T::*)(),
int) [with T = A; P = {}]’:
grid.ii:8:3: required from ‘void call_with_variant_args(void (T::*)()) [with
T = A]’
grid.ii:16:48: required from ‘void CallableCustomMethodPointer<T>::m_fn1()
[with T = A]’
grid.ii:16:16: required from here
grid.ii:3:63: error: parameter ‘p_args’ set but not used
[-Werror=unused-but-set-parameter]
3 | void call_with_variant_args_helper(void (T::*p_method)(), int p_args) {
| ~~~~^~~~~~
cc1plus: all warnings being treated as errors
>From gcc-bugs-return-671995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:51:22 2020
Return-Path: <gcc-bugs-return-671995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125540 invoked by alias); 2 Mar 2020 10:51: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 125488 invoked by uid 48); 2 Mar 2020 10:51:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93582] [10 Regression] -Warray-bounds gives error: array subscript 0 is outside array bounds of struct E[1]
Date: Mon, 02 Mar 2020 10:51: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, 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: P2
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-93582-4-e5cEv7Se0H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93582-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93582-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00104.txt
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93582
--- Comment #37 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #36)
> Yeah, just add a insert_p flag to the lookup function and the context
> struct, for lookups only valid under a mask we indeed may not record
> those into the hash tables.
The https://gcc.gnu.org/ml/gcc-patches/2020-02/msg01628.html patch does that
(roughly).
>From gcc-bugs-return-671996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:54:33 2020
Return-Path: <gcc-bugs-return-671996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128416 invoked by alias); 2 Mar 2020 10:54: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 128369 invoked by uid 48); 2 Mar 2020 10:54:28 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93951] [8/9/10 Regression] ICE with '-flto -g -femit-struct-debug-baseonly'
Date: Mon, 02 Mar 2020 10:54: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: 9.2.1
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93951-4-g4osxzCpoJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00105.txt
Content-length: 837
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93951
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
There's a reduced test-case:
$ cat pr93951.ii
# 2 "" 3
namespace std {
template <typename _Tp> struct A {};
template <typename, typename _Visitor> struct __gen_vtable {
using _Func_ptr = _Visitor;
using _Array_type = A<_Func_ptr>;
static _Array_type m_fn1() {}
static constexpr auto _S_vtable = m_fn1;
};
template <typename _Visitor> visit(_Visitor) {
using _Result_type = decltype(0);
__gen_vtable<_Result_type, _Visitor>::_S_vtable;
}
} // namespace std
struct V {
m_fn2() {
auto visitor = [] {};
std::visit(visitor);
}
};
Fails with:
$ g++ pr93951.ii -c -g -flto -femit-struct-debug-baseonly -std=c++17
-fno-eliminate-unused-debug-symbols -c
Will you take a look Richi?
>From gcc-bugs-return-671997-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 10:55:32 2020
Return-Path: <gcc-bugs-return-671997-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129920 invoked by alias); 2 Mar 2020 10: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 129852 invoked by uid 48); 2 Mar 2020 10:55:28 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93981] No EH information generated for asm statements
Date: Mon, 02 Mar 2020 10:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 9.2.1
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-93981-4-SETPjnMb2t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93981-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00106.txt
Content-length: 179
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93981
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Some stmt-ends-BB predicates are probably off for asms.
>From gcc-bugs-return-671998-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:01:18 2020
Return-Path: <gcc-bugs-return-671998-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7554 invoked by alias); 2 Mar 2020 11: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 7493 invoked by uid 48); 2 Mar 2020 11:01:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93951] [8/9/10 Regression] ICE with '-flto -g -femit-struct-debug-baseonly'
Date: Mon, 02 Mar 2020 11:01: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: 9.2.1
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: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status assigned_to target_milestone
Message-ID: <bug-93951-4-tsmAD3QkPP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00107.txt
Content-length: 661
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93951
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Target Milestone|--- |8.4
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
I will have a look (but I consider -femit-struct-debug-baseonly quite arcane
and possibly unsupported).
>From gcc-bugs-return-671999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:03:50 2020
Return-Path: <gcc-bugs-return-671999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9602 invoked by alias); 2 Mar 2020 11:03: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 9536 invoked by uid 48); 2 Mar 2020 11:03:46 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93996] [10 Regression] ICE in lookup_page_table_entry
Date: Mon, 02 Mar 2020 11: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: 10.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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: keywords component
Message-ID: <bug-93996-4-5tDOYsCtKp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00108.txt
Content-length: 1842
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93996
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-checking
Component|target |rtl-optimization
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
We set mem_attr->expr to NULL with:
0x0000000000986a22 in memcpy (__len=56, __src=0x7fffffffd2b0,
__dest=0x7ffff7252ce8) at
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
34 return __builtin___memcpy_chk (__dest, __src, __len, __bos0
(__dest));
(gdb) bt
#0 0x0000000000986a22 in memcpy (__len=56, __src=0x7fffffffd2b0,
__dest=0x7ffff7252ce8) at
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
#1 set_mem_attrs (mem=0x7ffff7343a98, attrs=0x7fffffffd2b0) at
/bajas/pinskia/src/toolchain-10/scripts/../src/gcc/emit-rtl.c:387
#2 0x00000000009888c6 in set_mem_alias_set (mem=mem@entry=0x7ffff7343a98,
set=set@entry=-1) at
/bajas/pinskia/src/toolchain-10/scripts/../src/gcc/emit-rtl.c:2212
#3 0x000000000084631d in get_builtin_sync_mem (loc=<addr_expr 0x7ffff6c460c0>,
mode=mode@entry=E_SImode) at
/bajas/pinskia/src/toolchain-10/scripts/../src/gcc/builtins.c:6502
But change it to the incorrect thing with:
#0 add_reg_note (insn=insn@entry=0x7ffff7252cb0,
kind=kind@entry=REG_SAVE_NOTE, datum=<optimized out>) at
/bajas/pinskia/src/toolchain-10/scripts/../src/gcc/rtlanal.c:2399
2398 REG_NOTES (insn) = alloc_reg_note (kind, datum, REG_NOTES (insn));
Here insn is:
(note 35 33 23 4 [bb 4] NOTE_INSN_BASIC_BLOCK)
Since this insn is not a INSN but a note, REG_NOTES is not value.
RTL checking would have caught this issue.
>From gcc-bugs-return-672001-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:04:34 2020
Return-Path: <gcc-bugs-return-672001-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11319 invoked by alias); 2 Mar 2020 11:04: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 11222 invoked by uid 48); 2 Mar 2020 11:04:26 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93996] [10 Regression] ICE in lookup_page_table_entry
Date: Mon, 02 Mar 2020 11: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: ice-checking, ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-93996-4-xtIQq8Q8Fn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00110.txt
Content-length: 249
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93996
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #5)
> Since this insn is not a INSN but a note, REG_NOTES is not value.
s/value/valid/
>From gcc-bugs-return-672000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:04:12 2020
Return-Path: <gcc-bugs-return-672000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10452 invoked by alias); 2 Mar 2020 11:04: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 10407 invoked by uid 48); 2 Mar 2020 11:04:08 -0000
From: "kito at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93995] ICE in patch_jump_insn, at cfgrtl.c:1290 on riscv64-linux-gnu
Date: Mon, 02 Mar 2020 11:04: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: kito 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-93995-4-cLptu3UWIu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00109.txt
Content-length: 172
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93995
--- Comment #3 from Kito Cheng <kito at gcc dot gnu.org> ---
Ooop, confirmed, I am debugging now, thanks your report.
>From gcc-bugs-return-672002-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:10:16 2020
Return-Path: <gcc-bugs-return-672002-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17884 invoked by alias); 2 Mar 2020 11:10: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 17806 invoked by uid 48); 2 Mar 2020 11:10:11 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93996] [10 Regression] ICE in lookup_page_table_entry
Date: Mon, 02 Mar 2020 11:10: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-checking, ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-93996-4-ISynGhiyS0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93996-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00111.txt
Content-length: 761
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93996
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This seems to fix the issue (but I am not a scheduler expert and I am not 100%
sure about it):
diff --git a/gcc/haifa-sched.c b/gcc/haifa-sched.c
index 1d3de7b6a76..9ca986eabdd 100644
--- a/gcc/haifa-sched.c
+++ b/gcc/haifa-sched.c
@@ -4239,6 +4239,8 @@ remove_notes (rtx_insn *head, rtx_insn *tail)
if (insn != tail)
{
remove_insn (insn);
+ if (NOTE_P (next) && NOTE_KIND (next) == NOTE_INSN_BASIC_BLOCK)
+ next = NEXT_INSN (next);
add_reg_note (next, REG_SAVE_NOTE,
GEN_INT (NOTE_INSN_EPILOGUE_BEG));
break;
>From gcc-bugs-return-672003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:10:21 2020
Return-Path: <gcc-bugs-return-672003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18557 invoked by alias); 2 Mar 2020 11:10: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 18041 invoked by uid 55); 2 Mar 2020 11:10:17 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93966] [9/10 Regression] -fcf-protection -flto -g don't work togeter
Date: Mon, 02 Mar 2020 11:10: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93966-4-6DqziwvNxD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00112.txt
Content-length: 672
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93966
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:
https://gcc.gnu.org/g:577350603a657590c4b54a4a966cb49497e2514c
commit r10-6965-g577350603a657590c4b54a4a966cb49497e2514c
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Mon Mar 2 03:08:57 2020 -0800
lto: Also copy .note.gnu.property section
When generating the separate file with LTO debug sections, we should
also copy .note.gnu.property section.
PR lto/93966
* simple-object.c (handle_lto_debug_sections): Also copy
.note.gnu.property section.
>From gcc-bugs-return-672004-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:14:21 2020
Return-Path: <gcc-bugs-return-672004-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21585 invoked by alias); 2 Mar 2020 11:14: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 21540 invoked by uid 55); 2 Mar 2020 11:14:17 -0000
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93966] [9/10 Regression] -fcf-protection -flto -g don't work togeter
Date: Mon, 02 Mar 2020 11:14: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93966-4-a4ilsernwl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00113.txt
Content-length: 753
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93966
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by H.J. Lu <hjl@gcc.gnu.org>:
https://gcc.gnu.org/g:cb54729240b30f187a143e5e84193f5bb5029a40
commit r9-8317-gcb54729240b30f187a143e5e84193f5bb5029a40
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Mon Mar 2 03:08:57 2020 -0800
lto: Also copy .note.gnu.property section
When generating the separate file with LTO debug sections, we should
also copy .note.gnu.property section.
PR lto/93966
* simple-object.c (handle_lto_debug_sections): Also copy
.note.gnu.property section.
(cherry picked from commit 577350603a657590c4b54a4a966cb49497e2514c)
>From gcc-bugs-return-672005-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:21:00 2020
Return-Path: <gcc-bugs-return-672005-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54079 invoked by alias); 2 Mar 2020 11:21: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 54000 invoked by uid 48); 2 Mar 2020 11:20:56 -0000
From: "thenlich at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93871] COTAN is slow for complex types
Date: Mon, 02 Mar 2020 11:21: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: ice-on-valid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: thenlich at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93871-4-xIK6404KwB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00114.txt
Content-length: 513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93871
--- Comment #35 from Thomas Henlich <thenlich at gcc dot gnu.org> ---
(In reply to Steve Kargl from comment #34)
> Even this appears to have some irregularities as my exhaustive
> test in the interval [1.e-8,1) with direct call to sinf() yields
>
This looks like a job for FMA: "Correctly rounded multiplication by arbitrary
precision constants"
(http://perso.ens-lyon.fr/jean-michel.muller/MultConstant.html) show that it
can be proven to always work.
>From gcc-bugs-return-672006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:22:25 2020
Return-Path: <gcc-bugs-return-672006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56393 invoked by alias); 2 Mar 2020 11:22: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 56297 invoked by uid 48); 2 Mar 2020 11:22:21 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93966] [9/10 Regression] -fcf-protection -flto -g don't work togeter
Date: Mon, 02 Mar 2020 11:22: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93966-4-G1EhLrYdMZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00115.txt
Content-length: 874
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93966
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Richard Biener from comment #3)
> Isn't this a linker bug? There's no code sections in the debug object.
This is a good question.
> Also you need to provide -fcf-protection at compile-time as well, not
> only at link-time (technically only at compile-time). Otherwise success
> is not guaranteed.
That is correct.
> I'm not aware why it should work with GCC 8 btw.
It is because GCC 8 doesn't have early LTO debug.
Fixed for GCC 10 and GCC 9.3.
>From gcc-bugs-return-672007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:26:54 2020
Return-Path: <gcc-bugs-return-672007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59504 invoked by alias); 2 Mar 2020 11:26: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 59477 invoked by uid 48); 2 Mar 2020 11:26:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93951] [8/9/10 Regression] ICE with '-flto -g -femit-struct-debug-baseonly'
Date: Mon, 02 Mar 2020 11:26: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: 9.2.1
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: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93951-4-p8HqeI0qMZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93951-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00116.txt
Content-length: 5087
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93951
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
The issue is that we have
DIE 0: DW_TAG_compile_unit (0x7ffff6837000)
abbrev id: 0 offset: 0 mark: 1
DW_AT_producer: "GNU C++17 10.0.1 20200302 (experimental) -g -flto
-femit-struct-debug-baseonly -std=c++17 -fno-eliminate-unused-debug-symbols"
DW_AT_language: 4
DW_AT_name: "t.ii"
DW_AT_comp_dir: "/abuild/rguenther/obj-work2-g/gcc"
DW_AT_stmt_list: label: *.Ldebug_line0
DIE 0: DW_TAG_namespace (0x7ffff6837140)
abbrev id: 0 offset: 0 mark: 1
DW_AT_name: "std"
DW_AT_decl_file: "<built-in>" (0)
DW_AT_decl_line: 0
DW_AT_sibling: die -> 0 (0x7ffff6837230)
DIE 0: DW_TAG_structure_type (0x7ffff68371e0)
abbrev id: 0 offset: 0 mark: 1
DW_AT_name: "A<V::m_fn2()::<lambda()> >"
DW_AT_declaration: 1
DIE 0: DW_TAG_template_type_param (0x7ffff6837410)
abbrev id: 0 offset: 0 mark: 1
DW_AT_name: "_Tp"
DW_AT_type: die -> 0 (0x7ffff68373c0)
but something pruned that last referenced DIE so it doens't get marked
and thus appears external. We're eventually coming from
0x0000000000fa2679 in generic_parameter_die (
parm=<type_decl 0x7ffff683cbe0 _Visitor>,
arg=<record_type 0x7ffff6968d20 ._anon_0>, emit_name_p=true,
parent_die=<dw_die_ref 0x7ffff6837190 DW_TAG_structure_type
<parent=0x7ffff6837140 DW_TAG_namespace>>)
at /space/rguenther/src/gcc-work2/gcc/dwarf2out.c:13665
(gdb) l
13660 TMPL_DIE should have a child DW_AT_type attribute that is
set
13661 to the type of the argument to PARM, which is ARG.
13662 If PARM is a type generic parameter, TMPL_DIE should have
a
13663 child DW_AT_type that is set to ARG. */
13664 tmpl_type = TYPE_P (arg) ? arg : TREE_TYPE (arg);
13665 add_type_attribute (tmpl_die, tmpl_type,
13666 (TREE_THIS_VOLATILE (tmpl_type)
13667 ? TYPE_QUAL_VOLATILE :
TYPE_UNQUALIFIED),
13668 false, parent_die);
(gdb) bt
#0 0x0000000000fa2679 in generic_parameter_die (
parm=<type_decl 0x7ffff683cbe0 _Visitor>,
arg=<record_type 0x7ffff6968d20 ._anon_0>, emit_name_p=true,
parent_die=<dw_die_ref 0x7ffff6837190 DW_TAG_structure_type
<parent=0x7ffff6837140 DW_TAG_namespace>>)
at /space/rguenther/src/gcc-work2/gcc/dwarf2out.c:13665
#1 0x0000000000fa23c5 in gen_generic_params_dies (
t=<record_type 0x7ffff6979150 __gen_vtable>)
at /space/rguenther/src/gcc-work2/gcc/dwarf2out.c:13585
#2 0x0000000000fc9fc6 in gen_scheduled_generic_parms_dies ()
at /space/rguenther/src/gcc-work2/gcc/dwarf2out.c:27138
#3 0x0000000000fd51d7 in dwarf2out_early_finish (
filename=0x7fffffffe1c6 "t.ii")
at /space/rguenther/src/gcc-work2/gcc/dwarf2out.c:32065
and that isn't expected to generate limbo dies. The
gen_scheduled_generic_parms_dies function says
/* Generate generic parameters DIEs for instances of generic types
that have been previously scheduled by
schedule_generic_params_dies_gen. This function must be called
after all the types of the CU have been laid out. */
but not all types of the CU have been laid out as obviously seen.
I'm really not sure that the implementation of -femit-struct-debug-
via should_emit_struct_debug () is sane. Preventing initial DIE
generation is really fragile and instead later pruning everything
we don't want is much easier to get correct.
Now, a fix for the testcase at hand would be to flush limbos one step later,
but that may simply paper over the underlying issue.
diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
index bb45279ea56..54075b011bf 100644
--- a/gcc/dwarf2out.c
+++ b/gcc/dwarf2out.c
@@ -32058,11 +32058,12 @@ dwarf2out_early_finish (const char *filename)
emit full debugging info for them. */
retry_incomplete_types ();
+ gen_scheduled_generic_parms_dies ();
+
/* The point here is to flush out the limbo list so that it is empty
and we don't need to stream it for LTO. */
flush_limbo_die_list ();
- gen_scheduled_generic_parms_dies ();
gen_remaining_tmpl_value_param_die_attribute ();
/* Add DW_AT_linkage_name for all deferred DIEs. */
Note for non-LTO it "works" because we flush limbos again in dwarf2out_finish
before marking DIEs which doesn't happen before we output the early debug.
That said, I wouldn't expect gen_scheduled_generic_parms_dies to generate
type DIEs in limbo. Limbo flushing may generate new DIEs as well and
IIRC ones with generic param DIEs, this was the reason of flushing
before. I'd hate to "iterate" here.
Jason?
>From gcc-bugs-return-672008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:28:25 2020
Return-Path: <gcc-bugs-return-672008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60917 invoked by alias); 2 Mar 2020 11:28: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 60877 invoked by uid 55); 2 Mar 2020 11:28:21 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93966] [9/10 Regression] -fcf-protection -flto -g don't work togeter
Date: Mon, 02 Mar 2020 11:28: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93966-4-AINJUnJs6x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00117.txt
Content-length: 1187
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93966
--- Comment #7 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 2 Mar 2020, hjl.tools at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93966
>
> H.J. Lu <hjl.tools at gmail dot com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|NEW |RESOLVED
> Resolution|--- |FIXED
>
> --- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> ---
> (In reply to Richard Biener from comment #3)
> > Isn't this a linker bug? There's no code sections in the debug object.
>
> This is a good question.
>
> > Also you need to provide -fcf-protection at compile-time as well, not
> > only at link-time (technically only at compile-time). Otherwise success
> > is not guaranteed.
>
> That is correct.
>
> > I'm not aware why it should work with GCC 8 btw.
>
> It is because GCC 8 doesn't have early LTO debug.
It does but section copying has been made more explicit about notes
only in GCC 9 it seems.
>From gcc-bugs-return-672009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:34:14 2020
Return-Path: <gcc-bugs-return-672009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69291 invoked by alias); 2 Mar 2020 11:34: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 69205 invoked by uid 48); 2 Mar 2020 11:34:10 -0000
From: "kito at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90883] Generated code is worse if returned struct is unnamed
Date: Mon, 02 Mar 2020 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: 9.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kito 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90883-4-kr4FGcSctU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90883-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90883-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00118.txt
Content-length: 399
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90883
--- Comment #30 from Kito Cheng <kito at gcc dot gnu.org> ---
After add --param max-inline-insns-size=1 to compile flags, x86, x86_64, rv32,
rv64, nds32 and arm are "Deleted redundant store" at dse1.
But mips, mips64 and aarch64 still not pass the scan testing since those 3
targets are expand "<retval> = {}" to loop at earlier passes.
>From gcc-bugs-return-672010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:39:49 2020
Return-Path: <gcc-bugs-return-672010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115247 invoked by alias); 2 Mar 2020 11:39: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 115139 invoked by uid 48); 2 Mar 2020 11:39:41 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93966] [9/10 Regression] -fcf-protection -flto -g don't work togeter
Date: Mon, 02 Mar 2020 11:39: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93966-4-TRUrIuwfoe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93966-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-03/txt/msg00119.txt
Content-length: 684
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93966
--- Comment #8 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to rguenther@suse.de from comment #7)
> >
> > It is because GCC 8 doesn't have early LTO debug.
>
> It does but section copying has been made more explicit about notes
> only in GCC 9 it seems.
GCC 8 has the same bug:
[hjl@gnu-cfl-2 tmp]$ /usr/gcc-8.2.1-x32/bin/gcc -flto -c -fcf-protection x.c -g
[hjl@gnu-cfl-2 tmp]$ /usr/gcc-8.2.1-x32/bin/gcc -flto -Wl,-z,cet-report=error
-fcf-protection x.o -g
/usr/local/bin/ld: /tmp/cc6vezl6debugobj: error: missing IBT and SHSTK
properties
collect2: error: ld returned 1 exit status
[hjl@gnu-cfl-2 tmp]$
>From gcc-bugs-return-672011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 02 11:41:52 2020
Return-Path: <gcc-bugs-return-672011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117988 invoked by alias); 2 Mar 2020 11:41: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 117929 invoked by uid 89); 2 Mar 2020 11:41:51 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=3.4 required=5.0 tests=AWL,BAYES_50,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_GREY autolearn=no version=3.3.1 spammy=photos, icons, H*F:U*test, H*Ad:U*test
X-HELO: xvfrqvdv.outbound-mail.sendgrid.net
Received: from xvfrqvdv.outbound-mail.sendgrid.net (HELO xvfrqvdv.outbound-mail.sendgrid.net) (168.245.72.216) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 02 Mar 2020 11:41:49 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sendgrid.net; h=content-type:mime-version:subject:to:from; s=smtpapi; bh=T9UpDaWJFTZkDCYFLiZ7T7BzJPMc/zrWL+U5Mk1JaPc=; b=pZMg5XH5+sZsR JD+oKyiAdA3RbxFHHyaGNnNzUfJ10Igv03yQhmJpbbKDgMxMBNRBTgyRLt/vlgtl s02ex9w1YTmVcH55leyJGRT+5vCxCZCbHiYHF9MY56BVmX47EVRJFVOgp6lnYRqn rTcKtYzK3/EsahrGou6CQgZnJ66nCgReceived: by filter1904p1mdw1.sendgrid.net with SMTP id filter1904p1mdw1-19158-5E5CE508-7 2020-03-02 10:50:48.286301536 +0000 UTC m=+1551166.326140365
Received: from [151.80.8.16] (unknown [151.80.8.16]) by ismtpd0006p1lon1.sendgrid.net (SG) with ESMTP id _BsXlUImRG69mSjK8mqxqQ for <gcc-bugs@gcc.gnu.org>; Mon, 02 Mar 2020 10:50:48.112 +0000 (UTC)
MIME-Version: 1.0
Subject: Your Account is under review
To: gcc-bugs@gcc.gnu.org
From: Server <test@mxsouth.com>
Date: Mon, 02 Mar 2020 11:41:00 -0000
Message-ID: <_BsXlUImRG69mSjK8mqxqQ@ismtpd0006p1lon1.sendgrid.net>
X-SG-EID: so+5eOIRbGkGykpCG15cyLckLIUjz5743fjk2uK2FzK+AMn2KQdGcVW4Tfn7HXJeC9RDdbFZU07yNQ gialjuIZELCjbH8lImALvrS6ZjBR0FPu5x7RFMp4BFWqLuaIqQLmXHzSk/9Fvm72zjJ14stfwGyL/d kUKltkUxaB56cH/GL/rmzQLTehvLZWmx0iBTLRn/HEJ0IQHyVib9uqdXsA=Content-Description: Mail message body
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2020-03/txt/msg00120.txt
Content-length: 698
Your Account will be disabled
Account gcc-bugs@gcc.gnu.org will be disabled. It looks like it was being used in a way that violated our policies.
We understand your account is important to you. So if you think this was a mistake, sign in to the disabled account and submit a request to restore it. You'll need to do this soon, because disabled accounts are eventually deleted, along with your emails, contacts, photos, and other data stored . Try to restore You received this email to let you know about important changes to your Google Account and services. © 2019 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (4 preceding siblings ...)
2020-02-25 14:55 ` [Bug middle-end/61577] [4.9.0 Regression] " peter.bisroev at groundlabs dot com
@ 2020-04-18 1:11 ` dave.anglin at bell dot net
2020-04-23 15:48 ` peter.bisroev at groundlabs dot com
` (73 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2020-04-18 1:11 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #206 from dave.anglin at bell dot net ---
Does adding the linker option "-Wl,-O" help to reduce the size of cc1 and
cc1plus?
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (5 preceding siblings ...)
2020-04-18 1:11 ` dave.anglin at bell dot net
@ 2020-04-23 15:48 ` peter.bisroev at groundlabs dot com
2020-04-23 16:50 ` dave.anglin at bell dot net
` (72 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: peter.bisroev at groundlabs dot com @ 2020-04-23 15:48 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
Peter Bisroev <peter.bisroev at groundlabs dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |peter.bisroev at groundlabs dot co
| |m
--- Comment #207 from Peter Bisroev <peter.bisroev at groundlabs dot com> ---
(In reply to dave.anglin from comment #206)
> Does adding the linker option "-Wl,-O" help to reduce the size of cc1 and
> cc1plus?
Hi Dave, sorry for the delayed response. That is a good catch, I missed that
option before. I will be able to test this out this weekend. Will let you know
asap.
Thanks!
--peter
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (6 preceding siblings ...)
2020-04-23 15:48 ` peter.bisroev at groundlabs dot com
@ 2020-04-23 16:50 ` dave.anglin at bell dot net
2020-05-02 4:14 ` peter.bisroev at groundlabs dot com
` (71 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2020-04-23 16:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #208 from dave.anglin at bell dot net ---
On 2020-04-23 11:48 a.m., peter.bisroev at groundlabs dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
>
> Peter Bisroev <peter.bisroev at groundlabs dot com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |peter.bisroev at groundlabs dot co
> | |m
>
> --- Comment #207 from Peter Bisroev <peter.bisroev at groundlabs dot com> ---
> (In reply to dave.anglin from comment #206)
>> Does adding the linker option "-Wl,-O" help to reduce the size of cc1 and
>> cc1plus?
> Hi Dave, sorry for the delayed response. That is a good catch, I missed that
> option before. I will be able to test this out this weekend. Will let you know
> asap.
I saw it perusing the comments for weak support on PA-RISC. I believe that I
found that shared libraries
are automatically garbage collected but applications are not.
Dave
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (7 preceding siblings ...)
2020-04-23 16:50 ` dave.anglin at bell dot net
@ 2020-05-02 4:14 ` peter.bisroev at groundlabs dot com
2020-05-02 14:30 ` dave.anglin at bell dot net
` (70 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: peter.bisroev at groundlabs dot com @ 2020-05-02 4:14 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #209 from Peter Bisroev <peter.bisroev at groundlabs dot com> ---
(In reply to dave.anglin from comment #206)
> Does adding the linker option "-Wl,-O" help to reduce the size of cc1 and
> cc1plus?
Hi Dave,
Sorry for the delayed response. I have tried linker option "-Wl,-O" but it does
not seem to make any difference. I used gcc 4.7.4 compiled with --enable-comdat
option as per my comment 181 and get the same number of PCREL21B errors as
before. I wonder if HPs linker does garbage collection after it deals with all
the relocations first.
Looks like we might have to get the fix into GNU AS first to get PCREL60B
working. I will try to look into how we can get this done hopefully next
weekend.
Thanks!
--peter
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (8 preceding siblings ...)
2020-05-02 4:14 ` peter.bisroev at groundlabs dot com
@ 2020-05-02 14:30 ` dave.anglin at bell dot net
2020-05-13 18:03 ` jared.martinsen at fiserv dot com
` (69 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2020-05-02 14:30 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #210 from dave.anglin at bell dot net ---
On 2020-05-02 12:14 a.m., peter.bisroev at groundlabs dot com wrote:
> Looks like we might have to get the fix into GNU AS first to get PCREL60B
> working. I will try to look into how we can get this done hopefully next
> weekend.
I agree.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (9 preceding siblings ...)
2020-05-02 14:30 ` dave.anglin at bell dot net
@ 2020-05-13 18:03 ` jared.martinsen at fiserv dot com
2020-05-13 19:04 ` dave.anglin at bell dot net
` (68 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jared.martinsen at fiserv dot com @ 2020-05-13 18:03 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
Jared <jared.martinsen at fiserv dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jared.martinsen at fiserv dot com
--- Comment #211 from Jared <jared.martinsen at fiserv dot com> ---
Are these errors the same as described above?
It give the following 2 errors:
ld: The value 0xfffffffffe38a260 does not fit when applying the relocation
PCREL21B for symbol ".text" at offset 0x22 in
section index 222 of file
/library/home/build/tapecut5/code/lib/libsubo.a[file1.o]
ld: The value 0xfffffffffe587970 does not fit when applying the relocation
PCREL21B for symbol ".text" at offset 0x22 in
section index 2125 of file
/library/home/build/tapecut5/code/lib/libsubo.a[file2.o]
Using gcc version 4.2.3. On 64 bit HP-UX
Here is the raw command line.
/usr/local/bin/g++ /library/home/build/tapecut5/code/obj/ocu00.o -z
-L/usr/local/lib/hpux32 -lxerces-c -lxerces-depdom -
L/opt/eloquence/8.2/lib/hpux32 -leqdb -limage3k -lfwutil
-L/library/home/build/tapecut5/code/lib -lsubo -lsubr -L/librar
y/home/build/tapecut5/code/spx/lib -lspx -lm -lcrypto -lssl -o
/library/home/build/tapecut5/code/bin/spectrum
Is there a fix for this? Newer compiler or an option?
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (10 preceding siblings ...)
2020-05-13 18:03 ` jared.martinsen at fiserv dot com
@ 2020-05-13 19:04 ` dave.anglin at bell dot net
2021-04-16 21:30 ` pinskia at gcc dot gnu.org
` (67 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2020-05-13 19:04 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #212 from dave.anglin at bell dot net ---
On 2020-05-13 2:03 p.m., jared.martinsen at fiserv dot com wrote:
> --- Comment #211 from Jared <jared.martinsen at fiserv dot com> ---
> Are these errors the same as described above?
>
> It give the following 2 errors:
> ld: The value 0xfffffffffe38a260 does not fit when applying the relocation
> PCREL21B for symbol ".text" at offset 0x22 in
> section index 222 of file
> /library/home/build/tapecut5/code/lib/libsubo.a[file1.o]
> ld: The value 0xfffffffffe587970 does not fit when applying the relocation
> PCREL21B for symbol ".text" at offset 0x22 in
> section index 2125 of file
> /library/home/build/tapecut5/code/lib/libsubo.a[file2.o]
Yes. Most likely these are references to weak symbols. Compiling with -Os
might help.
>
>
>
> Using gcc version 4.2.3. On 64 bit HP-UX
> Here is the raw command line.
> /usr/local/bin/g++ /library/home/build/tapecut5/code/obj/ocu00.o -z
> -L/usr/local/lib/hpux32 -lxerces-c -lxerces-depdom -
> L/opt/eloquence/8.2/lib/hpux32 -leqdb -limage3k -lfwutil
> -L/library/home/build/tapecut5/code/lib -lsubo -lsubr -L/librar
> y/home/build/tapecut5/code/spx/lib -lspx -lm -lcrypto -lssl -o
> /library/home/build/tapecut5/code/bin/spectrum
>
> Is there a fix for this? Newer compiler or an option?
>
No. They block building latter versions of gcc that require g++.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (11 preceding siblings ...)
2020-05-13 19:04 ` dave.anglin at bell dot net
@ 2021-04-16 21:30 ` pinskia at gcc dot gnu.org
2021-04-24 22:21 ` peter at int19h dot net
` (66 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-04-16 21:30 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #213 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Does this still happen with GCC 8 or above?
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (12 preceding siblings ...)
2021-04-16 21:30 ` pinskia at gcc dot gnu.org
@ 2021-04-24 22:21 ` peter at int19h dot net
2021-05-17 9:56 ` jvb at cyberscience dot com
` (65 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: peter at int19h dot net @ 2021-04-24 22:21 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #214 from Peter Bisroev <peter at int19h dot net> ---
(In reply to Andrew Pinski from comment #213)
> Does this still happen with GCC 8 or above?
Hi Andrew, yes it does from my last tests. As we have found out here, before
newer versions of GCC can work on HP-UX we need to get a working gas. Please
refer to this gas Bugzilla ticket for details:
https://sourceware.org/bugzilla/show_bug.cgi?id=25599
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (13 preceding siblings ...)
2021-04-24 22:21 ` peter at int19h dot net
@ 2021-05-17 9:56 ` jvb at cyberscience dot com
2021-05-19 16:23 ` dave.anglin at bell dot net
` (64 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-05-17 9:56 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
John Buddery <jvb at cyberscience dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvb at cyberscience dot com
--- Comment #215 from John Buddery <jvb at cyberscience dot com> ---
I recently upgraded my hp-ix ia64 gcc build to 11.1.0, and I thought I'd share
what I did in case it's useful for anyone still following this thread.
I started with the patches in this thread, and soon got to the 21 bit
relocation errors.
Thanks to the excellent PCREL60B analysis above, I applied this simple edit to
binutils 2.36 (you have to enable obsoletes to get a build):
--- binutils-2.36/gas/config/tc-ia64.c 2021-01-09 10:47:33.000000000 +0000
+++ binutils-2.36-snake/gas/config/tc-ia64.c 2021-05-17 10:21:40.651307362
+0100
@@ -6892,7 +6892,13 @@
for (j = 0; j < md.slot[curr].num_fixups; ++j)
{
ifix = md.slot[curr].fixup + j;
- fix = fix_new_exp (frag_now, frag_now_fix () - 16 + i, 8,
+
+ unsigned long where = frag_now_fix () - 16 + i;
+#ifdef TE_HPUX
+ if ( ifix->code == BFD_RELOC_IA64_PCREL60B ) where++;
+#endif
+
+ fix = fix_new_exp (frag_now, where, 8,
&ifix->expr, ifix->is_pcrel, ifix->code);
fix->tc_fix_data.opnd = ifix->opnd;
fix->fx_file = md.slot[curr].src_file;
This fixes, for HP only, the PCTEL60B offset to be what the HP linker expects.
I don't know if the same is appropriate for Linux ia-64 or not, as I don't have
access to that environment. I'll add that to the binutils bug report as well,
but I've included it here so people can find it for gcc more easily.
With the working as, I changed gcc to use brl instructions for calls, including
tail calls:
--- gcc-11.1.0/gcc/config/ia64/ia64.md 2021-04-27 11:00:13.000000000 +0100
+++ gcc-11.1.0-snake/gcc/config/ia64/ia64.md 2021-05-13 14:49:21.000000000
+0100
@@ -4410,7 +4410,9 @@
(const_int 0))
(clobber (match_operand:DI 1 "register_operand" "=b,b"))]
""
- "br.call%+.many %1 = %0"
+ "@
+ br.call%+.many %1 = %0
+ brl.call%+.many %1 = %0"
[(set_attr "itanium_class" "br,scall")])
(define_insn "call_value_nogp"
@@ -4419,14 +4421,18 @@
(const_int 0)))
(clobber (match_operand:DI 2 "register_operand" "=b,b"))]
""
- "br.call%+.many %2 = %1"
+ "@
+ br.call%+.many %2 = %1
+ brl.call%+.many %2 = %1"
[(set_attr "itanium_class" "br,scall")])
(define_insn "sibcall_nogp"
[(call (mem:DI (match_operand:DI 0 "call_operand" "?b,s"))
(const_int 0))]
""
- "br%+.many %0"
+ "@
+ br%+.many %0
+ brl%+.many %0"
[(set_attr "itanium_class" "br,scall")])
(define_insn "call_gp"
You have to be careful only to use brl on immediate calls, the assembler does
not accept brl with registers.
The above unconditionally uses brl - on hp-ux and other platforms. This would
work very badly (if at all) on an Itanium 1 (but I'm not sure they are still
around), and is slightly less efficient even on Itanium 2. So, possibly this
should be more limited, maybe using -mlong-call as requesting in Bug 20819 ?
Anyway, with the assembler patch and the brl patch, along with the other
patches in this thread, gcc 11.1.0 will successfully bootstrap in both 32 and
64 bits, and seems to work well - I've built a large 64 bit project with no
problems so far.
There are a lot of fails from the testsuite, but I suspect that's normal for
this os (I'll post results to the testresults list).
---
John
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (14 preceding siblings ...)
2021-05-17 9:56 ` jvb at cyberscience dot com
@ 2021-05-19 16:23 ` dave.anglin at bell dot net
2021-05-20 9:19 ` jvb at cyberscience dot com
` (63 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2021-05-19 16:23 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #216 from dave.anglin at bell dot net ---
On 2021-05-17 5:56 a.m., jvb at cyberscience dot com wrote:
> With the working as, I changed gcc to use brl instructions for calls, including
> tail calls:
>
> --- gcc-11.1.0/gcc/config/ia64/ia64.md 2021-04-27 11:00:13.000000000 +0100
> +++ gcc-11.1.0-snake/gcc/config/ia64/ia64.md 2021-05-13 14:49:21.000000000
> +0100
> @@ -4410,7 +4410,9 @@
> (const_int 0))
> (clobber (match_operand:DI 1 "register_operand" "=b,b"))]
> ""
> - "br.call%+.many %1 = %0"
> + "@
> + br.call%+.many %1 = %0
> + brl.call%+.many %1 = %0"
> [(set_attr "itanium_class" "br,scall")])
>
> (define_insn "call_value_nogp"
> @@ -4419,14 +4421,18 @@
> (const_int 0)))
> (clobber (match_operand:DI 2 "register_operand" "=b,b"))]
> ""
> - "br.call%+.many %2 = %1"
> + "@
> + br.call%+.many %2 = %1
> + brl.call%+.many %2 = %1"
> [(set_attr "itanium_class" "br,scall")])
>
> (define_insn "sibcall_nogp"
> [(call (mem:DI (match_operand:DI 0 "call_operand" "?b,s"))
> (const_int 0))]
> ""
> - "br%+.many %0"
> + "@
> + br%+.many %0
> + brl%+.many %0"
> [(set_attr "itanium_class" "br,scall")])
>
> (define_insn "call_gp"
We only should use brl when TARGET_HPUX and ia64_tune == PROCESSOR_ITANIUM2. I
wouldn't worry too much
about it being slightly less efficient. You can use the pattern constraint to
implement this.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (15 preceding siblings ...)
2021-05-19 16:23 ` dave.anglin at bell dot net
@ 2021-05-20 9:19 ` jvb at cyberscience dot com
2021-05-20 13:25 ` dave.anglin at bell dot net
` (62 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-05-20 9:19 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #217 from John Buddery <jvb at cyberscience dot com> ---
Thanks very much for adding the binutils patch.
Sorry, I'm new to .md definitions, so I've probably got this wrong. Did you
mean something like:
(define_insn "call_nogp_longcall"
[(call (mem:DI (match_operand:DI 0 "call_operand" "?b,s"))
(const_int 0))
(clobber (match_operand:DI 1 "register_operand" "=b,b"))]
"TARGET_HPUX && ia64_tune == PROCESSOR_ITANIUM2"
"@
br.call%+.many %1 = %0
brl.call%+.many %1 = %0"
[(set_attr "itanium_class" "br,scall")])
(define_insn "call_nogp"
[(call (mem:DI (match_operand:DI 0 "call_operand" "?b,s"))
(const_int 0))
(clobber (match_operand:DI 1 "register_operand" "=b,b"))]
""
"br.call%+.many %1 = %0"
[(set_attr "itanium_class" "br,scall")])
I assume you need a second instruction to catch the case where the condition
doesn't match ?
Itanium 1 support seems to have been dropped at some point, so -mtune only
accepts options mapping to Itanium2. So, I couldn't test the br case on HP.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (16 preceding siblings ...)
2021-05-20 9:19 ` jvb at cyberscience dot com
@ 2021-05-20 13:25 ` dave.anglin at bell dot net
2021-05-20 13:37 ` jvb at cyberscience dot com
` (61 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2021-05-20 13:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #218 from dave.anglin at bell dot net ---
On 2021-05-20 5:19 a.m., jvb at cyberscience dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
>
> --- Comment #217 from John Buddery <jvb at cyberscience dot com> ---
> Thanks very much for adding the binutils patch.
>
> Sorry, I'm new to .md definitions, so I've probably got this wrong. Did you
> mean something like:
>
> (define_insn "call_nogp_longcall"
> [(call (mem:DI (match_operand:DI 0 "call_operand" "?b,s"))
> (const_int 0))
> (clobber (match_operand:DI 1 "register_operand" "=b,b"))]
> "TARGET_HPUX && ia64_tune == PROCESSOR_ITANIUM2"
> "@
> br.call%+.many %1 = %0
> brl.call%+.many %1 = %0"
> [(set_attr "itanium_class" "br,scall")])
>
> (define_insn "call_nogp"
> [(call (mem:DI (match_operand:DI 0 "call_operand" "?b,s"))
> (const_int 0))
> (clobber (match_operand:DI 1 "register_operand" "=b,b"))]
> ""
> "br.call%+.many %1 = %0"
> [(set_attr "itanium_class" "br,scall")])
>
> I assume you need a second instruction to catch the case where the condition
> doesn't match ?
Yes. Note that the call_nogp pattern is output directly in a couple of places
in ia64.c. These
will need adjustment for hpux.
I'm not a ia64 maintainer. I can only apply changes specific to hpux.
I have limited knowledge of the ia64 instruction set. In the above, the
"brl.call" alternative
apples to the "s" constraint for operand 0. Is that what you want? The
"br.call" form is used
for the disparaged "b" constraint for operand 0.
I'm not sure that the scall call attribute is correct for brl.
>
> Itanium 1 support seems to have been dropped at some point, so -mtune only
> accepts options mapping to Itanium2. So, I couldn't test the br case on HP.
Then, we don't need to check the ia64_tune in the above.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (17 preceding siblings ...)
2021-05-20 13:25 ` dave.anglin at bell dot net
@ 2021-05-20 13:37 ` jvb at cyberscience dot com
2021-05-20 14:02 ` dave.anglin at bell dot net
` (60 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-05-20 13:37 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #219 from John Buddery <jvb at cyberscience dot com> ---
Great, thanks - I'll look at ia64.c and build and test with that change.
Yes, "b" on ia64 seems to be a branch register, and the brl op only accepts
immediate values not registers. Initially I hoped the assembler would patch
this up and accept both, but it doesn't so the two variants are needed.
I'll look into the scall attribute as well.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (18 preceding siblings ...)
2021-05-20 13:37 ` jvb at cyberscience dot com
@ 2021-05-20 14:02 ` dave.anglin at bell dot net
2021-05-20 14:59 ` jvb at cyberscience dot com
` (59 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2021-05-20 14:02 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #220 from dave.anglin at bell dot net ---
On 2021-05-20 9:37 a.m., jvb at cyberscience dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
>
> --- Comment #219 from John Buddery <jvb at cyberscience dot com> ---
> Great, thanks - I'll look at ia64.c and build and test with that change.
Instead of creating a separate HPUX pattern, another way might be to setup
an instruction alternative table. See define_insn for prefetch.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (19 preceding siblings ...)
2021-05-20 14:02 ` dave.anglin at bell dot net
@ 2021-05-20 14:59 ` jvb at cyberscience dot com
2021-05-20 15:03 ` dave.anglin at bell dot net
` (58 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-05-20 14:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #221 from John Buddery <jvb at cyberscience dot com> ---
Thanks - that is neater, as it avoids the need to change the calls in ia64.c,
which gets messy.
The simplest variant I have is:
(define_insn "call_nogp"
[(call (mem:DI (match_operand:DI 0 "call_operand" "?b,s"))
(const_int 0))
(clobber (match_operand:DI 1 "register_operand" "=b,b"))]
""
{
if (TARGET_HPUX && which_alternative == 1 )
return "brl.call%+.many %1 = %0";
else
return "br.call%+.many %1 = %0";
}
[(set_attr "itanium_class" "br,scall")])
but I need to work out how to vary the attribute, as you were right: scall maps
to a "B" type attribute, but brl is an L+X instruction not a pure B unit
instruction, so I think it should be type "L".
Looks like cond and match-test are valid for attributes, so it should be
possible to get this right.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (20 preceding siblings ...)
2021-05-20 14:59 ` jvb at cyberscience dot com
@ 2021-05-20 15:03 ` dave.anglin at bell dot net
2021-05-20 15:16 ` dave.anglin at bell dot net
` (57 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2021-05-20 15:03 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #222 from dave.anglin at bell dot net ---
On 2021-05-20 10:02 a.m., dave.anglin at bell dot net wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
>
> --- Comment #220 from dave.anglin at bell dot net ---
> On 2021-05-20 9:37 a.m., jvb at cyberscience dot com wrote:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
>>
>> --- Comment #219 from John Buddery <jvb at cyberscience dot com> ---
>> Great, thanks - I'll look at ia64.c and build and test with that change.
> Instead of creating a separate HPUX pattern, another way might be to setup
> an instruction alternative table. See define_insn for prefetch.
There is a which_alternative variable that could be used to check for "s"
constraint
(e.g., "which_alternative == 1").
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (21 preceding siblings ...)
2021-05-20 15:03 ` dave.anglin at bell dot net
@ 2021-05-20 15:16 ` dave.anglin at bell dot net
2021-05-20 17:00 ` dave.anglin at bell dot net
` (56 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2021-05-20 15:16 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #223 from dave.anglin at bell dot net ---
On 2021-05-20 10:59 a.m., jvb at cyberscience dot com wrote:
> The simplest variant I have is:
>
> (define_insn "call_nogp"
> [(call (mem:DI (match_operand:DI 0 "call_operand" "?b,s"))
> (const_int 0))
> (clobber (match_operand:DI 1 "register_operand" "=b,b"))]
> ""
> {
> if (TARGET_HPUX && which_alternative == 1 )
> return "brl.call%+.many %1 = %0";
> else
> return "br.call%+.many %1 = %0";
> }
This looks good.
I agree it should be possible to get the attribute right for brl.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (22 preceding siblings ...)
2021-05-20 15:16 ` dave.anglin at bell dot net
@ 2021-05-20 17:00 ` dave.anglin at bell dot net
2021-05-20 17:22 ` jvb at cyberscience dot com
` (55 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2021-05-20 17:00 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #224 from dave.anglin at bell dot net ---
On 2021-05-20 10:59 a.m., jvb at cyberscience dot com wrote:
> but I need to work out how to vary the attribute, as you were right: scall maps
> to a "B" type attribute, but brl is an L+X instruction not a pure B unit
> instruction, so I think it should be type "L".
I think brl needs its own class. Currently, long_i (for movl) and nop_x (for
nop.x) map to type "L".
The brl class should also map to type "L" but its bypass behavior should be
similar to scall.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (23 preceding siblings ...)
2021-05-20 17:00 ` dave.anglin at bell dot net
@ 2021-05-20 17:22 ` jvb at cyberscience dot com
2021-06-03 17:19 ` dave.anglin at bell dot net
` (54 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-05-20 17:22 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #225 from John Buddery <jvb at cyberscience dot com> ---
Yes, I looked briefly at that - I added a new class, but then started hitting
bundling errors because it wasn't being positioned correctly in the 3
instruction bundle.
It will need more changes to itanium2.md, which looks at the actual
itanium_class rather than just the derived type as I was expecting, and fixes
the bundling for long_i only (rather than type L).
For now I've reverted to scall to test the other changes - this seems to work,
probably because the assembler is fixing up any bundling issues
This isn't really right though, as you say it needs combined long_i and scall
behaviour for a new type.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (24 preceding siblings ...)
2021-05-20 17:22 ` jvb at cyberscience dot com
@ 2021-06-03 17:19 ` dave.anglin at bell dot net
2021-06-09 9:51 ` jvb at cyberscience dot com
` (53 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2021-06-03 17:19 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #226 from dave.anglin at bell dot net ---
John, would you please post your full patch set for ia64-hpux? This will help
others.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (25 preceding siblings ...)
2021-06-03 17:19 ` dave.anglin at bell dot net
@ 2021-06-09 9:51 ` jvb at cyberscience dot com
2021-06-09 10:12 ` jvb at cyberscience dot com
` (52 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-06-09 9:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #227 from John Buddery <jvb at cyberscience dot com> ---
Created attachment 50970
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50970&action=edit
Patches for gcc-11.1.0, hp-ia64
Mostly patches from this thread, apart from ia64.md which adds support for
using long calls (brl).
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (26 preceding siblings ...)
2021-06-09 9:51 ` jvb at cyberscience dot com
@ 2021-06-09 10:12 ` jvb at cyberscience dot com
2021-07-04 21:56 ` me at larbob dot org
` (51 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-06-09 10:12 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #228 from John Buddery <jvb at cyberscience dot com> ---
Sorry it took a while, I've been away for a bit and have lots to catch up on.
These patches are for 11.1.0, but should work on earlier versions too. With
this I have a working gcc which I've tested on several large projects.
Most of the patch is a cumulation of the patches posted earlier in this thread
- unsigned pointer extension, reverting @gprel changes etc.
gcov-tool.c avoids build errors from ftwbuf differences on HP, apply if you hit
errors but may need tidying up.
ia64.md is the patch for long calls, to avoid the 25 bit limit which prevents
linking gcc. It's still a work in progress as the instruction bundling is
wrong, but it does work.
Note that you must apply the binutils patch (or build the current binutils
master, or a release after 2.36) to get an assembler that will work with brl
and the HP linker. Do not apply the ia64.md patch without building a patched
gnu assembler first!
Also note that you need a working C++ compiler to bootstrap. That sounds
obvious, but is harder than you think - as far as I know, none of the
distributed g++ versions work sufficiently.
One way to get a working 4.9.2 g++ is described in my post in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64919 but there may be other
solutions as well. I've never tried to bootstrap with aCC.
My configure command is:
../gcc-11.1.0/configure --enable-comdat --disable-libgomp --with
-as=/usr/local/binutils/bin/as --enable-languages=c,c++
--prefix=/usr/local/gcc-
11.1.0 --with-gmp=/usr/local_32 --with-mpc=/usr/local_32
--with-mpfr=/usr/local_
32 --with-dwarf2
The --enable-comdat I think is required. I think libgomp doesn't build, I've
never investigated though and disable it. I use dwarf2 as recent gdb versions
won't work. The assembler I use is a patched binutils 2.36.
Good luck!
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (27 preceding siblings ...)
2021-06-09 10:12 ` jvb at cyberscience dot com
@ 2021-07-04 21:56 ` me at larbob dot org
2021-07-05 8:56 ` jvb at cyberscience dot com
` (50 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-04 21:56 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
Larkin Nickle <me at larbob dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |me at larbob dot org
--- Comment #229 from Larkin Nickle <me at larbob dot org> ---
I have not been able to reproduce a working GCC 4.7.4, 4.9.2, or 4.9.3 build
against binutils 2.36. Using HP's GCC 4.7.1 distribution, I am able to compile
4.7.4 against /opt/hp-gcc/bin/as and build a 4.9.2 or 4.9.3 against that same
as. However, building against a patched binutils 2.36 or 2.36.1 (comment #215)
results in an error when linking:
libtool: link: /home/larbob/Projects/gcc/confdirs/gcc-4.9.3-2/./gcc/xgcc
-shared-libgcc -B/home/larbob/Projects/gcc/confdirs/gcc-4.9.3-2/./gcc
-nostdinc++ -L/home/larbob/Projects/gcc/confdirs/gcc-4
.9.3-2/ia64-hp-hpux11.31/hpux64/libstdc++-v3/src
-L/home/larbob/Projects/gcc/confdirs/gcc-4.9.3-2/ia64-hp-hpux11.31/hpux64/libstdc++-v3/src/.libs
-L/home/larbob/Projects/gcc/confdirs/gcc-4.9.3-2/ia
64-hp-hpux11.31/hpux64/libstdc++-v3/libsupc++/.libs
-B/usr/util/gcc-4.9.3/ia64-hp-hpux11.31/bin/
-B/usr/util/gcc-4.9.3/ia64-hp-hpux11.31/lib/ -isystem
/usr/util/gcc-4.9.3/ia64-hp-hpux11.31/include
-isystem /usr/util/gcc-4.9.3/ia64-hp-hpux11.31/sys-include -mlp64 -shared
-nostdlib -fPIC -Wl,+h -Wl,libstdc++.so.6 -Wl,+nodefaultrpath -o
.libs/libstdc++.so.6.20 .libs/compatibility.o .libs/com
patibility-debug_list.o .libs/compatibility-debug_list-2.o
.libs/compatibility-c++0x.o .libs/compatibility-atomic-c++0x.o
.libs/compatibility-thread-c++0x.o .libs/compatibility-chrono.o .libs/compa
tibility-condvar.o
.libs/libstdc++.lax/libsupc++convenience.a/array_type_info.o
.libs/libstdc++.lax/libsupc++convenience.a/atexit_arm.o
.libs/libstdc++.lax/libsupc++convenience.a/atexit_thread.o
.libs/libstdc++.lax/libsupc++convenience.a/bad_alloc.o
.libs/libstdc++.lax/libsupc++convenience.a/bad_array_length.o
.libs/libstdc++.lax/libsupc++convenience.a/bad_array_new.o
.libs/libstdc++.lax/l
ibsupc++convenience.a/bad_cast.o
.libs/libstdc++.lax/libsupc++convenience.a/bad_typeid.o
.libs/libstdc++.lax/libsupc++convenience.a/class_type_info.o
.libs/libstdc++.lax/libsupc++convenience.a/del_
op.o .libs/libstdc++.lax/libsupc++convenience.a/del_opnt.o
.libs/libstdc++.lax/libsupc++convenience.a/del_opv.o
.libs/libstdc++.lax/libsupc++convenience.a/del_opvnt.o
.libs/libstdc++.lax/libsupc++c
onvenience.a/dyncast.o .libs/libstdc++.lax/libsupc++convenience.a/eh_alloc.o
.libs/libstdc++.lax/libsupc++convenience.a/eh_arm.o
.libs/libstdc++.lax/libsupc++convenience.a/eh_aux_runtime.o .libs/li
bstdc++.lax/libsupc++convenience.a/eh_call.o
.libs/libstdc++.lax/libsupc++convenience.a/eh_catch.o
.libs/libstdc++.lax/libsupc++convenience.a/eh_exception.o
.libs/libstdc++.lax/libsupc++convenience
.a/eh_globals.o .libs/libstdc++.lax/libsupc++convenience.a/eh_personality.o
.libs/libstdc++.lax/libsupc++convenience.a/eh_ptr.o
.libs/libstdc++.lax/libsupc++convenience.a/eh_term_handler.o .libs/li
bstdc++.lax/libsupc++convenience.a/eh_terminate.o
.libs/libstdc++.lax/libsupc++convenience.a/eh_tm.o
.libs/libstdc++.lax/libsupc++convenience.a/eh_throw.o
.libs/libstdc++.lax/libsupc++convenience.a
/eh_type.o .libs/libstdc++.lax/libsupc++convenience.a/eh_unex_handler.o
.libs/libstdc++.lax/libsupc++convenience.a/enum_type_info.o
.libs/libstdc++.lax/libsupc++convenience.a/function_type_info.o .
libs/libstdc++.lax/libsupc++convenience.a/fundamental_type_info.o
.libs/libstdc++.lax/libsupc++convenience.a/guard.o
.libs/libstdc++.lax/libsupc++convenience.a/guard_error.o
.libs/libstdc++.lax/libsupc++convenience.a/hash_bytes.o
.libs/libstdc++.lax/libsupc++convenience.a/nested_exception.o
.libs/libstdc++.lax/libsupc++convenience.a/new_handler.o
.libs/libstdc++.lax/libsupc++convenience.a/n$w_op.o
.libs/libstdc++.lax/libsupc++convenience.a/new_opnt.o
.libs/libstdc++.lax/libsupc++convenience.a/new_opv.o
.libs/libstdc++.lax/libsupc++convenience.a/new_opvnt.o
.libs/libstdc++.lax/libsupc$+convenience.a/pbase_type_info.o
.libs/libstdc++.lax/libsupc++convenience.a/pmem_type_info.o
.libs/libstdc++.lax/libsupc++convenience.a/pointer_type_info.o
.libs/libstdc++.lax/libsupc++convenience$a/pure.o
.libs/libstdc++.lax/libsupc++convenience.a/si_class_type_info.o
.libs/libstdc++.lax/libsupc++convenience.a/tinfo.o
.libs/libstdc++.lax/libsupc++convenience.a/tinfo2.o
.libs/libstdc++.lax/$ibsupc++convenience.a/vec.o
.libs/libstdc++.lax/libsupc++convenience.a/vmi_class_type_info.o
.libs/libstdc++.lax/libsupc++convenience.a/vterminate.o
.libs/libstdc++.lax/libsupc++convenience.a/cp-d$mangle.o
.libs/libstdc++.lax/libc++98convenience.a/bitmap_allocator.o
.libs/libstdc++.lax/libc++98convenience.a/pool_allocator.o
.libs/libstdc++.lax/libc++98convenience.a/mt_allocator.o
.libs/lib$tdc++.lax/libc++98convenience.a/codecvt.o
.libs/libstdc++.lax/libc++98convenience.a/complex_io.o
.libs/libstdc++.lax/libc++98convenience.a/ctype.o
.libs/libstdc++.lax/libc++98convenience.a/globals$io.o
.libs/libstdc++.lax/libc++98convenience.a/hash_tr1.o
.libs/libstdc++.lax/libc++98convenience.a/hashtable_tr1.o
.libs/libstdc++.lax/libc++98convenience.a/ios.o
.libs/libstdc++.lax/libc++98conv$nience.a/ios_failure.o
.libs/libstdc++.lax/libc++98convenience.a/ios_init.o
.libs/libstdc++.lax/libc++98convenience.a/ios_locale.o
.libs/libstdc++.lax/libc++98convenience.a/list.o
.libs/libstdc++.$ax/libc++98convenience.a/list-aux.o
.libs/libstdc++.lax/libc++98convenience.a/list-aux-2.o
.libs/libstdc++.lax/libc++98convenience.a/list_associated.o
.libs/libstdc++.lax/libc++98convenience.a/lis$_associated-2.o
.libs/libstdc++.lax/libc++98convenience.a/locale.o
.libs/libstdc++.lax/libc++98convenience.a/locale_init.o
.libs/libstdc++.lax/libc++98convenience.a/locale_facets.o
.libs/libstdc++$lax/libc++98convenience.a/localename.o
.libs/libstdc++.lax/libc++98convenience.a/math_stubs_float.o
.libs/libstdc++.lax/libc++98convenience.a/math_stubs_long_double.o
.libs/libstdc++.lax/libc++98c$nvenience.a/stdexcept.o
.libs/libstdc++.lax/libc++98convenience.a/strstream.o
.libs/libstdc++.lax/libc++98convenience.a/tree.o
.libs/libstdc++.lax/libc++98convenience.a/istream.o
.libs/libstdc++.l$x/libc++98convenience.a/streambuf.o
.libs/libstdc++.lax/libc++98convenience.a/valarray.o
.libs/libstdc++.lax/libc++98convenience.a/atomicity.o
.libs/libstdc++.lax/libc++98convenience.a/codecvt_mem$ers.o
.libs/libstdc++.lax/libc++98convenience.a/collate_members.o
.libs/libstdc++.lax/libc++98convenience.a/ctype_configure_char.o
.libs/libstdc++.lax/libc++98convenience.a/ctype_members.o
.libs/l$bstdc++.lax/libc++98convenience.a/messages_members.o
.libs/libstdc++.lax/libc++98convenience.a/monetary_members.o
.libs/libstdc++.lax/libc++98convenience.a/numeric_members.o
.libs/libstdc++.lax/li$c++98convenience.a/time_members.o
.libs/libstdc++.lax/libc++98convenience.a/basic_file.o
.libs/libstdc++.lax/libc++98convenience.a/c++locale.o
.libs/libstdc++.lax/libc++98convenience.a/allocator-i$st.o
.libs/libstdc++.lax/libc++98convenience.a/concept-inst.o
.libs/libstdc++.lax/libc++98convenience.a/ext-inst.o
.libs/libstdc++.lax/libc++98convenience.a/ios-inst.o
.libs/libstdc++.lax/libc++98$onvenience.a/iostream-inst.o
.libs/libstdc++.lax/libc++98convenience.a/istream-inst.o
.libs/libstdc++.lax/libc++98convenience.a/locale-inst.o
.libs/libstdc++.lax/libc++98convenience.a/misc-inst.o
$libs/libstdc++.lax/libc++98convenience.a/ostream-inst.o
.libs/libstdc++.lax/libc++98convenience.a/sstream-inst.o
.libs/libstdc++.lax/libc++98convenience.a/streambuf-inst.o
.libs/libstdc++.lax/libc$+98convenience.a/wlocale-inst.o
.libs/libstdc++.lax/libc++98convenience.a/parallel_settings.o
.libs/libstdc++.lax/libc++11convenience.a/chrono.o
.libs/libstdc++.lax/libc++11convenience.a/conditio$_variable.o
.libs/libstdc++.lax/libc++11convenience.a/debug.o
.libs/libstdc++.lax/libc++11convenience.a/functexcept.o
.libs/libstdc++.lax/libc++11convenience.a/functional.o
.libs/libstdc++.lax/lib$++11convenience.a/future.o
.libs/libstdc++.lax/libc++11convenience.a/hash_c++0x.o
.libs/libstdc++.lax/libc++11convenience.a/hashtable_c++0x.o
.libs/libstdc++.lax/libc++11convenience.a/limits.o
.li$s/libstdc++.lax/libc++11convenience.a/mutex.o
.libs/libstdc++.lax/libc++11convenience.a/placeholders.o
.libs/libstdc++.lax/libc++11convenience.a/random.o
.libs/libstdc++.lax/libc++11convenience.a/$egex.o
.libs/libstdc++.lax/libc++11convenience.a/shared_ptr.o
.libs/libstdc++.lax/libc++11convenience.a/snprintf_lite.o
.libs/libstdc++.lax/libc++11convenience.a/system_error.o
.libs/libstdc++.lax$libc++11convenience.a/thread.o
.libs/libstdc++.lax/libc++11convenience.a/fstream-inst.o
.libs/libstdc++.lax/libc++11convenience.a/string-inst.o
.libs/libstdc++.lax/libc++11convenience.a/wstring-in$t.o
-L/home/larbob/Projects/gcc/confdirs/gcc-4.9.3-2/ia64-hp-hpux11.31/hpux64/libstdc++-v3/libsupc++/.libs
-L/home/larbob/Projects/gcc/confdirs/gcc-4.9.3-2/ia64-hp-hpux11.31/hpux64/libstdc++-v3/$rc
-L/home/larbob/Projects/gcc/confdirs/gcc-4.9.3-2/ia64-hp-hpux11.31/hpux64/libstdc++-v3/src/.libs
-lm -L/home/larbob/Projects/gcc/confdirs/gcc-4.9.3-2/./gcc/hpux64
-L/usr/ccs/lib/hpux64 -L/lib/h$ux64 -L/usr/lib/hpux64
-L/home/larbob/Projects/gcc/confdirs/gcc-4.9.3-2/./gcc -L/usr/ccs/lib -lgcc_s
-lunwind -mlp64 -mlp64
collect2: error: ld terminated with signal 11 [Segmentation fault], core dumped
make[10]: *** [Makefile:553: libstdc++.la] Error 1
My linker version is as follows:
ld: 92453-07 linker ld HP Itanium(R) B.12.61 IPF/IPF
My config line is as follows:
$ ../../sources/gcc-4.9.3/configure --disable-libgomp --with-as=/usr/util/binu
tils-2.36/bin/as --enable-languages=c,c++ --prefix=/usr/util/gcc-4.9.3
--disable
-nls
This does not happen if I pass --with-as=/opt/hp-gcc/bin/as instead.
I have added #undef MAKE_DECL_ONE_ONLY in gcc/config/ia64/hpux.h in 4.7.4,
4.9.2, and 4.9.3 as specified in the thread that has been linked on getting a
working 4.9.2 up.
Furthermore, building 11.1.0 with 4.9.2/4.9.3 with HP GCC 4.7.1's as gives me:
In file included from ../../../../sources/gcc-11.1.0/mpfr/src/mpfr-impl.h:88:0,
from ../../../../sources/gcc-11.1.0/mpfr/src/clear.c:23:
../../../../sources/gcc-11.1.0/mpfr/src/clear.c: In function 'mpfr_clear':
/home/larbob/Projects/gcc/confdirs/gcc-11.1.0-1/./gmp/gmp.h:481:33: internal
compiler error: in plus_constant, at explow.c:87
#define mp_get_memory_functions __gmp_get_memory_functions
^
../../../../sources/gcc-11.1.0/mpfr/src/mpfr-gmp.h:267:13: note: in expansion
of macro 'mp_get_memory_functions'
(mp_get_memory_functions(&mpfr_allocate_func, \
^
../../../../sources/gcc-11.1.0/mpfr/src/mpfr-gmp.h:272:32: note: in expansion
of macro 'MPFR_GET_MEMFUNC'
#define __gmp_free_func (MPFR_GET_MEMFUNC, mpfr_free_func)
^
../../../../sources/gcc-11.1.0/mpfr/src/clear.c:28:5: note: in expansion of
macro '__gmp_free_func'
(*__gmp_free_func) (MPFR_GET_REAL_PTR (m),
So, has anyone else been able to reproduce a 11.1 build? And if so, what gmp,
mpfr, and mpc version did you use, how were they configured, etc.?
Thanks.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (28 preceding siblings ...)
2021-07-04 21:56 ` me at larbob dot org
@ 2021-07-05 8:56 ` jvb at cyberscience dot com
2021-07-14 2:51 ` bugzilla-gcc at thewrittenword dot com
` (49 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-07-05 8:56 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #230 from John Buddery <jvb at cyberscience dot com> ---
The mpfr issue seems to be an issue with gcc 4.9.2 compiling later mpfr
versions.
It builds with 4.7.2, so as a workaround try building mpfr outside the gcc tree
using 4.7.2. This may mean you need to build gmp and mpc outside the tree as
well.
I don't know about the ld crash - see if it occurs when building 11.1 after you
get past the mpfr issue.
If it does, that binutils patch will probably work with older binutils
versions, so you might be able to find one compatible with your ld. I don't
think it's the patch itself, as that only affects brl instructions which gcc
won't be generating until the 11.1 patch.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (29 preceding siblings ...)
2021-07-05 8:56 ` jvb at cyberscience dot com
@ 2021-07-14 2:51 ` bugzilla-gcc at thewrittenword dot com
2021-07-14 8:35 ` jvb at cyberscience dot com
` (48 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-14 2:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #231 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to John Buddery from comment #228)
> These patches are for 11.1.0, but should work on earlier versions too. With
> this I have a working gcc which I've tested on several large projects.
You don't #undef MAKE_DECL_ONE_ONLY in gcc/config/ia64/hpux.h? If you skip it,
do you skip it on earlier GCC builds as well?
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (30 preceding siblings ...)
2021-07-14 2:51 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-14 8:35 ` jvb at cyberscience dot com
2021-07-14 15:43 ` jvb at cyberscience dot com
` (47 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-07-14 8:35 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #232 from John Buddery <jvb at cyberscience dot com> ---
The #undef MAKE_DECL_ONE_ONLY is only for older builds, it's not needed with
the gcc 11 patches.
It was an alternative single line fix which works for 4.7.2 and 4.9.4, which
you need to build if you're starting from scratch.
This was never really the right fix, and as support for systems without
MAKE_DECL_ONE_ONLY has deteriorated in later versions it became harder and
harder to follow this route. I did get some intermediate versions working with
a lot of hacking, but for any vaguely recent release I would recommend using
the 11.1 patches instead.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (31 preceding siblings ...)
2021-07-14 8:35 ` jvb at cyberscience dot com
@ 2021-07-14 15:43 ` jvb at cyberscience dot com
2021-07-14 16:10 ` bugzilla-gcc at thewrittenword dot com
` (46 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-07-14 15:43 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #233 from John Buddery <jvb at cyberscience dot com> ---
One additional note - when building the patched binutils 2.36, it must be built
as 64 bit executables.
It seems that a 32 bit gas does not produce 64 bit object files properly on
this platform, causing the linker to crash when making the 64 bit libstdc++.so.
Build binutils as 64 bit, by using a configure something like:
CFLAGS="-O2 -mlp64" ./configure -prefix=/usr/local
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (32 preceding siblings ...)
2021-07-14 15:43 ` jvb at cyberscience dot com
@ 2021-07-14 16:10 ` bugzilla-gcc at thewrittenword dot com
2021-07-14 16:13 ` jvb at cyberscience dot com
` (45 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-14 16:10 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #234 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to John Buddery from comment #233)
> One additional note - when building the patched binutils 2.36, it must be
> built as 64 bit executables.
>
> It seems that a 32 bit gas does not produce 64 bit object files properly on
> this platform, causing the linker to crash when making the 64 bit
> libstdc++.so.
>
> Build binutils as 64 bit, by using a configure something like:
>
> CFLAGS="-O2 -mlp64" ./configure -prefix=/usr/local
Odd. We currently have a build of 11.1.0 going with as from binutils-2.30 built
using the HP C compiler and:
$ file ./.o/prev-ia64-hp-hpux11.31/libstdc++-v3/src/.libs/libstdc++.so
./.o/prev-ia64-hp-hpux11.31/hpux64/libstdc++-v3/src/.libs/libstdc++.so
./.o/prev-ia64-hp-hpux11.31/libstdc++-v3/src/.libs/libstdc++.so: ELF-32
shared object file - IA64
./.o/prev-ia64-hp-hpux11.31/hpux64/libstdc++-v3/src/.libs/libstdc++.so: ELF-64
shared object file - IA64
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (33 preceding siblings ...)
2021-07-14 16:10 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-14 16:13 ` jvb at cyberscience dot com
2021-07-14 16:37 ` bugzilla-gcc at thewrittenword dot com
` (44 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-07-14 16:13 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #235 from John Buddery <jvb at cyberscience dot com> ---
Interesting - that's with a 32 bit gas ?
It does look like you have got past the point in stage1 where ld was crashing.
It could be a change between 2.30 and 2.36 I guess, I might see if I can narrow
it down.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (34 preceding siblings ...)
2021-07-14 16:13 ` jvb at cyberscience dot com
@ 2021-07-14 16:37 ` bugzilla-gcc at thewrittenword dot com
2021-07-15 12:09 ` bugzilla-gcc at thewrittenword dot com
` (43 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-14 16:37 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #236 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to John Buddery from comment #235)
> Interesting - that's with a 32 bit gas?
$ file bin/gcc111/ia64-hp-hpux11.31/bin/as
bin/gcc111/ia64-hp-hpux11.31/bin/as: ELF-32 executable object file - IA64
$% bin/gcc111/ia64-hp-hpux11.31/bin/as --version
GNU assembler (GNU Binutils) 2.30
Copyright (C) 2018 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or later.
This program has absolutely no warranty.
This assembler was configured for a target of `ia64-hp-hpux11.31'.
> It could be a change between 2.30 and 2.36 I guess, I might see if I can
> narrow it down.
We prefer to build with HP C and only use GCC when we must. 2.36 didn't build
as easily out-of-the-box with HP C and we haven't tried to fix it so we've
stuck with 2.30 for newer GCC releases.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (35 preceding siblings ...)
2021-07-14 16:37 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-15 12:09 ` bugzilla-gcc at thewrittenword dot com
2021-07-15 14:22 ` jvb at cyberscience dot com
` (42 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-15 12:09 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #237 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to John Buddery from comment #228)
> gcov-tool.c avoids build errors from ftwbuf differences on HP, apply if you
> hit errors but may need tidying up.
Instead of this patch, try the patch for PR66319 instead.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (36 preceding siblings ...)
2021-07-15 12:09 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-15 14:22 ` jvb at cyberscience dot com
2021-07-15 14:39 ` bugzilla-gcc at thewrittenword dot com
` (41 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-07-15 14:22 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #238 from John Buddery <jvb at cyberscience dot com> ---
Thanks, I'll give it a go.
It seems binutils 2.32 and earlier works fine in 32 bit mode, but 2.33.1 and
later require a 64 bit build for 64 bit objects to work reliably.
Was your 11.1 build successful ?
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (37 preceding siblings ...)
2021-07-15 14:22 ` jvb at cyberscience dot com
@ 2021-07-15 14:39 ` bugzilla-gcc at thewrittenword dot com
2021-07-15 14:58 ` jvb at cyberscience dot com
` (40 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-15 14:39 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #239 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to John Buddery from comment #238)
> Thanks, I'll give it a go.
>
> It seems binutils 2.32 and earlier works fine in 32 bit mode, but 2.33.1 and
> later require a 64 bit build for 64 bit objects to work reliably.
>
> Was your 11.1 build successful ?
Ran out of disk space so had to restart :(
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (38 preceding siblings ...)
2021-07-15 14:39 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-15 14:58 ` jvb at cyberscience dot com
2021-07-15 15:01 ` bugzilla-gcc at thewrittenword dot com
` (39 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-07-15 14:58 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #240 from John Buddery <jvb at cyberscience dot com> ---
Yeah, it sure eats up the space.
One question about PR66319 - it's marked as resolved, so is this committed as a
patch in the trunk ?
I'm hoping that eventually there will be a way to get all the edits here
committed so that future versions will build out of the box.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (39 preceding siblings ...)
2021-07-15 14:58 ` jvb at cyberscience dot com
@ 2021-07-15 15:01 ` bugzilla-gcc at thewrittenword dot com
2021-07-15 15:24 ` dave.anglin at bell dot net
` (38 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-15 15:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #241 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to John Buddery from comment #240)
> One question about PR66319 - it's marked as resolved, so is this committed
> as a patch in the trunk ?
It's resolved for HP-UX/PA but my HP-UX/IA patch was never committed.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (40 preceding siblings ...)
2021-07-15 15:01 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-15 15:24 ` dave.anglin at bell dot net
2021-07-15 18:48 ` bugzilla-gcc at thewrittenword dot com
` (37 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2021-07-15 15:24 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #242 from dave.anglin at bell dot net ---
On 2021-07-15 11:01 a.m., bugzilla-gcc at thewrittenword dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
>
> --- Comment #241 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
> (In reply to John Buddery from comment #240)
>> One question about PR66319 - it's marked as resolved, so is this committed
>> as a patch in the trunk ?
> It's resolved for HP-UX/PA but my HP-UX/IA patch was never committed.
Patch for PR66319 needs submission to gcc-patches list with cc to ia64 and/or
hpux maintainer. Patch must be submitted
by someone with copyright assignment or DOC. See:
https://gcc.gnu.org/contribute.html
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (41 preceding siblings ...)
2021-07-15 15:24 ` dave.anglin at bell dot net
@ 2021-07-15 18:48 ` bugzilla-gcc at thewrittenword dot com
2021-07-16 11:33 ` jvb at cyberscience dot com
` (36 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-15 18:48 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #243 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to John Buddery from comment #238)
> It seems binutils 2.32 and earlier works fine in 32 bit mode, but 2.33.1 and
> later require a 64 bit build for 64 bit objects to work reliably.
I can build up to and including 2.32 with the HP C compiler. Starting with
2.33.1, they add -std=gnu99. Might be possible to fix this but I might retry
with 2.32.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (42 preceding siblings ...)
2021-07-15 18:48 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-16 11:33 ` jvb at cyberscience dot com
2021-07-16 12:48 ` bugzilla-gcc at thewrittenword dot com
` (35 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-07-16 11:33 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #244 from John Buddery <jvb at cyberscience dot com> ---
I tried a gcc 11 build with patched 2.30 binutils and it worked.
I also tried building binutils 2.36 with just /opt/aCC/bin and no gcc.
I didn't get any gnu99 errors, but it did fail because plugin-api.h couldn't
work out the endianism.
Configuring with:
CFLAGS="-O -D__BIG_ENDIAN__=1" ./configure --prefix=/u
sr/local/binutils-test --enable-obsolete
allowed gas to build, but the build then failed later on in libctf. It looks
like libtool is inserting +Maked into the command line for some reason, which
breaks things.
I don't know if this gas build would work for gcc, probably it would have the
same issues as a 32 bit gcc build. +DD64 might fix this.
Probably not worth updating though just for gcc if you have a working 2.30
build, since that works OK.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (43 preceding siblings ...)
2021-07-16 11:33 ` jvb at cyberscience dot com
@ 2021-07-16 12:48 ` bugzilla-gcc at thewrittenword dot com
2021-07-16 12:51 ` bugzilla-gcc at thewrittenword dot com
` (34 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-16 12:48 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #245 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to John Buddery from comment #238)
> Was your 11.1 build successful ?
Our rebuild of 11.1.0 completed successfully. I haven't tested it though. I am
going to try earlier GCC releases and build on 11.23/IA as well.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (44 preceding siblings ...)
2021-07-16 12:48 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-16 12:51 ` bugzilla-gcc at thewrittenword dot com
2021-07-16 13:27 ` jvb at cyberscience dot com
` (33 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-16 12:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #246 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
Created attachment 51163
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51163&action=edit
Build script and patches
Build script for zlib, gmp, mpfr, mpc, binutils 2.25.1, 2.30, 2.32, and GCC
4.4.6, 4.6.4, 4.7.4, 4.8.5, 4.9.5, and 11.1.0. Build instructions for GCC 9.4.0
and 10.3.0 included but not tested yet.
Patches for all of the above included as well.
Work-in-progress.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (45 preceding siblings ...)
2021-07-16 12:51 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-16 13:27 ` jvb at cyberscience dot com
2021-07-16 13:29 ` bugzilla-gcc at thewrittenword dot com
` (32 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-07-16 13:27 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #247 from John Buddery <jvb at cyberscience dot com> ---
Looks good, that's a lot of gcc versions!
For clarification, I assume this is using the HP aCC compiler for binutils
etc., rather than the bundled /usr/ccs/bin cc ?
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (46 preceding siblings ...)
2021-07-16 13:27 ` jvb at cyberscience dot com
@ 2021-07-16 13:29 ` bugzilla-gcc at thewrittenword dot com
2021-07-17 17:14 ` me at larbob dot org
` (31 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-16 13:29 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #248 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to John Buddery from comment #247)
> For clarification, I assume this is using the HP aCC compiler for binutils
> etc., rather than the bundled /usr/ccs/bin cc ?
Correct.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (47 preceding siblings ...)
2021-07-16 13:29 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-17 17:14 ` me at larbob dot org
2021-07-17 17:39 ` me at larbob dot org
` (30 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-17 17:14 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #249 from Larkin Nickle <me at larbob dot org> ---
I am still unable to replicate a proper 11.1 build against 2.36 gas. Here's my
process:
HP GCC 4.7.1 -> GCC 4.7.4:
../../sources/gcc-4.7.4/configure --prefix=/usr/util/toolchain/gcc-4.7.4 --w
ith-as=/opt/hp-gcc/bin/as --enable-languages=c,c++ --disable-nls
-> 4.9.2:
../../sources/gcc-4.9.2/configure --disable-libgomp --with-as=/opt/hp-gcc/bi
n/as --enable-languages=c,c++ --prefix=/usr/util/toolchain/gcc-4.9.2
--disable-n
ls
Then, I compiled binutils 2.36 (w/ -mlp64), gmp 6.2.1, mpfr 4.1.0, and mpc
1.2.1 with HP GCC 4.7.1. All GMP tests passed except for `t-printf`, all mpfr
tests passed except `tasprintf`, and all mpc tests passed. These results are
the same as John's except his `t-printf` passes with GMP.
Then, I compile GCC 11.1.0 with GCC 4.9.2:
../../sources/gcc-11.1.0/configure --prefix=/usr/util/toolchain/gcc-11.1.0 -
-enable-comdat --disable-libgomp --disable-nls
--with-as=/usr/util/toolchain/bin
utils-2.36/bin/as --with-gmp=/usr/util/toolchain/gmp-6.2.1
--with-mpfr=/usr/util
/toolchain/mpfr-4.1.0 --with-mpc=/usr/util/toolchain/mpc-1.2.1
--enable-language
s=c,c++ --with-dwarf2
First it errors out when compiling charset.c:
../../../sources/gcc-11.1.0-new/libcpp/charset.c: In function 'cset_converter
init_iconv_desc(cpp_reader*, const char*, const char*)':
../../../sources/gcc-11.1.0-new/libcpp/charset.c:695:1: internal compiler
error: in plus_constant, at explow.c:101
695 | }
| ^
libbacktrace could not find executable to open
Then, if libcpp's Makefile is patched so that charset.c is built with -O1, I
eventually run into other errors:
../../../../sources/gcc-11.1.0-new/libgcc/libgcov-interface.c: In function
'gcov_clear':
../../../../sources/gcc-11.1.0-new/libgcc/libgcov-interface.c:143:1: internal
compiler error: Illegal instruction
143 | }
| ^
libbacktrace could not find executable to open
After making that compile with -O1:
../../../sources/gcc-11.1.0/zlib/inftrees.c: In function 'inflate_table':
../../../sources/gcc-11.1.0/zlib/inftrees.c:32:19: internal compiler error:
Illegal instruction
32 | int ZLIB_INTERNAL inflate_table(type, lens, codes, table, bits, work)
| ^~~~~~~~~~~~~
libbacktrace could not find executable to open
I am only able to get a build of 11.1 with BOOT_CFLAGS="-g -O1"
BOOT_CXXFLAGS="-g -O1".
It's worth noting that I have rebuilt gmp with the -O1'd 11.1 build and it
fixed the `t-printf` test not passing. I then rebuilt mpfr and mpc against it
with 4.7.1 (4.9.2 and 11.1 can't seem to properly compile mpfr) and then tried
to build 11.1 against the new builds and still ran into the same issues.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (48 preceding siblings ...)
2021-07-17 17:14 ` me at larbob dot org
@ 2021-07-17 17:39 ` me at larbob dot org
2021-07-17 18:38 ` dave.anglin at bell dot net
` (29 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-17 17:39 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #250 from Larkin Nickle <me at larbob dot org> ---
I should probably note that my PATH is set to the standard path, appended with
the PATH to whichever GCC's bin folder as well as a folder I have with some
utilities:
awk gawk make mksh sed tar
I use mksh as my CONFIG_SHELL as the system shells don't play nicely with some
configure scripts, e.g. binutils' in my experience.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (49 preceding siblings ...)
2021-07-17 17:39 ` me at larbob dot org
@ 2021-07-17 18:38 ` dave.anglin at bell dot net
2021-07-18 2:02 ` bugzilla-gcc at thewrittenword dot com
` (28 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2021-07-17 18:38 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #251 from dave.anglin at bell dot net ---
On 2021-07-15 2:48 p.m., bugzilla-gcc at thewrittenword dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
>
> --- Comment #243 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
> (In reply to John Buddery from comment #238)
>> It seems binutils 2.32 and earlier works fine in 32 bit mode, but 2.33.1 and
>> later require a 64 bit build for 64 bit objects to work reliably.
> I can build up to and including 2.32 with the HP C compiler. Starting with
> 2.33.1, they add -std=gnu99. Might be possible to fix this but I might retry
> with 2.32.
Adding -std=gnu99 unilaterally seems like a bug.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (50 preceding siblings ...)
2021-07-17 18:38 ` dave.anglin at bell dot net
@ 2021-07-18 2:02 ` bugzilla-gcc at thewrittenword dot com
2021-07-18 12:39 ` bugzilla-gcc at thewrittenword dot com
` (27 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-18 2:02 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #252 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to Larkin Nickle from comment #249)
> Then, if libcpp's Makefile is patched so that charset.c is built with -O1, I
> eventually run into other errors:
>
> ../../../../sources/gcc-11.1.0-new/libgcc/libgcov-interface.c: In function
> 'gcov_clear':
> ../../../../sources/gcc-11.1.0-new/libgcc/libgcov-interface.c:143:1:
> internal compiler error: Illegal instruction
> 143 | }
> | ^
> libbacktrace could not find executable to open
I tried building 10.3.0 using the same patches as in 11.1.0 and ran into the
above for the 10.3.0 build.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (51 preceding siblings ...)
2021-07-18 2:02 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-18 12:39 ` bugzilla-gcc at thewrittenword dot com
2021-07-19 21:00 ` me at larbob dot org
` (26 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-18 12:39 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #253 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to The Written Word from comment #245)
> (In reply to John Buddery from comment #238)
> > Was your 11.1 build successful ?
>
> Our rebuild of 11.1.0 completed successfully. I haven't tested it though. I
> am going to try earlier GCC releases and build on 11.23/IA as well.
A build on 11.23/IA worked using similar patches to 11.31/IA.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (52 preceding siblings ...)
2021-07-18 12:39 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-19 21:00 ` me at larbob dot org
2021-07-19 22:43 ` me at larbob dot org
` (25 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-19 21:00 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #254 from Larkin Nickle <me at larbob dot org> ---
I've now tried 11.1.0 almost exactly as The Written Word builds it, and still
get:
during GIMPLE pass: dce
../../libiberty/mkstemps.c: In function 'mkstemps':
../../libiberty/mkstemps.c:80:1: internal compiler error: Illegal instruction
80 | mkstemps (char *pattern, int suffix_len)
| ^~~~~~~~
libbacktrace could not find executable to open
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
This happens against binutils 2.30 as TWW builds it, and against 2.36 or 2.37.
I also have to enable a version of gcc-11.1.0-PR64919.patch with #undef
MAKE_DECL_ONE_ONLY removed in order to build libgcov at a lower optimization
level to even get to this point. TWW gets this issue with 10.3, but not 11.1
for some reason.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (53 preceding siblings ...)
2021-07-19 21:00 ` me at larbob dot org
@ 2021-07-19 22:43 ` me at larbob dot org
2021-07-20 16:06 ` me at larbob dot org
` (24 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-19 22:43 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #255 from Larkin Nickle <me at larbob dot org> ---
Here's the log from the attempted 11.1 build against binutils 2.30. Built with
4.8.5. I'm not able to attach this as it's over the max size limit.
https://gist.githubusercontent.com/larb0b/f3a855892f7b16f4676444f2c056947e/raw/e94e0a3b54a555e6111ecef634d082d78d983ee9/gcc-11.1.0.b
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (54 preceding siblings ...)
2021-07-19 22:43 ` me at larbob dot org
@ 2021-07-20 16:06 ` me at larbob dot org
2021-07-20 16:07 ` me at larbob dot org
` (23 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-20 16:06 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #256 from Larkin Nickle <me at larbob dot org> ---
Created attachment 51179
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51179&action=edit
Configure log for gcc 11.1.0
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (55 preceding siblings ...)
2021-07-20 16:06 ` me at larbob dot org
@ 2021-07-20 16:07 ` me at larbob dot org
2021-07-20 16:08 ` me at larbob dot org
` (22 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-20 16:07 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #257 from Larkin Nickle <me at larbob dot org> ---
Created attachment 51180
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51180&action=edit
Build log for GCC 11.1 with -j1
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (56 preceding siblings ...)
2021-07-20 16:07 ` me at larbob dot org
@ 2021-07-20 16:08 ` me at larbob dot org
2021-07-20 17:04 ` dave.anglin at bell dot net
` (21 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-20 16:08 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #258 from Larkin Nickle <me at larbob dot org> ---
I've now attached the configure log as well as the build log for GCC 11.1 with
`-j1` passed to make so as to make the log more readable.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (57 preceding siblings ...)
2021-07-20 16:08 ` me at larbob dot org
@ 2021-07-20 17:04 ` dave.anglin at bell dot net
2021-07-20 17:05 ` me at larbob dot org
` (20 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2021-07-20 17:04 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #259 from dave.anglin at bell dot net ---
On 2021-07-19 5:00 p.m., me at larbob dot org wrote:
> I've now tried 11.1.0 almost exactly as The Written Word builds it, and still
> get:
>
> during GIMPLE pass: dce
> ../../libiberty/mkstemps.c: In function 'mkstemps':
> ../../libiberty/mkstemps.c:80:1: internal compiler error: Illegal instruction
> 80 | mkstemps (char *pattern, int suffix_len)
> | ^~~~~~~~
The compiler being used to compile mkstemps.c is broken. If core dumps are
enabled,
you should be able to use gdb (wdb) directly to find the illegal instruction.
If not, one can find the illegal instruction by adding "-save-temps -v" to the
compile command.
This will give the information needed to run the compilation under gdb (wdb)
If I was to guess, the illegal instruction is likely to be an out of range
branch.
I would check HP patch for HP ld. There may be version dependent differences
in weak support.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (58 preceding siblings ...)
2021-07-20 17:04 ` dave.anglin at bell dot net
@ 2021-07-20 17:05 ` me at larbob dot org
2021-07-20 17:58 ` me at larbob dot org
` (19 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-20 17:05 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #260 from Larkin Nickle <me at larbob dot org> ---
(In reply to dave.anglin from comment #259)
> The compiler being used to compile mkstemps.c is broken. If core dumps are
> enabled,
> you should be able to use gdb (wdb) directly to find the illegal instruction.
>
> If not, one can find the illegal instruction by adding "-save-temps -v" to
> the compile command.
> This will give the information needed to run the compilation under gdb (wdb)
>
> If I was to guess, the illegal instruction is likely to be an out of range
> branch.
>
> I would check HP patch for HP ld. There may be version dependent
> differences in weak support.
Indeed, I'm trying to get a working gdb up now. I have the latest ld version.
ld: 92453-07 linker ld HP Itanium(R) B.12.67 IPF/IPF
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (59 preceding siblings ...)
2021-07-20 17:05 ` me at larbob dot org
@ 2021-07-20 17:58 ` me at larbob dot org
2021-07-20 18:24 ` me at larbob dot org
` (18 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-20 17:58 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #261 from Larkin Nickle <me at larbob dot org> ---
https://gcc.gnu.org/bugzilla//show_bug.cgi?id=59447
Argh, it seems that `--with-dwarf2` basically just means use dwarf2 *or later*,
at least in GCCs this new. Will patch gcc/common.opt and rebuild.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (60 preceding siblings ...)
2021-07-20 17:58 ` me at larbob dot org
@ 2021-07-20 18:24 ` me at larbob dot org
2021-07-20 23:58 ` me at larbob dot org
` (17 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-20 18:24 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #262 from Larkin Nickle <me at larbob dot org> ---
Created attachment 51182
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51182&action=edit
GCC 11.1 patch to net dwarf2 debugging symbols
Rebuilding with this patch. Should hopefully net me actual dwarf2 debug
symbols.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (61 preceding siblings ...)
2021-07-20 18:24 ` me at larbob dot org
@ 2021-07-20 23:58 ` me at larbob dot org
2021-07-21 0:01 ` me at larbob dot org
` (16 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-20 23:58 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #263 from Larkin Nickle <me at larbob dot org> ---
I'm having trouble actually getting a GDB that can read the resulting symbols
properly.
readelf --debug-dump=info cc1 | grep -A 2 'Compilation Unit @'
Compilation Unit @ offset 0x0:
Length: 0xa390 (32-bit)
Version: 2
As shown above, using readelf, I've confirmed I am now getting DWARF2 symbols,
but I'm unable to read them with my own built GDB 7.3.1 or GDB 7.5.1 from
http://ftp.nluug.nl/os/HPUX/itrc/gcc-4.7.2-11.31.sd.bz. HP GDB 6.7 is able to
handle them somewhat:
Object file is generated with GNU compiler: GNU C++17 11.1.0 -g -O2 -fno-PIE
-fno-exceptions -fno-rtti -fasynchronous-unwind-tables
HP WDB does not support debugging of programs compiled with GNU compiler.
Some features may work, but it is not guaranteed.
HP recommends using HP aCC compiler, Refer: http://www.hp.com/go/aCC
Refer http://www.hp.com/go/wdb for the support statement
done.
Running cc1 w/ the arguments that lead to the illegal instruction error (as
verified with -v):
Program received signal SIGILL, Illegal instruction
si_code: 9 - ILL_REGNAT - Register NaT Consumption.
0x54af7f0:1 in get_ref_base_and_extent (exp=<not available>,
poffset=<not available>, psize=<not available>, pmax_size=<not available>,
preverse=<not available>) at ../../gcc/tree-dfa.c:525
525 maxsize = wi::to_poly_offset (asize) - bit_offset;
However, trying to get a backtrace with `bt` results in HP GDB core dumping:
#0 0x54af7f0:1 in get_ref_base_and_extent (exp=<not available>,
poffset=<not available>, psize=<not available>, pmax_size=<not available>,
preverse=<not available>) at ../../gcc/tree-dfa.c:525
Assertion failed: stacki == 0, file ../../../Src/gnu/gdb/dwarf2read.c, line
1579
ABORT instruction (core dumped)
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (62 preceding siblings ...)
2021-07-20 23:58 ` me at larbob dot org
@ 2021-07-21 0:01 ` me at larbob dot org
2021-07-21 2:32 ` bugzilla-gcc at thewrittenword dot com
` (15 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-21 0:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #264 from Larkin Nickle <me at larbob dot org> ---
Oh, and I should mention this is what I get with 7.3.1 or 7.5.1:
Reading symbols from
/home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/prev-gcc/cc1...BFD:
/home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/prev-gcc/cc1 symbol number
7214 references nonexistent SHT_SYMTAB_SHNDX section
Can't read symbols from
/home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/prev-gcc/cc1: File in
wrong format
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (63 preceding siblings ...)
2021-07-21 0:01 ` me at larbob dot org
@ 2021-07-21 2:32 ` bugzilla-gcc at thewrittenword dot com
2021-07-21 2:38 ` me at larbob dot org
` (14 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-21 2:32 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #265 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to Larkin Nickle from comment #264)
> Oh, and I should mention this is what I get with 7.3.1 or 7.5.1:
>
> Reading symbols from
> /home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/prev-gcc/cc1...BFD:
> /home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/prev-gcc/cc1 symbol
> number 7214 references nonexistent SHT_SYMTAB_SHNDX section
> Can't read symbols from
> /home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/prev-gcc/cc1: File in
> wrong format
There's a GDB 7.9.1 at http://hpux.connect.org.uk/hppd/hpux/Gnu/gdb-7.9.1/.
Does it work better?
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (64 preceding siblings ...)
2021-07-21 2:32 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-21 2:38 ` me at larbob dot org
2021-07-21 2:59 ` bugzilla-gcc at thewrittenword dot com
` (13 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-21 2:38 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #266 from Larkin Nickle <me at larbob dot org> ---
I'll try that 7.9.1 as a last resort; I noticed that 7.3.1 was able to read
dwarf4 symbols from a previous 4.9.2 build I did so I'm testing building 11.1
patched to produce debug symbols similarly.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (65 preceding siblings ...)
2021-07-21 2:38 ` me at larbob dot org
@ 2021-07-21 2:59 ` bugzilla-gcc at thewrittenword dot com
2021-07-21 4:36 ` bugzilla-gcc at thewrittenword dot com
` (12 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-21 2:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #267 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to Larkin Nickle from comment #266)
> I'll try that 7.9.1 as a last resort; I noticed that 7.3.1 was able to read
> dwarf4 symbols from a previous 4.9.2 build I did so I'm testing building
> 11.1 patched to produce debug symbols similarly.
7.9.1 was the last version that had support for HP-UX.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (66 preceding siblings ...)
2021-07-21 2:59 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-21 4:36 ` bugzilla-gcc at thewrittenword dot com
2021-07-21 5:13 ` me at larbob dot org
` (11 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: bugzilla-gcc at thewrittenword dot com @ 2021-07-21 4:36 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #268 from The Written Word <bugzilla-gcc at thewrittenword dot com> ---
(In reply to Larkin Nickle from comment #262)
> Created attachment 51182 [details]
> GCC 11.1 patch to net dwarf2 debugging symbols
>
> Rebuilding with this patch. Should hopefully net me actual dwarf2 debug
> symbols.
What if you use the GCC --gdwarf-2 option instead of this patch? Does the patch
just set the default DWARF version? Seems like if GCC supports DWARF >2,
--gdwarf-2 should generate just v2 DWARF info.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (67 preceding siblings ...)
2021-07-21 4:36 ` bugzilla-gcc at thewrittenword dot com
@ 2021-07-21 5:13 ` me at larbob dot org
2021-07-21 6:32 ` me at larbob dot org
` (10 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-21 5:13 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #269 from Larkin Nickle <me at larbob dot org> ---
(In reply to The Written Word from comment #268)
> (In reply to Larkin Nickle from comment #262)
> > Created attachment 51182 [details]
> > GCC 11.1 patch to net dwarf2 debugging symbols
> >
> > Rebuilding with this patch. Should hopefully net me actual dwarf2 debug
> > symbols.
>
> What if you use the GCC --gdwarf-2 option instead of this patch? Does the
> patch just set the default DWARF version? Seems like if GCC supports DWARF
> >2, --gdwarf-2 should generate just v2 DWARF info.
Yes, I think that should work fine too.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (68 preceding siblings ...)
2021-07-21 5:13 ` me at larbob dot org
@ 2021-07-21 6:32 ` me at larbob dot org
2021-07-21 15:15 ` dave.anglin at bell dot net
` (9 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-21 6:32 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #270 from Larkin Nickle <me at larbob dot org> ---
Reading symbols from
/home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/./prev-gcc/cc1...BFD:
/home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/prev-gcc/cc1 symbol number
7215 references nonexistent SHT_SYMTAB_SHNDX section
Can't read symbols from
/home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/prev-gcc/cc1: File in
wrong format
No dice with 7.9.1 either. I've now tried both dwarf2 and dwarf4 to no avail,
and have verified that gdb is able to read, for example, dwarf4 symbols from a
previous gcc 4.9.2 build that I did.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (69 preceding siblings ...)
2021-07-21 6:32 ` me at larbob dot org
@ 2021-07-21 15:15 ` dave.anglin at bell dot net
2021-07-21 16:19 ` me at larbob dot org
` (8 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2021-07-21 15:15 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #271 from dave.anglin at bell dot net ---
On 2021-07-21 2:32 a.m., me at larbob dot org wrote:
> Reading symbols from
> /home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/./prev-gcc/cc1...BFD:
> /home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/prev-gcc/cc1 symbol number
> 7215 references nonexistent SHT_SYMTAB_SHNDX section
> Can't read symbols from
> /home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/prev-gcc/cc1: File in
> wrong format
This seems to be a problem with the symbol table in cc1. It's not a problem
with the dwarf info.
Can readelf read symbols? What does file command show? If you strip cc1, does
gdb start?
disasm $pc-16,$pc+16 should show faulting instruction.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (70 preceding siblings ...)
2021-07-21 15:15 ` dave.anglin at bell dot net
@ 2021-07-21 16:19 ` me at larbob dot org
2021-07-21 16:43 ` jvb at cyberscience dot com
` (7 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-21 16:19 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #272 from Larkin Nickle <me at larbob dot org> ---
(In reply to dave.anglin from comment #271)
> On 2021-07-21 2:32 a.m., me at larbob dot org wrote:
> > Reading symbols from
> > /home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/./prev-gcc/cc1...BFD:
> > /home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/prev-gcc/cc1 symbol number
> > 7215 references nonexistent SHT_SYMTAB_SHNDX section
> > Can't read symbols from
> > /home/larbob/Projects/build-gcc/builds/gcc-11.1.0/.o/prev-gcc/cc1: File in
> > wrong format
> This seems to be a problem with the symbol table in cc1. It's not a problem
> with the dwarf info.
>
> Can readelf read symbols? What does file command show? If you strip cc1,
> does gdb start?
On system with a modern `file`:
cc1: ELF 32-bit MSB executable, IA-64, version 1 (HP-UX), dynamically linked,
interpreter /usr/lib/hpux32/uld.so:/usr/lib/hpux32/dld.so, with debug_info, not
stripped, too many notes (256)
Readelf is seemingly able to read them.
>
> disasm $pc-16,$pc+16 should show faulting instruction.
(gdb) disas $pc-16,$pc+16
Dump of assembler code from 0x54af7e1 to 0x54af801:
0x00000000054af7e1: st8 [r41]=r0
0x00000000054af7e2: nop.i 0x0;;
0x00000000054af7f0: [MMI] ld1.a r87=[r14]
=> 0x00000000054af7f1: st8 [r47]=r59
0x00000000054af7f2: nop.i 0x0
0x00000000054af800: [MMI] st4 [r46]=r0;;
End of assembler dump.
This issue happens in stage3.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (71 preceding siblings ...)
2021-07-21 16:19 ` me at larbob dot org
@ 2021-07-21 16:43 ` jvb at cyberscience dot com
2021-07-21 16:55 ` me at larbob dot org
` (6 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: jvb at cyberscience dot com @ 2021-07-21 16:43 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #273 from John Buddery <jvb at cyberscience dot com> ---
If you go back a bit further, is there a speculative load of one of those
registers
(probably r47 / r59 ) ?
A speculative load will have a .s I think.
I believe ILL_REGNAT should actually be a SEGV, not SIGILL - not sure why
that's the signal being generated.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (72 preceding siblings ...)
2021-07-21 16:43 ` jvb at cyberscience dot com
@ 2021-07-21 16:55 ` me at larbob dot org
2021-07-21 17:26 ` dave.anglin at bell dot net
` (5 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-21 16:55 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #274 from Larkin Nickle <me at larbob dot org> ---
Created attachment 51190
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51190&action=edit
disas of cc1 with more context
Here's `disas $pc-256,$pc+256`'s output.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (73 preceding siblings ...)
2021-07-21 16:55 ` me at larbob dot org
@ 2021-07-21 17:26 ` dave.anglin at bell dot net
2021-07-27 22:09 ` me at larbob dot org
` (4 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: dave.anglin at bell dot net @ 2021-07-21 17:26 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #275 from dave.anglin at bell dot net ---
On 2021-07-21 12:55 p.m., me at larbob dot org wrote:
> Here's `disas $pc-256,$pc+256`'s output.
Maybe r47 contains garbage.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [4.9.0 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (74 preceding siblings ...)
2021-07-21 17:26 ` dave.anglin at bell dot net
@ 2021-07-27 22:09 ` me at larbob dot org
2021-11-16 13:01 ` [Bug middle-end/61577] [9/10/11/12 " rguenth at gcc dot gnu.org
` (3 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: me at larbob dot org @ 2021-07-27 22:09 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #276 from Larkin Nickle <me at larbob dot org> ---
Created attachment 51215
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51215&action=edit
How I'm attempting to build GCC 11.1
For what it's worth, here's exactly how I'm attempting to build 11.1. This is
based on The Written Word's script from comment #246.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [9/10/11/12 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (75 preceding siblings ...)
2021-07-27 22:09 ` me at larbob dot org
@ 2021-11-16 13:01 ` rguenth at gcc dot gnu.org
2022-05-27 9:35 ` [Bug middle-end/61577] [10/11/12/13 " rguenth at gcc dot gnu.org
` (2 subsequent siblings)
79 siblings, 0 replies; 80+ messages in thread
From: rguenth at gcc dot gnu.org @ 2021-11-16 13:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Summary|[4.9.0 Regression] can't |[9/10/11/12 Regression]
|compile on hp-ux v3 ia64 |can't compile on hp-ux v3
| |ia64
Target Milestone|--- |9.5
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [10/11/12/13 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (76 preceding siblings ...)
2021-11-16 13:01 ` [Bug middle-end/61577] [9/10/11/12 " rguenth at gcc dot gnu.org
@ 2022-05-27 9:35 ` rguenth at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug middle-end/61577] [11/12/13/14 " rguenth at gcc dot gnu.org
79 siblings, 0 replies; 80+ messages in thread
From: rguenth at gcc dot gnu.org @ 2022-05-27 9:35 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|9.5 |10.4
--- Comment #277 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 9 branch is being closed
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [10/11/12/13 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (77 preceding siblings ...)
2022-05-27 9:35 ` [Bug middle-end/61577] [10/11/12/13 " rguenth at gcc dot gnu.org
@ 2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug middle-end/61577] [11/12/13/14 " rguenth at gcc dot gnu.org
79 siblings, 0 replies; 80+ messages in thread
From: jakub at gcc dot gnu.org @ 2022-06-28 10:31 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|10.4 |10.5
--- Comment #278 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
GCC 10.4 is being released, retargeting bugs to GCC 10.5.
^ permalink raw reply [flat|nested] 80+ messages in thread
* [Bug middle-end/61577] [11/12/13/14 Regression] can't compile on hp-ux v3 ia64
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
` (78 preceding siblings ...)
2022-06-28 10:31 ` jakub at gcc dot gnu.org
@ 2023-07-07 10:30 ` rguenth at gcc dot gnu.org
79 siblings, 0 replies; 80+ messages in thread
From: rguenth at gcc dot gnu.org @ 2023-07-07 10:30 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|10.5 |11.5
--- Comment #279 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 10 branch is being closed.
^ permalink raw reply [flat|nested] 80+ messages in thread
end of thread, other threads:[~2023-07-07 10:30 UTC | newest]
Thread overview: 80+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-61577-4@http.gcc.gnu.org/bugzilla/>
2014-06-21 11:01 ` [Bug c++/61577] [4.9.0] can't compile on hp-ux v3 ia64 FBergemann at web dot de
2015-10-15 11:04 ` [Bug target/61577] " josephpattara at gmail dot com
2015-10-19 11:34 ` josephpattara at gmail dot com
2019-07-05 1:51 ` dave.anglin at bell dot net
2020-02-25 14:55 ` [Bug middle-end/61577] [4.9.0 Regression] " peter.bisroev at groundlabs dot com
2020-04-18 1:11 ` dave.anglin at bell dot net
2020-04-23 15:48 ` peter.bisroev at groundlabs dot com
2020-04-23 16:50 ` dave.anglin at bell dot net
2020-05-02 4:14 ` peter.bisroev at groundlabs dot com
2020-05-02 14:30 ` dave.anglin at bell dot net
2020-05-13 18:03 ` jared.martinsen at fiserv dot com
2020-05-13 19:04 ` dave.anglin at bell dot net
2021-04-16 21:30 ` pinskia at gcc dot gnu.org
2021-04-24 22:21 ` peter at int19h dot net
2021-05-17 9:56 ` jvb at cyberscience dot com
2021-05-19 16:23 ` dave.anglin at bell dot net
2021-05-20 9:19 ` jvb at cyberscience dot com
2021-05-20 13:25 ` dave.anglin at bell dot net
2021-05-20 13:37 ` jvb at cyberscience dot com
2021-05-20 14:02 ` dave.anglin at bell dot net
2021-05-20 14:59 ` jvb at cyberscience dot com
2021-05-20 15:03 ` dave.anglin at bell dot net
2021-05-20 15:16 ` dave.anglin at bell dot net
2021-05-20 17:00 ` dave.anglin at bell dot net
2021-05-20 17:22 ` jvb at cyberscience dot com
2021-06-03 17:19 ` dave.anglin at bell dot net
2021-06-09 9:51 ` jvb at cyberscience dot com
2021-06-09 10:12 ` jvb at cyberscience dot com
2021-07-04 21:56 ` me at larbob dot org
2021-07-05 8:56 ` jvb at cyberscience dot com
2021-07-14 2:51 ` bugzilla-gcc at thewrittenword dot com
2021-07-14 8:35 ` jvb at cyberscience dot com
2021-07-14 15:43 ` jvb at cyberscience dot com
2021-07-14 16:10 ` bugzilla-gcc at thewrittenword dot com
2021-07-14 16:13 ` jvb at cyberscience dot com
2021-07-14 16:37 ` bugzilla-gcc at thewrittenword dot com
2021-07-15 12:09 ` bugzilla-gcc at thewrittenword dot com
2021-07-15 14:22 ` jvb at cyberscience dot com
2021-07-15 14:39 ` bugzilla-gcc at thewrittenword dot com
2021-07-15 14:58 ` jvb at cyberscience dot com
2021-07-15 15:01 ` bugzilla-gcc at thewrittenword dot com
2021-07-15 15:24 ` dave.anglin at bell dot net
2021-07-15 18:48 ` bugzilla-gcc at thewrittenword dot com
2021-07-16 11:33 ` jvb at cyberscience dot com
2021-07-16 12:48 ` bugzilla-gcc at thewrittenword dot com
2021-07-16 12:51 ` bugzilla-gcc at thewrittenword dot com
2021-07-16 13:27 ` jvb at cyberscience dot com
2021-07-16 13:29 ` bugzilla-gcc at thewrittenword dot com
2021-07-17 17:14 ` me at larbob dot org
2021-07-17 17:39 ` me at larbob dot org
2021-07-17 18:38 ` dave.anglin at bell dot net
2021-07-18 2:02 ` bugzilla-gcc at thewrittenword dot com
2021-07-18 12:39 ` bugzilla-gcc at thewrittenword dot com
2021-07-19 21:00 ` me at larbob dot org
2021-07-19 22:43 ` me at larbob dot org
2021-07-20 16:06 ` me at larbob dot org
2021-07-20 16:07 ` me at larbob dot org
2021-07-20 16:08 ` me at larbob dot org
2021-07-20 17:04 ` dave.anglin at bell dot net
2021-07-20 17:05 ` me at larbob dot org
2021-07-20 17:58 ` me at larbob dot org
2021-07-20 18:24 ` me at larbob dot org
2021-07-20 23:58 ` me at larbob dot org
2021-07-21 0:01 ` me at larbob dot org
2021-07-21 2:32 ` bugzilla-gcc at thewrittenword dot com
2021-07-21 2:38 ` me at larbob dot org
2021-07-21 2:59 ` bugzilla-gcc at thewrittenword dot com
2021-07-21 4:36 ` bugzilla-gcc at thewrittenword dot com
2021-07-21 5:13 ` me at larbob dot org
2021-07-21 6:32 ` me at larbob dot org
2021-07-21 15:15 ` dave.anglin at bell dot net
2021-07-21 16:19 ` me at larbob dot org
2021-07-21 16:43 ` jvb at cyberscience dot com
2021-07-21 16:55 ` me at larbob dot org
2021-07-21 17:26 ` dave.anglin at bell dot net
2021-07-27 22:09 ` me at larbob dot org
2021-11-16 13:01 ` [Bug middle-end/61577] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-05-27 9:35 ` [Bug middle-end/61577] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug middle-end/61577] [11/12/13/14 " rguenth 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).