public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug bootstrap/67733] New: elfdump and readelf in perl scripts should to use env vars ELFDUMP and READELF
@ 2015-09-27 16:11 ikozhukhov at gmail dot com
2015-09-27 16:14 ` [Bug target/67733] " pinskia at gcc dot gnu.org
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: ikozhukhov at gmail dot com @ 2015-09-27 16:11 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67733
Bug ID: 67733
Summary: elfdump and readelf in perl scripts should to use env
vars ELFDUMP and READELF
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: ikozhukhov at gmail dot com
Target Milestone: ---
with bootstrap on illumos based platform we can use /usr/bin/elfdump and
/use/bin/readelf or /usr/gnu/bin/elfdump & /usr/gnu/bin/readelf, but in scripts
:
contrib/make_sunver.pl
libstdc++-v3/scripts/extract_symvers.pl
i can see:
/usr/ccs/bin/elfdump
but it is mistake, because with removal of old unused links at /usr/ccs/bin/*
on illumos based platform (DilOS, http://www,dilos.org) gcc bootstrap will be
failed.
we try to use readelf based on current PATH, but it can be done as mistake or
problem if we have no PATH defined for tools: elfdump and readelf.
more better: to use env vars ELFDUMP and READELF instead.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug target/67733] elfdump and readelf in perl scripts should to use env vars ELFDUMP and READELF
2015-09-27 16:11 [Bug bootstrap/67733] New: elfdump and readelf in perl scripts should to use env vars ELFDUMP and READELF ikozhukhov at gmail dot com
@ 2015-09-27 16:14 ` pinskia at gcc dot gnu.org
2015-09-27 16:22 ` ikozhukhov at gmail dot com
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu.org @ 2015-09-27 16:14 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67733
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|bootstrap |target
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Why isn't illumos using the same filesystem layout as Solaris if it is calling
itself solaris as the os part of the target triplet?
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug target/67733] elfdump and readelf in perl scripts should to use env vars ELFDUMP and READELF
2015-09-27 16:11 [Bug bootstrap/67733] New: elfdump and readelf in perl scripts should to use env vars ELFDUMP and READELF ikozhukhov at gmail dot com
2015-09-27 16:14 ` [Bug target/67733] " pinskia at gcc dot gnu.org
@ 2015-09-27 16:22 ` ikozhukhov at gmail dot com
2015-09-27 16:25 ` pinskia at gcc dot gnu.org
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: ikozhukhov at gmail dot com @ 2015-09-27 16:22 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67733
--- Comment #2 from Igor Kozhukhov <ikozhukhov at gmail dot com> ---
/usr/ccs links old and unused.
also - illumos != solaris and can use his own layout.
at this moment it's not easy try to move to 'illumos' platform definition
because autotools not ready to define and use it.
illumos is OpenSources platform, but oracle solaris is closed and illumos
binaries incompatible with solaris binaries now.
will be more easy/better to use more universal gcc bootstrap process with
definition what can be using by env vars instead try to patch every gcc
bootstrap for every platform.
these changes not depend on illumos or solaris because we can use tools ELFDUMP
& READELF from different locations and hardcode it is not a good way for others
platforms to use it and hack bootstrap process every time.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug target/67733] elfdump and readelf in perl scripts should to use env vars ELFDUMP and READELF
2015-09-27 16:11 [Bug bootstrap/67733] New: elfdump and readelf in perl scripts should to use env vars ELFDUMP and READELF ikozhukhov at gmail dot com
2015-09-27 16:14 ` [Bug target/67733] " pinskia at gcc dot gnu.org
2015-09-27 16:22 ` ikozhukhov at gmail dot com
@ 2015-09-27 16:25 ` pinskia at gcc dot gnu.org
2015-09-27 16:44 ` graham.stott at btinternet dot com
2019-12-05 23:11 ` [Bug target/67733] illumos needs a new target triple ikozhukhov at gmail dot com
4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu.org @ 2015-09-27 16:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67733
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Igor Kozhukhov from comment #2)
> /usr/ccs links old and unused.
> also - illumos != solaris and can use his own layout.
> at this moment it's not easy try to move to 'illumos' platform definition
> because autotools not ready to define and use it.
Then do that first. Because ...
> illumos is OpenSources platform, but oracle solaris is closed and illumos
> binaries incompatible with solaris binaries now.
of this, you need a new triplet.
> will be more easy/better to use more universal gcc bootstrap process with
> definition what can be using by env vars instead try to patch every gcc
> bootstrap for every platform.
This is a because Solaris is special.
> these changes not depend on illumos or solaris because we can use tools
> ELFDUMP & READELF from different locations and hardcode it is not a good way
> for others platforms to use it and hack bootstrap process every time.
This is all in Solaris specific code though which is why it is done that way.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug target/67733] elfdump and readelf in perl scripts should to use env vars ELFDUMP and READELF
2015-09-27 16:11 [Bug bootstrap/67733] New: elfdump and readelf in perl scripts should to use env vars ELFDUMP and READELF ikozhukhov at gmail dot com
` (2 preceding siblings ...)
2015-09-27 16:25 ` pinskia at gcc dot gnu.org
@ 2015-09-27 16:44 ` graham.stott at btinternet dot com
2019-12-05 23:11 ` [Bug target/67733] illumos needs a new target triple ikozhukhov at gmail dot com
4 siblings, 0 replies; 6+ messages in thread
From: graham.stott at btinternet dot com @ 2015-09-27 16:44 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67733
--- Comment #4 from graham.stott at btinternet dot com ---
Sent from Samsung Mobile on O2
<div>-------- Original message --------</div><div>From: "pinskia at gcc dot
gnu.org" <gcc-bugzilla@gcc.gnu.org> </div><div>Date:27/09/2015 17:25
(GMT+00:00) </div><div>To: gcc-bugs@gcc.gnu.org </div><div>Subject: [Bug
target/67733] elfdump and readelf in perl scripts should to use env vars
ELFDUMP and READELF </div><div>
</div>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67733
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Igor Kozhukhov from comment #2)
> /usr/ccs links old and unused.
> also - illumos != solaris and can use his own layout.
> at this moment it's not easy try to move to 'illumos' platform definition
> because autotools not ready to define and use it.
Then do that first. Because ...
> illumos is OpenSources platform, but oracle solaris is closed and illumos
> binaries incompatible with solaris binaries now.
of this, you need a new triplet.
> will be more easy/better to use more universal gcc bootstrap process with
> definition what can be using by env vars instead try to patch every gcc
> bootstrap for every platform.
This is a because Solaris is special.
> these changes not depend on illumos or solaris because we can use tools
> ELFDUMP & READELF from different locations and hardcode it is not a good way
> for others platforms to use it and hack bootstrap process every time.
This is all in Solaris specific code though which is why it is done that way.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug target/67733] illumos needs a new target triple
2015-09-27 16:11 [Bug bootstrap/67733] New: elfdump and readelf in perl scripts should to use env vars ELFDUMP and READELF ikozhukhov at gmail dot com
` (3 preceding siblings ...)
2015-09-27 16:44 ` graham.stott at btinternet dot com
@ 2019-12-05 23:11 ` ikozhukhov at gmail dot com
4 siblings, 0 replies; 6+ messages in thread
From: ikozhukhov at gmail dot com @ 2019-12-05 23:11 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: 1383536 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67733
--- Comment #7 from Igor Kozhukhov <ikozhukhov at gmail dot com> ---
i'd like to have DilOS triplets like:
Intel:
x86_64-dilos/i386-dilos
(or for 64bit amd64-dilos)
SPARC:
sparc64-dilos/sparc-dilos (or sparc32-dilos)
(or 64bit: sparcv9-dilos, 32bit: sparcv7-dilos)
it one day DilOS can be independent platform and do not depend on illumos.
right now we have DilOS as separate platform for ZFS:
https://docs.google.com/spreadsheets/d/1CFapSYxA5QRFYy5k6ge3FutU7zbAWbaeGN2nKVXgxCI/edit?pli=1#gid=0
because ZFS features are different.
also, with DilOS we are try to port and use Debian userland in main place - it
is not what illumos does + additional platform specific updates.
i'm DilOS owner.
question is: if i need new triplets, what is procedure for add it to GCC
mainline?
what are triplets can be used/useful for our platform?
>From gcc-bugs-return-662508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 23:53:46 2019
Return-Path: <gcc-bugs-return-662508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102172 invoked by alias); 5 Dec 2019 23:53: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 102105 invoked by uid 55); 5 Dec 2019 23:53:41 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9/10 Regression] Maybe a wrong code for vector constants
Date: Thu, 05 Dec 2019 23:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92768-4-ip4ZZ268Hu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00578.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Dec 5 23:53:09 2019
New Revision: 279024
URL: https://gcc.gnu.org/viewcvs?rev=279024&root=gcc&view=rev
Log:
PR tree-optimization/92768
* gcc.dg/pr92768.c: Add -w -Wno-psabi to dg-options.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/pr92768.c
>From gcc-bugs-return-662509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 05 23:54:18 2019
Return-Path: <gcc-bugs-return-662509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103400 invoked by alias); 5 Dec 2019 23:54: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 103279 invoked by uid 48); 5 Dec 2019 23:54:11 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92824] Wrong optimization: representation of long doubles not copied even with memcpy
Date: Thu, 05 Dec 2019 23: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:
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: cf_gcctarget
Message-ID: <bug-92824-4-zuoXOTIkD5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00579.txt.bz2
Content-length: 698
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92824
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-linux-gnu, m68k
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
y = x;
I thought that would only copy the representational bits. so padding for the
scalar value is ignored.
NOTE this is only an issue with x86 (and maybe m68k too)'s 80bit but with 16bit
(or 48bit) worth of padding. Those are the only scalar types with padding. No
other targets have this padding issue.
>From gcc-bugs-return-662510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 00:13:06 2019
Return-Path: <gcc-bugs-return-662510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130781 invoked by alias); 6 Dec 2019 00:13:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130717 invoked by uid 48); 6 Dec 2019 00:13:00 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92824] Wrong optimization: representation of long doubles not copied even with memcpy
Date: Fri, 06 Dec 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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92824-4-VkGi9nlmMs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00580.txt.bz2
Content-length: 191
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92824
--- Comment #2 from Andreas Schwab <schwab@linux-m68k.org> ---
On m68k the padding is internal, and actually part of the representation.
>From gcc-bugs-return-662511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 00:19:08 2019
Return-Path: <gcc-bugs-return-662511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8433 invoked by alias); 6 Dec 2019 00: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 8375 invoked by uid 55); 6 Dec 2019 00:19:04 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92622] FAIL: gcc.dg/Warray-bounds-22.c on ILP32: missing warnings for VLA on lines 67 and 69
Date: Fri, 06 Dec 2019 00: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92622-4-bNmNbwcguD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92622-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92622-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00581.txt.bz2
Content-length: 620
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92622
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Fri Dec 6 00:18:32 2019
New Revision: 279029
URL: https://gcc.gnu.org/viewcvs?rev=279029&root=gcc&view=rev
Log:
PR middle-end/92622 - FAIL: gcc.dg/Warray-bounds-22.c on ILP32: missing
warnings for VLA on lines 67 and 69
gcc/ChangeLog:
PR middle-end/92622
* tree-vrp.c (vrp_prop::check_array_ref): Avoid using a variable
left uninitialized by get_addr_base_and_unit_offset ofn failure.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/tree-vrp.c
>From gcc-bugs-return-662512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 00:20:38 2019
Return-Path: <gcc-bugs-return-662512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10165 invoked by alias); 6 Dec 2019 00:20: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 10053 invoked by uid 48); 6 Dec 2019 00:20:33 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92622] FAIL: gcc.dg/Warray-bounds-22.c on ILP32: missing warnings for VLA on lines 67 and 69
Date: Fri, 06 Dec 2019 00: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: 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: keywords bug_status component resolution
Message-ID: <bug-92622-4-MRV8tyaTpq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92622-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92622-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00582.txt.bz2
Content-length: 620
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92622
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
Status|ASSIGNED |RESOLVED
Component|testsuite |middle-end
Resolution|--- |FIXED
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch (https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00386.html) committed in
r279029.
>From gcc-bugs-return-662513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 00:20:38 2019
Return-Path: <gcc-bugs-return-662513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10239 invoked by alias); 6 Dec 2019 00:20: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 10078 invoked by uid 48); 6 Dec 2019 00:20:34 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56456] [meta-bug] bogus/missing -Warray-bounds
Date: Fri, 06 Dec 2019 00:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: diagnostic, 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-56456-4-LwWz9rPqtu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56456-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56456-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00583.txt.bz2
Content-length: 513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456
Bug 56456 depends on bug 92622, which changed state.
Bug 92622 Summary: FAIL: gcc.dg/Warray-bounds-22.c on ILP32: missing warnings for VLA on lines 67 and 69
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92622
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-662514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 00:45:56 2019
Return-Path: <gcc-bugs-return-662514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64108 invoked by alias); 6 Dec 2019 00: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 63999 invoked by uid 48); 6 Dec 2019 00:45:49 -0000
From: "doko at ubuntu dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Fri, 06 Dec 2019 00:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at ubuntu dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92820-4-Uc5OUKnpmK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00584.txt.bz2
Content-length: 649
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
Matthias Klose <doko at ubuntu dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |doko at ubuntu dot com
--- Comment #8 from Matthias Klose <doko at ubuntu dot com> ---
an arm-linux-gnuebaihf build now fails with:
./../../src/libgo/runtime/go-context.S: Assembler messages:
../../../src/libgo/runtime/go-context.S:74: Error: junk at end of line, first
unrecognized character is `,'
make[6]: *** [Makefile:1441: runtime/go-context.lo] Error 1
>From gcc-bugs-return-662515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 00:47:33 2019
Return-Path: <gcc-bugs-return-662515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68851 invoked by alias); 6 Dec 2019 00: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 68691 invoked by uid 48); 6 Dec 2019 00:47:29 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Fri, 06 Dec 2019 00:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92820-4-65AiIHLUbn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00585.txt.bz2
Content-length: 449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
Matthias Klose <doko at debian dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|FIXED |---
--- Comment #9 from Matthias Klose <doko at debian dot org> ---
not fixed on arm-linux-gnuaebi-hf
>From gcc-bugs-return-662516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 01:03:07 2019
Return-Path: <gcc-bugs-return-662516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68746 invoked by alias); 6 Dec 2019 01:03: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 68658 invoked by uid 48); 6 Dec 2019 01:03:01 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92829] [10 regression] several test case failures starting with r278983
Date: Fri, 06 Dec 2019 01:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92829-4-6gglzcru7z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00586.txt.bz2
Content-length: 2429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92829
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
The failures in Warray-bounds-56.c boil down to this test case where the
powerpc64 cross-compiler diagnoses only three out of the four buffer overflows,
missing the one first one in f(). The native x86_64 compiler detects all of
them. I'll adjust the test to avoid the failure but I'll probably raise a
separate bug to look into why it happens because it affects other tests as
well.
$ cat t.c && /build/powerpc64le-linux/gcc-svn/gcc/xgcc -B
/build/powerpc64le-linux/gcc-svn/gcc -O2 -S -Wall -Wno-stringop-overflow
-ftrack-macro-expansion=0 t.c
typedef __SIZE_TYPE__ size_t;
extern void* malloc (size_t);
extern char* strcpy (char*, const char*);
void sink (void*);
size_t value (void);
size_t range (size_t min, size_t max)
{
size_t val = value ();
return val < min || max < val ? min : val;
}
#undef T
#define T(T, src, n) do { \
char *s = src; \
typedef struct { T n, ax[]; } Flex; \
Flex *p = (Flex*)malloc (sizeof *p + n); \
char *d = (char*)p->ax; \
strcpy (d, s); \
sink (p); \
} while (0)
void f (void)
{
size_t r_1_2 = range (1, 2);
size_t r_2_3 = range (2, 3);
T (char, "12", r_1_2); // { dg-warning "\\\[-Warray-bounds" }
T (char, "123456789", r_2_3); // { dg-warning "\\\[-Warray-bounds" }
}
void g (void)
{
size_t r_1_2 = range (1, 2);
T (char, "12", r_1_2); // { dg-warning "\\\[-Warray-bounds" }
size_t r_2_3 = range (2, 3);
T (char, "123456789", r_2_3); // { dg-warning "\\\[-Warray-bounds" }
}
t.c: In function 'f':
t.c:32:3: warning: '__builtin_memcpy' forming offset [4, 10] is out of the
bounds [0, 4] [-Warray-bounds]
32 | T (char, "123456789", r_2_3); // { dg-warning "\\\[-Warray-bounds"
}
| ^
t.c: In function 'g':
t.c:38:3: warning: '__builtin_memcpy' forming offset 3 is out of the bounds [0,
3] [-Warray-bounds]
38 | T (char, "12", r_1_2); // { dg-warning "\\\[-Warray-bounds"
}
| ^
t.c:41:3: warning: '__builtin_memcpy' forming offset [4, 10] is out of the
bounds [0, 4] [-Warray-bounds]
41 | T (char, "123456789", r_2_3); // { dg-warning "\\\[-Warray-bounds"
}
| ^
>From gcc-bugs-return-662517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 01:05:21 2019
Return-Path: <gcc-bugs-return-662517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76964 invoked by alias); 6 Dec 2019 01:05: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 76884 invoked by uid 55); 6 Dec 2019 01:05:15 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92829] [10 regression] several test case failures starting with r278983
Date: Fri, 06 Dec 2019 01:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92829-4-O5QStqHWzD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00587.txt.bz2
Content-length: 542
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92829
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Fri Dec 6 01:04:42 2019
New Revision: 279031
URL: https://gcc.gnu.org/viewcvs?rev=279031&root=gcc&view=rev
Log:
PR testsuite/92829 - several test case failures starting with r278983
gcc/testsuite/ChangeLog:
* gcc.dg/Warray-bounds-56.c: Rearrange code to avoid powerpc64*
failures.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/Warray-bounds-56.c
>From gcc-bugs-return-662518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 03:04:41 2019
Return-Path: <gcc-bugs-return-662518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67646 invoked by alias); 6 Dec 2019 03:04: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 67608 invoked by uid 48); 6 Dec 2019 03:04:35 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92826] Impossible to silence warning: non-standard suffix on floating constant [-Wpedantic]
Date: Fri, 06 Dec 2019 03: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92826-4-VVbUM3BKKo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92826-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00588.txt.bz2
Content-length: 507
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92826
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> I think this is a duplicate of an existing bug.
bug 87274 perhaps?
>From gcc-bugs-return-662519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 03:07:55 2019
Return-Path: <gcc-bugs-return-662519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81891 invoked by alias); 6 Dec 2019 03:07: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 81799 invoked by uid 48); 6 Dec 2019 03:07:49 -0000
From: "abensonca at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] New: segfault with inquire()
Date: Fri, 06 Dec 2019 03:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: abensonca 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-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00589.txt.bz2
Content-length: 4714
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
Bug ID: 92836
Summary: segfault with inquire()
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: abensonca at gmail dot com
Target Milestone: ---
I'm attempting to track down a segfault that seems to be associated with the
inquire() statement. Unfortunately it only happens when running a massively
parallel code, using both MPI and OpenMP parallelism, and I have as yet been
unable to make a simple test case that reproduces the bug. I also haven't
convinced myself 100% that the problem is really in the libgfortran code for
inquire() and not in my own code, but since it seems that inquire() should be
thread safe it seems that the problem at least could be in libgfortran.
So, I'm hoping that someone on the mailing list has suggestions for how to
track this down as I've exhausted everything I can think of!
The segfault is triggered by:
inquire(file=fileName,exist=exists)
This works as expected most of the time, but occasionally (typically after
thousands of calls in a code running with 128 MPI processes and 4 OpenMP
threads each) it will segfault. The gdb trace for the failed thread is:
(gdb) where
#0 galacticus_error::galacticus_signal_handler_sigsegv () at ./work/buildMPI/
galacticus.error.p.F90:328
#1 <signal handler called>
#2 find_file0 (u=<optimized out>, st=st@entry=0x7ffed9b88ad0) at ../../../gcc-
trunk/libgfortran/io/unix.c:1725
#3 0x00007f33ac1b7460 in find_file0 (u=<optimized out>,
st=st@entry=0x7ffed9b88ad0) at ../../../gcc-trunk/libgfortran/io/unix.c:1741
#4 0x00007f33ac1b7460 in find_file0 (u=<optimized out>,
st=st@entry=0x7ffed9b88ad0) at ../../../gcc-trunk/libgfortran/io/unix.c:1741
#5 0x00007f33ac1b7460 in find_file0 (u=<optimized out>,
st=st@entry=0x7ffed9b88ad0) at ../../../gcc-trunk/libgfortran/io/unix.c:1741
#6 0x00007f33ac1b7460 in find_file0 (u=<optimized out>,
st=st@entry=0x7ffed9b88ad0) at ../../../gcc-trunk/libgfortran/io/unix.c:1741
#7 0x00007f33ac1b7460 in find_file0 (u=<optimized out>,
st=st@entry=0x7ffed9b88ad0) at ../../../gcc-trunk/libgfortran/io/unix.c:1741
#8 0x00007f33ac1b8bbb in _gfortrani_find_file (file=<optimized out>,
file_len=<optimized out>) at ../../../gcc-trunk/libgfortran/io/unix.c:1779
#9 0x00007f33ac1a601d in _gfortran_st_inquire (iqp=0x7ffed9b88bf0) at
../../../gcc-trunk/libgfortran/io/inquire.c:803
and the relevant line in unix.c is:
1725 if (st[0].st_dev == s->st_dev && st[0].st_ino == s->st_ino)
If I examine the variables used in this line I find:
(gdb) print st[0]
$2 = {st_dev = 24, st_ino = 12194159, st_nlink = 1, st_mode = 33188, st_uid =
509, st_gid = 100, __pad0 = 0, st_rdev = 0, st_size = 104168, st_blksize =
1048576, st_blocks = 208,
st_atim = {tv_sec = 1575236480, tv_nsec = 343597308}, st_mtim = {tv_sec =
1575236486, tv_nsec = 774663718}, st_ctim = {tv_sec = 1575236486, tv_nsec =
774663718}, __unused = {0, 0,
0}}
(gdb) print *s
Cannot access memory at address 0x7f33818d7eb0
which suggests that "s" is somehow corrupted. I don't see how this can happen
though as the "unit_lock" lock is used by find_file() which should prevent any
modification to the tree of units.
One other OpenMP thread was waiting for unit_lock:
#0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/
lowlevellock.S:136
#1 0x00007f33ab4a354f in _L_lock_1028 () from /home/abenson/Galacticus/Tools/
lib/libpthread.so.0
#2 0x00007f33ab4a336b in __pthread_mutex_lock (mutex=0x7f33ac40b340
<_gfortrani_unit_lock>) at pthread_mutex_lock.c:61
#3 0x00007f33ac1b6f3c in __gthread_mutex_lock (__mutex=0x7f33ac40b340
<_gfortrani_unit_lock>) at ../libgcc/gthr-default.h:749
#4 _gfortrani_newunit_alloc () at ../../../gcc-trunk/libgfortran/io/unit.c:
906
#5 0x00007f33ac1b706b in _gfortrani_get_unit (dtp=dtp@entry=0x7f33a1785800,
do_create=do_create@entry=1) at ../../../gcc-trunk/libgfortran/io/unit.c:555
#6 0x00007f33ac1b4ebd in data_transfer_init (dtp=dtp@entry=0x7f33a1785800,
read_flag=read_flag@entry=0) at ../../../gcc-trunk/libgfortran/io/transfer.c:
2851
#7 0x00007f33ac1b5924 in _gfortran_st_write (dtp=dtp@entry=0x7f33a1785800) at
../../../gcc-trunk/libgfortran/io/transfer.c:4392
and was doing other writes to an internal file unit just prior to this.
>From gcc-bugs-return-662520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 03:08:37 2019
Return-Path: <gcc-bugs-return-662520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83112 invoked by alias); 6 Dec 2019 03:08: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 83063 invoked by uid 48); 6 Dec 2019 03:08:31 -0000
From: "abensonca at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 2019 03:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: abensonca 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-92836-4-WeEeOmn664@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00590.txt.bz2
Content-length: 2776
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
--- Comment #1 from Andrew Benson <abensonca at gmail dot com> ---
Running with -fsanitize=thread (suggested by Tobias) gives:
==================
WARNING: ThreadSanitizer: lock-order-inversion (potential deadlock) (pid=9982)
Cycle in lock order graph: M26 (0x7f02bb31c340) => M84 (0x7b58002efee0) =>
M26
Mutex M84 acquired here while holding mutex M26 in thread T63:
#0 pthread_mutex_lock ../../../../gcc-trunk/libsanitizer/sanitizer_common/
sanitizer_common_interceptors.inc:4148 (libtsan.so.0+0x5095a)
#1 __gthread_mutex_lock ../libgcc/gthr-default.h:749 (libgfortran.so.
5+0x1e25c9)
#2 insert_unit ../../../gcc-trunk/libgfortran/io/unit.c:244
(libgfortran.so.5+0x1e25c9)
#3 gomp_thread_start ../../../gcc-trunk/libgomp/team.c:123 (libgomp.so.
1+0x198a5)
Mutex M26 previously acquired by the same thread here:
#0 pthread_mutex_lock ../../../../gcc-trunk/libsanitizer/sanitizer_common/
sanitizer_common_interceptors.inc:4148 (libtsan.so.0+0x5095a)
#1 __gthread_mutex_lock ../libgcc/gthr-default.h:749 (libgfortran.so.
5+0x1e265c)
#2 get_gfc_unit ../../../gcc-trunk/libgfortran/io/unit.c:332
(libgfortran.so.5+0x1e265c)
#3 gomp_thread_start ../../../gcc-trunk/libgomp/team.c:123 (libgomp.so.
1+0x198a5)
Mutex M26 acquired here while holding mutex M84 in thread T63:
#0 pthread_mutex_lock ../../../../gcc-trunk/libsanitizer/sanitizer_common/
sanitizer_common_interceptors.inc:4148 (libtsan.so.0+0x5095a)
#1 __gthread_mutex_lock ../libgcc/gthr-default.h:749 (libgfortran.so.
5+0x1e336b)
#2 close_unit_1 ../../../gcc-trunk/libgfortran/io/unit.c:735
(libgfortran.so.5+0x1e336b)
#3 gomp_thread_start ../../../gcc-trunk/libgomp/team.c:123 (libgomp.so.
1+0x198a5)
Mutex M84 previously acquired by the same thread here:
#0 pthread_mutex_trylock ../../../../gcc-trunk/libsanitizer/tsan/
tsan_interceptors_posix.cpp:1246 (libtsan.so.0+0x4340a)
#1 __gthread_mutex_trylock ../libgcc/gthr-default.h:758 (libgfortran.so.
5+0x1e26f1)
#2 get_gfc_unit ../../../gcc-trunk/libgfortran/io/unit.c:380
(libgfortran.so.5+0x1e26f1)
#3 gomp_thread_start ../../../gcc-trunk/libgomp/team.c:123 (libgomp.so.
1+0x198a5)
Thread T63 (tid=10047, running) created by main thread at:
#0 pthread_create ../../../../gcc-trunk/libsanitizer/tsan/
tsan_interceptors_posix.cpp:962 (libtsan.so.0+0x5bb22)
#1 gomp_team_start ../../../gcc-trunk/libgomp/team.c:839 (libgomp.so.
1+0x19eba)
#2 main <null> (a.out+0x400ef9)
SUMMARY: ThreadSanitizer: lock-order-inversion (potential deadlock) ../libgcc/
gthr-default.h:749 in __gthread_mutex_lock
==================
>From gcc-bugs-return-662521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 03:17:28 2019
Return-Path: <gcc-bugs-return-662521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91833 invoked by alias); 6 Dec 2019 03:17: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 91666 invoked by uid 48); 6 Dec 2019 03:17:21 -0000
From: "abensonca at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 2019 03:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: abensonca 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-92836-4-Wk90SG7EYG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00591.txt.bz2
Content-length: 1658
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
--- Comment #2 from Andrew Benson <abensonca at gmail dot com> ---
Answers to questions raised by Jerry at:
https://gcc.gnu.org/ml/fortran/2019-12/msg00059.html
> 1) Are you opening a unique file (by file name) in each thread?
No. The code is operating on many files, but in the specific case that causes
the problem it's a file which is shared by all threads. Specifically, it's a
file which is generated by the code if the file does not already exist (it
stores solutions to a time-consuming calculation), or is read by the code if it
does exist. All threads write/read the same file.
> 2) Are you trying to synchronize these threads using the inquire?
No. The inquire() is used only to see if the file exists already. If it does,
the code branches to read the file, if it does not, the code branches to
generate the data for the file and then write it.
Synchronization of the file accesses are being handled using file locks, i.e. I
use ISO_C_Binding to allow me to call fcntl(). Since the Linux kernel on the
machine I'm using is too old to support OFD locks I'm using POSIX locks plus
OpenMP locks (since POSIX locks are per processes so I have to separately
synchronize the OpenMP threads).
> 3) or, trying to ensure a unique filename for each file or avoid the same
> file in two or more threads?
No. The problem always seems to occur when a thread inquires() on one
particular file, and the file name is the same across all threads.
There are other places in my code where inquire() is being used on other file
names. But in all cases the filename is the same for all threads.
>From gcc-bugs-return-662522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 04:02:47 2019
Return-Path: <gcc-bugs-return-662522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87336 invoked by alias); 6 Dec 2019 04:02: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 87268 invoked by uid 48); 6 Dec 2019 04:02:43 -0000
From: "arthur.j.odwyer at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92837] New: ICE on syntax error in requires clause, in cp_parser_constraint_primary_expression
Date: Fri, 06 Dec 2019 04: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: arthur.j.odwyer 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-92837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00592.txt.bz2
Content-length: 949
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92837
Bug ID: 92837
Summary: ICE on syntax error in requires clause, in
cp_parser_constraint_primary_expression
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: arthur.j.odwyer at gmail dot com
Target Milestone: ---
Bug 92439 may be related.
cat >test.cc <<EOF
template<class> concept A = true;
template<class T> requires (A<T> int
EOF
g++ -std=c++2a test.cc
test.cc:2:29: internal compiler error: in
cp_parser_constraint_primary_expression, at cp/parser.c:27319
3 | template<class T> requires (A<T> int
| ^~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-662523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 04:49:38 2019
Return-Path: <gcc-bugs-return-662523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101608 invoked by alias); 6 Dec 2019 04: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 101494 invoked by uid 48); 6 Dec 2019 04:49:33 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 2019 04:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-92836-4-K9KBE6PR7r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00593.txt.bz2
Content-length: 3580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at gcc dot gnu.org
--- Comment #3 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
With the the following example I see varying results:
program inq
use OMP_Lib
implicit none
logical :: s
character(len=27) :: c
integer :: i, j
i=64
!$omp parallel private(c,j,s)
print *, OMP_Get_Thread_Num(), omp_get_num_threads(), omp_get_num_threads()/2
do while (.true.)
if (OMP_Get_Thread_Num() < omp_get_num_threads()/2) then
open(newUnit=j,file='test.txt',form='formatted',status='unknown')
write (c,'(e17.10, ">>>",i5, i5, "<<<")') 1.23456d0, j,
OMP_Get_Thread_Num()
write (j,*) trim(c)
close(j)
else
inquire(file='test.txt',exist=s)
end if
end do
!$omp end parallel
end program
I get randomly:
$ ./a.out
0 8 4
3 8 4
6 8 4
5 8 4
4 8 4
1 8 4
2 8 4
At line 14 of file bug1.f90
At line 14 of file bug1.f90
7 8 4
Fortran runtime error: Fortran runtime error: End of recordEnd of record
$ ./a.out
2 8 4
5 8 4
6 8 4
1 8 4
7 8 4
0 8 4
4 8 4
3 8 4
At line 14 of file bug1.f90
At line 14 of file bug1.f90
At line 14 of file bug1.f90
At line 14 of file bug1.f90
Fortran runtime error: Fortran runtime error: Fortran runtime error: End of
recordFortran runtime error: End of recordEnd of record
End of record
[jerry@amdr threadbug]$ ./a.out
0 8 4
2 8 4
6 8 4
1 8 4
5 8 4
7 8 4
At line 14 of file bug1.f90
Fortran runtime error: End of record
3 8 4
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
$ ./a.out
2 8 4
6 8 4
1 8 4
0 8 4
5 8 4
7 8 4
3 8 4
4 8 4
At line 14 of file bug1.f90
At line 14 of file bug1.f90
Fortran runtime error: At line 14 of file bug1.f90
At line 14 of file bug1.f90
End of recordFortran runtime error: Fortran runtime error: Fortran runtime
error:
End of recordEnd of recordEnd of record
$ ./a.out
7 8 4
6 8 4
1 8 4
0 8 4
5 8 4
2 8 4
3 8 4
At line 14 of file bug1.f90
Fortran runtime error: 4 8 4
End of record
At line 14 of file bug1.f90
Fortran runtime error: End of file
>From gcc-bugs-return-662524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 05:07:05 2019
Return-Path: <gcc-bugs-return-662524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123931 invoked by alias); 6 Dec 2019 05:07: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 123861 invoked by uid 48); 6 Dec 2019 05:06:59 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 2019 05:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92836-4-LlFiFiC741@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00594.txt.bz2
Content-length: 814
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
--- Comment #4 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Removing close statement:
$ ./a.out
0 8 4
2 8 4
-10
5 8 4
4 8 4
3 8 4
At line 16 of file bug1.f90
Fortran runtime error: End of record
6 8 4
At line 14 of file bug1.f90
Internal Error: Unit number changed
At line 14 of file bug1.f90
What I speculate is happening is that newunit is getting invoked in the middle
of trying to close the unit on a different thread and we do end up with
duplicate unit numbers assigned by newunit. I need to look at that code yet.
Exploring further here.
>From gcc-bugs-return-662525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 05:33:32 2019
Return-Path: <gcc-bugs-return-662525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17915 invoked by alias); 6 Dec 2019 05:33: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 17844 invoked by uid 55); 6 Dec 2019 05:33:26 -0000
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92810] Compiling GCC go for aarch64_be-marvell-linux-gnu fails
Date: Fri, 06 Dec 2019 05:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92810-4-njX6WdSYSF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00595.txt.bz2
Content-length: 502
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92810
--- Comment #1 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Fri Dec 6 05:32:49 2019
New Revision: 279032
URL: https://gcc.gnu.org/viewcvs?rev=279032&root=gcc&view=rev
Log:
PR go/92810
libgo: recognize aarch64_be as arm64be
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/210038
Modified:
trunk/gcc/go/gofrontend/MERGE
trunk/libgo/configure
trunk/libgo/configure.ac
>From gcc-bugs-return-662526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 07:53:51 2019
Return-Path: <gcc-bugs-return-662526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67908 invoked by alias); 6 Dec 2019 07: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 67817 invoked by uid 55); 6 Dec 2019 07: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/92819] [10 Regression] Worse code generated on avx2 due to simplify_vector_constructor
Date: Fri, 06 Dec 2019 07: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92819-4-GmFVHWq0xS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00596.txt.bz2
Content-length: 849
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92819
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Fri Dec 6 07:53:15 2019
New Revision: 279033
URL: https://gcc.gnu.org/viewcvs?rev=279033&root=gcc&view=rev
Log:
2019-12-06 Richard Biener <rguenther@suse.de>
PR tree-optimization/92819
* match.pd (VEC_PERM_EXPR -> BIT_INSERT_EXPR): Handle inserts
into the last lane. For two-element vectors try inserting
into the last lane when inserting into the first fails.
* gcc.target/i386/pr92819-1.c: New testcase.
* gcc.target/i386/pr92803.c: Adjust.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr92819-1.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/match.pd
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.target/i386/pr92803.c
>From gcc-bugs-return-662527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 08:28:43 2019
Return-Path: <gcc-bugs-return-662527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67262 invoked by alias); 6 Dec 2019 08:28: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 67085 invoked by uid 48); 6 Dec 2019 08:28:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92819] [10 Regression] Worse code generated on avx2 due to simplify_vector_constructor
Date: Fri, 06 Dec 2019 08:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
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-92819-4-PNcybfeRvi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00597.txt.bz2
Content-length: 2857
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92819
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Update:
--- t2.s.9 2019-12-06 09:03:03.104331362 +0100
+++ t2.s.10 2019-12-06 09:02:52.700181055 +0100
@@ -6,8 +6,9 @@
foo:
.LFB0:
.cfi_startproc
- vunpckhpd %xmm0, %xmm0, %xmm0
- vmovhpd (%rdi), %xmm0, %xmm0
+ vbroadcastsd (%rdi), %ymm1
+ vperm2f128 $48, %ymm1, %ymm0, %ymm0
+ vshufpd $11, %ymm1, %ymm0, %ymm0
ret
.cfi_endproc
.LFE0:
@@ -29,8 +30,8 @@
baz:
.LFB2:
.cfi_startproc
- vunpckhpd %xmm0, %xmm0, %xmm0
- vmovhpd (%rdi), %xmm0, %xmm0
+ vmovddup (%rdi), %xmm1
+ vunpckhpd %xmm1, %xmm0, %xmm0
ret
.cfi_endproc
.LFE2:
@@ -52,12 +53,12 @@
corge:
.LFB4:
.cfi_startproc
- vextractf128 $0x1, %ymm0, %xmm0
- vunpckhpd %xmm0, %xmm0, %xmm0
- vmovhpd (%rdi), %xmm0, %xmm0
+ vbroadcastsd (%rdi), %ymm1
+ vperm2f128 $49, %ymm1, %ymm0, %ymm0
+ vshufpd $11, %ymm1, %ymm0, %ymm0
ret
.cfi_endproc
.LFE4:
.size corge, .-corge
- .ident "GCC: (GNU) 9.2.0"
+ .ident "GCC: (GNU) 10.0.0 20191206 (experimental) [trunk revision
270575]"
.section .note.GNU-stack,"",@progbits
"foo" is clearly worse, "corge" very likely and "baz" _might_ be slightly
better (the load happens one instruction earlier, eventually hiding some
latency and a dup from a load should be able to micro-fuse to the load op
in my naiive wishful thinking).
foo (v4df x, double * p)
{
double _1;
vector(4) double _5;
vector(4) double _6;
vector(2) double _7;
<bb 2> [local count: 1073741824]:
_1 = *p_4(D);
_5 = {_1, _1, _1, _1};
_6 = VEC_PERM_EXPR <x_2(D), _5, { 1, 5, 6, 7 }>;
_7 = BIT_FIELD_REF <_6, 128, 0>;
return _7;
baz (v2df x, double * p)
{
double _1;
vector(2) double _5;
vector(2) double _6;
<bb 2> [local count: 1073741824]:
_1 = *p_4(D);
_5 = {_1, _1};
_6 = VEC_PERM_EXPR <x_2(D), _5, { 1, 3 }>;
return _6;
corge (v4df x, double * p, v2df y)
{
double _1;
vector(4) double _5;
vector(4) double _6;
vector(2) double _7;
<bb 2> [local count: 1073741824]:
_1 = *p_4(D);
_5 = {_1, _1, _1, _1};
_6 = VEC_PERM_EXPR <x_2(D), _5, { 3, 5, 6, 7 }>;
_7 = BIT_FIELD_REF <_6, 128, 0>;
return _7;
Now disabling VEC_PERM generation won't be a 100% solution in general since
the user can present us with the above as well.
Looking at "corge" gcc9 expanded this as
extract upper half of x
extract lane 1 from this
load the scalar
concat both
so it performed the permute on smaller vectors rather than permuting
the orignals and then selecting the lowpart.
I'll see if I can cook up sth for simplify_bitfield_ref.
>From gcc-bugs-return-662528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 08:48:54 2019
Return-Path: <gcc-bugs-return-662528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103833 invoked by alias); 6 Dec 2019 08:48: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 103557 invoked by uid 48); 6 Dec 2019 08:48:44 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92823] Is that possible to optimize C++ exception??????????? I always HATE 2 phases of exception unwind
Date: Fri, 06 Dec 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: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: EH
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-92823-4-ycwGKk2PNN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92823-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00598.txt.bz2
Content-length: 233
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92823
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
It's called "exception" handling. If you use an "exception" on the fast path
you are doing something wrong.
>From gcc-bugs-return-662529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 09:18:06 2019
Return-Path: <gcc-bugs-return-662529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103402 invoked by alias); 6 Dec 2019 09:18: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 103336 invoked by uid 48); 6 Dec 2019 09:18:02 -0000
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92176] LRA problem with reloads for subreg operands
Date: Fri, 06 Dec 2019 09: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: ra, wrong-code
X-Bugzilla-Severity: major
X-Bugzilla-Who: krebbel at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92176-4-IcvTRwte8o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92176-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92176-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00599.txt.bz2
Content-length: 717
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92176
--- Comment #7 from Andreas Krebbel <krebbel at gcc dot gnu.org> ---
Created attachment 47432
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47432&action=edit
Updated testcase
This is an updated testcase with the changes I propose.
Your testcase works fine. However, I would propose two minor adjustments:
- add -mzarch to enable the vector instructions also in a testsuite run with
-m31. The testcase does not trigger the problem on -m31 for other reasons but
that way it would at least have to the chance to.
- scan also for the element index in vsteb to be 0. With the proper index there
is a chance that code with vsteb is actually correct.
>From gcc-bugs-return-662530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 09:20:33 2019
Return-Path: <gcc-bugs-return-662530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106193 invoked by alias); 6 Dec 2019 09: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 106136 invoked by uid 48); 6 Dec 2019 09:20:29 -0000
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92828] array out of bounds access in libcpp/mkdeps.c
Date: Fri, 06 Dec 2019 09:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: krebbel 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-92828-4-zoKwq0MeeO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00600.txt.bz2
Content-length: 557
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92828
Andreas Krebbel <krebbel at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
--- Comment #5 from Andreas Krebbel <krebbel at gcc dot gnu.org> ---
Since this currently prevents bootstrapping for z13 or higher on IBM Z I would
prefer to have a quick solution. Would it be acceptable to disable the warning
in mkdeps.c via pragma for now?
>From gcc-bugs-return-662531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 09:53:31 2019
Return-Path: <gcc-bugs-return-662531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95330 invoked by alias); 6 Dec 2019 09:53: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 95271 invoked by uid 48); 6 Dec 2019 09:53:26 -0000
From: "sw6ueyz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92838] New: ICE (internal compiler error) calling lambda object with requires clause (in in dependent_type_p)
Date: Fri, 06 Dec 2019 09:53: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: sw6ueyz 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-92838-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00601.txt.bz2
Content-length: 3740
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92838
Bug ID: 92838
Summary: ICE (internal compiler error) calling lambda object
with requires clause (in in dependent_type_p)
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: sw6ueyz at gmail dot com
Target Milestone: ---
Created attachment 47433
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47433&action=edit
the source
// this code generates ICE in g++
//
// command line :
// g++ prog.cc -Wall -Wextra -I/opt/wandbox/boost-1.71.0/gcc-head/include
-std=gnu++2a
//
// test link :
// https://godbolt.org/z/yeZ-Mc
template< class _Type >
auto foo( _Type&& )
{
if ( []() requires ( sizeof( _Type ) == 4U ) { return true; }() )
return true;
else
return false;
}
int main()
{
foo( 0 );
return 0;
}
/*
error log :
prog.cc: In instantiation of 'foo(_Type&&) [with _Type = int]::<lambda()>':
prog.cc:5:10: required from 'auto foo(_Type&&) [with _Type = int]'
prog.cc:14:9: required from here
prog.cc:5:26: internal compiler error: in dependent_type_p, at cp/pt.c:26007
5 | if ( []() requires ( sizeof( _Type ) == 4U ) { return true; }() )
| ^~~~~~~~~~~~~~~
0x5a08f0 dependent_type_p(tree_node*)
../../source/gcc/cp/pt.c:26007
0x739417 cxx_sizeof_or_alignof_type(tree_node*, tree_code, bool, bool)
../../source/gcc/cp/typeck.c:1687
0x6f3098 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
../../source/gcc/cp/pt.c:19188
0x6f1114 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
../../source/gcc/cp/pt.c:18814
0x6ecf8d tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
../../source/gcc/cp/pt.c:18814
0x6ecf8d tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
../../source/gcc/cp/pt.c:18472
0x61bef2 satisfy_constraint_r
../../source/gcc/cp/constraint.cc:2500
0x61c668 satisfy_constraint
../../source/gcc/cp/constraint.cc:2576
0x61d8e4 satisfy_declaration_constraints
../../source/gcc/cp/constraint.cc:2594
0x61dbd8 constraint_satisfaction_value
../../source/gcc/cp/constraint.cc:2709
0x61dbd8 constraints_satisfied_p(tree_node*)
../../source/gcc/cp/constraint.cc:2730
0x671cb4 maybe_add_lambda_conv_op(tree_node*)
../../source/gcc/cp/lambda.c:1052
0x6f0d5f tsubst_lambda_expr(tree_node*, tree_node*, int, tree_node*)
../../source/gcc/cp/pt.c:18784
0x6f35d4 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
../../source/gcc/cp/pt.c:20154
0x6f228f tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
../../source/gcc/cp/pt.c:19404
0x6f228f tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
../../source/gcc/cp/pt.c:19404
0x6ecf8d tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
../../source/gcc/cp/pt.c:18814
0x6ecf8d tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
../../source/gcc/cp/pt.c:18472
0x6ee3b4 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
../../source/gcc/cp/pt.c:17558
0x6ee3b4 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
../../source/gcc/cp/pt.c:18454
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-662532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 09:57:36 2019
Return-Path: <gcc-bugs-return-662532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100941 invoked by alias); 6 Dec 2019 09:57: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 100900 invoked by uid 48); 6 Dec 2019 09:57:32 -0000
From: "sw6ueyz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92838] ICE (internal compiler error) calling lambda object with requires clause (in in dependent_type_p)
Date: Fri, 06 Dec 2019 09:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sw6ueyz 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-92838-4-oGl6LFzlgt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92838-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92838-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00602.txt.bz2
Content-length: 291
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92838
--- Comment #1 from sw6ueyz at gmail dot com ---
Sorry.. you need not add "-I/opt/wandbox/boost-1.71.0/gcc-head/include" in
command line (this code does not use any include files.. I just copied command
line from wandbox.org test bed)
>From gcc-bugs-return-662533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 10:10:36 2019
Return-Path: <gcc-bugs-return-662533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60669 invoked by alias); 6 Dec 2019 10:10: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 54882 invoked by uid 48); 6 Dec 2019 10:10:32 -0000
From: "fxue at os dot amperecomputing.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92839] New: Normalize memory address to same base in non-loop code
Date: Fri, 06 Dec 2019 10:10: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-92839-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00603.txt.bz2
Content-length: 1798
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92839
Bug ID: 92839
Summary: Normalize memory address to same base in non-loop code
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: ---
If possible, IVOPTs can transform memory accesses to make them use same base,
which can decrease register pressure in loop. But it does not handle memory
address that is not an iv, or in a pure non-loop code.
Consider the following example, compile with -O3, we can find that data[b + ?]
will use same base register. But if we remove the line "for (i = 0; i < n; i++,
b++)" to make it be non-loop code, data[b + ?] will use different bases, with
result that we have to consume 10 register as bases, which is a much higher
register pressure. And since live ranges of these base registers cross function
call, most of them will be spilled to memory.
int data[100];
int fn();
void foo(int b, int n)
{
int i;
for (i = 0; i < n; i++, b++) // remove the statement to be non-loop
{
data[b + 1] += 1;
data[b + 3] += 3;
data[b + 5] += 5;
data[b + 7] += 7;
data[b + 9] += 9;
data[b + 11] += 11;
data[b + 13] += 13;
data[b + 15] += 15;
data[b + 17] += 17;
data[b + 19] += 19;
fn ();
data[b + 1] -= 1;
data[b + 3] -= 3;
data[b + 5] -= 5;
data[b + 7] -= 7;
data[b + 9] -= 9;
data[b + 11] -= 11;
data[b + 15] -= 13;
data[b + 17] -= 15;
data[b + 19] -= 19;
}
}
>From gcc-bugs-return-662534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 10:18:25 2019
Return-Path: <gcc-bugs-return-662534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129140 invoked by alias); 6 Dec 2019 10:18: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 129081 invoked by uid 48); 6 Dec 2019 10:18:21 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92809] [10 regression] error: calls_comdat_local is set outside of a comdat group
Date: Fri, 06 Dec 2019 10:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92809-4-4JBVYLK9la@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92809-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92809-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00604.txt.bz2
Content-length: 594
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92809
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #3 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
This one works for me and should be fixed now by
2019-12-05 Jan Hubicka <hubicka@ucw.cz>
* ipa-inline-transform.c (inline_call): Fix maintenatnce of
comdat_local
>From gcc-bugs-return-662535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 10:25:34 2019
Return-Path: <gcc-bugs-return-662535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81661 invoked by alias); 6 Dec 2019 10:25: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 81614 invoked by uid 48); 6 Dec 2019 10:25:29 -0000
From: "andysem at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88101] Implement P0528R3, C++20 cmpxchg and padding bits
Date: Fri, 06 Dec 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: andysem at mail dot ru
X-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-88101-4-wrDtsnoSRR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00605.txt.bz2
Content-length: 1424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88101
andysem at mail dot ru changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andysem at mail dot ru
--- Comment #1 from andysem at mail dot ru ---
I'd like to draw attention to the case of 80-bit long double on x86. When I
added support for it in Boost.Atomic I noticed that it would usually be passed
in an xmm register, where the lower 10 bytes contained value and the upper 6
contained undefined padding. Given that gcc stores and loads the full xmm
register, this means that clearing the storage prior to storing the value is
not enough (the random padding will be stored in the storage and break
cmpxchg16b). In Boost.Atomic I had to clear the padding after storing the
value, and this code is brittle because I have to know when long double value
is 10 bytes (note that sizeof(long double) returns 16 on x86-64 and 12 on
x86-32).
I don't know if anything was done about it in recent gcc versions. Maybe the
compiler could provide an intrinsic to clear any possible padding bits of a
type? That would be useful not only for long double, but for structs with
padding bits, because it allows to use memcpy to copy the value (which is
arguably more efficient) and only clear padding when accepting the value from
the user.
>From gcc-bugs-return-662536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 10:35:01 2019
Return-Path: <gcc-bugs-return-662536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53579 invoked by alias); 6 Dec 2019 10:35: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 53529 invoked by uid 48); 6 Dec 2019 10:34:56 -0000
From: "lyberta at lyberta dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/85309] demangler failed with signal 11
Date: Fri, 06 Dec 2019 10:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lyberta at lyberta 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-85309-4-NowcknALIh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85309-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85309-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00606.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85309
Lyberta <lyberta at lyberta dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Lyberta <lyberta at lyberta dot net> ---
Yes. Doesn't crash anymore.
>From gcc-bugs-return-662538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 10:55:23 2019
Return-Path: <gcc-bugs-return-662538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23633 invoked by alias); 6 Dec 2019 10:55: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 23531 invoked by uid 55); 6 Dec 2019 10:55:17 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88827] Rejects valid program using &* operator combination.
Date: Fri, 06 Dec 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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon 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-88827-4-timJgtu8C3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88827-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88827-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00608.txt.bz2
Content-length: 774
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88827
--- Comment #3 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Author: clyon
Date: Fri Dec 6 10:54:46 2019
New Revision: 279039
URL: https://gcc.gnu.org/viewcvs?rev=279039&root=gcc&view=rev
Log:
[testsuite][aarch64] type_redef_11.c: Update expected diagnostics.
After the fix for PR c/36941 and PR c/88827 (r278976), this test emits
a different error message and needs an update.
2019-12-06 Christophe Lyon <christophe.lyon@linaro.org>
PR c/36941
PR c/88827
* gcc.target/aarch64/sve/acle/general-c/type_redef_11.c: Update
expected diagnostics.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.target/aarch64/sve/acle/general-c/type_redef_11.c
>From gcc-bugs-return-662537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 10:55:23 2019
Return-Path: <gcc-bugs-return-662537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23627 invoked by alias); 6 Dec 2019 10:55: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 23541 invoked by uid 55); 6 Dec 2019 10:55:19 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/36941] gcc does not reject invalid cast
Date: Fri, 06 Dec 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: unknown
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon 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-36941-4-R4ajDKkfAp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-36941-4@http.gcc.gnu.org/bugzilla/>
References: <bug-36941-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00607.txt.bz2
Content-length: 775
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36941
--- Comment #11 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Author: clyon
Date: Fri Dec 6 10:54:46 2019
New Revision: 279039
URL: https://gcc.gnu.org/viewcvs?rev=279039&root=gcc&view=rev
Log:
[testsuite][aarch64] type_redef_11.c: Update expected diagnostics.
After the fix for PR c/36941 and PR c/88827 (r278976), this test emits
a different error message and needs an update.
2019-12-06 Christophe Lyon <christophe.lyon@linaro.org>
PR c/36941
PR c/88827
* gcc.target/aarch64/sve/acle/general-c/type_redef_11.c: Update
expected diagnostics.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.target/aarch64/sve/acle/general-c/type_redef_11.c
>From gcc-bugs-return-662539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 11:04:14 2019
Return-Path: <gcc-bugs-return-662539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25732 invoked by alias); 6 Dec 2019 11:04: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 25665 invoked by uid 48); 6 Dec 2019 11:04:09 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92824] Wrong optimization: representation of long doubles not copied even with memcpy
Date: Fri, 06 Dec 2019 11:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92824-4-h4eUn3SWeA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00609.txt.bz2
Content-length: 1095
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92824
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
So
int main()
{
long double x;
// make x pseudo-denormal
x = 0;
unsigned char *px = (unsigned char *)&x;
px[7] = 0x80;
// set padding
px[10] = 0x80;
px[11] = 0x80;
px[12] = 0x80;
px[13] = 0x80;
px[14] = 0x80;
px[15] = 0x80;
__builtin_printf("%lf\n", x);
return 0;
}
shows we're constant folding this to
__builtin_printf ("%lf\n",
3.36210314311209350626267781732175260259807934484647124011e-4932);
now. When we put #pragma GCC unroll 16 before your testcases loop we
get the following (unrolling and constant folding happens after the
"bad" transform)
main ()
{
<bb 2> [local count: 82570746]:
printf ("%02x ", 128);
printf ("%02x ", 128);
printf ("%02x ", 0);
printf ("%02x ", 0);
printf ("%02x ", 128);
printf ("%02x ", 0);
printf ("%02x ", 0);
printf ("%02x ", 0);
printf ("%02x ", 0);
printf ("%02x ", 0);
printf ("%02x ", 0);
printf ("%02x ", 0);
__builtin_putchar (10);
return 0;
>From gcc-bugs-return-662540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 11:05:09 2019
Return-Path: <gcc-bugs-return-662540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27137 invoked by alias); 6 Dec 2019 11: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 27069 invoked by uid 48); 6 Dec 2019 11:05:04 -0000
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 2019 11:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jb at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-92836-4-oNrQttDiZ9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00610.txt.bz2
Content-length: 3573
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
Janne Blomqvist <jb at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jb at gcc dot gnu.org
--- Comment #5 from Janne Blomqvist <jb at gcc dot gnu.org> ---
(In reply to Andrew Benson from comment #1)
> Running with -fsanitize=thread (suggested by Tobias) gives:
>
> ==================
> WARNING: ThreadSanitizer: lock-order-inversion (potential deadlock)
> (pid=9982)
> Cycle in lock order graph: M26 (0x7f02bb31c340) => M84 (0x7b58002efee0) =>
> M26
>
> Mutex M84 acquired here while holding mutex M26 in thread T63:
> #0 pthread_mutex_lock
> ../../../../gcc-trunk/libsanitizer/sanitizer_common/
> sanitizer_common_interceptors.inc:4148 (libtsan.so.0+0x5095a)
> #1 __gthread_mutex_lock ../libgcc/gthr-default.h:749 (libgfortran.so.
> 5+0x1e25c9)
> #2 insert_unit ../../../gcc-trunk/libgfortran/io/unit.c:244
> (libgfortran.so.5+0x1e25c9)
> #3 gomp_thread_start ../../../gcc-trunk/libgomp/team.c:123 (libgomp.so.
> 1+0x198a5)
>
> Mutex M26 previously acquired by the same thread here:
> #0 pthread_mutex_lock
> ../../../../gcc-trunk/libsanitizer/sanitizer_common/
> sanitizer_common_interceptors.inc:4148 (libtsan.so.0+0x5095a)
> #1 __gthread_mutex_lock ../libgcc/gthr-default.h:749 (libgfortran.so.
> 5+0x1e265c)
> #2 get_gfc_unit ../../../gcc-trunk/libgfortran/io/unit.c:332
> (libgfortran.so.5+0x1e265c)
> #3 gomp_thread_start ../../../gcc-trunk/libgomp/team.c:123 (libgomp.so.
> 1+0x198a5)
>
> Mutex M26 acquired here while holding mutex M84 in thread T63:
> #0 pthread_mutex_lock
> ../../../../gcc-trunk/libsanitizer/sanitizer_common/
> sanitizer_common_interceptors.inc:4148 (libtsan.so.0+0x5095a)
> #1 __gthread_mutex_lock ../libgcc/gthr-default.h:749 (libgfortran.so.
> 5+0x1e336b)
> #2 close_unit_1 ../../../gcc-trunk/libgfortran/io/unit.c:735
> (libgfortran.so.5+0x1e336b)
> #3 gomp_thread_start ../../../gcc-trunk/libgomp/team.c:123 (libgomp.so.
> 1+0x198a5)
>
> Mutex M84 previously acquired by the same thread here:
> #0 pthread_mutex_trylock ../../../../gcc-trunk/libsanitizer/tsan/
> tsan_interceptors_posix.cpp:1246 (libtsan.so.0+0x4340a)
> #1 __gthread_mutex_trylock ../libgcc/gthr-default.h:758 (libgfortran.so.
> 5+0x1e26f1)
> #2 get_gfc_unit ../../../gcc-trunk/libgfortran/io/unit.c:380
> (libgfortran.so.5+0x1e26f1)
> #3 gomp_thread_start ../../../gcc-trunk/libgomp/team.c:123 (libgomp.so.
> 1+0x198a5)
>
> Thread T63 (tid=10047, running) created by main thread at:
> #0 pthread_create ../../../../gcc-trunk/libsanitizer/tsan/
> tsan_interceptors_posix.cpp:962 (libtsan.so.0+0x5bb22)
> #1 gomp_team_start ../../../gcc-trunk/libgomp/team.c:839 (libgomp.so.
> 1+0x19eba)
> #2 main <null> (a.out+0x400ef9)
>
> SUMMARY: ThreadSanitizer: lock-order-inversion (potential deadlock)
> ../libgcc/
> gthr-default.h:749 in __gthread_mutex_lock
> ==================
FWIW, this is a known problem (don't know if there's a PR for it). As far as
I've been able to see, the problem is that threadsanitizer cannot prove that
the unit locking scheme is correct even though it is.
Of course, it would be nice if we could redesign the locking so that
threadsanitizer would be happy, as then threadsanitizer would be more useful
for us.
>From gcc-bugs-return-662541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 11:08:58 2019
Return-Path: <gcc-bugs-return-662541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34639 invoked by alias); 6 Dec 2019 11:08: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 34493 invoked by uid 48); 6 Dec 2019 11:08:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92829] [10 regression] several test case failures starting with r278983
Date: Fri, 06 Dec 2019 11:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-92829-4-h5Xndx2sSy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00611.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92829
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-662542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 11:09:50 2019
Return-Path: <gcc-bugs-return-662542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36311 invoked by alias); 6 Dec 2019 11:09: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 36249 invoked by uid 48); 6 Dec 2019 11:09:46 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 2019 11:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92836-4-BazkTnyKJY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00612.txt.bz2
Content-length: 2308
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Andrew Benson from comment #1)
> Running with -fsanitize=thread (suggested by Tobias) gives:
> WARNING: ThreadSanitizer: lock-order-inversion (potential deadlock)
> (pid=9982)
> Mutex M84 acquired here while holding mutex M26 in thread T63:
> #2 insert_unit ../../../gcc-trunk/libgfortran/io/unit.c:244
>
> Mutex M26 previously acquired by the same thread here:
> #2 get_gfc_unit ../../../gcc-trunk/libgfortran/io/unit.c:332
I think this part is fine:
1. get_gfc_unit: Get global lock ("unit_lock").
2. Call insert_unit: Get lock in u->lock which is for a particular unit number.
3. get_gfc_unit: unlock global lock
(4. u->lock is unlocked at some later point.)
> Mutex M26 acquired here while holding mutex M84 in thread T63:
> #2 close_unit_1 ../../../gcc-trunk/libgfortran/io/unit.c:735
close_unit_1:
* Obtain global lock ("unit_lock") – that's line 735
* Unlock the unit-number-specific lock u->lock
* Unlock the global lock.
> Mutex M84 previously acquired by the same thread here:
> #2 get_gfc_unit ../../../gcc-trunk/libgfortran/io/unit.c:380
That's again in get_gfc_unit. Here, I am a bit unsure about the code – but I
have not spend a lot of time on the code:
1. Get global lock (unit_lock)
2. Unit has been found
3. Call the following, i.e. if the outer condition is true,
-> if the lock could not been obtained, unlock 'unit_lock' (to avoid a
deadlock) ? But still return 'p'
if (p != NULL && (p->child_dtio == 0))
{
/* Fast path. */
if (! TRYLOCK (&p->lock))
{
/* assert (p->closed == 0); */
UNLOCK (&unit_lock);
return p;
}
The TRYLOCK is the one in line 380.
This part looks a bit fishy. Shouldn't this be "if (TRYLOCK (...))"? Without
"!" – or do I miss something crucial?
https://www.kernel.org/doc/htmldocs/kernel-locking/API-mutex-trylock.html
>From gcc-bugs-return-662543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 11:10:28 2019
Return-Path: <gcc-bugs-return-662543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73097 invoked by alias); 6 Dec 2019 11: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 67337 invoked by uid 48); 6 Dec 2019 11:10:24 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92840] New: [OpenACC] Disallow 'acc_unmap_data' for everything other than 'acc_map_data'
Date: Fri, 06 Dec 2019 11:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00613.txt.bz2
Content-length: 912
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92840
Bug ID: 92840
Summary: [OpenACC] Disallow 'acc_unmap_data' for everything
other than 'acc_map_data'
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: openacc, patch
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: jakub at gcc dot gnu.org, jules at gcc dot gnu.org
Target Milestone: ---
OpenACC 2.6, 3.2.27. "acc_unmap_data" states that "It is undefined behavior to
call 'acc_unmap_data' with a host address unless that host address was mapped
to device memory using 'acc_map_data'. We're currently not checking that, but
it's easy enough to do (..., and uncovers some weirdness...).
WIP patch exists.
>From gcc-bugs-return-662544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 11:16:28 2019
Return-Path: <gcc-bugs-return-662544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9277 invoked by alias); 6 Dec 2019 11: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 3836 invoked by uid 48); 6 Dec 2019 11:16:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92831] CWG1299 extend_ref_init_temps_1 punts on COND_EXPRs
Date: Fri, 06 Dec 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: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92831-4-rn8IL6bWAE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00614.txt.bz2
Content-length: 254
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92831
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47434
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47434&action=edit
gcc10-pr92831.patch
Untested fix.
>From gcc-bugs-return-662545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 11:24:38 2019
Return-Path: <gcc-bugs-return-662545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17290 invoked by alias); 6 Dec 2019 11: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 17188 invoked by uid 48); 6 Dec 2019 11:24:34 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92834] misssed SLP vectorization in LightPixel
Date: Fri, 06 Dec 2019 11: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: 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-92834-4-TY5JGZXmlS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00615.txt.bz2
Content-length: 1544
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92834
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org,
| |rsandifo at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
t.C:260:16: missed: Build SLP failed: incompatible vector types for: patt_288
= (unsigned char) patt_290;
t.C:260:16: note: old vector type: vector(8) unsigned char
t.C:260:16: note: new vector type: vector(4) unsigned char
we're also re-trying for all vector sizes even though the above issue
will prevail.
But one of the main issues is likely that we don't pattern match
static inline unsigned umax(unsigned a, unsigned b) {
return a - ((a - b) & -(a < b));
}
static inline unsigned umin(unsigned a, unsigned b) {
return a - ((a - b) & -(a > b));
}
I wonder if they desperately searched for sth not handled by GCC ;)
Btw, my copy of clang (OK, 7.0...) doesn't vectorize the color.components[]
compute but only the leading three-component compute involving reverse
sqrt, not vectorized by us because we don't handle BB vectorization of
reductions. There's duplicate PRs about this.
Which part is important to vectorize?
Also - what flags did you use? (tried -Ofast -mavx2)
>From gcc-bugs-return-662546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 11:49:47 2019
Return-Path: <gcc-bugs-return-662546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81562 invoked by alias); 6 Dec 2019 11:49:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81502 invoked by uid 48); 6 Dec 2019 11:49:43 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 2019 11:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92836-4-OBfEpL1W4W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00616.txt.bz2
Content-length: 915
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
--- Comment #7 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Jerry DeLisle from comment #3)
> character(len=27) :: c
> Fortran runtime error: Fortran runtime error: End of recordEnd of record
This error I get because 27 characters are not enough — Otherwise, it works
here.
(In reply to Tobias Burnus from comment #6)
> This part looks a bit fishy. Shouldn't this be "if (TRYLOCK (...))"? Without
> "!" – or do I miss something crucial?
> https://www.kernel.org/doc/htmldocs/kernel-locking/API-mutex-trylock.html
In any case, with '!' removed, it seems to deadlock (running the c-length fixed
version of Jerry's code w/ the 'while' + 'end while' lines commented out).
Hence, it is either wrong in a more complicated way – or (likely) I simply
misunderstand how it is supposed to work – or both.
>From gcc-bugs-return-662547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 11:52:54 2019
Return-Path: <gcc-bugs-return-662547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85325 invoked by alias); 6 Dec 2019 11:52: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 85288 invoked by uid 48); 6 Dec 2019 11:52:50 -0000
From: "bp at alien8 dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92841] New: Optimize -fstack-protector-strong code generation a bit
Date: Fri, 06 Dec 2019 11:52: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: bp at alien8 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-92841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00617.txt.bz2
Content-length: 1489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841
Bug ID: 92841
Summary: Optimize -fstack-protector-strong code generation a
bit
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: bp at alien8 dot de
Target Milestone: ---
Created attachment 47435
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47435&action=edit
prepocessed source
Hi,
I'm building the linux kernel with
gcc (Debian 9.2.1-8) 9.2.1 20190909
and -fstack-protector-strong on x86 and from looking at what it generates, it
could be optimized a little:
# arch/x86/kernel/cpu/scattered.c:48: {
movq %gs:40, %rax # MEM[(<address-space-2> long unsigned int
*)40B], tmp125
movq %rax, 16(%rsp) # tmp125, D.21425
xorl %eax, %eax # tmp125
movl $6, %eax #, pretmp_35
jmp .L6 #
AFAICT, the stack protector part would load the canary value from the %gs
offset and use a temp register to stick it on the stack and then clear that
temp register, %rax in this case.
As part of further function processing, it would stick a value in that same
register, which makes the previous clearing superfluous.
I'm being told this could be taken care of in a "late peephole". :)
Attaching preprocessed source.
Thx.
>From gcc-bugs-return-662548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 11:56:34 2019
Return-Path: <gcc-bugs-return-662548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4155 invoked by alias); 6 Dec 2019 11:56: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 128212 invoked by uid 48); 6 Dec 2019 11:56:29 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Fri, 06 Dec 2019 11:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92820-4-nYkSk3VqdD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00618.txt.bz2
Content-length: 411
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
--- Comment #10 from Matthias Klose <doko at debian dot org> ---
that fixes it ...
--- libgo/runtime/go-context.S (revision 279039)
+++ libgo/runtime/go-context.S (working copy)
@@ -71,4 +71,8 @@
#endif
+#if defined(__ARM_EABI__)
+ .section .note.GNU-stack,"",%progbits
+#else
.section .note.GNU-stack,"",@progbits
+#endif
>From gcc-bugs-return-662549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 12:00:44 2019
Return-Path: <gcc-bugs-return-662549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24240 invoked by alias); 6 Dec 2019 12: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 24086 invoked by uid 48); 6 Dec 2019 12:00:38 -0000
From: "doko at ubuntu dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92842] New: [10 Regression] libgo build failure on i686-gnu
Date: Fri, 06 Dec 2019 12:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at ubuntu dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92842-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00619.txt.bz2
Content-length: 1800
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92842
Bug ID: 92842
Summary: [10 Regression] libgo build failure on i686-gnu
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: doko at ubuntu dot com
CC: cmang at google dot com
Target Milestone: ---
trunk 20191205 ftbfs on the Hurd, i686-gnu:
./../../src/libgo/go/runtime/os_hurd.go:42:7: error: reference to undefined
field or method 'mos'
42 | if mp.mos.waitsema != 0 {
| ^
../../../src/libgo/go/runtime/os_hurd.go:55:4: error: reference to undefined
field or method 'mos'
55 | mp.mos.waitsema = uintptr(unsafe.Pointer(sem))
| ^
../../../src/libgo/go/runtime/os_hurd.go:65:48: error: reference to undefined
field or method 'mos'
65 | if sem_timedwait((*_sem_t)(unsafe.Pointer(_m_.mos.waitsema)), &ts) !=
0 {
| ^
../../../src/libgo/go/runtime/os_hurd.go:75:46: error: reference to undefined
field or method 'mos'
75 | r1 := sem_wait((*_sem_t)(unsafe.Pointer(_m_.mos.waitsema)))
| ^
../../../src/libgo/go/runtime/os_hurd.go:89:41: error: reference to undefined
field or method 'mos'
89 | if sem_post((*_sem_t)(unsafe.Pointer(mp.mos.waitsema))) != 0 {
| ^
../../../src/libgo/go/runtime/os_hurd.go:95:21: error: reference to undefined
name '_SC_NPROCESSORS_ONLN'
95 | n := int32(sysconf(_SC_NPROCESSORS_ONLN))
| ^
Makefile:2836: recipe for target 'runtime.lo' failed
make[6]: *** [runtime.lo] Error 1
>From gcc-bugs-return-662550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 12:23:46 2019
Return-Path: <gcc-bugs-return-662550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122269 invoked by alias); 6 Dec 2019 12:23: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 122217 invoked by uid 48); 6 Dec 2019 12:23:40 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92775] [8/9/10 Regression] Incorrect expression in DW_AT_byte_stride on an array
Date: Fri, 06 Dec 2019 12:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus 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: cc
Message-ID: <bug-92775-4-auxoUogZRW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00620.txt.bz2
Content-length: 460
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92775
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Posted patch by Jakub:
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00395.html
>From gcc-bugs-return-662551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 12:25:19 2019
Return-Path: <gcc-bugs-return-662551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125482 invoked by alias); 6 Dec 2019 12:25: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 125255 invoked by uid 48); 6 Dec 2019 12:25:15 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBmb3J0cmFuLzkyNzkzXSBGb3J0cmFuIExvY2F0aW9uIERhdGEgZm9y?= =?UTF-8?B?IERpYWdub3N0aWMgbGFja3MgdGhlIGNvbHVtbiBudW1iZXIg4oCTIHdoZW4g?= =?UTF-8?B?cGFzc2luZyBvbiB0byBNRQ==?Date: Fri, 06 Dec 2019 12:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92793-4-PyA6xIapMN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92793-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00621.txt.bz2
Content-length: 184
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92793
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00207.html
>From gcc-bugs-return-662552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 12:31:50 2019
Return-Path: <gcc-bugs-return-662552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7128 invoked by alias); 6 Dec 2019 12:31: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 7006 invoked by uid 48); 6 Dec 2019 12:31:43 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92834] misssed SLP vectorization in LightPixel
Date: Fri, 06 Dec 2019 12: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: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92834-4-QiGCUabfx4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00622.txt.bz2
Content-length: 3341
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92834
--- Comment #2 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Created attachment 47436
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47436&action=edit
Clang assembly from perf
It is clang9 build
https://treeherder.mozilla.org/#/jobs?repo=try&revision=7d7ee02817ab1ea39a6415862ab7889f5e416598&selectedJob=278948829
it has full logs and binary, too
/builds/worker/fetches/sccache/sccache /builds/worker/fetches/clang/bin/clang++
-o Unified_cpp_gfx_2d2.o -c -flto=thin
-I/builds/worker/workspace/build/src/obj-firefox/dist/system_wrappers -include
/builds/worker/workspace/build/src/config/gcc_hidden.h -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=2 -fstack-protector-strong -DMOZILLA_CLIENT -include
/builds/worker/workspace/build/src/obj-firefox/mozilla-config.h
-Qunused-arguments -Qunused-arguments -Wall -Wbitfield-enum-conversion
-Wempty-body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith
-Wshadow-field-in-constructor-modified -Wsign-compare -Wtype-limits
-Wunreachable-code -Wunreachable-code-return -Wwrite-strings
-Wno-invalid-offsetof -Wclass-varargs -Wfloat-overflow-conversion
-Wfloat-zero-conversion -Wloop-analysis -Wc++1z-compat -Wc++2a-compat -Wcomma
-Wimplicit-fallthrough -Werror=non-literal-null-conversion -Wstring-conversion
-Wtautological-overlap-compare -Wtautological-unsigned-enum-zero-compare
-Wtautological-unsigned-zero-compare -Wno-error=tautological-type-limit-compare
-Wno-inline-new-delete -Wno-error=type-limits -Wno-error=pessimizing-move
-Wno-error=nonnull -Wno-error=deprecated-declarations -Wno-error=array-bounds
-Wno-error=backend-plugin -Wno-error=return-std-move
-Wno-error=atomic-alignment -Wformat -Wformat-security
-Wno-gnu-zero-variadic-macro-arguments -Wno-unknown-warning-option
-Wno-return-type-c-linkage -D_GLIBCXX_USE_CXX11_ABI=0 -fno-sized-deallocation
-fno-aligned-new -fcrash-diagnostics-dir=/builds/worker/artifacts
-fno-strict-aliasing -fno-strict-aliasing -fno-exceptions -fno-rtti
-fno-exceptions -fno-math-errno -pthread -pipe
-I/builds/worker/workspace/build/src/obj-firefox/dist/stl_wrappers -DNDEBUG=1
-DTRIMMED=1 -DUSE_SSE2 -DOS_POSIX=1 -DOS_LINUX=1 -DUSE_CAIRO
-DMOZ2D_HAS_MOZ_CAIRO -DMOZ_ENABLE_FREETYPE -DSTATIC_EXPORTABLE_JS_API
-DMOZ_HAS_MOZGLUE -DMOZILLA_INTERNAL_API -DIMPL_LIBXUL
-I/builds/worker/workspace/build/src/gfx/2d
-I/builds/worker/workspace/build/src/obj-firefox/gfx/2d
-I/builds/worker/workspace/build/src/obj-firefox/ipc/ipdl/_ipdlheaders
-I/builds/worker/workspace/build/src/ipc/chromium/src
-I/builds/worker/workspace/build/src/ipc/glue
-I/builds/worker/workspace/build/src/gfx/skia
-I/builds/worker/workspace/build/src/gfx/skia/skia
-I/builds/worker/workspace/build/src/obj-firefox/dist/include
-I/builds/worker/workspace/build/src/obj-firefox/dist/include/nspr
-I/builds/worker/workspace/build/src/obj-firefox/dist/include/nss -fPIC -g
-Xclang -load -Xclang
/builds/worker/workspace/build/src/obj-firefox/build/clang-plugin/libclang-plugin.so
-Xclang -add-plugin -Xclang moz-check -O2 -fno-omit-frame-pointer
-funwind-tables -Werror -Wno-error=shadow
-I/builds/worker/workspace/build/src/obj-firefox/dist/include/cairo
-I/usr/include/freetype2 -MD -MP -MF .deps/Unified_cpp_gfx_2d2.o.pp
Unified_cpp_gfx_2d2.cpp
>From gcc-bugs-return-662553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 13:21:32 2019
Return-Path: <gcc-bugs-return-662553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77735 invoked by alias); 6 Dec 2019 13: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 71825 invoked by uid 48); 6 Dec 2019 13:21:28 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 2019 13: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92836-4-Pp0pK8U6EU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00623.txt.bz2
Content-length: 1317
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #8 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
> No. The inquire() is used only to see if the file exists already. If it
> does, the code branches to read the file, if it does not, the code branches
> to generate the data for the file and then write it.
You have to watch out here.
If you are
a) using INQUIRE to check if the file exists
b) using OPEN if it does not
in a thread, this is classic race condition - separate threads
may INQUIRE and then try to open, in parallel. This is not atomic,
and is a classic race condition.
You should always put such a sequence into OMP CRITICAL. This has
the nice side effect that you will also avoid this bug (which should
be fixed regardless).
Also, why do you use inquire at all? AFAIK, it is not an error
to OPEN a file more than one if you don't change anything, so
a simple
open (10,file="foo.dat",status="unknown")
should, in principle, work even with OpenMP; if it doesn't, this is
another bug that needs fixing.
>From gcc-bugs-return-662554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 13:29:37 2019
Return-Path: <gcc-bugs-return-662554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55796 invoked by alias); 6 Dec 2019 13:29: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 55699 invoked by uid 55); 6 Dec 2019 13:29:30 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92775] [8/9/10 Regression] Incorrect expression in DW_AT_byte_stride on an array
Date: Fri, 06 Dec 2019 13:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92775-4-uaDYfC2Fwd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00624.txt.bz2
Content-length: 1062
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92775
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Dec 6 13:28:59 2019
New Revision: 279045
URL: https://gcc.gnu.org/viewcvs?rev=279045&root=gcc&view=rev
Log:
PR fortran/92775
* trans.h (struct lang_type, struct lang_decl): Remove span member.
(GFC_DECL_SPAN, GFC_TYPE_ARRAY_SPAN): Remove macros.
* trans-array.h (gfc_get_descriptor_offsets_for_info): Add another
argument.
* trans-array.c (gfc_get_descriptor_offsets_for_info): Add SPAN_OFF
argument and initialize *SPAN_OFF to the offset of span field.
* trans-types.c (gfc_get_array_descr_info): Adjust
gfc_get_descriptor_offsets_for_info caller. Compute elem_size
as base->span instead of TYPE_SIZE_UNIT (etype) constant.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/fortran/trans-array.h
trunk/gcc/fortran/trans-types.c
trunk/gcc/fortran/trans.h
>From gcc-bugs-return-662555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 13:38:33 2019
Return-Path: <gcc-bugs-return-662555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5173 invoked by alias); 6 Dec 2019 13:38: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 5065 invoked by uid 48); 6 Dec 2019 13:38:28 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92843] New: [OpenACC] Disallow 'acc_delete' etc. for everything without a dynamic reference count
Date: Fri, 06 Dec 2019 13:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00625.txt.bz2
Content-length: 698
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92843
Bug ID: 92843
Summary: [OpenACC] Disallow 'acc_delete' etc. for everything
without a dynamic reference count
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: openacc, patch
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: jakub at gcc dot gnu.org, jules at gcc dot gnu.org
Target Milestone: ---
..., which seems easy enough to implement (..., and uncovers some
weirdness...).
WIP patch exists.
>From gcc-bugs-return-662556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 14:16:10 2019
Return-Path: <gcc-bugs-return-662556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80691 invoked by alias); 6 Dec 2019 14:16:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80472 invoked by uid 48); 6 Dec 2019 14:16:02 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92844] New: [10 regression] libgomp.fortran/use_device_ptr-optional-2.f90 fails after r279004
Date: Fri, 06 Dec 2019 14:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 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 cc target_milestone
Message-ID: <bug-92844-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00626.txt.bz2
Content-length: 5689
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92844
Bug ID: 92844
Summary: [10 regression]
libgomp.fortran/use_device_ptr-optional-2.f90 fails
after r279004
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
Executing on host: /home/seurer/gcc/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/build/gcc-test/gcc/
/home/seurer/gcc/gcc-test/libgomp/testsuite/libgomp.fortran/use_device_ptr-optional-2.f90
-B/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/
-B/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/.libs
-I/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp
-I/home/seurer/gcc/gcc-test/libgomp/testsuite/../../include
-I/home/seurer/gcc/gcc-test/libgomp/testsuite/.. -fmessage-length=0
-fno-diagnostics-show-caret -Wno-hsa -fdiagnostics-color=never -fopenmp
-B/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/../libquadmath/.libs/
-O
-B/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/../libgfortran/.libs
-fintrinsic-modules-path=/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp
-L/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/../libquadmath/.libs/
-L/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/../libgfortran/.libs
-lgfortran -foffload=-lgfortran -lquadmath -lm -o
./use_device_ptr-optional-2.exe (timeout = 300)
spawn -ignore SIGHUP /home/seurer/gcc/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/build/gcc-test/gcc/
/home/seurer/gcc/gcc-test/libgomp/testsuite/libgomp.fortran/use_device_ptr-optional-2.f90
-B/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/
-B/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/.libs
-I/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp
-I/home/seurer/gcc/gcc-test/libgomp/testsuite/../../include
-I/home/seurer/gcc/gcc-test/libgomp/testsuite/.. -fmessage-length=0
-fno-diagnostics-show-caret -Wno-hsa -fdiagnostics-color=never -fopenmp
-B/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/../libquadmath/.libs/
-O
-B/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/../libgfortran/.libs
-fintrinsic-modules-path=/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp
-L/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/../libquadmath/.libs/
-L/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/../libgfortran/.libs
-lgfortran -foffload=-lgfortran -lquadmath -lm -o
./use_device_ptr-optional-2.exe
PASS: libgomp.fortran/use_device_ptr-optional-2.f90 -O (test for excess
errors)
Setting LD_LIBRARY_PATH to
.:/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/.libs:/home/seurer/gcc/build/gcc-test/gcc:/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/../libgfortran/.libs:/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/../libquadmath/.libs:.:/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/.libs:/home/seurer/gcc/build/gcc-test/gcc:/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/../libgfortran/.libs:/home/seurer/gcc/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgomp/../libquadmath/.libs:/home/seurer/gcc/build/gcc-test/./gmp/.libs:/home/seurer/gcc/build/gcc-test/./prev-gmp/.libs:/home/seurer/gcc/build/gcc-test/./mpfr/src/.libs:/home/seurer/gcc/build/gcc-test/./prev-mpfr/src/.libs:/home/seurer/gcc/build/gcc-test/./mpc/src/.libs:/home/seurer/gcc/build/gcc-test/./prev-mpc/src/.libs:/home/seurer/gcc/build/gcc-test/./isl/.libs:/home/seurer/gcc/build/gcc-test/./prev-isl/.libs:/home/seurer/gcc/install/gcc-7.4.0/lib64
Execution timeout is: 300
spawn [open ...]
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x3fffa38a04d7 in ???
#1 0x3fffa2ff38c8 in ???
FAIL: libgomp.fortran/use_device_ptr-optional-2.f90 -O execution test
testcase
/home/seurer/gcc/gcc-test/libgomp/testsuite/libgomp.fortran/fortran.exp
completed in 0 seconds
Trying it in gdb (compiled without -O and with -g) I see:
(gdb) run
Starting program: /home/seurer/gcc/build/gcc-test/use_device_ptr-optional-2.exe
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/powerpc64le-linux-gnu/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x00000000100014ec in main (argc=<error reading variable: Cannot access memory
at address 0x20>, argv=<error reading variable: Cannot access memory at address
0x28>)
at
/home/seurer/gcc/gcc-test/libgomp/testsuite/libgomp.fortran/use_device_ptr-optional-2.f90:6
6 call foo()
(gdb) where
#0 0x00000000100014ec in main (argc=<error reading variable: Cannot access
memory at address 0x20>, argv=<error reading variable: Cannot access memory at
address 0x28>)
at
/home/seurer/gcc/gcc-test/libgomp/testsuite/libgomp.fortran/use_device_ptr-optional-2.f90:6
Backtrace stopped: Cannot access memory at address 0x50
>From gcc-bugs-return-662557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 14:25:32 2019
Return-Path: <gcc-bugs-return-662557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106737 invoked by alias); 6 Dec 2019 14: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 106624 invoked by uid 48); 6 Dec 2019 14:25:28 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92843] [OpenACC] Disallow 'acc_delete' etc. for everything without a dynamic reference count
Date: Fri, 06 Dec 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on see_also assigned_to everconfirmed
Message-ID: <bug-92843-4-sqpWSYcWru@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00627.txt.bz2
Content-length: 1886
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92843
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-06
See Also| |https://github.com/OpenACC/
| |openacc-spec/issues/246
Assignee|unassigned at gcc dot gnu.org |jules at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Julian, please verify the following against your understanding of OpenACC 2.6
semantics.
I had assumed that that 'acc_delete'/'#pragma acc exit data delete'/etc. should
not be permitted on '#pragma acc declare'd data, and should not be permitted
after 'acc_map_data'. (Which in GCC are those using REFCOUNT_INFINITY', so
that's easy to detect.)
But, I'm not sure now, after thinking through the following. ;-\
Because: per my reading, it actually is permissible to call 'acc_delete'/etc.
(dynamic reference counter; "present decrement" action) inside '#pragma acc
data' (structured reference counter). This "decrements the [...] dynamic
reference counter for 'var', if its value is greater than zero. If the
reference counter is already zero, its value is left unchanged". The latter
applies here. "If both reference counters are then zero, a delete action is
performed." The structured reference counter is left untouched by
'acc_delete', so the data remains mapped; 'acc_delete' actually is a no-op?
#define N 23
float h[N];
#pragma acc data create(h)
{
acc_delete(&h, 92); // no-op
// 'h' remains mapped!
}
>From gcc-bugs-return-662558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 14:38:08 2019
Return-Path: <gcc-bugs-return-662558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22309 invoked by alias); 6 Dec 2019 14:38: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 22250 invoked by uid 48); 6 Dec 2019 14:38:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92834] misssed SLP vectorization in LightPixel
Date: Fri, 06 Dec 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: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92834-4-XJCQSBkW2h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00628.txt.bz2
Content-length: 371
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92834
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47437
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47437&action=edit
gcc10-pr92834.patch
This untested patch just undoes the fancy way of writing blend operation and
turns it into ?: that we are able to optimize better.
>From gcc-bugs-return-662559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 14:41:16 2019
Return-Path: <gcc-bugs-return-662559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24953 invoked by alias); 6 Dec 2019 14:41:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24832 invoked by uid 48); 6 Dec 2019 14:41:09 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92844] [10 regression] libgomp.fortran/use_device_ptr-optional-2.f90 fails after r279004
Date: Fri, 06 Dec 2019 14:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92844-4-E8zaxgHPjQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92844-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92844-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00629.txt.bz2
Content-length: 449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92844
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
I think that is or could be a duplicate of PR 92305. See esp. PR 92305 comment
8 (and following) and PR 92305 comment 16.
At least both use type(c_ptr) and optional. I think it makes sense to fix PR
92305 first before digging into this issue, in case it is the same issue.
Any debugging help with PR 92305 is highly welcome.
>From gcc-bugs-return-662560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 14:47:53 2019
Return-Path: <gcc-bugs-return-662560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42120 invoked by alias); 6 Dec 2019 14: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 42052 invoked by uid 48); 6 Dec 2019 14:47:48 -0000
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 2019 14:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jb at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92836-4-e9SavD7Clw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00630.txt.bz2
Content-length: 1509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
--- Comment #9 from Janne Blomqvist <jb at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #8)
> > No. The inquire() is used only to see if the file exists already. If it
> > does, the code branches to read the file, if it does not, the code branches
> > to generate the data for the file and then write it.
>
> You have to watch out here.
>
> If you are
>
> a) using INQUIRE to check if the file exists
>
> b) using OPEN if it does not
>
> in a thread, this is classic race condition - separate threads
> may INQUIRE and then try to open, in parallel. This is not atomic,
> and is a classic race condition.
>
> You should always put such a sequence into OMP CRITICAL. This has
> the nice side effect that you will also avoid this bug (which should
> be fixed regardless).
>
> Also, why do you use inquire at all? AFAIK, it is not an error
> to OPEN a file more than one if you don't change anything, so
> a simple
>
> open (10,file="foo.dat",status="unknown")
>
> should, in principle, work even with OpenMP; if it doesn't, this is
> another bug that needs fixing.
The best way in cases like this is usually to skip the inquire, try to open the
file with a suitable value for status=, and if the open fails handle the error.
That avoids the race condition.
That being said, like you say, this is still a case that GFortran should handle
without crashing, so yes it's a bug that should be fixed.
>From gcc-bugs-return-662561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 14:51:33 2019
Return-Path: <gcc-bugs-return-662561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48383 invoked by alias); 6 Dec 2019 14:51: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 48299 invoked by uid 48); 6 Dec 2019 14:51:30 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92784] [10 regression] ICE when compiling g++.dg/torture/pr59226.C after r278944
Date: Fri, 06 Dec 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: other
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: 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-92784-4-py0iWu3ALO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92784-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92784-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00631.txt.bz2
Content-length: 225
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92784
--- Comment #3 from seurer at gcc dot gnu.org ---
Could be the same thing. Perhaps you can check what changed with this revision
to start this particular test failing.
>From gcc-bugs-return-662562-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 15:13:16 2019
Return-Path: <gcc-bugs-return-662562-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106760 invoked by alias); 6 Dec 2019 15:13: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 106701 invoked by uid 48); 6 Dec 2019 15:13:11 -0000
From: "abensonca at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 2019 15:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: abensonca 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-92836-4-yIY2ykBn1D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00632.txt.bz2
Content-length: 2314
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
--- Comment #10 from Andrew Benson <abensonca at gmail dot com> ---
(In reply to Thomas Koenig from comment #8)
> > No. The inquire() is used only to see if the file exists already. If it
> > does, the code branches to read the file, if it does not, the code branches
> > to generate the data for the file and then write it.
>
> You have to watch out here.
>
> If you are
>
> a) using INQUIRE to check if the file exists
>
> b) using OPEN if it does not
>
> in a thread, this is classic race condition - separate threads
> may INQUIRE and then try to open, in parallel. This is not atomic,
> and is a classic race condition.
>
> You should always put such a sequence into OMP CRITICAL. This has
> the nice side effect that you will also avoid this bug (which should
> be fixed regardless).
It's actually doing a sequence like this:
1) INQUIRE to test for the existence of the file; assuming it does not exist
then:
2) Synchronize access to the file using an OMP CRITICAL section, and a file
lock (the file lock being necessary as this is running with MPI so there are
multiple processes than can be attempting to access the file);
3) INQUIRE again to test the existence of the file (since it's possible that it
just happened to have been created by another thread)
4) Generate data to be written to the file;
5) Open, write, and close the file.
6) Exit the OPENMP CRITICAL section and release the file lock.
This clearly allows multiple threads to INQUIRE in parallel, but I don't think
it allows any race condition on the OPEN. If I'm wrong about that though then I
should fix my code!
> Also, why do you use inquire at all? AFAIK, it is not an error
> to OPEN a file more than one if you don't change anything, so
> a simple
>
> open (10,file="foo.dat",status="unknown")
>
> should, in principle, work even with OpenMP; if it doesn't, this is
> another bug that needs fixing.
I haven't tried this. Are you suggesting this as an alternative to using
INQUIRE? My reasoning for using INQUIRE to check the existence of the file is
that if it doesn't exist I want one thread to proceed to create the data for
the file (and actually that thread will then spawn another set of nested OpenMP
threads to do that work).
>From gcc-bugs-return-662563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 15:19:44 2019
Return-Path: <gcc-bugs-return-662563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121752 invoked by alias); 6 Dec 2019 15: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 121687 invoked by uid 48); 6 Dec 2019 15:19:40 -0000
From: "marc at kdab dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvNTk0MjNdIE1pc2xlYWRpbmcgd2FybmluZyB3aGVuICdlbnVt?= =?UTF-8?B?IGNsYXNzJyBiYXNlIHR5cGUgdW5yZXNvbHZlZDogZWxhYm9yYXRlZC10eXBl?= =?UTF-8?B?LXNwZWNpZmllciBmb3IgYSBzY29wZWQgZW51bSBtdXN0IG5vdCB1c2UgdGhl?= =?UTF-8?B?IOKAmGNsYXNz4oCZIGtleXdvcmQ=?Date: Fri, 06 Dec 2019 15:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marc at kdab 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-59423-4-Y2Lz8K0Fi2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59423-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59423-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00633.txt.bz2
Content-length: 939
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59423
marc at kdab dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marc at kdab dot com
--- Comment #2 from marc at kdab dot com ---
Still in GCC 10. The error message and surrounding warning are pointing at
everything _but_ where the error is:
<source>:1:6: warning: elaborated-type-specifier for a scoped enum must not use
the 'class' keyword
1 | enum class IntegerSystem : int8 {};
| ~~~~ ^~~~~
| -----
<source>:1:12: error: use of enum 'IntegerSystem' without previous declaration
1 | enum class IntegerSystem : int8 {};
| ^~~~~~~~~~~~~
<source>:1:26: error: expected unqualified-id before ':' token
1 | enum class IntegerSystem : int8 {};
| ^
>From gcc-bugs-return-662564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 15:21:44 2019
Return-Path: <gcc-bugs-return-662564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123715 invoked by alias); 6 Dec 2019 15:21: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 123666 invoked by uid 48); 6 Dec 2019 15:21:40 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92843] [OpenACC] Disallow 'acc_delete' etc. for everything without a dynamic reference count
Date: Fri, 06 Dec 2019 15:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92843-4-pgVqOg0u3E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00634.txt.bz2
Content-length: 797
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92843
--- Comment #2 from jules at gcc dot gnu.org ---
I don't think your example is valid, but I'm not sure it will be fail in quite
the right way with the current version of my refcount overhaul patch. Actually
I think the acc_map_data implementation using REFCOUNT_INFINITY is probably
wrong too.
I will try changing the implementation as follows:
- calls to acc_delete with the structured reference count being non-zero (or
infinity in the case of '#pragma acc declare'd data) should raise an error.
- acc_map_data should use GOMP_MAP_VARS_OPENACC_ENTER_DATA instead of forcing
the refcount to infinity (i.e., making the behaviour the same as "enter data
(create)").
Does that match your understanding of what the behaviour should be?
>From gcc-bugs-return-662565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 15:47:41 2019
Return-Path: <gcc-bugs-return-662565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100692 invoked by alias); 6 Dec 2019 15: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 100621 invoked by uid 48); 6 Dec 2019 15:47:36 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 2019 15:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92836-4-xGxoiF84C9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00635.txt.bz2
Content-length: 2332
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
--- Comment #11 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Andrew Benson from comment #10)
> (In reply to Thomas Koenig from comment #8)
> > Also, why do you use inquire at all? AFAIK, it is not an error
> > to OPEN a file more than one if you don't change anything, so
> > a simple
> >
> > open (10,file="foo.dat",status="unknown")
> >
> > should, in principle, work even with OpenMP; if it doesn't, this is
> > another bug that needs fixing.
>
> I haven't tried this. Are you suggesting this as an alternative to using
> INQUIRE?
That is the idea.
> My reasoning for using INQUIRE to check the existence of the file
> is that if it doesn't exist I want one thread to proceed to create the data
> for the file (and actually that thread will then spawn another set of nested
> OpenMP threads to do that work).
If you look at 12.5.6.1 in F2018, you will find
If the file to be connected to the unit is the same as the file to which the
unit is connected, a new connection is not
established and values for any changeable modes (12.5.2) specified come into
effect for the established connection;
the current file position is unaffected. Before any effect on changeable modes,
a wait operation is performed for
any pending asynchronous data transfer operations for the specified unit. If
the POSITION= specifier appears
in such an OPEN statement, the value specified shall not disagree with the
current position of the file. If the
STATUS= specifier is included in such an OPEN statement, it shall be specified
with the value OLD. Other than
ERR=, IOSTAT=, and IOMSG=, and the changeable modes, the values of all other
specifiers in such an OPEN
statement shall not differ from those in effect for the established connection.
... so my example was actually not quite correct, because the
STATUS was wrong.
However, in order to to do what you describe, maybe an explicit variable
to hold the file number (or flag) may be better, like this, with
access guarded by OMP CRITICAL:
integer :: file_num = -1
!$omp parallel
...
!$omp critical
if (file_num < 0) then
open (newunit = file_num, file="foo.dat")
! Do a lot of other stuff
end if
!$omp end critical
! file_num contains something valid here
>From gcc-bugs-return-662566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 15:51:45 2019
Return-Path: <gcc-bugs-return-662566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6860 invoked by alias); 6 Dec 2019 15:51:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6802 invoked by uid 48); 6 Dec 2019 15:51:41 -0000
From: "abensonca at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 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: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: abensonca 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-92836-4-2Z1StMYkuW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00636.txt.bz2
Content-length: 2116
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
--- Comment #12 from Andrew Benson <abensonca at gmail dot com> ---
(In reply to Thomas Koenig from comment #11)
> (In reply to Andrew Benson from comment #10)
> > (In reply to Thomas Koenig from comment #8)
> > My reasoning for using INQUIRE to check the existence of the file
> > is that if it doesn't exist I want one thread to proceed to create the data
> > for the file (and actually that thread will then spawn another set of nested
> > OpenMP threads to do that work).
>
> If you look at 12.5.6.1 in F2018, you will find
>
> If the file to be connected to the unit is the same as the file to which the
> unit is connected, a new connection is not
> established and values for any changeable modes (12.5.2) specified come into
> effect for the established connection;
> the current file position is unaffected. Before any effect on changeable
> modes, a wait operation is performed for
> any pending asynchronous data transfer operations for the specified unit. If
> the POSITION= specifier appears
> in such an OPEN statement, the value specified shall not disagree with the
> current position of the file. If the
> STATUS= specifier is included in such an OPEN statement, it shall be
> specified with the value OLD. Other than
> ERR=, IOSTAT=, and IOMSG=, and the changeable modes, the values of all other
> specifiers in such an OPEN
> statement shall not differ from those in effect for the established
> connection.
>
> ... so my example was actually not quite correct, because the
> STATUS was wrong.
>
> However, in order to to do what you describe, maybe an explicit variable
> to hold the file number (or flag) may be better, like this, with
> access guarded by OMP CRITICAL:
>
> integer :: file_num = -1
>
> !$omp parallel
>
> ...
>
> !$omp critical
> if (file_num < 0) then
> open (newunit = file_num, file="foo.dat")
> ! Do a lot of other stuff
> end if
> !$omp end critical
> ! file_num contains something valid here
That seems like a good approach - thanks for the suggestion!
>From gcc-bugs-return-662567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 16:10:04 2019
Return-Path: <gcc-bugs-return-662567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45278 invoked by alias); 6 Dec 2019 16:10: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 45176 invoked by uid 48); 6 Dec 2019 16:09:59 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92841] Optimize -fstack-protector-strong code generation a bit
Date: Fri, 06 Dec 2019 16:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
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-92841-4-zLqRkP6PZm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00637.txt.bz2
Content-length: 1835
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |law at gcc dot gnu.org,
| |uros at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The reason for the xor is increased security, shorten the lifetime of the
dangerous value in a register as much as possible, so that e.g. signal handlers
or whatever else don't spill it somewhere from where an exploit could pick it
up.
The xor is done intentionally in the same pattern, so it is never split.
The pattern looks like:
(define_insn "@stack_protect_set_1_<mode>"
[(set (match_operand:PTR 0 "memory_operand" "=m")
(unspec:PTR [(match_operand:PTR 1 "memory_operand" "m")]
UNSPEC_SP_SET))
(set (match_scratch:PTR 2 "=&r") (const_int 0))
(clobber (reg:CC FLAGS_REG))]
""
"mov{<imodesuffix>}\t{%1, %2|%2, %1}\;mov{<imodesuffix>}\t{%2, %0|%0,
%2}\;xor{l}\t%k2, %k2"
[(set_attr "type" "multi")])
So, without compromising security, the only thing that could be done is add
pattern which would be similar to the above, except that it would use
match_operand instead of match_scratch for the second set and would use some
input operand which could say be another GPR or a constant and perhaps could
use a mode other than PTR if needed and peephole2 to match it. I think it
would be a bad idea to try to split it, such that the two modes would be in one
pattern and the mov would be another one, because then e.g. the scheduler could
move it away etc.
>From gcc-bugs-return-662568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 16:18:40 2019
Return-Path: <gcc-bugs-return-662568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63149 invoked by alias); 6 Dec 2019 16:18: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 62615 invoked by uid 48); 6 Dec 2019 16:18:35 -0000
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Fri, 06 Dec 2019 16:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jb at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92836-4-msbjLvVWHL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00638.txt.bz2
Content-length: 1026
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
--- Comment #13 from Janne Blomqvist <jb at gcc dot gnu.org> ---
To clarify my previous message, instead of
inquire(..., exist=exist)
if (exist) then
open(...)
else
! Handle file not existing
end if
you can do
open(..., status='old', iostat=stat)
if (stat /= o) then
! Handle file not existing
end if
If you open a file with status='old', then opening the file will fail if it
doesn't exist, and thus there is no race between checking whether the file
exists with inquire and trying to open it.
Similarly, if you want to make sure that the file is created, i.e. that it
doesn't exist previously, instead of doing
inquire(..., exist=exist)
if (!exist) then
open(...)
else
! Handle if the file does exist
end if
You should do
open(..., status='new', iostat=stat)
if (stat /= 0) then
! Handle file existing
end if
With status='new', the file will be created and opened with O_CREAT|O_EXCL
which is guaranteed to be atomic.
>From gcc-bugs-return-662569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 16:27:06 2019
Return-Path: <gcc-bugs-return-662569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82288 invoked by alias); 6 Dec 2019 16:27: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 82238 invoked by uid 48); 6 Dec 2019 16:27:02 -0000
From: "vgupta at synopsys dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89838] [ARC] ICE building glibc testsuite
Date: Fri, 06 Dec 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vgupta at synopsys 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-89838-4-RNFNgWfxFj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89838-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89838-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00639.txt.bz2
Content-length: 141
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89838
--- Comment #3 from Vineet Gupta <vgupta at synopsys dot com> ---
Can this be closed ?
>From gcc-bugs-return-662570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 16:35:43 2019
Return-Path: <gcc-bugs-return-662570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96763 invoked by alias); 6 Dec 2019 16:35:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96671 invoked by uid 48); 6 Dec 2019 16:35:37 -0000
From: "mkuvyrkov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)
Date: Fri, 06 Dec 2019 16:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: EH, ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mkuvyrkov at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92007-4-JRhZ59yZB1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00640.txt.bz2
Content-length: 1130
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007
Maxim Kuvyrkov <mkuvyrkov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mkuvyrkov at gcc dot gnu.org
--- Comment #21 from Maxim Kuvyrkov <mkuvyrkov at gcc dot gnu.org> ---
(In reply to iii from comment #18)
> Author: iii
> Date: Mon Oct 28 13:09:54 2019
> New Revision: 277515
>
> URL: https://gcc.gnu.org/viewcvs?rev=277515&root=gcc&view=rev
> Log:
> Move jump threading before reload
Hi Ilya,
This patch regresses performance of SPEC CPU2006's 400.perlbench on
aarch64-linux-gnu -O3 by 5% with most of the slowdown in the hottest function
S_regmatch (this is for gcc-9-branch).
benchmark,symbol,rel_sample,rel_size,results-0:sample,results-1:sample,results-0:size,results-1:size
400.perlbench,perlbench_base.default, 105,100,9281,9761,1281408,1285488
400.perlbench,[.] S_regmatch , 107,100,3641,3910,16460,16460
Is there a way to fix the problem gcc-9-branch in less intrusive way?
>From gcc-bugs-return-662571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 16:44:52 2019
Return-Path: <gcc-bugs-return-662571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108044 invoked by alias); 6 Dec 2019 16:44:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107949 invoked by uid 48); 6 Dec 2019 16:44:47 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92843] [OpenACC] Disallow 'acc_delete' etc. for everything without a dynamic reference count
Date: Fri, 06 Dec 2019 16:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92843-4-VmuFGZ2ocr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00641.txt.bz2
Content-length: 1390
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92843
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to jules from comment #2)
> I don't think your example is valid
Which one, specifically?
> but I'm not sure it will be fail in
> quite the right way with the current version of my refcount overhaul patch.
> Actually I think the acc_map_data implementation using REFCOUNT_INFINITY is
> probably wrong too.
Maybe, but adjusting that can wait until later. And in particular,
incrementally.
> I will try changing the implementation as follows:
>
> - calls to acc_delete with the structured reference count being non-zero (or
> infinity in the case of '#pragma acc declare'd data) should raise an error.
Are you sure about that? Per my reading as detailed above, that would actually
be valid, and be a no-op. (That's also what I'm asking about in
<https://github.com/OpenACC/openacc-spec/issues/246>, using the very same
text/example.)
> - acc_map_data should use GOMP_MAP_VARS_OPENACC_ENTER_DATA instead of
> forcing the refcount to infinity (i.e., making the behaviour the same as
> "enter data (create)").
>
> Does that match your understanding of what the behaviour should be?
I still have to look into that one (which may have changed between OpenACC 2.6
and later?), but let's defer that one until later, as mentioned above.
>From gcc-bugs-return-662572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 16:53:55 2019
Return-Path: <gcc-bugs-return-662572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73097 invoked by alias); 6 Dec 2019 16:53: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 72987 invoked by uid 48); 6 Dec 2019 16:53:47 -0000
From: "iii at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)
Date: Fri, 06 Dec 2019 16: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: EH, ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iii at linux dot ibm.com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92007-4-MxbPUy4o0J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00642.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007
--- Comment #22 from Ilya Leoshkevich <iii at linux dot ibm.com> ---
Hello Maxim,
Sorry about that!
I don't think it's possible to simply move jump threading back, since
it's not correct to have it where it used to be. So I will build and
run the new and the old 400.perlbench on gcc compile farm and see what
else I can do about the difference.
Best regards,
Ilya
>From gcc-bugs-return-662573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 16:55:37 2019
Return-Path: <gcc-bugs-return-662573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74798 invoked by alias); 6 Dec 2019 16:55: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 74760 invoked by uid 48); 6 Dec 2019 16:55:32 -0000
From: "vgupta at synopsys dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92845] New: [ARC] gcc not generating hardware compare instruction FDCMP for -mcpu=hs38_linux
Date: Fri, 06 Dec 2019 16:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vgupta at synopsys 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-92845-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00643.txt.bz2
Content-length: 783
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92845
Bug ID: 92845
Summary: [ARC] gcc not generating hardware compare instruction
FDCMP for -mcpu=hs38_linux
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: vgupta at synopsys dot com
CC: claziss at gcc dot gnu.org, claziss at gmail dot com
Target Milestone: ---
Test case:
int f(double x, double y)
{
return x > y;
}
arc-linux-gcc -mcpu=hs38_linux -c -O2 --save-temps
push_s blink
bl @__gtdf2;1
setgt r0, r0, 0
pop_s blink
j_s [blink]
>From gcc-bugs-return-662574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 17:10:45 2019
Return-Path: <gcc-bugs-return-662574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6752 invoked by alias); 6 Dec 2019 17: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 6653 invoked by uid 48); 6 Dec 2019 17:10:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92837] ICE on syntax error in requires clause, in cp_parser_constraint_primary_expression
Date: Fri, 06 Dec 2019 17:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92837-4-iNVoJLNKik@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92837-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00644.txt.bz2
Content-length: 1031
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92837
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-06
CC| |asutton at gcc dot gnu.org,
| |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This is an incorrect assumption in cp_parser_constraint_primary_expression. It
assumes that when doing a tentative parse that the returned expr will always be
error_mark_node if there are any errors, but that is not the case, e.g. if
there is just missing closing ) it can simulate an error which later causes
cp_parse_definitely to fail, yet expr is still not error_mark_node and pce can
still be pce_ok.
>From gcc-bugs-return-662575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 17:21:37 2019
Return-Path: <gcc-bugs-return-662575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23620 invoked by alias); 6 Dec 2019 17: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 22900 invoked by uid 48); 6 Dec 2019 17:21:30 -0000
From: "vgupta at synopsys dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92846] New: [ARC] gloating point compares not generating Invalid Operand
Date: Fri, 06 Dec 2019 17:21: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: vgupta at synopsys 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-92846-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00645.txt.bz2
Content-length: 896
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92846
Bug ID: 92846
Summary: [ARC] gloating point compares not generating Invalid
Operand
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: vgupta at synopsys dot com
CC: claziss at gcc dot gnu.org, vgupta at synopsys dot com
Target Milestone: ---
This is similar to issues reported for other targets
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77918
The FDCMP instructions generated raised Invalid operand only for sNaN. This
causes glibc testsuite failures test-{double,float,...}-iseqsig which test both
qNaN and sNaN and expect either to pass.
>From gcc-bugs-return-662576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 17:24:50 2019
Return-Path: <gcc-bugs-return-662576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30605 invoked by alias); 6 Dec 2019 17:24: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 30557 invoked by uid 48); 6 Dec 2019 17:24:45 -0000
From: "vgupta at synopsys dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92846] [ARC] gloating point compares not generating Invalid Operand
Date: Fri, 06 Dec 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: target
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vgupta at synopsys 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-92846-4-M4kAkiPEcs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92846-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92846-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00646.txt.bz2
Content-length: 342
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92846
--- Comment #1 from Vineet Gupta <vgupta at synopsys dot com> ---
Test case:
int f(double x, double y)
{
return x > y; // expected FDCMPF (qNaN, sNaN)
}
int f2(double x, double y)
{
return __builtin_isgreater(x, y); // expected FDCMP (only sNan)
}
>From gcc-bugs-return-662578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 17:31:54 2019
Return-Path: <gcc-bugs-return-662578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32092 invoked by alias); 6 Dec 2019 17: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 31452 invoked by uid 48); 6 Dec 2019 17:31:46 -0000
From: "laurent.stacul at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvOTI4NDddIE5ldzogW0MrKzIwXSBhbWJpZ3VvdXMgb3Zlcmxv?= =?UTF-8?B?YWQgZm9yIOKAmG9wZXJhdG9yPT3igJkgPw==?Date: Fri, 06 Dec 2019 17:31: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: laurent.stacul 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-92847-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00648.txt.bz2
Content-length: 2395
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92847
Bug ID: 92847
Summary: [C++20] ambiguous overload for ‘operator==’ ?
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: laurent.stacul at gmail dot com
Target Milestone: ---
Hello,
Compiling the following reproducer with the gcc trunk and the option
-std=gnu++2a (c++2a), I get the following error:
#include <iostream>
template<typename T>
class A {
public:
A() {}
template<typename U>
A(const A<U>&) {}
bool operator==(const A<T>&) { return true; }
};
int main(int argc, const char *argv[])
{
A<const std::string> a;
A<std::string> b;
if (a == b) {}
return 0;
}
a.cpp: In function ‘int main(int, const char**)’:
a.cpp:25:11: error: ambiguous overload for ‘operator==’ (operand types are
‘A<const std::__cxx11::basic_string<char> >’ and
‘A<std::__cxx11::basic_string<char> >’)
25 | if (a == b) {}
| ~ ^~ ~
| | |
| | A<basic_string<[...]>>
| A<basic_string<[...]>>
a.cpp:15:10: note: candidate: ‘bool A<T>::operator==(const A<T>&) [with T =
std::__cxx11::basic_string<char>]’
15 | bool operator==(const A<T>&) {
| ^~~~~~~~
a.cpp:15:10: note: candidate: ‘bool A<T>::operator==(const A<T>&) [with T =
const std::__cxx11::basic_string<char>]’
When I compile with gcc 9.2, I have no issue. The generated code is the one I
expect (implicit call to the constructor A<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >
const>::A<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> > >(A<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > const&) then call to the
A<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char>
> const>::operator==(A<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> > const> const&).
Can you tell me which C++ 20 rule I am breaking here ?
Thanks in advance for your reply,
Laurent
>From gcc-bugs-return-662577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 17:31:21 2019
Return-Path: <gcc-bugs-return-662577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30199 invoked by alias); 6 Dec 2019 17:31: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 30129 invoked by uid 48); 6 Dec 2019 17:31:17 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Fri, 06 Dec 2019 17:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
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: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92820-4-3c9I2LNXFs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00647.txt.bz2
Content-length: 916
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
As elsewhere, the .note should be guarded on Linux or so, either
#ifdef __linux__
or something similar. And the second thing is that @progbits is only
recognized on some platforms, others need %progbits, but ARM isn't the only
one, e.g. AArch64, SH, microblaze, and I believe SPARC Solaris as need that
too. Maybe PA too?
Maybe %progbits works everywhere, e.g.
libphobos/libdruntime/config/common/threadasm.S
uses
#if (__linux__ || __FreeBSD__ || __NetBSD__ || __DragonFly__) && __ELF__
.section .note.GNU-stack,"",%progbits
#endif
>From gcc-bugs-return-662579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 17:33:12 2019
Return-Path: <gcc-bugs-return-662579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34299 invoked by alias); 6 Dec 2019 17:33: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 34246 invoked by uid 48); 6 Dec 2019 17:33:08 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92775] [8/9 Regression] Incorrect expression in DW_AT_byte_stride on an array
Date: Fri, 06 Dec 2019 17: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: 10.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-92775-4-5BAKEqKDrS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00649.txt.bz2
Content-length: 716
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92775
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[8/9/10 Regression] |[8/9 Regression] Incorrect
|Incorrect expression in |expression in
|DW_AT_byte_stride on an |DW_AT_byte_stride on an
|array |array
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Regression fixed on the trunk, though it would be nice to optimize again the
most common case where we know we don't need to load up descr->span.
>From gcc-bugs-return-662580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 17:35:08 2019
Return-Path: <gcc-bugs-return-662580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36709 invoked by alias); 6 Dec 2019 17:35: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 36642 invoked by uid 48); 6 Dec 2019 17:35:04 -0000
From: "vgupta at synopsys dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92846] [ARC] gloating point compares not generating Invalid Operand
Date: Fri, 06 Dec 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: target
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vgupta at synopsys 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-92846-4-hEDCxG28om@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92846-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92846-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00650.txt.bz2
Content-length: 322
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92846
--- Comment #2 from Vineet Gupta <vgupta at synopsys dot com> ---
Created attachment 47438
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47438&action=edit
proposed fix
Ran full glibc tessuite with this: No regressions
gcc dejagnu test pr52451.c passes too
>From gcc-bugs-return-662581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 17:45:31 2019
Return-Path: <gcc-bugs-return-662581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55539 invoked by alias); 6 Dec 2019 17:45: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 55277 invoked by uid 48); 6 Dec 2019 17:45:03 -0000
From: "vgupta at synopsys dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons
Date: Fri, 06 Dec 2019 17:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vgupta at synopsys dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-52451-4-KQFRkasJJR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52451-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52451-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00651.txt.bz2
Content-length: 1219
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451
Vineet Gupta <vgupta at synopsys dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vgupta at synopsys dot com
--- Comment #11 from Vineet Gupta <vgupta at synopsys dot com> ---
ARC gcc backend suffers from this and I've created
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92845 and also a tentative fix
which passes gcc.dg/torture/pr52451.c
However I'm curious that the test uses qNaN. What is the expected behavior for
sNaN. If you tweak the testcase slightly as follows:
diff --git a/gcc/testsuite/gcc.dg/torture/pr52451.c
b/gcc/testsuite/gcc.dg/torture/pr52451.c
- volatile TYPE nan##S = __builtin_nan##S (""); \
+ volatile TYPE nan##S = __builtin_nans##S (""); \
With that even on ARM (RPI3) it now fails for the "quite" C operations "==" and
"!=" and isless(),isgreater(),islessequal(),isgreaterequal().
Is that expected, OK ? I guess there's no easy to fix this unless hardware
supports the 3 varaints or glibc code has a way to clear exception in certain
cases.
>From gcc-bugs-return-662582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 17:47:11 2019
Return-Path: <gcc-bugs-return-662582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59773 invoked by alias); 6 Dec 2019 17:47: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 59715 invoked by uid 48); 6 Dec 2019 17:47:07 -0000
From: "vgupta at synopsys dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons
Date: Fri, 06 Dec 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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vgupta at synopsys dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-52451-4-qxoUkDwEsK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52451-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52451-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00652.txt.bz2
Content-length: 167
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451
--- Comment #12 from Vineet Gupta <vgupta at synopsys dot com> ---
oops the ARC bug is (PR 92846) not (PR 92845)
>From gcc-bugs-return-662583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 17:48:35 2019
Return-Path: <gcc-bugs-return-662583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67052 invoked by alias); 6 Dec 2019 17:48: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 66863 invoked by uid 48); 6 Dec 2019 17:48:22 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92848] New: [OpenACC] Memory leak for simple 'acc_create', 'acc_delete' sequence
Date: Fri, 06 Dec 2019 17:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00653.txt.bz2
Content-length: 1067
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92848
Bug ID: 92848
Summary: [OpenACC] Memory leak for simple 'acc_create',
'acc_delete' sequence
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: openacc
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: jakub at gcc dot gnu.org, jules at gcc dot gnu.org
Target Milestone: ---
By means of a simple test using the OpenACC Profiling Interface, I noticed that
for a simple 'acc_create', 'acc_delete' sequence, we're leaking the device
memory. That's bad, of course; often such things are done in a loop (with some
computation in between, of course).
This seems to get fixed as part of Julian's big "OpenACC reference count
overhaul" patch, but we need to understand what exactly is going on (I think I
know), and, quite obviously, we need test cases (I have some).
>From gcc-bugs-return-662584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 17:50:58 2019
Return-Path: <gcc-bugs-return-662584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106997 invoked by alias); 6 Dec 2019 17:50:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98949 invoked by uid 48); 6 Dec 2019 17:50:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92768] [8/9 Regression] Maybe a wrong code for vector constants
Date: Fri, 06 Dec 2019 17:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-92768-4-zIx7jA4fQf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00654.txt.bz2
Content-length: 528
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92768
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[8/9/10 Regression] Maybe a |[8/9 Regression] Maybe a
|wrong code for vector |wrong code for vector
|constants |constants
--- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk.
>From gcc-bugs-return-662585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 17:59:11 2019
Return-Path: <gcc-bugs-return-662585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5604 invoked by alias); 6 Dec 2019 17:59: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 5546 invoked by uid 48); 6 Dec 2019 17:59:06 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92828] array out of bounds access in libcpp/mkdeps.c
Date: Fri, 06 Dec 2019 17:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92828-4-4fBSeOX6mD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00655.txt.bz2
Content-length: 1436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92828
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
Here's a slightly more reduced example that reproduces a similar warning:
$ cat pr92828.C && gcc -O2 -S -Wall pr92828.C
extern int f (void);
static const char*
g (unsigned n, const char *t)
{
for (unsigned i = n; i--; )
{
if (f ())
{
const char *p = t + n;
if (p[1] == '.' && p[2] == '.' && p[3] == '/')
goto not_this_one;
break;
}
not_this_one:;
}
return t;
}
void h (unsigned n)
{
g (n, "-");
}
pr92828.C: In function ‘void h(unsigned int)’:
pr92828.C:11:26: warning: array subscript [2, 4294967297] is outside array
bounds of ‘const char [2]’ [-Warray-bounds]
11 | if (p[1] == '.' && p[2] == '.' && p[3] == '/')
| ~~~^
pr92828.C:11:41: warning: array subscript [3, 4294967298] is outside array
bounds of ‘const char [2]’ [-Warray-bounds]
11 | if (p[1] == '.' && p[2] == '.' && p[3] == '/')
| ~~~^
>From gcc-bugs-return-662586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 18:04:18 2019
Return-Path: <gcc-bugs-return-662586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20226 invoked by alias); 6 Dec 2019 18:04: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 20153 invoked by uid 48); 6 Dec 2019 18:04:11 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92828] array out of bounds access in libcpp/mkdeps.c
Date: Fri, 06 Dec 2019 18:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92828-4-jGHL9uKUDp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00656.txt.bz2
Content-length: 476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92828
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
Rather than suppressing the warning via a pragma, would replacing the call to
deps_add_target (d, "-", 1);
with
d->targets.push (xstrdup (t));
be a better solution? Unless I've overlooked something it should have the same
effect because "-" has no path separator in it and so apply_vpath won't do
anything with it and neither will deps_add_target.
>From gcc-bugs-return-662587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 18:06:21 2019
Return-Path: <gcc-bugs-return-662587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22519 invoked by alias); 6 Dec 2019 18:06:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22446 invoked by uid 48); 6 Dec 2019 18:06:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92773] [8/9/10 Regression] GCC compilation with big array / header is infinite
Date: Fri, 06 Dec 2019 18:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: compile-time-hog, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92773-4-LGUJvX3q2D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00657.txt.bz2
Content-length: 769
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92773
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So, historical data regarding #c8. Before r211289, it used to print a single
-Wmissing-brace warning, starting with r211289 aka PR53119 it started printing
73 of these + 73 near initialization + 432 in expansion of macro notes.
Starting with r244061 we only emit 73 warnings and no near initialization
warnings and no in expansion of macro notes and that is the case until current
trunk.
>From gcc-bugs-return-662588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 18:09:33 2019
Return-Path: <gcc-bugs-return-662588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86348 invoked by alias); 6 Dec 2019 18: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 86228 invoked by uid 48); 6 Dec 2019 18:09:28 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92773] [8/9/10 Regression] GCC compilation with big array / header is infinite
Date: Fri, 06 Dec 2019 18: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: 9.2.1
X-Bugzilla-Keywords: compile-time-hog, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92773-4-sF0SP8pOZk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00658.txt.bz2
Content-length: 260
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92773
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
For the kernel module, I'd suggest just fixing the external tool, so it emits {
{ 0x.., 0x.. } },
lines instead of { 0x.., 0x.. }, lines.
>From gcc-bugs-return-662589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 18:45:59 2019
Return-Path: <gcc-bugs-return-662589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34440 invoked by alias); 6 Dec 2019 18:45: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 33752 invoked by uid 48); 6 Dec 2019 18:45:45 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92805] gfortran: blanks within literal constants should not be allowed
Date: Fri, 06 Dec 2019 18:45: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: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92805-4-WjBvzajBeu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92805-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92805-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00659.txt.bz2
Content-length: 1650
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92805
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-06
CC| |kargl at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from kargl at gcc dot gnu.org ---
Index: gcc/fortran/primary.c
===================================================================
--- gcc/fortran/primary.c (revision 279052)
+++ gcc/fortran/primary.c (working copy)
@@ -90,16 +90,25 @@ match_kind_param (int *kind, int *is_iso_c)
static int
get_kind (int *is_iso_c)
{
+ char c;
int kind;
match m;
*is_iso_c = 0;
+ c = gfc_peek_ascii_char ();
+ if (gfc_current_form == FORM_FREE && gfc_is_whitespace (c))
+ {
+ gfc_error ("Invalid kind type parameter syntax at %C");
+ return -1;
+ }
+
if (gfc_match_char ('_') != MATCH_YES)
return -2;
- m = match_kind_param (&kind, is_iso_c);
- if (m == MATCH_NO)
+ c = gfc_peek_ascii_char ();
+ if ((gfc_current_form == FORM_FREE && gfc_is_whitespace (c))
+ || (m = match_kind_param (&kind, is_iso_c)) == MATCH_NO)
gfc_error ("Missing kind-parameter at %C");
return (m == MATCH_YES) ? kind : -1;
>From gcc-bugs-return-662590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 18:48:59 2019
Return-Path: <gcc-bugs-return-662590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41987 invoked by alias); 6 Dec 2019 18:48:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41218 invoked by uid 48); 6 Dec 2019 18:48:06 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92805] gfortran: blanks within literal constants should not be allowed
Date: Fri, 06 Dec 2019 18: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: 9.2.1
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92805-4-wtLZs6RFtP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92805-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92805-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00660.txt.bz2
Content-length: 1393
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92805
--- Comment #3 from kargl at gcc dot gnu.org ---
(In reply to kargl from comment #2)
> Index: gcc/fortran/primary.c
> ===================================================================
> --- gcc/fortran/primary.c (revision 279052)
> +++ gcc/fortran/primary.c (working copy)
> @@ -90,16 +90,25 @@ match_kind_param (int *kind, int *is_iso_c)
> static int
> get_kind (int *is_iso_c)
> {
> + char c;
> int kind;
> match m;
>
> *is_iso_c = 0;
>
> + c = gfc_peek_ascii_char ();
> + if (gfc_current_form == FORM_FREE && gfc_is_whitespace (c))
> + {
> + gfc_error ("Invalid kind type parameter syntax at %C");
> + return -1;
> + }
> +
> if (gfc_match_char ('_') != MATCH_YES)
> return -2;
>
> - m = match_kind_param (&kind, is_iso_c);
> - if (m == MATCH_NO)
> + c = gfc_peek_ascii_char ();
> + if ((gfc_current_form == FORM_FREE && gfc_is_whitespace (c))
> + || (m = match_kind_param (&kind, is_iso_c)) == MATCH_NO)
> gfc_error ("Missing kind-parameter at %C");
>
> return (m == MATCH_YES) ? kind : -1;
Patch isn't quite correct. The first gfc_error should probably be removed and
return -2.
>From gcc-bugs-return-662591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 18:55:03 2019
Return-Path: <gcc-bugs-return-662591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16133 invoked by alias); 6 Dec 2019 18:55: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 15841 invoked by uid 48); 6 Dec 2019 18:54:59 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92810] Compiling GCC go for aarch64_be-marvell-linux-gnu fails
Date: Fri, 06 Dec 2019 18:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92810-4-ZH9zBS6KW9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00661.txt.bz2
Content-length: 214
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92810
--- Comment #2 from Ian Lance Taylor <ian at airs dot com> ---
The configure script should work now, but I don't know what other problems you
will encounter.
>From gcc-bugs-return-662592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 19:31:23 2019
Return-Path: <gcc-bugs-return-662592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116659 invoked by alias); 6 Dec 2019 19: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 116100 invoked by uid 55); 6 Dec 2019 19:31:14 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92176] LRA problem with reloads for subreg operands
Date: Fri, 06 Dec 2019 19:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ra, wrong-code
X-Bugzilla-Severity: major
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92176-4-MI5J5mLpwQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92176-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92176-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00662.txt.bz2
Content-length: 850
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92176
--- Comment #8 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
Author: vmakarov
Date: Fri Dec 6 19:30:37 2019
New Revision: 279061
URL: https://gcc.gnu.org/viewcvs?rev=279061&root=gcc&view=rev
Log:
2019-12-06 Andreas Krebbel <krebbel@linux.ibm.com>
Vladimir Makarov <vmakarov@redhat.com>
PR rtl-optimization/92176
* lra.c (simplify_subreg_regno): Don't permit unconditional
changing mode for LRA too.
2019-12-06 Andreas Krebbel <krebbel@linux.ibm.com>
Vladimir Makarov <vmakarov@redhat.com>
PR rtl-optimization/92176
* gcc.target/s390/pr92176.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/s390/pr92176.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/rtlanal.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 19:36:35 2019
Return-Path: <gcc-bugs-return-662593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85276 invoked by alias); 6 Dec 2019 19:36: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 80618 invoked by uid 48); 6 Dec 2019 19:36:31 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92176] LRA problem with reloads for subreg operands
Date: Fri, 06 Dec 2019 19: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, wrong-code
X-Bugzilla-Severity: major
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92176-4-4PemRXytGH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92176-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92176-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00663.txt.bz2
Content-length: 202
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92176
--- Comment #9 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
Thank you, Andreas. I've committed the patch with your changes in the test.
>From gcc-bugs-return-662594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 19:38:19 2019
Return-Path: <gcc-bugs-return-662594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90611 invoked by alias); 6 Dec 2019 19: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 88197 invoked by uid 55); 6 Dec 2019 19:38:13 -0000
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/29842] [meta-bug] outstanding patches / issues from STMicroelectronics
Date: Fri, 06 Dec 2019 19: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.2.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian 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-29842-4-hUVH4pE6a9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-29842-4@http.gcc.gnu.org/bugzilla/>
References: <bug-29842-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00664.txt.bz2
Content-length: 502
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29842
--- Comment #6 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Fri Dec 6 19:37:39 2019
New Revision: 279062
URL: https://gcc.gnu.org/viewcvs?rev=279062&root=gcc&view=rev
Log:
PR go/29842
runtime: update HURD support for mOS now being embedded
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/210285
Modified:
trunk/gcc/go/gofrontend/MERGE
trunk/libgo/go/runtime/os_hurd.go
>From gcc-bugs-return-662595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 19:53:28 2019
Return-Path: <gcc-bugs-return-662595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44013 invoked by alias); 6 Dec 2019 19:53: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 43256 invoked by uid 55); 6 Dec 2019 19:53:21 -0000
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Fri, 06 Dec 2019 19:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92820-4-ZeBJiNklBP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00665.txt.bz2
Content-length: 514
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
--- Comment #12 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Fri Dec 6 19:52:46 2019
New Revision: 279063
URL: https://gcc.gnu.org/viewcvs?rev=279063&root=gcc&view=rev
Log:
PR go/92820
runtime: only build go-context for x86 GNU/Linux
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/210258
Modified:
trunk/gcc/go/gofrontend/MERGE
trunk/libgo/Makefile.am
trunk/libgo/Makefile.in
>From gcc-bugs-return-662596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 20:02:03 2019
Return-Path: <gcc-bugs-return-662596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87998 invoked by alias); 6 Dec 2019 20:02: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 87911 invoked by uid 48); 6 Dec 2019 20:01:58 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92820] [10 Regression] libgo.so.15 has executable stack
Date: Fri, 06 Dec 2019 20:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92820-4-mS9RWtLvQY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00666.txt.bz2
Content-length: 447
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92820
Ian Lance Taylor <ian at airs dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #13 from Ian Lance Taylor <ian at airs dot com> ---
Fixed again. This time for sure.
>From gcc-bugs-return-662597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 20:03:56 2019
Return-Path: <gcc-bugs-return-662597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90377 invoked by alias); 6 Dec 2019 20:03: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 90306 invoked by uid 48); 6 Dec 2019 20:03:51 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92842] [10 Regression] libgo build failure on i686-gnu
Date: Fri, 06 Dec 2019 20:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92842-4-PkcIus8Xfu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92842-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92842-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00667.txt.bz2
Content-length: 456
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92842
Ian Lance Taylor <ian at airs dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Ian Lance Taylor <ian at airs dot com> ---
Should be fixed now by SVN revision 279062.
>From gcc-bugs-return-662598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 20:04:14 2019
Return-Path: <gcc-bugs-return-662598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91232 invoked by alias); 6 Dec 2019 20:04:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91173 invoked by uid 55); 6 Dec 2019 20:04:08 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92805] gfortran: blanks within literal constants should not be allowed
Date: Fri, 06 Dec 2019 20:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92805-4-3bEinAUUta@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92805-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92805-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00668.txt.bz2
Content-length: 2708
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92805
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Fri, Dec 06, 2019 at 06:48:04PM +0000, kargl at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92805
>
> --- Comment #3 from kargl at gcc dot gnu.org ---
> (In reply to kargl from comment #2)
> > Index: gcc/fortran/primary.c
> > ===================================================================
> > --- gcc/fortran/primary.c (revision 279052)
> > +++ gcc/fortran/primary.c (working copy)
> > @@ -90,16 +90,25 @@ match_kind_param (int *kind, int *is_iso_c)
> > static int
> > get_kind (int *is_iso_c)
> > {
> > + char c;
> > int kind;
> > match m;
> >
> > *is_iso_c = 0;
> >
> > + c = gfc_peek_ascii_char ();
> > + if (gfc_current_form == FORM_FREE && gfc_is_whitespace (c))
> > + {
> > + gfc_error ("Invalid kind type parameter syntax at %C");
> > + return -1;
> > + }
> > +
> > if (gfc_match_char ('_') != MATCH_YES)
> > return -2;
> >
> > - m = match_kind_param (&kind, is_iso_c);
> > - if (m == MATCH_NO)
> > + c = gfc_peek_ascii_char ();
> > + if ((gfc_current_form == FORM_FREE && gfc_is_whitespace (c))
> > + || (m = match_kind_param (&kind, is_iso_c)) == MATCH_NO)
> > gfc_error ("Missing kind-parameter at %C");
> >
> > return (m == MATCH_YES) ? kind : -1;
>
> Patch isn't quite correct. The first gfc_error should probably be removed and
> return -2.
>
Tested.
Index: gcc/fortran/primary.c
===================================================================
--- gcc/fortran/primary.c (revision 279052)
+++ gcc/fortran/primary.c (working copy)
@@ -90,16 +90,22 @@ match_kind_param (int *kind, int *is_iso_c)
static int
get_kind (int *is_iso_c)
{
+ char c;
int kind;
match m;
*is_iso_c = 0;
+ c = gfc_peek_ascii_char ();
+ if (gfc_current_form == FORM_FREE && gfc_is_whitespace (c))
+ return -2;
+
if (gfc_match_char ('_') != MATCH_YES)
return -2;
- m = match_kind_param (&kind, is_iso_c);
- if (m == MATCH_NO)
+ c = gfc_peek_ascii_char ();
+ if ((gfc_current_form == FORM_FREE && gfc_is_whitespace (c))
+ || (m = match_kind_param (&kind, is_iso_c)) == MATCH_NO)
gfc_error ("Missing kind-parameter at %C");
return (m == MATCH_YES) ? kind : -1;
>From gcc-bugs-return-662599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 20:09:07 2019
Return-Path: <gcc-bugs-return-662599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123809 invoked by alias); 6 Dec 2019 20:09: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 123782 invoked by uid 48); 6 Dec 2019 20:09:03 -0000
From: "kholdstare0.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92849] New: call to 'operator()' incorrectly considered ambiguous, when inherited twice with different type parameters
Date: Fri, 06 Dec 2019 20: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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kholdstare0.0 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-92849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00669.txt.bz2
Content-length: 2604
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92849
Bug ID: 92849
Summary: call to 'operator()' incorrectly considered ambiguous,
when inherited twice with different type parameters
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: kholdstare0.0 at gmail dot com
Target Milestone: ---
Minimal test case:
#include <type_traits>
template <typename Signature>
struct declfunc;
template <typename Result, typename... Args>
struct declfunc<Result(Args...)>
{
Result operator() (Args...);
};
template <typename... Signatures>
struct decloverload
: declfunc<Signatures>...
{ };
using overload_set = decloverload<void(int), void(int, int)>;
static_assert(std::is_invocable_v<overload_set, int>);
Expected result: compilation succeeds. See the godbolt link below, and try it
with clang - clang accepts the code since version 4
Actual result:
/opt/compiler-explorer/gcc-9.2.0/include/c++/9.2.0/type_traits:2336:26: error:
request for member 'operator()' is ambiguous
2336 | std::declval<_Fn>()(std::declval<_Args>()...)
| ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~
<source>:9:16: note: candidates are: 'Result declfunc<Result(Args
...)>::operator()(Args ...) [with Result = void; Args = {int, int}]'
9 | Result operator() (Args...);
| ^~~~~~~~
<source>:9:16: note: 'Result declfunc<Result(Args
...)>::operator()(Args ...) [with Result = void; Args = {int}]'
<source>:18:24: error: static assertion failed
18 | static_assert(std::is_invocable_v<overload_set, int>);
| ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Compiler returned: 1
Godbolt link with test case as well as '-E' preprocessor output:
https://godbolt.org/z/D9nTBr
I suspect the ambiguity comes from the fact that two call operators are
inherited from the same class (`declfunc` in this case), and the call operators
"look the same" - i.e both are `Result operator() (Args...)`. However since
`declfunc` is instantiated with different template paramaters, the concrete
instances of the call operators are in fact different - Args is `{int}` in one
case and `{int, int}` in another. The compiler mentions this in the error
message. Perhaps the overload check should descend deeper (using the concrete
parameters for `Args...`)
>From gcc-bugs-return-662600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 20:17:05 2019
Return-Path: <gcc-bugs-return-662600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1733 invoked by alias); 6 Dec 2019 20:17: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 1628 invoked by uid 55); 6 Dec 2019 20:17:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92831] CWG1299 extend_ref_init_temps_1 punts on COND_EXPRs
Date: Fri, 06 Dec 2019 20:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92831-4-jJAo1JLe7q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00670.txt.bz2
Content-length: 1235
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92831
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Dec 6 20:16:27 2019
New Revision: 279064
URL: https://gcc.gnu.org/viewcvs?rev=279064&root=gcc&view=rev
Log:
PR c++/92831 - CWG 1299, not extending temporary lifetime for ?:
* cp-tree.h (extend_ref_init_temps): Add a new argument with NULL
default arg.
* call.c (set_up_extended_ref_temp): Add COND_GUARD argument, pass it
down to extend_ref_init_temps. Before pushing cleanup, if COND_GUARD
is non-NULL, create a bool temporary if needed, initialize to false
and guard the cleanup with the temporary being true.
(extend_ref_init_temps_1): Add COND_GUARD argument, pass it down
to recursive calls and set_up_extended_ref_temp. Handle COND_EXPR.
(extend_ref_init_temps): Add COND_GUARD argument, pass it down to
recursive calls and to extend_ref_init_temps_1.
* g++.dg/cpp0x/temp-extend2.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/temp-extend2.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/call.c
trunk/gcc/cp/cp-tree.h
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 20:18:05 2019
Return-Path: <gcc-bugs-return-662601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6603 invoked by alias); 6 Dec 2019 20:18: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 6330 invoked by uid 48); 6 Dec 2019 20:18:00 -0000
From: "kholdstare0.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92849] call to 'operator()' incorrectly considered ambiguous, when inherited twice with different type parameters
Date: Fri, 06 Dec 2019 20:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kholdstare0.0 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-92849-4-jMQBk8FY9p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00671.txt.bz2
Content-length: 769
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92849
--- Comment #1 from Alexander Kondratskiy <kholdstare0.0 at gmail dot com> ---
Actually, this might be bogus. If I do an explicit `using`, everything works:
#include <type_traits>
template <typename Signature>
struct declfunc;
template <typename Result, typename... Args>
struct declfunc<Result(Args...)>
{
Result operator() (Args...);
};
template <typename... Signatures>
struct decloverload
: declfunc<Signatures>...
{
using declfunc<Signatures>::operator()...;
};
using overload_set = decloverload<void(int), void(int, int)>;
static_assert(std::is_invocable_v<overload_set, int>);
Godbolt link: https://godbolt.org/z/VJwPV4
>From gcc-bugs-return-662602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 20:44:26 2019
Return-Path: <gcc-bugs-return-662602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109280 invoked by alias); 6 Dec 2019 20:44:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109227 invoked by uid 48); 6 Dec 2019 20:44:21 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvOTI4NDddIFtDKysyMF0gYW1iaWd1b3VzIG92ZXJsb2FkIGZv?= =?UTF-8?B?ciDigJhvcGVyYXRvcj094oCZID8=?Date: Fri, 06 Dec 2019 20:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92847-4-JQAmeJdUjZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92847-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92847-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00672.txt.bz2
Content-length: 260
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92847
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Laurent Stacul from comment #0)
> bool operator==(const A<T>&) { return true; }
This member function should be const.
>From gcc-bugs-return-662603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 20:49:04 2019
Return-Path: <gcc-bugs-return-662603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117174 invoked by alias); 6 Dec 2019 20:49: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 116947 invoked by uid 48); 6 Dec 2019 20:48:58 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvOTI4NDddIFtDKysyMF0gYW1iaWd1b3VzIG92ZXJsb2FkIGZv?= =?UTF-8?B?ciDigJhvcGVyYXRvcj094oCZID8=?Date: Fri, 06 Dec 2019 20: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: unknown
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-92847-4-ZzR05VfhxA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92847-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92847-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00673.txt.bz2
Content-length: 271
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92847
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Although it's still ambiguous with that fixed. There are some known issues with
the default comparisons feature in C++20, this might be one of them.
>From gcc-bugs-return-662604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 20:53:58 2019
Return-Path: <gcc-bugs-return-662604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8977 invoked by alias); 6 Dec 2019 20:53:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8945 invoked by uid 48); 6 Dec 2019 20:53:54 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvOTI4NDddIFtDKysyMF0gYW1iaWd1b3VzIG92ZXJsb2FkIGZv?= =?UTF-8?B?ciDigJhvcGVyYXRvcj094oCZID8=?Date: Fri, 06 Dec 2019 20:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
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-92847-4-3DWimKfXYr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92847-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92847-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00674.txt.bz2
Content-length: 909
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92847
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Reduced:
template<typename T>
struct A {
A() {}
template<typename U>
A(const A<U>&) {}
bool operator==(const A&) const { return true; }
};
A<const int> a;
A<int> b;
auto c = (a == b);
Compiled with -std=gnu++2a:
cmp.cc:13:13: error: ambiguous overload for 'operator==' (operand types are
'A<const int>' and 'A<int>')
13 | auto c = (a == b);
| ~ ^~ ~
| | |
| | A<int>
| A<const int>
cmp.cc:8:8: note: candidate: 'bool A<T>::operator==(const A<T>&) const [with T
= int]' (reversed)
8 | bool operator==(const A&) const { return true; }
| ^~~~~~~~
cmp.cc:8:8: note: candidate: 'bool A<T>::operator==(const A<T>&) const [with T
= const int]'
>From gcc-bugs-return-662605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 21:03:03 2019
Return-Path: <gcc-bugs-return-662605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73626 invoked by alias); 6 Dec 2019 21:03: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 73525 invoked by uid 48); 6 Dec 2019 21:02:59 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92849] call to 'operator()' incorrectly considered ambiguous, when inherited twice with different type parameters
Date: Fri, 06 Dec 2019 21:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.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-92849-4-R0nzD4bUFC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00675.txt.bz2
Content-length: 507
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92849
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
If name lookup finds the name in multiple base classes, the lookup is
ambiguous. Overload resolution is not done to determine if one function is a
better match than the other.
By pulling them all into the derived class with a using-declaration it means
name lookup finds them all in the same scope, and then applies overload
resolution to find the best one.
So I think GCC is correct.
>From gcc-bugs-return-662606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 21:18:14 2019
Return-Path: <gcc-bugs-return-662606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 131018 invoked by alias); 6 Dec 2019 21:18: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 130559 invoked by uid 48); 6 Dec 2019 21:18:07 -0000
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92823] Is that possible to optimize C++ exception??????????? I always HATE 2 phases of exception unwind
Date: Fri, 06 Dec 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: 10.0
X-Bugzilla-Keywords: EH
X-Bugzilla-Severity: normal
X-Bugzilla-Who: euloanty at live dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92823-4-2h411HwV0O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92823-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00676.txt.bz2
Content-length: 602
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92823
--- Comment #2 from fdlbxtqi <euloanty at live dot com> ---
(In reply to Richard Biener from comment #1)
> It's called "exception" handling. If you use an "exception" on the fast path
> you are doing something wrong.
Have you read recent papers about deterministic exceptions? It all depends on
the use case.
I thought the same before. Now I do not.
However, I would like to try these solutions for both. I think the time for GCC
to start a new branch for a deterministic exception TS in C/C++ just like C++
module TS and coroutine TS.
>From gcc-bugs-return-662607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 21:20:32 2019
Return-Path: <gcc-bugs-return-662607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15153 invoked by alias); 6 Dec 2019 21:20: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 14876 invoked by uid 48); 6 Dec 2019 21:20:26 -0000
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92823] Is that possible to optimize C++ exception??????????? I always HATE 2 phases of exception unwind
Date: Fri, 06 Dec 2019 21: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: EH
X-Bugzilla-Severity: normal
X-Bugzilla-Who: euloanty at live dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92823-4-eQfVL8VgJP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92823-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00677.txt.bz2
Content-length: 441
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92823
--- Comment #3 from fdlbxtqi <euloanty at live dot com> ---
(In reply to Richard Biener from comment #1)
> It's called "exception" handling. If you use an "exception" on the fast path
> you are doing something wrong.
If this succeeds, we will be able to directly use POSIX APIs in C++ with an
exception thrown without ANY wrapper. That will be a great improvement to our
language.
>From gcc-bugs-return-662608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 21:52:33 2019
Return-Path: <gcc-bugs-return-662608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30798 invoked by alias); 6 Dec 2019 21:52: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 30755 invoked by uid 48); 6 Dec 2019 21:52:29 -0000
From: "kholdstare0.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92849] call to 'operator()' incorrectly considered ambiguous, when inherited twice with different type parameters
Date: Fri, 06 Dec 2019 21:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kholdstare0.0 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-92849-4-XON7413ZTk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00678.txt.bz2
Content-length: 188
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92849
--- Comment #3 from Alexander Kondratskiy <kholdstare0.0 at gmail dot com> ---
I think you're right. I think the bug can be closed.
>From gcc-bugs-return-662609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 21:58:03 2019
Return-Path: <gcc-bugs-return-662609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37656 invoked by alias); 6 Dec 2019 21: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 37524 invoked by uid 48); 6 Dec 2019 21:57:59 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92849] call to 'operator()' incorrectly considered ambiguous, when inherited twice with different type parameters
Date: Fri, 06 Dec 2019 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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek 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-92849-4-nh9KVVHCBr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00679.txt.bz2
Content-length: 515
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92849
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |mpolacek at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Closing thus.
>From gcc-bugs-return-662610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 22:03:51 2019
Return-Path: <gcc-bugs-return-662610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54888 invoked by alias); 6 Dec 2019 22:03:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54849 invoked by uid 48); 6 Dec 2019 22:03:47 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92451] [10 Regression] ICE: Segmentation fault (in add_candidates)
Date: Fri, 06 Dec 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: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
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 cc assigned_to
Message-ID: <bug-92451-4-CwJ4Vgaqug@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92451-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92451-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00680.txt.bz2
Content-length: 567
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92451
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |mpolacek at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed by r278786, will add the test.
>From gcc-bugs-return-662611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 22:12:07 2019
Return-Path: <gcc-bugs-return-662611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100354 invoked by alias); 6 Dec 2019 22: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 100328 invoked by uid 48); 6 Dec 2019 22:12:03 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92810] Compiling GCC go for aarch64_be-marvell-linux-gnu fails
Date: Fri, 06 Dec 2019 22:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92810-4-ZW3FA7VZSL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00681.txt.bz2
Content-length: 1380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92810
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Next error:
/bajas/pinskia/src/toolchain-10/scripts/../src/libgo/go/internal/syscall/unix/getrandom_linux.go:35:34:
error: reference to undefined name ‘randomTrap’
35 | r1, _, errno := syscall.Syscall(randomTrap,
| ^
make[7]: Entering directory
'/bajas/pinskia/src/toolchain-10/build-aarch64_be-marvell-linux-gnu/aarch64_be-marvell-linux-gnu/ilp32/libsanitizer'
Makefile:2826: recipe for target 'internal/syscall/unix.lo' failed
make[5]: *** [internal/syscall/unix.lo] Error 1
go/internal/syscall/unix/getrandom_linux_generic.go looks like it is not being
used.
Something like:
diff --git a/libgo/go/internal/syscall/unix/getrandom_linux_generic.go
b/libgo/go/internal/syscall/unix/getrandom_linux_generic.go
index f70ada31a98..fa41e64116a 100644
--- a/libgo/go/internal/syscall/unix/getrandom_linux_generic.go
+++ b/libgo/go/internal/syscall/unix/getrandom_linux_generic.go
@@ -2,7 +2,7 @@
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.
-// +build linux,arm64 linux,nios2 linux,riscv64
+// +build linux,arm64 linux,arm64be linux,nios2 linux,riscv64
package unix
---- CUT ----
Testing that (and see what the next failure is)
>From gcc-bugs-return-662612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 22:15:51 2019
Return-Path: <gcc-bugs-return-662612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105199 invoked by alias); 6 Dec 2019 22:15: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 105147 invoked by uid 48); 6 Dec 2019 22:15:47 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92451] [10 Regression] ICE: Segmentation fault (in add_candidates)
Date: Fri, 06 Dec 2019 22: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: error-recovery, ice-on-invalid-code
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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92451-4-hxsc1x777x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92451-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92451-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00682.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92451
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Fri Dec 6 22:12:51 2019
New Revision: 279067
URL: https://gcc.gnu.org/viewcvs?rev=279067&root=gcc&view=rev
Log:
Add test for c++/92451.
This was ICEing from r277865 to r278786.
* g++.dg/overload/error4.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/overload/error4.C
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 22:16:02 2019
Return-Path: <gcc-bugs-return-662613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105910 invoked by alias); 6 Dec 2019 22: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 105829 invoked by uid 48); 6 Dec 2019 22:15:57 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92451] [10 Regression] ICE: Segmentation fault (in add_candidates)
Date: Fri, 06 Dec 2019 22:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: 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-92451-4-ic9FS5Xy35@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92451-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92451-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00683.txt.bz2
Content-length: 428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92451
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> ---
Done.
>From gcc-bugs-return-662614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 22:52:39 2019
Return-Path: <gcc-bugs-return-662614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32719 invoked by alias); 6 Dec 2019 22:52: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 32672 invoked by uid 48); 6 Dec 2019 22:52:36 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92841] Optimize -fstack-protector-strong code generation a bit
Date: Fri, 06 Dec 2019 22: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: unknown
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: 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-92841-4-jY13yqjA6p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00684.txt.bz2
Content-length: 562
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841
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> ---
Yea, if we were to split it, then we'd probably have to add barriers to keep
the scheduler from moving things around. And if we're adding barriers then the
split is of little value anyway.
>From gcc-bugs-return-662615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 23:05:13 2019
Return-Path: <gcc-bugs-return-662615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47671 invoked by alias); 6 Dec 2019 23:05: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 47639 invoked by uid 48); 6 Dec 2019 23:05:09 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92810] Compiling GCC go for aarch64_be-marvell-linux-gnu fails
Date: Fri, 06 Dec 2019 23:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92810-4-mt1JPkfKaG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00685.txt.bz2
Content-length: 313
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92810
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> Testing that (and see what the next failure is)
After the above patch, there are no build failures; I have not tried to run the
testsuite yet.
>From gcc-bugs-return-662616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 23:10:53 2019
Return-Path: <gcc-bugs-return-662616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55490 invoked by alias); 6 Dec 2019 23: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 55379 invoked by uid 48); 6 Dec 2019 23:10:48 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)
Date: Fri, 06 Dec 2019 23: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: EH, ice-checking, ice-on-valid-code
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: 9.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92007-4-ICqOVQWyTp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00686.txt.bz2
Content-length: 280
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007
--- Comment #23 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Maxim Kuvyrkov from comment #21)
>
> Is there a way to fix the problem gcc-9-branch in less intrusive way?
Could this be an alignment issue?
>From gcc-bugs-return-662617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 23:13:51 2019
Return-Path: <gcc-bugs-return-662617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59310 invoked by alias); 6 Dec 2019 23:13: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 59234 invoked by uid 48); 6 Dec 2019 23:13:47 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92796] [10 Regression] ICE in lra_assign, at lra-assigns.c:1646 on powerpc64le-linux-gnu
Date: Fri, 06 Dec 2019 23:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92796-4-AT87jFzTEP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00687.txt.bz2
Content-length: 3315
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92796
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at gcc dot gnu.org,
| |vmakarov at gcc dot gnu.org
--- Comment #6 from Peter Bergner <bergner at gcc dot gnu.org> ---
CCing Vlad (and Jeff) for LRA questions below.
Here is a slightly smaller test case that ICEs using -O2
-fstack-protector-strong -mcpu=power8:
typedef union
{
__ieee128 a;
int b;
} c;
__ieee128
d (__ieee128 x)
{
__ieee128 g;
c h;
h.a = x;
g = h.b & 5;
h.b = g;
if (g)
return x - x;
return h.a;
}
After IRA, we have the following:
Disposition:
3:r121 l0 mem 8:r133 l0 66
(insn 44 13 2 2 (set (reg:KF 133)
(reg:KF 66 2 [ xD.2842 ])) "pr92796.i":9:1 1112
{vsx_movkf_64bit})
(insn 2 44 37 2 (set (reg/v:KF 121 [ xD.2842 ])
(reg:KF 133)) "pr92796.i":9:1 1112 {vsx_movkf_64bit}
(expr_list:REG_DEAD (reg:KF 133)))
...
<hard reg 66 is live here>
Hard reg 66 is used after insn 2, but since regs 133 and 66 are connected
via a copy, they do not conflict, which is what allows 133 to be assigned
to hard reg 66 (a good thing generally). This is all fine up to this point.
Since pseudo 121 is spilled, LRA generates reloads for insn 2 and we end
up with the following rtl:
(insn 44 13 53 2 (set (reg:KF 133)
(reg:KF 66 2 [ xD.2842 ])) "pr92796.i":9:1 1112
{vsx_movkf_64bit})
(insn 53 44 2 2 (set (reg:DI 144)
(plus:DI (reg/f:DI 110 sfp)
(const_int 32 [0x20]))) "pr92796.i":9:1 66
{*adddi3})
(insn 2 53 37 2 (set (mem/c:KF (reg:DI 144) [4 %sfpD.2858+-16 S16 A128])
(reg:KF 133)) "pr92796.i":9:1 1094 {*vsx_le_perm_store_kf}
(expr_list:REG_DEAD (reg:DI 144)))
...
<hard reg 66 is live here>
Here is where we run into a problem. The pattern *vsx_le_perm_store_kf's
source operand constraint "+wa.r", marks the source operand as an
input/output operand. That now means that pseudo 133 should now be
made to conflict with the hard registers live at that point (ie, 66).
Since pseudo 133 is assigned to hard reg 66, we somehow need to reassign
pseudo 133. However, LRA seems to think insn 2 satisfies its constraints,
so it happily continues on until we reach the assertion at lra-assigns.c:1646
and we ICE:
for (i = FIRST_PSEUDO_REGISTER; i < max_regno; i++)
if (lra_reg_info[i].nrefs != 0
&& reg_renumber[i] >= 0
&& overlaps_hard_reg_set_p (lra_reg_info[i].conflict_hard_regs,
PSEUDO_REGNO_MODE (i), reg_renumber[i]))
gcc_unreachable ();
Vlad (or Jeff), can you point me to where this is supposed to be handled?
I don't think I see where LRA verifies the reg_renumber[regno] values are still
valid with respect to the new pattern constraints for the insns that are
modified by spilling.
lra_reg_info[133].conflict_hard_regs does contain 66, so LRA knows it conflicts
with reg 66, but it never seems to use that information as a sign that pseudo
133 needs reassigning.
>From gcc-bugs-return-662618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 06 23:44:21 2019
Return-Path: <gcc-bugs-return-662618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105577 invoked by alias); 6 Dec 2019 23:44: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 105476 invoked by uid 55); 6 Dec 2019 23:44:17 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92831] CWG1299 extend_ref_init_temps_1 punts on COND_EXPRs
Date: Fri, 06 Dec 2019 23:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92831-4-E0fOaiSLXe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00688.txt.bz2
Content-length: 661
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92831
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Dec 6 23:43:45 2019
New Revision: 279069
URL: https://gcc.gnu.org/viewcvs?rev=279069&root=gcc&view=rev
Log:
PR c++/92831
* call.c (build_conditional_expr_1): For ?: with omitted middle
operand use cp_stabilize_reference if arg1 is glvalue_p rather than
just if it is lvalue_p.
* g++.dg/ext/temp-extend1.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/ext/temp-extend1.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/call.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 00:40:50 2019
Return-Path: <gcc-bugs-return-662619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96259 invoked by alias); 7 Dec 2019 00:40: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 96178 invoked by uid 48); 7 Dec 2019 00:40:44 -0000
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92850] New: clang has already supported concepts in latest trunk. However it does not define __cpp_concepts macro. I defined it but crashes clang compiler
Date: Sat, 07 Dec 2019 00:40: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: euloanty at live dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00689.txt.bz2
Content-length: 16125
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92850
Bug ID: 92850
Summary: clang has already supported concepts in latest trunk.
However it does not define __cpp_concepts macro. I
defined it but crashes clang compiler
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: euloanty at live dot com
Target Milestone: ---
#include<concepts>
#include<ranges>
#include<vector>
int main()
{
std::ranges::contiguous_range auto& vec(std::vector<std::size_t>());
}
//fails to compile with clang++ -o a a.cc -Ofast -std=c++2a -s
a.cc:7:7: error: no member named 'ranges' in namespace 'std'
std::ranges::contiguous_range auto& vec(std::vector<std::size_t>());
~~~~~^
a.cc:7:41: warning: parentheses were disambiguated as a function declaration
[-Wvexing-parse]
std::ranges::contiguous_range auto& vec(std::vector<std::size_t>());
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
a.cc:7:42: note: add a pair of parentheses to declare a variable
std::ranges::contiguous_range auto& vec(std::vector<std::size_t>());
^
( )
1 warning and 1 error generated.
//crashes with clang++ -o a a.cc -Ofast -std=c++2a -s -D__cpp_concepts=201907L
In file included from a.cc:1:
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:73:10:
error: expected expression
&& requires(add_rvalue_reference_t<_From> (&__f)()) {
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:81:10:
error: use of undeclared identifier 'convertible_to'
&& convertible_to<_Tp, common_reference_t<_Tp, _Up>>
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:82:10:
error: use of undeclared identifier 'convertible_to'
&& convertible_to<_Up, common_reference_t<_Tp, _Up>>;
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:88:10:
error: expected expression
&& requires {
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:128:10:
error: expected expression
&& requires(_Lhs __lhs, _Rhs&& __rhs) {
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:127:10:
error: use of undeclared identifier 'common_reference_with'
&& common_reference_with<__detail::__cref<_Lhs>, __detail::__cref<_Rhs>>
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:144:10:
error: expected expression
&& requires
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:153:39:
error: use of undeclared identifier 'convertible_to'
= constructible_from<_Tp, _Tp> && convertible_to<_Tp, _Tp>;
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:158:9:
error: use of undeclared identifier 'move_constructible'
= move_constructible<_Tp>
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:159:43:
error: use of undeclared identifier 'convertible_to'
&& constructible_from<_Tp, _Tp&> && convertible_to<_Tp&, _Tp>
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:160:49:
error: use of undeclared identifier 'convertible_to'
&& constructible_from<_Tp, const _Tp&> && convertible_to<const _Tp&, _Tp>
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:161:48:
error: use of undeclared identifier 'convertible_to'
&& constructible_from<_Tp, const _Tp> && convertible_to<const _Tp, _Tp>;
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:175:7:
error: expected expression
&& requires(_Tp&& __t, _Up&& __u) {
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:195:13:
error: use of undeclared identifier '__adl_swap'
requires __adl_swap<_Tp, _Up>
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:197:11:
error: use of undeclared identifier 'move_constructible'
&& move_constructible<remove_reference_t<_Tp>>
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:198:11:
error: use of undeclared identifier 'assignable_from'
&& assignable_from<_Tp, remove_reference_t<_Tp>>)
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:186:20:
error: use of undeclared identifier '__adl_swap'; did you mean '__sync_swap'?
if constexpr (__adl_swap<_Tp, _Up>)
^
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:195:13:
note: '__sync_swap' declared here
requires __adl_swap<_Tp, _Up>
^
Stack dump:
0. Program arguments: /usr/local/bin/clang-10 -cc1 -triple
x86_64-unknown-linux-gnu -emit-obj -disable-free -disable-llvm-verifier
-discard-value-names -main-file-name a.cc -mrelocation-model static
-mthread-model posix -mframe-pointer=none -menable-no-infs -menable-no-nans
-menable-unsafe-fp-math -fno-signed-zeros -mreassociate -freciprocal-math
-ffp-contract=fast -fno-rounding-math -ffast-math -ffinite-math-only
-masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array
-target-cpu x86-64 -dwarf-column-info -debugger-tuning=gdb -resource-dir
/usr/local/lib/clang/10.0.0 -D __cpp_concepts=201907L -internal-isystem
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0
-internal-isystem
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/x86_64-pc-linux-gnu
-internal-isystem
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/backward
-internal-isystem /usr/local/include -internal-isystem
/usr/local/lib/clang/10.0.0/include -internal-externc-isystem
/usr/include/x86_64-linux-gnu -internal-externc-isystem /include
-internal-externc-isystem /usr/include -Ofast -std=c++2a -fdeprecated-macro
-fdebug-compilation-dir /mnt/d/hg/fast_io/examples/0000.Hello World
-ferror-limit 19 -fmessage-length 0 -fgnuc-version=4.2.1 -fno-implicit-modules
-fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option
-fcolor-diagnostics -vectorize-loops -vectorize-slp -faddrsig -o
/tmp/a-94c4ee.o -x c++ a.cc
1.
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:186:40:
current parser token ')'
2.
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:46:1:
parsing namespace 'std'
3.
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:165:3:
parsing namespace 'std::ranges'
4.
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:167:5:
parsing namespace 'std::ranges::__cust_swap'
5.
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:179:7:
parsing struct/union/class body 'std::ranges::__cust_swap::_Swap'
6.
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:185:4:
parsing function body 'std::ranges::__cust_swap::_Swap::_S_noexcept'
7.
/usr/local/bin/../lib/gcc/x86_64-pc-linux-gnu/10.0.0/../../../../include/c++/10.0.0/concepts:185:4:
in compound statement ('{}')
#0 0x0000000002140d64 PrintStackTraceSignalHandler(void*)
(/usr/local/bin/clang-10+0x2140d64)
#1 0x000000000213eaee llvm::sys::RunSignalHandlers()
(/usr/local/bin/clang-10+0x213eaee)
#2 0x000000000214114c SignalHandler(int) (/usr/local/bin/clang-10+0x214114c)
#3 0x00007efbff2ca890 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x12890)
#4 0x00007efbfe0c0f75 (/lib/x86_64-linux-gnu/libc.so.6+0x16ef75)
#5 0x0000000003f46932 clang::Expr::EvaluateKnownConstInt(clang::ASTContext
const&, llvm::SmallVectorImpl<std::pair<clang::SourceLocation,
clang::PartialDiagnostic> >*) const (/usr/local/bin/clang-10+0x3f46932)
#6 0x000000000395f216 clang::Sema::ActOnCondition(clang::Scope*,
clang::SourceLocation, clang::Expr*, clang::Sema::ConditionKind)
(/usr/local/bin/clang-10+0x395f216)
#7 0x00000000035e54df
clang::Parser::ParseCXXCondition(clang::ActionResult<clang::Stmt*, true>*,
clang::SourceLocation, clang::Sema::ConditionKind,
clang::Parser::ForRangeInfo*) (/usr/local/bin/clang-10+0x35e54df)
#8 0x000000000361dfa2
clang::Parser::ParseParenExprOrCondition(clang::ActionResult<clang::Stmt*,
true>*, clang::Sema::ConditionResult&, clang::SourceLocation,
clang::Sema::ConditionKind) (/usr/local/bin/clang-10+0x361dfa2)
#9 0x0000000003619000 clang::Parser::ParseIfStatement(clang::SourceLocation*)
(/usr/local/bin/clang-10+0x3619000)
#10 0x0000000003616622
clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*,
32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*,
clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang-10+0x3616622)
#11 0x0000000003615e71
clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*,
32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*)
(/usr/local/bin/clang-10+0x3615e71)
#12 0x000000000361d8f1 clang::Parser::ParseCompoundStatementBody(bool)
(/usr/local/bin/clang-10+0x361d8f1)
#13 0x000000000361e725 clang::Parser::ParseFunctionStatementBody(clang::Decl*,
clang::Parser::ParseScope&) (/usr/local/bin/clang-10+0x361e725)
#14 0x000000000359183c
clang::Parser::ParseLexedMethodDef(clang::Parser::LexedMethod&)
(/usr/local/bin/clang-10+0x359183c)
#15 0x000000000359087e
clang::Parser::ParseLexedMethodDefs(clang::Parser::ParsingClass&)
(/usr/local/bin/clang-10+0x359087e)
#16 0x00000000035bc48f
clang::Parser::ParseCXXMemberSpecification(clang::SourceLocation,
clang::SourceLocation, clang::Parser::ParsedAttributesWithRange&, unsigned int,
clang::Decl*) (/usr/local/bin/clang-10+0x35bc48f)
#17 0x00000000035ba1b6
clang::Parser::ParseClassSpecifier(clang::tok::TokenKind,
clang::SourceLocation, clang::DeclSpec&, clang::Parser::ParsedTemplateInfo
const&, clang::AccessSpecifier, bool, clang::Parser::DeclSpecContext,
clang::Parser::ParsedAttributesWithRange&) (/usr/local/bin/clang-10+0x35ba1b6)
#18 0x000000000359d2a5
clang::Parser::ParseDeclarationSpecifiers(clang::DeclSpec&,
clang::Parser::ParsedTemplateInfo const&, clang::AccessSpecifier,
clang::Parser::DeclSpecContext, clang::Parser::LateParsedAttrList*)
(/usr/local/bin/clang-10+0x359d2a5)
#19 0x0000000003587dec
clang::Parser::ParseDeclOrFunctionDefInternal(clang::Parser::ParsedAttributesWithRange&,
clang::ParsingDeclSpec&, clang::AccessSpecifier)
(/usr/local/bin/clang-10+0x3587dec)
#20 0x0000000003587bb5
clang::Parser::ParseDeclarationOrFunctionDefinition(clang::Parser::ParsedAttributesWithRange&,
clang::ParsingDeclSpec*, clang::AccessSpecifier)
(/usr/local/bin/clang-10+0x3587bb5)
#21 0x0000000003586d34
clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&,
clang::ParsingDeclSpec*) (/usr/local/bin/clang-10+0x3586d34)
#22 0x00000000035b385a
clang::Parser::ParseInnerNamespace(llvm::SmallVector<clang::Parser::InnerNamespaceInfo,
4u> const&, unsigned int, clang::SourceLocation&, clang::ParsedAttributes&,
clang::BalancedDelimiterTracker&) (/usr/local/bin/clang-10+0x35b385a)
#23 0x00000000035b3429 clang::Parser::ParseNamespace(clang::DeclaratorContext,
clang::SourceLocation&, clang::SourceLocation)
(/usr/local/bin/clang-10+0x35b3429)
#24 0x000000000359c9ed
clang::Parser::ParseDeclaration(clang::DeclaratorContext,
clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&,
clang::SourceLocation*) (/usr/local/bin/clang-10+0x359c9ed)
#25 0x00000000035862a0
clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&,
clang::ParsingDeclSpec*) (/usr/local/bin/clang-10+0x35862a0)
#26 0x00000000035b385a
clang::Parser::ParseInnerNamespace(llvm::SmallVector<clang::Parser::InnerNamespaceInfo,
4u> const&, unsigned int, clang::SourceLocation&, clang::ParsedAttributes&,
clang::BalancedDelimiterTracker&) (/usr/local/bin/clang-10+0x35b385a)
#27 0x00000000035b3429 clang::Parser::ParseNamespace(clang::DeclaratorContext,
clang::SourceLocation&, clang::SourceLocation)
(/usr/local/bin/clang-10+0x35b3429)
#28 0x000000000359c9ed
clang::Parser::ParseDeclaration(clang::DeclaratorContext,
clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&,
clang::SourceLocation*) (/usr/local/bin/clang-10+0x359c9ed)
#29 0x00000000035862a0
clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&,
clang::ParsingDeclSpec*) (/usr/local/bin/clang-10+0x35862a0)
#30 0x00000000035b385a
clang::Parser::ParseInnerNamespace(llvm::SmallVector<clang::Parser::InnerNamespaceInfo,
4u> const&, unsigned int, clang::SourceLocation&, clang::ParsedAttributes&,
clang::BalancedDelimiterTracker&) (/usr/local/bin/clang-10+0x35b385a)
#31 0x00000000035b3429 clang::Parser::ParseNamespace(clang::DeclaratorContext,
clang::SourceLocation&, clang::SourceLocation)
(/usr/local/bin/clang-10+0x35b3429)
#32 0x000000000359c9ed
clang::Parser::ParseDeclaration(clang::DeclaratorContext,
clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&,
clang::SourceLocation*) (/usr/local/bin/clang-10+0x359c9ed)
#33 0x00000000035862a0
clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&,
clang::ParsingDeclSpec*) (/usr/local/bin/clang-10+0x35862a0)
#34 0x0000000003584e1a
clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&, bool)
(/usr/local/bin/clang-10+0x3584e1a)
#35 0x00000000035802d8 clang::ParseAST(clang::Sema&, bool, bool)
(/usr/local/bin/clang-10+0x35802d8)
#36 0x00000000027bd922 clang::FrontendAction::Execute()
(/usr/local/bin/clang-10+0x27bd922)
#37 0x000000000275a6cf
clang::CompilerInstance::ExecuteAction(clang::FrontendAction&)
(/usr/local/bin/clang-10+0x275a6cf)
#38 0x000000000285cbaa
clang::ExecuteCompilerInvocation(clang::CompilerInstance*)
(/usr/local/bin/clang-10+0x285cbaa)
#39 0x00000000009ce203 cc1_main(llvm::ArrayRef<char const*>, char const*,
void*) (/usr/local/bin/clang-10+0x9ce203)
#40 0x00000000009cc089 main (/usr/local/bin/clang-10+0x9cc089)
#41 0x00007efbfdf73b97 __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x21b97)
#42 0x00000000009c94aa _start (/usr/local/bin/clang-10+0x9c94aa)
clang-10: error: unable to execute command: Segmentation fault
clang-10: error: clang frontend command failed due to signal (use -v to see
invocation)
clang version 10.0.0 (https://github.com/llvm/llvm-project.git
84fdd9d7a50b9b41148e5ae8b93bfc4d2613feea)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/local/bin
clang-10: note: diagnostic msg: PLEASE submit a bug report to and include the
crash backtrace, preprocessed source, and associated run script.
clang-10: note: diagnostic msg:
********************
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-10: note: diagnostic msg: /tmp/a-056fca.cpp
clang-10: note: diagnostic msg: /tmp/a-056fca.sh
clang-10: note: diagnostic msg:
********************
>From gcc-bugs-return-662620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 00:44:55 2019
Return-Path: <gcc-bugs-return-662620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99567 invoked by alias); 7 Dec 2019 00:44:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99528 invoked by uid 48); 7 Dec 2019 00:44:51 -0000
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92823] Is that possible to optimize C++ exception??????????? I always do not like 2 phases of exception unwind since it does not call destructors.
Date: Sat, 07 Dec 2019 00:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: EH
X-Bugzilla-Severity: normal
X-Bugzilla-Who: euloanty at live dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92823-4-NxR9Ve0a3E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92823-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00690.txt.bz2
Content-length: 210
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92823
--- Comment #4 from fdlbxtqi <euloanty at live dot com> ---
I know it is mostly a clang bug. However, jwakely you can try to use clang to
test your code.
>From gcc-bugs-return-662621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 00:47:23 2019
Return-Path: <gcc-bugs-return-662621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112895 invoked by alias); 7 Dec 2019 00:47: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 112858 invoked by uid 48); 7 Dec 2019 00:47:19 -0000
From: "goblock at marvell dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92800] IPA escape analysis for structs
Date: Sat, 07 Dec 2019 00:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: goblock at marvell 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-92800-4-EqW7zpHis9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92800-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92800-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00691.txt.bz2
Content-length: 1010
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92800
Gary Oblock <goblock at marvell dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |goblock at marvell dot com
--- Comment #3 from Gary Oblock <goblock at marvell dot com> ---
What we have started doing at Marvell for mcf is basically a version
of the single-pool scheme of ARM. That is, we'll be turning an array
of structures into a structure of arrays. For the multi-pool
optimization we'll initially be doing an extended version of the
single-pool optimization where instead on a simple index to represent
an array location, we'll use an index and base pair. This approach
yields less performance improvement than ARM's multi-pool
optimization. However, because of being so similar to the single-pool
scheme, it will be expedient to do this before we or others tackle
ARM's more complex transformation.
>From gcc-bugs-return-662622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 00:58:14 2019
Return-Path: <gcc-bugs-return-662622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83785 invoked by alias); 7 Dec 2019 00:58: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 83738 invoked by uid 48); 7 Dec 2019 00:58:10 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92850] clang has already supported concepts in latest trunk. However it does not define __cpp_concepts macro. I defined it but crashes clang compiler
Date: Sat, 07 Dec 2019 00:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92850-4-FtPlfZJRo3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92850-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00692.txt.bz2
Content-length: 233
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92850
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The crash itself should report to llvm project for sure.
Are you sure concepts are fully implemented in clang?
>From gcc-bugs-return-662623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 01:01:05 2019
Return-Path: <gcc-bugs-return-662623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87135 invoked by alias); 7 Dec 2019 01:01: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 87045 invoked by uid 48); 7 Dec 2019 01:01:01 -0000
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92850] clang has already supported concepts in latest trunk. However it does not define __cpp_concepts macro. I defined it but crashes clang compiler
Date: Sat, 07 Dec 2019 01: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: euloanty at live dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92850-4-xhhWZwNKmd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92850-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00693.txt.bz2
Content-length: 620
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92850
--- Comment #2 from fdlbxtqi <euloanty at live dot com> ---
(In reply to Andrew Pinski from comment #1)
> The crash itself should report to llvm project for sure.
>
> Are you sure concepts are fully implemented in clang?
Yea. I know it is an LLVM bug and should be reported for LLVM project and I
have done that directly to clang concepts author. However, this can still be
useful to check whether <concepts>, <ranges> implementation in GCC is valid or
not.
"Are you sure concepts are fully implemented in clang?"
Yes, but feature testing macro is missing.
>From gcc-bugs-return-662624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 01:37:48 2019
Return-Path: <gcc-bugs-return-662624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8009 invoked by alias); 7 Dec 2019 01:37: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 7959 invoked by uid 48); 7 Dec 2019 01:37:43 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/80532] warning on pointer access after free
Date: Sat, 07 Dec 2019 01:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm 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-80532-4-rlN8SBMWiM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80532-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80532-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00694.txt.bz2
Content-length: 2554
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80532
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
My analyzer finds these:
./xgcc -B. -fanalyzer -c ../../src/gcc/testsuite/gcc.dg/analyzer/pr80532.c
-ftime-report
../../src/gcc/testsuite/gcc.dg/analyzer/pr80532.c: In function ‘free_list’:
../../src/gcc/testsuite/gcc.dg/analyzer/pr80532.c:14:28: warning: use after
‘free’ of ‘p’ [CWE-416] [-Wanalyzer-use-after-free]
14 | for (p = head; p != 0; p = p->next) /* { dg-warning "use after 'free'
of 'p'" } */
| ~~^~~~~~~~~
‘free_list’: events 1-4
|
| 14 | for (p = head; p != 0; p = p->next) /* { dg-warning "use after
'free' of 'p'" } */
| | ^~~ ~~~~~~~~~~~
| | | |
| | | (4) use after ‘free’ of ‘p’; freed at
(3)
| | (1) following ‘true’ branch (when ‘p’ is non-NULL)...
| 15 | free (p); /* { dg-message "freed here" } */
| | ~~~~~~~~
| | |
| | (2) ...to here
| | (3) freed here
|
../../src/gcc/testsuite/gcc.dg/analyzer/pr80532.c:14:28: note: 8 duplicates
14 | for (p = head; p != 0; p = p->next) /* { dg-warning "use after 'free'
of 'p'" } */
| ~~^~~~~~~~~
../../src/gcc/testsuite/gcc.dg/analyzer/pr80532.c: In function ‘foobar’:
../../src/gcc/testsuite/gcc.dg/analyzer/pr80532.c:24:3: warning: double-‘free’
of ‘p’ [CWE-415] [-Wanalyzer-double-free]
24 | free (p); /* { dg-warning "double-'free' of 'p'" } */
| ^~~~~~~~
‘foobar’: events 1-2
|
| 22 | memset (p, 0, n);
| | ^~~~~~~~~~~~~~~~
| | |
| | (1) first ‘free’ here
| 23 | free (p); /* { dg-message "first 'free' here" } */
| 24 | free (p); /* { dg-warning "double-'free' of 'p'" } */
| | ~~~~~~~~
| | |
| | (2) second ‘free’ here; first ‘free’ was at (1)
|
>From gcc-bugs-return-662625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 01:40:20 2019
Return-Path: <gcc-bugs-return-662625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10658 invoked by alias); 7 Dec 2019 01:40: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 10603 invoked by uid 48); 7 Dec 2019 01:40:16 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85055] warn on accessing free memory
Date: Sat, 07 Dec 2019 01:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85055-4-SnVnMCPDIV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85055-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85055-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00695.txt.bz2
Content-length: 965
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85055
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org
--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
My analyser reports on this:
pr85055.c: In function ‘f’:
pr85055.c:6:13: warning: use after ‘free’ of ‘foo’ [CWE-416]
[-Wanalyzer-use-after-free]
6 | return foo[0];
| ~~~^~~
‘f’: events 1-2
|
| 5 | free(foo);
| | ^~~~~~~~~
| | |
| | (1) freed here
| 6 | return foo[0];
| | ~~~~~~
| | |
| | (2) use after ‘free’ of ‘foo’; freed at (1)
|
>From gcc-bugs-return-662626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 02:04:49 2019
Return-Path: <gcc-bugs-return-662626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12200 invoked by alias); 7 Dec 2019 02: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 11984 invoked by uid 48); 7 Dec 2019 02:04:41 -0000
From: "flast at flast dot jp" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92851] New: Lambda capture of *this with mutable is not mutable
Date: Sat, 07 Dec 2019 02:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: flast at flast dot 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-92851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00696.txt.bz2
Content-length: 673
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92851
Bug ID: 92851
Summary: Lambda capture of *this with mutable is not mutable
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: flast at flast dot jp
Target Milestone: ---
GCC rejects assignment to copied *this even lambda is mutable, like a following
code.
----
void foo() const
{
[*this]() mutable
{
a = 0;
}();
}
----
https://wandbox.org/permlink/YCzFnI9cDOsPSigf
>From gcc-bugs-return-662627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 03:29:05 2019
Return-Path: <gcc-bugs-return-662627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58086 invoked by alias); 7 Dec 2019 03:29: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 58065 invoked by uid 48); 7 Dec 2019 03:29:00 -0000
From: "marcpawl at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92852] New: location references block not in block tree
Date: Sat, 07 Dec 2019 03:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marcpawl at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-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: 2019-12/txt/msg00697.txt.bz2
Content-length: 1363
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92852
Bug ID: 92852
Summary: location references block not in block tree
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: marcpawl at gmail dot com
Target Milestone: ---
https://godbolt.org/z/Kh3xWR
Add...
#include <iostream>
#include <tuple>
#include <algorithm>
void foo()
{
std::ostream& message_stream = std::cout;
auto data = std::make_tuple(3,4.5,"cd");
auto format = [&message_stream](auto && x) { message_stream << x ;};
std::apply([&](auto const& ...x){(..., format(x));}, data);
}
x86-64 gcc (trunk) (Editor #1, Compiler #2) C++
x86-64 gcc (trunk)
-O0 -std=c++17
1
<Compilation failed>
x86-64 gcc (trunk) - 2085ms
#2 with x86-64 gcc (trunk)
<source>: In lambda function:
<source>:12:2: error: location references block not in block tree
12 | }
| ^
&cout
std::basic_ostream<char>::operator<< (&cout, _1);
during IPA pass: *free_lang_data
<source>:12:2: internal compiler error: verify_gimple failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
Compiler returned: 1
>From gcc-bugs-return-662628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 08:09:33 2019
Return-Path: <gcc-bugs-return-662628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102862 invoked by alias); 7 Dec 2019 08: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 102840 invoked by uid 48); 7 Dec 2019 08:09:28 -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++/86037] __PRETTY_FUNCTION__ for constexpr lambda's is missing [with = type]
Date: Sat, 07 Dec 2019 08:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.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-86037-4-WMoFrHKHJF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86037-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86037-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00698.txt.bz2
Content-length: 166
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86037
--- Comment #1 from gcc-bugs at marehr dot dialup.fu-berlin.de ---
This still persists in gcc-9.2 and gcc-10.0.
>From gcc-bugs-return-662629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 08:15:42 2019
Return-Path: <gcc-bugs-return-662629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105546 invoked by alias); 7 Dec 2019 08:15: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 105365 invoked by uid 48); 7 Dec 2019 08:15:14 -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++/90764] [10 Regression] internal compiler error in build_deduction_guide, at cp/pt.c:27162
Date: Sat, 07 Dec 2019 08: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: ice-on-invalid-code
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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90764-4-hwHqSNd3dR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90764-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90764-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00699.txt.bz2
Content-length: 1551
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90764
--- Comment #2 from gcc-bugs at marehr dot dialup.fu-berlin.de ---
This produces
```
> g++-git -std=c++17 ice.cpp
ice.cpp: In instantiation of ‘void g() [with f = e]’:
ice.cpp:7:17: required from here
ice.cpp:6:54: error: cannot deduce template arguments for ‘e<...auto...>’ from
‘()’
6 | template <template <typename> typename f> void g() { f(); }
|
```
where
```
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++ --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 --disable-boostrap
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.0.0 20191207 (experimental) (GCC)
```
>From gcc-bugs-return-662631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 08:20:12 2019
Return-Path: <gcc-bugs-return-662631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108896 invoked by alias); 7 Dec 2019 08:20: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 108806 invoked by uid 48); 7 Dec 2019 08:20:07 -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: Sat, 07 Dec 2019 08:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gcc-bugs at marehr dot dialup.fu-berlin.de
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-91121-4-LtzAvlFl5R@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-12/txt/msg00701.txt.bz2
Content-length: 1576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91121
gcc-bugs at marehr dot dialup.fu-berlin.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from gcc-bugs at marehr dot dialup.fu-berlin.de ---
This seems to be fixed now:
```
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++ --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 --disable-boostrap
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.0.0 20191207 (experimental) (GCC)
```
*** This bug has been marked as a duplicate of bug 90764 ***
>From gcc-bugs-return-662630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 08:20:12 2019
Return-Path: <gcc-bugs-return-662630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108888 invoked by alias); 7 Dec 2019 08:20: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 108828 invoked by uid 48); 7 Dec 2019 08:20:08 -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++/90764] [10 Regression] internal compiler error in build_deduction_guide, at cp/pt.c:27162
Date: Sat, 07 Dec 2019 08:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90764-4-Vw9v6B0SnJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90764-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90764-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00700.txt.bz2
Content-length: 183
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90764
--- Comment #3 from gcc-bugs at marehr dot dialup.fu-berlin.de ---
*** Bug 91121 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-662632-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 08:23:32 2019
Return-Path: <gcc-bugs-return-662632-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121689 invoked by alias); 7 Dec 2019 08:23:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121631 invoked by uid 48); 7 Dec 2019 08:23:29 -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++/91525] ICE (Segmentation Fault) on a bool conversion operator with concepts
Date: Sat, 07 Dec 2019 08:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gcc-bugs at marehr dot dialup.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-91525-4-v4G69SPx97@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91525-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91525-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00702.txt.bz2
Content-length: 192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91525
--- Comment #2 from gcc-bugs at marehr dot dialup.fu-berlin.de ---
This still fails and furthermore fails in `-std=c++2a` mode as well.
>From gcc-bugs-return-662633-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 08:25:02 2019
Return-Path: <gcc-bugs-return-662633-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128318 invoked by alias); 7 Dec 2019 08:25:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128033 invoked by uid 55); 7 Dec 2019 08:24:58 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87488] hyperlink filenames in diagnostics
Date: Sat, 07 Dec 2019 08:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
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: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87488-4-xUNrNdZLex@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00703.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87488
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sat Dec 7 08:24:14 2019
New Revision: 279073
URL: https://gcc.gnu.org/viewcvs?rev=279073&root=gcc&view=rev
Log:
PR c/87488
* pretty-print.c (pp_begin_url, pp_end_url, test_urls): Use BEL
instead of ST sequence to terminate OSC 8 strings.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/pretty-print.c
>From gcc-bugs-return-662634-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 08:27:42 2019
Return-Path: <gcc-bugs-return-662634-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129977 invoked by alias); 7 Dec 2019 08:27: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 129901 invoked by uid 48); 7 Dec 2019 08:27:39 -0000
From: "gcc at mattwhitlock dot name" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92853] New: std::filesystem::path::operator+=(std::filesystem::path const&) corrupts the heap
Date: Sat, 07 Dec 2019 08:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gcc at mattwhitlock dot name
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-92853-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00704.txt.bz2
Content-length: 819
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92853
Bug ID: 92853
Summary: std::filesystem::path::operator+=(std::filesystem::pat
h const&) corrupts the heap
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc at mattwhitlock dot name
Target Milestone: ---
// BEGIN test.cpp
#include <filesystem>
int main() {
using std::filesystem::path;
path p1{ "." }, p2{ "/" };
p1 += p2; // corrupts heap
path p3{ p1 }; // CRASH!
return 0;
}
// END test.cpp
$ g++ -std=gnu++2a -o test test.cpp
$ ./test
malloc(): corrupted top size
Aborted
>From gcc-bugs-return-662635-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 08:57:22 2019
Return-Path: <gcc-bugs-return-662635-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59165 invoked by alias); 7 Dec 2019 08:57: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 59083 invoked by uid 48); 7 Dec 2019 08:57:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87488] hyperlink filenames in diagnostics
Date: Sat, 07 Dec 2019 08: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: diagnostic
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: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87488-4-x8ndrsm1JC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00705.txt.bz2
Content-length: 1117
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87488
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I came up independently with the same patch (sorry, wasn't aware a patch is
discussed in this PR, I've searched just the mailing list and nothing has been
posted), thus I've added you to attribution.
In https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00473.html
I'm mentioning the behavior of various terminals, ~ last year and ~ 4 years
ago.
What still worries me is the 4 years old gnome-terminal that emits garbage to
the screen for both sequences.
And, given that new GCC is quite often used with older setups, whether running
on some remote host over ssh etc., especially if this is enabled by default, it
is better to use something that works with more terminals. Perhaps in a few
years we can change it back to ST from BEL.
>From gcc-bugs-return-662636-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 10:04:31 2019
Return-Path: <gcc-bugs-return-662636-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112925 invoked by alias); 7 Dec 2019 10:04: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 112862 invoked by uid 48); 7 Dec 2019 10:04:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92831] CWG1299 extend_ref_init_temps_1 punts on COND_EXPRs
Date: Sat, 07 Dec 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: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92831-4-ffWH3OLhpw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00706.txt.bz2
Content-length: 212
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92831
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Should be fixed on the trunk so far, will backport to release branches in two
weeks or so.
>From gcc-bugs-return-662637-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 11:07:44 2019
Return-Path: <gcc-bugs-return-662637-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100721 invoked by alias); 7 Dec 2019 11:07: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 100671 invoked by uid 55); 7 Dec 2019 11:07:39 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBmb3J0cmFuLzkyNzkzXSBGb3J0cmFuIExvY2F0aW9uIERhdGEgZm9y?= =?UTF-8?B?IERpYWdub3N0aWMgbGFja3MgdGhlIGNvbHVtbiBudW1iZXIg4oCTIHdoZW4g?= =?UTF-8?B?cGFzc2luZyBvbiB0byBNRQ==?Date: Sat, 07 Dec 2019 11:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92793-4-OHyCDWj4Li@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92793-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00707.txt.bz2
Content-length: 1252
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92793
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Sat Dec 7 11:07:07 2019
New Revision: 279075
URL: https://gcc.gnu.org/viewcvs?rev=279075&root=gcc&view=rev
Log:
Fortran] PR 92793 - fix column used for error diagnostic
PR fortran/92793
* trans.c (gfc_get_location): Declare.
* trans.c (gfc_get_location): Define; returns column-corrected
location.
(trans_runtime_error_vararg, gfc_trans_runtime_check,
gfc_generate_module_code): Use new function.
* trans-array.c (gfc_trans_auto_array_allocation): Likewise.
* trans-common.c (build_field, get_init_field, create_common):
Likewise.
* trans-decl.c (gfc_build_label_decl, gfc_get_symbol_decl): Likewise.
* trans-openmp.c (gfc_trans_omp_reduction_list, gfc_trans_omp_clauses):
Likewise.
* trans-stmt.c (gfc_trans_if_1): Likewise.
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/fortran/trans-common.c
trunk/gcc/fortran/trans-decl.c
trunk/gcc/fortran/trans-openmp.c
trunk/gcc/fortran/trans-stmt.c
trunk/gcc/fortran/trans.c
trunk/gcc/fortran/trans.h
>From gcc-bugs-return-662638-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 11:12:43 2019
Return-Path: <gcc-bugs-return-662638-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113153 invoked by alias); 7 Dec 2019 11:12: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 113088 invoked by uid 48); 7 Dec 2019 11:12:38 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBmb3J0cmFuLzkyNzkzXSBGb3J0cmFuIExvY2F0aW9uIERhdGEgZm9y?= =?UTF-8?B?IERpYWdub3N0aWMgbGFja3MgdGhlIGNvbHVtbiBudW1iZXIg4oCTIHdoZW4g?= =?UTF-8?B?cGFzc2luZyBvbiB0byBNRQ==?Date: Sat, 07 Dec 2019 11:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92793-4-3wKXiiWqOQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92793-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00708.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92793
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
FIXED on GCC 10/trunk
>From gcc-bugs-return-662639-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 11:18:01 2019
Return-Path: <gcc-bugs-return-662639-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119186 invoked by alias); 7 Dec 2019 11: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 119096 invoked by uid 48); 7 Dec 2019 11:17:56 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92850] clang has already supported concepts in latest trunk. However it does not define __cpp_concepts macro. I defined it but crashes clang compiler
Date: Sat, 07 Dec 2019 11:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
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: 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-92850-4-cY8FH2saHz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92850-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00709.txt.bz2
Content-length: 521
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92850
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |ebotcazou at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Not a GCC bug.
>From gcc-bugs-return-662640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 12:21:19 2019
Return-Path: <gcc-bugs-return-662640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118114 invoked by alias); 7 Dec 2019 12: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 118060 invoked by uid 55); 7 Dec 2019 12:21:15 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90840] [8 Regression] ICE in simplify_subreg, at simplify-rtx.c:6441
Date: Sat, 07 Dec 2019 12:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou 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-90840-4-Xy8B9XLaYn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00710.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90840
--- Comment #10 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Sat Dec 7 12:20:44 2019
New Revision: 279076
URL: https://gcc.gnu.org/viewcvs?rev=279076&root=gcc&view=rev
Log:
PR middle-end/90840
* expr.c (expand_assignment): In the case of a CONCAT on the LHS, make
sure to pass a valid inner mode in calls to simplify_gen_subreg.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/expr.c
>From gcc-bugs-return-662641-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 13:15:59 2019
Return-Path: <gcc-bugs-return-662641-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55573 invoked by alias); 7 Dec 2019 13:15:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55097 invoked by uid 48); 7 Dec 2019 13:15:27 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92682] [10 Regression] maxlocval_4.f90 / minlocval_4.f90 failure on POWER9
Date: Sat, 07 Dec 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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92682-4-zzpVvhJvWB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00711.txt.bz2
Content-length: 513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92682
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
So, let's mark this as WORKSFORME, then. If it reappears,
we should be able to see it.
>From gcc-bugs-return-662642-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 14:35:40 2019
Return-Path: <gcc-bugs-return-662642-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22143 invoked by alias); 7 Dec 2019 14:35: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 22078 invoked by uid 48); 7 Dec 2019 14:35:36 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92831] CWG1299 extend_ref_init_temps_1 punts on COND_EXPRs
Date: Sat, 07 Dec 2019 14:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka 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: cc
Message-ID: <bug-92831-4-wMYilcg00G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00712.txt.bz2
Content-length: 554
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92831
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
--- Comment #7 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Thank you! I wonder if your fix can also have an optional warning which would
let us to fix occurrences of this in Firefox since requiring unreleased
compilers is not cool
>From gcc-bugs-return-662643-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 15:15:53 2019
Return-Path: <gcc-bugs-return-662643-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106038 invoked by alias); 7 Dec 2019 15:15: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 105519 invoked by uid 48); 7 Dec 2019 15:15:48 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92854] New: [OpenACC] Always-true conditional in 'libgomp/oacc-mem.c:acc_unmap_data'?
Date: Sat, 07 Dec 2019 15:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00713.txt.bz2
Content-length: 865
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92854
Bug ID: 92854
Summary: [OpenACC] Always-true conditional in
'libgomp/oacc-mem.c:acc_unmap_data'?
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: openacc
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: jakub at gcc dot gnu.org, jules at gcc dot gnu.org
Target Milestone: ---
Given the current implementation (in particular, the "force unmap" semantics of
'acc_unmap_data'?), can there be any way where the 'if (t->refcount == 2)'
conditional in 'libgomp/oacc-mem.c:acc_unmap_data' would not be true? (Putting
in an 'assert' didn't turn up anything.)
>From gcc-bugs-return-662644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 15:16:53 2019
Return-Path: <gcc-bugs-return-662644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109524 invoked by alias); 7 Dec 2019 15: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 109443 invoked by uid 48); 7 Dec 2019 15:16:48 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92854] [OpenACC] Always-true conditional in 'libgomp/oacc-mem.c:acc_unmap_data'?
Date: Sat, 07 Dec 2019 15:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules 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-92854-4-Du52Kp4Fgn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00714.txt.bz2
Content-length: 711
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92854
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-07
Assignee|unassigned at gcc dot gnu.org |jules at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Julian, I'm aware you're changing this code in your big "OpenACC reference
count overhaul", but still/because of that, please have a look here.
>From gcc-bugs-return-662645-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 16:23:19 2019
Return-Path: <gcc-bugs-return-662645-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57869 invoked by alias); 7 Dec 2019 16:23: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 57801 invoked by uid 48); 7 Dec 2019 16:23:13 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87488] hyperlink filenames in diagnostics
Date: Sat, 07 Dec 2019 16:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87488-4-z1OnWzpbGV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00715.txt.bz2
Content-length: 1361
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87488
--- Comment #19 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #18)
> I came up independently with the same patch (sorry, wasn't aware a patch is
> discussed in this PR, I've searched just the mailing list and nothing has
> been posted), thus I've added you to attribution.
Yes, it looks like the three of us each managed to write the same patch.
Bother. Thanks for testing it and committing it.
> In https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00473.html
> I'm mentioning the behavior of various terminals, ~ last year and ~ 4 years
> ago.
> What still worries me is the 4 years old gnome-terminal that emits garbage
> to the screen for both sequences.
> And, given that new GCC is quite often used with older setups, whether
> running on some remote host over ssh etc., especially if this is enabled by
> default, it is better to use something that works with more terminals.
> Perhaps in a few years we can change it back to ST from BEL.
I'm concerned about the behavior of this with the terminals shipped in existing
distributions. Do we need a configure-time flag to allow distributions to
configure the default for URLification? (e.g. perhaps turn it off by default
for gcc 10 on older RHELs? I don't have a RHEL box handy here)
>From gcc-bugs-return-662646-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 16:44:04 2019
Return-Path: <gcc-bugs-return-662646-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73664 invoked by alias); 7 Dec 2019 16: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 73618 invoked by uid 48); 7 Dec 2019 16:44:00 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92825] Unnecesary stack protection in Firefox's LightPixel.
Date: Sat, 07 Dec 2019 16:44: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: 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-92825-4-ufCENoCdNO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92825-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00716.txt.bz2
Content-length: 612
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92825
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> ---
I'm pretty sure it's just an oversight. If an object, regardless of its type,
lives in registers, then the object need not be considered for
stack-protector-strong.
I think we'll need to clarify a bit at the doc level if you fix this.
>From gcc-bugs-return-662647-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 17:36:30 2019
Return-Path: <gcc-bugs-return-662647-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103106 invoked by alias); 7 Dec 2019 17:36: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 103041 invoked by uid 55); 7 Dec 2019 17:36:26 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91678] [9/10 Regression] decltype returns wrong type under certain conditions
Date: Sat, 07 Dec 2019 17:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: patch, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91678-4-94JvWuPUWv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00717.txt.bz2
Content-length: 1382
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91678
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Sat Dec 7 17:35:54 2019
New Revision: 279077
URL: https://gcc.gnu.org/viewcvs?rev=279077&root=gcc&view=rev
Log:
PR c++/91678 - wrong error with decltype and location wrapper.
Compiling this testcase results in a bogus "invalid cast" error; this occurs
since the introduction of location wrappers in finish_id_expression.
Here we are parsing the decltype expression via cp_parser_decltype_expr which
can lead to calling various fold_* and c-family routines. They use
non_lvalue_loc, but that won't create a NON_LVALUE_EXPR wrapper around a
location
wrapper.
So before the location wrappers addition cp_parser_decltype_expr would return
NON_LVALUE_EXPR <c>. Now it returns VIEW_CONVERT_EXPR<float *>(c), but the
STRIP_ANY_LOCATION_WRAPPER immediately following it strips the location
wrapper,
and suddenly we don't know whether we have an lvalue anymore. And that's sad
because then decltype produces the wrong type, causing nonsense errors.
* fold-const.c (maybe_lvalue_p): Handle VIEW_CONVERT_EXPR.
* g++.dg/cpp0x/decltype73.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/decltype73.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/fold-const.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662648-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 17:56:24 2019
Return-Path: <gcc-bugs-return-662648-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100668 invoked by alias); 7 Dec 2019 17:56: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 100360 invoked by uid 48); 7 Dec 2019 17:56:19 -0000
From: "thiago at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92855] New: -fvisibility-inlines-hidden failing to hide out-of-line copies of certain inline member functions
Date: Sat, 07 Dec 2019 17: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: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: thiago at kde 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-92855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00718.txt.bz2
Content-length: 2451
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92855
Bug ID: 92855
Summary: -fvisibility-inlines-hidden failing to hide
out-of-line copies of certain inline member functions
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: thiago at kde dot org
Target Milestone: ---
Related to bug 47877 and bug 45065, but apparently different. Issue probably
goes back a long time.
We're compiling with -fvisibility=hidden -fvisibility-inlines-hidden and expect
that any inline functions used by libstdc++ to perform its job are hidden and
not exported from our library. Unfortunately, GCC is failing to hide some of
those functions and they can be seen with eu-readelf -s in the library output,
where they appear as "WEAK DEFAULT".
This is currently not expected to be a big problem, since these functions *are*
inline and therefore expected to be emitted in any user code that needed to use
them. They just cause our symbol table to be bigger than it needs to be.
Testcase:
#include <future>
class QThreadCreateThread
{
public:
explicit QThreadCreateThread(std::future<void> &&future)
: m_future(std::move(future))
{
}
private:
virtual void run()
{
m_future.get();
}
std::future<void> m_future;
};
// QThread *QThread::createThreadImpl(std::future<void> &&future)
QThreadCreateThread *createThreadImpl(std::future<void> &&future)
{
return new QThreadCreateThread(std::move(future));
}
Compile with -O2 -fvisibility=hidden -fvisibility-inlines-hidden -fno-inline to
force no inlining. In the assembly output, there are plenty of inline functions
with .hidden and plenty without. For example, see
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release():
.section
.text.std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release(),"axG",@progbits,std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release(),comdat
.align 2
.p2align 4
.weak std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release()
.type
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release(), @function
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release():
[...]
No .hidden present.
>From gcc-bugs-return-662649-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 17:57:27 2019
Return-Path: <gcc-bugs-return-662649-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103064 invoked by alias); 7 Dec 2019 17: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 102741 invoked by uid 48); 7 Dec 2019 17:57:24 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91678] [9 Regression] decltype returns wrong type under certain conditions
Date: Sat, 07 Dec 2019 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.2.0
X-Bugzilla-Keywords: patch, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-91678-4-Su06jwSYHt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00719.txt.bz2
Content-length: 704
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91678
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[9/10 Regression] decltype |[9 Regression] decltype
|returns wrong type under |returns wrong type under
|certain conditions |certain conditions
--- Comment #7 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Marek Polacek from comment #5)
> It doesn't seem to fix Comment 4 though, will have to look why :/.
This patch actually fixed that, too:
$ ./cc1plus -quiet 91678.C
$
>From gcc-bugs-return-662650-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 18:43:43 2019
Return-Path: <gcc-bugs-return-662650-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38265 invoked by alias); 7 Dec 2019 18:43: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 38117 invoked by uid 48); 7 Dec 2019 18:43:37 -0000
From: "egmont at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87488] hyperlink filenames in diagnostics
Date: Sat, 07 Dec 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: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egmont at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87488-4-WCcYxHtb32@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00720.txt.bz2
Content-length: 1024
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87488
--- Comment #20 from Egmont Koblinger <egmont at gmail dot com> ---
GNOME Terminal's behavior mainly depends on VTE. Hyperlinks are supported since
VTE 0.50 and a corresponding GNOME Terminal 3.26.
VTE 0.48.2 and 0.46.3, and newer versions within these stable series silently
ignore OSC 8.
VTE 0.48.[01], 0.46.[012] and older stable series emit garbage.
As far as I know, an up-to-date RHEL7 contains VTE 0.52 (see
https://bugzilla.redhat.com/show_bug.cgi?id=1569801). I cannot verify this, nor
can comment about older RHELs.
Older distros are also more likely to ship an older Terminator, Xfce4-Terminal,
Guake, LXterminal etc. which might use the GTK2-based VTE 0.28 (which also
emits garbage), rather than the as-of-then-current GTK3-based VTE 0.4x-0.5x.
You'd need to manually check the exact terminal packages and their dependencies
to get the whole picture.
I can only guess that distros would probably appreciate such a compile-time
kill switch.
>From gcc-bugs-return-662651-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 19:40:06 2019
Return-Path: <gcc-bugs-return-662651-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106963 invoked by alias); 7 Dec 2019 19:40: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 106896 invoked by uid 48); 7 Dec 2019 19:40:02 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92855] -fvisibility-inlines-hidden failing to hide out-of-line copies of certain inline member functions
Date: Sat, 07 Dec 2019 19: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:
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-92855-4-FksUcemFLl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00721.txt.bz2
Content-length: 242
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92855
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The libstdc++ headers have visibility extern on them. Looks like the symbol
you are pointing out would be one of those.
>From gcc-bugs-return-662652-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Dec 07 20:55:45 2019
Return-Path: <gcc-bugs-return-662652-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112851 invoked by alias); 7 Dec 2019 20:55: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 112810 invoked by uid 48); 7 Dec 2019 20:55:41 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92855] -fvisibility-inlines-hidden failing to hide out-of-line copies of certain inline member functions
Date: Sat, 07 Dec 2019 20:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92855-4-CAFBavGmax@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00722.txt.bz2
Content-length: 1102
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92855
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
# 33
"/bajas/pinskia/src/toolchain-10/marvell-tools-be/aarch64_be-marvell-linux-gnu/include/c++/10.0.0/ext/concurrence.h"
3
...
namespace __gnu_cxx __attribute__ ((__visibility__ ("default")))
{
...
enum _Lock_policy { _S_single, _S_mutex, _S_atomic };
...
# 57
"/bajas/pinskia/src/toolchain-10/marvell-tools-be/aarch64_be-marvell-linux-gnu/include/c++/10.0.0/bits/shared_ptr_base.h"
2 3
namespace std __attribute__ ((__visibility__ ("default")))
{
....
template<_Lock_policy _Lp = __default_lock_policy>
class _Sp_counted_base
: public _Mutex_base<_Lp>
--- CUT ---
I am not going to audit all of the functions to prove that the libstdc++
headers have this.
>From gcc-bugs-return-662653-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 08:36:53 2019
Return-Path: <gcc-bugs-return-662653-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71672 invoked by alias); 8 Dec 2019 08: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 71616 invoked by uid 48); 8 Dec 2019 08:36:49 -0000
From: "marc at kdab dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92856] New: incorrectly accepts invalid C++11 braced initialisation of double from long double
Date: Sun, 08 Dec 2019 08: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: marc at kdab 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-92856-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00723.txt.bz2
Content-length: 1173
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92856
Bug ID: 92856
Summary: incorrectly accepts invalid C++11 braced
initialisation of double from long double
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: marc at kdab dot com
Target Milestone: ---
The following code:
// https://godbolt.org/z/tWa2dr
int main() {
extern long double ld;
double d{ld};
}
is invalid according to [dcl.list.init]3.9
(http://eel.is/c++draft/dcl.init.list#3.9): regardless of a target's actual
size for these types, long double -> double is considered a narrowing
conversion [dcl.list.init]/7 (http://eel.is/c++draft/dcl.init.list#7.2), and
the compiler cannot use the constant expression loophole here.
Clang and MSVC correctly error on this.
Actual behaviour: GCC only warns (-Wnarrowing), even with -pedantic.
Expected behaviour: GCC does not accept this code.
This bug exists in all compiler versions, afaict (4.7.4, 4.8.3, 9.1, trunk).
>From gcc-bugs-return-662654-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 11:48:42 2019
Return-Path: <gcc-bugs-return-662654-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13950 invoked by alias); 8 Dec 2019 11: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 13930 invoked by uid 48); 8 Dec 2019 11:48:38 -0000
From: "joshua.a.saxby at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92857] New: -Wsign-conversion flag issues false positives for expression using typedef'ed unsigned types
Date: Sun, 08 Dec 2019 11: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: 5.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joshua.a.saxby 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-92857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00724.txt.bz2
Content-length: 3605
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92857
Bug ID: 92857
Summary: -Wsign-conversion flag issues false positives for
expression using typedef'ed unsigned types
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: joshua.a.saxby at gmail dot com
Target Milestone: ---
Created attachment 47439
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47439&action=edit
Full pre-processed source of the minimal code sample required to produce the
erroneous behaviour
When using typedef'ed unsigned types in an arithmetic expression and compiling
with GCC's -Wsign-conversion flag, GCC produces a false positive warning about
sign conversion as a result of the expression.
Here is a minimal code sample (gcc_sign_conversion_warning_bug.c):
#include <stddef.h>
#include <stdint.h>
typedef uint8_t MyUnsigned;
int main(void) {
MyUnsigned foo = 3U;
MyUnsigned bar = 2U;
// conversion to ‘unsigned int’ from ‘int’ may change the sign of the
result
size_t baz = foo - bar + 1U;
// ^
return (int)baz;
}
(the full preprocessed source is also attached as a file to this bug report)
Essential information:
- GCC version 5.4.0 20160609
- Running on Ubuntu 16.04
- GCC build-time options: ../src/configure -v --with-pkgversion='Ubuntu
5.4.0-6ubuntu1~16.04.12' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-5 --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 --with-system-zlib
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--enable-objc-gc --enable-multiarch --disable-werror --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
- Command line that triggers the bug: gcc -v -save-temps -std=gnu99
-Wsign-conversion gcc_sign_conversion_warning_bug.c
- The erroneous warning message produced is:
gcc_sign_conversion_warning_bug.c:16:28: warning: conversion to ‘unsigned int’
from ‘int’ may change the sign of the result [-Wsign-conversion]
size_t baz = foo - bar + 1U;
^
Additional information:
I have used the online Compiler Explorer at godbolt.org to verify that this
issue is also present on all GCC versions from 5.4 through 9.2 inclusive. If it
is useful to anyone, there is a link to this online sample here:
https://godbolt.org/z/-2jSYx
I have also tested this on the Clang compiler on the same system used to verify
the GCC sample and Clang does not issue a warning (same warning flag was used).
>From gcc-bugs-return-662655-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 11:51:56 2019
Return-Path: <gcc-bugs-return-662655-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120646 invoked by alias); 8 Dec 2019 11:51: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 120040 invoked by uid 48); 8 Dec 2019 11:51:52 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92858] New: [10 regression] spurious backslashes around switch string in warning messages
Date: Sun, 08 Dec 2019 11: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: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: minor
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-92858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00725.txt.bz2
Content-length: 1485
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92858
Bug ID: 92858
Summary: [10 regression] spurious backslashes around switch
string in warning messages
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: minor
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: ebotcazou at gcc dot gnu.org
Target Milestone: ---
The switch string is printed between a pair of backslashes in warning messages,
which doesn't seem to be a progress. Consider the following C file:
int A[128];
inline void
fill (int *a, int n)
{
for (int i = 0; i < n; i++)
a[i] = i * 2 - n;
}
int get (int i)
{
fill (A, 128);
return A[i];
}
compiled at -O -fno-early-inlining --param max-inline-insns-single=0 -Winline:
t.c: In function 'get':
t.c:4:1: warning: inlining failed in call to 'fill': --param
max-inline-insns-single limit reached [\-Winline\]
4 | fill (int *a, int n)
| ^~~~
t.c:12:3: note: called from here
12 | fill (A, 128);
| ^~~~~~~~~~~~~
With the GCC 9 compiler, the message is:
t.c: In function 'get':
t.c:4:1: warning: inlining failed in call to 'fill': --param
max-inline-insns-single limit reached [-Winline]
4 | fill (int *a, int n)
| ^~~~
t.c:12:3: note: called from here
12 | fill (A, 128);
| ^~~~~~~~~~~~~
which looks fine.
>From gcc-bugs-return-662656-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 11:56:32 2019
Return-Path: <gcc-bugs-return-662656-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126001 invoked by alias); 8 Dec 2019 11:56: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 125946 invoked by uid 48); 8 Dec 2019 11:56:27 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/40362] openmp: some libgomp functions trigger data races
Date: Sun, 08 Dec 2019 11:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 4.4.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-40362-4-6tgbiAsW26@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-40362-4@http.gcc.gnu.org/bugzilla/>
References: <bug-40362-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00726.txt.bz2
Content-length: 4631
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40362
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #16 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Looking at a simple OMP program, I now get conflicts reported by
valgrind which I do not see here:
program main
implicit none
integer, parameter :: n = 100
real, dimension(n) :: a
real, dimension(n,n) :: b
integer :: i, j, n1, n2
call random_number (a)
!$omp parallel private(i,j)
!$omp do
do j=1,n
do i=1,n
b(i,j) = a(i) * a(j)
end do
end do
!$omp end parallel
read (*,*) n1, n2
print *,b(n1, n2)
end program main
$ gfortran -g -fopenmp -fcheck=all do.f90
$ echo 10 10 | valgrind --tool=helgrind ./a.out 2>&1 | head -60
==4359== Helgrind, a thread error detector
==4359== Copyright (C) 2007-2017, and GNU GPL'd, by OpenWorks LLP et al.
==4359== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==4359== Command: ./a.out
==4359==
==4359== ---Thread-Announcement------------------------------------------
==4359==
==4359== Thread #1 is the program's root thread
==4359==
==4359== ---Thread-Announcement------------------------------------------
==4359==
==4359== Thread #16 was created
==4359== at 0x5F9BE4E: clone (in /lib64/libc-2.22.so)
==4359== by 0x5C993AF: create_thread (in /lib64/libpthread-2.22.so)
==4359== by 0x5C9AECA: pthread_create@@GLIBC_2.2.5 (in
/lib64/libpthread-2.22.so)
==4359== by 0x4C313C9: pthread_create_WRK (hg_intercepts.c:427)
==4359== by 0x4C324BF: pthread_create@* (hg_intercepts.c:460)
==4359== by 0x561167A: gomp_team_start (team.c:836)
==4359== by 0x5609CFC: GOMP_parallel (parallel.c:169)
==4359== by 0x400B45: MAIN__ (do.f90:8)
==4359== by 0x400D1E: main (do.f90:18)
==4359==
==4359== ----------------------------------------------------------------
==4359==
==4359== Possible data race during write of size 4 at 0x645BC00 by thread #1
==4359== Locks held: none
==4359== at 0x56138DB: gomp_barrier_wait_end (bar.c:40)
==4359== by 0x56138DB: gomp_barrier_wait_end (bar.c:35)
==4359== by 0x5611AA0: gomp_simple_barrier_wait (simple-bar.h:60)
==4359== by 0x5611AA0: gomp_team_start (team.c:850)
==4359== by 0x5609CFC: GOMP_parallel (parallel.c:169)
==4359== by 0x400B45: MAIN__ (do.f90:8)
==4359== by 0x400D1E: main (do.f90:18)
==4359==
==4359== This conflicts with a previous read of size 4 by thread #16
==4359== Locks held: none
==4359== at 0x561392B: gomp_barrier_wait_start (bar.h:98)
==4359== by 0x561392B: gomp_barrier_wait (bar.c:56)
==4359== by 0x5611032: gomp_simple_barrier_wait (simple-bar.h:60)
==4359== by 0x5611032: gomp_thread_start (team.c:117)
==4359== by 0x4C315BD: mythread_wrapper (hg_intercepts.c:389)
==4359== by 0x5C9A723: start_thread (in /lib64/libpthread-2.22.so)
==4359== by 0x5F9BE8C: clone (in /lib64/libc-2.22.so)
==4359== Address 0x645bc00 is 128 bytes inside a block of size 192 alloc'd
==4359== at 0x4C2B831: malloc (vg_replace_malloc.c:309)
==4359== by 0x56040E8: gomp_malloc (alloc.c:38)
==4359== by 0x5611278: gomp_get_thread_pool (pool.h:42)
==4359== by 0x5611278: get_last_team (team.c:150)
==4359== by 0x5611278: gomp_new_team (team.c:169)
==4359== by 0x5609CE5: GOMP_parallel (parallel.c:169)
==4359== by 0x400B45: MAIN__ (do.f90:8)
==4359== by 0x400D1E: main (do.f90:18)
==4359== Block was alloc'd by thread #1
==4359==
==4359== ----------------------------------------------------------------
==4359==
==4359== Possible data race during write of size 4 at 0x645BBC4 by thread #1
==4359== Locks held: none
==4359== at 0x56138E1: gomp_barrier_wait_end (bar.c:41)
==4359== by 0x56138E1: gomp_barrier_wait_end (bar.c:35)
... and so on.
I would have to dig a bit deeper into this to see if this is valid.
This is with current trunk and valgrind 3.15.0 on x86_64-pc-linux-gnu.
>From gcc-bugs-return-662657-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 12:25:53 2019
Return-Path: <gcc-bugs-return-662657-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41736 invoked by alias); 8 Dec 2019 12:25:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41691 invoked by uid 55); 8 Dec 2019 12:25:46 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92755] [10 Regression] ICE in gfc_dep_resolver, at fortran/dependency.c:2123
Date: Sun, 08 Dec 2019 12:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92755-4-nMNSButmzo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92755-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00727.txt.bz2
Content-length: 733
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92755
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Sun Dec 8 12:25:15 2019
New Revision: 279086
URL: https://gcc.gnu.org/viewcvs?rev=279086&root=gcc&view=rev
Log:
2019-12-08 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/92755
* dependency.c (gfc_dep_resolver): Move skipping of _data ref
into the loop.
2019-12-08 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/92755
* gfortran.dg/dependency_57.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/dependency_57.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/dependency.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662658-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 12:29:40 2019
Return-Path: <gcc-bugs-return-662658-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47995 invoked by alias); 8 Dec 2019 12:29: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 47946 invoked by uid 48); 8 Dec 2019 12:29:36 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92755] [10 Regression] ICE in gfc_dep_resolver, at fortran/dependency.c:2123
Date: Sun, 08 Dec 2019 12:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: 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-92755-4-wuvlmrpP4F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92755-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00728.txt.bz2
Content-length: 461
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92755
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed.
Thanks a lot for the bug report!
>From gcc-bugs-return-662659-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 13:03:30 2019
Return-Path: <gcc-bugs-return-662659-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93135 invoked by alias); 8 Dec 2019 13:03: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 93044 invoked by uid 55); 8 Dec 2019 13:03:25 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92764] ICE in gfc_procedure_use
Date: Sun, 08 Dec 2019 13:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92764-4-ey7uB6A1q4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92764-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92764-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00729.txt.bz2
Content-length: 730
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92764
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Sun Dec 8 13:02:54 2019
New Revision: 279087
URL: https://gcc.gnu.org/viewcvs?rev=279087&root=gcc&view=rev
Log:
2018-12-08 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/92764
* interface.c (gfc_procedure_use): Check for existence of derived
component before using (twice).
2018-12-08 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/92764
* gfortran.dg/interface_44.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/interface_44.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/interface.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662660-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 13:04:57 2019
Return-Path: <gcc-bugs-return-662660-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96446 invoked by alias); 8 Dec 2019 13:04: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 96397 invoked by uid 48); 8 Dec 2019 13:04:52 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92764] ICE in gfc_procedure_use
Date: Sun, 08 Dec 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: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: 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-92764-4-7MgCUeYsZ2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92764-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92764-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00730.txt.bz2
Content-length: 540
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92764
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |tkoenig at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed on trunk.
Thanks for the bug report!
>From gcc-bugs-return-662661-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 13:43:18 2019
Return-Path: <gcc-bugs-return-662661-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25887 invoked by alias); 8 Dec 2019 13: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 25847 invoked by uid 55); 8 Dec 2019 13:43:14 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92780] [10 Regression] ICE in gfc_get_class_from_expr, at fortran/trans-expr.c:484
Date: Sun, 08 Dec 2019 13:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-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-92780-4-ttUh09ayoS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92780-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92780-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00731.txt.bz2
Content-length: 751
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92780
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Sun Dec 8 13:42:42 2019
New Revision: 279088
URL: https://gcc.gnu.org/viewcvs?rev=279088&root=gcc&view=rev
Log:
Error on Associate with a program.
2018-12-08 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/92780
* resolve.c (resolve_assoc_var): Issue error if the associating
entity is a program.
2018-12-08 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/92780
* gfortran.dg/associate_50.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/associate_50.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662663-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 13:44:27 2019
Return-Path: <gcc-bugs-return-662663-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28806 invoked by alias); 8 Dec 2019 13:44: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 28707 invoked by uid 48); 8 Dec 2019 13:44:19 -0000
From: "armagvvg at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92859] New: compiler treats enum type as an integer during overload resolution when a bit-field of this enum is considered
Date: Sun, 08 Dec 2019 13:44: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: armagvvg 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-92859-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00733.txt.bz2
Content-length: 3248
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92859
Bug ID: 92859
Summary: compiler treats enum type as an integer during
overload resolution when a bit-field of this enum is
considered
Product: gcc
Version: 7.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: armagvvg at gmail dot com
Target Milestone: ---
Created attachment 47440
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47440&action=edit
gzipped preprocessed file
Enumeration types are different from their underlying types when participating
in function overload resolution. But the compiler doesn't differentiate them
when a bit-field member is defined from the enumeration type. And an overloaded
stream operator is defined inside a class where that enum exists. The sample:
--------
#include <iostream>
struct ES {
enum E { v };
// 1
friend std::ostream& operator<<(std::ostream& os, E) { return os << "E"; }
};
// 2 - should be the same but...
// std::ostream& operator<<(std::ostream& os, ES::E) { return os << "E"; }
struct S {
ES::E e : 1;
};
int main() {
S s{};
std::cout << s.e << std::endl;
return 0;
}
--------
It's expected that an output should be 'E' thus calling the operator<<(..., E)
defined here. But 's.e' field is considered integer and '0' is printed.
What's more interesting, if the operator will be defined as marked by '2', all
it works as expected.
Compiled with: g++ -Wall -Wextra -std=c++11 --save-temps -o tst.gcc tst.cpp
No output during compilation.
> gcc -v:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-7
--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 --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
> uname -r
5.0.0-32-generic
I've repeated this bug also on my work with gcc 9.1.0. The same behaviour using
-std=c++14 and -std=c++17.
>From gcc-bugs-return-662662-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 13:44:26 2019
Return-Path: <gcc-bugs-return-662662-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28747 invoked by alias); 8 Dec 2019 13:44: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 28679 invoked by uid 48); 8 Dec 2019 13:44:18 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92780] [10 Regression] ICE in gfc_get_class_from_expr, at fortran/trans-expr.c:484
Date: Sun, 08 Dec 2019 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: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: 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-92780-4-t8X8qCJqTO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92780-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92780-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00732.txt.bz2
Content-length: 530
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92780
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |tkoenig at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed. Thanks for the bug report!
>From gcc-bugs-return-662664-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 13:48:51 2019
Return-Path: <gcc-bugs-return-662664-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33687 invoked by alias); 8 Dec 2019 13:48:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33651 invoked by uid 48); 8 Dec 2019 13:48:47 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92860] New: [8,9,10 regression] Global flags affected by -O settings are clobbered by optimize attribute
Date: Sun, 08 Dec 2019 13:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00734.txt.bz2
Content-length: 1244
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92860
Bug ID: 92860
Summary: [8,9,10 regression] Global flags affected by -O
settings are clobbered by optimize attribute
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
Target Milestone: ---
Hi,
the following testcase:
void linker_error();
__attribute__ ((optimize("-O0")))
int a ()
{
}
static int remove_me ()
{
linker_error ();
}
void
main()
{
}
builds with GCC6 but not with GCC8, GCC9 and GCC10:
hubicka@lomikamen-jh:/aux/hubicka/trunk4/gcc$ gcc -O2 t.c
hubicka@lomikamen-jh:/aux/hubicka/trunk4/gcc$
/aux/hubicka/trunk-install/bin/gcc -O2 t.c
/usr/local/bin/ld: /tmp/cckSFE5R.o: in function `remove_me':
t.c:(.text+0x17): undefined reference to `linker_error'
collect2: error: ld returned 1 exit status
The problem is that while processing the optimize attribute for a we overwritte
flag_toplevel_reorder that is affected by optimization flag but not marked as
Optimization. I suppose there are other cases like this.
>From gcc-bugs-return-662665-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 13:51:07 2019
Return-Path: <gcc-bugs-return-662665-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55229 invoked by alias); 8 Dec 2019 13:51: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 55186 invoked by uid 55); 8 Dec 2019 13:51:03 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92860] [8,9,10 regression] Global flags affected by -O settings are clobbered by optimize attribute
Date: Sun, 08 Dec 2019 13:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92860-4-TW20eBgx9u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00735.txt.bz2
Content-length: 457
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92860
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Author: hubicka
Date: Sun Dec 8 13:50:32 2019
New Revision: 279089
URL: https://gcc.gnu.org/viewcvs?rev=279089&root=gcc&view=rev
Log:
PR tree-optimization/92860
* common.opt (fprofile-reorder-functions, ftoplevel-reorder): Add
Optimization flag.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/common.opt
>From gcc-bugs-return-662666-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 13:54:41 2019
Return-Path: <gcc-bugs-return-662666-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65415 invoked by alias); 8 Dec 2019 13:54: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 65384 invoked by uid 48); 8 Dec 2019 13:54:37 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92860] [8/9/10 regression] Global flags affected by -O settings are clobbered by optimize attribute
Date: Sun, 08 Dec 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: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on short_desc everconfirmed
Message-ID: <bug-92860-4-DIKun1sDFu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00736.txt.bz2
Content-length: 871
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92860
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-08
Summary|[8,9,10 regression] Global |[8/9/10 regression] Global
|flags affected by -O |flags affected by -O
|settings are clobbered by |settings are clobbered by
|optimize attribute |optimize attribute
Ever confirmed|0 |1
--- Comment #2 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Partly fixed on trunk - I think we have other flags/params missing Optimization
attribute that behaves same way.
>From gcc-bugs-return-662667-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 14:39:16 2019
Return-Path: <gcc-bugs-return-662667-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8760 invoked by alias); 8 Dec 2019 14:39:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8672 invoked by uid 48); 8 Dec 2019 14:39:10 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92191] internal compiler error: Segmentation fault
Date: Sun, 08 Dec 2019 14:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc
Message-ID: <bug-92191-4-cdSIiIrhd7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92191-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92191-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00737.txt.bz2
Content-length: 3225
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92191
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
CC| |tkoenig at gcc dot gnu.org
--- Comment #9 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Here's where it segfaults with 7.4.0:
(gdb) r
Starting program: /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/f951.exe tst.f
-ffixed-form -quiet -dumpbase tst.f -mtune=generic -march=x86-64 -auxbase tst
-g -ffpe-trap=zero,overflow,underflow -fdollar-ok -fintrinsic-modules-path
/usr/lib/gcc/x86_64-pc-cygwin/7.4.0/finclude -o /tmp/ccuPm0Se.s
[New Thread 12104.0x2468]
[New Thread 12104.0x2650]
[New Thread 12104.0x2e74]
[New Thread 12104.0x2600]
[New Thread 12104.0x2368]
Thread 1 received signal SIGSEGV, Segmentation fault.
0x00000001004fcf20 in build_common_decl (is_init=false, union_type=<optimized
out>, com=0x6001e8870) at
/usr/src/debug/gcc-7.4.0-1/gcc/fortran/trans-common.c:463
463 attributes = gfc_add_attributes_to_decl (com->head->attr,
NULL_TREE);
(gdb) p com
$1 = (gfc_common_head *) 0x6001e8870
(gdb) p com->head
$2 = (gfc_symbol *) 0x0
$4 = {where = {nextc = 0x6000d6a60, lb = 0x6000d6a10}, use_assoc = 0 '\000',
saved = 0 '\000', threadprivate = 0 '\000', omp_declare_target = 0 '\000',
omp_declare_target_link = 0 '\000', name = "__BLNK__", '\000' <repeats 55
times>, head = 0x0, binding_label = 0x0,
is_bind_c = 0, refs = 0}
Backtrace:
#0 0x00000001004fcf20 in build_common_decl (is_init=false,
union_type=<optimized out>, com=0x6001e8870) at
/usr/src/debug/gcc-7.4.0-1/gcc/fortran/trans-common.c:463
#1 create_common (com=com@entry=0x6001e8870, head=head@entry=0x60020bff0,
saw_equiv=<optimized out>) at
/usr/src/debug/gcc-7.4.0-1/gcc/fortran/trans-common.c:672
#2 0x00000001004fd4c9 in translate_common (common=0x6001e8870,
var_list=<optimized out>) at
/usr/src/debug/gcc-7.4.0-1/gcc/fortran/trans-common.c:1213
#3 0x00000001004fd6d0 in gfc_trans_common (ns=ns@entry=0x60017dc10) at
/usr/src/debug/gcc-7.4.0-1/gcc/fortran/trans-common.c:1300
#4 0x000000010050aac4 in gfc_generate_function_code (ns=0x60017dc10) at
/usr/src/debug/gcc-7.4.0-1/gcc/fortran/trans-decl.c:6235
#5 0x00000001004983af in translate_all_program_units
(gfc_global_ns_list=<optimized out>) at
/usr/src/debug/gcc-7.4.0-1/gcc/fortran/parse.c:6075
#6 gfc_parse_file () at /usr/src/debug/gcc-7.4.0-1/gcc/fortran/parse.c:6275
#7 0x00000001004df32b in gfc_be_parse_file () at
/usr/src/debug/gcc-7.4.0-1/gcc/fortran/f95-lang.c:204
#8 0x00000001008fd8ac in compile_file () at
/usr/src/debug/gcc-7.4.0-1/gcc/toplev.c:467
#9 0x00000001010e7b8d in do_compile () at
/usr/src/debug/gcc-7.4.0-1/gcc/toplev.c:2003
#10 toplev::main (this=this@entry=0xffffca46, argc=<optimized out>,
argc@entry=17, argv=<optimized out>, argv@entry=0xffffcac0) at
/usr/src/debug/gcc-7.4.0-1/gcc/toplev.c:2138
#11 0x0000000101107545 in main (argc=17, argv=0xffffcac0) at
/usr/src/debug/gcc-7.4.0-1/gcc/main.c:39
>From gcc-bugs-return-662668-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 14:49:44 2019
Return-Path: <gcc-bugs-return-662668-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30973 invoked by alias); 8 Dec 2019 14:49: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 30900 invoked by uid 48); 8 Dec 2019 14:49:40 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92191] internal compiler error: Segmentation fault
Date: Sun, 08 Dec 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: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-92191-4-l63PYO8W0L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92191-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92191-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00738.txt.bz2
Content-length: 545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92191
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #10 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
I cannot reproduce the error any more with cygwin's current 8.3.0
(testing), so it seems to be fixed in the meantime.
Could you confirm that? If so, we could mark this as FIXED.
>From gcc-bugs-return-662669-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 15:16:09 2019
Return-Path: <gcc-bugs-return-662669-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51347 invoked by alias); 8 Dec 2019 15:16: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 51253 invoked by uid 48); 8 Dec 2019 15:16:05 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92836] segfault with inquire()
Date: Sun, 08 Dec 2019 15:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92836-4-YYlgm8YTog@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00739.txt.bz2
Content-length: 3209
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92836
--- Comment #14 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Created attachment 47441
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47441&action=edit
Output of valgrind --tool=helgrind
The code from https://gcc.gnu.org/ml/fortran/2019-12/msg00020.html :
program inq
use OMP_Lib
implicit none
logical :: s
character(len=27) :: c
integer :: i, j
i=64
!$omp parallel private(c,j,s)
do while (.true.)
if (OMP_Get_Thread_Num() < omp_get_num_threads()/2) then
open(newUnit=j,file='test.txt',form='formatted',status='unknown')
write (c,'(e17.10)') 1.23456d0
write (j,*) trim(c)
close(j)
else
inquire(file='test.txt',exist=s)
end if
end do
!$omp end parallel
end program
certainly raises a few flags using valgrind --tool=helgrind (see attachment);
apart from the things that happen in libgomp (see PR40362), there are also
fishy things going on in libgfortran:
==4669== Possible data race during write of size 8 at 0x645E9E8 by thread #5
==4669== Locks held: 1, at address 0x645EAC0
==4669== at 0x5099EA0: _gfortrani_new_unit (open.c:566)
==4669== by 0x509A7FC: already_open (open.c:720)
==4669== by 0x509A7FC: _gfortran_st_open (open.c:897)
==4669== by 0x400BED: MAIN__._omp_fn.0 (in /tmp/a.out)
==4669== by 0x5611065: gomp_thread_start (team.c:123)
==4669== by 0x4C315BD: mythread_wrapper (hg_intercepts.c:389)
==4669== by 0x5C9A723: start_thread (in /lib64/libpthread-2.22.so)
==4669== by 0x5F9BE8C: clone (in /lib64/libc-2.22.so)
==4669==
==4669== This conflicts with a previous read of size 8 by thread #16
==4669== Locks held: 1, at address 0x52F94C0
==4669== at 0x50A39D1: find_file0 (unix.c:1722)
==4669== by 0x50A39EE: find_file0 (unix.c:1741)
==4669== by 0x50A514A: _gfortrani_find_file (unix.c:1779)
==4669== by 0x509258C: _gfortran_st_inquire (inquire.c:803)
==4669== by 0x400B5C: MAIN__._omp_fn.0 (in /tmp/a.out)
==4669== by 0x5611065: gomp_thread_start (team.c:123)
==4669== by 0x4C315BD: mythread_wrapper (hg_intercepts.c:389)
==4669== by 0x5C9A723: start_thread (in /lib64/libpthread-2.22.so)
==4669== Address 0x645e9e8 is 8 bytes inside a block of size 752 alloc'd
==4669== at 0x4C2DA51: calloc (vg_replace_malloc.c:762)
==4669== by 0x4E5D612: _gfortrani_xcalloc (memory.c:78)
==4669== by 0x50A2B17: insert_unit (unit.c:233)
==4669== by 0x50A2D77: get_gfc_unit (unit.c:356)
==4669== by 0x509A788: _gfortran_st_open (open.c:889)
==4669== by 0x400BED: MAIN__._omp_fn.0 (in /tmp/a.out)
==4669== by 0x5611065: gomp_thread_start (team.c:123)
==4669== by 0x4C315BD: mythread_wrapper (hg_intercepts.c:389)
==4669== by 0x5C9A723: start_thread (in /lib64/libpthread-2.22.so)
==4669== by 0x5F9BE8C: clone (in /lib64/libc-2.22.so)
==4669== Block was alloc'd by thread #5
...
>From gcc-bugs-return-662670-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 16:34:16 2019
Return-Path: <gcc-bugs-return-662670-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110053 invoked by alias); 8 Dec 2019 16:34: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 98285 invoked by uid 48); 8 Dec 2019 16:34:12 -0000
From: "thiago at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92855] -fvisibility-inlines-hidden failing to hide out-of-line copies of certain inline member functions
Date: Sun, 08 Dec 2019 16:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: visibility
X-Bugzilla-Severity: normal
X-Bugzilla-Who: thiago at kde dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92855-4-Z8RmCJPfCz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00740.txt.bz2
Content-length: 899
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92855
--- Comment #3 from Thiago Macieira <thiago at kde dot org> ---
The symbol in question is inline, therefore -fvisibility-inlines-hidden should
trigger and cause it to become hidden too.
Testcase showing that GCC will apply that:
#define VISIBILITY(x) __attribute__((visibility(#x)))
namespace N VISIBILITY(default) {
void other();
inline void f()
{
other();
}
void g() { f(); }
}
If you compile this with -fno-inline to cause f() to be emitted, you'll see:
.section .text.N::f(),"axG",@progbits,N::f(),comdat
.p2align 4
.weak N::f()
.hidden N::f()
.type N::f(), @function
N::f():
jmp N::other()
.size N::f(), .-N::f()
See: https://gcc.godbolt.org/z/nW3RbX
So I contend that the symbol should have been hidden and wasn't because of a
bug. Please reconsider.
>From gcc-bugs-return-662671-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 20:04:40 2019
Return-Path: <gcc-bugs-return-662671-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95500 invoked by alias); 8 Dec 2019 20:04: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 95405 invoked by uid 48); 8 Dec 2019 20:04:36 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92855] -fvisibility-inlines-hidden failing to hide out-of-line copies of certain inline member functions
Date: Sun, 08 Dec 2019 20: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: 9.2.1
X-Bugzilla-Keywords: visibility
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: cc
Message-ID: <bug-92855-4-fD13huK7zP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00741.txt.bz2
Content-length: 765
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92855
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #4 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(FWIW, making 'f' a template in your example makes it non-hidden)
Can you explain why you expect the command-line option to override the
attribute on the namespace? GCC usually implements the opposite, i.e.
attributes prevail over the defaults specified on the command line.
In your sample on Godbolt, Clang also appears to honour the attribute rather
than the option.
>From gcc-bugs-return-662672-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 20:12:48 2019
Return-Path: <gcc-bugs-return-662672-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109492 invoked by alias); 8 Dec 2019 20:12:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109416 invoked by uid 48); 8 Dec 2019 20:12:43 -0000
From: "pavel.kryukov at phystech dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65424] gcc does not recognize byte swaps implemented as loop.
Date: Sun, 08 Dec 2019 20:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pavel.kryukov at phystech dot edu
X-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-65424-4-MoROaS7mGQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65424-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65424-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00742.txt.bz2
Content-length: 686
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65424
Pavel I. Kryukov <pavel.kryukov at phystech dot edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pavel.kryukov at phystech dot edu
--- Comment #5 from Pavel I. Kryukov <pavel.kryukov at phystech dot edu> ---
Could you please tell if there is any progress?
I use C++ templates to do low-level byte operations for BE CPU simulator hosted
on LE machine. The example is here: https://godbolt.org/z/ff-NAF (I replaced
template type with a define, but it does not change output a lot).
>From gcc-bugs-return-662673-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 20:16:15 2019
Return-Path: <gcc-bugs-return-662673-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119100 invoked by alias); 8 Dec 2019 20: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 118954 invoked by uid 48); 8 Dec 2019 20:16:10 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92858] [10 regression] spurious backslashes around switch string in warning messages
Date: Sun, 08 Dec 2019 20:16: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: diagnostic
X-Bugzilla-Severity: minor
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-92858-4-ZHP9ftQSnk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92858-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00743.txt.bz2
Content-length: 403
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92858
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> ---
In konsole? See PR87488.
>From gcc-bugs-return-662674-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 21:10:22 2019
Return-Path: <gcc-bugs-return-662674-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103127 invoked by alias); 8 Dec 2019 21:10: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 103074 invoked by uid 48); 8 Dec 2019 21:10:18 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92856] incorrectly accepts invalid C++11 braced initialisation of double from long double
Date: Sun, 08 Dec 2019 21:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
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-92856-4-Kp8uZOnCar@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92856-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92856-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00744.txt.bz2
Content-length: 585
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92856
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The standard requires a diagnostic for this, and GCC issues a diagnostic. The
behaviour is by design and not a bug.
Use -Werror=narrowing if you want an error.
>From gcc-bugs-return-662675-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 21:13:35 2019
Return-Path: <gcc-bugs-return-662675-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106115 invoked by alias); 8 Dec 2019 21:13: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 106058 invoked by uid 48); 8 Dec 2019 21:13:31 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92850] clang has already supported concepts in latest trunk. However it does not define __cpp_concepts macro. I defined it but crashes clang compiler
Date: Sun, 08 Dec 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: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: 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-92850-4-Q9WLfQSY8G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92850-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00745.txt.bz2
Content-length: 299
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92850
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
If the macro is not defined it's either a clang bug, or is intentional because
the implementation is not finished.
It is undefined for you to define any __cpp* macro yourself.
>From gcc-bugs-return-662676-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 21:40:18 2019
Return-Path: <gcc-bugs-return-662676-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101371 invoked by alias); 8 Dec 2019 21: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 101302 invoked by uid 48); 8 Dec 2019 21:40:13 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92850] clang has already supported concepts in latest trunk. However it does not define __cpp_concepts macro. I defined it but crashes clang compiler
Date: Sun, 08 Dec 2019 21: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: 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-92850-4-SSPE0spVLh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92850-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00746.txt.bz2
Content-length: 396
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92850
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to fdlbxtqi from comment #2)
> "Are you sure concepts are fully implemented in clang?"
>
> Yes, but feature testing macro is missing.
No, it very obviously doesn't support concepts:
https://godbolt.org/z/n4AkpC
So that will be why it doesn't define the macro.
>From gcc-bugs-return-662677-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 21:41:04 2019
Return-Path: <gcc-bugs-return-662677-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110522 invoked by alias); 8 Dec 2019 21:41: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 105556 invoked by uid 48); 8 Dec 2019 21:41:00 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92853] std::filesystem::path::operator+=(std::filesystem::path const&) corrupts the heap
Date: Sun, 08 Dec 2019 21:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
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 cf_reconfirmed_on assigned_to target_milestone everconfirmed
Message-ID: <bug-92853-4-13UuNqrVYX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92853-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92853-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00747.txt.bz2
Content-length: 542
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92853
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-08
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Target Milestone|--- |9.3
Ever confirmed|0 |1
>From gcc-bugs-return-662678-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 22:08:14 2019
Return-Path: <gcc-bugs-return-662678-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47004 invoked by alias); 8 Dec 2019 22:08: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 46902 invoked by uid 48); 8 Dec 2019 22:08:10 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92858] [10 regression] spurious backslashes around switch string in warning messages
Date: Sun, 08 Dec 2019 22:08: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: diagnostic
X-Bugzilla-Severity: minor
X-Bugzilla-Who: ebotcazou 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-92858-4-0sgoLFXpxG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92858-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00748.txt.bz2
Content-length: 516
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92858
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Yes, thanks, I missed it.
*** This bug has been marked as a duplicate of bug 87488 ***
>From gcc-bugs-return-662679-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 22:08:15 2019
Return-Path: <gcc-bugs-return-662679-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47131 invoked by alias); 8 Dec 2019 22: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 46953 invoked by uid 48); 8 Dec 2019 22:08:11 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87488] hyperlink filenames in diagnostics
Date: Sun, 08 Dec 2019 22:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
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: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87488-4-Mh3VG4fFBU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00749.txt.bz2
Content-length: 454
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87488
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebotcazou at gcc dot gnu.org
--- Comment #21 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
*** Bug 92858 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-662680-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 23:08:47 2019
Return-Path: <gcc-bugs-return-662680-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14701 invoked by alias); 8 Dec 2019 23:08: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 14635 invoked by uid 48); 8 Dec 2019 23:08:42 -0000
From: "thiago at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92855] -fvisibility-inlines-hidden failing to hide out-of-line copies of certain inline member functions
Date: Sun, 08 Dec 2019 23:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: visibility
X-Bugzilla-Severity: normal
X-Bugzilla-Who: thiago at kde dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92855-4-Mj2qcaduIv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00750.txt.bz2
Content-length: 2096
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92855
--- Comment #5 from Thiago Macieira <thiago at kde dot org> ---
(In reply to Alexander Monakov from comment #4)
> (FWIW, making 'f' a template in your example makes it non-hidden)
>
> Can you explain why you expect the command-line option to override the
> attribute on the namespace? GCC usually implements the opposite, i.e.
> attributes prevail over the defaults specified on the command line.
>
> In your sample on Godbolt, Clang also appears to honour the attribute rather
> than the option.
And ICC does the opposite and hides everything. Either way, GCC's behaviour of
applying this to templates (which is bug 47877, so you may close as duplicate)
is unexpected and seems inconsistent.
I expect the emitted function to be hidden because it's inline and because of
-fvisibility-inlines-hidden. From the TexInfo manual:
The effect of this is that GCC may, effectively, mark inline
methods with '__attribute__ ((visibility ("hidden")))' so that they
do not appear in the export table of a DSO and do not require a PLT
indirection when used within the DSO. Enabling this option can
have a dramatic effect on load and link times of a DSO as it
massively reduces the size of the dynamic export table when the
library makes heavy use of templates.
Since the out-of-line copies of the inline functions will be emitted in every
TU that failed to inline them, and thus remain in every DSO, there's no need to
export them. Each DSO can call its own, local copy through PC-relative calls
and jumps.
For the particular problem at hand, which we're still debugging, see
https://bugreports.qt.io/browse/QTBUG-80535. The issue there is that certain
non-Qt symbols were exported by the DSO and thus got tagged with the ELF
version "Qt_5". That by itself is not a problem, but we've found that some
applications began referencing those symbols with that ELF version and we don't
understand why. The result is that the internal details of how something was
implemented became part of our ABI.
>From gcc-bugs-return-662681-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 23:25:41 2019
Return-Path: <gcc-bugs-return-662681-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47211 invoked by alias); 8 Dec 2019 23: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 47121 invoked by uid 48); 8 Dec 2019 23:25:36 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92853] std::filesystem::path::operator+=(std::filesystem::path const&) corrupts the heap
Date: Sun, 08 Dec 2019 23:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.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: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92853-4-tBCtfEdNpv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92853-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92853-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00751.txt.bz2
Content-length: 1445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92853
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The problem is that the trailing slash in the right operand gets processed
twice:
977 if (it != last && it->_M_type() == _Type::_Root_dir)
978 {
979 ++it;
980 if (it == last)
981 {
982 // This root-dir becomes a trailing slash
983 auto pos = _M_pathname.length() + p._M_pathname.length();
984 ::new(output++) _Cmpt({}, _Type::_Filename, pos);
985 ++_M_cmpts._M_impl->_M_size;
986 }
987 }
...
999 if (is_dir_sep(_M_pathname.back()))
1000 {
1001 ::new(output++) _Cmpt({}, _Type::_Filename, _M_pathname.length());
1002 ++_M_cmpts._M_impl->_M_size;│
1003 }
Which is easily fixed:
--- a/libstdc++-v3/src/c++17/fs_path.cc
+++ b/libstdc++-v3/src/c++17/fs_path.cc
@@ -975,16 +975,7 @@ path::operator+=(const path& p)
}
if (it != last && it->_M_type() == _Type::_Root_dir)
- {
- ++it;
- if (it == last)
- {
- // This root-dir becomes a trailing slash
- auto pos = _M_pathname.length() + p._M_pathname.length();
- ::new(output++) _Cmpt({}, _Type::_Filename, pos);
- ++_M_cmpts._M_impl->_M_size;
- }
- }
+ ++it;
while (it != last)
{
>From gcc-bugs-return-662682-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 23:28:51 2019
Return-Path: <gcc-bugs-return-662682-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50267 invoked by alias); 8 Dec 2019 23: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 50220 invoked by uid 48); 8 Dec 2019 23:28:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92856] incorrectly accepts invalid C++11 braced initialisation of double from long double
Date: Sun, 08 Dec 2019 23:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92856-4-d5OkZQkLDK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92856-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92856-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00752.txt.bz2
Content-length: 729
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92856
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> The behaviour is by design
And documented, see
https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Dialect-Options.html#index-Wnarrowing
"For C++11 and later standards, narrowing conversions are diagnosed by default,
as required by the standard. A narrowing conversion from a constant produces an
error, and a narrowing conversion from a non-constant produces a warning, but
-Wno-narrowing suppresses the diagnostic. Note that this does not affect the
meaning of well-formed code; narrowing conversions are still considered
ill-formed in SFINAE contexts."
>From gcc-bugs-return-662683-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 23:31:32 2019
Return-Path: <gcc-bugs-return-662683-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52994 invoked by alias); 8 Dec 2019 23:31: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 52941 invoked by uid 48); 8 Dec 2019 23:31:28 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92859] compiler treats enum type as an integer during overload resolution when a bit-field of this enum is considered
Date: Sun, 08 Dec 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: c++
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords: wrong-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 bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-92859-4-OoLc6BoOHa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92859-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92859-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00753.txt.bz2
Content-length: 649
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92859
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-08
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
N.B. GCC 7 is no longer supported by the GCC project.
Confirmed as a bug in supported releases though (and svn trunk).
>From gcc-bugs-return-662684-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Dec 08 23:32:27 2019
Return-Path: <gcc-bugs-return-662684-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54227 invoked by alias); 8 Dec 2019 23:32: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 54167 invoked by uid 48); 8 Dec 2019 23:32:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92851] Lambda capture of *this with mutable is not mutable
Date: Sun, 08 Dec 2019 23:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 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-92851-4-CSjHR80PQf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92851-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00754.txt.bz2
Content-length: 560
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92851
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-12-08
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Please provide a complete testcase not a URL, as required by
https://gcc.gnu.org/bugs/
>From gcc-bugs-return-662685-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 00:48:55 2019
Return-Path: <gcc-bugs-return-662685-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47304 invoked by alias); 9 Dec 2019 00:48: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 46976 invoked by uid 48); 9 Dec 2019 00:48:46 -0000
From: "flast at flast dot jp" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92851] Lambda capture of *this with mutable is not mutable
Date: Mon, 09 Dec 2019 00:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: flast at flast dot jp
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-92851-4-KEhW416fH4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92851-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00755.txt.bz2
Content-length: 656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92851
--- Comment #2 from Kohei Takahashi <flast at flast dot jp> ---
(In reply to Jonathan Wakely from comment #1)
> Please provide a complete testcase not a URL, as required by
> https://gcc.gnu.org/bugs/
Sorry, here is reproducible complete code.
----
struct S
{
int a;
void foo() const
{
[*this]() mutable
{
a = 0;
}();
}
};
----
GCC rejects with following message, but clang not.
----
prog.cc: In lambda function:
prog.cc:9:15: error: assignment of member 'S::a' in read-only object
9 | a = 0;
| ~~^~~
----
>From gcc-bugs-return-662686-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 01:11:13 2019
Return-Path: <gcc-bugs-return-662686-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38479 invoked by alias); 9 Dec 2019 01:11: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 38416 invoked by uid 48); 9 Dec 2019 01:11:08 -0000
From: "samuel.thibault@ens-lyon.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92861] New: Passes relative time to sem_timedwait on GNU/Hurd
Date: Mon, 09 Dec 2019 01:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: samuel.thibault@ens-lyon.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone attachments.created
Message-ID: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00756.txt.bz2
Content-length: 865
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92861
Bug ID: 92861
Summary: Passes relative time to sem_timedwait on GNU/Hurd
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: samuel.thibault@ens-lyon.org
CC: cmang at google dot com
Target Milestone: ---
Created attachment 47442
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47442&action=edit
proposed fix
In src/libgo/go/runtime/os_hurd.go, a relative time is set in var ts, and &ts
is passed to sem_timedwait. But sem_timedwait expects an absolute time, not a
relative time. The attached patch fixes this by using the time from
clock_gettime(CLOCK_REALTIME), like is done in os_aix.go.
>From gcc-bugs-return-662687-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 01:26:14 2019
Return-Path: <gcc-bugs-return-662687-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64630 invoked by alias); 9 Dec 2019 01:26: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 64585 invoked by uid 48); 9 Dec 2019 01:26:10 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92822] [10 Regression] testsuite failures on aarch64 after r278938
Date: Mon, 09 Dec 2019 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: 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: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-92822-4-UWb7e9OibJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00757.txt.bz2
Content-length: 997
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92822
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-09
CC| |pinskia at gcc dot gnu.org
Target Milestone|--- |10.0
Summary|regressions on aarch64 |[10 Regression] testsuite
|after r278938 |failures on aarch64 after
| |r278938
Ever confirmed|0 |1
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.
>FAIL: gcc.target/aarch64/singleton_intrinsics_1.c scan-assembler-times aarch64_get_lanev2di 2
Works now.
>From gcc-bugs-return-662688-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 03:44:14 2019
Return-Path: <gcc-bugs-return-662688-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78100 invoked by alias); 9 Dec 2019 03:44: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 77364 invoked by uid 55); 9 Dec 2019 03:44:06 -0000
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92861] Passes relative time to sem_timedwait on GNU/Hurd
Date: Mon, 09 Dec 2019 03:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92861-4-gy2yk6DIE2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00758.txt.bz2
Content-length: 522
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92861
--- Comment #1 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Mon Dec 9 03:43:33 2019
New Revision: 279106
URL: https://gcc.gnu.org/viewcvs?rev=279106&root=gcc&view=rev
Log:
PR go/92861
runtime: use absolute time for sem_timedwait
Patch by Samuel Thibault.
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/210457
Modified:
trunk/gcc/go/gofrontend/MERGE
trunk/libgo/go/runtime/os_hurd.go
>From gcc-bugs-return-662689-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 03:53:08 2019
Return-Path: <gcc-bugs-return-662689-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111658 invoked by alias); 9 Dec 2019 03: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 111583 invoked by uid 48); 9 Dec 2019 03:53:02 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92861] Passes relative time to sem_timedwait on GNU/Hurd
Date: Mon, 09 Dec 2019 03:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92861-4-qgdP3cd7sE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00759.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92861
Ian Lance Taylor <ian at airs dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Ian Lance Taylor <ian at airs dot com> ---
Thanks, committed.
>From gcc-bugs-return-662690-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 04:17:34 2019
Return-Path: <gcc-bugs-return-662690-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22935 invoked by alias); 9 Dec 2019 04:17: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 22837 invoked by uid 55); 9 Dec 2019 04:17:28 -0000
From: "liuhongt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92686] Inefficient mask operation for 128/256-bit vector VCOND_EXPR under avx512f
Date: Mon, 09 Dec 2019 04: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: enhancement
X-Bugzilla-Who: liuhongt 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-92686-4-7JsajIKFbV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92686-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92686-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00760.txt.bz2
Content-length: 3092
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92686
--- Comment #5 from liuhongt at gcc dot gnu.org ---
Author: liuhongt
Date: Mon Dec 9 04:16:24 2019
New Revision: 279107
URL: https://gcc.gnu.org/viewcvs?rev=279107&root=gcc&view=rev
Log:
Enable mask movement for VCOND_EXPR under avx512f for
128/256-bit vector when integer mask is available.
Changelog
gcc/
PR target/92686
* config/i386/sse.md
(*<avx512>_cmp<mode>3<mask_scalar_merge_name><round_saeonly_name>,
*<avx512>_cmp<mode>3<mask_scalar_merge_name>,
*<avx512>_ucmp<mode>3<mask_scalar_merge_name>,
*<avx512>_ucmp<mode>3<mask_scalar_merge_name>): New.
* config/i386/i386.c (ix86_print_operand): New operand substitution.
* config/i386/i386-expand.c (ix86_valid_mask_cmp_mode):
New function.
(ix86_expand_sse_cmp): Relax condition for integer mask from
512-bit vector to all 128/256/512-bit vector. Delete code gen
for avx512f compare patterns since we have generic pattern now.
(ix86_expand_sse_movcc): Adjust condition and codegen for
maskcmp.
(ix86_expand_int_sse_cmp): Don't canonicalize the comparison
when corresponding vector compare is available.
gcc/testsuite/
* gcc.target/i386/pr92686.inc: New file.
* gcc.target/i386/avx512bw-pr92686-vpcmp-1.c: New test.
* gcc.target/i386/avx512bw-pr92686-vpcmp-intelasm-1.c: Ditto.
* gcc.target/i386/avx512bw-pr92686-vpcmp-2.c: Ditto.
* gcc.target/i386/avx512vl-pr92686-vpcmp-1.c: Ditto.
* gcc.target/i386/avx512vl-pr92686-vpcmp-intelasm-1.c: Ditto.
* gcc.target/i386/avx512vl-pr92686-vpcmp-2.c: Ditto.
* gcc.target/i386/avx512bw-pr92686-movcc-1.c: Ditto.
* gcc.target/i386/avx512bw-pr92686-movcc-2.c: Ditto.
* gcc.target/i386/avx512vl-pr92686-movcc-1.c: Ditto.
* gcc.target/i386/avx512vl-pr92686-movcc-2.c: Ditto.
* gcc.target/i386/avx512vl-pr88547-1.c: Adjust testcase.
* gcc.target/i386/pr88547-1.c: Ditto.
Added:
trunk/gcc/testsuite/gcc.target/i386/avx512bw-pr92686-movcc-1.c
trunk/gcc/testsuite/gcc.target/i386/avx512bw-pr92686-movcc-2.c
trunk/gcc/testsuite/gcc.target/i386/avx512bw-pr92686-vpcmp-1.c
trunk/gcc/testsuite/gcc.target/i386/avx512bw-pr92686-vpcmp-2.c
trunk/gcc/testsuite/gcc.target/i386/avx512bw-pr92686-vpcmp-intelasm-1.c
trunk/gcc/testsuite/gcc.target/i386/avx512vl-pr92686-movcc-1.c
trunk/gcc/testsuite/gcc.target/i386/avx512vl-pr92686-movcc-2.c
trunk/gcc/testsuite/gcc.target/i386/avx512vl-pr92686-vpcmp-1.c
trunk/gcc/testsuite/gcc.target/i386/avx512vl-pr92686-vpcmp-2.c
trunk/gcc/testsuite/gcc.target/i386/avx512vl-pr92686-vpcmp-intelasm-1.c
trunk/gcc/testsuite/gcc.target/i386/pr92686.inc
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386-expand.c
trunk/gcc/config/i386/i386.c
trunk/gcc/config/i386/sse.md
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.target/i386/avx512vl-pr88547-1.c
trunk/gcc/testsuite/gcc.target/i386/pr88547-1.c
>From gcc-bugs-return-662691-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 04:25:00 2019
Return-Path: <gcc-bugs-return-662691-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120761 invoked by alias); 9 Dec 2019 04: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 120046 invoked by uid 48); 9 Dec 2019 04:24:28 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/80969] [8 Regression] ICE in ix86_expand_prologue, at config/i386/i386.c:14606
Date: Mon, 09 Dec 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: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: crazylht at gmail dot com
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: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-80969-4-cO85kqTSah@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80969-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80969-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00761.txt.bz2
Content-length: 2101
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80969
Hongtao.liu <crazylht at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |crazylht at gmail dot com
--- Comment #8 from Hongtao.liu <crazylht at gmail dot com> ---
ICE in r279107, I think my patch trigger some potential bug.
/export/users/liuhongt/gcc/gnu-toolchain/gcc/gcc/testsuite/gcc.target/i386/pr80969-1.c:
In function ‘main’:
/export/users/liuhongt/gcc/gnu-toolchain/gcc/gcc/testsuite/gcc.target/i386/pr80969-1.c:16:1:
internal compiler error: in sp_valid_at, at config/i386/i386.c:6160
0x747bd7 sp_valid_at
../../../gcc/gnu-toolchain/gcc/gcc/config/i386/i386.c:6160
0x10ded88 choose_basereg
../../../gcc/gnu-toolchain/gcc/gcc/config/i386/i386.c:6196
0x10df115 choose_baseaddr
../../../gcc/gnu-toolchain/gcc/gcc/config/i386/i386.c:6309
0x10df1b6 ix86_emit_save_reg_using_mov
../../../gcc/gnu-toolchain/gcc/gcc/config/i386/i386.c:6358
0x10f450e ix86_emit_save_sse_regs_using_mov
../../../gcc/gnu-toolchain/gcc/gcc/config/i386/i386.c:6447
0x10f55b0 ix86_expand_prologue()
../../../gcc/gnu-toolchain/gcc/gcc/config/i386/i386.c:8248
0x14368ba gen_prologue()
../../../gcc/gnu-toolchain/gcc/gcc/config/i386/i386.md:13130
0x10e5988 target_gen_prologue
../../../gcc/gnu-toolchain/gcc/gcc/config/i386/i386.md:19667
0xabcdb7 make_prologue_seq
../../../gcc/gnu-toolchain/gcc/gcc/function.c:5779
0xabcf82 thread_prologue_and_epilogue_insns()
../../../gcc/gnu-toolchain/gcc/gcc/function.c:5896
0xabd672 rest_of_handle_thread_prologue_and_epilogue
../../../gcc/gnu-toolchain/gcc/gcc/function.c:6387
0xabd672 execute
../../../gcc/gnu-toolchain/gcc/gcc/function.c:6463
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.
Same error for pr80969-4.c.
>From gcc-bugs-return-662692-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 04:25:33 2019
Return-Path: <gcc-bugs-return-662692-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122497 invoked by alias); 9 Dec 2019 04: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 122384 invoked by uid 48); 9 Dec 2019 04:25:28 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92686] Inefficient mask operation for 128/256-bit vector VCOND_EXPR under avx512f
Date: Mon, 09 Dec 2019 04:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: crazylht at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92686-4-YvyHcWwBIN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92686-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92686-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00762.txt.bz2
Content-length: 430
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92686
Hongtao.liu <crazylht at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Hongtao.liu <crazylht at gmail dot com> ---
Fixed in GCC10.
>From gcc-bugs-return-662693-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 05:09:31 2019
Return-Path: <gcc-bugs-return-662693-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52544 invoked by alias); 9 Dec 2019 05:09:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52480 invoked by uid 48); 9 Dec 2019 05:09:27 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/12955] Incorrect rounding of soft float denorm mul/div
Date: Mon, 09 Dec 2019 05: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: 3.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: eager at mvista dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-12955-4-KhAsYpRIKv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-12955-4@http.gcc.gnu.org/bugzilla/>
References: <bug-12955-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00763.txt.bz2
Content-length: 611
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12955
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |geoffk at gcc dot gnu.org
--- Comment #14 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #8)
> I could not find any more mention of this after
> <http://gcc.gnu.org/ml/gcc-patches/2003-11/msg00699.html>,
> was there another patch.
cc-ing Geoffrey Keating from that thread
>From gcc-bugs-return-662694-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 05:23:46 2019
Return-Path: <gcc-bugs-return-662694-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73073 invoked by alias); 9 Dec 2019 05:23: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 72442 invoked by uid 48); 9 Dec 2019 05:23:42 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/29997] [meta-bug] various targets: GCC fails to encode epilogues in unwind-info
Date: Mon, 09 Dec 2019 05: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: 4.3.0
X-Bugzilla-Keywords: EH, meta-bug, wrong-code, wrong-debug
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-29997-4-agvWVbpM37@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-29997-4@http.gcc.gnu.org/bugzilla/>
References: <bug-29997-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00764.txt.bz2
Content-length: 849
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29997
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rth at gcc dot gnu.org
--- Comment #8 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Ian Lance Taylor from comment #6)
> All the insns in sh_expand_epilogue need to be examined to see if they need
> REG_CFA notes. Some of them already have them. I don't know what more are
> needed.
>
> For example, look at the changes made to the i386 backend when rth added the
> general support for unwinding through epilogues:
> http://gcc.gnu.org/ml/gcc-patches/2009-05/msg00277.html
cc-ing rth then, if his changes are relevant here...
>From gcc-bugs-return-662695-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 06:35:53 2019
Return-Path: <gcc-bugs-return-662695-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77314 invoked by alias); 9 Dec 2019 06: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 77278 invoked by uid 48); 9 Dec 2019 06:35:49 -0000
From: "fxue at os dot amperecomputing.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92862] New: Suspicious codes in tree-ssa-loop-niter.c and predict.c
Date: Mon, 09 Dec 2019 06:35: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-92862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00765.txt.bz2
Content-length: 1337
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92862
Bug ID: 92862
Summary: Suspicious codes in tree-ssa-loop-niter.c and
predict.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: ---
Function loop_only_exit_p() in tree-ssa-loop-niter.c:
for (i = 0; i < loop->num_nodes; i++)
{
for (bsi = gsi_start_bb (body[i]); !gsi_end_p (bsi); gsi_next (&bsi))
if (stmt_can_terminate_bb_p (gsi_stmt (bsi)))
{
return true;
}
}
we should return false, not true?
Function predict_paths_leading_to_edge() in predict.c:
FOR_EACH_EDGE (e2, ei, bb->succs)
if (e2->dest != e->src && e2->dest != e->dest
&& !unlikely_executed_edge_p (e)
&& !dominated_by_p (CDI_POST_DOMINATORS, e->src, e2->dest))
{
has_nonloop_edge = true;
break;
}
"e" is loop invariant, I guess that unlikely_executed_edge_p (e) might be
unlikely_executed_edge_p (e2), which is more reasonable. And we can find
similar code in predict_paths_for_bb () that uses the latter.
>From gcc-bugs-return-662696-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 06:37:35 2019
Return-Path: <gcc-bugs-return-662696-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78891 invoked by alias); 9 Dec 2019 06: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 78843 invoked by uid 48); 9 Dec 2019 06:37:30 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92863] New: ICE in gfc_typename
Date: Mon, 09 Dec 2019 06:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92863-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00766.txt.bz2
Content-length: 2704
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92863
Bug ID: 92863
Summary: ICE in gfc_typename
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: error-recovery, ice-on-invalid-code
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
gfortran-10.0.0-alpha20191208 snapshot (r279100) ICEs when compiling the
following testcase:
type(l1) function mp()
call sub(mp)
end function mp
function bi(ry)
call sub(ry)
end function bi
% powerpc-e300c3-linux-gnu-gfortran-10.0.0-alpha20191208 -c pws8056f.f90
pws8056f.f90:1:0:
1 | type(l1) function mp()
|
Error: The type for function 'mp' at (1) is not accessible
f951: internal compiler error: Segmentation fault
0xe74916 crash_signal
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/toplev.c:328
0x860c1b sprintf
/usr/include/bits/stdio2.h:36
0x860c1b gfc_typename(gfc_typespec*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/fortran/misc.c:167
0x834466 compare_parameter
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/fortran/interface.c:2399
0x834466 gfc_compare_actual_formal(gfc_actual_arglist**, gfc_formal_arglist*,
int, int, bool, locus*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/fortran/interface.c:3149
0x9749ef check_externals_procedure
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/fortran/frontend-passes.c:5410
0x97a9a3 gfc_code_walker(gfc_code**, int (*)(gfc_code**, int*, void*), int
(*)(gfc_expr**, int*, void*), void*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/fortran/frontend-passes.c:5039
0x97c24f gfc_check_externals(gfc_namespace*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/fortran/frontend-passes.c:5496
0x885704 gfc_parse_file()
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/fortran/parse.c:6494
0x8d3fbe gfc_be_parse_file
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/fortran/f95-lang.c:210
>From gcc-bugs-return-662697-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 07:35:45 2019
Return-Path: <gcc-bugs-return-662697-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47491 invoked by alias); 9 Dec 2019 07: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 47444 invoked by uid 48); 9 Dec 2019 07:35:41 -0000
From: "thenlich+gccbug at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/90374] Fortran 2018: Support d0.d, e0.d, es0.d, en0.d, g0.d and ew.d e0 edit descriptors for output
Date: Mon, 09 Dec 2019 07:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: thenlich+gccbug at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90374-4-3XYA6omj2J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90374-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90374-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00767.txt.bz2
Content-length: 1245
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90374
--- Comment #10 from Thomas Henlich <thenlich+gccbug at gmail dot com> ---
(In reply to Jerry DeLisle from comment #5)
> Author: jvdelisle
> Date: Thu Nov 28 18:33:20 2019
> New Revision: 278817
>
> URL: https://gcc.gnu.org/viewcvs?rev=278817&root=gcc&view=rev
> Log:
> PR fortran/90374
> * io.c (check_format): Allow zero width expoenent with e0.
>
> * io/format.c (parse_format_list): Relax format checking to allow
> e0 exponent specifier.
>
> * gfortran.dg/fmt_zero_width.f90: Update test.
>
> Modified:
> trunk/gcc/fortran/ChangeLog
> trunk/gcc/fortran/io.c
> trunk/gcc/testsuite/ChangeLog
> trunk/gcc/testsuite/gfortran.dg/fmt_zero_width.f90
> trunk/libgfortran/ChangeLog
> trunk/libgfortran/io/format.c
> trunk/libgfortran/io/write_float.def
fmt_zero_width.f90:
..
write (aresult,fmt="(E0.10e0)") rn
if (aresult /= "0.3139999928E-02") stop 39
Shouldn't that be (according to Fortran 2018):
if (aresult /= "0.3139999928E-2") stop 39
13.7.2.3.3 E and D editing
... If e is positive the exponent part contains e digits, otherwise it
contains the minimum number of digits required to represent the exponent value.
...
>From gcc-bugs-return-662698-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 08:42:33 2019
Return-Path: <gcc-bugs-return-662698-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115036 invoked by alias); 9 Dec 2019 08:42: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 114903 invoked by uid 48); 9 Dec 2019 08:42:30 -0000
From: "iii at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)
Date: Mon, 09 Dec 2019 08: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: EH, ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iii at linux dot ibm.com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92007-4-gBUcEpFydx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00768.txt.bz2
Content-length: 594
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007
--- Comment #24 from Ilya Leoshkevich <iii at linux dot ibm.com> ---
I got the following results on gcc113:
400.perlbench
Compiler flags: -DSPEC_CPU -DNDEBUG -DPERL_CORE -march=native -g -O3
-funroll-loops -fopt-info-vec-optimized -DSPEC_CPU -DNDEBUG -DPERL_CORE
-DSPEC_CPU_LINUX -DSPEC_CPU_BIGENDIAN -D_GNU_SOURCE -DSPEC_CPU_LP64
-fno-strict-aliasing -std=gnu90
r277511 (without this fix): 884.11s
r277515 (with this fix): 874.93s
Maxim, could you please share compiler flags with which you are seeing the
regression?
>From gcc-bugs-return-662699-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 08:54:28 2019
Return-Path: <gcc-bugs-return-662699-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46910 invoked by alias); 9 Dec 2019 08:54: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 46853 invoked by uid 48); 9 Dec 2019 08:54:24 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92844] [10 regression] libgomp.fortran/use_device_ptr-optional-2.f90 fails after r279004
Date: Mon, 09 Dec 2019 08:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
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: target_milestone
Message-ID: <bug-92844-4-mYgrnXNOTE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92844-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92844-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00769.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92844
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-662700-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 08:59:12 2019
Return-Path: <gcc-bugs-return-662700-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59023 invoked by alias); 9 Dec 2019 08:59: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 58953 invoked by uid 48); 9 Dec 2019 08:59:03 -0000
From: "rguenth 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: Mon, 09 Dec 2019 08: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.0
X-Bugzilla-Keywords: ice-checking, 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work version keywords cf_reconfirmed_on cc everconfirmed short_desc target_milestone cf_known_to_fail
Message-ID: <bug-92852-4-BoBgOeJcI6@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: 2019-12/txt/msg00770.txt.bz2
Content-length: 1216
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92852
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Known to work| |7.5.0
Version|unknown |9.2.0
Keywords| |ice-checking,
| |needs-bisection
Last reconfirmed| |2019-12-09
CC| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
Summary|location references block |[8/9/10 Regression]
|not in block tree |location references block
| |not in block tree
Target Milestone|--- |8.4
Known to fail| |10.0, 8.1.0, 8.3.0, 9.2.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. This can lead to compiler memory corruption and all sorts of nasty
effects.
>From gcc-bugs-return-662701-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:01:28 2019
Return-Path: <gcc-bugs-return-662701-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64650 invoked by alias); 9 Dec 2019 09:01: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 64453 invoked by uid 55); 9 Dec 2019 09:01:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92737] cgraph_node and varpool_node needs explicit constructor
Date: Mon, 09 Dec 2019 09: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: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92737-4-NY925Sk5Qm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00771.txt.bz2
Content-length: 1064
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92737
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Mon Dec 9 09:00:42 2019
New Revision: 279109
URL: https://gcc.gnu.org/viewcvs?rev=279109&root=gcc&view=rev
Log:
Come up with constructors of symtab_node, cgraph_node and varpool_node.
2019-12-09 Martin Liska <mliska@suse.cz>
PR ipa/92737
* cgraph.c (symbol_table_test::symbol_table_test): Fix
coding style.
* cgraph.h (symtab_node::symtab_node): New constructor.
(cgraph_node::cgraph_node): Likewise.
(varpool_node::varpool_node): Likewise.
(symbol_table::allocate_cgraph_symbol): Use newly
created constructor.
(symbol_table::allocate_cgraph_symbol): Remove.
* cgraphunit.c (symtab_terminator): Likewise.
* varpool.c (varpool_node::create_empty): Use newly
created constructor.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/cgraph.c
trunk/gcc/cgraph.h
trunk/gcc/cgraphunit.c
trunk/gcc/varpool.c
>From gcc-bugs-return-662702-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:02:27 2019
Return-Path: <gcc-bugs-return-662702-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91704 invoked by alias); 9 Dec 2019 09: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 91620 invoked by uid 48); 9 Dec 2019 09:02:19 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92857] -Wsign-conversion flag issues false positives for expression using typedef'ed unsigned types
Date: Mon, 09 Dec 2019 09:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords: diagnostic
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_known_to_fail
Message-ID: <bug-92857-4-LXK6oo3n5z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92857-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00772.txt.bz2
Content-length: 603
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92857
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Known to fail| |9.2.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think the warning is about foo - bar being carried out in type 'int' due to
integer promotion and that converted to size_t which may turn the negative
result into a positive.
>From gcc-bugs-return-662703-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:03:15 2019
Return-Path: <gcc-bugs-return-662703-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109217 invoked by alias); 9 Dec 2019 09:03: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 108250 invoked by uid 48); 9 Dec 2019 09:03:10 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92860] [8/9/10 regression] Global flags affected by -O settings are clobbered by optimize attribute
Date: Mon, 09 Dec 2019 09: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: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-92860-4-FPSomJczTp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00773.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92860
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.4
>From gcc-bugs-return-662704-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:05:37 2019
Return-Path: <gcc-bugs-return-662704-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112126 invoked by alias); 9 Dec 2019 09:05: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 112070 invoked by uid 48); 9 Dec 2019 09:05:33 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92862] Suspicious codes in tree-ssa-loop-niter.c and predict.c
Date: Mon, 09 Dec 2019 09:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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-92862-4-dzFN7AY9Zv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00774.txt.bz2
Content-length: 1549
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92862
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-09
CC| |hubicka at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Feng Xue from comment #0)
> Function loop_only_exit_p() in tree-ssa-loop-niter.c:
>
> for (i = 0; i < loop->num_nodes; i++)
> {
> for (bsi = gsi_start_bb (body[i]); !gsi_end_p (bsi); gsi_next (&bsi))
> if (stmt_can_terminate_bb_p (gsi_stmt (bsi)))
> {
> return true;
> }
> }
>
> we should return false, not true?
Indeed... A patch fixing this is pre-approved (and obvious).
>
> Function predict_paths_leading_to_edge() in predict.c:
>
> FOR_EACH_EDGE (e2, ei, bb->succs)
> if (e2->dest != e->src && e2->dest != e->dest
> && !unlikely_executed_edge_p (e)
> && !dominated_by_p (CDI_POST_DOMINATORS, e->src, e2->dest))
> {
> has_nonloop_edge = true;
> break;
> }
>
> "e" is loop invariant, I guess that unlikely_executed_edge_p (e) might be
> unlikely_executed_edge_p (e2), which is more reasonable. And we can find
> similar code in predict_paths_for_bb () that uses the latter.
CCing Honza for the above.
>From gcc-bugs-return-662705-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:06:56 2019
Return-Path: <gcc-bugs-return-662705-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113856 invoked by alias); 9 Dec 2019 09:06: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 113779 invoked by uid 48); 9 Dec 2019 09:06:52 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92832] valgrind error in incorporate_penalties
Date: Mon, 09 Dec 2019 09:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: 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-92832-4-vj31KNNspa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00775.txt.bz2
Content-length: 575
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-12-09
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Hello.
Which compiled file is affected? Can you please attach a pre-processed source
file?
>From gcc-bugs-return-662706-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:13:49 2019
Return-Path: <gcc-bugs-return-662706-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127354 invoked by alias); 9 Dec 2019 09:13:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127295 invoked by uid 48); 9 Dec 2019 09:13:45 -0000
From: "claziss at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92845] [ARC] gcc not generating hardware compare instruction FDCMP for -mcpu=hs38_linux
Date: Mon, 09 Dec 2019 09:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: claziss 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-92845-4-rOIEB9gCaN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92845-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92845-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00776.txt.bz2
Content-length: 1066
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92845
--- Comment #1 from Claudiu Zissulescu <claziss at gmail dot com> ---
Although the FDCMP (the double precision floating point compare instruction) is
added to the compiler, it is not properly used via cstoredi pattern.
A patch can be this one:
index b592f25afce..bd44030b409 100644
--- a/gcc/config/arc/arc.md
+++ b/gcc/config/arc/arc.md
@@ -3749,7 +3749,7 @@ archs4x, archs4xd"
})
(define_mode_iterator SDF [(SF "TARGET_FP_SP_BASE || TARGET_OPTFPE")
- (DF "TARGET_OPTFPE")])
+ (DF "TARGET_FP_DP_BASE || TARGET_OPTFPE")])
(define_expand "cstore<mode>4"
[(set (reg:CC CC_REG)
@@ -3759,7 +3759,7 @@ archs4x, archs4xd"
(match_operator:SI 1 "comparison_operator" [(reg CC_REG)
(const_int 0)]))]
- "TARGET_FP_SP_BASE || TARGET_OPTFPE"
+ "TARGET_HARD_FLOAT || TARGET_OPTFPE"
{
gcc_assert (XEXP (operands[1], 0) == operands[2]);
gcc_assert (XEXP (operands[1], 1) == operands[3]);
>From gcc-bugs-return-662707-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:19:39 2019
Return-Path: <gcc-bugs-return-662707-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21091 invoked by alias); 9 Dec 2019 09:19: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 20999 invoked by uid 48); 9 Dec 2019 09:19:35 -0000
From: "lucas.bader at sap dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/79106] wrong source line printed in diagnostics for a translation unit
Date: Mon, 09 Dec 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: preprocessor
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lucas.bader at sap 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 attachments.created
Message-ID: <bug-79106-4-BH1kzNL0Ik@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00777.txt.bz2
Content-length: 927
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79106
Lucas Bader <lucas.bader at sap dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lucas.bader at sap dot com
--- Comment #7 from Lucas Bader <lucas.bader at sap dot com> ---
Created attachment 47443
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47443&action=edit
Proposed patch
This behavior (opening the original source file for diagnostics) also causes
issues when compiling within a compile cluster because only preprocessed files
are distributed. This results in wrong or no source lines being printed.
The attached patch attempts to alter the behavior by implementing a
location_get_source_line_preprocessed function that can be used in
diagnostic-show-locus.c in case a preprocessed file is compiled.
>From gcc-bugs-return-662708-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:23:15 2019
Return-Path: <gcc-bugs-return-662708-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52765 invoked by alias); 9 Dec 2019 09:23: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 52674 invoked by uid 48); 9 Dec 2019 09:23:11 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92737] cgraph_node and varpool_node needs explicit constructor
Date: Mon, 09 Dec 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: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92737-4-m75FLXXq3T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00778.txt.bz2
Content-length: 448
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92737
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Implemented on trunk.
>From gcc-bugs-return-662709-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:32:53 2019
Return-Path: <gcc-bugs-return-662709-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72306 invoked by alias); 9 Dec 2019 09:32:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71974 invoked by uid 48); 9 Dec 2019 09:32:47 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92863] ICE in gfc_typename
Date: Mon, 09 Dec 2019 09:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig 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-92863-4-qyKhg0Lq7s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92863-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92863-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00779.txt.bz2
Content-length: 747
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92863
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-09
CC| |tkoenig at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Probably a regression introduced by my earlier patches with
argument checking. Should be easy enough to fix.
>From gcc-bugs-return-662710-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:43:33 2019
Return-Path: <gcc-bugs-return-662710-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34631 invoked by alias); 9 Dec 2019 09:43:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29393 invoked by uid 48); 9 Dec 2019 09:43:29 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92283] [10 Regression] 454.calculix miscomparison since r276645 with -O2 -march=znver2
Date: Mon, 09 Dec 2019 09:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ra, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92283-4-Bu6FREMcqf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92283-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92283-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00780.txt.bz2
Content-length: 430
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92283
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #28 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-662711-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:43:34 2019
Return-Path: <gcc-bugs-return-662711-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35088 invoked by alias); 9 Dec 2019 09:43:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30461 invoked by uid 48); 9 Dec 2019 09:43:30 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
Date: Mon, 09 Dec 2019 09:43: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: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-26163-4-h59FEiUFMr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
References: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00781.txt.bz2
Content-length: 509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 92283, which changed state.
Bug 92283 Summary: [10 Regression] 454.calculix miscomparison since r276645 with -O2 -march=znver2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92283
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-662712-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:44:11 2019
Return-Path: <gcc-bugs-return-662712-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46900 invoked by alias); 9 Dec 2019 09: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 46766 invoked by uid 48); 9 Dec 2019 09:44:07 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92855] -fvisibility-inlines-hidden failing to hide out-of-line copies of certain inline member functions
Date: Mon, 09 Dec 2019 09:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: visibility
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov 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: resolution
Message-ID: <bug-92855-4-Ci9FMSXIYw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00782.txt.bz2
Content-length: 925
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92855
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |DUPLICATE
--- Comment #6 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Thanks. PR 47877 is definitely related but not an exact duplicate. Here we have
the visibility attribute on the enclosing namespace, and even though the
documentation does not spell out what should happen, it appears the intent is
that the option should prevail (so inline functions in the namespace would need
to be decorated with the visibility attribute individually to make them
non-hidden).
I'll close this as duplicate and add an example with a namespace to the older
PR.
*** This bug has been marked as a duplicate of bug 47877 ***
>From gcc-bugs-return-662713-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:44:11 2019
Return-Path: <gcc-bugs-return-662713-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46905 invoked by alias); 9 Dec 2019 09:44: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 46805 invoked by uid 48); 9 Dec 2019 09:44:07 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/47877] -fvisibility-inlines-hidden does not hide member template functions
Date: Mon, 09 Dec 2019 09:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.5.2
X-Bugzilla-Keywords: documentation, visibility
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: cc
Message-ID: <bug-47877-4-lnJz7MlBLR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00783.txt.bz2
Content-length: 450
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47877
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thiago at kde dot org
--- Comment #4 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
*** Bug 92855 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-662714-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:46:20 2019
Return-Path: <gcc-bugs-return-662714-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52336 invoked by alias); 9 Dec 2019 09:46: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 51785 invoked by uid 48); 9 Dec 2019 09:46:16 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/47877] -fvisibility-inlines-hidden does not hide member template functions
Date: Mon, 09 Dec 2019 09:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.5.2
X-Bugzilla-Keywords: documentation, visibility
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: cc
Message-ID: <bug-47877-4-sm5d3NFBdI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00784.txt.bz2
Content-length: 790
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47877
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #5 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
In PR 92855 we have a similar situation where an inline template function
inherits visibility from the enclosing namespace, while a non-template function
becomes hidden as requested by -fvisibility-inlines-hidden:
namespace N
__attribute__((visibility("default")))
{
inline void foo() {};
template<class T>
inline void bar() {};
}
int main()
{
N::foo();
N::bar<void>();
}
>From gcc-bugs-return-662715-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:50:55 2019
Return-Path: <gcc-bugs-return-662715-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74509 invoked by alias); 9 Dec 2019 09:50: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 74421 invoked by uid 48); 9 Dec 2019 09:50:51 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92832] valgrind error in incorporate_penalties
Date: Mon, 09 Dec 2019 09:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: WAITING
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-92832-4-RdIz25Waw4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00785.txt.bz2
Content-length: 376
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
--- Comment #2 from David Binderman <dcb314 at hotmail dot com> ---
I am not sure which file was affected. make -j 10 was running, so it could
be one of many.
Fortran is probably not the cause. Beyond trying a make -j 1 build without
fortran, which might take 24 hours or more, I am not sure how to answer your
question.
>From gcc-bugs-return-662716-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 09:59:31 2019
Return-Path: <gcc-bugs-return-662716-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101961 invoked by alias); 9 Dec 2019 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 101895 invoked by uid 55); 9 Dec 2019 09:59:27 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92853] std::filesystem::path::operator+=(std::filesystem::path const&) corrupts the heap
Date: Mon, 09 Dec 2019 09: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: 9.2.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: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92853-4-FWI8XgAupy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92853-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92853-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00786.txt.bz2
Content-length: 1209
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92853
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Dec 9 09:58:56 2019
New Revision: 279110
URL: https://gcc.gnu.org/viewcvs?rev=279110&root=gcc&view=rev
Log:
libstdc++: fix buffer overflow in path::operator+= (PR92853)
When concatenating a path ending in a root-directory onto another path,
we added an empty filename to the end of the path twice, but only
reserved space for one. That meant the second write went past the end of
the allocated buffer.
PR libstdc++/92853
* src/c++17/fs_path.cc (filesystem::path::operator+=(const path&)):
Do not process a trailing directory separator twice.
* testsuite/27_io/filesystem/path/concat/92853.cc: New test.
* testsuite/27_io/filesystem/path/concat/path.cc: Test more cases.
Added:
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/concat/92853.cc
- copied, changed from r279109,
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/concat/path.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/src/c++17/fs_path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/concat/path.cc
>From gcc-bugs-return-662717-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:00:40 2019
Return-Path: <gcc-bugs-return-662717-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105501 invoked by alias); 9 Dec 2019 10:00: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 104482 invoked by uid 55); 9 Dec 2019 10:00:25 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89007] [SVE] Implement generic vector average expansion
Date: Mon, 09 Dec 2019 10:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89007-4-FNxt6ICcoM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00787.txt.bz2
Content-length: 898
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89007
--- Comment #1 from prathamesh3492 at gcc dot gnu.org ---
Author: prathamesh3492
Date: Mon Dec 9 09:59:42 2019
New Revision: 279112
URL: https://gcc.gnu.org/viewcvs?rev=279112&root=gcc&view=rev
Log:
2019-12-09 Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
PR tree-optimization/89007
* tree-vect-patterns.c (vect_recog_average_pattern): If there is no
target support available, generate code to distribute rshift over plus
and add a carry.
testsuite/
* gcc.target/aarch64/sve/pr89007-1.c: New test.
* gcc.target/aarch64/sve/pr89007-2.c: Likewise.
Added:
trunk/gcc/testsuite/gcc.target/aarch64/sve/pr89007-1.c
trunk/gcc/testsuite/gcc.target/aarch64/sve/pr89007-2.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-vect-patterns.c
>From gcc-bugs-return-662719-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:01:52 2019
Return-Path: <gcc-bugs-return-662719-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111711 invoked by alias); 9 Dec 2019 10: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 111586 invoked by uid 48); 9 Dec 2019 10:01:47 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92864] [10 Regression] ICE in is_really_empty_class at gcc/cp/class.c:8595 since r276563
Date: Mon, 09 Dec 2019 10:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92864-4-paXNBRBsfj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92864-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92864-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00789.txt.bz2
Content-length: 569
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92864
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-09
Known to work| |9.2.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
>From gcc-bugs-return-662718-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:01:39 2019
Return-Path: <gcc-bugs-return-662718-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110864 invoked by alias); 9 Dec 2019 10:01: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 110746 invoked by uid 48); 9 Dec 2019 10:01:34 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92864] New: [10 Regression] ICE in is_really_empty_class at gcc/cp/class.c:8595 since r276563
Date: Mon, 09 Dec 2019 10:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 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-92864-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00788.txt.bz2
Content-length: 3236
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92864
Bug ID: 92864
Summary: [10 Regression] ICE in is_really_empty_class at
gcc/cp/class.c:8595 since r276563
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
I see the following ICE:
$ cat ice.ii
namespace std {
class type_info {};
} // namespace std
void fn1() { !((void **)&typeid(short))[0]; }
$ g++ ice.ii -c
ice.ii: In function ‘void fn1()’:
ice.ii:4:42: internal compiler error: Segmentation fault
4 | void fn1() { !((void **)&typeid(short))[0]; }
| ^
0x10370ef crash_signal
/home/marxin/Programming/gcc/gcc/toplev.c:328
0x7ff2d3a2814f ???
/usr/src/debug/glibc-2.30-1.3.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x91531b tree_check(tree_node*, char const*, int, char const*, tree_code)
/home/marxin/Programming/gcc/gcc/tree.h:3272
0x91531b is_really_empty_class(tree_node*, bool)
/home/marxin/Programming/gcc/gcc/cp/class.c:8595
0x92df9d cxx_eval_constant_expression
/home/marxin/Programming/gcc/gcc/cp/constexpr.c:4919
0x9390af cxx_eval_component_reference
/home/marxin/Programming/gcc/gcc/cp/constexpr.c:2995
0x92f595 cxx_eval_constant_expression
/home/marxin/Programming/gcc/gcc/cp/constexpr.c:5374
0x9390af cxx_eval_component_reference
/home/marxin/Programming/gcc/gcc/cp/constexpr.c:2995
0x92f595 cxx_eval_constant_expression
/home/marxin/Programming/gcc/gcc/cp/constexpr.c:5374
0x93831b cxx_eval_indirect_ref
/home/marxin/Programming/gcc/gcc/cp/constexpr.c:3825
0x92dbf9 cxx_eval_constant_expression
/home/marxin/Programming/gcc/gcc/cp/constexpr.c:5200
0x93106b cxx_eval_outermost_constant_expr
/home/marxin/Programming/gcc/gcc/cp/constexpr.c:5977
0x935f5b maybe_constant_value(tree_node*, tree_node*, bool)
/home/marxin/Programming/gcc/gcc/cp/constexpr.c:6254
0x950e85 cp_fully_fold(tree_node*)
/home/marxin/Programming/gcc/gcc/cp/cp-gimplify.c:2272
0xae096a cp_build_binary_op(op_location_t const&, tree_code, tree_node*,
tree_node*, int)
/home/marxin/Programming/gcc/gcc/cp/typeck.c:5682
0xae41aa cp_truthvalue_conversion(tree_node*, int)
/home/marxin/Programming/gcc/gcc/cp/typeck.c:6019
0x9568ab ocp_convert(tree_node*, tree_node*, int, int, int)
/home/marxin/Programming/gcc/gcc/cp/cvt.c:852
0x957efd cp_convert(tree_node*, tree_node*, int)
/home/marxin/Programming/gcc/gcc/cp/cvt.c:637
0x957efd cp_convert_and_check(tree_node*, tree_node*, int)
/home/marxin/Programming/gcc/gcc/cp/cvt.c:656
0x8f9b03 convert_like_real
/home/marxin/Programming/gcc/gcc/cp/call.c:7784
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-662721-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:03:25 2019
Return-Path: <gcc-bugs-return-662721-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116157 invoked by alias); 9 Dec 2019 10:03: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 116036 invoked by uid 48); 9 Dec 2019 10:03:20 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85559] [meta-bug] Improve conditional move
Date: Mon, 09 Dec 2019 10:03: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: 9.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: crazylht at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85559-4-11m2ExwaCj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85559-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85559-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00791.txt.bz2
Content-length: 453
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85559
Bug 85559 depends on bug 92578, which changed state.
Bug 92578 Summary: [i386] cmov not generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92578
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
>From gcc-bugs-return-662720-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:03:25 2019
Return-Path: <gcc-bugs-return-662720-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116115 invoked by alias); 9 Dec 2019 10:03: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 116015 invoked by uid 48); 9 Dec 2019 10:03:20 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92578] [i386] cmov not generated
Date: Mon, 09 Dec 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: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: crazylht 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: bug_status resolution
Message-ID: <bug-92578-4-GqVYJoxeOj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92578-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92578-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00790.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92578
Hongtao.liu <crazylht at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from Hongtao.liu <crazylht at gmail dot com> ---
It's designed on purpose.
>From gcc-bugs-return-662722-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:07:43 2019
Return-Path: <gcc-bugs-return-662722-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127530 invoked by alias); 9 Dec 2019 10:07: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 127472 invoked by uid 48); 9 Dec 2019 10:07:39 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92865] New: [10 Regression] error: unrecognizable insn: in extract_insn, at recog.c:2294 since
Date: Mon, 09 Dec 2019 10:07: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-92865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00792.txt.bz2
Content-length: 1890
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
Bug ID: 92865
Summary: [10 Regression] error: unrecognizable insn: in
extract_insn, at recog.c:2294 since
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: crazylht at gmail dot com
Target Milestone: ---
I see the following ICE:
$ cat ice.c
int A[16];
int
main() {
int i = 0;
for (; i < 16; i++)
A[i] = A[i] >= 2;
}
$ gcc -mxop -march=knl -O3 ice.c
ice.c: In function ‘main’:
ice.c:8:1: error: unrecognizable insn:
8 | }
| ^
(insn 10 9 11 2 (set (reg:V16SI 91)
(gt:V16SI (reg:V16SI 90)
(reg:V16SI 87))) "ice.c":7:10 -1
(nil))
during RTL pass: vregs
ice.c:8:1: internal compiler error: in extract_insn, at recog.c:2294
0x6b726c _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/marxin/Programming/gcc/gcc/rtl-error.c:108
0x6b7288 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
/home/marxin/Programming/gcc/gcc/rtl-error.c:116
0x6b5497 extract_insn(rtx_insn*)
/home/marxin/Programming/gcc/gcc/recog.c:2294
0xadcd23 instantiate_virtual_regs_in_insn
/home/marxin/Programming/gcc/gcc/function.c:1607
0xadcd23 instantiate_virtual_regs
/home/marxin/Programming/gcc/gcc/function.c:1977
0xadcd23 execute
/home/marxin/Programming/gcc/gcc/function.c:2026
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.
It's likely caused by r279107
>From gcc-bugs-return-662723-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:07:54 2019
Return-Path: <gcc-bugs-return-662723-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128216 invoked by alias); 9 Dec 2019 10:07: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 128181 invoked by uid 48); 9 Dec 2019 10:07:51 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92865] [10 Regression] error: unrecognizable insn: in extract_insn, at recog.c:2294 since
Date: Mon, 09 Dec 2019 10:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92865-4-mBQiKdgWNX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00793.txt.bz2
Content-length: 569
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-09
Known to work| |9.2.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
>From gcc-bugs-return-662724-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:10:21 2019
Return-Path: <gcc-bugs-return-662724-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15736 invoked by alias); 9 Dec 2019 10: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 15682 invoked by uid 48); 9 Dec 2019 10:10:17 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92865] [10 Regression] error: unrecognizable insn: in extract_insn, at recog.c:2294 since
Date: Mon, 09 Dec 2019 10: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: crazylht 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-92865-4-MovzrVh4Gx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00794.txt.bz2
Content-length: 136
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
--- Comment #1 from Hongtao.liu <crazylht at gmail dot com> ---
I'll take a look.
>From gcc-bugs-return-662725-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:13:54 2019
Return-Path: <gcc-bugs-return-662725-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19671 invoked by alias); 9 Dec 2019 10:13: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 19599 invoked by uid 55); 9 Dec 2019 10:13:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92834] misssed SLP vectorization in LightPixel
Date: Mon, 09 Dec 2019 10: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92834-4-n1iUMFjd9H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00795.txt.bz2
Content-length: 641
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92834
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Dec 9 10:13:18 2019
New Revision: 279113
URL: https://gcc.gnu.org/viewcvs?rev=279113&root=gcc&view=rev
Log:
PR tree-optimization/92834
* match.pd (A - ((A - B) & -(C cmp D)) -> (C cmp D) ? B : A,
A + ((B - A) & -(C cmp D)) -> (C cmp D) ? B : A): New simplifications.
* gcc.dg/tree-ssa/pr92834.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr92834.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/match.pd
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662726-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:16:16 2019
Return-Path: <gcc-bugs-return-662726-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22415 invoked by alias); 9 Dec 2019 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 22321 invoked by uid 48); 9 Dec 2019 10:16:07 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92865] [10 Regression] error: unrecognizable insn: in extract_insn, at recog.c:2294 since r279107
Date: Mon, 09 Dec 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: 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: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: liuhongt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to short_desc
Message-ID: <bug-92865-4-R7GlY7z3ey@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00796.txt.bz2
Content-length: 796
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |liuhongt at gcc dot gnu.org
Summary|[10 Regression] error: |[10 Regression] error:
|unrecognizable insn: in |unrecognizable insn: in
|extract_insn, at |extract_insn, at
|recog.c:2294 since |recog.c:2294 since r279107
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Yes, I can confirm that it's caused by your commit.
>From gcc-bugs-return-662728-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:28:30 2019
Return-Path: <gcc-bugs-return-662728-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90262 invoked by alias); 9 Dec 2019 10:28: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 90176 invoked by uid 48); 9 Dec 2019 10:28:26 -0000
From: "marc at kdab dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92856] incorrectly accepts invalid C++11 braced initialisation of double from long double
Date: Mon, 09 Dec 2019 10:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marc at kdab dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: resolution
Message-ID: <bug-92856-4-wHvXnJXl5H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92856-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92856-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00798.txt.bz2
Content-length: 409
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92856
Marc Mutz <marc at kdab dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |DUPLICATE
--- Comment #4 from Marc Mutz <marc at kdab dot com> ---
*** This bug has been marked as a duplicate of bug 55783 ***
>From gcc-bugs-return-662727-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:28:03 2019
Return-Path: <gcc-bugs-return-662727-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89326 invoked by alias); 9 Dec 2019 10: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 89218 invoked by uid 48); 9 Dec 2019 10:27:58 -0000
From: "marc at kdab dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92856] incorrectly accepts invalid C++11 braced initialisation of double from long double
Date: Mon, 09 Dec 2019 10:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marc at kdab 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-92856-4-0KKRQi8IMp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92856-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92856-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00797.txt.bz2
Content-length: 651
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92856
--- Comment #3 from Marc Mutz <marc at kdab dot com> ---
Indeed, I didn't check that it actually fails in SFINAE. Sorry for that.
This works:
// https://godbolt.org/z/EfJmS4
#include <utility>
#include <experimental/type_traits>
template <typename From, typename To>
using nonnarrowing_test = decltype(To{std::declval<From&>()});
template <typename From, typename To>
using is_narrowing =
std::negation<std::experimental::is_detected<nonnarrowing_test, From, To>>;
static_assert(is_narrowing<long double, double>{});
static_assert(!is_narrowing<double, long double>{});
>From gcc-bugs-return-662729-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:28:31 2019
Return-Path: <gcc-bugs-return-662729-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90348 invoked by alias); 9 Dec 2019 10:28: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 90221 invoked by uid 48); 9 Dec 2019 10:28:27 -0000
From: "marc at kdab dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55783] Warnings instead of compiler errors for narrowing conversions within list-initializations
Date: Mon, 09 Dec 2019 10:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.7.2
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marc at kdab 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-55783-4-1ew6rwcSXk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00799.txt.bz2
Content-length: 420
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55783
Marc Mutz <marc at kdab dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marc at kdab dot com
--- Comment #15 from Marc Mutz <marc at kdab dot com> ---
*** Bug 92856 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-662730-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:33:59 2019
Return-Path: <gcc-bugs-return-662730-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101473 invoked by alias); 9 Dec 2019 10: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 101405 invoked by uid 48); 9 Dec 2019 10:33:55 -0000
From: "rguenth 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: Mon, 09 Dec 2019 10:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: ice-checking, needs-bisection, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-92852-4-7Oq1S83bz6@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: 2019-12/txt/msg00800.txt.bz2
Content-length: 1871
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92852
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-reduction
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
It's the &cout ADDR_EXPR of std::basic_ostream<char>::operator<< (&cout, _1);
<addr_expr 0x7ffff3b2a0e0
type <pointer_type 0x7ffff3cca5e8
$7 = <gimple_call 0x7ffff3751090>
std::basic_ostream<char>::operator<< (&cout, _1);
I think unnesting doesn't have any code rewriting BLOCK references to BLOCKs
outside of the nested function. I guess we simply don't expect there to be
any... but then we probably do not expect the outer function to vanish
without the inner vanishing as well and the checking code doesn't try to
"search" for the BLOCK in the outer function.
But the testcase must be somehow more "tricky" because the issue doesn't
reproduce with
int global;
void bar(int &, int);
void foo()
{
int& l = global;
auto x = [&l](auto && y) { bar(l, y); };
x(1);
}
which shows a similar &global use in operator():
foo()::<lambda(auto:1&&)>::operator()<const int&> (const struct __lambda7 *
const __closure, const int & x)
{
struct ostream & message_stream [value-expr: ((const struct __lambda7 *)
__closure)->__message_stream];
_1 = *x;
std::basic_ostream<char>::operator<< (&cout, _1);
}
vs.
foo()::<lambda(auto:1&&)>::operator()<int> (const struct __lambda0 * const
__closure, int & y)
{
int & l [value-expr: ((const struct __lambda0 *) __closure)->__l];
_1 = *y;
bar (&global, _1);
}
so maybe the situation is all different. Anyway, testcase needs reduction.
My limited C++ fu doesn't even allow to remove <tuple> use ;) (that
variadic stuff)
>From gcc-bugs-return-662731-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:36:56 2019
Return-Path: <gcc-bugs-return-662731-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14751 invoked by alias); 9 Dec 2019 10:36: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 14687 invoked by uid 48); 9 Dec 2019 10:36:52 -0000
From: "doko at ubuntu dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92866] New: [10 Regression] libgo build failure on arm-linux-gnueabihf (ICE, segfault)
Date: Mon, 09 Dec 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: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at ubuntu dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92866-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00801.txt.bz2
Content-length: 2844
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92866
Bug ID: 92866
Summary: [10 Regression] libgo build failure on
arm-linux-gnueabihf (ICE, segfault)
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: doko at ubuntu dot com
CC: cmang at google dot com
Target Milestone: ---
seen with 20191208 trunk.
./../../src/libgo/go/text/template/parse/node.go: In function
'parse.CopyPipe..1text/template/parse.PipeNode':
../../../src/libgo/go/text/template/parse/node.go:186:1: internal compiler
error: Segmentation fault
186 | func (p *PipeNode) CopyPipe() *PipeNode {
| ^
0x5532c3 crash_signal
../../src/gcc/toplev.c:328
0x44c96b add_regs_to_insn_regno_info
../../src/gcc/lra.c:1509
0x44ca5f add_regs_to_insn_regno_info
../../src/gcc/lra.c:1531
0x44ca5f add_regs_to_insn_regno_info
../../src/gcc/lra.c:1531
0x44db0d lra_update_insn_regno_info(rtx_insn*)
../../src/gcc/lra.c:1624
0x46062b process_insn_for_elimination
../../src/gcc/lra-eliminations.c:1317
0x46062b lra_eliminate(bool, bool)
../../src/gcc/lra-eliminations.c:1367
0x44ed77 lra(_IO_FILE*)
../../src/gcc/lra.c:2557
0x420895 do_reload
../../src/gcc/ira.c:5518
0x420895 execute
../../src/gcc/ira.c:5704
Please submit a full bug report,
with preprocessed source if appropriate.
gcc configured with
--enable-languages=c,c++,go,d,fortran,objc,obj-c++
--prefix=/usr
--with-gcc-major-version-only
--program-suffix=-10
--program-prefix=arm-linux-gnueabihf-
--enable-shared
--enable-linker-build-id
--libexecdir=/usr/lib
--without-included-gettext
--enable-threads=posix
--libdir=/usr/lib
--enable-nls
--enable-clocale=gnu
--enable-libstdcxx-debug
--enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new
--enable-gnu-unique-object
--disable-libitm
--disable-libquadmath
--disable-libquadmath-support
--enable-plugin
--enable-default-pie
--with-system-zlib
--with-target-system-zlib=auto
--enable-objc-gc=auto
--enable-multiarch
--enable-multilib
--disable-sjlj-exceptions
--with-arch=armv7-a
--with-fpu=vfpv3-d16
--with-float=hard
--with-mode=thumb
--disable-werror
--enable-multilib
--enable-checking=release
--build=arm-linux-gnueabihf
--host=arm-linux-gnueabihf
--target=arm-linux-gnueabihf
>From gcc-bugs-return-662732-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:40:14 2019
Return-Path: <gcc-bugs-return-662732-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17924 invoked by alias); 9 Dec 2019 10:40: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 17861 invoked by uid 48); 9 Dec 2019 10:40:10 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92862] Suspicious codes in tree-ssa-loop-niter.c and predict.c
Date: Mon, 09 Dec 2019 10: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc version assigned_to target_milestone
Message-ID: <bug-92862-4-2petos7pLJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00802.txt.bz2
Content-length: 1345
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92862
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |marxin at gcc dot gnu.org
Version|unknown |10.0
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
Target Milestone|--- |10.0
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
> >
> > Function predict_paths_leading_to_edge() in predict.c:
> >
> > FOR_EACH_EDGE (e2, ei, bb->succs)
> > if (e2->dest != e->src && e2->dest != e->dest
> > && !unlikely_executed_edge_p (e)
> > && !dominated_by_p (CDI_POST_DOMINATORS, e->src, e2->dest))
> > {
> > has_nonloop_edge = true;
> > break;
> > }
> >
> > "e" is loop invariant, I guess that unlikely_executed_edge_p (e) might be
> > unlikely_executed_edge_p (e2), which is more reasonable. And we can find
> > similar code in predict_paths_for_bb () that uses the latter.
>
> CCing Honza for the above.
Yes, after reading of the code, there should really be 'e2'. Let me send patch
for both issues.
>From gcc-bugs-return-662733-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:44:21 2019
Return-Path: <gcc-bugs-return-662733-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23808 invoked by alias); 9 Dec 2019 10:44: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 23739 invoked by uid 48); 9 Dec 2019 10:44:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92832] valgrind error in incorporate_penalties
Date: Mon, 09 Dec 2019 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status target_milestone
Message-ID: <bug-92832-4-3ax3wOwgvp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00803.txt.bz2
Content-length: 457
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |ASSIGNED
Target Milestone|--- |10.0
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
I see, then let me take a look.
>From gcc-bugs-return-662734-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:51:05 2019
Return-Path: <gcc-bugs-return-662734-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38809 invoked by alias); 9 Dec 2019 10:51: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 38723 invoked by uid 48); 9 Dec 2019 10:51:01 -0000
From: "mkuvyrkov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)
Date: Mon, 09 Dec 2019 10:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: EH, ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mkuvyrkov at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92007-4-5uDvCQKofN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00804.txt.bz2
Content-length: 1096
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007
--- Comment #25 from Maxim Kuvyrkov <mkuvyrkov at gcc dot gnu.org> ---
(In reply to Ilya Leoshkevich from comment #24)
> I got the following results on gcc113:
>
> 400.perlbench
>
> Compiler flags: -DSPEC_CPU -DNDEBUG -DPERL_CORE -march=native -g -O3
> -funroll-loops -fopt-info-vec-optimized -DSPEC_CPU -DNDEBUG
> -DPERL_CORE -DSPEC_CPU_LINUX -DSPEC_CPU_BIGENDIAN -D_GNU_SOURCE
> -DSPEC_CPU_LP64 -fno-strict-aliasing -std=gnu90
>
> r277511 (without this fix): 884.11s
> r277515 (with this fix): 874.93s
>
> Maxim, could you please share compiler flags with which you are seeing the
> regression?
Hi Ilya,
Thank you for looking into this.
The flags were "-O3 -save-temps=obj -c -o av.o -DSPEC_CPU -DNDEBUG -DPERL_CORE
-DSPEC_CPU_LP64 -DSPEC_CPU_LINUX_X64 -fgnu89-inline" . From
"-DSPEC_CPU_BIGENDIAN" I'm guessing a Power architecture, and I've confirmed
the regression on AArch64 Cortex-A57.
I'll start a run with "-funroll-loops -fopt-info-vec-optimized" to check if
they are making the problem go away.
>From gcc-bugs-return-662735-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 10:53:43 2019
Return-Path: <gcc-bugs-return-662735-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47758 invoked by alias); 9 Dec 2019 10:53: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 47676 invoked by uid 48); 9 Dec 2019 10:53:39 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/91154] [10 Regression] 456.hmmer regression on Haswell caused by r272922
Date: Mon, 09 Dec 2019 10:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: 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-91154-4-9TTjsJdZmy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91154-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91154-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00805.txt.bz2
Content-length: 541
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91154
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
--- Comment #38 from Martin Liška <marxin at gcc dot gnu.org> ---
Just for the record, the same can be seen on -march=znver1:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=248.180.0&plot.1=27.180.0&
>From gcc-bugs-return-662736-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:01:26 2019
Return-Path: <gcc-bugs-return-662736-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59342 invoked by alias); 9 Dec 2019 11: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 59143 invoked by uid 48); 9 Dec 2019 11:01:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92864] [10 Regression] ICE in is_really_empty_class at gcc/cp/class.c:8595 since r276563
Date: Mon, 09 Dec 2019 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 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-92864-4-tlpSnyEz1n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92864-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92864-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00806.txt.bz2
Content-length: 487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92864
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Dup.
*** This bug has been marked as a duplicate of bug 92009 ***
>From gcc-bugs-return-662737-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:01:26 2019
Return-Path: <gcc-bugs-return-662737-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59388 invoked by alias); 9 Dec 2019 11: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 59166 invoked by uid 48); 9 Dec 2019 11:01:22 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92009] [10 Regression] ICE: Segmentation fault (in is_really_empty_class)
Date: Mon, 09 Dec 2019 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92009-4-1RO2bh4OXF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92009-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92009-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00807.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92009
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
*** Bug 92864 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-662738-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:02:30 2019
Return-Path: <gcc-bugs-return-662738-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61527 invoked by alias); 9 Dec 2019 11:02: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 61478 invoked by uid 48); 9 Dec 2019 11:02:26 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92388] [10 Regression] ICE in insert_regs, at cse.c:1129
Date: Mon, 09 Dec 2019 11: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: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92388-4-SsKKPc8rt4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92388-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92388-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00808.txt.bz2
Content-length: 150
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92388
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Any update on this Kyril?
>From gcc-bugs-return-662739-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:04:14 2019
Return-Path: <gcc-bugs-return-662739-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81005 invoked by alias); 9 Dec 2019 11:04:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80949 invoked by uid 48); 9 Dec 2019 11:04:10 -0000
From: "rguenth 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: Mon, 09 Dec 2019 11:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: ice-checking, needs-bisection, needs-reduction
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-92852-4-UlJlJDWv11@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: 2019-12/txt/msg00809.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92852
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Somewhat reduced:
#include <tuple>
#include <algorithm>
struct S
{
int operator<<(const int &);
};
S glob;
void foo()
{
S& message_stream = glob;
auto data = std::make_tuple(3,4u);
auto format = [&message_stream](auto && x) { message_stream << x ;};
std::apply([&](auto const& ...x){(..., format(x));}, data);
}
with std::make_tuple(3,4) it doesn't reproduce(?!)
>From gcc-bugs-return-662740-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:06:21 2019
Return-Path: <gcc-bugs-return-662740-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86822 invoked by alias); 9 Dec 2019 11:06:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84813 invoked by uid 48); 9 Dec 2019 11:06:17 -0000
From: "rguenth 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: Mon, 09 Dec 2019 11: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: 9.2.0
X-Bugzilla-Keywords: ice-checking, needs-bisection, needs-reduction
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-92852-4-0IINChLO50@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: 2019-12/txt/msg00810.txt.bz2
Content-length: 340
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92852
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Aha. Reduced testcase:
struct S { int operator<<(const int &); } glob;
void foo()
{
S& message_stream = glob;
auto format = [&message_stream](auto && x) { message_stream << x ;};
format(3);
format(4u);
}
>From gcc-bugs-return-662741-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:10:02 2019
Return-Path: <gcc-bugs-return-662741-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95525 invoked by alias); 9 Dec 2019 11: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 95432 invoked by uid 48); 9 Dec 2019 11:09:57 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92867] New: Use ERF_RETURNS_ARG in more places
Date: Mon, 09 Dec 2019 11:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00811.txt.bz2
Content-length: 3457
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92867
Bug ID: 92867
Summary: Use ERF_RETURNS_ARG in more places
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
Shouldn't we use the fact that some functions returns one of its arguments
unmodified in more places?
E.g. for tail calls:
char buf[128] = { 1 };
char *
foo (int n)
{
return __builtin_memset (buf, ' ', n);
}
char *
bar (int n)
{
__builtin_memset (buf, ' ', n);
return buf;
}
we get better code (tail call) just in the first case and not the second one.
Shouldn't we perform IPA discovery of calls that return one of their arguments?
And, shouldn't we have some user attribute which would allow to specify this?
>From gcc-bugs-return-662742-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:11:39 2019
Return-Path: <gcc-bugs-return-662742-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97419 invoked by alias); 9 Dec 2019 11:11: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 97347 invoked by uid 48); 9 Dec 2019 11:11:35 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92868] New: [10 Regression] ICE: tree check: expected integer_cst, have ssa_name in to_wide, at tree.h:5855
Date: Mon, 09 Dec 2019 11:11: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-92868-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00812.txt.bz2
Content-length: 3071
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92868
Bug ID: 92868
Summary: [10 Regression] ICE: tree check: expected integer_cst,
have ssa_name in to_wide, at tree.h:5855
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: ---
gfortran-10.0.0-alpha20191208 snapshot (r279100) ICEs when compiling
gcc/testsuite/gfortran.dg/associate_33.f03 w/ -O2 -fno-tree-loop-optimize
--param max-completely-peeled-insns=1:
% powerpc-e300c3-linux-gnu-gfortran-10.0.0-alpha20191208 -O2
-fno-tree-loop-optimize --param max-completely-peeled-insns=1 -c
gcc/testsuite/gfortran.dg/associate_33.f03
during GIMPLE pass: strlen
gcc/testsuite/gfortran.dg/associate_33.f03:11:0:
11 | end
|
internal compiler error: tree check: expected integer_cst, have ssa_name in
to_wide, at tree.h:5855
0x6fef46 tree_check_failed(tree_node const*, char const*, int, char const*,
...)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/tree.c:9688
0x702163 tree_check(tree_node const*, char const*, int, char const*, tree_code)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/tree.h:3529
0x702163 wi::to_wide(tree_node const*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/tree.h:5855
0x702163 tree_int_cst_sgn(tree_node const*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/tree.c:7381
0x9a47f8 compute_objsize(tree_node*, int, tree_node**, tree_node**)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/builtins.c:3930
0x1064fd2 handle_store
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/tree-ssa-strlen.c:4381
0x1064fd2 check_and_optimize_stmt
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/tree-ssa-strlen.c:5013
0x1064fd2 strlen_dom_walker::before_dom_children(basic_block_def*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/tree-ssa-strlen.c:5190
0x15e2e17 dom_walker::walk(basic_block_def*)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/domwalk.c:309
0x1056de6 printf_strlen_execute
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-10.0.0_alpha20191208/work/gcc-10-20191208/gcc/tree-ssa-strlen.c:5256
(While my target here is powerpc, the ICE is not target-specific.)
>From gcc-bugs-return-662743-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:13:00 2019
Return-Path: <gcc-bugs-return-662743-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99261 invoked by alias); 9 Dec 2019 11:13: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 99174 invoked by uid 48); 9 Dec 2019 11:12:56 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92865] [10 Regression] error: unrecognizable insn: in extract_insn, at recog.c:2294 since r279107
Date: Mon, 09 Dec 2019 11:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: crazylht at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: liuhongt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92865-4-0FnqH4pyd7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00813.txt.bz2
Content-length: 600
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
--- Comment #3 from Hongtao.liu <crazylht at gmail dot com> ---
Since TARGET_XOP only supports 128-bit vector compare, ix86_valid_mask_cmp_mode
should also handle 256/512-bit vector compare when avx512f is avalable.
untested patch
@@ -3428,7 +3428,7 @@ static bool
ix86_valid_mask_cmp_mode (machine_mode mode)
{
/* XOP has its own vector conditional movement. */
- if (TARGET_XOP)
+ if (TARGET_XOP && GET_MODE_SIZE (mode) == 128)
return false;
/* AVX512F is needed for mask operation. */
I'll add some testcase later.
>From gcc-bugs-return-662744-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:17:08 2019
Return-Path: <gcc-bugs-return-662744-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103094 invoked by alias); 9 Dec 2019 11:17: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 103057 invoked by uid 55); 9 Dec 2019 11:17:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92853] std::filesystem::path::operator+=(std::filesystem::path const&) corrupts the heap
Date: Mon, 09 Dec 2019 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
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-92853-4-YbeiQTxDBO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92853-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92853-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00814.txt.bz2
Content-length: 1484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92853
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Dec 9 11:16:29 2019
New Revision: 279115
URL: https://gcc.gnu.org/viewcvs?rev=279115&root=gcc&view=rev
Log:
libstdc++: fix buffer overflow in path::operator+= (PR92853)
When concatenating a path ending in a root-directory onto another path,
we added an empty filename to the end of the path twice, but only
reserved space for one. That meant the second write went past the end of
the allocated buffer.
PR libstdc++/92853
* src/c++17/fs_path.cc (filesystem::path::operator+=(const path&)):
Do not process a trailing directory separator twice.
* testsuite/27_io/filesystem/path/concat/92853.cc: New test.
* testsuite/27_io/filesystem/path/concat/path.cc: Test more cases.
* testsuite/27_io/filesystem/path/concat/strings.cc: Test more cases.
Added:
branches/gcc-9-branch/libstdc++-v3/testsuite/27_io/filesystem/path/concat/92853.cc
- copied, changed from r279103,
branches/gcc-9-branch/libstdc++-v3/testsuite/27_io/filesystem/path/concat/path.cc
Modified:
branches/gcc-9-branch/libstdc++-v3/ChangeLog
branches/gcc-9-branch/libstdc++-v3/src/c++17/fs_path.cc
branches/gcc-9-branch/libstdc++-v3/testsuite/27_io/filesystem/path/concat/path.cc
branches/gcc-9-branch/libstdc++-v3/testsuite/27_io/filesystem/path/concat/strings.cc
>From gcc-bugs-return-662745-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:17:36 2019
Return-Path: <gcc-bugs-return-662745-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104252 invoked by alias); 9 Dec 2019 11:17: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 103953 invoked by uid 48); 9 Dec 2019 11:17:31 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92853] std::filesystem::path::operator+=(std::filesystem::path const&) corrupts the heap
Date: Mon, 09 Dec 2019 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: 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-92853-4-qdzh73I9xF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92853-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92853-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00815.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92853
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for GCC 9.3 and 10.1
>From gcc-bugs-return-662746-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:19:10 2019
Return-Path: <gcc-bugs-return-662746-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115509 invoked by alias); 9 Dec 2019 11:19: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 111337 invoked by uid 48); 9 Dec 2019 11:19:05 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92868] [10 Regression] ICE: tree check: expected integer_cst, have ssa_name in to_wide, at tree.h:5855
Date: Mon, 09 Dec 2019 11:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 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-92868-4-vy0T1iEO29@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92868-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92868-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00816.txt.bz2
Content-length: 369
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92868
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
Target Milestone|--- |10.0
>From gcc-bugs-return-662748-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:20:17 2019
Return-Path: <gcc-bugs-return-662748-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117771 invoked by alias); 9 Dec 2019 11: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 117498 invoked by uid 48); 9 Dec 2019 11:20:12 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92867] Use ERF_RETURNS_ARG in more places
Date: Mon, 09 Dec 2019 11: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: 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: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-92867-4-Kt8h6gWjvj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00818.txt.bz2
Content-length: 560
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92867
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-09
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Yes, yes and yes.
>From gcc-bugs-return-662749-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:20:30 2019
Return-Path: <gcc-bugs-return-662749-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118595 invoked by alias); 9 Dec 2019 11:20:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118476 invoked by uid 48); 9 Dec 2019 11:20:23 -0000
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/12955] Incorrect rounding of soft float denorm mul/div
Date: Mon, 09 Dec 2019 11:20: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: 3.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: steven at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: eager at mvista dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-12955-4-Qtx25yUQwf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-12955-4@http.gcc.gnu.org/bugzilla/>
References: <bug-12955-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00819.txt.bz2
Content-length: 352
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12955
--- Comment #15 from Steven Bosscher <steven at gcc dot gnu.org> ---
> cc-ing Geoffrey Keating from that thread
Eric, can you please stop adding people from the past to CC lists?
I'm sure you mean well, but it's not always appreciated.
Geoff hasn't been involved in GCC work for almost a decade.
>From gcc-bugs-return-662747-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:20:06 2019
Return-Path: <gcc-bugs-return-662747-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116823 invoked by alias); 9 Dec 2019 11:20: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 116614 invoked by uid 48); 9 Dec 2019 11:19:58 -0000
From: "iii at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)
Date: Mon, 09 Dec 2019 11:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: EH, ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iii at linux dot ibm.com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92007-4-zhbMW4bQEJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00817.txt.bz2
Content-length: 340
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007
--- Comment #26 from Ilya Leoshkevich <iii at linux dot ibm.com> ---
Whoops, I accidentally used a script I normally use for big-endian
machines (s390 actually). But gcc113 is an APM X-Gene Mustang board.
I'll try again with your flags and see if I can reproduce the regression
there.
>From gcc-bugs-return-662750-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:23:38 2019
Return-Path: <gcc-bugs-return-662750-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123857 invoked by alias); 9 Dec 2019 11:23: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 123803 invoked by uid 48); 9 Dec 2019 11:23:33 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92865] [10 Regression] error: unrecognizable insn: in extract_insn, at recog.c:2294 since r279107
Date: Mon, 09 Dec 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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: liuhongt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92865-4-KgY80WhFQC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00820.txt.bz2
Content-length: 831
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Hongtao.liu from comment #3)
> Since TARGET_XOP only supports 128-bit vector compare,
> ix86_valid_mask_cmp_mode should also handle 256/512-bit vector compare when
> avx512f is avalable.
>
>
> untested patch
>
> @@ -3428,7 +3428,7 @@ static bool
> ix86_valid_mask_cmp_mode (machine_mode mode)
> {
> /* XOP has its own vector conditional movement. */
> - if (TARGET_XOP)
> + if (TARGET_XOP && GET_MODE_SIZE (mode) == 128)
> return false;
Shouldn't we do sth like TARGET_XOP && !TARGET_AVX512F instead? That is
maybe simply elide that check completely, not sure why it was added.
> /* AVX512F is needed for mask operation. */
>
> I'll add some testcase later.
>From gcc-bugs-return-662751-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:26:10 2019
Return-Path: <gcc-bugs-return-662751-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5892 invoked by alias); 9 Dec 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 5840 invoked by uid 48); 9 Dec 2019 11:26:06 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92854] [OpenACC] Always-true conditional in 'libgomp/oacc-mem.c:acc_unmap_data'?
Date: Mon, 09 Dec 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: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92854-4-CTXz98X26X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00821.txt.bz2
Content-length: 998
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92854
--- Comment #2 from jules at gcc dot gnu.org ---
For strictly-paired acc_map_data/acc_unmap_data calls that don't interfere with
other mappings -- no, probably not. But (like I guess you noticed too) the
existing code feels wrong (or at least ugly) nonetheless.
It's probably possible to come up with a legal (but odd) test case in which the
condition is false -- maybe something like this (untested!):
int arr1[100], arr2[100], arr3[100];
void foo (void)
{
#pragma acc data copy(arr1) copy(arr2) copy(arr3)
{
void *darr2 = acc_deviceptr (arr2);
acc_map_data (arr2, darr2, sizeof (arr2));
[...]
acc_unmap_data (arr2);
}
}
Now I think the acc_map_data call will reuse the tgt for the structured data
mapping, which binds together several array copies into a single device block.
Forcing the first key's refcount to infinity (as is done in the current
implementation of acc_map_data) is also wrong in that case.
>From gcc-bugs-return-662752-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:32:24 2019
Return-Path: <gcc-bugs-return-662752-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24483 invoked by alias); 9 Dec 2019 11: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 24292 invoked by uid 48); 9 Dec 2019 11:32:20 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92832] valgrind error in incorporate_penalties
Date: Mon, 09 Dec 2019 11:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92832-4-kNR1DhhRak@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00822.txt.bz2
Content-length: 1429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
--- Comment #4 from David Binderman <dcb314 at hotmail dot com> ---
Some progress: make -j 1 with languages set to C only, got this:
/home/dcb/gcc/working/./gcc/xgcc -B/home/dcb/gcc/working/./gcc/
-B/home/dcb/gcc/results.279100.valgrind/x86_64-pc-linux-gnu/bin/
-B/home/dcb/gcc/results.279100.valgrind/x86_64-pc-linux-gnu/lib/ -isystem
/home/dcb/gcc/results.279100.valgrind/x86_64-pc-linux-gnu/include -isystem
/home/dcb/gcc/results.279100.valgrind/x86_64-pc-linux-gnu/sys-include -g -O3
-O2 -g -O3 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem
./include -fpic -mlong-double-80 -DUSE_ELF_SYMVER -g -DIN_LIBGCC2
-fbuilding-libgcc -fno-stack-protector -fpic -mlong-double-80
-DUSE_ELF_SYMVER -I. -I. -I../.././gcc -I../../../trunk/libgcc
-I../../../trunk/libgcc/. -I../../../trunk/libgcc/../gcc
-I../../../trunk/libgcc/../include -I../../../trunk/libgcc/config/libbid
-DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS -DUSE_TLS -o _clear_cache.o -MT
_clear_cache.o -MD -MP -MF _clear_cache.dep -DL_clear_cache -c
../../../trunk/libgcc/libgcc2.c -fvisibility=hidden -DHIDE_EXPORTS
==647411== Conditional jump or move depends on uninitialised value(s)
==647411== at 0x14990E8: incorporate_penalties (ipa-cp.c:3174)
I will get the pre-processed file to you.
>From gcc-bugs-return-662753-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:36:14 2019
Return-Path: <gcc-bugs-return-662753-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27795 invoked by alias); 9 Dec 2019 11:36: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 27753 invoked by uid 48); 9 Dec 2019 11:36:11 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92832] valgrind error in incorporate_penalties
Date: Mon, 09 Dec 2019 11:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92832-4-v8e8XqQsTC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00823.txt.bz2
Content-length: 233
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
--- Comment #5 from David Binderman <dcb314 at hotmail dot com> ---
Problem seems to go away if I set VALGRIND_OPTS
export VALGRIND_OPTS="--expensive-definedness-checks=yes"
>From gcc-bugs-return-662754-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:36:55 2019
Return-Path: <gcc-bugs-return-662754-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28804 invoked by alias); 9 Dec 2019 11:36: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 28766 invoked by uid 48); 9 Dec 2019 11:36:50 -0000
From: "joshua.a.saxby at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92857] -Wsign-conversion flag issues false positives for expression using typedef'ed unsigned types
Date: Mon, 09 Dec 2019 11:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joshua.a.saxby 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-92857-4-d8vRvDDB0P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92857-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00824.txt.bz2
Content-length: 802
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92857
--- Comment #2 from Joshua Saxby <joshua.a.saxby at gmail dot com> ---
(In reply to Richard Biener from comment #1)
> I think the warning is about foo - bar being carried out in type 'int' due to
> integer promotion and that converted to size_t which may turn the negative
> result into a positive.
That could be the issue, although I would expect the integer promotion to
promote to an unsigned integer type rather than a signed one. Am I mistaken in
this assumption?
I don't know if it makes a difference, but if `MyUnsigned` is replaced with
`unsigned`, then the warning diagnostic is not issued.
Then again, to demonstrate if it is an issue with the integer promotion or not,
probably it should be tested with `unsigned char` as well.
>From gcc-bugs-return-662756-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:40:58 2019
Return-Path: <gcc-bugs-return-662756-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33577 invoked by alias); 9 Dec 2019 11:40: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 33071 invoked by uid 48); 9 Dec 2019 11:40:53 -0000
From: "epagone at email dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92586] ICE in gimplify_expr, at gimplify.c:13479 with nested allocatable derived types
Date: Mon, 09 Dec 2019 11:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: epagone at email dot it
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92586-4-6LMKbQkFtM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92586-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92586-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00826.txt.bz2
Content-length: 174
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92586
--- Comment #4 from epagone <epagone at email dot it> ---
The test case compiles and runs correctly on ifort 19.0.1.144
>From gcc-bugs-return-662755-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:40:54 2019
Return-Path: <gcc-bugs-return-662755-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33093 invoked by alias); 9 Dec 2019 11: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 33014 invoked by uid 55); 9 Dec 2019 11:40:49 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92854] [OpenACC] Always-true conditional in 'libgomp/oacc-mem.c:acc_unmap_data'?
Date: Mon, 09 Dec 2019 11:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92854-4-5Tq0lP1ZPZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00825.txt.bz2
Content-length: 580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92854
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Author: tschwinge
Date: Mon Dec 9 11:40:17 2019
New Revision: 279120
URL: https://gcc.gnu.org/viewcvs?rev=279120&root=gcc&view=rev
Log:
[PR92854] Add 'libgomp.oacc-c-c++-common/pr92854-1.c'
... to document the status quo.
libgomp/
PR libgomp/92854
* testsuite/libgomp.oacc-c-c++-common/pr92854-1.c: New file.
Added:
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr92854-1.c
Modified:
trunk/libgomp/ChangeLog
>From gcc-bugs-return-662757-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:41:12 2019
Return-Path: <gcc-bugs-return-662757-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34811 invoked by alias); 9 Dec 2019 11:41:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34557 invoked by uid 55); 9 Dec 2019 11:41:08 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92511] [OpenACC] Support subset subarray mappings
Date: Mon, 09 Dec 2019 11:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92511-4-oqyu4ihHS0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92511-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92511-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00827.txt.bz2
Content-length: 2109
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92511
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Author: tschwinge
Date: Mon Dec 9 11:40:36 2019
New Revision: 279122
URL: https://gcc.gnu.org/viewcvs?rev=279122&root=gcc&view=rev
Log:
[PR92511] More testing for OpenACC "present" subarrays
In particular, "subset subarrays".
libgomp/
PR libgomp/92511
* testsuite/libgomp.oacc-c-c++-common/copyin-devptr-1.c: Remove
this file...
* testsuite/libgomp.oacc-c-c++-common/copyin-devptr-2.c: ..., and
this file...
* testsuite/libgomp.oacc-c-c++-common/lib-22.c: ..., and this
file...
* testsuite/libgomp.oacc-c-c++-common/lib-30.c: ..., and this
file...
* testsuite/libgomp.oacc-c-c++-common/subset-subarray-mappings-1-r-p.c:
... with their content moved into, and extended in this new file.
* testsuite/libgomp.oacc-c-c++-common/subset-subarray-mappings-1-d-a.c:
New file.
* testsuite/libgomp.oacc-c-c++-common/subset-subarray-mappings-1-d-p.c:
Likewise.
* testsuite/libgomp.oacc-c-c++-common/subset-subarray-mappings-1-r-a.c:
Likewise.
* testsuite/libgomp.oacc-c-c++-common/subset-subarray-mappings-2.c:
Likewise.
Added:
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/subset-subarray-mappings-1-d-a.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/subset-subarray-mappings-1-d-p.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/subset-subarray-mappings-1-r-a.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/subset-subarray-mappings-1-r-p.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/subset-subarray-mappings-2.c
Removed:
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/copyin-devptr-1.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/copyin-devptr-2.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/lib-22.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/lib-30.c
Modified:
trunk/libgomp/ChangeLog
>From gcc-bugs-return-662758-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:43:00 2019
Return-Path: <gcc-bugs-return-662758-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43575 invoked by alias); 9 Dec 2019 11:43:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43535 invoked by uid 48); 9 Dec 2019 11:42:56 -0000
From: "joshua.a.saxby at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92857] -Wsign-conversion flag issues false positives for expression using typedef'ed unsigned types
Date: Mon, 09 Dec 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: c
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joshua.a.saxby 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-92857-4-rvXfSDABIQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92857-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00828.txt.bz2
Content-length: 283
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92857
--- Comment #3 from Joshua Saxby <joshua.a.saxby at gmail dot com> ---
I can confirm that if `MyUnsigned` is changed to `unsigned char`, the issue
persists, however if it is changed to `unsigned int`, the issue is not present.
>From gcc-bugs-return-662759-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:47:41 2019
Return-Path: <gcc-bugs-return-662759-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49397 invoked by alias); 9 Dec 2019 11: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 49319 invoked by uid 48); 9 Dec 2019 11:47:36 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92867] Use ERF_RETURNS_ARG in more places
Date: Mon, 09 Dec 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: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 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-92867-4-3o5MHWBQL4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00829.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92867
prathamesh3492 at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |prathamesh3492 at gcc dot gnu.org
--- Comment #2 from prathamesh3492 at gcc dot gnu.org ---
If it's OK, I will try to implement this.
Thanks,
Prathamesh
>From gcc-bugs-return-662760-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:54:06 2019
Return-Path: <gcc-bugs-return-662760-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58367 invoked by alias); 9 Dec 2019 11: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 58297 invoked by uid 48); 9 Dec 2019 11:54:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92867] Use ERF_RETURNS_ARG in more places
Date: Mon, 09 Dec 2019 11:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: 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-92867-4-ExX96m9vIg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00830.txt.bz2
Content-length: 135
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92867
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Sure, go ahead.
>From gcc-bugs-return-662761-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:57:36 2019
Return-Path: <gcc-bugs-return-662761-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63700 invoked by alias); 9 Dec 2019 11:57: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 63630 invoked by uid 48); 9 Dec 2019 11:57:32 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92832] valgrind error in incorporate_penalties
Date: Mon, 09 Dec 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: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92832-4-b19Z0D7OhX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00831.txt.bz2
Content-length: 164
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
I have a reduced test-case, but thanks.
>From gcc-bugs-return-662763-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:59:46 2019
Return-Path: <gcc-bugs-return-662763-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71224 invoked by alias); 9 Dec 2019 11: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 71097 invoked by uid 48); 9 Dec 2019 11:59:42 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92832] valgrind error in incorporate_penalties
Date: Mon, 09 Dec 2019 11:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92832-4-OMp2BO5l7H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00833.txt.bz2
Content-length: 501
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |INVALID
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
Yes, I can confirm that --expensive-definedness-checks=yes fixed that.
>From gcc-bugs-return-662762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 11:59:46 2019
Return-Path: <gcc-bugs-return-662762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71204 invoked by alias); 9 Dec 2019 11: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 71123 invoked by uid 48); 9 Dec 2019 11:59:42 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/63426] [meta-bug] Issues found with -fsanitize=undefined
Date: Mon, 09 Dec 2019 11:59: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: 5.0
X-Bugzilla-Keywords: meta-bug
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 resolution
Message-ID: <bug-63426-4-LqFXACCxRw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63426-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63426-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00832.txt.bz2
Content-length: 467
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 92832, which changed state.
Bug 92832 Summary: valgrind error in incorporate_penalties
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |INVALID
>From gcc-bugs-return-662764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 12:04:31 2019
Return-Path: <gcc-bugs-return-662764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85048 invoked by alias); 9 Dec 2019 12:04: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 84967 invoked by uid 55); 9 Dec 2019 12:04:25 -0000
From: "matmal01 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: Mon, 09 Dec 2019 12:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matmal01 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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:
Message-ID: <bug-92410-4-qFLWOHlzDz@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: 2019-12/txt/msg00834.txt.bz2
Content-length: 3004
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92410
--- Comment #8 from Matthew Malcomson <matmal01 at gcc dot gnu.org> ---
Author: matmal01
Date: Mon Dec 9 12:03:53 2019
New Revision: 279124
URL: https://gcc.gnu.org/viewcvs?rev=279124&root=gcc&view=rev
Log:
[mid-end] Add notes to dataflow insn info when re-emitting (PR92410)
In scheduling passes, notes are removed with `remove_notes` before the
scheduling is done, and added back in with `reemit_notes` once the
scheduling has been decided.
This process leaves the notes in the RTL chain with different insn uid's
than were there before. Having different UID's (larger than the
previous ones) means that DF_INSN_INFO_GET(insn) will access outside of
the allocated array.
This has been seen in the `regstat_bb_compute_calls_crossed` function.
This patch adds an assert to the `regstat_bb_compute_calls_crossed`
function so that bad accesses here are caught instead of going
unnoticed, and then avoids the problem.
We avoid the problem by ensuring that new notes added by `reemit_notes` have an
insn record given to them. This is done by adding a call to
`df_insn_create_insn_record` on each note added in `reemit_notes`.
`df_insn_create_insn_record` leaves this new record zeroed out, which appears
to be fine for notes (e.g. `df_bb_refs_record` already does not set
anything except the luid for notes, and notes have no dataflow information to
record).
We add the testcase that Martin found here
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92410#c2 .
This testcase fails with the "regstat.c" change, and then succeeds with the
"haifa-sched.c" change.
There is a similar problem with labels, that the `gcc_assert` catches
when running regression tests in gcc.dg/fold-eqandshift-1.c and
gcc.c-torture/compile/pr32482.c.
This is due to the `cfg_layout_finalize` call in `bb-reorder.c` emitting
new labels, and these labels not having a dataflow df_insn_info member.
We solve this by manually calling `df_recompute_luids` on each basic
block once this pass has finished.
Testing done:
Ran regression tests on aarch64-none-linux-gnu cross compiler.
Bootstrapped and ran tests on aarch64-none-linux-gnu native.
gcc/ChangeLog:
2019-12-09 Matthew Malcomson <matthew.malcomson@arm.com>
PR middle-end/92410
* bb-reorder.c (pass_reorder_blocks::execute): Recompute
dataflow luids once basic blocks have been reordered.
* haifa-sched.c (reemit_notes): Create df insn record for each
new note.
* regstat.c (regstat_bb_compute_calls_crossed): Assert every
insn has an insn record before trying to use it.
gcc/testsuite/ChangeLog:
2019-12-09 Matthew Malcomson <matthew.malcomson@arm.com>
PR middle-end/92410
* gcc.dg/torture/pr92410.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/torture/pr92410.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/bb-reorder.c
trunk/gcc/haifa-sched.c
trunk/gcc/regstat.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 12:39:55 2019
Return-Path: <gcc-bugs-return-662765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68640 invoked by alias); 9 Dec 2019 12:39: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 68532 invoked by uid 48); 9 Dec 2019 12:39:50 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92854] [OpenACC] Always-true conditional in 'libgomp/oacc-mem.c:acc_unmap_data'?
Date: Mon, 09 Dec 2019 12:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92854-4-5dZUEnV0xC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00835.txt.bz2
Content-length: 1860
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92854
--- Comment #4 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Created attachment 47444
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47444&action=edit
[WIP] 'libgomp.oacc-c-c++-common/acc_map_data-device_already-*.c',
'libgomp.oacc-c-c++-common/acc_map_data-host_already-*.c'
(In reply to jules from comment #2)
> For strictly-paired acc_map_data/acc_unmap_data calls that don't interfere
> with other mappings -- no, probably not. But (like I guess you noticed too)
> the existing code feels wrong (or at least ugly) nonetheless.
;-)
> It's probably possible to come up with a legal (but odd) test case
Odd is not the problem -- actual users are doing such things, too.
> in which
> the condition is false -- maybe something like this (untested!):
>
> int arr1[100], arr2[100], arr3[100];
>
> void foo (void)
> {
> #pragma acc data copy(arr1) copy(arr2) copy(arr3)
> {
> void *darr2 = acc_deviceptr (arr2);
> acc_map_data (arr2, darr2, sizeof (arr2));
> [...]
> acc_unmap_data (arr2);
> }
> }
>
> Now I think the acc_map_data call will reuse the tgt for the structured data
> mapping, which binds together several array copies into a single device
> block. Forcing the first key's refcount to infinity (as is done in the
> current implementation of acc_map_data) is also wrong in that case.
In these cases, 'acc_map_data' will (should) refuse because "address [...] is
already mapped", see the test cases I'm attaching. (ACK?)
Can you easily (please don't spend much time on this) tell what's wrong with
'libgomp.oacc-c-c++-common/acc_map_data-device_already-3.c' (see TODOs
therein). If not, then we shall file a separate PR for this OpenACC 'declare'
case -- GCC's OpenACC 'declare' implementation has many other issues, after
all.
>From gcc-bugs-return-662766-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 12:48:35 2019
Return-Path: <gcc-bugs-return-662766-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86663 invoked by alias); 9 Dec 2019 12: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 86493 invoked by uid 48); 9 Dec 2019 12:48:30 -0000
From: "drepper.fsp+rhbz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92867] Use ERF_RETURNS_ARG in more places
Date: Mon, 09 Dec 2019 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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: drepper.fsp+rhbz 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-92867-4-RXAaBKuPOZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00836.txt.bz2
Content-length: 1474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92867
Ulrich Drepper <drepper.fsp+rhbz at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |drepper.fsp+rhbz at gmail dot com
--- Comment #4 from Ulrich Drepper <drepper.fsp+rhbz at gmail dot com> ---
This BZ came out of a discussion around C++ function call chaining along the
line of:
void f1(std::string& s, int a)
{
std::cout << "hello " << s;
if (a != 0)
std::cout << a;
std::cout << '\n';
}
The 'if' prevents one single series of calls through operator<< from being used
and the compiler has reload std::cout from memory every time. There are ugly
work-arounds in the source to get the desired behaviour but this should happen
automatically. The work-arounds are too ugly and there is lots of code out
there.
One way would be to expose a way to specify one of the arguments is returned.
Jakub mentioned that there is already internally a way to use the "fn spec"
attribute. How about exposing this explicitly as a function attribute?
Jakub also raised the point how this should be applied to member functions. I
suggest that the parameter for the attribute is really a number (not parameter
name) and that argument 1 (or 0, if you want the count start at zero) refers to
'this' in case of member functions.
How about this?
>From gcc-bugs-return-662767-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 12:57:16 2019
Return-Path: <gcc-bugs-return-662767-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113800 invoked by alias); 9 Dec 2019 12:57: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 113759 invoked by uid 48); 9 Dec 2019 12:57:12 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92503] [OpenACC] Behavior of 'acc_free' if the memory space is still used in a mapping
Date: Mon, 09 Dec 2019 12:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92503-4-TCm3ZkTiBc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92503-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92503-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00837.txt.bz2
Content-length: 1127
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92503
--- Comment #2 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Created attachment 47445
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47445&action=edit
[PR92503] [OpenACC] Don't silently 'acc_unmap_data' in 'acc_free'
(In reply to jules from comment #1)
> FWIW, I don't think we should do this implicit unmapping
Julian, please have a look at the patch I'm attaching.
There are nvptx offloading TODOs in
'libgomp.oacc-c-c++-common/acc_free-pr92503-4.c',
'libgomp.oacc-c-c++-common/acc_free-pr92503-4-2.c'. Can you easily (please
don't spend much time on this) what's going wrong? Otherwise I shall commit
that XFAILed.
Please also verify whether there are any changes necessary for AMD GCN
offloading, in particular un-XFAILing the two nvptx ones, I suppose?
> particularly since
> it implies an expensive device-to-host-address lookup.
ACK. That's not yet done; let's first wait what OpenACC is going to require.
I had the idea that we might actually keep such additional/expensive
sanity-checking, but guard it by an environment variable.
>From gcc-bugs-return-662768-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 12:58:02 2019
Return-Path: <gcc-bugs-return-662768-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115218 invoked by alias); 9 Dec 2019 12: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 115016 invoked by uid 48); 9 Dec 2019 12:57:58 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92865] [10 Regression] error: unrecognizable insn: in extract_insn, at recog.c:2294 since r279107
Date: Mon, 09 Dec 2019 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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: crazylht at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: liuhongt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92865-4-V118k4QaR0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00838.txt.bz2
Content-length: 933
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
--- Comment #5 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Richard Biener from comment #4)
> (In reply to Hongtao.liu from comment #3)
> > Since TARGET_XOP only supports 128-bit vector compare,
> > ix86_valid_mask_cmp_mode should also handle 256/512-bit vector compare when
> > avx512f is avalable.
> >
> >
> > untested patch
> >
> > @@ -3428,7 +3428,7 @@ static bool
> > ix86_valid_mask_cmp_mode (machine_mode mode)
> > {
> > /* XOP has its own vector conditional movement. */
> > - if (TARGET_XOP)
> > + if (TARGET_XOP && GET_MODE_SIZE (mode) == 128)
> > return false;
>
> Shouldn't we do sth like TARGET_XOP && !TARGET_AVX512F instead? That is
> maybe simply elide that check completely, not sure why it was added.
True, thanks
>
> > /* AVX512F is needed for mask operation. */
> >
> > I'll add some testcase later.
>From gcc-bugs-return-662769-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 13:05:59 2019
Return-Path: <gcc-bugs-return-662769-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64480 invoked by alias); 9 Dec 2019 13: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 52811 invoked by uid 48); 9 Dec 2019 13:05:54 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92867] Use ERF_RETURNS_ARG in more places
Date: Mon, 09 Dec 2019 13:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: 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-92867-4-Cjjfp9o9LE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00839.txt.bz2
Content-length: 895
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92867
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
GCC already has various attributes that take argument positions, e.g. the
nonnull, alloc_size, format, format_arg, so we should follow what is used for
those for this argument.
E.g. for format_arg we document:
The parameter STRING-INDEX specifies which argument is the format
string argument (starting from one). Since non-static C++ methods
have an implicit 'this' argument, the arguments of such methods
should be counted from two.
and similarly for format, for nonnull and alloc_size we don't, so it might be
worth checking what we actually do.
There is also the case of an artificial argument holding address to the return
slot, I think that is what comes up only in RTL and would hope RTL handles it
right, but it is worth checking that too.
>From gcc-bugs-return-662770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 13:13:39 2019
Return-Path: <gcc-bugs-return-662770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88646 invoked by alias); 9 Dec 2019 13:13: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 88576 invoked by uid 48); 9 Dec 2019 13:13:35 -0000
From: "samuel.thibault@ens-lyon.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92861] Passes relative time to sem_timedwait on GNU/Hurd
Date: Mon, 09 Dec 2019 13:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: samuel.thibault@ens-lyon.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92861-4-v1BHjbB1Kb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00840.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92861
--- Comment #3 from Samuel Thibault <samuel.thibault@ens-lyon.org> ---
Created attachment 47446
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47446&action=edit
fix duplicate definition
Ah, sorry, _CLOCK_REALTIME is actually already getting defined in the generated
libgo/runtime_sysinfo.go file, the attached patch is needed on top of what was
already committed.
>From gcc-bugs-return-662771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 13:14:01 2019
Return-Path: <gcc-bugs-return-662771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89788 invoked by alias); 9 Dec 2019 13:14: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 89710 invoked by uid 48); 9 Dec 2019 13:13:58 -0000
From: "samuel.thibault@ens-lyon.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92861] Passes relative time to sem_timedwait on GNU/Hurd
Date: Mon, 09 Dec 2019 13:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: samuel.thibault@ens-lyon.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92861-4-OEZPjRAEqo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00841.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92861
Samuel Thibault <samuel.thibault@ens-lyon.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|FIXED |---
--- Comment #4 from Samuel Thibault <samuel.thibault@ens-lyon.org> ---
Reopening the bug for the fix to be commited
>From gcc-bugs-return-662772-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 13:16:25 2019
Return-Path: <gcc-bugs-return-662772-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97598 invoked by alias); 9 Dec 2019 13:16: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 97538 invoked by uid 48); 9 Dec 2019 13:16:21 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92840] [OpenACC] Disallow 'acc_unmap_data' for everything other than 'acc_map_data'
Date: Mon, 09 Dec 2019 13:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed attachments.created
Message-ID: <bug-92840-4-DaKJ8zkBo6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00842.txt.bz2
Content-length: 864
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92840
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-09
Assignee|unassigned at gcc dot gnu.org |tschwinge at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Created attachment 47447
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47447&action=edit
[PR92840] [OpenACC] Refuse 'acc_unmap_data' unless mapped by 'acc_map_data'
Julian, any comments on the attached patch?
The TODO we shall deal with later; certainly not a priority right now.
>From gcc-bugs-return-662773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 13:30:54 2019
Return-Path: <gcc-bugs-return-662773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66241 invoked by alias); 9 Dec 2019 13: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 66154 invoked by uid 48); 9 Dec 2019 13:30:49 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90282] internal compiler error: qsort checking failed in snapshot-20190429
Date: Mon, 09 Dec 2019 13:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90282-4-1bcMWf9vlN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00843.txt.bz2
Content-length: 6594
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90282
--- Comment #3 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
This problem is still present in r278870:
../../src/gcc/ubsan.c: In function 'tree_node* ubsan_type_descriptor(tree,
ubsan_print_style)':
../../src/gcc/ubsan.c:409:33: warning: unterminated quote character ''' in
format [-Wformat-diag]
409 | pp_printf (&pretty_name, "'%s%s%s%s%s%s%s",
| ^
../../src/gcc/ubsan.c:428:36: warning: spurious trailing space in format
[-Wformat-diag]
428 | pp_printf (&pretty_name, "'%s ", tname);
| ^
../../src/gcc/ubsan.c:428:33: warning: unterminated quote character ''' in
format [-Wformat-diag]
428 | pp_printf (&pretty_name, "'%s ", tname);
| ^
/<<PKGBUILDDIR>>/build/./prev-gcc/xg++ -B/<<PKGBUILDDIR>>/build/./prev-gcc/
-B/usr/lib/gcc-snapshot/ia64-linux-gnu/bin/ -nostdinc++
-B/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/src/.libs
-B/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/libsupc++/.libs
-I/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/include/ia64-linux-gnu
-I/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/include
-I/<<PKGBUILDDIR>>/src/libstdc++-v3/libsupc++
-L/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/src/.libs
-L/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/libsupc++/.libs
-fno-PIE -c -DUSE_LIBUNWIND_EXCEPTIONS -g -O2 -fno-checking -gtoggle -DIN_GCC
-fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall
-Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute
-Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -fno-common -DHAVE_CONFIG_H -I. -I. -I../../src/gcc
-I../../src/gcc/. -I../../src/gcc/../include -I../../src/gcc/../libcpp/include
-I../../src/gcc/../libdecnumber -I../../src/gcc/../libdecnumber/dpd
-I../libdecnumber -I../../src/gcc/../libbacktrace -o sancov.o -MT sancov.o
-MMD -MP -MF ./.deps/sancov.TPo ../../src/gcc/sancov.c
/<<PKGBUILDDIR>>/build/./prev-gcc/xg++ -B/<<PKGBUILDDIR>>/build/./prev-gcc/
-B/usr/lib/gcc-snapshot/ia64-linux-gnu/bin/ -nostdinc++
-B/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/src/.libs
-B/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/libsupc++/.libs
-I/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/include/ia64-linux-gnu
-I/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/include
-I/<<PKGBUILDDIR>>/src/libstdc++-v3/libsupc++
-L/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/src/.libs
-L/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/libsupc++/.libs
-fno-PIE -c -DUSE_LIBUNWIND_EXCEPTIONS -g -O2 -fno-checking -gtoggle -DIN_GCC
-fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall
-Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute
-Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -fno-common -DHAVE_CONFIG_H -I. -I. -I../../src/gcc
-I../../src/gcc/. -I../../src/gcc/../include -I../../src/gcc/../libcpp/include
-I../../src/gcc/../libdecnumber -I../../src/gcc/../libdecnumber/dpd
-I../libdecnumber -I../../src/gcc/../libbacktrace -o tree-call-cdce.o -MT
tree-call-cdce.o -MMD -MP -MF ./.deps/tree-call-cdce.TPo
../../src/gcc/tree-call-cdce.c
/<<PKGBUILDDIR>>/build/./prev-gcc/xg++ -B/<<PKGBUILDDIR>>/build/./prev-gcc/
-B/usr/lib/gcc-snapshot/ia64-linux-gnu/bin/ -nostdinc++
-B/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/src/.libs
-B/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/libsupc++/.libs
-I/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/include/ia64-linux-gnu
-I/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/include
-I/<<PKGBUILDDIR>>/src/libstdc++-v3/libsupc++
-L/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/src/.libs
-L/<<PKGBUILDDIR>>/build/prev-ia64-linux-gnu/libstdc++-v3/libsupc++/.libs
-fno-PIE -c -DUSE_LIBUNWIND_EXCEPTIONS -g -O2 -fno-checking -gtoggle -DIN_GCC
-fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall
-Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute
-Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros
-Wno-overlength-strings -fno-common -DHAVE_CONFIG_H -I. -I. -I../../src/gcc
-I../../src/gcc/. -I../../src/gcc/../include -I../../src/gcc/../libcpp/include
-I../../src/gcc/../libdecnumber -I../../src/gcc/../libdecnumber/dpd
-I../libdecnumber -I../../src/gcc/../libbacktrace -o tree-cfg.o -MT
tree-cfg.o -MMD -MP -MF ./.deps/tree-cfg.TPo ../../src/gcc/tree-cfg.c
../../src/gcc/tree-call-cdce.c: In function 'void
gen_shrink_wrap_conditions(gcall*, vec<gimple*>, unsigned int*)':
../../src/gcc/tree-call-cdce.c:793:1: error: qsort comparator non-negative on
sorted output: 1
793 | }
| ^
during RTL pass: mach
../../src/gcc/tree-call-cdce.c:793:1: internal compiler error: qsort checking
failed
0x40000000044ce41f qsort_chk_error
../../src/gcc/vec.c:214
0x40000000044cf3bf qsort_chk(void*, unsigned long, unsigned long, int (*)(void
const*, void const*, void*), void*)
../../src/gcc/vec.c:256
0x400000000458daaf gcc_qsort(void*, unsigned long, unsigned long, int (*)(void
const*, void const*))
../../src/gcc/sort.cc:270
0x40000000040b72ff ready_sort_real
../../src/gcc/haifa-sched.c:3095
0x40000000040b744f ready_sort
../../src/gcc/haifa-sched.c:3111
0x40000000040d3b9f schedule_block(basic_block_def**, void*)
../../src/gcc/haifa-sched.c:6699
0x400000000431747f schedule_ebb(rtx_insn*, rtx_insn*, bool)
../../src/gcc/sched-ebb.c:536
0x40000000043181ef schedule_ebbs()
../../src/gcc/sched-ebb.c:655
0x400000000340e94f ia64_reorg
../../src/gcc/config/ia64/ia64.c:9854
0x40000000024147ef execute
../../src/gcc/reorg.c:3981
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-snapshot/README.Bugs> for instructions.
Preprocessed source stored into /tmp/ccQzjkVp.out file, please attach this to
your bugreport.
Compiler dump can see in Debian's build log:
https://buildd.debian.org/status/fetch.php?pkg=gcc-snapshot&arch=ia64&ver=1%3A20191130-1&stamp=1575698799&raw=0
There have been a few snapshots after the 20190429 one where the problem didn't
show, see: https://buildd.debian.org/status/logs.php?pkg=gcc-snapshot&arch=ia64
>From gcc-bugs-return-662774-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 13:40:58 2019
Return-Path: <gcc-bugs-return-662774-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31164 invoked by alias); 9 Dec 2019 13:40: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 25261 invoked by uid 48); 9 Dec 2019 13:40:54 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90282] internal compiler error: qsort checking failed in snapshot-20190429
Date: Mon, 09 Dec 2019 13:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90282-4-QpkCgUClBH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00844.txt.bz2
Content-length: 151
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90282
--- Comment #4 from Andreas Schwab <schwab@linux-m68k.org> ---
Workaround: use release checking.
>From gcc-bugs-return-662775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 13:44:53 2019
Return-Path: <gcc-bugs-return-662775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62629 invoked by alias); 9 Dec 2019 13:44: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 57955 invoked by uid 48); 9 Dec 2019 13:44:49 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92840] [OpenACC] Disallow 'acc_unmap_data' for everything other than 'acc_map_data'
Date: Mon, 09 Dec 2019 13:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92840-4-92kdaBvx68@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00845.txt.bz2
Content-length: 134
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92840
--- Comment #2 from jules at gcc dot gnu.org ---
I think that looks OK, thanks.
>From gcc-bugs-return-662776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 13:46:54 2019
Return-Path: <gcc-bugs-return-662776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93655 invoked by alias); 9 Dec 2019 13:46: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 93591 invoked by uid 48); 9 Dec 2019 13:46:50 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92854] [OpenACC] Always-true conditional in 'libgomp/oacc-mem.c:acc_unmap_data'?
Date: Mon, 09 Dec 2019 13:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92854-4-SaXKmVF72J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00846.txt.bz2
Content-length: 222
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92854
--- Comment #5 from jules at gcc dot gnu.org ---
Huh, yes, I missed that line in the spec (about existing mappings). I'll have a
look at the test case you mentioned.
>From gcc-bugs-return-662777-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 14:00:01 2019
Return-Path: <gcc-bugs-return-662777-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53408 invoked by alias); 9 Dec 2019 14:00: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 53309 invoked by uid 55); 9 Dec 2019 13:59:56 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91226] wrong propagation of non-canonical _Decimal64 and _Decimal128 constant (BID only)
Date: Mon, 09 Dec 2019 14: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91226-4-w1g8pckB6P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91226-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91226-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00847.txt.bz2
Content-length: 2623
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91226
--- Comment #3 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Author: jsm28
Date: Mon Dec 9 13:59:24 2019
New Revision: 279129
URL: https://gcc.gnu.org/viewcvs?rev=279129&root=gcc&view=rev
Log:
Fix libdecnumber handling of non-canonical BID significands (PR
middle-end/91226).
As reported in bug 91226, the libdecnumber code used on the host to
interpret DFP values in the BID encoding fails, for _Decimal64 and
_Decimal128, to check for the case where a significand is too large
and so specified in IEEE 754 to be a non-canonical encoding of the
zero significand. This patch adds the required handling of that case,
together with tests both using -O2 (testing this host code) and -O0
(testing libgcc code, which already worked before the patch); the
tests also cover _Decimal32, which already had the required check.
In the _Decimal128 case, where the code previously completely ignored
the case where the first four bits of the combination field are 1100,
1101 or 1110, the logic for determining the correct quantum exponent
in that case is also newly added by this patch, so tests are added for
that as well (again, libgcc already handled it correctly when the
conversion was done at runtime rather than at compile time).
Bootstrapped with no regressions for x86_64-pc-linux-gnu.
PR middle-end/91226
libdecnumber:
* bid/bid2dpd_dpd2bid.c (_bid_to_dpd64): Handle non-canonical
significands.
(_bid_to_dpd128): Likewise. Check for case where combination
field starts 1100, 1101 or 1110.
gcc/testsuite:
* gcc.dg/dfp/bid-non-canonical-d128-1.c,
gcc.dg/dfp/bid-non-canonical-d128-2.c,
gcc.dg/dfp/bid-non-canonical-d128-3.c,
gcc.dg/dfp/bid-non-canonical-d128-4.c,
gcc.dg/dfp/bid-non-canonical-d32-1.c,
gcc.dg/dfp/bid-non-canonical-d32-2.c,
gcc.dg/dfp/bid-non-canonical-d64-1.c,
gcc.dg/dfp/bid-non-canonical-d64-2.c: New tests.
Added:
trunk/gcc/testsuite/gcc.dg/dfp/bid-non-canonical-d128-1.c
trunk/gcc/testsuite/gcc.dg/dfp/bid-non-canonical-d128-2.c
trunk/gcc/testsuite/gcc.dg/dfp/bid-non-canonical-d128-3.c
trunk/gcc/testsuite/gcc.dg/dfp/bid-non-canonical-d128-4.c
trunk/gcc/testsuite/gcc.dg/dfp/bid-non-canonical-d32-1.c
trunk/gcc/testsuite/gcc.dg/dfp/bid-non-canonical-d32-2.c
trunk/gcc/testsuite/gcc.dg/dfp/bid-non-canonical-d64-1.c
trunk/gcc/testsuite/gcc.dg/dfp/bid-non-canonical-d64-2.c
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/libdecnumber/ChangeLog
trunk/libdecnumber/bid/bid2dpd_dpd2bid.c
>From gcc-bugs-return-662778-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 14:01:12 2019
Return-Path: <gcc-bugs-return-662778-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55334 invoked by alias); 9 Dec 2019 14:01: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 55255 invoked by uid 48); 9 Dec 2019 14:01:02 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/91226] wrong propagation of non-canonical _Decimal64 and _Decimal128 constant (BID only)
Date: Mon, 09 Dec 2019 14: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: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91226-4-82VtzbSVRj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91226-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91226-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00848.txt.bz2
Content-length: 231
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91226
--- Comment #4 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Fixed for GCC 10. Leaving open for now for possible backports to GCC 9 and 8
branches as a wrong-code fix.
>From gcc-bugs-return-662779-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 14:05:44 2019
Return-Path: <gcc-bugs-return-662779-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124600 invoked by alias); 9 Dec 2019 14:05: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 124530 invoked by uid 48); 9 Dec 2019 14:05:40 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92843] [OpenACC] Disallow 'acc_delete' etc. for everything without a dynamic reference count
Date: Mon, 09 Dec 2019 14:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92843-4-cbInCZnF3v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00849.txt.bz2
Content-length: 633
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92843
--- Comment #4 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Created attachment 47448
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47448&action=edit
[WIP] [PR92843] [OpenACC] Disallow 'acc_delete' etc. for TODOeverything without
a dynamic reference count
Julian, please have a look at the WIP patch I'm attaching.
Resolving the '#if 0' will of course depend on settling on a reading of the
interactions between structured and dynamic reference counting. (Your thoughts
on that?) Per my current understanding, we would simply drop the '#if 0'
block.
>From gcc-bugs-return-662780-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 14:08:19 2019
Return-Path: <gcc-bugs-return-662780-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1626 invoked by alias); 9 Dec 2019 14: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 1540 invoked by uid 48); 9 Dec 2019 14:08:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92825] Unnecesary stack protection in Firefox's LightPixel.
Date: Mon, 09 Dec 2019 14:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
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: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-92825-4-cxAO10gCbM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92825-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00850.txt.bz2
Content-length: 579
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92825
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 47449
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47449&action=edit
gcc10-pr92825.patch
Untested fix.
>From gcc-bugs-return-662781-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 14:12:06 2019
Return-Path: <gcc-bugs-return-662781-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5291 invoked by alias); 9 Dec 2019 14:12:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5216 invoked by uid 48); 9 Dec 2019 14:12:02 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92843] [OpenACC] Disallow 'acc_delete' etc. for everything without a dynamic reference count
Date: Mon, 09 Dec 2019 14:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92843-4-W8jRf0kF6S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00851.txt.bz2
Content-length: 528
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92843
--- Comment #5 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Created attachment 47450
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47450&action=edit
[WIP] [PR92843, or is this a separate PR?] Properly handly dynamic reference
counts for TODO'REFCOUNT_INFINITY'
Julian, please also have a look at the other WIP patch I'm attaching. (I think
I convinced myself that this doesn't have to be a separate PR from this one.)
Your thoughts on that one?
>From gcc-bugs-return-662782-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 14:25:31 2019
Return-Path: <gcc-bugs-return-662782-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39512 invoked by alias); 9 Dec 2019 14:25:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39459 invoked by uid 48); 9 Dec 2019 14:25:27 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92868] [10 Regression] ICE: tree check: expected integer_cst, have ssa_name in to_wide, at tree.h:5855
Date: Mon, 09 Dec 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work assigned_to everconfirmed cf_known_to_fail
Message-ID: <bug-92868-4-UNAhe8f44g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92868-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92868-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00852.txt.bz2
Content-length: 783
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92868
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-09
CC| |marxin at gcc dot gnu.org
Known to work| |9.2.0
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |10.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r278983.
>From gcc-bugs-return-662783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 14:31:09 2019
Return-Path: <gcc-bugs-return-662783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57420 invoked by alias); 9 Dec 2019 14:31: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 57379 invoked by uid 48); 9 Dec 2019 14:31:05 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92838] ICE (internal compiler error) calling lambda object with requires clause (in in dependent_type_p)
Date: Mon, 09 Dec 2019 14:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 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 cc everconfirmed
Message-ID: <bug-92838-4-6N93YvOY0T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92838-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92838-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00853.txt.bz2
Content-length: 686
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92838
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-09
CC| |jason at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r277655, it was rejected before the revision.
>From gcc-bugs-return-662784-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 14:46:41 2019
Return-Path: <gcc-bugs-return-662784-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112628 invoked by alias); 9 Dec 2019 14:46: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 112553 invoked by uid 48); 9 Dec 2019 14:46:36 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92843] [OpenACC] Disallow 'acc_delete' etc. for everything without a dynamic reference count
Date: Mon, 09 Dec 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: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92843-4-HjRDJxKh9H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00854.txt.bz2
Content-length: 556
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92843
--- Comment #6 from jules at gcc dot gnu.org ---
Please don't start making changes to the reference-counting code that is being
replaced by my overhaul patch. The existing code was rewritten for a reason --
that being, I hit various problems with it (albeit long since forgotten) that
interfered with the manual deep-copy implementation. We have refcount
self-checking code for the overhauled code.
We can address corner-case bug fixes as follow-ons once the main overhaul patch
is committed.
>From gcc-bugs-return-662785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 14:50:22 2019
Return-Path: <gcc-bugs-return-662785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122182 invoked by alias); 9 Dec 2019 14:50: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 122092 invoked by uid 48); 9 Dec 2019 14:50:18 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92398] [10 regression] error in update of gcc.target/powerpc/pr72804.c in r277872
Date: Mon, 09 Dec 2019 14:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-92398-4-ArrUwUVmIZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00855.txt.bz2
Content-length: 512
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92398
Bill Schmidt <wschmidt at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-09
Ever confirmed|0 |1
--- Comment #11 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Confirmed. ;-) Is this ready to close?
>From gcc-bugs-return-662786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 14:52:01 2019
Return-Path: <gcc-bugs-return-662786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125433 invoked by alias); 9 Dec 2019 14: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 125360 invoked by uid 48); 9 Dec 2019 14:51:57 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92848] [OpenACC] Memory leak for simple 'acc_create', 'acc_delete' sequence
Date: Mon, 09 Dec 2019 14:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed attachments.created
Message-ID: <bug-92848-4-tUMHHsvnf3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00856.txt.bz2
Content-length: 1062
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92848
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-09
Assignee|unassigned at gcc dot gnu.org |tschwinge at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Created attachment 47451
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47451&action=edit
[WIP] [PR92848] [OpenACC] Use 'GOMP_MAP_VARS_ENTER_DATA' for dynamic data
lifetimes
Julian, your thoughts on the WIP patch I'm attaching, please?
As implied by
<http://mid.mail-archive.com/878snl36eu.fsf@euler.schwinge.homeip.net>, using
'gomp_remove_var' instead of 'gomp_remove_var_async' is is not causing any
problems for nvptx offloading (strange?); does it for AMD GCN offloading?
>From gcc-bugs-return-662787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 15:06:53 2019
Return-Path: <gcc-bugs-return-662787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7014 invoked by alias); 9 Dec 2019 15:06: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 6976 invoked by uid 48); 9 Dec 2019 15:06:49 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92848] [OpenACC] Memory leak for simple 'acc_create', 'acc_delete' sequence
Date: Mon, 09 Dec 2019 15:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92848-4-0AsNmRd15c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00857.txt.bz2
Content-length: 316
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92848
--- Comment #2 from jules at gcc dot gnu.org ---
Again, please don't change this code under the feet of the refcount overhaul
patch! Using the (currently OpenMP-specific) GOMP_MAP_VARS_ENTER_DATA is going
to end up mighty confusing from OpenACC-specific code.
>From gcc-bugs-return-662788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 15:20:04 2019
Return-Path: <gcc-bugs-return-662788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99868 invoked by alias); 9 Dec 2019 15:20: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 99731 invoked by uid 48); 9 Dec 2019 15:19:58 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92868] [10 Regression] ICE: tree check: expected integer_cst, have ssa_name in to_wide, at tree.h:5855
Date: Mon, 09 Dec 2019 15: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: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92868-4-PTlHJfCazD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92868-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92868-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00858.txt.bz2
Content-length: 6058
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92868
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> ---
That code has lots of issues. Some in patch form as I was going through them:
gimple_call_alloc_size: for the case when size is INTEGER_CST and it is the one
argument alloc_size, I don't see a reason not to return size earlier, there is
no need to wi::to_wide. I don't see a point in computing rng1[0] and rng2[0]
when nothing really uses it (write-only element). Some formatting and typo in
comment.
I don't understand why you are using wi::sign_mask, the normal test for
negative wide_int when it is treated as signed integer of the corresponding
precision is wi::neg_p, that is more readable and descriptive. If something is
tested on the wide ints with extra precision and the ::from was UNSIGNED, that
is of course not possible, but sign_mask will not work in that case either.
And if it is ::from with SIGNED, neg_p should work fine too.
There is a weird:
wide_int declsize = wi::to_wide (size);
if (wi::sign_mask (dstoffrng[0]) > 0)
declsize += dstoffrng[0];
that condition is never true, sign_mask will only ever return 0 or -1:
return (HOST_WIDE_INT) (high) < 0 ? -1 : 0;
None of this fixes the ICE. How exactly to fix that depends on whether *poff
can be something other than INTEGER_CST or not. If it can be only INTEGER_CST,
then whatever code is setting *poff to non-INTEGER_CST should instead punt or
set to some safe value, whatever, if it can be anything, then while it is fine
to call functions like integer_zerop etc. on that, tree_int_cst_sgn requires
the argument to be INTEGER_CST only, so there needs to be TREE_CODE (*poff) ==
INTEGER_CST && tree_int_csgn (*poff) < 0 instead. Or perhaps you want
!tree_expr_nonnegative_p (*poff) instead?
--- gcc/builtins.c.jj 2019-12-05 09:47:23.178710510 +0100
+++ gcc/builtins.c 2019-12-09 15:52:55.951404452 +0100
@@ -3746,36 +3746,33 @@ gimple_call_alloc_size (gimple *stmt)
}
tree size = gimple_call_arg (stmt, argidx1);
+ if (argidx2 > nargs && TREE_CODE (size) == INTEGER_CST)
+ return size;
wide_int rng1[2];
if (TREE_CODE (size) == INTEGER_CST)
- rng1[0] = rng1[1] = wi::to_wide (size);
+ rng1[1] = wi::to_wide (size);
else if (TREE_CODE (size) != SSA_NAME
|| get_range_info (size, rng1, rng1 + 1) != VR_RANGE)
return NULL_TREE;
- if (argidx2 > nargs && TREE_CODE (size) == INTEGER_CST)
- return size;
-
/* To handle ranges do the math in wide_int and return the product
of the upper bounds as a constant. Ignore anti-ranges. */
- tree n = argidx2 < nargs ? gimple_call_arg (stmt, argidx2) :
integer_one_node;
+ tree n
+ = argidx2 < nargs ? gimple_call_arg (stmt, argidx2) : integer_one_node;
wide_int rng2[2];
if (TREE_CODE (n) == INTEGER_CST)
- rng2[0] = rng2[1] = wi::to_wide (n);
+ rng2[1] = wi::to_wide (n);
else if (TREE_CODE (n) != SSA_NAME
|| get_range_info (n, rng2, rng2 + 1) != VR_RANGE)
return NULL_TREE;
- /* Extend to the maximum precsion to avoid overflow. */
+ /* Extend to the maximum precision to avoid overflow. */
const int prec = ADDR_MAX_PRECISION;
- rng1[0] = wide_int::from (rng1[0], prec, UNSIGNED);
rng1[1] = wide_int::from (rng1[1], prec, UNSIGNED);
- rng2[0] = wide_int::from (rng2[0], prec, UNSIGNED);
rng2[1] = wide_int::from (rng2[1], prec, UNSIGNED);
/* Return the lesser of SIZE_MAX and the product of the upper bounds. */
- rng1[0] = rng1[0] * rng2[0];
rng1[1] = rng1[1] * rng2[1];
tree size_max = TYPE_MAX_VALUE (sizetype);
if (wi::gtu_p (rng1[1], wi::to_wide (size_max, prec)))
@@ -3853,7 +3850,7 @@ compute_objsize (tree dest, int ostype,
/* Ignore negative offsets for now. For others,
use the lower bound as the most optimistic
estimate of the (remaining) size. */
- if (wi::sign_mask (wioff))
+ if (wi::neg_p (wioff))
;
else if (wi::ltu_p (wioff, wisiz))
{
@@ -3882,9 +3879,8 @@ compute_objsize (tree dest, int ostype,
/* Ignore negative offsets for now. For others,
use the lower bound as the most optimistic
- estimate of the (remaining)size. */
- if (wi::sign_mask (min)
- || wi::sign_mask (max))
+ estimate of the (remaining) size. */
+ if (wi::neg_p (min) || wi::neg_p (max))
;
else if (wi::ltu_p (min, wisiz))
{
@@ -3912,8 +3908,7 @@ compute_objsize (tree dest, int ostype,
if (!ostype)
return NULL_TREE;
- if (TREE_CODE (dest) == ARRAY_REF
- || TREE_CODE (dest) == MEM_REF)
+ if (TREE_CODE (dest) == ARRAY_REF || TREE_CODE (dest) == MEM_REF)
{
tree ref = TREE_OPERAND (dest, 0);
tree off = TREE_OPERAND (dest, 1);
@@ -3972,7 +3967,7 @@ compute_objsize (tree dest, int ostype,
*poff = size_binop (PLUS_EXPR, *poff, off);
}
- if (wi::sign_mask (offrng[0]) >= 0)
+ if (!wi::neg_p (offrng[0]))
{
if (TREE_CODE (size) != INTEGER_CST)
return NULL_TREE;
@@ -4007,7 +4002,7 @@ compute_objsize (tree dest, int ostype,
declsize += dstoffrng[0];
offrng[1] += dstoffrng[1];
- if (wi::sign_mask (offrng[1]) < 0)
+ if (wi::neg_p (offrng[1]))
return size_zero_node;
return wide_int_to_tree (sizetype, declsize);
>From gcc-bugs-return-662789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 15:58:22 2019
Return-Path: <gcc-bugs-return-662789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1181 invoked by alias); 9 Dec 2019 15:58:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1104 invoked by uid 48); 9 Dec 2019 15:58:18 -0000
From: "iii at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)
Date: Mon, 09 Dec 2019 15:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: EH, ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iii at linux dot ibm.com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92007-4-ZBI57ZKLQE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00859.txt.bz2
Content-length: 1699
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007
--- Comment #27 from Ilya Leoshkevich <iii at linux dot ibm.com> ---
With
-DSPEC_CPU -DNDEBUG -DPERL_CORE -O3 -save-temps=obj -fopt-info-vec-optimized
-DSPEC_CPU_LP64 -DSPEC_CPU_LINUX_X64 -fgnu89-inline
on gcc113 I can see 2% slowdown:
r277511 (without this fix): 880.09s
r277515 (with this fix): 897.85s
The function that degraded the most is indeed S_regmatch:
$ perf diff perf-9760321.data perf-44b2b4c.data
32.24% exe [.] S_regmatch
8.92% exe [.] S_find_byclass.isra.0
6.80% +0.28% libc-2.19.so [.] 0x000000000007dec0
5.20% exe [.] S_regtry
However, the "shape" of S_regmatch did not change, that is, when all
offsets and register numbers are replaced with "x" in the objdump
output, the old and the new versions are identical. This hints at some
microarchitectural effect - aliasing in the branch predictor maybe?
From my perspective, this happens too often, so I use the following test
to rule this out: just add a nop at the beginning of the problematic
function. This changes all the offsets and makes aliasing situation
completely different. And indeed, by adding a single nop to S_regmatch,
I get wildly different results (for now this is just 1 repeat, I will
run best-of-3 overnight):
r277511 (without this fix): 929.1s
r277515 (with this fix): 931.48s
>From gcc-bugs-return-662790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 16:04:01 2019
Return-Path: <gcc-bugs-return-662790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17038 invoked by alias); 9 Dec 2019 16:04: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 16969 invoked by uid 48); 9 Dec 2019 16:03:56 -0000
From: "mpolacek 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: Mon, 09 Dec 2019 16: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: 9.2.0
X-Bugzilla-Keywords: ice-checking, needs-bisection
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: cc
Message-ID: <bug-92852-4-ZyIMdb4xfZ@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: 2019-12/txt/msg00860.txt.bz2
Content-length: 421
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92852
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Might be dup/related to bug 91165.
>From gcc-bugs-return-662791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 16:40:31 2019
Return-Path: <gcc-bugs-return-662791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108827 invoked by alias); 9 Dec 2019 16:40:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108793 invoked by uid 48); 9 Dec 2019 16:40:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92841] Optimize -fstack-protector-strong code generation a bit
Date: Mon, 09 Dec 2019 16:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-92841-4-ldPTYESbzb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00861.txt.bz2
Content-length: 758
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-09
Ever confirmed|0 |1
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reduced testcase that reproduces this with -O2 -fstack-protector-strong on
x86_64-linux -m64:
const struct S { int b; } c[] = {30, 12, 20, 0, 11};
void bar (int *);
void
foo (void)
{
int e[4];
const struct S *a;
for (a = c; a < c + sizeof (c); a++)
if (a->b)
bar (e);
}
>From gcc-bugs-return-662792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 17:21:24 2019
Return-Path: <gcc-bugs-return-662792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56516 invoked by alias); 9 Dec 2019 17: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 56205 invoked by uid 48); 9 Dec 2019 17:21:20 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92867] Use ERF_RETURNS_ARG in more places
Date: Mon, 09 Dec 2019 17:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
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: cc
Message-ID: <bug-92867-4-hUej0QmuyV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00862.txt.bz2
Content-length: 694
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92867
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
The "returns-argument" attribute should also be used to help detect buffer
overflow after returning from functions declared with it (either built-ins or
user-defined):
__attribute__ ((returns_arg (1))) char* f (char*);
char a[4], b[8];
void g (void)
{
memcpy (b, f (a), sizeof b); // reads 8 bytes from a
}
>From gcc-bugs-return-662793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 17:30:03 2019
Return-Path: <gcc-bugs-return-662793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77169 invoked by alias); 9 Dec 2019 17: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 76948 invoked by uid 48); 9 Dec 2019 17:29:58 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92868] [10 Regression] ICE: tree check: expected integer_cst, have ssa_name in to_wide, at tree.h:5855
Date: Mon, 09 Dec 2019 17:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: 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: 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-92868-4-Bgb0Mn59H6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92868-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92868-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00863.txt.bz2
Content-length: 271
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92868
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Martin, thanks for CC'ing me on bugs I cause, but please leave assigning them
to me or whoever might choose to come up with a fix before I get to it.
>From gcc-bugs-return-662794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 17:32:19 2019
Return-Path: <gcc-bugs-return-662794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81190 invoked by alias); 9 Dec 2019 17: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 81155 invoked by uid 48); 9 Dec 2019 17:32:14 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92857] -Wsign-conversion flag issues false positives for expression using typedef'ed unsigned types
Date: Mon, 09 Dec 2019 17: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: 5.4.0
X-Bugzilla-Keywords: diagnostic
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-92857-4-8iznjscIlq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92857-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00864.txt.bz2
Content-length: 703
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92857
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Joshua Saxby from comment #2)
> (In reply to Richard Biener from comment #1)
> > I think the warning is about foo - bar being carried out in type 'int' due to
> > integer promotion and that converted to size_t which may turn the negative
> > result into a positive.
>
> That could be the issue, although I would expect the integer promotion to
> promote to an unsigned integer type rather than a signed one. Am I mistaken
> in this assumption?
YES you are. If a type is smaller than int and fits into int, then it is
prompoted to int (and not unsigned int).
>From gcc-bugs-return-662795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 17:38:04 2019
Return-Path: <gcc-bugs-return-662795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84354 invoked by alias); 9 Dec 2019 17:38: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 84138 invoked by uid 48); 9 Dec 2019 17:37:59 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92868] [10 Regression] ICE: tree check: expected integer_cst, have ssa_name in to_wide, at tree.h:5855
Date: Mon, 09 Dec 2019 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: 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
Message-ID: <bug-92868-4-CAA1V6PIV9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92868-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92868-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00865.txt.bz2
Content-length: 463
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92868
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
The problem is fixed by the patch for PR 91582:
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00478.html
>From gcc-bugs-return-662796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 17:42:22 2019
Return-Path: <gcc-bugs-return-662796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34744 invoked by alias); 9 Dec 2019 17:42: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 34667 invoked by uid 48); 9 Dec 2019 17:42:18 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92868] [10 Regression] ICE: tree check: expected integer_cst, have ssa_name in to_wide, at tree.h:5855
Date: Mon, 09 Dec 2019 17: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: ice-on-valid-code, patch
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: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92868-4-3pvHQJXVSm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92868-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92868-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00866.txt.bz2
Content-length: 452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92868
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #4)
> The problem is fixed by the patch for PR 91582:
> https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00478.html
That patch doesn't even mention the compute_objsize changes that matter most
for this in the ChangeLog entry.
The sign_mask > 0 case which is never possible is still in there etc.
>From gcc-bugs-return-662797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 17:59:38 2019
Return-Path: <gcc-bugs-return-662797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67167 invoked by alias); 9 Dec 2019 17:59: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 67089 invoked by uid 48); 9 Dec 2019 17:59:34 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92866] [10 Regression] libgo build failure on arm-linux-gnueabihf (ICE, segfault)
Date: Mon, 09 Dec 2019 17:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92866-4-zZOf8ncciG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92866-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92866-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00867.txt.bz2
Content-length: 187
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92866
--- Comment #1 from Ian Lance Taylor <ian at airs dot com> ---
This doesn't look like a Go problem, it looks like a backend problem.
>From gcc-bugs-return-662798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 18:01:08 2019
Return-Path: <gcc-bugs-return-662798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70371 invoked by alias); 9 Dec 2019 18:01: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 70273 invoked by uid 48); 9 Dec 2019 18:01:04 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92861] Passes relative time to sem_timedwait on GNU/Hurd
Date: Mon, 09 Dec 2019 18:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92861-4-cF1OUaUBBS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00868.txt.bz2
Content-length: 215
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92861
--- Comment #5 from Ian Lance Taylor <ian at airs dot com> ---
You can also just send patches to gcc-patches@gcc.gnu.org and/or
gofrontend-dev@googlegroups.com.
>From gcc-bugs-return-662799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 18:04:37 2019
Return-Path: <gcc-bugs-return-662799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88872 invoked by alias); 9 Dec 2019 18:04:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88774 invoked by uid 55); 9 Dec 2019 18:04:33 -0000
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92861] Passes relative time to sem_timedwait on GNU/Hurd
Date: Mon, 09 Dec 2019 18:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92861-4-oF7fUZAr62@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00869.txt.bz2
Content-length: 569
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92861
--- Comment #6 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Mon Dec 9 18:03:53 2019
New Revision: 279136
URL: https://gcc.gnu.org/viewcvs?rev=279136&root=gcc&view=rev
Log:
PR go/92861
runtime: don't define CLOCK_REALTIME in os_hurd.go
It's already defined in sysinfo.go.
Patch by Samuel Thibault.
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/210538
Modified:
trunk/gcc/go/gofrontend/MERGE
trunk/libgo/go/runtime/os_hurd.go
>From gcc-bugs-return-662800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 18:11:37 2019
Return-Path: <gcc-bugs-return-662800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106781 invoked by alias); 9 Dec 2019 18:11: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 106670 invoked by uid 48); 9 Dec 2019 18:11:33 -0000
From: "igor.chorazewicz at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92869] New: g++ wrongly reports aggregate type as not-aggregate (when explicitly defaulted ctors are added)
Date: Mon, 09 Dec 2019 18: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: igor.chorazewicz at intel dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00870.txt.bz2
Content-length: 1033
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92869
Bug ID: 92869
Summary: g++ wrongly reports aggregate type as not-aggregate
(when explicitly defaulted ctors are added)
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: igor.chorazewicz at intel dot com
Target Milestone: ---
The following code, when compiled with -std=c++17 results in "0" being printed.
The correct behavior is to print "1". Removing ctors fixes the issue, however,
accordingly to the standard, explicitly defaulted ctors are allowed for an
aggregate.
#include <array>
#include <type_traits>
#include <iostream>
template <typename T, std::size_t N>
struct A {
A() = default;
A(const A &) = default;
A(A &&) = default;
T arr[N];
};
int main()
{
std::cout << std::is_aggregate<A<int,3>>::value;
}
>From gcc-bugs-return-662801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 18:11:39 2019
Return-Path: <gcc-bugs-return-662801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107087 invoked by alias); 9 Dec 2019 18:11: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 106708 invoked by uid 48); 9 Dec 2019 18:11:35 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/92861] Passes relative time to sem_timedwait on GNU/Hurd
Date: Mon, 09 Dec 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: go
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92861-4-LkJGa4bx1U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00871.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92861
Ian Lance Taylor <ian at airs dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Ian Lance Taylor <ian at airs dot com> ---
Patch committed.
>From gcc-bugs-return-662802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 18:22:14 2019
Return-Path: <gcc-bugs-return-662802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2192 invoked by alias); 9 Dec 2019 18:22: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 2133 invoked by uid 48); 9 Dec 2019 18:22:09 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92869] g++ wrongly reports aggregate type as not-aggregate (when explicitly defaulted ctors are added)
Date: Mon, 09 Dec 2019 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: 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
Message-ID: <bug-92869-4-D0P2F4MNQ2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00872.txt.bz2
Content-length: 487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92869
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Most likely does not implement the difference between C++11/14 and C++17 with
respect to default member initializers.
>From gcc-bugs-return-662803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 18:26:01 2019
Return-Path: <gcc-bugs-return-662803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84047 invoked by alias); 9 Dec 2019 18:26: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 83987 invoked by uid 48); 9 Dec 2019 18:25:57 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92870] New: new test case gcc.dg/vect/vect-shift-5.c fails starting with its introduction in r279114
Date: Mon, 09 Dec 2019 18:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00873.txt.bz2
Content-length: 3024
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92870
Bug ID: 92870
Summary: new test case gcc.dg/vect/vect-shift-5.c fails
starting with its introduction in r279114
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
xecuting on host: /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/vect/vect-shift-5.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -maltivec -mpower8-vector
-ftree-vectorize -fno-tree-loop-distribute-patterns -fno-vect-cost-model
-fno-common -O2 -fdump-tree-vect-details -S -o vect-shift-5.s (timeout =
300)
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/vect/vect-shift-5.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -maltivec -mpower8-vector
-ftree-vectorize -fno-tree-loop-distribute-patterns -fno-vect-cost-model
-fno-common -O2 -fdump-tree-vect-details -S -o vect-shift-5.s
PASS: gcc.dg/vect/vect-shift-5.c (test for excess errors)
FAIL: gcc.dg/vect/vect-shift-5.c scan-tree-dump vect "vectorizable_shift
===[\\n\\r][^\\n]*prologue_cost = 0"
Executing on host: /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/vect/vect-shift-5.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -flto -ffat-lto-objects
-maltivec -mpower8-vector -ftree-vectorize -fno-tree-loop-distribute-patterns
-fno-vect-cost-model -fno-common -O2 -fdump-tree-vect-details -S -o
vect-shift-5.s (timeout = 300)
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/vect/vect-shift-5.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -flto -ffat-lto-objects
-maltivec -mpower8-vector -ftree-vectorize -fno-tree-loop-distribute-patterns
-fno-vect-cost-model -fno-common -O2 -fdump-tree-vect-details -S -o
vect-shift-5.s
PASS: gcc.dg/vect/vect-shift-5.c -flto -ffat-lto-objects (test for excess
errors)
FAIL: gcc.dg/vect/vect-shift-5.c -flto -ffat-lto-objects scan-tree-dump vect
"vectorizable_shift ===[\\n\\r][^\\n]*prologue_cost = 0"
testcase /home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vect/vect.exp
completed in 1 seconds
=== gcc Summary ===
# of expected passes 2
# of unexpected failures 2
>From gcc-bugs-return-662804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 18:30:48 2019
Return-Path: <gcc-bugs-return-662804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4945 invoked by alias); 9 Dec 2019 18:30: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 4869 invoked by uid 48); 9 Dec 2019 18:30:43 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92871] New: new test case g++.dg/ext/temp-extend1.C fails starting with its introduction in r279069
Date: Mon, 09 Dec 2019 18:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00874.txt.bz2
Content-length: 12258
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92871
Bug ID: 92871
Summary: new test case g++.dg/ext/temp-extend1.C fails starting
with its introduction in r279069
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
Executing on host: /home/seurer/gcc/build/gcc-test/gcc/testsuite/g++/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/ext/temp-extend1.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++14
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/.libs
-lm -o ./temp-extend1.exe (timeout = 300)
spawn -ignore SIGHUP
/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/ext/temp-extend1.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++14
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/.libs
-lm -o ./temp-extend1.exe
PASS: g++.dg/ext/temp-extend1.C -std=gnu++14 (test for excess errors)
Setting LD_LIBRARY_PATH to
.:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/.libs:/home/seurer/gcc/build/gcc-test/gcc:.:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/.libs:/home/seurer/gcc/build/gcc-test/gcc:/home/seurer/gcc/build/gcc-test/./gmp/.libs:/home/seurer/gcc/build/gcc-test/./prev-gmp/.libs:/home/seurer/gcc/build/gcc-test/./mpfr/src/.libs:/home/seurer/gcc/build/gcc-test/./prev-mpfr/src/.libs:/home/seurer/gcc/build/gcc-test/./mpc/src/.libs:/home/seurer/gcc/build/gcc-test/./prev-mpc/src/.libs:/home/seurer/gcc/build/gcc-test/./isl/.libs:/home/seurer/gcc/build/gcc-test/./prev-isl/.libs:/home/seurer/gcc/install/gcc-7.4.0/lib64
Execution timeout is: 300
spawn [open ...]
FAIL: g++.dg/ext/temp-extend1.C -std=gnu++14 execution test
Executing on host: /home/seurer/gcc/build/gcc-test/gcc/testsuite/g++/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/ext/temp-extend1.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++17
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/.libs
-lm -o ./temp-extend1.exe (timeout = 300)
spawn -ignore SIGHUP
/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/ext/temp-extend1.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++17
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/.libs
-lm -o ./temp-extend1.exe
PASS: g++.dg/ext/temp-extend1.C -std=gnu++17 (test for excess errors)
Setting LD_LIBRARY_PATH to
.:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/.libs:/home/seurer/gcc/build/gcc-test/gcc:.:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/.libs:/home/seurer/gcc/build/gcc-test/gcc:/home/seurer/gcc/build/gcc-test/./gmp/.libs:/home/seurer/gcc/build/gcc-test/./prev-gmp/.libs:/home/seurer/gcc/build/gcc-test/./mpfr/src/.libs:/home/seurer/gcc/build/gcc-test/./prev-mpfr/src/.libs:/home/seurer/gcc/build/gcc-test/./mpc/src/.libs:/home/seurer/gcc/build/gcc-test/./prev-mpc/src/.libs:/home/seurer/gcc/build/gcc-test/./isl/.libs:/home/seurer/gcc/build/gcc-test/./prev-isl/.libs:/home/seurer/gcc/install/gcc-7.4.0/lib64
Execution timeout is: 300
spawn [open ...]
FAIL: g++.dg/ext/temp-extend1.C -std=gnu++17 execution test
Executing on host: /home/seurer/gcc/build/gcc-test/gcc/testsuite/g++/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/ext/temp-extend1.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++2a
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/.libs
-lm -o ./temp-extend1.exe (timeout = 300)
spawn -ignore SIGHUP
/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++/../../xg++
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/g++/../../
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/ext/temp-extend1.C
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -nostdinc++
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/libstdc++-v3/include
-I/home/seurer/gcc/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++2a
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/.libs
-lm -o ./temp-extend1.exe
PASS: g++.dg/ext/temp-extend1.C -std=gnu++2a (test for excess errors)
Setting LD_LIBRARY_PATH to
.:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/.libs:/home/seurer/gcc/build/gcc-test/gcc:.:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libitm/.libs:/home/seurer/gcc/build/gcc-test/gcc:/home/seurer/gcc/build/gcc-test/./gmp/.libs:/home/seurer/gcc/build/gcc-test/./prev-gmp/.libs:/home/seurer/gcc/build/gcc-test/./mpfr/src/.libs:/home/seurer/gcc/build/gcc-test/./prev-mpfr/src/.libs:/home/seurer/gcc/build/gcc-test/./mpc/src/.libs:/home/seurer/gcc/build/gcc-test/./prev-mpc/src/.libs:/home/seurer/gcc/build/gcc-test/./isl/.libs:/home/seurer/gcc/build/gcc-test/./prev-isl/.libs:/home/seurer/gcc/install/gcc-7.4.0/lib64
Execution timeout is: 300
spawn [open ...]
FAIL: g++.dg/ext/temp-extend1.C -std=gnu++2a execution test
testcase /home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/dg.exp completed in 0
seconds
=== g++ Summary ===
# of expected passes 3
# of unexpected failures 3
# of unsupported tests 1
Running it in gdb I see:
(gdb) where
#0 0x00003fffb79e247c in .raise () from /lib64/libc.so.6
#1 0x00003fffb79e4688 in .abort () from /lib64/libc.so.6
#2 0x00000000100009c8 in baz (i=1) at
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/ext/temp-extend1.C:25
#3 0x0000000010000ae4 in main () at
/home/seurer/gcc/gcc-test/gcc/testsuite/g++.dg/ext/temp-extend1.C:40
int
main ()
{
foo (0);
if (S::c != 0)
__builtin_abort ();
foo (1);
if (S::c != 0)
__builtin_abort ();
baz (0);
if (S::c != 0)
__builtin_abort ();
baz (1);
if (S::c != 0) // line 40
__builtin_abort ();
}
>From gcc-bugs-return-662805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 18:47:30 2019
Return-Path: <gcc-bugs-return-662805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88885 invoked by alias); 9 Dec 2019 18:47: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 86266 invoked by uid 48); 9 Dec 2019 18:47:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92841] Optimize -fstack-protector-strong code generation a bit
Date: Mon, 09 Dec 2019 18:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-92841-4-zKDRpJfZBe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00875.txt.bz2
Content-length: 579
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841
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 47452
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47452&action=edit
gcc10-pr92841.patch
Untested fix.
>From gcc-bugs-return-662806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 19:11:15 2019
Return-Path: <gcc-bugs-return-662806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72720 invoked by alias); 9 Dec 2019 19:11: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 72679 invoked by uid 48); 9 Dec 2019 19:11:11 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92854] [OpenACC] Always-true conditional in 'libgomp/oacc-mem.c:acc_unmap_data'?
Date: Mon, 09 Dec 2019 19:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92854-4-j0q75JnvuF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00876.txt.bz2
Content-length: 967
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92854
--- Comment #6 from jules at gcc dot gnu.org ---
Created attachment 47453
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47453&action=edit
Patch for acc_map_data-device_already-3.c problem
This patch fixes the acc_map_data-device_already-3.c problem, which I guess has
probably been broken forever. The single tgt_mem_desc used for all the function
and global variable mappings (created in gomp_load_image_to_device) does not
have its tgt_start and tgt_end fields set properly, so oacc-mem.c:lookup_dev
cannot find any global variable.
We can fix this by calculating the total address range covered by (the union
of) all offloaded functions and global variables, and set tgt_start and tgt_end
appropriately. We then go through each splay tree key's tgt_offset, and adjust
it to be an offset within that range.
I've yet to run full tests with this, but it works for the test case mentioned.
>From gcc-bugs-return-662807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 19:39:40 2019
Return-Path: <gcc-bugs-return-662807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78384 invoked by alias); 9 Dec 2019 19:39: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 70908 invoked by uid 48); 9 Dec 2019 19:39:34 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88624] [Coarray] Rejects allocatable coarray passed as a dummy argument
Date: Mon, 09 Dec 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: fortran
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88624-4-RDps6JFVZg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88624-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88624-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00877.txt.bz2
Content-length: 1320
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88624
G. Steinmetz <gscfq@t-online.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gscfq@t-online.de
--- Comment #2 from G. Steinmetz <gscfq@t-online.de> ---
Update :
$ cat z1.f90
subroutine g(x)
real, allocatable :: x(:)[:]
call h(x)
contains
subroutine h(z)
real :: z(:)[*]
end
end
$ gfortran-10-20191208 -c z1.f90 -fcoarray=lib
z1.f90:3:0:
3 | call h(x)
|
internal compiler error: in gfc_conv_procedure_call, at
fortran/trans-expr.c:6579
0x710ece gfc_conv_procedure_call(gfc_se*, gfc_symbol*, gfc_actual_arglist*,
gfc_expr*, vec<tree_node*, va_gc, vl_embed>*)
../../gcc/fortran/trans-expr.c:6578
0x745888 gfc_trans_call(gfc_code*, bool, tree_node*, tree_node*, bool)
../../gcc/fortran/trans-stmt.c:406
0x6d6981 trans_code
../../gcc/fortran/trans.c:1932
0x6ffb24 gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6801
0x688be6 translate_all_program_units
../../gcc/fortran/parse.c:6302
0x688be6 gfc_parse_file()
../../gcc/fortran/parse.c:6541
0x6d306f gfc_be_parse_file
../../gcc/fortran/f95-lang.c:210
>From gcc-bugs-return-662808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 19:42:25 2019
Return-Path: <gcc-bugs-return-662808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113519 invoked by alias); 9 Dec 2019 19: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 110994 invoked by uid 48); 9 Dec 2019 19:42:21 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92872] New: [10 Regression] ICE in build_fold_indirect_ref_loc, at fold-const.c:14842
Date: Mon, 09 Dec 2019 19:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92872-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00878.txt.bz2
Content-length: 2018
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92872
Bug ID: 92872
Summary: [10 Regression] ICE in build_fold_indirect_ref_loc, at
fold-const.c:14842
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Changed between 20190929 and 20191006 :
(with a legal z0 for reference)
$ cat z0.f90
subroutine s(x)
integer, allocatable, optional :: x(:)
x = [1, 2, 3]
end
$ gfortran-10-20191208 -c z0.f90
$ cat z1.f90
subroutine s(x) bind(c)
integer, allocatable, optional :: x(:)
x = [1, 2, 3]
end
$ gfortran-10-20190929 -c z1.f90
$
$ gfortran-10-20191208 -c z1.f90
z1.f90:3:0:
3 | x = [1, 2, 3]
|
internal compiler error: Segmentation fault
0xd05dff crash_signal
../../gcc/toplev.c:328
0x9821e4 contains_struct_check(tree_node*, tree_node_structure_enum, char
const*, int, char const*)
../../gcc/tree.h:3386
0x9821e4 build_fold_indirect_ref_loc(unsigned int, tree_node*)
../../gcc/fold-const.c:14842
0x715eef gfc_conv_scalarized_array_ref
../../gcc/fortran/trans-array.c:3511
0x716c54 gfc_conv_array_ref(gfc_se*, gfc_array_ref*, gfc_expr*, locus*)
../../gcc/fortran/trans-array.c:3641
0x75679e gfc_conv_variable
../../gcc/fortran/trans-expr.c:2808
0x7514ba gfc_conv_expr(gfc_se*, gfc_expr*)
../../gcc/fortran/trans-expr.c:8665
0x75d677 gfc_trans_assignment_1
../../gcc/fortran/trans-expr.c:10884
0x709ee7 trans_code
../../gcc/fortran/trans.c:1864
0x74107d gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6801
0x6bafe6 translate_all_program_units
../../gcc/fortran/parse.c:6302
0x6bafe6 gfc_parse_file()
../../gcc/fortran/parse.c:6541
0x705fcf gfc_be_parse_file
../../gcc/fortran/f95-lang.c:210
>From gcc-bugs-return-662809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 19:46:22 2019
Return-Path: <gcc-bugs-return-662809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105578 invoked by alias); 9 Dec 2019 19:46: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 105485 invoked by uid 48); 9 Dec 2019 19:46:18 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92873] New: ICE in unmodified_parm_or_parm_agg_item, at ipa-fnsummary.c:1166
Date: Mon, 09 Dec 2019 19:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92873-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00879.txt.bz2
Content-length: 2552
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92873
Bug ID: 92873
Summary: ICE in unmodified_parm_or_parm_agg_item, at
ipa-fnsummary.c:1166
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Affects versions down to at least gcc-5 :
$ cat z1.f90
module m
contains
elemental function f(a,b) result(c)
character(*), intent(in) :: a, b
character(len(a)**len(b)) :: c
c = a // b
end
subroutine s
call sub (f(['abc'], ['xyz']))
end
end
$ gfortran-10-20191208 -c z1.f90 -O2
during IPA pass: fnsummary
z1.f90:7:0:
7 | end
|
internal compiler error: Segmentation fault
0xb800af crash_signal
../../gcc/toplev.c:328
0x99add0 gimple_assign_single_p
../../gcc/gimple.h:2784
0x99add0 unmodified_parm_or_parm_agg_item
../../gcc/ipa-fnsummary.c:1166
0x99add0 decompose_param_expr
../../gcc/ipa-fnsummary.c:1340
0x9a0bcd set_cond_stmt_execution_predicate
../../gcc/ipa-fnsummary.c:1463
0x9a0bcd compute_bb_predicates
../../gcc/ipa-fnsummary.c:1745
0x9a0bcd analyze_function_body
../../gcc/ipa-fnsummary.c:2481
0x9a1b64 compute_fn_summary(cgraph_node*, bool)
../../gcc/ipa-fnsummary.c:2932
0x9a212b inline_analyze_function(cgraph_node*)
../../gcc/ipa-fnsummary.c:4042
0x9a22b9 ipa_fn_summary_generate
../../gcc/ipa-fnsummary.c:4085
0xabd39c execute_ipa_summary_passes(ipa_opt_pass_d*)
../../gcc/passes.c:2189
0x7d55f9 ipa_passes
../../gcc/cgraphunit.c:2631
0x7d55f9 symbol_table::compile()
../../gcc/cgraphunit.c:2741
0x7d73a6 symbol_table::compile()
../../gcc/cgraphunit.c:2991
0x7d73a6 symbol_table::finalize_compilation_unit()
../../gcc/cgraphunit.c:2988
$ gfortran-10-20191208 -c z1.f90 # with --enable-checking=yes
during GIMPLE pass: fixup_cfg
z1.f90:3:0:
3 | elemental function f(a,b) result(c)
|
internal compiler error: Segmentation fault
0xd05dff crash_signal
../../gcc/toplev.c:328
0xf5ce22 get_use_from_ptr
../../gcc/tree-ssa-operands.h:112
0xf5ce22 verify_use
../../gcc/tree-ssa.c:926
0xf614e2 verify_ssa(bool, bool)
../../gcc/tree-ssa.c:1161
0xc1d957 execute_function_todo
../../gcc/passes.c:1990
0xc1e6c2 execute_todo
../../gcc/passes.c:2037
>From gcc-bugs-return-662810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 19:50:27 2019
Return-Path: <gcc-bugs-return-662810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69053 invoked by alias); 9 Dec 2019 19:50: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 68983 invoked by uid 48); 9 Dec 2019 19:50:22 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92874] New: ICE in gfc_dep_compare_expr, at fortran/dependency.c:36
Date: Mon, 09 Dec 2019 19:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92874-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00880.txt.bz2
Content-length: 2663
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92874
Bug ID: 92874
Summary: ICE in gfc_dep_compare_expr, at
fortran/dependency.c:36
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Affects versions down to at least gfortran-4.9,
compiles and works with -fno-frontend-optimize :
$ cat z1.f90
program p
call s('a')
call s('abc')
end
subroutine s(x)
character(*) :: x
print *, (x(1:1) == x(1:))
end
$ gfortran-10-20191208 z1.f90 -O2 -fno-frontend-optimize && ./a.out
T
F
$ gfortran-10-20191208 -c z1.f90 -O2
f951: internal compiler error: Segmentation fault
0xb800af crash_signal
../../gcc/toplev.c:328
0x6c9b14 gfc_dep_compare_expr(gfc_expr*, gfc_expr*)
../../gcc/fortran/dependency.c:368
0x6ca0ea are_identical_variables
../../gcc/fortran/dependency.c:187
0x6ca0ea gfc_dep_compare_expr(gfc_expr*, gfc_expr*)
../../gcc/fortran/dependency.c:486
0x758249 optimize_comparison
../../gcc/fortran/frontend-passes.c:2077
0x759a2f optimize_op
../../gcc/fortran/frontend-passes.c:1914
0x759a2f optimize_expr
../../gcc/fortran/frontend-passes.c:352
0x75a205 gfc_expr_walker(gfc_expr**, int (*)(gfc_expr**, int*, void*), void*)
../../gcc/fortran/frontend-passes.c:4929
0x75a3e9 gfc_expr_walker(gfc_expr**, int (*)(gfc_expr**, int*, void*), void*)
../../gcc/fortran/frontend-passes.c:4936
0x75cab1 gfc_code_walker(gfc_code**, int (*)(gfc_code**, int*, void*), int
(*)(gfc_expr**, int*, void*), void*)
../../gcc/fortran/frontend-passes.c:5347
0x75cb47 gfc_code_walker(gfc_code**, int (*)(gfc_code**, int*, void*), int
(*)(gfc_expr**, int*, void*), void*)
../../gcc/fortran/frontend-passes.c:5355
0x75dd12 optimize_namespace
../../gcc/fortran/frontend-passes.c:1474
0x75e15f gfc_run_passes(gfc_namespace*)
../../gcc/fortran/frontend-passes.c:165
0x69a1c7 gfc_resolve(gfc_namespace*)
../../gcc/fortran/resolve.c:17227
0x69a591 gfc_resolve(gfc_namespace*)
../../gcc/fortran/resolve.c:2546
0x69a591 resolve_global_procedure
../../gcc/fortran/resolve.c:2548
0x6a3378 resolve_call
../../gcc/fortran/resolve.c:3676
0x697d7d gfc_resolve_code(gfc_code*, gfc_namespace*)
../../gcc/fortran/resolve.c:11878
0x69a0d7 resolve_codes
../../gcc/fortran/resolve.c:17186
0x69a19e gfc_resolve(gfc_namespace*)
../../gcc/fortran/resolve.c:17221
>From gcc-bugs-return-662811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 19:51:46 2019
Return-Path: <gcc-bugs-return-662811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70404 invoked by alias); 9 Dec 2019 19:51:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70377 invoked by uid 48); 9 Dec 2019 19:51:42 -0000
From: "anders at wahrzeichnen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92875] New: GCC ignores the floating-point 'f' suffix in C11 mode
Date: Mon, 09 Dec 2019 19: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders at wahrzeichnen 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-92875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00881.txt.bz2
Content-length: 1830
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92875
Bug ID: 92875
Summary: GCC ignores the floating-point 'f' suffix in C11 mode
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders at wahrzeichnen dot de
Target Milestone: ---
Created attachment 47454
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47454&action=edit
test case with return value 0 or 8 expected, returns 12
GCC treats floating-point constants suffixed with 'f' as double, when compiled
with either -std=c11 or -std=c18. The attached test case illustrates this
problem: There are four functions f0, f1, f2, and f3. The first three functions
f0, f1, and f2 should all compile to the same code, f4 is different and there
for reference.
It turns out that with -std=387 and -m32 (or with -mfpmath=387), GCC compiles
f0 and f1 to equivalent asm but not f2. Instead, it creates the same asm for f2
as for f3, involving some loading a constant into an FPU register using double
precision. Apparently, writing '0.1f' is not enough to convince GCC that the
constant is single precision.
This can be seen with the attached program:
$ gcc -O -m32 testcase.c && ./a.out; echo $?
8
$ gcc -std=c11 -O -m32 testcase.c && ./a.out; echo $?
12
The result should be either 0, 8, or 15, depending on how exactly the decimal
constant 0.1 is rounded to binary floating-point, but it should never be
anything else.
The bug seems to be independent of optimization; it happens with -O0, -O1, -O2,
-O3, -Os, and -Og. I can trace it from GCC 9.2 all the way back to 4.8.4. It
can be triggered on 387 (with -m32 or -mfpmath=387).
>From gcc-bugs-return-662812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 19:57:07 2019
Return-Path: <gcc-bugs-return-662812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77418 invoked by alias); 9 Dec 2019 19:57:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77357 invoked by uid 48); 9 Dec 2019 19:57:03 -0000
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92876] New: ICE in expand_UNIQUE, at internal-fn.c:2599
Date: Mon, 09 Dec 2019 19:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gscfq@t-online.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92876-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00882.txt.bz2
Content-length: 1260
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92876
Bug ID: 92876
Summary: ICE in expand_UNIQUE, at internal-fn.c:2599
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Affects versions down to gfortran-6 at -O1+ :
(presumably related to pr89499)
$ cat z1.f90
program p
call s
contains
subroutine s
!$acc routine vector
!$acc loop vector
do i = 1, 8
end do
end
end
$ gfortran-10-20191208 -c z1.f90 -fopenacc -Og
$
$ gfortran-10-20191208 -c z1.f90 -fopenacc -O2
during RTL pass: expand
z1.f90:6:0:
6 | !$acc loop vector
|
internal compiler error: in expand_UNIQUE, at internal-fn.c:2599
0x97011f expand_UNIQUE
../../gcc/internal-fn.c:2599
0x79c6e7 expand_call_stmt
../../gcc/cfgexpand.c:2639
0x79c6e7 expand_gimple_stmt_1
../../gcc/cfgexpand.c:3709
0x79c6e7 expand_gimple_stmt
../../gcc/cfgexpand.c:3874
0x7a1827 expand_gimple_basic_block
../../gcc/cfgexpand.c:5914
0x7a3e76 execute
../../gcc/cfgexpand.c:6569
>From gcc-bugs-return-662813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 19:57:37 2019
Return-Path: <gcc-bugs-return-662813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78759 invoked by alias); 9 Dec 2019 19:57:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 78410 invoked by uid 48); 9 Dec 2019 19:57:32 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92875] GCC ignores the floating-point 'f' suffix in C11 mode
Date: Mon, 09 Dec 2019 19:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
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: cf_gcctarget dependson
Message-ID: <bug-92875-4-1CwaIS9Ibl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00883.txt.bz2
Content-length: 596
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92875
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |i?86-linux-gnu
Depends on| |323
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Does -ffloat-store help?
See 323 also.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=323
[Bug 323] optimized code gives strange floating point results
>From gcc-bugs-return-662814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 20:01:31 2019
Return-Path: <gcc-bugs-return-662814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84260 invoked by alias); 9 Dec 2019 20:01: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 84167 invoked by uid 48); 9 Dec 2019 20:01:27 -0000
From: "joshua.a.saxby at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92857] -Wsign-conversion flag issues false positives for expression using typedef'ed unsigned types
Date: Mon, 09 Dec 2019 20:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joshua.a.saxby 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: bug_status resolution
Message-ID: <bug-92857-4-pouJIJR64y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92857-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00884.txt.bz2
Content-length: 545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92857
Joshua Saxby <joshua.a.saxby at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #5 from Joshua Saxby <joshua.a.saxby at gmail dot com> ---
Ah, I have some reading to do, then. Thank you for pointing that out and
apologies for wasting your time everyone.
>From gcc-bugs-return-662815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 20:04:27 2019
Return-Path: <gcc-bugs-return-662815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112012 invoked by alias); 9 Dec 2019 20: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 111924 invoked by uid 55); 9 Dec 2019 20:04:22 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/49973] Column numbers count multibyte characters as multiple columns
Date: Mon, 09 Dec 2019 20:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 4.5.2
X-Bugzilla-Keywords: easyhack, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm 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-49973-4-oPgbMaA4QS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49973-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49973-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00885.txt.bz2
Content-length: 7437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49973
--- Comment #19 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Author: dmalcolm
Date: Mon Dec 9 20:03:47 2019
New Revision: 279137
URL: https://gcc.gnu.org/viewcvs?rev=279137&root=gcc&view=rev
Log:
Byte vs column awareness for diagnostic-show-locus.c (PR 49973)
contrib/ChangeLog
2019-12-09 Lewis Hyatt <lhyatt@gmail.com>
PR preprocessor/49973
* unicode/from_glibc/unicode_utils.py: Support script from
glibc (commit 464cd3) to extract character widths from Unicode data
files.
* unicode/from_glibc/utf8_gen.py: Likewise.
* unicode/UnicodeData.txt: Unicode v. 12.1.0 data file.
* unicode/EastAsianWidth.txt: Likewise.
* unicode/PropList.txt: Likewise.
* unicode/gen_wcwidth.py: New utility to generate
libcpp/generated_cpp_wcwidth.h with help from the glibc support
scripts and the Unicode data files.
* unicode/unicode-license.txt: Added.
* unicode/README: New explanatory file.
libcpp/ChangeLog
2019-12-09 Lewis Hyatt <lhyatt@gmail.com>
PR preprocessor/49973
* generated_cpp_wcwidth.h: New file generated by
../contrib/unicode/gen_wcwidth.py, supports new cpp_wcwidth function.
* charset.c (compute_next_display_width): New function to help
implement display columns.
(cpp_byte_column_to_display_column): Likewise.
(cpp_display_column_to_byte_column): Likewise.
(cpp_wcwidth): Likewise.
* include/cpplib.h (cpp_byte_column_to_display_column): Declare.
(cpp_display_column_to_byte_column): Declare.
(cpp_wcwidth): Declare.
(cpp_display_width): New function.
gcc/ChangeLog
2019-12-09 Lewis Hyatt <lhyatt@gmail.com>
PR preprocessor/49973
* input.c (location_compute_display_column): New function to help with
multibyte awareness in diagnostics.
(test_cpp_utf8): New self-test.
(input_c_tests): Call the new test.
* input.h (location_compute_display_column): Declare.
* diagnostic-show-locus.c: Pervasive changes to add multibyte awareness
to all classes and functions.
(enum column_unit): New enum.
(class exploc_with_display_col): New class.
(class layout_point): Convert m_column member to array m_columns[2].
(layout_range::contains_point): Add col_unit argument.
(test_layout_range_for_single_point): Pass new argument.
(test_layout_range_for_single_line): Likewise.
(test_layout_range_for_multiple_lines): Likewise.
(line_bounds::convert_to_display_cols): New function.
(layout::get_state_at_point): Add col_unit argument.
(make_range): Use empty filename rather than dummy filename.
(get_line_width_without_trailing_whitespace): Rename to...
(get_line_bytes_without_trailing_whitespace): ...this.
(test_get_line_width_without_trailing_whitespace): Rename to...
(test_get_line_bytes_without_trailing_whitespace): ...this.
(class layout): m_exploc changed to exploc_with_display_col from
plain expanded_location.
(layout::get_linenum_width): New accessor member function.
(layout::get_x_offset_display): Likewise.
(layout::calculate_linenum_width): New subroutine for the constuctor.
(layout::calculate_x_offset_display): Likewise.
(layout::layout): Use the new subroutines. Add multibyte awareness.
(layout::print_source_line): Add multibyte awareness.
(layout::print_line): Likewise.
(layout::print_annotation_line): Likewise.
(line_label::line_label): Likewise.
(layout::print_any_labels): Likewise.
(layout::annotation_line_showed_range_p): Likewise.
(get_printed_columns): Likewise.
(class line_label): Rename m_length to m_display_width.
(get_affected_columns): Rename to...
(get_affected_range): ...this; add col_unit argument and multibyte
awareness.
(class correction): Add m_affected_bytes and m_display_cols
members. Rename m_len to m_byte_length for clarity. Add multibyte
awareness throughout.
(correction::insertion_p): Add multibyte awareness.
(correction::compute_display_cols): New function.
(correction::ensure_terminated): Use new member name m_byte_length.
(line_corrections::add_hint): Add multibyte awareness.
(layout::print_trailing_fixits): Likewise.
(layout::get_x_bound_for_row): Likewise.
(test_one_liner_simple_caret_utf8): New self-test analogous to the one
with _utf8 suffix removed, testing multibyte awareness.
(test_one_liner_caret_and_range_utf8): Likewise.
(test_one_liner_multiple_carets_and_ranges_utf8): Likewise.
(test_one_liner_fixit_insert_before_utf8): Likewise.
(test_one_liner_fixit_insert_after_utf8): Likewise.
(test_one_liner_fixit_remove_utf8): Likewise.
(test_one_liner_fixit_replace_utf8): Likewise.
(test_one_liner_fixit_replace_non_equal_range_utf8): Likewise.
(test_one_liner_fixit_replace_equal_secondary_range_utf8): Likewise.
(test_one_liner_fixit_validation_adhoc_locations_utf8): Likewise.
(test_one_liner_many_fixits_1_utf8): Likewise.
(test_one_liner_many_fixits_2_utf8): Likewise.
(test_one_liner_labels_utf8): Likewise.
(test_diagnostic_show_locus_one_liner_utf8): Likewise.
(test_overlapped_fixit_printing_utf8): Likewise.
(test_overlapped_fixit_printing): Adapt for changes to
get_affected_columns, get_printed_columns and class corrections.
(test_overlapped_fixit_printing_2): Likewise.
(test_linenum_sep): New constant.
(test_left_margin): Likewise.
(test_offset_impl): Helper function for new test.
(test_layout_x_offset_display_utf8): New test.
(diagnostic_show_locus_c_tests): Call new tests.
gcc/testsuite/ChangeLog:
2019-12-09 Lewis Hyatt <lhyatt@gmail.com>
PR preprocessor/49973
* gcc.dg/plugin/diagnostic_plugin_test_show_locus.c
(test_show_locus): Tweak so that expected output is the same as
before the diagnostic-show-locus.c changes.
* gcc.dg/cpp/pr66415-1.c: Likewise.
Added:
trunk/contrib/unicode/
trunk/contrib/unicode/EastAsianWidth.txt
trunk/contrib/unicode/PropList.txt
trunk/contrib/unicode/README
trunk/contrib/unicode/UnicodeData.txt
trunk/contrib/unicode/from_glibc/
trunk/contrib/unicode/from_glibc/unicode_utils.py
trunk/contrib/unicode/from_glibc/utf8_gen.py (with props)
trunk/contrib/unicode/gen_wcwidth.py (with props)
trunk/contrib/unicode/unicode-license.txt
trunk/libcpp/generated_cpp_wcwidth.h
Modified:
trunk/contrib/ChangeLog
trunk/gcc/ChangeLog
trunk/gcc/diagnostic-show-locus.c
trunk/gcc/input.c
trunk/gcc/input.h
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/cpp/pr66415-1.c
trunk/gcc/testsuite/gcc.dg/plugin/diagnostic_plugin_test_show_locus.c
trunk/libcpp/ChangeLog
trunk/libcpp/charset.c
trunk/libcpp/include/cpplib.h
Propchange: trunk/contrib/unicode/from_glibc/utf8_gen.py
('svn:executable' added)
Propchange: trunk/contrib/unicode/gen_wcwidth.py
('svn:executable' added)
>From gcc-bugs-return-662816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 20:27:44 2019
Return-Path: <gcc-bugs-return-662816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30674 invoked by alias); 9 Dec 2019 20:27: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 30606 invoked by uid 48); 9 Dec 2019 20:27:40 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/49973] Column numbers count multibyte characters as multiple columns
Date: Mon, 09 Dec 2019 20:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 4.5.2
X-Bugzilla-Keywords: easyhack, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm 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-49973-4-xZKLl8p4Ea@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49973-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49973-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00886.txt.bz2
Content-length: 3204
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49973
--- Comment #20 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
I've committed r279137 on Lewis's behalf, which fixes the issues identified in
patch #13.
As noted in review of the patch, we didn't attempt to change the behavior of
diagnostic_get_location_text with this change. Quoting myself from:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02171.html
> This is the column number as reported in the diagnostic i.e the COL_NUM
> when printing e.g.
> warning: FILENAME:LINE_NUM:COL_NUM: some message
>
> It seems to me that PR 49973 and this patch cover two separate things:
> (a) bytes vs display columns in diagnostic-show-locus.c
> (b) the "COL_NUM" mentioned above.
>
> I'd prefer to omit (b) from the patch, and have the focus of the patch
> be (a), to tackle (b) in a separate patch.
>
> [There's also the meaning of column numbers in the JSON output, and in
> the output of -fdiagnostics-parseable-fixits (which is intended to mimic
> clang's output format)]
>
> It's unclear to me what the reported COL_NUM should be.
> There are various possibilities:
>
> Units:
> (A) [status quo] report a count of bytes within the line
> (B) report a count of unicode characters
> (C) report a count of unicode graphemes
> (D) report based on the wcwidth of the characters
> etc
>
> Origin/baseline:
> (A) [status quo] use 1 for the leftmost column
> (B) use 0 for the leftmost column
>
> Tab-handling:
> (A) [status quo] don't give any kind of special status to tab characters
> (B) implement tab stops, somehow. For example, get_visual_column in
> c-family/c-indentation implements tab stops based on bytes.
>
> (so at least 4*2*2 = 16 possible meanings, ugh)
>
> See also e.g.:
> https://github.com/oasis-tcs/sarif-spec/issues/178
>
> The GNU Coding Standards say
>
> Line numbers should start from 1 at the beginning of the file, and
> column numbers should start from 1 at the beginning of the line.
> (Both of these conventions are chosen for compatibility.) Calculate
> column numbers assuming that space and all ASCII printing characters
> have equal width, and assuming tab stops every 8 columns. For
> non-ASCII characters, Unicode character widths should be used when in
> a UTF-8 locale; GNU libc and GNU gnulib provide suitable wcwidth
> functions.
> (https://www.gnu.org/prep/standards/standards.html#Errors)
>
> I think if we do change the meaning of the "COL_NUM" output, we should
> probably add an option for it, to help with the transition (so that
> people can easily revert to the old behavior).
>
> Perhaps something like:
>
> -fdiagnostics-column-unit=[bytes|gnu]
>
> bytes: [status-quo]; 1-based count of bytes, not respecting tab stops
> gnu: as per GNU Coding Standards above
>
> and have gcc 10 default to "gnu" (or whatever we call it), so that
> people can override it back to "bytes".
>
> (again, I'm thinking aloud here)
>
> But please can you split that out as a separate patch? (it's arguably
> still in time for GCC 10, as it's from a patch was posted before the
> stage 1 deadline).
>From gcc-bugs-return-662817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 20:32:37 2019
Return-Path: <gcc-bugs-return-662817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39451 invoked by alias); 9 Dec 2019 20:32: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 39373 invoked by uid 48); 9 Dec 2019 20:32:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92871] new test case g++.dg/ext/temp-extend1.C fails starting with its introduction in r279069
Date: Mon, 09 Dec 2019 20:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone everconfirmed
Message-ID: <bug-92871-4-3T8H0vgOG4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00887.txt.bz2
Content-length: 2259
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92871
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-09
CC| |jason at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Oops, I see what's going on.
The ?: with omitted middle operand is transformed earlier into
cp_stabilize_reference (arg1) ? cp_stabilize_reference (arg1) : ...
where the first two arguments are the same, then the middle argument is wrapped
into ADDR_EXPR (but I'd be afraid that generally it can be much harder to
figure out what is what) and only much later extend_ref_init_temps_1, which
only modifies the second argument (and third) and puts the subinit initializers
in there. While the tree of the TARGET_EXPR is obviously shared between the
first and second COND_EXPR arguments, as we put the initialization just into
the second, it means the VAR_DECL that replaced the TARGET_EXPR is used before
it is initialized.
Now, I'm afraid it will be nasty to fix it up.
Either we mark with some flag COND_EXPRs that had originally the middle operand
omitted, propagate it through all the COND_EXPR rationalization etc. and then
try to figure out how to get from the second operand something suitable for the
first operand if that is at all possible (e.g. in this testcase perhaps by
figuring out that originally the second argument is & of the first one and
after changing the second one, modify the first argument to be INDIRECT_REF of
the second one and thus get all the subinit initialization in there.
Or try to somehow discover if the first and second argument were originally the
same without a flag. Or make sure we keep the middle operand NULL much longer.
Any other ideas?
This problem isn't actually powerpc64 specific, on x86_64-linux, while we are
lucky that the test passes, valgrind shows that it uses uninitialized memory.
>From gcc-bugs-return-662818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 20:39:33 2019
Return-Path: <gcc-bugs-return-662818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49497 invoked by alias); 9 Dec 2019 20:39: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 49442 invoked by uid 48); 9 Dec 2019 20:39:29 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92877] New: [OpenACC] Failure to resolve back via 'acc_hostptr' an 'acc_deviceptr' retrieved for a structured mapping
Date: Mon, 09 Dec 2019 20:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00888.txt.bz2
Content-length: 812
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92877
Bug ID: 92877
Summary: [OpenACC] Failure to resolve back via 'acc_hostptr' an
'acc_deviceptr' retrieved for a structured mapping
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: openacc, patch
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: jakub at gcc dot gnu.org, jules at gcc dot gnu.org
Target Milestone: ---
This currently fails:
int var;
#pragma acc data create (var)
{
void *var_p_d = acc_deviceptr (&var);
assert (acc_hostptr (var_p_d) == &var);
}
Patch exists.
>From gcc-bugs-return-662819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 20:39:38 2019
Return-Path: <gcc-bugs-return-662819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50099 invoked by alias); 9 Dec 2019 20:39: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 49513 invoked by uid 48); 9 Dec 2019 20:39:33 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/49973] Column numbers count multibyte characters as multiple columns
Date: Mon, 09 Dec 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: preprocessor
X-Bugzilla-Version: 4.5.2
X-Bugzilla-Keywords: easyhack, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm 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-49973-4-OHr7eg0pQO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49973-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49973-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00889.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49973
--- Comment #21 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #20)
> I've committed r279137 on Lewis's behalf, which fixes the issues identified
> in patch #13.
comment #13, I meant to say
>From gcc-bugs-return-662820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 20:41:24 2019
Return-Path: <gcc-bugs-return-662820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52413 invoked by alias); 9 Dec 2019 20:41: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 52347 invoked by uid 48); 9 Dec 2019 20:41:20 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92503] [OpenACC] Behavior of 'acc_free' if the memory space is still used in a mapping
Date: Mon, 09 Dec 2019 20:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-92503-4-I9mJNvMuhD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92503-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92503-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00890.txt.bz2
Content-length: 1153
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92503
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-09
Assignee|unassigned at gcc dot gnu.org |tschwinge at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to myself from comment #2)
> There are nvptx offloading TODOs in
> 'libgomp.oacc-c-c++-common/acc_free-pr92503-4.c',
> 'libgomp.oacc-c-c++-common/acc_free-pr92503-4-2.c'. Can you easily (please
> don't spend much time on this) what's going wrong? Otherwise I shall commit
> that XFAILed.
This is a variant of PR92877. ;-O
> Please also verify whether there are any changes necessary for AMD GCN
> offloading, in particular un-XFAILing the two nvptx ones, I suppose?
..., so not related to nvptx offloading.
>From gcc-bugs-return-662821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 20:42:14 2019
Return-Path: <gcc-bugs-return-662821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53870 invoked by alias); 9 Dec 2019 20:42: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 53804 invoked by uid 48); 9 Dec 2019 20:42:10 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92877] [OpenACC] Failure to resolve back via 'acc_hostptr' an 'acc_deviceptr' retrieved for a structured mapping
Date: Mon, 09 Dec 2019 20:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-92877-4-5xxg0tQz0f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00891.txt.bz2
Content-length: 499
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92877
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-09
Assignee|unassigned at gcc dot gnu.org |tschwinge at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-662823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 20:54:49 2019
Return-Path: <gcc-bugs-return-662823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86853 invoked by alias); 9 Dec 2019 20:54: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 86746 invoked by uid 55); 9 Dec 2019 20:54:43 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92762] hash_table::empty_slow invokes assignment on invalid objects
Date: Mon, 09 Dec 2019 20:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92762-4-UO7Jiy9e7Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00893.txt.bz2
Content-length: 905
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92762
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Mon Dec 9 20:54:11 2019
New Revision: 279139
URL: https://gcc.gnu.org/viewcvs?rev=279139&root=gcc&view=rev
Log:
PR middle-end/92761 - hash_table::expand invokes assignment on invalid objects
PR middle-end/92762 - hash_table::empty_slow invokes assignment on invalid
objects
gcc/ChangeLog:
PR middle-end/92761
PR middle-end/92762
* hash-map-tests.c (test_map_of_type_with_ctor_and_dtor): Tighten
up tests.
* hash-table.h (hash_table::expand): Use placement new to copy
construct objects in uninitialized storage.
(hash_table::empty_slow): Avoid invoking copy assignment on
uninitialized objects.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/hash-map-tests.c
trunk/gcc/hash-table.h
>From gcc-bugs-return-662822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 20:54:49 2019
Return-Path: <gcc-bugs-return-662822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86850 invoked by alias); 9 Dec 2019 20:54: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 86744 invoked by uid 55); 9 Dec 2019 20:54:43 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92761] hash_table::expand invokes assignment on invalid objects
Date: Mon, 09 Dec 2019 20: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: build, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92761-4-VmwE3hUXQ9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00892.txt.bz2
Content-length: 906
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
--- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Mon Dec 9 20:54:11 2019
New Revision: 279139
URL: https://gcc.gnu.org/viewcvs?rev=279139&root=gcc&view=rev
Log:
PR middle-end/92761 - hash_table::expand invokes assignment on invalid objects
PR middle-end/92762 - hash_table::empty_slow invokes assignment on invalid
objects
gcc/ChangeLog:
PR middle-end/92761
PR middle-end/92762
* hash-map-tests.c (test_map_of_type_with_ctor_and_dtor): Tighten
up tests.
* hash-table.h (hash_table::expand): Use placement new to copy
construct objects in uninitialized storage.
(hash_table::empty_slow): Avoid invoking copy assignment on
uninitialized objects.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/hash-map-tests.c
trunk/gcc/hash-table.h
>From gcc-bugs-return-662824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 20:56:01 2019
Return-Path: <gcc-bugs-return-662824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90664 invoked by alias); 9 Dec 2019 20: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 90627 invoked by uid 48); 9 Dec 2019 20:55:57 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92761] hash_table::expand invokes assignment on invalid objects
Date: Mon, 09 Dec 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: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: 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
Message-ID: <bug-92761-4-Yf1IZJlF0t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00894.txt.bz2
Content-length: 499
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92761
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from Martin Sebor <msebor at gcc dot gnu.org> ---
Fixed in 279139. (Though there are outstanding problems with non-trivial
types.)
>From gcc-bugs-return-662825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 21:08:38 2019
Return-Path: <gcc-bugs-return-662825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122601 invoked by alias); 9 Dec 2019 21:08: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 122203 invoked by uid 48); 9 Dec 2019 21:08:34 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92796] [10 Regression] ICE in lra_assign, at lra-assigns.c:1646 on powerpc64le-linux-gnu
Date: Mon, 09 Dec 2019 21:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92796-4-TDIzGNAByX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00895.txt.bz2
Content-length: 955
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92796
--- Comment #7 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #6)
>
> Vlad (or Jeff), can you point me to where this is supposed to be handled?
> I don't think I see where LRA verifies the reg_renumber[regno] values are
> still
> valid with respect to the new pattern constraints for the insns that are
> modified by spilling.
>
> lra_reg_info[133].conflict_hard_regs does contain 66, so LRA knows it
> conflicts
> with reg 66, but it never seems to use that information as a sign that pseudo
> 133 needs reassigning.
A very interesting case, Peter. I reproduced the case too. I can take it from
here if you don't mind. The solution I see for this problem is to check that
if we change operand constraint from IN to INOUT when we change insn
alternative then we reconsider all conflicts for pseudos already assigned to
hard registers.
>From gcc-bugs-return-662826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 21:21:59 2019
Return-Path: <gcc-bugs-return-662826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58665 invoked by alias); 9 Dec 2019 21:21:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58593 invoked by uid 48); 9 Dec 2019 21:21:56 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92796] [10 Regression] ICE in lra_assign, at lra-assigns.c:1646 on powerpc64le-linux-gnu
Date: Mon, 09 Dec 2019 21:21: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: 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92796-4-JMxlPHW7Ux@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00896.txt.bz2
Content-length: 572
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92796
--- Comment #8 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #7)
> A very interesting case, Peter. I reproduced the case too. I can take it
> from here if you don't mind. The solution I see for this problem is to
> check that if we change operand constraint from IN to INOUT when we change
> insn alternative then we reconsider all conflicts for pseudos already
> assigned to hard registers.
Sorry, I meant insn code change not the insn alternative change.
>From gcc-bugs-return-662827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 21:31:35 2019
Return-Path: <gcc-bugs-return-662827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92129 invoked by alias); 9 Dec 2019 21: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 92046 invoked by uid 48); 9 Dec 2019 21:31:30 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92116] Potential null pointer dereference in 'gomp_acc_remove_pointer'
Date: Mon, 09 Dec 2019 21:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge 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 component assigned_to
Message-ID: <bug-92116-4-TacEfED65A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92116-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92116-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00897.txt.bz2
Content-length: 4293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92116
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|openacc |
Component|libgomp |tree-optimization
Assignee|jules at gcc dot gnu.org |msebor at gcc dot gnu.org
--- Comment #2 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Martin Sebor, regarding this:
(In reply to myself from comment #0)
> As reported in
> <http://mid.mail-archive.com/58cdb016-4c82-a271-cbc5-1ede344fdad3@gmail.com>:
>
> | PS I tried compiling GCC with [a new] patch. It fails in libgomp
> | with:
> |
> | libgomp/oacc-mem.c: In function ‘gomp_acc_remove_pointer’:
> | cc1: warning: invalid use of a null pointer [-Wnonnull]
> |
> | so clearly it's missing location information. With
> | -Wnull-dereference enabled we get more detail:
> |
> | libgomp/oacc-mem.c: In function ‘gomp_acc_remove_pointer’:
> | libgomp/oacc-mem.c:1013:31: warning: potential null pointer dereference [-Wnull-dereference]
> | 1013 | for (size_t i = 0; i < t->list_count; i++)
> | | ~^~~~~~~~~~~~
> | libgomp/oacc-mem.c:1012:19: warning: potential null pointer dereference [-Wnull-dereference]
> | 1012 | t->refcount = minrefs;
> | | ~~~~~~~~~~~~^~~~~~~~~
> | libgomp/oacc-mem.c:1013:31: warning: potential null pointer dereference [-Wnull-dereference]
> | 1013 | for (size_t i = 0; i < t->list_count; i++)
> | | ~^~~~~~~~~~~~
> | libgomp/oacc-mem.c:1012:19: warning: potential null pointer dereference [-Wnull-dereference]
> | 1012 | t->refcount = minrefs;
> | | ~~~~~~~~~~~~^~~~~~~~~
> | cc1: warning: invalid use of a null pointer [-Wnonnull]
> |
> | I didn't spend too long examining the code but it seems like
> | the warnings might actually be justified. When the first loop
> | terminates with t being null
It's actually not possible to terminate this loop with 't = NULL'. ;-)
As I understand this, what your compiler analysis pass has difficulties to
figure out (from the code as written in 'gomp_acc_remove_pointer'?) is that
here:
> | the subsequent dereferences are
> | invalid:
> |
> | if (t->refcount == minrefs)
> | {
> | /* This is the last reference, so pull the descriptor off the
> | chain. This prevents gomp_unmap_vars via gomp_unmap_tgt from
> | freeing the device memory. */
> | struct target_mem_desc *tp;
> | for (tp = NULL, t = acc_dev->openacc.data_environ; t != NULL;
> | tp = t, t = t->prev)
> | {
> | if (n->tgt == t)
> | {
> | if (tp)
> | tp->prev = t->prev;
> | else
> | acc_dev->openacc.data_environ = t->prev;
> | break;
> | }
> | }
> | }
... we are always going to eventually find 'n->tgt == t': we start this loop
with 't == n->tgt' (see further above), and what this code here is doing is
just to locate 'n->tgt' in 'data_environ', which is guaranteed to contain it
(yes, there should be some 'assert' or similar for that...), and then un-link
it from 'data_environ'. Then we 'break', and thus after the loop we again have
the original 't = n->tgt', and so here:
> | /* Set refcount to 1 to allow gomp_unmap_vars to unmap it. */
> | n->refcount = 1;
> | t->refcount = minrefs;
> | for (size_t i = 0; i < t->list_count; i++)
..., there will never be 't == NULL'.
Certainly this code is a bit "strange" -- but maybe that's something your
analysis has to consider for "real-world code"? I'm assigning this PR to you
in case you'd like to track this, otherwise please set RESOLVED, INVALID or
something like that.
..., and that said, we shall be removing this code from
'gomp_acc_remove_pointer' any moment now... ;-)
>From gcc-bugs-return-662828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:08:57 2019
Return-Path: <gcc-bugs-return-662828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5737 invoked by alias); 9 Dec 2019 22:08: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 5640 invoked by uid 55); 9 Dec 2019 22:08:51 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52451] gcc w/i387 float generates fucom rather than fcom for floating point comparsons
Date: Mon, 09 Dec 2019 22: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ubizjak at gmail dot com
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-52451-4-wcUEJdUfzF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52451-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52451-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00898.txt.bz2
Content-length: 796
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52451
--- Comment #13 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Fri, 6 Dec 2019, vgupta at synopsys dot com wrote:
> However I'm curious that the test uses qNaN. What is the expected behavior for
> sNaN. If you tweak the testcase slightly as follows:
All the comparison operations raise exceptions for sNaN. See IEEE 754.
"Invalid operation is the only exception that a comparison predicate can
signal. All predicates signal the invalid operation exception on signaling
NaN operands. The predicates named Quiet shall not signal any exception,
unless an operand is a signaling NaN. The predicates named Signaling shall
signal the invalid operation exception on quiet NaN operands.".
>From gcc-bugs-return-662829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:21:12 2019
Return-Path: <gcc-bugs-return-662829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85756 invoked by alias); 9 Dec 2019 22:21: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 79304 invoked by uid 48); 9 Dec 2019 22:21:08 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92796] [10 Regression] ICE in lra_assign, at lra-assigns.c:1646 on powerpc64le-linux-gnu
Date: Mon, 09 Dec 2019 22:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92796-4-O8twUBGJ7n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00899.txt.bz2
Content-length: 854
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92796
--- Comment #9 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #7)
> A very interesting case, Peter. I reproduced the case too. I can take it
> from here if you don't mind. The solution I see for this problem is to
> check that if we change operand constraint from IN to INOUT when we change
> insn alternative [code as you meantion later] then we reconsider all conflicts
> for pseudos already assigned to hard registers.
I'm more than fine if you want to handle this yourself, since you know this
code better than anyone.
I'm guessing this was never a problem before I added the code to not add
conflicts for copies. Before then, any two pseudos/registers that were live
simultaneously were made to conflict, which would have hid this bug.
>From gcc-bugs-return-662830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:24:40 2019
Return-Path: <gcc-bugs-return-662830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89453 invoked by alias); 9 Dec 2019 22:24: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 89340 invoked by uid 48); 9 Dec 2019 22:24:34 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92863] ICE in gfc_typename
Date: Mon, 09 Dec 2019 22:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92863-4-mkB3Lrg8Ob@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92863-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92863-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00900.txt.bz2
Content-length: 1133
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92863
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
This looks reasonable:
Index: misc.c
===================================================================
--- misc.c (Revision 279064)
+++ misc.c (Arbeitskopie)
@@ -164,9 +164,17 @@ gfc_typename (gfc_typespec *ts)
sprintf (buffer, "UNION(%s)", ts->u.derived->name);
break;
case BT_DERIVED:
- sprintf (buffer, "TYPE(%s)", ts->u.derived->name);
+ if (ts->u.derived)
+ sprintf (buffer, "TYPE(%s)", ts->u.derived->name);
+ else
+ sprintf (buffer, "invalid type");
break;
case BT_CLASS:
+ if (ts->u.derived == NULL)
+ {
+ sprintf (buffer, "invalid class");
+ break;
+ }
ts1 = ts->u.derived->components ? &ts->u.derived->components->ts : NULL;
if (ts1 && ts1->u.derived && ts1->u.derived->attr.unlimited_polymorphic)
sprintf (buffer, "CLASS(*)");
>From gcc-bugs-return-662832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:37:54 2019
Return-Path: <gcc-bugs-return-662832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108091 invoked by alias); 9 Dec 2019 22:37: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 108029 invoked by uid 48); 9 Dec 2019 22:37:50 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92796] [10 Regression] ICE in lra_assign, at lra-assigns.c:1646 on powerpc64le-linux-gnu
Date: Mon, 09 Dec 2019 22:37: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: 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92796-4-aQcxdvspmj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00902.txt.bz2
Content-length: 822
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92796
--- Comment #10 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #7)
>
>
> I'm guessing this was never a problem before I added the code to not add
> conflicts for copies. Before then, any two pseudos/registers that were live
> simultaneously were made to conflict, which would have hid this bug.
I believe this bug existed before. For example, the initial assignment (and
some LRA transformations) does not guarantee correctness of already made
assignments.
Therefore there is flag lra_risky_transformations_p (I am going to change this
name) to deal with such situations. Simply the current situation was not
considered before.
I have a patch and after some testing I'll commit it (probably tomorrow).
>From gcc-bugs-return-662831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:37:14 2019
Return-Path: <gcc-bugs-return-662831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106791 invoked by alias); 9 Dec 2019 22:37: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 106661 invoked by uid 48); 9 Dec 2019 22:37:08 -0000
From: "erick.ochoa@theobroma-systems.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92538] Proposal for IPA init() constant propagation
Date: Mon, 09 Dec 2019 22:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: erick.ochoa@theobroma-systems.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-92538-4-QqX4faX6qZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92538-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92538-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00901.txt.bz2
Content-length: 2083
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92538
Erick Ochoa <erick.ochoa@theobroma-systems.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #47278|0 |1
is obsolete| |
Attachment #47355|0 |1
is obsolete| |
--- Comment #5 from Erick Ochoa <erick.ochoa@theobroma-systems.com> ---
Created attachment 47455
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47455&action=edit
Patch version 3
Hello,
I am updating the patch version.
Currently, this patch can be applied against this commit on master branch.
commit 3cce71b23f6ed221b4335b600e718d79903cc83d
Date: Wed Dec 4 20:04:10 2019 +0000
git-svn-id:
svn+ssh://gcc.gnu.org/svn/gcc/trunk@278975 138bc75d-0d04-0410-961f-82ee72b054a4
This patch works on the previous patch by eliminating bugs.
Currently, all SPEC CPU 2017 benchmarks can be compiled with this patch and run
successfully.
Furthermore, it detects several constants that can be propagated in 12 of the
SPEC CPU benchmarks.
>From gcc-bugs-return-662833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:40:13 2019
Return-Path: <gcc-bugs-return-662833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110631 invoked by alias); 9 Dec 2019 22:40: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 110547 invoked by uid 48); 9 Dec 2019 22:40:08 -0000
From: "anders at wahrzeichnen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92875] GCC ignores the floating-point 'f' suffix in C11 mode
Date: Mon, 09 Dec 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: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders at wahrzeichnen dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92875-4-rvUBzLX1E9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00903.txt.bz2
Content-length: 784
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92875
--- Comment #2 from anders at wahrzeichnen dot de <anders at wahrzeichnen dot de> ---
No, -ffloat-store does not help. And this has little if anything to do with
323, imho.
The asm generated for f3 is instructive: There, GCC wants to load a double
constant 0x3fb999999999999a into the 387 FPU, which is
0.10000000000000000555... The single-precision constant t passed as argument to
f0...f3 is 0x3dcccccd, which is 0.10000000149... So, it's no wonder that f3
returns 1; after all 0.10000000149 > 0.10000000000000000555.
The questions are: Why does the code generated for f2 try to load a double
constant even if it is explicitly suffixed 'f'? Why should casting to (float)
help? Why does std=c11 or c18 change the game?
>From gcc-bugs-return-662834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:41:03 2019
Return-Path: <gcc-bugs-return-662834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111868 invoked by alias); 9 Dec 2019 22:41: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 111821 invoked by uid 55); 9 Dec 2019 22:40:59 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92875] GCC ignores the floating-point 'f' suffix in C11 mode
Date: Mon, 09 Dec 2019 22:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92875-4-reewr7ZDps@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00904.txt.bz2
Content-length: 513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92875
--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
The value of FLT_EVAL_METHOD applies to constants as well as to
operations. That is, when FLT_EVAL_METHOD == 2, 0.1f has the precision of
long double but the semantic type of float, and 0.1 has the precision of
long double but the semantic type of double. An explicit cast to float
removes excess precision. This is as specified in the C standard.
>From gcc-bugs-return-662835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:45:51 2019
Return-Path: <gcc-bugs-return-662835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115976 invoked by alias); 9 Dec 2019 22:45: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 115370 invoked by uid 48); 9 Dec 2019 22:45:16 -0000
From: "skpgkp2 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92807] gcc generate extra move for the snippet code along with lea instruction.
Date: Mon, 09 Dec 2019 22:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: skpgkp2 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-92807-4-PWDhDo9wNe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92807-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00905.txt.bz2
Content-length: 187
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92807
--- Comment #5 from Sunil Pandey <skpgkp2 at gmail dot com> ---
Patch link: https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00450.html
>From gcc-bugs-return-662836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:49:54 2019
Return-Path: <gcc-bugs-return-662836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124324 invoked by alias); 9 Dec 2019 22:49:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124250 invoked by uid 48); 9 Dec 2019 22:49:49 -0000
From: "anders at wahrzeichnen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92875] GCC ignores the floating-point 'f' suffix in C11 mode
Date: Mon, 09 Dec 2019 22:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders at wahrzeichnen dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92875-4-d0goFe4Xl7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00906.txt.bz2
Content-length: 539
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92875
--- Comment #4 from anders at wahrzeichnen dot de <anders at wahrzeichnen dot de> ---
I don't know about other archs, but on amd64, GCC emits comiss insns (SSE2
single-precision scalar compare) for f0, f1, and f2 and comisd insns (SSE2
double-precision scalar compare) for f3. So this is evidently not a problem on
amd64 (i.e. it does not depend on how the decimal-to-binary rounding was done
for the value 0.1). Conclusion: Ignoring the 'f' suffix seems to be specific
for 387.
>From gcc-bugs-return-662837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:50:19 2019
Return-Path: <gcc-bugs-return-662837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125298 invoked by alias); 9 Dec 2019 22:50: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 125141 invoked by uid 48); 9 Dec 2019 22:50:11 -0000
From: "eitan at mosenkis dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/83967] LTO removes C functions declared as weak in assembler(depending on files order in linking)
Date: Mon, 09 Dec 2019 22:50: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: 7.2.1
X-Bugzilla-Keywords: lto, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eitan at mosenkis dot net
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: cc
Message-ID: <bug-83967-4-kVfsPWseCI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83967-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83967-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00907.txt.bz2
Content-length: 1341
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83967
eitan at mosenkis dot net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eitan at mosenkis dot net
--- Comment #15 from eitan at mosenkis dot net ---
(In reply to Matthijs Kooijman from comment #14)
> I actually think this is a different problem from the fixed
> https://sourceware.org/bugzilla/show_bug.cgi?id=22502. Using gcc 8.2.1 and
> binutils 2.31.51.20181213 from the STM32 Arduino core
> (https://github.com/stm32duino/Arduino_Core_STM32), I can still reproduce
> this problem using the example from comment 11 (and also in an actual
> implementation using stm32duino). I also tested the example from the linked
> bug, which *is* indeed fixed, leading me to believe this is a different
> problem (or the fix is not complete yet).
>
> The example from this bug is a lot bigger than the one from 22502, so there
> is probably something in here that triggers this. Maybe that the weak
> implementation is defined in assembly rather than C?
I am also still able to reproduce the problem in production code
(http://github.com/solokeys/solo) using GNU ld (GNU Tools for Arm Embedded
Processors 9-2019-q4-major) 2.33.1.20191025.
>From gcc-bugs-return-662840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:53:33 2019
Return-Path: <gcc-bugs-return-662840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 457 invoked by alias); 9 Dec 2019 22: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 361 invoked by uid 55); 9 Dec 2019 22:53:29 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92116] Potential null pointer dereference in 'gomp_acc_remove_pointer'
Date: Mon, 09 Dec 2019 22: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge 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-92116-4-1J5nZFuqqE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92116-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92116-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00910.txt.bz2
Content-length: 1222
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92116
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Author: tschwinge
Date: Mon Dec 9 22:52:56 2019
New Revision: 279147
URL: https://gcc.gnu.org/viewcvs?rev=279147&root=gcc&view=rev
Log:
[PR92116, PR92877] [OpenACC] Replace 'openacc.data_environ' by standard libgomp
mechanics
libgomp/
PR libgomp/92116
PR libgomp/92877
* oacc-mem.c (lookup_dev): Reimplement. Adjust all users.
* libgomp.h (struct acc_dispatch_t): Remove 'data_environ' member.
Adjust all users.
* testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-4-2.c:
Remove XFAIL.
* testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-4.c:
Likewise.
* testsuite/libgomp.oacc-c-c++-common/pr92877-1.c: New file.
Added:
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr92877-1.c
Modified:
trunk/libgomp/ChangeLog
trunk/libgomp/libgomp.h
trunk/libgomp/oacc-host.c
trunk/libgomp/oacc-mem.c
trunk/libgomp/target.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-4-2.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-4.c
>From gcc-bugs-return-662841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:53:33 2019
Return-Path: <gcc-bugs-return-662841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 460 invoked by alias); 9 Dec 2019 22: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 342 invoked by uid 55); 9 Dec 2019 22:53:29 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92877] [OpenACC] Failure to resolve back via 'acc_hostptr' an 'acc_deviceptr' retrieved for a structured mapping
Date: Mon, 09 Dec 2019 22:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92877-4-qgPBEc6bsg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00911.txt.bz2
Content-length: 1222
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92877
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Author: tschwinge
Date: Mon Dec 9 22:52:56 2019
New Revision: 279147
URL: https://gcc.gnu.org/viewcvs?rev=279147&root=gcc&view=rev
Log:
[PR92116, PR92877] [OpenACC] Replace 'openacc.data_environ' by standard libgomp
mechanics
libgomp/
PR libgomp/92116
PR libgomp/92877
* oacc-mem.c (lookup_dev): Reimplement. Adjust all users.
* libgomp.h (struct acc_dispatch_t): Remove 'data_environ' member.
Adjust all users.
* testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-4-2.c:
Remove XFAIL.
* testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-4.c:
Likewise.
* testsuite/libgomp.oacc-c-c++-common/pr92877-1.c: New file.
Added:
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr92877-1.c
Modified:
trunk/libgomp/ChangeLog
trunk/libgomp/libgomp.h
trunk/libgomp/oacc-host.c
trunk/libgomp/oacc-mem.c
trunk/libgomp/target.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-4-2.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-4.c
>From gcc-bugs-return-662839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:53:23 2019
Return-Path: <gcc-bugs-return-662839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130395 invoked by alias); 9 Dec 2019 22:53: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 130334 invoked by uid 55); 9 Dec 2019 22:53:19 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92503] [OpenACC] Behavior of 'acc_free' if the memory space is still used in a mapping
Date: Mon, 09 Dec 2019 22:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92503-4-ldSoxAXjX4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92503-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92503-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00909.txt.bz2
Content-length: 2821
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92503
--- Comment #4 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Author: tschwinge
Date: Mon Dec 9 22:52:47 2019
New Revision: 279146
URL: https://gcc.gnu.org/viewcvs?rev=279146&root=gcc&view=rev
Log:
[PR92503] [OpenACC] Don't silently 'acc_unmap_data' in 'acc_free'
libgomp/
PR libgomp/92503
* oacc-mem.c (acc_free): Error out instead of 'acc_unmap_data'.
* testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-1.c: New
file.
* testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-2.c:
Likewise.
* testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-3-2.c:
Likewise.
* testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-3.c:
Likewise.
* testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-4-2.c:
Likewise.
* testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-4.c:
Likewise.
* testsuite/libgomp.oacc-c-c++-common/clauses-1.c: Adjust.
* testsuite/libgomp.oacc-c-c++-common/context-1.c: Likewise.
* testsuite/libgomp.oacc-c-c++-common/context-2.c: Likewise.
* testsuite/libgomp.oacc-c-c++-common/context-3.c: Likewise.
* testsuite/libgomp.oacc-c-c++-common/context-4.c: Likewise.
* testsuite/libgomp.oacc-c-c++-common/lib-13.c: Likewise.
* testsuite/libgomp.oacc-c-c++-common/lib-14.c: Likewise.
* testsuite/libgomp.oacc-c-c++-common/lib-18.c: Likewise.
* testsuite/libgomp.oacc-c-c++-common/lib-91.c: Likewise.
* testsuite/libgomp.oacc-c-c++-common/nested-1.c: Likewise.
Added:
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-1.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-2.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-3-2.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-3.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-4-2.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_free-pr92503-4.c
Modified:
trunk/libgomp/ChangeLog
trunk/libgomp/oacc-mem.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/clauses-1.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/context-1.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/context-2.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/context-3.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/context-4.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/lib-13.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/lib-14.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/lib-18.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/lib-91.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/nested-1.c
>From gcc-bugs-return-662838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:53:13 2019
Return-Path: <gcc-bugs-return-662838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129618 invoked by alias); 9 Dec 2019 22:53: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 129543 invoked by uid 55); 9 Dec 2019 22:53:08 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92840] [OpenACC] Disallow 'acc_unmap_data' for everything other than 'acc_map_data'
Date: Mon, 09 Dec 2019 22:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92840-4-DNLdLDHRxU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00908.txt.bz2
Content-length: 1404
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92840
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Author: tschwinge
Date: Mon Dec 9 22:52:36 2019
New Revision: 279145
URL: https://gcc.gnu.org/viewcvs?rev=279145&root=gcc&view=rev
Log:
[PR92840] [OpenACC] Refuse 'acc_unmap_data' unless mapped by 'acc_map_data'
libgomp/
PR libgomp/92840
* oacc-mem.c (acc_map_data): Clarify reference counting behavior.
(acc_unmap_data): Add error case for 'REFCOUNT_INFINITY'.
* testsuite/libgomp.oacc-c-c++-common/acc_unmap_data-pr92840-1.c:
New file.
* testsuite/libgomp.oacc-c-c++-common/acc_unmap_data-pr92840-2.c:
Likewise.
* testsuite/libgomp.oacc-c-c++-common/acc_unmap_data-pr92840-3.c:
Likewise.
* testsuite/libgomp.oacc-c-c++-common/clauses-1.c: Adjust.
* testsuite/libgomp.oacc-c-c++-common/nested-1.c: Adjust.
Added:
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_unmap_data-pr92840-1.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_unmap_data-pr92840-2.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/acc_unmap_data-pr92840-3.c
Modified:
trunk/libgomp/ChangeLog
trunk/libgomp/oacc-mem.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/clauses-1.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/nested-1.c
>From gcc-bugs-return-662842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:54:10 2019
Return-Path: <gcc-bugs-return-662842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3091 invoked by alias); 9 Dec 2019 22:54: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 3062 invoked by uid 48); 9 Dec 2019 22:54:06 -0000
From: "ville.voutilainen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92878] New: Parenthesized aggregate initialization doesn't work in a new-expression
Date: Mon, 09 Dec 2019 22:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ville.voutilainen 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-92878-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00912.txt.bz2
Content-length: 784
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92878
Bug ID: 92878
Summary: Parenthesized aggregate initialization doesn't work in
a new-expression
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ville.voutilainen at gmail dot com
Target Milestone: ---
//#include <memory>
struct aggressive_aggregate
{
int a;
int b;
};
int main()
{
auto x = aggressive_aggregate(1,2); // OK
auto y = new aggressive_aggregate(1,2); // rejected, should be OK?
//auto z = std::make_unique<aggressive_aggregate>(1,2); // rejected, should
be OK?
}
>From gcc-bugs-return-662843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 22:59:29 2019
Return-Path: <gcc-bugs-return-662843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65897 invoked by alias); 9 Dec 2019 22: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 63220 invoked by uid 48); 9 Dec 2019 22:59:22 -0000
From: "bp at alien8 dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92841] Optimize -fstack-protector-strong code generation a bit
Date: Mon, 09 Dec 2019 22:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bp at alien8 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-92841-4-e08aTQVuhx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00913.txt.bz2
Content-length: 541
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841
--- Comment #5 from Boris <bp at alien8 dot de> ---
Hohumm, looks good - this is the same site it generated with your patch:
# arch/x86/kernel/cpu/scattered.c:48: {
movq %gs:40, %rax # MEM[(<address-space-2> long unsigned int
*)40B], prephitmp_18
movq %rax, 16(%rsp) # prephitmp_18, D.21446
movl $6, %eax #, prephitmp_18
jmp .L6 #
I haven't checked any other sites whether they are still fine but I'll do that
soon.
Thx.
>From gcc-bugs-return-662844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 23:06:27 2019
Return-Path: <gcc-bugs-return-662844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83517 invoked by alias); 9 Dec 2019 23:06: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 83343 invoked by uid 48); 9 Dec 2019 23:06:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92878] Parenthesized aggregate initialization doesn't work in a new-expression
Date: Mon, 09 Dec 2019 23:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 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-92878-4-xqqNM7T8Nn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92878-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92878-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00914.txt.bz2
Content-length: 475
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92878
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-09
CC| |redi at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-662845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 23:09:39 2019
Return-Path: <gcc-bugs-return-662845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95681 invoked by alias); 9 Dec 2019 23:09: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 95310 invoked by uid 48); 9 Dec 2019 23:09:35 -0000
From: "ville.voutilainen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92878] Parenthesized aggregate initialization doesn't work in a new-expression
Date: Mon, 09 Dec 2019 23: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ville.voutilainen 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-92878-4-GDvqgXQ49m@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92878-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92878-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00915.txt.bz2
Content-length: 331
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92878
--- Comment #1 from Ville Voutilainen <ville.voutilainen at gmail dot com> ---
Wishlist item: please add a C++2a mode libstdc++ test that verifies that
make_unique and make_shared work with aggregates. Bonus points for
std::allocator_traits<std::allocator<Aggr>>::construct.
>From gcc-bugs-return-662846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 23:12:18 2019
Return-Path: <gcc-bugs-return-662846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98705 invoked by alias); 9 Dec 2019 23:12: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 98667 invoked by uid 55); 9 Dec 2019 23:12:13 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92875] GCC ignores the floating-point 'f' suffix in C11 mode
Date: Mon, 09 Dec 2019 23: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92875-4-hSq9NhWKIY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00916.txt.bz2
Content-length: 572
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92875
--- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Most architectures use FLT_EVAL_METHOD == 0. It's specific to x87 (and
older m68k) that FLT_EVAL_METHOD == 2 because x87 doesn't support direct
arithmetic on float or double. Lack of direct float and double arithmetic
requires FLT_EVAL_METHOD == 2 and FLT_EVAL_METHOD == 2 requires
interpreting floating constants to the range and precision of long double,
whatever their semantic type.
>From gcc-bugs-return-662847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 23:19:56 2019
Return-Path: <gcc-bugs-return-662847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117538 invoked by alias); 9 Dec 2019 23:19:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117453 invoked by uid 48); 9 Dec 2019 23:19:51 -0000
From: "anders at wahrzeichnen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92875] GCC ignores the floating-point 'f' suffix in C11 mode
Date: Mon, 09 Dec 2019 23:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders at wahrzeichnen dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92875-4-p8MAY8yVqS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00917.txt.bz2
Content-length: 1130
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92875
--- Comment #6 from anders at wahrzeichnen dot de <anders at wahrzeichnen dot de> ---
(In reply to joseph@codesourcery.com from comment #3)
> This is as specified in the C standard.
I guess you are referring to the C18 section
6.3.1.8 (2) "The values of floating operands and of the results of floating
expressions may be represented in greater range and precision than that
required by the type; the types are not changed thereby. --footnote: The cast
and assignment operators are still required to remove extra range and
precision."
in conjunction with
6.6 (5) "An expression that evaluates to a constant is required in several
contexts. If a floating expression is evaluated in the translation environment,
the arithmetic range and precision shall be at least as great as if the
expression were being evaluated in the execution environment. --footnote: The
use of evaluation formats as characterized by FLT_EVAL_METHOD also applies to
evaluation in the translation environment."
If so, I propose to close this bug (as __FLT_EVAL_METHOD__ is indeed 2).
>From gcc-bugs-return-662848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 23:20:57 2019
Return-Path: <gcc-bugs-return-662848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119309 invoked by alias); 9 Dec 2019 23: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 119242 invoked by uid 48); 9 Dec 2019 23:20:53 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92875] GCC ignores the floating-point 'f' suffix in C11 mode
Date: Mon, 09 Dec 2019 23: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: unknown
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-92875-4-SoJCyNLNKw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00918.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92875
--- Comment #7 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
(In reply to joseph@codesourcery.com from comment #5)
> Lack of direct float and double arithmetic requires FLT_EVAL_METHOD == 2
No, FLT_EVAL_METHOD could also be negative, in which case GCC would be allowed
to evaluate floating-point constants of type float in whatever range and
precision it wishes.
>From gcc-bugs-return-662849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 23:24:26 2019
Return-Path: <gcc-bugs-return-662849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124422 invoked by alias); 9 Dec 2019 23:24: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 124189 invoked by uid 48); 9 Dec 2019 23:24:18 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92875] GCC ignores the floating-point 'f' suffix in C11 mode
Date: Mon, 09 Dec 2019 23:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
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: cc
Message-ID: <bug-92875-4-Bsk9E62k2Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00919.txt.bz2
Content-length: 1009
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92875
Vincent Lefèvre <vincent-gcc at vinc17 dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vincent-gcc at vinc17 dot net
--- Comment #8 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
(In reply to anders@wahrzeichnen.de from comment #6)
> 6.6 (5) "An expression that evaluates to a constant is required in several
> contexts. If a floating expression is evaluated in the translation
> environment, the arithmetic range and precision shall be at least as great
> as if the expression were being evaluated in the execution environment.
> --footnote: The use of evaluation formats as characterized by
> FLT_EVAL_METHOD also applies to evaluation in the translation environment."
This is about constant expressions and is not applicable to constants. See
5.2.4.2.2p9 for constants.
>From gcc-bugs-return-662850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 09 23:33:36 2019
Return-Path: <gcc-bugs-return-662850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103759 invoked by alias); 9 Dec 2019 23:33: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 103679 invoked by uid 48); 9 Dec 2019 23:33:32 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92116] Potential null pointer dereference in 'gomp_acc_remove_pointer'
Date: Mon, 09 Dec 2019 23:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to
Message-ID: <bug-92116-4-I6gWicKzGT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92116-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92116-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00920.txt.bz2
Content-length: 905
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92116
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Assignee|msebor at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #2)
IIRC, I assumed based on the check for t != NULL in the controlling expression
that the loop could terminate with t == NULL. The warning code predates the
patch I was testing -- it just enables it without enhancing its implementation.
But since r279147 removes the loop I think this report can be resolved, either
as fixed or as invalid.
>From gcc-bugs-return-662851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 01:32:08 2019
Return-Path: <gcc-bugs-return-662851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41048 invoked by alias); 10 Dec 2019 01:32: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 40829 invoked by uid 48); 10 Dec 2019 01:32:04 -0000
From: "helijia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92398] [10 regression] error in update of gcc.target/powerpc/pr72804.c in r277872
Date: Tue, 10 Dec 2019 01:32: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: helijia 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-92398-4-wutbLrjL1X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00921.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92398
Li Jia He <helijia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |helijia at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #12 from Li Jia He <helijia at gcc dot gnu.org> ---
fixed on trunk together with r278918. On behave of Xiong Hu to close the issue
since his account couldn't.
>From gcc-bugs-return-662852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 02:02:56 2019
Return-Path: <gcc-bugs-return-662852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67759 invoked by alias); 10 Dec 2019 02:02: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 67656 invoked by uid 48); 10 Dec 2019 02:02:50 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/90374] Fortran 2018: Support d0.d, e0.d, es0.d, en0.d, g0.d and ew.d e0 edit descriptors for output
Date: Tue, 10 Dec 2019 02: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90374-4-0DWC1kxHuf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90374-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90374-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00922.txt.bz2
Content-length: 587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90374
--- Comment #11 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Thomas Henlich from comment #10)
--- snip ---
>
> 13.7.2.3.3 E and D editing
> ... If e is positive the exponent part contains e digits, otherwise it
> contains the minimum number of digits required to represent the exponent
> value. ...
Yes, thanks Thomas.
I will fix this. It was very easy to do what I did with the existing code. To
get rid of the leading zero on the exponent will require me to scratch my head
a little further.
Cheers
>From gcc-bugs-return-662853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 04:13:05 2019
Return-Path: <gcc-bugs-return-662853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36734 invoked by alias); 10 Dec 2019 04:13: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 36700 invoked by uid 48); 10 Dec 2019 04:13:01 -0000
From: "cas43 at cs dot stanford.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92879] New: incorrect warning of __builtin_memset offset is out of the bounds on zero-size allocation and initialization
Date: Tue, 10 Dec 2019 04: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cas43 at cs dot stanford.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-92879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00923.txt.bz2
Content-length: 1830
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92879
Bug ID: 92879
Summary: incorrect warning of __builtin_memset offset is out of
the bounds on zero-size allocation and initialization
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: cas43 at cs dot stanford.edu
Target Milestone: ---
DIAGNOSTIC:
g++ prog.cpp -c -Wall -O3
In constructor ‘S::S(int)’,
inlined from ‘(static initializers for prog.cpp)’ at prog.cpp:16:6:
prog.cpp:13:30: warning: ‘void* __builtin_memset(void*, int, long unsigned
int)’ offset [0, 3] is out of the bounds [0, 0]
[]8;;https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Warray-bounds-Warray-bounds]8;;]
13 | for(int i=0;i<m;i++) new(p+i)int();
| ^~~~~~~~~~~~~
CODE:
inline void* operator new(long unsigned int, void* v) noexcept
{
return v;
}
struct S
{
int* p;
int m;
S(int i)
{
m=i;
p=(int*)new unsigned char[sizeof(int)*m];
for(int i=0;i<m;i++) new(p+i)int();
}
};
S a(0);
COMPILER:
Using built-in specs.
COLLECT_GCC=/home/craig/new-gcc/i-trunk/bin/g++
COLLECT_LTO_WRAPPER=/home/craig/new-gcc/i-trunk/libexec/gcc/x86_64-pc-linux-gnu/10.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../s-trunk/configure --prefix=/home/craig/new-gcc/i-trunk
--disable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.0.0 20191209 (experimental) (GCC)
EXPLANATION:
The body of the initialization loop never executes, so no out-of-bounds is
possible.
>From gcc-bugs-return-662854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 04:26:24 2019
Return-Path: <gcc-bugs-return-662854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46283 invoked by alias); 10 Dec 2019 04:26: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 46248 invoked by uid 48); 10 Dec 2019 04:26:19 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92879] incorrect warning of __builtin_memset offset is out of the bounds on zero-size allocation and initialization
Date: Tue, 10 Dec 2019 04: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: diagnostic
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-92879-4-Tamne8d3pj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00924.txt.bz2
Content-length: 733
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92879
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Target| |x86_64-linux-gnu
| |aarch64-linux-gnu (LP64
| |targets)
Component|c++ |tree-optimization
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
It is seeming related to ILP32 vs LP64. That is the warning does not show up
in ILP32 ABI targets.
>From gcc-bugs-return-662855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 05:00:02 2019
Return-Path: <gcc-bugs-return-662855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82683 invoked by alias); 10 Dec 2019 05:00: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 82442 invoked by uid 48); 10 Dec 2019 04:59:56 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92865] [10 Regression] error: unrecognizable insn: in extract_insn, at recog.c:2294 since r279107
Date: Tue, 10 Dec 2019 05: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: crazylht at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: liuhongt at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92865-4-PX993TOFPZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00925.txt.bz2
Content-length: 2022
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
--- Comment #6 from Hongtao.liu <crazylht at gmail dot com> ---
The missing point of my patch is for 512-bit vector compare, integer mask
vector compare still should be used even with target_xop, that's the root cause
of this issue.
Refer to this part.
---------------
- if (GET_MODE_SIZE (cmp_ops_mode) == 64)
+ if (ix86_valid_mask_cmp_mode (cmp_ops_mode))
{
unsigned int nbits = GET_MODE_NUNITS (cmp_ops_mode);
- cmp_mode = int_mode_for_size (nbits, 0).require ();
maskcmp = true;
+ cmp_mode = nbits > 8 ? int_mode_for_size (nbits, 0).require () :
E_QImode;
}
else
cmp_mode = cmp_ops_mode;
@@ -3461,37 +3484,6 @@ ix86_expand_sse_cmp (rtx dest, enum rtx_code code, rtx
cmp_op0, rtx cmp_op1,
|| (op_false && reg_overlap_mentioned_p (dest, op_false)))
dest = gen_reg_rtx (maskcmp ? cmp_mode : mode);
- /* Compare patterns for int modes are unspec in AVX512F only. */
- if (maskcmp && (code == GT || code == EQ))
- {
- rtx (*gen)(rtx, rtx, rtx);
-
- switch (cmp_ops_mode)
- {
- case E_V64QImode:
- gcc_assert (TARGET_AVX512BW);
- gen = code == GT ? gen_avx512bw_gtv64qi3 : gen_avx512bw_eqv64qi3_1;
- break;
- case E_V32HImode:
- gcc_assert (TARGET_AVX512BW);
- gen = code == GT ? gen_avx512bw_gtv32hi3 : gen_avx512bw_eqv32hi3_1;
- break;
- case E_V16SImode:
- gen = code == GT ? gen_avx512f_gtv16si3 : gen_avx512f_eqv16si3_1;
- break;
- case E_V8DImode:
- gen = code == GT ? gen_avx512f_gtv8di3 : gen_avx512f_eqv8di3_1;
- break;
- default:
- gen = NULL;
- }
-
- if (gen)
- {
- emit_insn (gen (dest, cmp_op0, cmp_op1));
- return dest;
- }
- }
x = gen_rtx_fmt_ee (code, cmp_mode, cmp_op0, cmp_op1);
if (cmp_mode != mode && !maskcmp)
-------------------------
>From gcc-bugs-return-662856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:07:06 2019
Return-Path: <gcc-bugs-return-662856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56577 invoked by alias); 10 Dec 2019 08:07:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56538 invoked by uid 48); 10 Dec 2019 08:07:02 -0000
From: "arthur200126 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/92880] New: Documentation for Built-in Vector-Extensions should mention C99 Fixed-width ints as base types
Date: Tue, 10 Dec 2019 08:07: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: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: arthur200126 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-92880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00926.txt.bz2
Content-length: 1326
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92880
Bug ID: 92880
Summary: Documentation for Built-in Vector-Extensions should
mention C99 Fixed-width ints as base types
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: web
Assignee: unassigned at gcc dot gnu.org
Reporter: arthur200126 at gmail dot com
Target Milestone: ---
The current version of gcc doc section 6.52 "Using Vector Instructions through
Built-in Functions" does not seem to mention the possibility of using C99
fixed-width stdint types like uint32_t.
Since a quick test seems to show that these types do in fact work, it would be
a good idea to mention it in the documentation. This should, in theory, allow
programmers to write truly platform-independent vectorized code.
A test case with some knobs to play with:
#include <stdint.h>
#define namevxsi(u, l) vec_i##u##x##l##_t
#define mkvxsi(u, l) \
typedef uint##u##_t namevxsi(u, l) __attribute__ ((vector_size (l * u /
8)))
mkvxsi(8, 16); /* vec_i8x16_t */
#define vectype namevxsi(8, 16)
vectype op(vectype a, vectype b)
{
a = 2 * b + 1;
return a;
}
(Hell, it even works with __uint128_t.)
>From gcc-bugs-return-662857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:14:48 2019
Return-Path: <gcc-bugs-return-662857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69267 invoked by alias); 10 Dec 2019 08:14: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 69194 invoked by uid 48); 10 Dec 2019 08:14:44 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/92880] Documentation for Built-in Vector-Extensions should mention C99 Fixed-width ints as base types
Date: Tue, 10 Dec 2019 08:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: 9.2.1
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-92880-4-2izOWRGtJc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92880-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00927.txt.bz2
Content-length: 234
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92880
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Because the fixed types in C99 are just typedef of normal types. So it really
does not need to describe that.
>From gcc-bugs-return-662858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:21:15 2019
Return-Path: <gcc-bugs-return-662858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76767 invoked by alias); 10 Dec 2019 08: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 76724 invoked by uid 48); 10 Dec 2019 08:21:11 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92881] New: [OpenACC] In async context, need to use 'gomp_remove_var_async' instead of 'gomp_remove_var'
Date: Tue, 10 Dec 2019 08:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92881-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00928.txt.bz2
Content-length: 867
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92881
Bug ID: 92881
Summary: [OpenACC] In async context, need to use
'gomp_remove_var_async' instead of 'gomp_remove_var'
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: openacc, patch
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: jakub at gcc dot gnu.org, jules at gcc dot gnu.org
Target Milestone: ---
As discussed in
<http://mid.mail-archive.com/20191209150415.4100dbd9@squid.athome>.
Searching through my email archive, I just re-discovered that it was actually
me who wrote some of that code,
<https://gcc.gnu.org/ml/gcc-patches/2018-12/msg01620.html>. ;-)
>From gcc-bugs-return-662859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:26:22 2019
Return-Path: <gcc-bugs-return-662859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85764 invoked by alias); 10 Dec 2019 08: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 85708 invoked by uid 48); 10 Dec 2019 08:26:18 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92881] [OpenACC] In async context, need to use 'gomp_remove_var_async' instead of 'gomp_remove_var'
Date: Tue, 10 Dec 2019 08:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules 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-92881-4-TevcEfH2Rb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92881-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92881-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00929.txt.bz2
Content-length: 495
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92881
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-10
Assignee|unassigned at gcc dot gnu.org |jules at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-662860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:26:56 2019
Return-Path: <gcc-bugs-return-662860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87520 invoked by alias); 10 Dec 2019 08:26: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 87468 invoked by uid 48); 10 Dec 2019 08:26:51 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92882] New: [10 Regression] ICE in regstat_bb_compute_calls_crossed, at regstat.c:327 since r279124
Date: Tue, 10 Dec 2019 08:26: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: 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-92882-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00930.txt.bz2
Content-length: 2346
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92882
Bug ID: 92882
Summary: [10 Regression] ICE in
regstat_bb_compute_calls_crossed, at regstat.c:327
since r279124
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-linux-gnu
Target: s390x-linux-gnu
After we added a new assert in the revision, I see the following ICE:
$ s390x-linux-gnu-gcc
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/secnds.f -fno-inline -O2
-c
during RTL pass: sched1
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/secnds.f:34:0:
34 | end
|
internal compiler error: in regstat_bb_compute_calls_crossed, at regstat.c:327
0x5875ee regstat_bb_compute_calls_crossed
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/regstat.c:327
0x5875ee regstat_compute_calls_crossed()
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/regstat.c:380
0x113f4dc sched_init()
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/haifa-sched.c:7337
0x1140b2d haifa_sched_init()
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/haifa-sched.c:7354
0xacb20a schedule_insns()
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/sched-rgn.c:3514
0xacb813 schedule_insns()
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/sched-rgn.c:3508
0xacb813 rest_of_handle_sched
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/sched-rgn.c:3726
0xacb813 execute
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-s390x/build/gcc/sched-rgn.c:3834
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-662862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:27:28 2019
Return-Path: <gcc-bugs-return-662862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89091 invoked by alias); 10 Dec 2019 08: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 89039 invoked by uid 48); 10 Dec 2019 08:27:24 -0000
From: "marxin 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: Tue, 10 Dec 2019 08: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: 10.0
X-Bugzilla-Keywords: needs-bisection
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: matmal01 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92410-4-aF9k4z4729@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: 2019-12/txt/msg00932.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92410
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
I would close this as fixed.
>From gcc-bugs-return-662861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:27:11 2019
Return-Path: <gcc-bugs-return-662861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88313 invoked by alias); 10 Dec 2019 08:27: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 88222 invoked by uid 48); 10 Dec 2019 08:27:07 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92882] [10 Regression] ICE in regstat_bb_compute_calls_crossed, at regstat.c:327 since r279124
Date: Tue, 10 Dec 2019 08: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone everconfirmed
Message-ID: <bug-92882-4-LgLldQeDta@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92882-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92882-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00931.txt.bz2
Content-length: 537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92882
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
CC| |matmal01 at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
>From gcc-bugs-return-662863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:33:00 2019
Return-Path: <gcc-bugs-return-662863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98660 invoked by alias); 10 Dec 2019 08:33: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 98604 invoked by uid 48); 10 Dec 2019 08:32:56 -0000
From: "doko at ubuntu dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92866] [10 Regression] libgo build failure on arm-linux-gnueabihf (ICE, segfault)
Date: Tue, 10 Dec 2019 08:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at ubuntu 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92866-4-a14cnhQfw7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92866-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92866-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00933.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92866
Matthias Klose <doko at ubuntu dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #2 from Matthias Klose <doko at ubuntu dot com> ---
and it works again with r279131 ...
>From gcc-bugs-return-662864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:37:33 2019
Return-Path: <gcc-bugs-return-662864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122004 invoked by alias); 10 Dec 2019 08:37: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 121944 invoked by uid 55); 10 Dec 2019 08:37:28 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92862] Suspicious codes in tree-ssa-loop-niter.c and predict.c
Date: Tue, 10 Dec 2019 08:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92862-4-dr41nLFzb8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00934.txt.bz2
Content-length: 632
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92862
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Tue Dec 10 08:36:56 2019
New Revision: 279156
URL: https://gcc.gnu.org/viewcvs?rev=279156&root=gcc&view=rev
Log:
Fix typos in 2 functions.
2019-12-10 Martin Liska <mliska@suse.cz>
PR tree-optimization/92862
* predict.c (predict_paths_leading_to_edge): Fix typo from e to e2.
* tree-ssa-loop-niter.c (loop_only_exit_p): Return false
instead of true;
Modified:
trunk/gcc/ChangeLog
trunk/gcc/predict.c
trunk/gcc/tree-ssa-loop-niter.c
>From gcc-bugs-return-662865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:38:48 2019
Return-Path: <gcc-bugs-return-662865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124468 invoked by alias); 10 Dec 2019 08:38: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 124425 invoked by uid 48); 10 Dec 2019 08:38:43 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92862] Suspicious codes in tree-ssa-loop-niter.c and predict.c
Date: Tue, 10 Dec 2019 08: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92862-4-PcNYqKDUWj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00935.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92862
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-662866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:43:05 2019
Return-Path: <gcc-bugs-return-662866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130675 invoked by alias); 10 Dec 2019 08: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 130601 invoked by uid 48); 10 Dec 2019 08:43:00 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92879] [10 Regression] incorrect warning of __builtin_memset offset is out of the bounds on zero-size allocation and initialization
Date: Tue, 10 Dec 2019 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: 10.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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone short_desc everconfirmed cf_known_to_fail
Message-ID: <bug-92879-4-pDw19dj2Vb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00936.txt.bz2
Content-length: 1194
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92879
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
CC| |marxin at gcc dot gnu.org,
| |msebor at gcc dot gnu.org
Known to work| |9.2.0
Target Milestone|--- |10.0
Summary|incorrect warning of |[10 Regression] incorrect
|__builtin_memset offset is |warning of __builtin_memset
|out of the bounds on |offset is out of the bounds
|zero-size allocation and |on zero-size allocation and
|initialization |initialization
Ever confirmed|0 |1
Known to fail| |10.0
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r278983.
>From gcc-bugs-return-662867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:47:18 2019
Return-Path: <gcc-bugs-return-662867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9623 invoked by alias); 10 Dec 2019 08:47: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 9550 invoked by uid 48); 10 Dec 2019 08:47:14 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92876] ICE in expand_UNIQUE, at internal-fn.c:2599
Date: Tue, 10 Dec 2019 08:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92876-4-3TpXSvnijP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92876-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92876-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00937.txt.bz2
Content-length: 697
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92876
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
CC| |cesar at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r231081. It was rejected before the revision.
>From gcc-bugs-return-662868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 08:52:01 2019
Return-Path: <gcc-bugs-return-662868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49010 invoked by alias); 10 Dec 2019 08: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 48935 invoked by uid 48); 10 Dec 2019 08:51:57 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92874] ICE in gfc_dep_compare_expr, at fortran/dependency.c:36
Date: Tue, 10 Dec 2019 08:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-92874-4-mr8oQIOjmV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92874-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92874-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00938.txt.bz2
Content-length: 649
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92874
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-10
CC| |marxin at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, I've got a patch for that.
>From gcc-bugs-return-662869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 09:11:20 2019
Return-Path: <gcc-bugs-return-662869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78019 invoked by alias); 10 Dec 2019 09:11: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 77960 invoked by uid 48); 10 Dec 2019 09:11:16 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92873] ICE in unmodified_parm_or_parm_agg_item, at ipa-fnsummary.c:1166
Date: Tue, 10 Dec 2019 09:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92873-4-gHUZRkSjsW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92873-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92873-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00939.txt.bz2
Content-length: 584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92873
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, it's very old issue.
>From gcc-bugs-return-662870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 09:13:51 2019
Return-Path: <gcc-bugs-return-662870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84986 invoked by alias); 10 Dec 2019 09:13: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 84882 invoked by uid 48); 10 Dec 2019 09:13:47 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92843] [OpenACC] Disallow 'acc_delete' etc. for everything without a dynamic reference count
Date: Tue, 10 Dec 2019 09:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92843-4-K7mFN7ZQWj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00940.txt.bz2
Content-length: 1883
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92843
--- Comment #7 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to jules from comment #6)
> Please don't start making changes to the reference-counting code that is
> being replaced by my overhaul patch.
We first need to establish a stable baseline, with test cases, and then (or, as
part of that) merge the several independent pieces of the big "OpenACC
reference count overhaul".
> The existing code was rewritten for a
> reason -- that being, I hit various problems with it (albeit long since
> forgotten) that interfered with the manual deep-copy implementation.
So you'll have to dig out your notes, and/or we'll have to figure out any
rationale again, now. Patches that change such fundamental things in libgomp
we cannot just commit on the basis that once they made sense to somebody. They
have to come with rationale, and test cases.
> We have
> refcount self-checking code for the overhauled code.
... which surely can be adapted.
And, per my understanding, this is only checking libgomp internal consistency,
but not the semantics exposed to users via OpenACC directives/API calls etc.,
which in part you're changing of your patch (without test cases). This, again,
I've spent the best part of the past weeks understanding, writing test cases
for, filing GCC PRs, resolving them one by one, independently, incrementally,
comprehensibly.
> We can address corner-case bug fixes as follow-ons once the main overhaul
> patch is committed.
Further bug fixes, yes, but we have to make some reasonable effort to not
introduce new bugs with the big "OpenACC reference count overhaul" changes.
It doesn't help if these changes go in, then the OpenACC 2.6 manual deep copy
changes, but as part of that the dynamic reference counting behavior
unexpectedly changes/breaks, for example.
>From gcc-bugs-return-662871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 09:14:58 2019
Return-Path: <gcc-bugs-return-662871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87886 invoked by alias); 10 Dec 2019 09:14:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87724 invoked by uid 48); 10 Dec 2019 09:14:54 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92872] [10 Regression] ICE in build_fold_indirect_ref_loc, at fold-const.c:14842
Date: Tue, 10 Dec 2019 09:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-92872-4-YZocJUbU11@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92872-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92872-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00941.txt.bz2
Content-length: 904
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92872
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
CC| |burnus at gcc dot gnu.org,
| |kcy at codesourcery dot com,
| |marxin at gcc dot gnu.org
Known to work| |9.2.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r276444.
>From gcc-bugs-return-662872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 09:18:31 2019
Return-Path: <gcc-bugs-return-662872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110879 invoked by alias); 10 Dec 2019 09:18:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110825 invoked by uid 48); 10 Dec 2019 09:18:27 -0000
From: "igor.chorazewicz at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92869] C++17 wrongly reports aggregate type as not-aggregate (when explicitly defaulted ctors are added)
Date: Tue, 10 Dec 2019 09: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: igor.chorazewicz at intel dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92869-4-RX6NhJy99A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00942.txt.bz2
Content-length: 734
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92869
--- Comment #2 from Igor Chorazewicz <igor.chorazewicz at intel dot com> ---
Hm, from what I thought C++11 (not sure about C++14 but probably also) allows
ctors to be explicitly defaulted for aggregates. See C++11 [dcl.init.aggr].
Consider the following code:
#include <array>
#include <type_traits>
#include <iostream>
template <typename T, std::size_t N>
struct A {
A() = default;
A(const A &) = default;
A(A &&) = default;
T arr[N];
};
int main()
{
A<int, 3> a {{1,2,3}};
}
This code compiles with g++ 9.2 for -std=c++11, -std=c++14, std=c++17 (but not
for -std=c++2a) and fails to compile for g++ 10 for all standards
>From gcc-bugs-return-662873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 09:23:25 2019
Return-Path: <gcc-bugs-return-662873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121251 invoked by alias); 10 Dec 2019 09: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 121175 invoked by uid 48); 10 Dec 2019 09:23:20 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92848] [OpenACC] Memory leak for simple 'acc_create', 'acc_delete' sequence
Date: Tue, 10 Dec 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: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-92848-4-CJ68OTrVC9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00943.txt.bz2
Content-length: 972
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92848
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to jules from comment #2)
> Again, please don't change this code under the feet of the refcount overhaul
> patch!
But why? This here is one independent chance. The big "OpenACC reference
count overhaul" will then either lose some of its changes, or replace this here
by something else ('GOMP_MAP_VARS_OPENACC_ENTER_DATA'), but it's an incremental
step (forward).
> Using the (currently OpenMP-specific) GOMP_MAP_VARS_ENTER_DATA is
> going to end up mighty confusing from OpenACC-specific code.
Why do you think so? It has exactly! the semantics that we need here, for this
PR.
>From gcc-bugs-return-662874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 09:46:34 2019
Return-Path: <gcc-bugs-return-662874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61113 invoked by alias); 10 Dec 2019 09:46:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61096 invoked by uid 48); 10 Dec 2019 09:46:30 -0000
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92883] New: [10 Regression] ICE in compare_values_warnv
Date: Tue, 10 Dec 2019 09:46: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: krebbel at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92883-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00944.txt.bz2
Content-length: 2192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92883
Bug ID: 92883
Summary: [10 Regression] ICE in compare_values_warnv
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: krebbel at gcc dot gnu.org
Target Milestone: ---
Created attachment 47456
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47456&action=edit
Reduced testcase
Compiling the attached testcase for IBM Z with
gcc -O2 -march=z13 t.c -c
during IPA pass: cp
crash0.c: At top level:
crash0.c:718:1: internal compiler error: in compare_values_warnv, at
tree-vrp.c:540
0x1b5cd43 compare_values_warnv(tree_node*, tree_node*, bool*)
/home/andreas/gcc/gcc/tree-vrp.c:539
0x1b5ce15 compare_values(tree_node*, tree_node*)
/home/andreas/gcc/gcc/tree-vrp.c:700
0x1ba9beb value_range::check()
/home/andreas/gcc/gcc/value-range.cc:283
0x1baa673 value_range::set(tree_node*, tree_node*, value_range_kind)
/home/andreas/gcc/gcc/value-range.cc:236
0x1bad70b value_range::set(tree_node*, tree_node*, value_range_kind)
/home/andreas/gcc/gcc/value-range.cc:84
0x1bad70b value_range::intersect_helper(value_range const*, value_range const*)
/home/andreas/gcc/gcc/value-range.cc:943
0x1bae4c7 value_range::intersect(value_range const*)
/home/andreas/gcc/gcc/value-range.cc:1323
0x208db01 propagate_vr_across_jump_function
/home/andreas/gcc/gcc/ipa-cp.c:2020
0x208db01 propagate_constants_across_call
/home/andreas/gcc/gcc/ipa-cp.c:2393
0x20917d3 propagate_constants_topo
/home/andreas/gcc/gcc/ipa-cp.c:3313
0x20917d3 ipcp_propagate_stage
/home/andreas/gcc/gcc/ipa-cp.c:3409
0x20958f5 ipcp_driver
/home/andreas/gcc/gcc/ipa-cp.c:5261
0x20958f5 execute
/home/andreas/gcc/gcc/ipa-cp.c:5354
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.
The testcase compiles fine before r278185
>From gcc-bugs-return-662875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 09:55:45 2019
Return-Path: <gcc-bugs-return-662875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76796 invoked by alias); 10 Dec 2019 09:55: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 76759 invoked by uid 48); 10 Dec 2019 09:55:41 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92882] [10 Regression] ICE in regstat_bb_compute_calls_crossed, at regstat.c:327 since r279124
Date: Tue, 10 Dec 2019 09:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro 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: cf_gcctarget cc
Message-ID: <bug-92882-4-YN31h3hQdg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92882-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92882-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00945.txt.bz2
Content-length: 1539
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92882
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|s390x-linux-gnu |s390x-linux-gnu,
| |sparc-sun-solaris2.11
CC| |ro at gcc dot gnu.org
--- Comment #1 from Rainer Orth <ro at gcc dot gnu.org> ---
I'm seeing the same ICE on 32-bit SPARC (only; 64-bit is fine):
+FAIL: gfortran.fortran-torture/execute/math.f90, -O3 -g (internal compiler
error)
during RTL pass: sched1
/vol/gcc/src/hg/trunk/local/gcc/testsuite/gfortran.fortran-torture/execute/math.f90:19:0:
internal compiler error: in regstat_bb_compute_calls_crossed, at regstat.c:327
0xbc723b regstat_bb_compute_calls_crossed
/vol/gcc/src/hg/trunk/local/gcc/regstat.c:327
0xbc723b regstat_compute_calls_crossed()
/vol/gcc/src/hg/trunk/local/gcc/regstat.c:380
0x142882f sched_init()
/vol/gcc/src/hg/trunk/local/gcc/haifa-sched.c:7337
0x142a5ab haifa_sched_init()
/vol/gcc/src/hg/trunk/local/gcc/haifa-sched.c:7354
0xc0e59f schedule_insns()
/vol/gcc/src/hg/trunk/local/gcc/sched-rgn.c:3514
0xc0ef63 schedule_insns()
/vol/gcc/src/hg/trunk/local/gcc/sched-rgn.c:3508
0xc0ef63 rest_of_handle_sched
/vol/gcc/src/hg/trunk/local/gcc/sched-rgn.c:3726
0xc0ef63 execute
/vol/gcc/src/hg/trunk/local/gcc/sched-rgn.c:3834
>From gcc-bugs-return-662876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 10:04:39 2019
Return-Path: <gcc-bugs-return-662876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97892 invoked by alias); 10 Dec 2019 10:04: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 97832 invoked by uid 48); 10 Dec 2019 10:04:35 -0000
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92883] [10 Regression] ICE in compare_values_warnv
Date: Tue, 10 Dec 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: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: krebbel at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-92883-4-doiBDyFU7z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92883-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92883-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00946.txt.bz2
Content-length: 2044
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92883
Andreas Krebbel <krebbel at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #47456|0 |1
is obsolete| |
--- Comment #1 from Andreas Krebbel <krebbel at gcc dot gnu.org> ---
Created attachment 47457
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47457&action=edit
Actually reduced testcase
gcc -O2 t.c -c
during IPA pass: cp
t.c:17:1: internal compiler error: in compare_values_warnv, at tree-vrp.c:540
0x1b5cd43 compare_values_warnv(tree_node*, tree_node*, bool*)
/home/andreas/gcc/gcc/tree-vrp.c:539
0x1b5ce15 compare_values(tree_node*, tree_node*)
/home/andreas/gcc/gcc/tree-vrp.c:700
0x1ba9beb value_range::check()
/home/andreas/gcc/gcc/value-range.cc:283
0x1baa673 value_range::set(tree_node*, tree_node*, value_range_kind)
/home/andreas/gcc/gcc/value-range.cc:236
0x1bad70b value_range::set(tree_node*, tree_node*, value_range_kind)
/home/andreas/gcc/gcc/value-range.cc:84
0x1bad70b value_range::intersect_helper(value_range const*, value_range const*)
/home/andreas/gcc/gcc/value-range.cc:943
0x1bae4c7 value_range::intersect(value_range const*)
/home/andreas/gcc/gcc/value-range.cc:1323
0x208db01 propagate_vr_across_jump_function
/home/andreas/gcc/gcc/ipa-cp.c:2020
0x208db01 propagate_constants_across_call
/home/andreas/gcc/gcc/ipa-cp.c:2393
0x20917d3 propagate_constants_topo
/home/andreas/gcc/gcc/ipa-cp.c:3313
0x20917d3 ipcp_propagate_stage
/home/andreas/gcc/gcc/ipa-cp.c:3409
0x20958f5 ipcp_driver
/home/andreas/gcc/gcc/ipa-cp.c:5261
0x20958f5 execute
/home/andreas/gcc/gcc/ipa-cp.c:5354
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-662877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 10:06:00 2019
Return-Path: <gcc-bugs-return-662877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118480 invoked by alias); 10 Dec 2019 10:06: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 109331 invoked by uid 48); 10 Dec 2019 10:05:57 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92872] [10 Regression] ICE in build_fold_indirect_ref_loc, at fold-const.c:14842
Date: Tue, 10 Dec 2019 10: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: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92872-4-MstEn4sRXW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92872-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92872-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00947.txt.bz2
Content-length: 514
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92872
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #1)
> Confirmed, started with r276444.
Untested patch:
--- a/gcc/fortran/trans-array.c
+++ b/gcc/fortran/trans-array.c
@@ -884,3 +884,3 @@ get_CFI_desc (gfc_symbol *sym, gfc_expr *expr,
- if (tmp && DECL_LANG_SPECIFIC (tmp))
+ if (tmp && DECL_LANG_SPECIFIC (tmp) && GFC_DECL_SAVED_DESCRIPTOR (tmp))
tmp = GFC_DECL_SAVED_DESCRIPTOR (tmp);
>From gcc-bugs-return-662878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 10:09:04 2019
Return-Path: <gcc-bugs-return-662878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41734 invoked by alias); 10 Dec 2019 10:09: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 41656 invoked by uid 48); 10 Dec 2019 10:08:59 -0000
From: "will at kernel dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92424] [aarch64] Broken code with -fpatchable-function-entry and BTI
Date: Tue, 10 Dec 2019 10: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: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: will at kernel 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: cc
Message-ID: <bug-92424-4-ocUnhhw6dR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92424-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92424-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00948.txt.bz2
Content-length: 1292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92424
Will Deacon <will at kernel dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |will at kernel dot org
--- Comment #1 from Will Deacon <will at kernel dot org> ---
I just ran into this with GCC 9.2 and reproduced on trunk. The combination of
-fpatchable-function-entry with -mbranch-protection={standard,bti} is likely to
be used for building the Linux kernel when in-kernel BTI is used in conjunction
with dynamic function tracing. I think this will be a common configuration, so
although forcing the options to be mutually exclusive is definitely better than
broken codegen, ultimately we're going to need a way to combine them.
I suspect that placing the PACIASP before the NOPs is going to be problematic
unless it's done for all functions (including leaf functions), otherwise
hooking the NOPs at runtime is difficult because you can't tell whether or not
x30 is signed. You may end up needing to use BTI for the target instead.
The Clang folks are starting to look at -fpatchable-function-entry for AArch64
and will need to follow whatever you end up doing here.
>From gcc-bugs-return-662879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 10:32:17 2019
Return-Path: <gcc-bugs-return-662879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77967 invoked by alias); 10 Dec 2019 10:32: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 77864 invoked by uid 48); 10 Dec 2019 10:32:12 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92884] New: [SVE] Add support for chained extract-last reductions
Date: Tue, 10 Dec 2019 10:32: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: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92884-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00949.txt.bz2
Content-length: 1646
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92884
Bug ID: 92884
Summary: [SVE] Add support for chained extract-last reductions
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: rsandifo at gcc dot gnu.org
Target Milestone: ---
Extract-last (i.e. CLASTB) reductions can't yet handle chained
conditions, such as those seen in gcc.dg/vect/vect-cond-reduc-5.c.
We just fall back to the normal COND_REDUCTION handling instead.
If we have:
res_0 = PHI <res_n(latch), init(entry)>;
res_1 = COND_EXPR <cond_1, res_0, val_1>;
res_2 = COND_EXPR <cond_2, res_1, val_2>;
...
res_n = COND_EXPR <cond_n, res_{n-1}, val_n>;
one alternative would be (pseudo-code):
res_0 = PHI <res_n(latch), init(entry)>;
vec.res_1 = vec.val_1;
vec.res_2 = VEC_COND_EXPR <vec.cond_2, vec.res_1, vec.val_2>;
...
vec.res_n = VEC_COND_EXPR <vec.cond_n, vec.res_{n-1}, vec.val_n>;
vec.cond_any = IOR_EXPR <vec.cond_1, ..., vec.cond_n>;
res_n = .EXTRACT_LAST (res_0, vec.cond_any, vec.res_n);
Perhaps it would make sense to move the IFN_EXTRACT_LAST generation
from vectorizable_condition to vect_create_epilog_for_reduction.
All vectorizable_condition would need to do differently from
COND_REDUCTION is to handle the special case of:
vec.res_1 = vec.val_1;
instead of using a VEC_COND_EXPR between vec.val_1 and vec.res_0.
(res_0 isn't vectorised for EXTRACT_LAST_REDUCTION.)
>From gcc-bugs-return-662880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 10:32:48 2019
Return-Path: <gcc-bugs-return-662880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79109 invoked by alias); 10 Dec 2019 10:32: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 79027 invoked by uid 55); 10 Dec 2019 10:32:43 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92872] [10 Regression] ICE in build_fold_indirect_ref_loc, at fold-const.c:14842
Date: Tue, 10 Dec 2019 10:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92872-4-8rTLFPHEiX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92872-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92872-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00950.txt.bz2
Content-length: 663
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92872
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Tue Dec 10 10:32:12 2019
New Revision: 279160
URL: https://gcc.gnu.org/viewcvs?rev=279160&root=gcc&view=rev
Log:
Fortran] PR 92872 – Fix get_CFI_desc
PR fortran/92872
* trans-array.c (get_CFI_desc): Fix cond whether saved desc exists.
PR fortran/92872
* gfortran.dg/bind_c_optional-1.f90: New.
Added:
trunk/gcc/testsuite/gfortran.dg/bind_c_optional-1.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 10:38:54 2019
Return-Path: <gcc-bugs-return-662881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77110 invoked by alias); 10 Dec 2019 10:38: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 77064 invoked by uid 48); 10 Dec 2019 10:38:51 -0000
From: "sudi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92870] new test case gcc.dg/vect/vect-shift-5.c fails starting with its introduction in r279114
Date: Tue, 10 Dec 2019 10:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sudi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: sudi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to everconfirmed
Message-ID: <bug-92870-4-VRmakjqsrY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00951.txt.bz2
Content-length: 411
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92870
sudi at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |sudi at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-662882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 10:40:45 2019
Return-Path: <gcc-bugs-return-662882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79458 invoked by alias); 10 Dec 2019 10:40:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79368 invoked by uid 48); 10 Dec 2019 10:40:41 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92872] [10 Regression] ICE in build_fold_indirect_ref_loc, at fold-const.c:14842
Date: Tue, 10 Dec 2019 10: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: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92872-4-pw9Cn8k49L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92872-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92872-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00952.txt.bz2
Content-length: 1027
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92872
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #3)
> trunk/gcc/testsuite/gfortran.dg/bind_c_optional-1.f90
FIXED. Thanks for the report! You seems to have/create a nice test collection
which is very, very helpful to avoid issues in the release!
Note that due to PR 92189, your example only works at run time if the lower
bound starts at 0 – at least it seems to work by chance, if I allocated it with
lbound = 0 in the caller. (That's what I do in the added test case.)
(In reply to Martin Liška from comment #1)
> Confirmed, started with r276444.
Thanks for doing all those bug triages!
>From gcc-bugs-return-662883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 10:43:07 2019
Return-Path: <gcc-bugs-return-662883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98060 invoked by alias); 10 Dec 2019 10:43: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 92596 invoked by uid 48); 10 Dec 2019 10:43:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92883] [10 Regression] ICE in compare_values_warnv
Date: Tue, 10 Dec 2019 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
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: cf_gcctarget bug_status cf_reconfirmed_on cc cf_gcchost everconfirmed cf_gccbuild
Message-ID: <bug-92883-4-sSp6AFGd9y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92883-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92883-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00953.txt.bz2
Content-length: 1152
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92883
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|s390x-ibm-linux |
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
CC| |jakub at gcc dot gnu.org
Host|s390x-ibm-linux |
Ever confirmed|0 |1
Build|s390x-ibm-linux |
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Cleaned up testcase, ICEs at -O2 also on x86_64-linux:
int a, b, c, d;
unsigned e;
void baz (void *, int);
void grault (int, unsigned long);
int foo (unsigned g) { return a / g; }
void bar (void *g) { if (b) baz (g, 5); }
static void quux (int, unsigned long);
static void qux (unsigned long g) { if (g) { d = foo (-1); quux (e, (d & 2) +
g); } }
static void quux (int g, unsigned long m) { (void) g; grault (c, m); bar ("");
}
void corge () { qux (e); }
>From gcc-bugs-return-662884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 10:53:21 2019
Return-Path: <gcc-bugs-return-662884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13549 invoked by alias); 10 Dec 2019 10:53:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13280 invoked by uid 48); 10 Dec 2019 10:53:17 -0000
From: "sudi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92870] new test case gcc.dg/vect/vect-shift-5.c fails starting with its introduction in r279114
Date: Tue, 10 Dec 2019 10:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sudi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: sudi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92870-4-wXgInWJOjb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00954.txt.bz2
Content-length: 236
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92870
--- Comment #1 from sudi at gcc dot gnu.org ---
Ah I think I need a better effective target check. This test would only pass
for target that have a vector/scalar shift/rotate optab.
>From gcc-bugs-return-662885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 11:01:03 2019
Return-Path: <gcc-bugs-return-662885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54384 invoked by alias); 10 Dec 2019 11:01: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 54315 invoked by uid 48); 10 Dec 2019 11:00:58 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/92880] Documentation for Built-in Vector-Extensions should mention C99 Fixed-width ints as base types
Date: Tue, 10 Dec 2019 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-92880-4-1gyjOVul2f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92880-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00955.txt.bz2
Content-length: 860
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92880
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |documentation
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Mingye Wang from comment #0)
> Since a quick test seems to show that these types do in fact work,
Of course it does. As Andrew said, they're just typedefs.
> it would
> be a good idea to mention it in the documentation. This should, in theory,
> allow programmers to write truly platform-independent vectorized code.
Not really, because uint32_t is not guaranteed to be available on all
platforms.
uint_least32_t is more portable, but not guaranteed to have exactly 32 bits.
>From gcc-bugs-return-662886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 11:06:34 2019
Return-Path: <gcc-bugs-return-662886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72190 invoked by alias); 10 Dec 2019 11: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 72027 invoked by uid 48); 10 Dec 2019 11:06:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92883] [10 Regression] ICE in compare_values_warnv
Date: Tue, 10 Dec 2019 11: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:
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: target_milestone
Message-ID: <bug-92883-4-nvaDNBPDcs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92883-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92883-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00956.txt.bz2
Content-length: 1272
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92883
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The fix for the ICE is easy:
--- gcc/ipa-cp.c.jj 2019-12-06 00:40:40.000000000 +0100
+++ gcc/ipa-cp.c 2019-12-10 11:57:10.354999085 +0100
@@ -2400,7 +2400,7 @@ propagate_vr_across_jump_function (cgrap
NOP_EXPR,
param_type,
jfunc->m_vr->type ()))
- vr.intersect (*jfunc->m_vr);
+ vr.intersect (jvr);
}
return dest_lat->meet_with (&vr);
}
but what isn't quite obvious why the code ever tries to intersect the range [0,
0xffffffffUL] which I'd bet comes from corge passing unsigned int to an
unsigned long argument, and ~[0B, 0B] with char[1] * type which must come from
quux calling bar with "" argument which is certainly non-NULL. I mean, what do
those two ranges have in common?
>From gcc-bugs-return-662887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 11:16:34 2019
Return-Path: <gcc-bugs-return-662887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63681 invoked by alias); 10 Dec 2019 11:16: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 63610 invoked by uid 48); 10 Dec 2019 11:16:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92883] [10 Regression] ICE in compare_values_warnv
Date: Tue, 10 Dec 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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92883-4-NZbhIDlEMW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92883-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92883-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00957.txt.bz2
Content-length: 1294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92883
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jamborm at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Note, qux is passing through the argument to quux (after it has been determined
that d after early inlining has [0, 1] range and thus d & 2 is always 0):
# RANGE [0, 4294967295] NONZERO 4294967295
_2 = (long unsigned int) e.3_1;
qux (_2);
...
qux (long unsigned int g)
{
long unsigned int g_5(D) = g;
long unsigned int _1;
...
<bb 2> [local count: 1073741824]:
if (g_5(D) != 0)
goto <bb 3>; [33.00%]
...
# RANGE [1, 18446744073709551615]
_1 = g_5(D);
e.5_2 = e;
e.6_3 = (int) e.5_2;
quux (e.6_3, _1);
so I'd expect an intersection between the [0, 4294967295] range and
[1, 18446744073709551615], yielding [1, 4294967295], but instead it intersects
[0, 4294967295] with the pointer-ish unrelated ~[0B, 0B] where the effect is
actually the same. I think the #c3 patch is fairly obviously correct, but
there is still the question if there isn't something else broken too.
>From gcc-bugs-return-662888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 11:30:49 2019
Return-Path: <gcc-bugs-return-662888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117532 invoked by alias); 10 Dec 2019 11: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 117466 invoked by uid 48); 10 Dec 2019 11:30:26 -0000
From: "davidgkinniburgh at yahoo dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92885] New: ICE (segfault) with allocatable coarrays
Date: Tue, 10 Dec 2019 11:30: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: davidgkinniburgh at yahoo dot co.uk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92885-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00958.txt.bz2
Content-length: 1287
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92885
Bug ID: 92885
Summary: ICE (segfault) with allocatable coarrays
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: davidgkinniburgh at yahoo dot co.uk
Target Milestone: ---
Please can someone check this out? Compiles with ifort 19.0.5.281. Thanks.
program caf_alloc_gfortran_ice
! coarray program
! gfortran -c -Wall -fcoarray=single -O0 caf_alloc_gfortran_ice.f90
! Thread model: win32
! gcc version 9.2.0 (GCC) on Windows
IMPLICIT none
type string
character(:), allocatable :: s
end type string
type result
type(string), allocatable :: sp(:)
end type result
! coarray
type(result), allocatable :: results(:)[:]
! now allocate
allocate(results(2)[*])
end program caf_alloc_gfortran_ice
gives
21 | allocate(results(2)[*])
|
internal compiler error: Segmentation fault
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.
>From gcc-bugs-return-662889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 11:43:56 2019
Return-Path: <gcc-bugs-return-662889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19381 invoked by alias); 10 Dec 2019 11:43: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 19300 invoked by uid 48); 10 Dec 2019 11:43:51 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92883] [10 Regression] ICE in compare_values_warnv
Date: Tue, 10 Dec 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: 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: ASSIGNED
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
Message-ID: <bug-92883-4-N7YACbbcZr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92883-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92883-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00959.txt.bz2
Content-length: 1150
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92883
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
What I see is that the jfunc->m_vr originally pointed to the expected
long unsigned int [1, +INF]
value range.
But the hash table used to store the value ranges actually doesn't care about
type compatibility of different value ranges.
So I think we need additionally:
--- gcc/ipa-prop.c.jj 2019-12-06 01:26:39.000000000 +0100
+++ gcc/ipa-prop.c 2019-12-10 12:38:57.564926519 +0100
@@ -121,7 +121,7 @@ struct ipa_vr_ggc_hash_traits : public g
static bool
equal (const value_range *a, const value_range *b)
{
- return a->equal_p (*b);
+ return a->equal_p (*b) && types_compatible_p (a->type (), b->type ());
}
static void
mark_empty (value_range *&p)
because value_range equal_p really assumes that it is called with compatible
typed value ranges.
>From gcc-bugs-return-662890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 11:51:54 2019
Return-Path: <gcc-bugs-return-662890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27118 invoked by alias); 10 Dec 2019 11: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 27065 invoked by uid 48); 10 Dec 2019 11:51:50 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86373] Destructor shall not be instantiated in C++17 mode for prvalue
Date: Tue, 10 Dec 2019 11:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-86373-4-plrnAc1nGh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86373-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86373-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00960.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86373
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
Ever confirmed|0 |1
>From gcc-bugs-return-662891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 11:52:39 2019
Return-Path: <gcc-bugs-return-662891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28124 invoked by alias); 10 Dec 2019 11:52: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 28080 invoked by uid 48); 10 Dec 2019 11:52:35 -0000
From: "kakkoko at pushf dot jp" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92886] New: Inappropriate comment for std::ios_base::trunc
Date: Tue, 10 Dec 2019 11:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kakkoko at pushf dot 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-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: 2019-12/txt/msg00961.txt.bz2
Content-length: 1020
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92886
Bug ID: 92886
Summary: Inappropriate comment for std::ios_base::trunc
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: kakkoko at pushf dot jp
Target Milestone: ---
The comment attached to std::ios_base::trunc looks wrong.
libstdc++-v3/include/bits/ios_base.h:
/// Open for input. Default for @c ofstream.
static const openmode trunc = _S_trunc;
"Open for input"? Hmm... It looks copy-pasted from the comment on
std::ios_base::in...
/// Open for input. Default for @c ifstream and fstream.
static const openmode in = _S_in;
Proposal:
- /// Open for input. Default for @c ofstream.
+ /// Truncate to zero length after opening. Default for @c ofstream.
static const openmode trunc = _S_trunc;
>From gcc-bugs-return-662892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 11:54:36 2019
Return-Path: <gcc-bugs-return-662892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41581 invoked by alias); 10 Dec 2019 11:54: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 36523 invoked by uid 48); 10 Dec 2019 11:54:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89311] Brace initialization needlessly invokes destructor
Date: Tue, 10 Dec 2019 11:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-89311-4-sEf4G4ynxE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89311-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89311-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00962.txt.bz2
Content-length: 590
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89311
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is fixed on trunk and gcc-9-branch, by the patches for PR 85552, so I'm
closing it as a dup of that.
*** This bug has been marked as a duplicate of bug 85552 ***
>From gcc-bugs-return-662893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 11:54:37 2019
Return-Path: <gcc-bugs-return-662893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41835 invoked by alias); 10 Dec 2019 11:54: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 37055 invoked by uid 48); 10 Dec 2019 11:54:33 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85552] Adding curly braces to the declaration of a std::unique_ptr to a forward declared class breaks compilation
Date: Tue, 10 Dec 2019 11:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85552-4-Du7EgU6yFG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85552-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85552-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00963.txt.bz2
Content-length: 498
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85552
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |raphael.kubo.da.costa@intel
| |.com
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 89311 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-662894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 12:02:49 2019
Return-Path: <gcc-bugs-return-662894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86401 invoked by alias); 10 Dec 2019 12:02: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 86340 invoked by uid 48); 10 Dec 2019 12:02:45 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90282] internal compiler error: qsort checking failed in snapshot-20190429
Date: Tue, 10 Dec 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: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90282-4-hAXSO96PPy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00964.txt.bz2
Content-length: 325
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90282
--- Comment #5 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Andreas Schwab from comment #4)
> Workaround: use release checking.
Stupid question: How do I do that? Is there a switch that can be passed to the
configure script?
>From gcc-bugs-return-662895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 12:05:27 2019
Return-Path: <gcc-bugs-return-662895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92942 invoked by alias); 10 Dec 2019 12:05: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 92889 invoked by uid 48); 10 Dec 2019 12:05:23 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90282] internal compiler error: qsort checking failed in snapshot-20190429
Date: Tue, 10 Dec 2019 12:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90282-4-IbkQqvlRgu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00965.txt.bz2
Content-length: 443
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90282
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to John Paul Adrian Glaubitz from comment #5)
> (In reply to Andreas Schwab from comment #4)
> > Workaround: use release checking.
>
> Stupid question: How do I do that? Is there a switch that can be passed to
> the configure script?
-fno-checking, or -fchecking=0. I will take a look at the bug today.
>From gcc-bugs-return-662896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 12:09:06 2019
Return-Path: <gcc-bugs-return-662896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95552 invoked by alias); 10 Dec 2019 12:09: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 95463 invoked by uid 48); 10 Dec 2019 12:08:58 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90282] internal compiler error: qsort checking failed in snapshot-20190429
Date: Tue, 10 Dec 2019 12:09: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: glaubitz at physik dot fu-berlin.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90282-4-zXdDszPIUY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00966.txt.bz2
Content-length: 746
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90282
--- Comment #7 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Martin Liška from comment #6)
> (In reply to John Paul Adrian Glaubitz from comment #5)
> > (In reply to Andreas Schwab from comment #4)
> > > Workaround: use release checking.
> >
> > Stupid question: How do I do that? Is there a switch that can be passed to
> > the configure script?
>
> -fno-checking, or -fchecking=0. I will take a look at the bug today.
Okay. Thanks. Let me know if you need access to an Itanium box. To my shame, I
haven't managed to set up a GCC porterbox for ia64 yet which has been on my
TODO list for quite a while.
Hopefully early next year.
>From gcc-bugs-return-662897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 12:09:52 2019
Return-Path: <gcc-bugs-return-662897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97007 invoked by alias); 10 Dec 2019 12:09:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96521 invoked by uid 48); 10 Dec 2019 12:09:48 -0000
From: "nsz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92822] [10 Regression] testsuite failures on aarch64 after r278938
Date: Tue, 10 Dec 2019 12: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nsz at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92822-4-P2vQT2TQEF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00967.txt.bz2
Content-length: 1106
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92822
nsz at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nsz at gcc dot gnu.org
--- Comment #2 from nsz at gcc dot gnu.org ---
e.g.
#include <arm_neon.h>
float32x2_t
foo (float32x2_t v0, float32x4_t v1)
{
return vmulx_laneq_f32 (v0, v1, 0);
}
used to get translated to
foo:
fmulx v0.2s, v0.2s, v1.s[0]
ret
now it is
foo:
adrp x0, .LC0
ldr q2, [x0, #:lo12:.LC0]
tbl v1.16b, {v1.16b}, v2.16b
fmulx v0.2s, v0.2s, v1.2s
ret
.size foo, .-foo
.section .rodata.cst16,"aM",@progbits,16
.align 4
.LC0:
.byte 0
.byte 1
.byte 2
.byte 3
.byte 0
.byte 1
.byte 2
.byte 3
.byte 0
.byte 1
.byte 2
.byte 3
.byte 4
.byte 5
.byte 6
.byte 7
>From gcc-bugs-return-662898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 12:17:22 2019
Return-Path: <gcc-bugs-return-662898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115971 invoked by alias); 10 Dec 2019 12:17: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 115933 invoked by uid 48); 10 Dec 2019 12:17:18 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92835] [OpenACC] Run time error with enter./exit data
Date: Tue, 10 Dec 2019 12:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge 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-92835-4-xcJ33RDPnQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00968.txt.bz2
Content-length: 1140
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92835
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-12-10
CC| |tschwinge at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to Ron from comment #0)
> I am trying to compile and run my OpenACC code with GNU 9.1.0 branch.
>
> I am getting the following error:
Thanks for the report.
> libgomp: >>>> GOACC_enter_exit_data UNHANDLED kind 0x01
>
> What does this mean? My code works fine with PGI.
Huh, that's strange. That's the data mapping kind used for the OpenACC
'copyin' clause, which certainly I see handled in 'GOACC_enter_exit_data'. Can
you tell what your source code line is? You can run your code in GDB, with
'break gomp_fatal', and when this hits, then 'backtrace'.
>From gcc-bugs-return-662899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 12:20:43 2019
Return-Path: <gcc-bugs-return-662899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11148 invoked by alias); 10 Dec 2019 12:20: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 11088 invoked by uid 48); 10 Dec 2019 12:20:39 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92878] Parenthesized aggregate initialization doesn't work in a new-expression
Date: Tue, 10 Dec 2019 12:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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 cc assigned_to
Message-ID: <bug-92878-4-AXONUzNc6J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92878-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92878-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00969.txt.bz2
Content-length: 461
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92878
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |mpolacek at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
>From gcc-bugs-return-662900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 12:36:54 2019
Return-Path: <gcc-bugs-return-662900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86125 invoked by alias); 10 Dec 2019 12:36: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 86017 invoked by uid 48); 10 Dec 2019 12:36:49 -0000
From: "nsz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92822] [10 Regression] testsuite failures on aarch64 after r278938
Date: Tue, 10 Dec 2019 12:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nsz 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-92822-4-QiRb523EkJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00970.txt.bz2
Content-length: 525
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92822
--- Comment #3 from nsz at gcc dot gnu.org ---
it seems at least the following neon intrinsics are affected:
float32x2_t vmulx_laneq_f32 (float32x2_t, float32x4_t, const int);
float32x2_t vmul_laneq_f32 (float32x2_t, float32x4_t, const int);
float32x2_t vfma_laneq_f32 (float32x2_t, float32x2_t, float32x4_t, const int);
float32x2_t vfms_laneq_f32 (float32x2_t, float32x2_t, float32x4_t, const int);
float64x1_t vmul_laneq_f64 (float64x1_t, float64x2_t, const int);
>From gcc-bugs-return-662901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 12:42:57 2019
Return-Path: <gcc-bugs-return-662901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91516 invoked by alias); 10 Dec 2019 12:42: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 91446 invoked by uid 48); 10 Dec 2019 12:42:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92882] [10 Regression] ICE in regstat_bb_compute_calls_crossed, at regstat.c:327 since r279124
Date: Tue, 10 Dec 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: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92882-4-s6mXM4W5pm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92882-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92882-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00971.txt.bz2
Content-length: 2006
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92882
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> ---
Dunno if it isn't just workaround, but it makes absolutely no sense to
DF_INSN_INFO_GET on insns for which we really don't need it, such as debug
insns, CODE_LABEL etc. for which we never use insn_info and we just continue;.
Patch like below fixes the ICE for me.
The question is if we just have some exception that for new labels etc. we
don't grow the tables, while for insns we always do. If yes, the patch is a
real fix, if not, we can wait for further ICEs on the same assertion.
2019-12-10 Jakub Jelinek <jakub@redhat.com>
PR rtl-optimization/92882
* regstat.c (regstat_bb_compute_calls_crossed): Don't check
INSN_UID against DF_INSN_SIZE or use DF_INSN_INFO_GET unless
NONDEBUG_INSN_P.
* gfortran.dg/pr92882.f: New test.
--- gcc/regstat.c.jj 2019-12-09 15:02:30.112287863 +0100
+++ gcc/regstat.c 2019-12-10 13:36:23.231327649 +0100
@@ -324,13 +324,13 @@ regstat_bb_compute_calls_crossed (unsign
FOR_BB_INSNS_REVERSE (bb, insn)
{
+ if (!NONDEBUG_INSN_P (insn))
+ continue;
+
gcc_assert (INSN_UID (insn) < (int) DF_INSN_SIZE ());
struct df_insn_info *insn_info = DF_INSN_INFO_GET (insn);
unsigned int regno;
- if (!NONDEBUG_INSN_P (insn))
- continue;
-
/* Process the defs. */
if (CALL_P (insn))
{
--- gcc/testsuite/gfortran.dg/pr92882.f.jj 2019-12-10 13:38:17.737571868
+0100
+++ gcc/testsuite/gfortran.dg/pr92882.f 2019-12-10 13:38:07.453729553 +0100
@@ -0,0 +1,4 @@
+C PR rtl-optimization/92882
+C { dg-do compile }
+C { dg-options "-O2 -fno-inline" }
+ INCLUDE 'secnds.f'
>From gcc-bugs-return-662902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 12:50:33 2019
Return-Path: <gcc-bugs-return-662902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97994 invoked by alias); 10 Dec 2019 12:50:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97852 invoked by uid 48); 10 Dec 2019 12:50:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92869] [10 Regression] C++17 wrongly reports aggregate type as not-aggregate (when explicitly defaulted ctors are added)
Date: Tue, 10 Dec 2019 12:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: 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: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc target_milestone short_desc
Message-ID: <bug-92869-4-mJrE0cclPL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00972.txt.bz2
Content-length: 936
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92869
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |jason at gcc dot gnu.org
Target Milestone|--- |10.0
Summary|C++17 wrongly reports |[10 Regression] C++17
|aggregate type as |wrongly reports aggregate
|not-aggregate (when |type as not-aggregate (when
|explicitly defaulted ctors |explicitly defaulted ctors
|are added) |are added)
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The #c2 testcase is rejected since r278298 aka P1816R0 implementation.
>From gcc-bugs-return-662903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 12:54:15 2019
Return-Path: <gcc-bugs-return-662903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101828 invoked by alias); 10 Dec 2019 12:54: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 101762 invoked by uid 48); 10 Dec 2019 12:54:11 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92869] [10 Regression] C++17 wrongly reports aggregate type as not-aggregate (when explicitly defaulted ctors are added)
Date: Tue, 10 Dec 2019 12:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
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: 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-92869-4-iy26T8oozA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00973.txt.bz2
Content-length: 376
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92869
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And the
template <typename T, __SIZE_TYPE__ N>
struct A {
A() = default;
A(const A &) = default;
A(A &&) = default;
T arr[N];
};
int main()
{
if (!__is_aggregate (A<int,3>))
__builtin_abort ();
}
testcase reduced from #c0 too.
>From gcc-bugs-return-662905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 12:54:57 2019
Return-Path: <gcc-bugs-return-662905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103842 invoked by alias); 10 Dec 2019 12: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 103764 invoked by uid 55); 10 Dec 2019 12:54:53 -0000
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91790] ICE: verify_ssa failed (error: definition in block 2 follows the use)
Date: Tue, 10 Dec 2019 12:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, wrong-code
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:
Message-ID: <bug-91790-4-xCbYRUhPXq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91790-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91790-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00975.txt.bz2
Content-length: 1165
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91790
--- Comment #15 from Kewen Lin <linkw at gcc dot gnu.org> ---
Author: linkw
Date: Tue Dec 10 12:54:21 2019
New Revision: 279166
URL: https://gcc.gnu.org/viewcvs?rev=279166&root=gcc&view=rev
Log:
[PATCH] Fix PR91790 by considering different first_stmt_info for realign
As PR91790 exposed, when we have one slp node whose first_stmt_info_for_drptr
is different from first_stmt_info, it's possible that the first_stmt DR isn't
initialized yet before stmt SLP_TREE_SCALAR_STMTS[0] of slp node. So we
shouldn't use first_stmt_info for vect_setup_realignment, instead we can use
the one based on first_stmt_info_for_drptr DR with additional adjustment by
bumping the distance from first_stmt DR.
2019-12-10 Kewen Lin <linkw@gcc.gnu.org>
Backport from mainline
2019-11-27 Kewen Lin <linkw@gcc.gnu.org>
PR tree-optimization/91790
* gcc/tree-vect-stmts.c (vectorizable_load): Use the adjusted DR for
vect_setup_realignment when first_stmt_info is different from
first_stmt_info_for_drptr.
Modified:
branches/gcc-9-branch/gcc/ChangeLog
branches/gcc-9-branch/gcc/tree-vect-stmts.c
>From gcc-bugs-return-662904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 12:54:42 2019
Return-Path: <gcc-bugs-return-662904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102990 invoked by alias); 10 Dec 2019 12:54: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 102938 invoked by uid 48); 10 Dec 2019 12:54:39 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90282] internal compiler error: qsort checking failed in snapshot-20190429
Date: Tue, 10 Dec 2019 12:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90282-4-kh6GUxiEmj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00974.txt.bz2
Content-length: 145
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90282
--- Comment #8 from Andreas Schwab <schwab@linux-m68k.org> ---
--enable-checking=release
>From gcc-bugs-return-662906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:00:36 2019
Return-Path: <gcc-bugs-return-662906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123409 invoked by alias); 10 Dec 2019 13:00: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 122115 invoked by uid 48); 10 Dec 2019 13:00:32 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90282] internal compiler error: qsort checking failed in snapshot-20190429
Date: Tue, 10 Dec 2019 13:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-90282-4-0BkQeC2Wdp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00976.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90282
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-12-10
Ever confirmed|0 |1
--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
@John: Can you please attach a pre-processed source file (-E option). I should
be able to reproduce that then with a cross compiler.
>From gcc-bugs-return-662907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:03:43 2019
Return-Path: <gcc-bugs-return-662907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126146 invoked by alias); 10 Dec 2019 13: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 126046 invoked by uid 48); 10 Dec 2019 13:03:39 -0000
From: "igor.chorazewicz at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92869] [10 Regression] C++17 wrongly reports aggregate type as not-aggregate (when explicitly defaulted ctors are added)
Date: Tue, 10 Dec 2019 13:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: igor.chorazewicz at intel dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92869-4-BzoXB5cQPI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00977.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92869
--- Comment #5 from Igor Chorazewicz <igor.chorazewicz at intel dot com> ---
Ok, but P1816R0 talks about argument deduction - in my example I specify all
template arguments for A, so should this fail?
Moreover, for g++ 10 and g++ 9.2 even the following, non-template code fails
for -std=c++2a
struct A {
A() = default;
A(const A &) = default;
A(A &&) = default;
int arr[3];
};
int main()
{
A a = {{1,2,3}};
}
>From gcc-bugs-return-662908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:05:09 2019
Return-Path: <gcc-bugs-return-662908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130096 invoked by alias); 10 Dec 2019 13:05: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 129977 invoked by uid 48); 10 Dec 2019 13:05:01 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90282] internal compiler error: qsort checking failed in snapshot-20190429
Date: Tue, 10 Dec 2019 13:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de
X-Bugzilla-Status: 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-90282-4-2W4DApN2N8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00978.txt.bz2
Content-length: 612
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90282
--- Comment #10 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Martin Liška from comment #9)
> @John: Can you please attach a pre-processed source file (-E option). I
> should be able to reproduce that then with a cross compiler.
Is the output after "=== BEGIN GCC DUMP ===" in the logfile what you need?
> https://buildd.debian.org/status/fetch.php?pkg=gcc-snapshot&arch=ia64&ver=1%3A20191130-1&stamp=1575698799&raw=0
Otherwise, I'll generate the pre-processed source as requested.
>From gcc-bugs-return-662909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:11:59 2019
Return-Path: <gcc-bugs-return-662909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12902 invoked by alias); 10 Dec 2019 13:11: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 12818 invoked by uid 48); 10 Dec 2019 13:11:55 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92869] [10 Regression] C++17 wrongly reports aggregate type as not-aggregate (when explicitly defaulted ctors are added)
Date: Tue, 10 Dec 2019 13:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
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: 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-92869-4-pb8HfjS35H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00979.txt.bz2
Content-length: 368
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92869
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
#c5 is rejected with -std=c++2a starting with r263115 aka
http://wg21.link/p1008r1
So, I believe it is correct to reject this in C++20, but I think neither of
those papers have been a DR and so shouldn't affect C++17 or earlier
compilation modes.
>From gcc-bugs-return-662910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:12:27 2019
Return-Path: <gcc-bugs-return-662910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13931 invoked by alias); 10 Dec 2019 13:12: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 13873 invoked by uid 48); 10 Dec 2019 13:12:23 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92885] [8/9/10 Regression] ICE (segfault) with allocatable coarrays
Date: Tue, 10 Dec 2019 13:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone short_desc everconfirmed cf_known_to_fail
Message-ID: <bug-92885-4-FGjeupBwh3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92885-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92885-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00980.txt.bz2
Content-length: 1051
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92885
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
CC| |marxin at gcc dot gnu.org,
| |vehre at gcc dot gnu.org
Known to work| |6.5.0
Target Milestone|--- |8.4
Summary|ICE (segfault) with |[8/9/10 Regression] ICE
|allocatable coarrays |(segfault) with allocatable
| |coarrays
Ever confirmed|0 |1
Known to fail| |10.0, 7.4.0, 8.3.0, 9.2.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r243021.
>From gcc-bugs-return-662911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:28:09 2019
Return-Path: <gcc-bugs-return-662911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75296 invoked by alias); 10 Dec 2019 13: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 75183 invoked by uid 48); 10 Dec 2019 13:28:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92869] [10 Regression] C++17 wrongly reports aggregate type as not-aggregate (when explicitly defaulted ctors are added)
Date: Tue, 10 Dec 2019 13:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
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 assigned_to everconfirmed attachments.created
Message-ID: <bug-92869-4-LRTeh7xyXR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00981.txt.bz2
Content-length: 743
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92869
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-12-10
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47458
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47458&action=edit
gcc10-pr92869.patch
Thus, I think we want to do something like this. Untested so far.
>From gcc-bugs-return-662912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:30:57 2019
Return-Path: <gcc-bugs-return-662912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92953 invoked by alias); 10 Dec 2019 13:30:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85640 invoked by uid 48); 10 Dec 2019 13:30:51 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90282] internal compiler error: qsort checking failed in snapshot-20190429
Date: Tue, 10 Dec 2019 13:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-90282-4-ysOSDaE85W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00982.txt.bz2
Content-length: 1003
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90282
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #11 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to John Paul Adrian Glaubitz from comment #10)
> (In reply to Martin Liška from comment #9)
> > @John: Can you please attach a pre-processed source file (-E option). I
> > should be able to reproduce that then with a cross compiler.
>
> Is the output after "=== BEGIN GCC DUMP ===" in the logfile what you need?
>
> > https://buildd.debian.org/status/fetch.php?pkg=gcc-snapshot&arch=ia64&ver=1%3A20191130-1&stamp=1575698799&raw=0
>
> Otherwise, I'll generate the pre-processed source as requested.
Yes, the file is what I needed. However, I can't reproduce that with a cross
compiler.
>From gcc-bugs-return-662913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:31:52 2019
Return-Path: <gcc-bugs-return-662913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31740 invoked by alias); 10 Dec 2019 13:31: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 31690 invoked by uid 48); 10 Dec 2019 13:31:48 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90282] internal compiler error: qsort checking failed in snapshot-20190429
Date: Tue, 10 Dec 2019 13:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
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: attachments.created
Message-ID: <bug-90282-4-MAVGxH5q0d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00983.txt.bz2
Content-length: 235
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90282
--- Comment #12 from Martin Liška <marxin at gcc dot gnu.org> ---
Created attachment 47459
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47459&action=edit
test-case
>From gcc-bugs-return-662914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:40:25 2019
Return-Path: <gcc-bugs-return-662914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45898 invoked by alias); 10 Dec 2019 13: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 45853 invoked by uid 48); 10 Dec 2019 13:40:21 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92887] New: [F2008] Passing nullified/disassociated pointer or unalloc allocatable to OPTIONAL + VALUE dummy fails
Date: Tue, 10 Dec 2019 13:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92887-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00984.txt.bz2
Content-length: 1832
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92887
Bug ID: 92887
Summary: [F2008] Passing nullified/disassociated pointer or
unalloc allocatable to OPTIONAL + VALUE dummy fails
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
Target Milestone: ---
Cf. PR 44666, except that one this time has a VALUE in addition.
The following program segfaults at run time as 'aa' and 'pp' are dereferenced.
It should pass '0'* as absent argument plus false to the hidden _argument.
Cf. F2018, 15.5.2.12, Paragraph 1:
"A dummy argument […] is not present if the dummy argument […]
* does not have the ALLOCATABLE or POINTER attribute, and corresponds to an
actual argument that
– has the ALLOCATABLE attribute and is not allocated, or
– has the POINTER attribute and is disassociated;"
Cf. gfc_conv_procedure_call and search for:
/* For scalar arguments with VALUE attribute which are passed by
value, pass "0" and a hidden argument gives the optional
status. */
[* also CHARACTER or derived types are currently passed by value, but I think
they should be copied + passed by reference, cf. PR91196 and possibly
others. Likewise for arrays, but those are not yet supported with VALUE,
cf. PR 92702]
implicit none (type, external)
integer, allocatable :: aa
integer, pointer :: pp
nullify(pp)
call sub(aa, pp)
contains
subroutine sub(x, y)
integer, value, optional :: x, y
if (present(x)) stop 1
if (present(y)) stop 2
end subroutine sub
end
>From gcc-bugs-return-662916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:45:58 2019
Return-Path: <gcc-bugs-return-662916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69645 invoked by alias); 10 Dec 2019 13:45: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 69474 invoked by uid 48); 10 Dec 2019 13:45:54 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53947] [meta-bug] vectorizer missed-optimizations
Date: Tue, 10 Dec 2019 13:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: 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: bug_status resolution
Message-ID: <bug-53947-4-2w27hG1Flm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53947-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00986.txt.bz2
Content-length: 497
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 91790, which changed state.
Bug 91790 Summary: ICE: verify_ssa failed (error: definition in block 2 follows the use)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91790
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-662915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:45:58 2019
Return-Path: <gcc-bugs-return-662915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69546 invoked by alias); 10 Dec 2019 13:45:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69422 invoked by uid 48); 10 Dec 2019 13:45:53 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91790] ICE: verify_ssa failed (error: definition in block 2 follows the use)
Date: Tue, 10 Dec 2019 13:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91790-4-Mekah0avMY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91790-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91790-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00985.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91790
Arseny Solokha <asolokha at gmx dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #16 from Arseny Solokha <asolokha at gmx dot com> ---
Fixed on all affected branches by Kewen.
>From gcc-bugs-return-662917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:48:40 2019
Return-Path: <gcc-bugs-return-662917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101611 invoked by alias); 10 Dec 2019 13:48: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 90910 invoked by uid 48); 10 Dec 2019 13:48:23 -0000
From: "sudi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/92870] new test case gcc.dg/vect/vect-shift-5.c fails starting with its introduction in r279114
Date: Tue, 10 Dec 2019 13:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sudi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: sudi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92870-4-HiDM2a5CVT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00987.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92870
--- Comment #2 from sudi at gcc dot gnu.org ---
So I am sure how to get a list of targets that would support a particular
optab. I guess I can introduce a new effective target check with only the
targets that I know pass? Would that be ok?
>From gcc-bugs-return-662918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 13:55:45 2019
Return-Path: <gcc-bugs-return-662918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123378 invoked by alias); 10 Dec 2019 13:55: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 123315 invoked by uid 48); 10 Dec 2019 13:55:41 -0000
From: "matmal01 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92882] [10 Regression] ICE in regstat_bb_compute_calls_crossed, at regstat.c:327 since r279124
Date: Tue, 10 Dec 2019 13:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matmal01 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-92882-4-BjwjrpRGze@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92882-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92882-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00988.txt.bz2
Content-length: 1303
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92882
--- Comment #3 from Matthew Malcomson <matmal01 at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> The question is if we just have some exception that for new labels etc. we
> don't grow the tables, while for insns we always do. If yes, the patch is a
> real fix, if not, we can wait for further ICEs on the same assertion.
>
That's a good point.
At the time I proposed r279124 I decided that the comment inside
`df_recompute_luids` was enough of an indication that labels should be in the
tables, but another interpretation could be that we already know labels can be
outside of a table for some period of computation.
void
df_recompute_luids (basic_block bb)
{
rtx_insn *insn;
int luid = 0;
df_grow_insn_info ();
/* Scan the block an insn at a time from beginning to end. */
FOR_BB_INSNS (bb, insn)
{
struct df_insn_info *insn_info = DF_INSN_INFO_GET (insn);
/* Inserting labels does not always trigger the incremental
rescanning. */
if (!insn_info)
{
gcc_assert (!INSN_P (insn));
insn_info = df_insn_create_insn_record (insn);
}
DF_INSN_INFO_LUID (insn_info) = luid;
if (INSN_P (insn))
luid++;
}
}
>From gcc-bugs-return-662919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 14:11:04 2019
Return-Path: <gcc-bugs-return-662919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28465 invoked by alias); 10 Dec 2019 14:11: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 28364 invoked by uid 48); 10 Dec 2019 14:10:59 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86037] __PRETTY_FUNCTION__ for constexpr lambda's is missing [with = type]
Date: Tue, 10 Dec 2019 14:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-86037-4-WLLE4YhnSg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86037-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86037-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00989.txt.bz2
Content-length: 1054
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86037
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
CC| |jakub at gcc dot gnu.org,
| |jason at gcc dot gnu.org,
| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Bisection shows that the g++ 7 behavior mentioned above has been present before
r251433 where it started to be rejected (__PRETTY_FUNCTION__ was not declared),
then in r251567 started ICEing and finally with r258660 is accepted again, but
without the [with ...].
Unfortunately, due to the long time when it was ICEing, it is hard to narrow it
further.
>From gcc-bugs-return-662920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 14:14:37 2019
Return-Path: <gcc-bugs-return-662920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32333 invoked by alias); 10 Dec 2019 14:14: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 32226 invoked by uid 48); 10 Dec 2019 14:14:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87488] hyperlink filenames in diagnostics
Date: Tue, 10 Dec 2019 14: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: 9.0
X-Bugzilla-Keywords: diagnostic
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: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87488-4-MjZgoxTD5x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00990.txt.bz2
Content-length: 446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87488
--- Comment #22 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Indeed, RHEL5 (admittedly in extended lifecycle support only now) and RHEL6 use
old VTE though, dunno about the other long term support distros. Dunno what
are the probabilities users will use new GCC on those (but, it is enough if
they use such old distros on the desktop and just ssh to some other host
running new gcc).
>From gcc-bugs-return-662921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 14:25:27 2019
Return-Path: <gcc-bugs-return-662921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86198 invoked by alias); 10 Dec 2019 14:25: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 86133 invoked by uid 48); 10 Dec 2019 14:25:23 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92843] [OpenACC] Disallow 'acc_delete' etc. for everything without a dynamic reference count
Date: Tue, 10 Dec 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92843-4-52FeSgJ6Iv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00991.txt.bz2
Content-length: 2863
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92843
--- Comment #8 from jules at gcc dot gnu.org ---
(In reply to Thomas Schwinge from comment #7)
> We first need to establish a stable baseline, with test cases, and then (or,
> as part of that) merge the several independent pieces of the big "OpenACC
> reference count overhaul".
OK -- I think I misunderstood your strategy here, which is to avoid committing
that patch in one go. IMO (:-)) it's a clear improvement overall, particularly
with the consistency checking. Test coverage could probably be better -- but,
I'm sure many of the new tests introduced by the manual deep-copy patch would
not operate correctly without the refcounting fixes underneath (and the two
patches were all merged together to start with, of course).
> > The existing code was rewritten for a
> > reason -- that being, I hit various problems with it (albeit long since
> > forgotten) that interfered with the manual deep-copy implementation.
>
> So you'll have to dig out your notes, and/or we'll have to figure out any
> rationale again, now. Patches that change such fundamental things in
> libgomp we cannot just commit on the basis that once they made sense to
> somebody. They have to come with rationale, and test cases.
That's holding the new code to a rather higher standard than some of the
existing code! But, that's OK, I suppose. I will see if there are any notes I
made at the time that might be helpful.
> > We have
> > refcount self-checking code for the overhauled code.
>
> ... which surely can be adapted.
If you do that adaptation now, you might get a better idea of the state of the
current refcounting implementation! Not sure if that'll be helpful.
> And, per my understanding, this is only checking libgomp internal
> consistency, but not the semantics exposed to users via OpenACC
> directives/API calls etc., which in part you're changing of your patch
> (without test cases). This, again, I've spent the best part of the past
> weeks understanding, writing test cases for, filing GCC PRs, resolving them
> one by one, independently, incrementally, comprehensibly.
No, not just internal consistency. At least with the deep copy bits, there was
user-visible breakage with the existing code (again, IIRC).
> > We can address corner-case bug fixes as follow-ons once the main overhaul
> > patch is committed.
>
> Further bug fixes, yes, but we have to make some reasonable effort to not
> introduce new bugs with the big "OpenACC reference count overhaul" changes.
That's what the testsuite is for, I guess -- the burden of proof for getting
patches approved is lack of regressions in existing tests, generally. Yes there
could be more, but this is a real fundamental thing that most of the existing
OpenACC tests will touch in some way, so it's not *that* bad.
>From gcc-bugs-return-662922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 14:48:27 2019
Return-Path: <gcc-bugs-return-662922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55494 invoked by alias); 10 Dec 2019 14:48: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 55201 invoked by uid 48); 10 Dec 2019 14:48:02 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92843] [OpenACC] Disallow 'acc_delete' etc. for everything without a dynamic reference count
Date: Tue, 10 Dec 2019 14:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92843-4-42C4Rtpom0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00992.txt.bz2
Content-length: 2386
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92843
--- Comment #9 from jules at gcc dot gnu.org ---
FWIW, I wrote this at the time wrt. the refcounting changes (some parts refer
to a previous iteration of the manual deep copy patches)...
Writing a couple of new attach/detach tests, I realised that reference
counting for OpenACC was pretty seriously broken. In an attempt to fix
that, I've:
- written self-checking code to verify reference counts. This walks
over the whole memory-mapping splay tree and re-counts references,
making sure they match up with the running tallies kept by the
mapping/unmapping routines.
- removed the dubious "finalize" arguments from the unmap routines you
pointed out. Call "detach" in more appropriate places.
- rewritten gomp_acc_{insert,remove}_pointer, and change the way
"enter data" mapping works in OpenACC to be more like the
implementation for OpenMP (gomp_acc_remove_pointer is now modelled
on target.c:gomp_exit_data).
- ...which means we can get rid of the "acc_dev->openacc.data_environ"
list. I think I added that to start with (ICBW!) but now I don't
think we need it. That means we avoid a lot of scanning through
linear linked lists to find the "right" target_mem_desc to unmap --
which it turns out was buggy, and also probably conceptually wrong.
(In GOACC_enter_exit_data, that meant each mapping clause got its own
"target_mem_desc" when entering, which isn't how things normally work
for gomp_map_vars. That meant that when "exit data"ing, again
individual clauses could remove the corresponding target_mem_desc.
What *didn't* work is if the mappings for a single target_mem_desc
returned by GOACC_enter_exit_data refer to *other* target_mem_descs
in their argument lists, rather than pointing back to the same one. A
lot of the code that was checking "t->refcount" for "2" or "minrefs"
in oacc-mem.c was simply broken.)
- lookup_dev scans over the splay tree instead of looking through the
data_environ list. It should have done that to start with -- it
means it'll be able to find data mapped inside "pragma acc data"
blocks, which it wouldn't have been able to previously.
It's a lot of changes, but (I hope!) with the RC_CHECKING feature we'll
be able to be a little more confident that we've got the memory map
refcounting right, at least.
>From gcc-bugs-return-662923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 14:59:50 2019
Return-Path: <gcc-bugs-return-662923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88805 invoked by alias); 10 Dec 2019 14:59: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 88319 invoked by uid 48); 10 Dec 2019 14:59:41 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92560] ICE using decltype(x < y) when that operator uses operator<=>
Date: Tue, 10 Dec 2019 14:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
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: jason 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-92560-4-p9EZBokyar@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92560-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92560-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00993.txt.bz2
Content-length: 538
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92560
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
>From gcc-bugs-return-662924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 15:09:49 2019
Return-Path: <gcc-bugs-return-662924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127833 invoked by alias); 10 Dec 2019 15:09: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 127728 invoked by uid 48); 10 Dec 2019 15:09:44 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92888] New: [OpenACC] Failure to resolve back via 'acc_hostptr' an 'acc_deviceptr' retrieved for a '#pragma acc declare'd variable
Date: Tue, 10 Dec 2019 15:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc dependson target_milestone
Message-ID: <bug-92888-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00994.txt.bz2
Content-length: 1337
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92888
Bug ID: 92888
Summary: [OpenACC] Failure to resolve back via 'acc_hostptr' an
'acc_deviceptr' retrieved for a '#pragma acc declare'd
variable
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: openacc, patch
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: jakub at gcc dot gnu.org, jules at gcc dot gnu.org
Depends on: 92877
Target Milestone: ---
This currently fails:
double global_var;
#pragma acc declare create (global_var)
[...]
void *global_var_p_d = acc_deviceptr (&global_var);
assert (acc_hostptr (global_var_p_d) == &global_var);
Julian's got analysis and patch posted in
<https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92854#c6>.
There isn't something similar to 'acc_hostptr' ("returns the host pointer
associated with a specific device address") in OpenMP, I suppose?
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92877
[Bug 92877] [OpenACC] Failure to resolve back via 'acc_hostptr' an
'acc_deviceptr' retrieved for a structured mapping
>From gcc-bugs-return-662925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 15:14:54 2019
Return-Path: <gcc-bugs-return-662925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40211 invoked by alias); 10 Dec 2019 15:14:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40108 invoked by uid 48); 10 Dec 2019 15:14:49 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92888] [OpenACC] Failure to resolve back via 'acc_hostptr' an 'acc_deviceptr' retrieved for a '#pragma acc declare'd variable
Date: Tue, 10 Dec 2019 15:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92888-4-Jy3vELrq19@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92888-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92888-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00995.txt.bz2
Content-length: 265
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92888
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Created attachment 47460
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47460&action=edit
'libgomp.oacc-c-c++-common/pr92888-1.c'
>From gcc-bugs-return-662926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 15:23:46 2019
Return-Path: <gcc-bugs-return-662926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68368 invoked by alias); 10 Dec 2019 15:23: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 68303 invoked by uid 48); 10 Dec 2019 15:23:42 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92878] Parenthesized aggregate initialization doesn't work in a new-expression
Date: Tue, 10 Dec 2019 15: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: 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:
Message-ID: <bug-92878-4-khQHA04r3V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92878-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92878-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00996.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92878
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I guess this example should be compiled:
A new-expression that creates an object of type T initializes that object as
follows:
...
-- Otherwise, the new-initializer is interpreted according to the
initialization rules of [dcl.init] for direct-initialization.
=> do dcl.init#17.6.2.2.
>From gcc-bugs-return-662927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 15:25:04 2019
Return-Path: <gcc-bugs-return-662927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69963 invoked by alias); 10 Dec 2019 15: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 69673 invoked by uid 48); 10 Dec 2019 15:25:00 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92745] [8/9/10 Regression] Initializing array with vec4 results in compile error
Date: Tue, 10 Dec 2019 15:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: 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-92745-4-Tp1Uq40ZbZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00997.txt.bz2
Content-length: 384
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92745
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
>From gcc-bugs-return-662928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 15:27:11 2019
Return-Path: <gcc-bugs-return-662928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75013 invoked by alias); 10 Dec 2019 15:27:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74951 invoked by uid 48); 10 Dec 2019 15:27:07 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92854] [OpenACC] Always-true conditional in 'libgomp/oacc-mem.c:acc_unmap_data'?
Date: Tue, 10 Dec 2019 15:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jules at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92854-4-Y7J6z7iINT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00998.txt.bz2
Content-length: 526
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92854
--- Comment #7 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to jules from comment #6)
> This patch fixes the acc_map_data-device_already-3.c problem, which I guess
> has probably been broken forever. [...]
..., hence not a priority to get that fixed now. Thanks for the initial
analysis and WIP patch! We now understand the issue, so I'll commit my test
case XFAILed. I filed PR92888 for tracking this problem, so please move
discussion there.
>From gcc-bugs-return-662929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 15:29:50 2019
Return-Path: <gcc-bugs-return-662929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83032 invoked by alias); 10 Dec 2019 15: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 82993 invoked by uid 48); 10 Dec 2019 15:29:46 -0000
From: "drucker.nir at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92889] New: GCC-8 considers the _mm_gf2p8affine_epi64_epi8 intrinsic to be symmetric
Date: Tue, 10 Dec 2019 15:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: drucker.nir 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-92889-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg00999.txt.bz2
Content-length: 1504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92889
Bug ID: 92889
Summary: GCC-8 considers the _mm_gf2p8affine_epi64_epi8
intrinsic to be symmetric
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: drucker.nir at gmail dot com
Target Milestone: ---
Created attachment 47461
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47461&action=edit
Source file for reproducing the bug
GCC version: gcc-8 (Ubuntu 8.3.0-6ubuntu1~18.04.1) 8.3.0
Platform: Dell XPS 13 7390 2-in-1 with the 10th Intel(C) Core^TM Generation
(Micro architecture Codename ``Ice Lake''[ICL]) Intel(c) Core^TM i7-1065G7 CPU
1.30GHz.
The source file gfni_bug.c is a stand-alone file for reproducing the bug.
The file prints two vectors that are not supposed to be equal.
To compile use:
Correct compilation: gcc-8 -O3 -march=native gfni_bug.c -DGOOD_TEST=1
Bad compilation: gcc-8 -O3 -march=native gfni_bug.c
The problem is with the new _mm_gf2p8affine_epi64_epi8 (x86_64 GF-NI)
intrinsic.
When calling
OUT = _mm_gf2p8affine_epi64_epi8(A,B,0)
gcc-8 translates it to assembler in two different ways:
1) vgf2p8affineqb $0x0, A, B, OUT //Good
2) vgf2p8affineqb $0x0, B, A, OUT //Bad
Where only one of these can be correct because the operation is not symmetric.
Thanks,
Nir Drucker
>From gcc-bugs-return-662930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 15:34:19 2019
Return-Path: <gcc-bugs-return-662930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88754 invoked by alias); 10 Dec 2019 15:34: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 88664 invoked by uid 48); 10 Dec 2019 15:34:14 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92723] [10 Regression] ICE in expand_shift_1, at expmed.c:2635
Date: Tue, 10 Dec 2019 15:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
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: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-92723-4-zMm1otvcKZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01000.txt.bz2
Content-length: 654
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92723
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> ---
Hand-reduced:
void
foo (unsigned long long *x, unsigned long long *y, int z)
{
int i;
for (i = 0; i < 1024; i++)
x[i] = (y[i] >> z) | (y[i] << (-z & (__SIZEOF_LONG_LONG__ * __CHAR_BIT__ -
1)));
}
>From gcc-bugs-return-662931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 15:43:35 2019
Return-Path: <gcc-bugs-return-662931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52553 invoked by alias); 10 Dec 2019 15:43: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 52502 invoked by uid 48); 10 Dec 2019 15:43:31 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92723] [10 Regression] ICE in expand_shift_1, at expmed.c:2635
Date: Tue, 10 Dec 2019 15:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 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: 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-92723-4-b2uqQ4TeH9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01001.txt.bz2
Content-length: 254
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92723
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47462
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47462&action=edit
gcc10-pr92723.patch
Untested fix.
>From gcc-bugs-return-662932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 15:55:24 2019
Return-Path: <gcc-bugs-return-662932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122858 invoked by alias); 10 Dec 2019 15: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 121271 invoked by uid 48); 10 Dec 2019 15:55:19 -0000
From: "mkuvyrkov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)
Date: Tue, 10 Dec 2019 15:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: EH, ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mkuvyrkov at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92007-4-wrpUUsynkB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01002.txt.bz2
Content-length: 2028
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007
--- Comment #28 from Maxim Kuvyrkov <mkuvyrkov at gcc dot gnu.org> ---
(In reply to Ilya Leoshkevich from comment #27)
> With
>
> -DSPEC_CPU -DNDEBUG -DPERL_CORE -O3 -save-temps=obj
> -fopt-info-vec-optimized -DSPEC_CPU_LP64 -DSPEC_CPU_LINUX_X64
> -fgnu89-inline
>
> on gcc113 I can see 2% slowdown:
>
> r277511 (without this fix): 880.09s
> r277515 (with this fix): 897.85s
>
> The function that degraded the most is indeed S_regmatch:
>
> $ perf diff perf-9760321.data perf-44b2b4c.data
> 32.24% exe [.] S_regmatch
>
> 8.92% exe [.] S_find_byclass.isra.0
>
> 6.80% +0.28% libc-2.19.so [.] 0x000000000007dec0
>
> 5.20% exe [.] S_regtry
>
>
> However, the "shape" of S_regmatch did not change, that is, when all
> offsets and register numbers are replaced with "x" in the objdump
> output, the old and the new versions are identical. This hints at some
> microarchitectural effect - aliasing in the branch predictor maybe?
>
> From my perspective, this happens too often, so I use the following test
> to rule this out: just add a nop at the beginning of the problematic
> function. This changes all the offsets and makes aliasing situation
> completely different. And indeed, by adding a single nop to S_regmatch,
> I get wildly different results (for now this is just 1 repeat, I will
> run best-of-3 overnight):
>
> r277511 (without this fix): 929.1s
> r277515 (with this fix): 931.48s
Hi Ilya,
Thanks for the analysis. Doesn't seem like we can do anything useful about
this regression.
[For completeness, I see same 5% slowdown with "-O3 -funroll-loops" as with
plain -O3 on Cortex-A57.]
>From gcc-bugs-return-662933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 15:59:11 2019
Return-Path: <gcc-bugs-return-662933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41238 invoked by alias); 10 Dec 2019 15:59: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 41167 invoked by uid 48); 10 Dec 2019 15:59:07 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92878] Parenthesized aggregate initialization doesn't work in a new-expression
Date: Tue, 10 Dec 2019 15:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 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-92878-4-9FN9oMWv3S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92878-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92878-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01003.txt.bz2
Content-length: 2616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92878
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I've found an ICE:
struct A
{
int a;
int b;
int c = 42;
};
void
fn ()
{
auto y = new A(1, 2);
}
$ ./cc1plus -quiet i.C -std=c++2a
In function ‘void fn()’:
cc1plus: internal compiler error: in gimplify_init_constructor, at
gimplify.c:5195
0x1040e1b gimplify_init_constructor
/home/mpolacek/src/gcc/gcc/gimplify.c:5195
0x1041432 gimplify_modify_expr_rhs
/home/mpolacek/src/gcc/gcc/gimplify.c:5357
0x104257c gimplify_modify_expr
/home/mpolacek/src/gcc/gcc/gimplify.c:5708
0x106868a gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
/home/mpolacek/src/gcc/gcc/gimplify.c:13368
0x1046a72 gimplify_stmt(tree_node**, gimple**)
/home/mpolacek/src/gcc/gcc/gimplify.c:6810
0x1031946 gimplify_and_add(tree_node*, gimple**)
/home/mpolacek/src/gcc/gcc/gimplify.c:482
0x1069c9b gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
/home/mpolacek/src/gcc/gcc/gimplify.c:13719
0x1046a72 gimplify_stmt(tree_node**, gimple**)
/home/mpolacek/src/gcc/gcc/gimplify.c:6810
0x1043c32 gimplify_compound_expr
/home/mpolacek/src/gcc/gcc/gimplify.c:6012
0x10413ee gimplify_modify_expr_rhs
/home/mpolacek/src/gcc/gcc/gimplify.c:5345
0x104257c gimplify_modify_expr
/home/mpolacek/src/gcc/gcc/gimplify.c:5708
0x106868a gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
/home/mpolacek/src/gcc/gcc/gimplify.c:13368
0x1046a72 gimplify_stmt(tree_node**, gimple**)
/home/mpolacek/src/gcc/gcc/gimplify.c:6810
0x1045fa6 gimplify_cleanup_point_expr
/home/mpolacek/src/gcc/gcc/gimplify.c:6552
0x106a117 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
/home/mpolacek/src/gcc/gcc/gimplify.c:13760
0x1046a72 gimplify_stmt(tree_node**, gimple**)
/home/mpolacek/src/gcc/gcc/gimplify.c:6810
0x1035e44 gimplify_statement_list
/home/mpolacek/src/gcc/gcc/gimplify.c:1857
0x106a4c4 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
/home/mpolacek/src/gcc/gcc/gimplify.c:13812
0x1046a72 gimplify_stmt(tree_node**, gimple**)
/home/mpolacek/src/gcc/gcc/gimplify.c:6810
0x10344f3 gimplify_bind_expr
/home/mpolacek/src/gcc/gcc/gimplify.c:1420
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-662934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:04:31 2019
Return-Path: <gcc-bugs-return-662934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46718 invoked by alias); 10 Dec 2019 16: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 46661 invoked by uid 48); 10 Dec 2019 16:04:26 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92879] [10 Regression] incorrect warning of __builtin_memset offset is out of the bounds on zero-size allocation and initialization
Date: Tue, 10 Dec 2019 16: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: alias, 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords blocked
Message-ID: <bug-92879-4-vq9AbfIKSc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01004.txt.bz2
Content-length: 1891
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92879
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |alias
Blocks| |56456
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
The warning sees the IL below so it's doing the right thing. GCC doesn't
"know" that operator new doesn't clobber this->m so it doesn't eliminate the
for loop. Rewriting the loop like so avoids the warning and results in optimal
code equivalent to that emitted by Clang:
for(int j=0;j<i;j++) new(p+j)int();
Unlike in LP64 where the range of the size argument to memset is [4,
8589934588], in ILP32 its range is VARYING (a 32-bit int converted to a 32-bit
unsigned), so the warning isn't issued.
Since in a ctor, the this pointer can be assumed not to have escaped (unless
proven otherwise from its body), I think the root cause is a limitation of the
aliasing machinery.
_GLOBAL__sub_I_a ()
{
int i;
int _2;
void * _5;
sizetype _6;
sizetype _7;
unsigned int _12;
unsigned int _20;
sizetype _21;
<bb 2> [local count: 1073741824]:
MEM[(struct &)&a] ={v} {CLOBBER};
a.m = 0;
_5 = operator new [] (0);
a.p = _5;
_2 = a.m; <<< unnecessary: _2 must be 0
if (_2 <= 0)
goto <bb 4>; [11.00%]
else
goto <bb 3>; [89.00%]
<bb 3> [local count: 955630224]:
_20 = (unsigned int) _2;
_12 = _20 + 4294967295;
_6 = (sizetype) _12;
_21 = (sizetype) _2;
_7 = _21 * 4;
__builtin_memset (_5, 0, _7);
<bb 4> [local count: 1073741833]:
return;
}
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456
[Bug 56456] [meta-bug] bogus/missing -Warray-bounds
>From gcc-bugs-return-662935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:06:20 2019
Return-Path: <gcc-bugs-return-662935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57161 invoked by alias); 10 Dec 2019 16:06: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 57085 invoked by uid 48); 10 Dec 2019 16:06:15 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92878] Parenthesized aggregate initialization doesn't work in a new-expression
Date: Tue, 10 Dec 2019 16: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: 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-92878-4-NBodaC2lDU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92878-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92878-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01005.txt.bz2
Content-length: 159
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92878
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Nevermind, I had some local changes.
>From gcc-bugs-return-662936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:09:00 2019
Return-Path: <gcc-bugs-return-662936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59767 invoked by alias); 10 Dec 2019 16: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 59679 invoked by uid 48); 10 Dec 2019 16:08:56 -0000
From: "iii at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92007] [9/10 Regression] ICE: verify_flow_info failed (error: EH edge crosses section boundary in bb 7)
Date: Tue, 10 Dec 2019 16:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: EH, ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iii at linux dot ibm.com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92007-4-y2LD6ugg6i@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01006.txt.bz2
Content-length: 543
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92007
--- Comment #29 from Ilya Leoshkevich <iii at linux dot ibm.com> ---
Created attachment 47463
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47463&action=edit
nop plugin
Hi Maxim,
Just to clear my conscience, could you please try the nop trick in your
setup? I normally use the attached plugin for that. Just build it and
add e.g.
-fplugin=$HOME/gcc-nop-plugin/libgcc_nop_plugin.so
-fplugin-arg-libgcc_nop_plugin-S_regmatch=4
to the compiler flags.
Best regards,
Ilya
>From gcc-bugs-return-662937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:11:12 2019
Return-Path: <gcc-bugs-return-662937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61954 invoked by alias); 10 Dec 2019 16:11: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 61867 invoked by uid 48); 10 Dec 2019 16:11:08 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90282] internal compiler error: qsort checking failed in snapshot-20190429
Date: Tue, 10 Dec 2019 16:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
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: cc
Message-ID: <bug-90282-4-oj9VAoQ4bC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90282-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01007.txt.bz2
Content-length: 592
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90282
Arseny Solokha <asolokha at gmx dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |asolokha at gmx dot com
--- Comment #13 from Arseny Solokha <asolokha at gmx dot com> ---
This one should block PR82407.
Citing Jakub from PR84345 comment 2:
> Isn't this dup of the many other qsort checking issues in the scheduler?
> The scheduler qsort comparator is not valid comparator in many ways.
>From gcc-bugs-return-662938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:13:35 2019
Return-Path: <gcc-bugs-return-662938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81772 invoked by alias); 10 Dec 2019 16:13: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 81714 invoked by uid 55); 10 Dec 2019 16:13:30 -0000
From: "frederik at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBmb3J0cmFuLzkyNzkzXSBGb3J0cmFuIExvY2F0aW9uIERhdGEgZm9y?= =?UTF-8?B?IERpYWdub3N0aWMgbGFja3MgdGhlIGNvbHVtbiBudW1iZXIg4oCTIHdoZW4g?= =?UTF-8?B?cGFzc2luZyBvbiB0byBNRQ==?Date: Tue, 10 Dec 2019 16:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frederik 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-92793-4-KSLnRam90w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92793-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01008.txt.bz2
Content-length: 842
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92793
--- Comment #4 from Frederik Harwath <frederik at gcc dot gnu.org> ---
Author: frederik
Date: Tue Dec 10 16:12:58 2019
New Revision: 279169
URL: https://gcc.gnu.org/viewcvs?rev=279169&root=gcc&view=rev
Log:
Add tests to verify OpenACC clause locations
Check that the column information for OpenACC clauses is communicated correctly
to the middle-end, in particular by the Fortran front-end (cf. PR 92793).
2019-12-10 Frederik Harwath <frederik@codesourcery.com>
gcc/testsuite/
* c-c++-common/goacc/clause-locations.c: New test.
* gfortran.dg/goacc/clause-locations.f90: New test.
Added:
trunk/gcc/testsuite/c-c++-common/goacc/clause-locations.c
trunk/gcc/testsuite/gfortran.dg/goacc/clause-locations.f90
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:14:34 2019
Return-Path: <gcc-bugs-return-662939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83227 invoked by alias); 10 Dec 2019 16:14: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 83158 invoked by uid 48); 10 Dec 2019 16:14:25 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92879] [10 Regression] incorrect warning of __builtin_memset offset is out of the bounds on zero-size allocation and initialization
Date: Tue, 10 Dec 2019 16: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: alias, 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92879-4-8enyQsPb0Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01009.txt.bz2
Content-length: 396
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92879
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
After some more thought I think I need to correct myself: I suppose even in a
ctor the this pointer might need to be treated as having escaped and be
accessible to a replacement operator new, but placement new is not replaceable
so it can't access such an escaped pointer.
>From gcc-bugs-return-662940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:14:47 2019
Return-Path: <gcc-bugs-return-662940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84143 invoked by alias); 10 Dec 2019 16:14: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 84089 invoked by uid 48); 10 Dec 2019 16:14:43 -0000
From: "nknikita at niisi dot ras.ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92890] New: Member name lookup
Date: Tue, 10 Dec 2019 16:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nknikita at niisi dot ras.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-92890-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01010.txt.bz2
Content-length: 2121
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92890
Bug ID: 92890
Summary: Member name lookup
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nknikita at niisi dot ras.ru
Target Milestone: ---
An example from ISO/IEC 14882:2017 (E) [class.member.lookup]/7:
struct A { int x; }; // S(x,A) = {{A::x},{A}}
struct B { float x; }; // S(x,B) = {{B::x},{B}}
struct C: public A, public B {}; // S(x,C) = {{invalid}, {A in C, B in
C}}
struct D: public virtual C {}; // S(x,D) = S(x,C)
struct E: public virtual C { char x; }; // S(x,E) = {{E::x},{E}}
struct F: public D, public E {}; // S(x,F) = S(x,E)
int main ()
{
F f;
f.x = 0; // OK, lookup finds E::x
}
g++ is unable to compile it. I don't know if this error or not, but the example
can be compiled with clang++ (> 3.8.0) and vc++. The example is still present
in N4842.
>From gcc-bugs-return-662941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:27:33 2019
Return-Path: <gcc-bugs-return-662941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110690 invoked by alias); 10 Dec 2019 16:27:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110612 invoked by uid 48); 10 Dec 2019 16:27:29 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92891] New: ice in decompose, at wide-int.h:984
Date: Tue, 10 Dec 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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-92891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01011.txt.bz2
Content-length: 1612
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92891
Bug ID: 92891
Summary: ice in decompose, at wide-int.h:984
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 47464
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47464&action=edit
C source code
The attached C code, with recent gcc trunk and compiler flag -O2,
does this:
during GIMPLE pass: strlen
iplookup.c: In function ‘iplookup_router_entry’:
iplookup.c:148:1: internal compiler error: in decompose, at wide-int.h:984
0x5da4cc wi::int_traits<generic_wide_int<wide_int_storage> >::decompose(long*,
u
nsigned int, generic_wide_int<wide_int_storage> const&)
../../trunk/gcc/wide-int.h:984
0x949225 wi::int_traits<generic_wide_int<wide_int_storage> >::decompose(long*,
u
nsigned int, generic_wide_int<wide_int_storage> const&)
../../trunk/gcc/wide-int.h:1931
0x949225 wide_int_ref_storage<true,
false>::wide_int_ref_storage<generic_wide_in
t<wide_int_storage> >(generic_wide_int<wide_int_storage> const&, unsigned int)
../../trunk/gcc/wide-int.h:1034
0x949225 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)
The problem first seems to occur sometime between revision 278950
and 279000.
Reducing the code now.
>From gcc-bugs-return-662942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:38:21 2019
Return-Path: <gcc-bugs-return-662942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34537 invoked by alias); 10 Dec 2019 16:38: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 34458 invoked by uid 48); 10 Dec 2019 16:38:17 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92889] GCC-8 considers the _mm_gf2p8affine_epi64_epi8 intrinsic to be symmetric
Date: Tue, 10 Dec 2019 16: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.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92889-4-o7wrxb3nKb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92889-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92889-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01012.txt.bz2
Content-length: 815
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92889
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
CC| |jakub at gcc dot gnu.org,
| |jbeulich at suse dot com
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I believe this has been fixed already for GCC10+ in r272783, so just that
change needs to be backported to GCC9 and GCC8.
https://gcc.gnu.org/ml/gcc-patches/2019-06/msg01833.html
CCing patch author.
>From gcc-bugs-return-662943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:38:31 2019
Return-Path: <gcc-bugs-return-662943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35240 invoked by alias); 10 Dec 2019 16:38: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 35185 invoked by uid 48); 10 Dec 2019 16:38:27 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92890] Member name lookup
Date: Tue, 10 Dec 2019 16: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: 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: bug_status resolution
Message-ID: <bug-92890-4-ZMIMuxYEnC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92890-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92890-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01013.txt.bz2
Content-length: 488
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92890
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 bug has been marked as a duplicate of bug 77725 ***
>From gcc-bugs-return-662944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:38:31 2019
Return-Path: <gcc-bugs-return-662944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35365 invoked by alias); 10 Dec 2019 16: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 35198 invoked by uid 48); 10 Dec 2019 16:38:27 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/77725] An example from the standard regarding member lookup fails to compile
Date: Tue, 10 Dec 2019 16: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: 6.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-77725-4-g9ZQZ2sRNJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77725-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77725-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01014.txt.bz2
Content-length: 447
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77725
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nknikita at niisi dot ras.ru
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 92890 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-662945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:39:30 2019
Return-Path: <gcc-bugs-return-662945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37191 invoked by alias); 10 Dec 2019 16:39: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 37142 invoked by uid 48); 10 Dec 2019 16:39:27 -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: Tue, 10 Dec 2019 16: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: unknown
X-Bugzilla-Keywords:
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-92886-4-c9Gbzoi34G@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: 2019-12/txt/msg01015.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92886
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
Ever confirmed|0 |1
>From gcc-bugs-return-662946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:43:42 2019
Return-Path: <gcc-bugs-return-662946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42505 invoked by alias); 10 Dec 2019 16:43: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 42410 invoked by uid 48); 10 Dec 2019 16:43:36 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59655] incorrect diagnostic on templatized function with lambda parameter
Date: Tue, 10 Dec 2019 16:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: diagnostic, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on
Message-ID: <bug-59655-4-41ZTKTRrDC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01016.txt.bz2
Content-length: 1558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59655
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2019-03-08 00:00:00 |2019-12-10
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is now blocking the implementation of std::ranges algorithms, because this
error is given for types that are only used in concept satisfaction (and never
actually odr-used):
#include <iterator>
template<typename T,
std::indirect_unary_predicate<std::projected<T*, std::identity>> Pred>
constexpr void
all_of(T*, Pred)
{ }
void
test01()
{
struct X { };
X x;
all_of(&x, [](X&) { return false; });
}
Compiled with -std=gnu++2a and current trunk:
In file included from
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_iterator_base_types.h:71,
from /home/jwakely/gcc/10/include/c++/10.0.0/iterator:61,
from proj.cc:1:
/home/jwakely/gcc/10/include/c++/10.0.0/bits/iterator_concepts.h:669:40: error:
'std::indirect_result_t<_Proj&, _Iter> std::projected<_Iter,
_Proj>::operator*() const [with _Iter = test01()::X*; _Proj = std::identity;
std::indirect_result_t<_Proj&, _Iter> = test01()::X&]', declared using local
type 'test01()::X', is used but never defined [-fpermissive]
669 | indirect_result_t<_Proj&, _Iter> operator*() const; // not
defined
| ^~~~~~~~
>From gcc-bugs-return-662947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:47:43 2019
Return-Path: <gcc-bugs-return-662947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62642 invoked by alias); 10 Dec 2019 16:47: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 61891 invoked by uid 48); 10 Dec 2019 16:47:38 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92891] ice in decompose, at wide-int.h:984
Date: Tue, 10 Dec 2019 16:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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-92891-4-XHL6M7Xs70@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01017.txt.bz2
Content-length: 291
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92891
--- Comment #1 from David Binderman <dcb314 at hotmail dot com> ---
Reduced C code:
int a, b;
int *c() __attribute__((alloc_size(1)));
void d() {
char *e = c(1);
while (a) {
if (b <= 0)
continue;
e[b] = 0;
}
}
>From gcc-bugs-return-662948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:49:03 2019
Return-Path: <gcc-bugs-return-662948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65329 invoked by alias); 10 Dec 2019 16:49: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 65271 invoked by uid 48); 10 Dec 2019 16:48:59 -0000
From: "dpochepk at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92892] New: [AARCH64] TBL-based permutations can be implemented more efficiently for 2-element vectors
Date: Tue, 10 Dec 2019 16:49: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: dpochepk 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-92892-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01018.txt.bz2
Content-length: 1185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92892
Bug ID: 92892
Summary: [AARCH64] TBL-based permutations can be implemented
more efficiently for 2-element vectors
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: dpochepk at gmail dot com
Target Milestone: ---
Current vector elements permutation implementation generates different
instructions depending on specific permutation form. For permutations like:
"target[0] = src1[0]; target[1] = src2[1];" the TBL instruction is used and
following instructions sequence is generated:
mov tmpReg1, src1;
mov tmpReg2, src2;
tbl target, {tmpReg1, tmpReg2}, ...
// the tmpReg1 and tmpReg2 registers which are numbered consecutively, as
required by tbl instruction
For 2-element vectors this sequence can be reduced to:
mov target[0], src1[0]
mov target[1], src2[1]
And it can be reduced to a single mov in case target = src, which is already
implemented in patch prototype I'm working on.
>From gcc-bugs-return-662949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 16:51:19 2019
Return-Path: <gcc-bugs-return-662949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67871 invoked by alias); 10 Dec 2019 16:51: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 67785 invoked by uid 48); 10 Dec 2019 16:51:14 -0000
From: "sbergman at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92893] New: Unhelpful -Wstringop-overflow warning
Date: Tue, 10 Dec 2019 16:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sbergman 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: ---
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-92893-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01019.txt.bz2
Content-length: 3464
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92893
Bug ID: 92893
Summary: Unhelpful -Wstringop-overflow warning
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: sbergman at redhat dot com
Target Milestone: ---
Recent GCC 10 trunk produces a -Wstringop-overflow warning that at least
gcc-c++-9.2.1-1.fc31.x86_64 does not produce. Unfortunately the minimal
reproducer I came up with is still a bit lengthy:
> $ cat test.cc
> #include <cstring>
>
> struct View {
> View(char const * s): s_(s), n_(std::strlen(s)) {}
> char const * s_;
> std::size_t n_;
> };
>
> template<typename T> struct Add {
> static char * add(char * buf, T const &);
> };
>
> template<int N> struct Add<char const[N]> {
> static char * add(char * buf, char const s[N]) {
> std::memcpy(buf, s, N);
> return buf + N;
> }
> };
>
> template<> struct Add<View> {
> static char * add(char * buf, View const & v) {
> std::memcpy(buf, v.s_, v.n_);
> return buf + v.n_;
> }
> };
>
> template<typename T1, typename T2> struct Cat {
> Cat(T1 const & x, T2 const & y): x_(x), y_(y) {}
> char * add(char * buf) const
> { return Add<T2>::add(Add<T1>::add(buf, x_), y_); }
> T1 const & x_;
> T2 const & y_;
> };
>
> template<typename T1, typename T2> struct Add<Cat<T1, T2>> {
> static char * add(char * buf, Cat<T1, T2> const & c) { return c.add(buf); }
> };
>
> Cat<char const[1], View> catA(char const(&x)[1], View const & y) {
> return {x, y};
> }
>
> Cat<Cat<char const[1], View>, char const[4]> catB(
> Cat<char const[1], View> const & x, char const (&y)[4])
> {
> return {x, y};
> }
>
> struct Buf { char buf[1]; };
>
> Buf * get();
>
> struct Str {
> template<typename T1, typename T2> Str(Cat<T1, T2> c)
> { c.add(get()->buf); }
> };
>
> void f(char const * p) { Str(catB(catA("", View(p)), "xxx")); }
> $ g++ -O2 -c test.cc
> In member function ‘char* Cat<T1, T2>::add(char*) const [with T1 = Cat<const char [1], View>; T2 = const char [4]]’,
> inlined from ‘Str::Str(Cat<T1, T2>) [with T1 = Cat<const char [1], View>; T2 = const char [4]]’ at test.cc:55:10,
> inlined from ‘void f(const char*)’ at test.cc:58:26:
> test.cc:15:16: warning: writing 4 bytes into a region of size 1 [-Wstringop-overflow=]
> 15 | std::memcpy(buf, s, N);
> | ~~~~~~~~~~~^~~~~~~~~~~
The warning only appears with this specific case where catB takes a char[4],
not for other char[N].
Buff::buf is meant to be a trailing flexible array member. In the original
code, it needs to stay that way for compatibility reasons, but also if it is
replaced with the canonical GCC-extended flexible array member syntax,
> struct Buf { char buf[0]; };
the warning remains (this time as "writing 4 bytes into a region of size 0").
At least in the original code, I found no range of code that could be wrapped
in
> #pragma GCC diagnostic push
> #pragma GCC diagnostic ignored "-Wstringop-overflow"
[...]
> #pragma GCC diagnostic push
short of disabling the warning completely. But maybe there is a way to
annotate the call to c.add(get()->buf) in the Str constructor, to break the
connection that Buf::buf is nominally of size 1 there?
>From gcc-bugs-return-662950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 17:08:10 2019
Return-Path: <gcc-bugs-return-662950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3391 invoked by alias); 10 Dec 2019 17:08:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3073 invoked by uid 48); 10 Dec 2019 17:08:06 -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: Tue, 10 Dec 2019 17:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-92886-4-ykzI8VB77q@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: 2019-12/txt/msg01020.txt.bz2
Content-length: 496
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92886
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.0
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed on trunk, thanks.
>From gcc-bugs-return-662951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 17:08:25 2019
Return-Path: <gcc-bugs-return-662951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4334 invoked by alias); 10 Dec 2019 17:08: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 4111 invoked by uid 48); 10 Dec 2019 17:08:21 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/92848] [OpenACC] Memory leak for simple 'acc_create', 'acc_delete' sequence
Date: Tue, 10 Dec 2019 17:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92848-4-0AJ9izCsS3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01021.txt.bz2
Content-length: 1176
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92848
--- Comment #4 from jules at gcc dot gnu.org ---
(In reply to Thomas Schwinge from comment #3)
> (In reply to jules from comment #2)
> > Again, please don't change this code under the feet of the refcount overhaul
> > patch!
>
> But why? This here is one independent chance. The big "OpenACC reference
> count overhaul" will then either lose some of its changes, or replace this
> here by something else ('GOMP_MAP_VARS_OPENACC_ENTER_DATA'), but it's an
> incremental step (forward).
It's hard for me to evaluate if the changes are correct, given that I don't
trust the current baseline, mostly.
> > Using the (currently OpenMP-specific) GOMP_MAP_VARS_ENTER_DATA is
> > going to end up mighty confusing from OpenACC-specific code.
>
> Why do you think so? It has exactly! the semantics that we need here, for
> this PR.
Is the desired behaviour change just the reference count initialized by
target.c:gomp_map_vars_internal? I suppose that's OK. The danger is if the
semantics needed for OpenMP ever shift away from what we need for OpenACC here.
But I guess this code might not be around for long anyway?
>From gcc-bugs-return-662952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 17:19:25 2019
Return-Path: <gcc-bugs-return-662952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47402 invoked by alias); 10 Dec 2019 17:19: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 47307 invoked by uid 48); 10 Dec 2019 17:19:21 -0000
From: "bp at alien8 dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92841] Optimize -fstack-protector-strong code generation a bit
Date: Tue, 10 Dec 2019 17: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bp at alien8 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-92841-4-zn0klUECBw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01022.txt.bz2
Content-length: 1544
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841
--- Comment #6 from Boris <bp at alien8 dot de> ---
Ok, so there was a mix-up between patterns with and without multi-nodes
in your untested fix, which Micha found and fixed, see attached patch.
(otherwise it wouldn't even build a whole kernel).
With it, it fixed the pattern which I reported to properly overwrite
RAX:
mov %gs:0x28,%rax
mov %rax,0x10(%rsp)
mov $0x6,%eax
Other places look good too:
mov %gs:0x28,%rax
mov %rax,0xf0(%rsp)
mov 0x120e664(%rip),%rax # ffffffff8220f020 <blacklisted_initcalls>
But browsing the code it generated, there are still suboptimal patterns
like:
mov %gs:0x28,%rax
mov %rax,0x8(%rsp)
xor %eax,%eax
mov 0x98(%rdi),%rax
or
mov %gs:0x28,%rax
mov %rax,0x80(%rsp)
xor %eax,%eax
mov %rbx,%rax
I'm guessing this has to do with the patterns which probably should also
match mem and reg source operand. Or so, just guessing here.
Also, there's more complex stuff like:
mov %gs:0x28,%rax
mov %rax,-0x28(%rbp)
xor %eax,%eax
add %gs:0x7f00ffc4(%rip),%r13 # 12360 <this_cpu_off>
mov 0x80(%rdi),%rax
test %rax,%rax
and if that ADD can land under the following MOV, then, one could remove
the XOR too. But maybe that's too complicated to do or it'll become too
ugly...
Oh, and there actually are cases where the XOR *is* needed:
mov %gs:0x28,%rax
mov %rax,0x68(%rsp)
xor %eax,%eax
rep stos %rax,%es:(%rdi)
Fun.
Thanks!
>From gcc-bugs-return-662954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 17:20:41 2019
Return-Path: <gcc-bugs-return-662954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52413 invoked by alias); 10 Dec 2019 17:20: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 51587 invoked by uid 48); 10 Dec 2019 17:20:33 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92894] New: "declared using local type 'test01()::X', is used but never defined" during concept satisfaction
Date: Tue, 10 Dec 2019 17:20: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: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter blocked target_milestone
Message-ID: <bug-92894-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01024.txt.bz2
Content-length: 1791
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92894
Bug ID: 92894
Summary: "declared using local type 'test01()::X', is used but
never defined" during concept satisfaction
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Blocks: 67491
Target Milestone: ---
The following should compile, because the undefined member function is never
odr-used, only its return type is needed.
#include <iterator>
template<typename T,
std::indirect_unary_predicate<std::projected<T*, std::identity>> Pred>
constexpr void
all_of(T*, Pred)
{ }
void
test01()
{
struct X { };
X x;
all_of(&x, [](X&) { return false; });
}
Compiled with -std=gnu++2a and current trunk:
In file included from
/home/jwakely/gcc/10/include/c++/10.0.0/bits/stl_iterator_base_types.h:71,
from /home/jwakely/gcc/10/include/c++/10.0.0/iterator:61,
from proj.cc:1:
/home/jwakely/gcc/10/include/c++/10.0.0/bits/iterator_concepts.h:669:40: error:
'std::indirect_result_t<_Proj&, _Iter> std::projected<_Iter,
_Proj>::operator*() const [with _Iter = test01()::X*; _Proj = std::identity;
std::indirect_result_t<_Proj&, _Iter> = test01()::X&]', declared using local
type 'test01()::X', is used but never defined [-fpermissive]
669 | indirect_result_t<_Proj&, _Iter> operator*() const; // not
defined
| ^~~~~~~~
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67491
[Bug 67491] [meta-bug] concepts issues
>From gcc-bugs-return-662953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 17:20:41 2019
Return-Path: <gcc-bugs-return-662953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52356 invoked by alias); 10 Dec 2019 17:20: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 51597 invoked by uid 48); 10 Dec 2019 17:20:33 -0000
From: "bp at alien8 dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92841] Optimize -fstack-protector-strong code generation a bit
Date: Tue, 10 Dec 2019 17: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: 9.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bp at alien8 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: attachments.created
Message-ID: <bug-92841-4-mV6LYd5smU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01023.txt.bz2
Content-length: 290
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841
--- Comment #7 from Boris <bp at alien8 dot de> ---
Created attachment 47465
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47465&action=edit
Micha's patterns fix
Fix for mix-up between patterns with and without multi-nodes.
>From gcc-bugs-return-662956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 17:22:55 2019
Return-Path: <gcc-bugs-return-662956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56880 invoked by alias); 10 Dec 2019 17: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 56729 invoked by uid 48); 10 Dec 2019 17:22:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92841] Optimize -fstack-protector-strong code generation a bit
Date: Tue, 10 Dec 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: target
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92841-4-GUfIVs2oGO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01026.txt.bz2
Content-length: 281
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
In the patch attached in this PR, yes, but I think it is fixed in the one I've
posted to gcc-patches -
https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00664.html
>From gcc-bugs-return-662955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 17:22:10 2019
Return-Path: <gcc-bugs-return-662955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55432 invoked by alias); 10 Dec 2019 17:22: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 55364 invoked by uid 48); 10 Dec 2019 17:22:04 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59655] incorrect diagnostic on templatized function with lambda parameter
Date: Tue, 10 Dec 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: 4.9.0
X-Bugzilla-Keywords: diagnostic, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59655-4-DvhzVGHii9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01025.txt.bz2
Content-length: 195
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59655
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Comment 6 seems to be a different issue, so I've reported that as PR 92894
>From gcc-bugs-return-662957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 17:28:36 2019
Return-Path: <gcc-bugs-return-662957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65225 invoked by alias); 10 Dec 2019 17:28: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 65151 invoked by uid 48); 10 Dec 2019 17:28:32 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92841] Optimize -fstack-protector-strong code generation a bit
Date: Tue, 10 Dec 2019 17: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92841-4-MupkczrXKq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01027.txt.bz2
Content-length: 837
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
There is a scheduling pass in between the peephole2 which this patch uses and
the final pass, so it is possible there was some other instruction in between
before scheduling, thus the peephole2 didn't trigger, later sched2 changes the
order and now you see it. If we don't want to split the pattern and thus risk
scheduling moving it away significantly etc., that will simply always happen,
what matters is that the patch handles the common cases. And no, we aren't
going to do anything about the cases where the register is set after several
instructions, the clearing of the register is a security feature and we simply
don't want to extend the exposure of the security sensitive data in any
register.
>From gcc-bugs-return-662958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 17:35:25 2019
Return-Path: <gcc-bugs-return-662958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79594 invoked by alias); 10 Dec 2019 17: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 79538 invoked by uid 48); 10 Dec 2019 17:35:20 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/82520] Missing warning when stack addresses escape the current scope
Date: Tue, 10 Dec 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: c
X-Bugzilla-Version: 7.1.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dmalcolm 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-82520-4-qPEn4EC83y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82520-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82520-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01028.txt.bz2
Content-length: 656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82520
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org
--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
FWIW the analyzer branch can warn about comment #0, but only if the value gets
used, not simply that it escapes.
See e.g. the -Wanalyzer-use-of-pointer-in-stale-stack-frame warning within
https://godbolt.org/z/PAtqhB
Probably ought to warn about it simply escaping.
>From gcc-bugs-return-662959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 17:36:18 2019
Return-Path: <gcc-bugs-return-662959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81127 invoked by alias); 10 Dec 2019 17: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 81052 invoked by uid 55); 10 Dec 2019 17:36:14 -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: Tue, 10 Dec 2019 17:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92886-4-6SwmnNZYLe@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: 2019-12/txt/msg01029.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92886
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Tue Dec 10 17:35:42 2019
New Revision: 279175
URL: https://gcc.gnu.org/viewcvs?rev=279175&root=gcc&view=rev
Log:
libstdc++: Fix description of std::ios::trunc (PR 92886)
PR libstdc++/92886
* include/bits/ios_base.h (std::ios_base::trunc): Fix comment.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/ios_base.h
>From gcc-bugs-return-662960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 17:39:43 2019
Return-Path: <gcc-bugs-return-662960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87675 invoked by alias); 10 Dec 2019 17:39: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 87640 invoked by uid 48); 10 Dec 2019 17:39:39 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92891] [10 Regression] ice in decompose, at wide-int.h:984
Date: Tue, 10 Dec 2019 17: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: ice-on-valid-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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords component target_milestone short_desc
Message-ID: <bug-92891-4-lmoKfjNmtC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01030.txt.bz2
Content-length: 626
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92891
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Component|c |tree-optimization
Target Milestone|--- |10.0
Summary|ice in decompose, at |[10 Regression] ice in
|wide-int.h:984 |decompose, at
| |wide-int.h:984
>From gcc-bugs-return-662961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 17:57:39 2019
Return-Path: <gcc-bugs-return-662961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61093 invoked by alias); 10 Dec 2019 17:57: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 61055 invoked by uid 48); 10 Dec 2019 17:57:35 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92889] [8/9 only] GCC-8 considers the _mm_gf2p8affine_epi64_epi8 intrinsic to be symmetric
Date: Tue, 10 Dec 2019 17: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: 8.3.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: keywords target_milestone
Message-ID: <bug-92889-4-mT594Wj6yi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92889-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92889-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01031.txt.bz2
Content-length: 352
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92889
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Target Milestone|--- |8.4
>From gcc-bugs-return-662963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 18:01:53 2019
Return-Path: <gcc-bugs-return-662963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12651 invoked by alias); 10 Dec 2019 18: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 12596 invoked by uid 48); 10 Dec 2019 18:01:48 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92892] [AARCH64] TBL-based permutations can be implemented more efficiently for 2-element vectors
Date: Tue, 10 Dec 2019 18:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
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: bug_severity
Message-ID: <bug-92892-4-aqLSWVjx3h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92892-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92892-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01033.txt.bz2
Content-length: 300
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92892
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
>From gcc-bugs-return-662962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 18:01:15 2019
Return-Path: <gcc-bugs-return-662962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11523 invoked by alias); 10 Dec 2019 18:01: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 11360 invoked by uid 48); 10 Dec 2019 18:01:10 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92892] [AARCH64] TBL-based permutations can be implemented more efficiently for 2-element vectors
Date: Tue, 10 Dec 2019 18:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: 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 component dependson
Message-ID: <bug-92892-4-zun5lNe8al@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92892-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92892-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01032.txt.bz2
Content-length: 655
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92892
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Component|rtl-optimization |target
Depends on| |82199
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
See PR 82199 also.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82199
[Bug 82199] __builtin_shuffle sometimes should produce zip1 rather than TBL
>From gcc-bugs-return-662964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 18:03:23 2019
Return-Path: <gcc-bugs-return-662964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16173 invoked by alias); 10 Dec 2019 18:03: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 16097 invoked by uid 48); 10 Dec 2019 18:03:19 -0000
From: "lewissbaker.opensource at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92895] New: [libstdc++] stop_token conformance issues
Date: Tue, 10 Dec 2019 18:03: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: lewissbaker.opensource 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-92895-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01034.txt.bz2
Content-length: 5261
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92895
Bug ID: 92895
Summary: [libstdc++] stop_token conformance issues
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: lewissbaker.opensource at gmail dot com
Target Milestone: ---
The current implementation of std::stop_token in trunk has a few issues that
make it non-conformant with regards to the latest draft specification N4842.
The version I reviewed was:
https://github.com/gcc-mirror/gcc/blob/87f8610d5d61ceda80ca91be963bdf3e989af4f6/libstdc%2B%2B-v3/include/std/stop_token
Note that there is a reference implementation available here:
https://github.com/josuttis/jthread/blob/master/source/stop_token.hpp
stop_token::stop_possible()
This implementation is just checking whether the stop_token has
ownership of a shared-state.
This is necessary as per [stoptoken.mem]/2.1, but insufficient.
It also needs to take into account [stoptoken.mem]/2.2 which requires that
this
method also return false when it does have ownership of a shared state but
where
there is no associated stop_source.
This generally requires keeping a separate ref-count for the number of
stop_source
instances.
stop_token::_Stop_cb::_M_callback
The function pointer type could be declared noexcept here.
This might avoid some extra exception-handling codegen being generated in
_M_request_stop() when this function pointer is invoked.
stop_token::_Stop_cb::_S_execute()
It is valid for the invocation of a callback registered with the
stop_callback to
end up calling the destructor of the stop_callback object from within the
callback.
See [stopcallback.cons]/6 which says:
"... If callback is executing on the current thread, then the destructor
does not block (3.6)
waiting for the return from the invocation of callback. ..."
The intent of this wording was to indicate that it is potentially valid for
the destructor of
a stop_callback object to execute on the thread that is currently executing
that instance's
registered callback. i.e. that the destructor might run inside the
user-provided callback.
Thus the current logic that tries to update '__cb->_M_prev = __cb->_M_next =
nullptr;' after
invoking the registered callback is thus potentially writing to a dangling
pointer. You would
either need to update these pointers before invoking the callback or
otherwise somehow detect
whether the destructor has been run during the invocation of the callback.
stop_token::_Stop_state_t::_M_request_stop()
This method holds the _Stop_state_t::_M_mtx lock while invoking user-provided
callbacks.
This prevents stop_callbacks from being deregistered concurrently while the
user-provided
callback is executing.
See [stopcallback.cons]/6 which says:
"The destructor does not block waiting for the execution of another
callback
registered by an associated stop_callback."
This is necessary to prevent certain deadlock situations that would otherwise
arise were
a callback to try to acquire a lock on some mutex that might currently be
held by another thread
that is concurrently trying to deregister a stop_callback.
stop_source::operator=(stop_source&& rhs)
This implementation just does a swap() which leaves rhs with the previous
state
of *this rather than leaving rhs as an empty state.
See [stopcallback.cons]/10 which says that this should instead be equivalent
to:
stop_source(std::move(rhs)).swap(*this).
ie. you first need to construct a temporary stop_source and call swap() with
that.
stop_callback::stop_callback(const stop_token&, Callback&&)
stop_callback::stop_callback(stop_token&&, Callback&&)
These constructors are only supposed to throw exceptions that are thrown by
the constructor of the callback object.
See [stopcallback.cons]/5 which states:
"Throws: Any exception thrown by the initialization of callback."
This implementation calls the _Stop_state_t::_M_register_callback()
method which is not declared noexcept and which calls std::mutex::lock()
which might
throw a std::system_error if it failed to acquire the mutex lock.
It might be easier to provide a noexcept implementation here if the
implementation was built
on top of std::atomic and used std::atomic::wait()-based spin-locks instead
of std::mutex.
These constructors also have a race-condition that fails to call the callback
being registered
inline if request_stop() is called concurrently by another thread in-between
the call to
if (__state->_M_stop_requested())
and
else if (__state->_M_register_callback(this))
stop_callback::~stop_callback()
This needs to ensure that it blocks until the callback finishes executing if
the
the callback is executing concurrently on another thread and that it does not
block
if the callback is currently executing on the current thread.
It also needs to ensure that it does not block waiting for the execution of
some
other associated callback to complete.
See [stopcallback.cons]/6 for more info.
>From gcc-bugs-return-662965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 18:04:16 2019
Return-Path: <gcc-bugs-return-662965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18282 invoked by alias); 10 Dec 2019 18:04: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 17985 invoked by uid 48); 10 Dec 2019 18:04:11 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92893] Unhelpful -Wstringop-overflow warning
Date: Tue, 10 Dec 2019 18:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on blocked everconfirmed
Message-ID: <bug-92893-4-cLydJ1T1li@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92893-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92893-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01035.txt.bz2
Content-length: 2317
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92893
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
Blocks| |88443
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
The warning sees the IL below. It calls compute_objsize() to determine the
size of the destination (what _34 points to) which, after failing to determine
the size of the object the pointer points to, falls back on its type, which it
determines from the assignment to _30 to be 1.
A solution that I think would avoid the warning in this case is to work a
harder and before falling back on using the type consider where the pointer
comes from. Here, it's ADDR_EXPR (MEM_REF (SSA_NAME (get()), 1)), so by
drilling into the operands we arrive at offset 1 from Buf*. Determining that
offset 1 from Buf* corresponds to a trailing array would let us avoid the
warning. I think all the bits to implement this are in place (particularly
field_at_offset in gimple-ssa-sprintf.c), so they just need to be made use of
here.
#pragma GCC warning is unfortunately known to work poorly for middle-end
warnings. It's also on my list of things to do for GCC 10 but I haven't gotten
around to it yet.
f (const char * p)
{
char * D.2771;
struct Cat c;
struct View D.2558;
struct Cat D.2568;
struct Buf * _6;
long unsigned int _8;
char * _30;
char * _34;
<bb 2> [local count: 1073741824]:
_8 = __builtin_strlen (p_2(D));
_6 = get ();
MEM[(char * {ref-all})_6] = 0;
_30 = &MEM <char[1]> [(void *)_6 + 1B]; <<< char[1]
__builtin_memcpy (_30, p_2(D), _8);
_34 = _30 + _8;
MEM <unsigned int> [(char * {ref-all})_34] = 7895160; <<<
-Wstringop-overflow
c ={v} {CLOBBER};
D.2568 ={v} {CLOBBER};
D.2558 ={v} {CLOBBER};
return;
}
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443
[Bug 88443] [meta-bug] bogus/missing -Wstringop-overflow warnings
>From gcc-bugs-return-662966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 18:12:40 2019
Return-Path: <gcc-bugs-return-662966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39173 invoked by alias); 10 Dec 2019 18:12: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 39134 invoked by uid 48); 10 Dec 2019 18:12:36 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92893] Unhelpful -Wstringop-overflow warning
Date: Tue, 10 Dec 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: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92893-4-B0RcvQwy6m@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92893-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92893-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01036.txt.bz2
Content-length: 669
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92893
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Defining Str like so works for the test case:
struct Str {
template<typename T1, typename T2> Str(Cat<T1, T2> c)
{
struct Flex { char c, a[]; } *p = (Flex*)get();
c.add(p->a);
}
};
by changing the IL the warning sees to:
<bb 2> [local count: 1073741824]:
_8 = __builtin_strlen (p_2(D));
_6 = get ();
MEM[(char * {ref-all})_6 + 1B] = 0;
_30 = &MEM <char[<unknown>]> [(void *)_6 + 2B]; <<< char[]
__builtin_memcpy (_30, p_2(D), _8);
_34 = _30 + _8;
MEM <unsigned int> [(char * {ref-all})_34] = 7895160;
>From gcc-bugs-return-662967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 18:15:15 2019
Return-Path: <gcc-bugs-return-662967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71047 invoked by alias); 10 Dec 2019 18: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 70631 invoked by uid 48); 10 Dec 2019 18:15:00 -0000
From: "bp at alien8 dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92841] Optimize -fstack-protector-strong code generation a bit
Date: Tue, 10 Dec 2019 18: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bp at alien8 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-92841-4-7QBN6AQZF3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01037.txt.bz2
Content-length: 222
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92841
--- Comment #10 from Boris <bp at alien8 dot de> ---
Ok, fair enough. After all, security is not free. :)
If you need me to test anything else, lemme know.
Thx guys.
>From gcc-bugs-return-662968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 18:31:46 2019
Return-Path: <gcc-bugs-return-662968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12784 invoked by alias); 10 Dec 2019 18: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 126980 invoked by uid 48); 10 Dec 2019 18:31:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59655] incorrect diagnostic on templatized function with lambda parameter
Date: Tue, 10 Dec 2019 18:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: diagnostic, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59655-4-4GOzdSVpQl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01038.txt.bz2
Content-length: 1222
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59655
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I can confirm the #c0/#c1 case, I think #c4/#c5 are actually invalid testcases.
For #c1, a slightly modified testcase where the foo call is before the
static_assert rather than after it works (emits just one error for the
static_assert failure).
What is going on is that if the current instantiation is erroneous, we don't
instantiate some of the templates, limit_bad_template_recursion is called and
if the current template is neglectable_inst_p, we just return early from
instantiate_decl.
The question is, should we not call any of the no_linkage_error if any errors
were diagnosed first (errorcount + sorrycount > 0), or just ignore in such
cases templates that are neglectable_inst_p? Of course, the errorcount +
sorrycount would need to be evaluated before the loop, so we can emit multiple
no_linkage_error errors.
Or shall we mark the templates we haven't instantiated due to this some way
(some lang specific flag or something in cgraph node) and just skip those in
no_linkage_error and check_global_declaration?
Note, the latter already uses TREE_NO_WARNING as one way to shut it up.
>From gcc-bugs-return-662969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 18:32:09 2019
Return-Path: <gcc-bugs-return-662969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37947 invoked by alias); 10 Dec 2019 18:32: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 37830 invoked by uid 55); 10 Dec 2019 18:32:04 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92863] ICE in gfc_typename
Date: Tue, 10 Dec 2019 18:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92863-4-xjSHX2ZCPe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92863-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92863-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01039.txt.bz2
Content-length: 763
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92863
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Tue Dec 10 18:31:33 2019
New Revision: 279180
URL: https://gcc.gnu.org/viewcvs?rev=279180&root=gcc&view=rev
Log:
2019-12-10 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/92863
* misc.c (gfc_typename): If derived component is NULL for
derived or class, return "invalid type" or "invalid class",
respectively.
2019-12-10 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/92863
* gfortran.dg/interface_45.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/interface_45.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/misc.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 18:38:10 2019
Return-Path: <gcc-bugs-return-662970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51940 invoked by alias); 10 Dec 2019 18:38: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 51885 invoked by uid 48); 10 Dec 2019 18:38:06 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92863] ICE in gfc_typename
Date: Tue, 10 Dec 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: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92863-4-4PEORiQoEz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92863-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92863-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01040.txt.bz2
Content-length: 470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92863
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed, closing.
Thanks a lot for the bug report!
>From gcc-bugs-return-662971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 18:46:41 2019
Return-Path: <gcc-bugs-return-662971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98972 invoked by alias); 10 Dec 2019 18:46: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 98843 invoked by uid 48); 10 Dec 2019 18:46:35 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/89047] [OpenACC] ICE in mark_scope_block_unused, at tree-ssa-live.c:391
Date: Tue, 10 Dec 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: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc
Message-ID: <bug-89047-4-SGNJoLrgUX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89047-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89047-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01041.txt.bz2
Content-length: 5322
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89047
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
Summary|ICE in |[OpenACC] ICE in
|mark_scope_block_unused, at |mark_scope_block_unused, at
|tree-ssa-live.c:391 |tree-ssa-live.c:391
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to kargl from comment #2)
> The code in the original comment now compiles. Likely fixed by one of
> Tobias's recent patches.
At r279064, I get a different place where it crashes:
z1.f90:18:0:
18 | c = g(x)
|
interner Compiler-Fehler: Speicherzugriffsfehler
0xe0dfff crash_signal
../../trunk/gcc/toplev.c:328
0x8ee73f tree_check3(tree_node*, char const*, int, char const*, tree_code,
tree_code, tree_code)
../../trunk/gcc/tree.h:3311
0x8ee73f gfc_conv_component_ref
../../trunk/gcc/fortran/trans-expr.c:2461
0x8f794b gfc_conv_variable
../../trunk/gcc/fortran/trans-expr.c:2829
0x8f68e0 gfc_conv_expr_lhs(gfc_se*, gfc_expr*)
../../trunk/gcc/fortran/trans-expr.c:8695
0x8c5788 gfc_conv_ss_descriptor
../../trunk/gcc/fortran/trans-array.c:2962
0x8c8690 gfc_conv_ss_startstride(gfc_loopinfo*)
../../trunk/gcc/fortran/trans-array.c:4340
0x8f8684 gfc_conv_subref_array_arg(gfc_se*, gfc_expr*, int, sym_intent, bool,
gfc_symbol const*, char const*, gfc_symbol*, bool)
../../trunk/gcc/fortran/trans-expr.c:4663
0x902c5a gfc_conv_procedure_call(gfc_se*, gfc_symbol*, gfc_actual_arglist*,
gfc_expr*, vec<tree_node*, va_gc, vl_embed>*)
../../trunk/gcc/fortran/trans-expr.c:6185
0x8f62ba gfc_apply_interface_mapping(gfc_interface_mapping*, gfc_se*,
gfc_expr*)
../../trunk/gcc/fortran/trans-expr.c:4589
0x8c4643 gfc_set_loop_bounds_from_array_spec(gfc_interface_mapping*, gfc_se*,
gfc_array_spec*)
../../trunk/gcc/fortran/trans-array.c:1012
0x900ffd gfc_conv_procedure_call(gfc_se*, gfc_symbol*, gfc_actual_arglist*,
gfc_expr*, vec<tree_node*, va_gc, vl_embed>*)
../../trunk/gcc/fortran/trans-expr.c:6733
0x906905 gfc_conv_function_expr
../../trunk/gcc/fortran/trans-expr.c:7517
0x906905 gfc_trans_arrayfunc_assign
../../trunk/gcc/fortran/trans-expr.c:10066
0x907494 gfc_trans_assignment(gfc_expr*, gfc_expr*, bool, bool, bool, bool)
../../trunk/gcc/fortran/trans-expr.c:11187
0x8bd372 trans_code
../../trunk/gcc/fortran/trans.c:1852
0x8eb37e gfc_generate_function_code(gfc_namespace*)
../../trunk/gcc/fortran/trans-decl.c:6801
0x8c1691 gfc_generate_module_code(gfc_namespace*)
../../trunk/gcc/fortran/trans.c:2252
0x86a7d5 translate_all_program_units
../../trunk/gcc/fortran/parse.c:6289
0x86a7d5 gfc_parse_file()
../../trunk/gcc/fortran/parse.c:6541
Is this ICE on valid or ICE on invalid?
>From gcc-bugs-return-662972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 18:58:11 2019
Return-Path: <gcc-bugs-return-662972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10952 invoked by alias); 10 Dec 2019 18:58: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 10318 invoked by uid 55); 10 Dec 2019 18:58:05 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92874] ICE in gfc_dep_compare_expr, at fortran/dependency.c:36
Date: Tue, 10 Dec 2019 18:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-92874-4-dHlNzyWd8Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92874-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92874-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01042.txt.bz2
Content-length: 769
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92874
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Tue Dec 10 18:57:30 2019
New Revision: 279181
URL: https://gcc.gnu.org/viewcvs?rev=279181&root=gcc&view=rev
Log:
Bail out in gfc_dep_compare_expr for a NULL argument.
2019-12-10 Martin Liska <mliska@suse.cz>
PR fortran/92874
* dependency.c (gfc_dep_compare_expr): Bail out
when one of the arguments is null.
2019-12-10 Martin Liska <mliska@suse.cz>
PR fortran/92874
* gfortran.dg/pr92874.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/pr92874.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/dependency.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-662973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 19:00:36 2019
Return-Path: <gcc-bugs-return-662973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14583 invoked by alias); 10 Dec 2019 19:00: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 14519 invoked by uid 48); 10 Dec 2019 19:00:31 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92874] ICE in gfc_dep_compare_expr, at fortran/dependency.c:36
Date: Tue, 10 Dec 2019 19:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin 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-92874-4-awNVNtr6kM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92874-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92874-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01043.txt.bz2
Content-length: 475
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92874
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed on trunk, not planning to make a backport.
>From gcc-bugs-return-662974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 19:23:25 2019
Return-Path: <gcc-bugs-return-662974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44303 invoked by alias); 10 Dec 2019 19:23: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 44166 invoked by uid 48); 10 Dec 2019 19:23:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92891] [10 Regression] ice in decompose, at wide-int.h:984
Date: Tue, 10 Dec 2019 19: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92891-4-ZJtjJ4UJmV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg01044.txt.bz2
Content-length: 856
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92891
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-10
CC| |jakub at gcc dot gnu.org,
| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Most likely r278983. The ICE is on
3889 else if (wi::ltu_p (min, wisiz))
where min->precision is 64 and wisiz->precision is 32. That is invalid, ltu_p
etc. can be called only with the same precision wide_ints.
>From gcc-bugs-return-662975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 10 19:31:34 2019
Return-Path: <gcc-bugs-return-662975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83437 invoked by alias); 10 Dec 2019 19:31: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 81798 invoked by uid 89); 10 Dec 2019 19:31:28 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=3.4 required=5.0 testsºYES_50,FILL_THIS_FORM,FILL_THIS_FORM_LONG,HK_OBFDOM,HTML_MESSAGE,HTTP_ESCAPED_HOST,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 spammy=Website, UD:xml, Market, zip
X-HELO: NAM02-SN1-obe.outbound.protection.outlook.com
Received: from mail-eopbgr770099.outbound.protection.outlook.com (HELO NAM02-SN1-obe.outbound.protection.outlook.com) (40.107.77.99) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 10 Dec 2019 19:31:21 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DQU4Nuq18UiOE7vwg9FTksnungwCe5+hY08hFv1XrkhcGNDdrlOGQLrXr+4Mmf7dVe0+mXUvyN3/NPXwGYjuhrBhZ5FeCSQ320LikvZlHbr8P4+nAANU7hL0j+qChoPbM//vz31eUqQ2wA53u59cyLqzv3BdYvWD1GsYytfXQcG9Rii/GVCmc079Cqe46zFttdiFiIB5w7lambSepgQum3NLu0lTwh03DE8rgeA8MgvkVL9SCM2kxlWFbmqcd7a+cgzldzsjqiXt4O5yFHvEhEfomcWf6WHLN9BXalMYFaputyRQl3Ui8YL30giFOd0JXuD1xhV2dsu2ZMn2BkxCZg=ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XSL90eBFxPR1mMJ2Knpn2RVub0gDQyml4WNm4nsx5w4=; b=hJQ2HyHD2IhAXJ4P/BkGa4TmuvlqrZb131Wr7YprNjuHuVIuze0zdh92pzP7vYiTfCujGG7Lp/tW2zSrQBLo/0ZTrIeC37+9t87W5CKpwBrIkBjG380NS2q2eUpeRyooyG99hdQB/HNsh/TQS83tSgF571y0olfO/MYgqWY0sr7iGcxLfdNWQvhRvbN1zeUwSdkeURz3ljQ3ZdocXWYirNlgRXpdt81vN1PswSUC0BSSyD+KFru7AAMsC02QTM4LJkaUZuvy5OcDvpfcmsqpa/G2sTRZNRtvjCmk3wqwZ37D2ehWKqXq3j2cOc9gyp7Ohj2J4v3LKYvSUkJkv57sgw=ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=digitalmedianewtork.com; dmarc=pass action=none header.from=digitalmedianewtork.com; dkim=pass header.d=digitalmedianewtork.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Digitalmedianewtorkcom.onmicrosoft.com; s=selector1-Digitalmedianewtorkcom-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XSL90eBFxPR1mMJ2Knpn2RVub0gDQyml4WNm4nsx5w4=; b=YsBwO5/zbT0TkXmqgmls5UCBd0KJAVv0v35Iyur7CB2NnOd7QAvFWfYHR4hZsA0i2WVWPGL5L5cYCPsp3Y3xUeG3NxKWCFTxkZ3Ud0i6s/XwV4LPtv0VvrEZOa8o/wPuvZdg82O0q5Lre7ugTTRkSS0IiaaJxIXqR2KPROgo5Q0Received: from BN7PR07MB4193.namprd07.prod.outlook.com (52.135.242.14) by BN7PR07MB4420.namprd07.prod.outlook.com (52.135.246.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.17; Tue, 10 Dec 2019 19:31:19 +0000
Received: from BN7PR07MB4193.namprd07.prod.outlook.com ([fe80::b409:b36b:b03b:c93c]) by BN7PR07MB4193.namprd07.prod.outlook.com ([fe80::b409:b36b:b03b:c93c%4]) with mapi id 15.20.2516.018; Tue, 10 Dec 2019 19:31:19 +0000
From: Rebecca Harvey <rebecca.harvey@Digitalmedianewtork.com>
To: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>
Subject: New list
Date: Tue, 10 Dec 2019 19:31:00 -0000
Message-ID: <BN7PR07MB41936B5283D69FB6F36198A59B5B0@BN7PR07MB4193.namprd07.prod.outlook.com>
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rebecca.harvey@Digitalmedianewtork.com;
x-ms-oob-tlc-oobclassifiers: OLM:3276;
received-spf: None (protection.outlook.com: Digitalmedianewtork.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: DDgjCrkx9H65xUhRuMe6gLU/JzTAE4POyM09B4Mgr2WZt8i6L5NNah1VBB8U8Xa4jrb6folgz8kZHI7UilZv6HdkffAL18VohIRValqtCwdj6VkSM0A0uae8VWZRfJJ3
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2019-12/txt/msg01045.txt.bz2
Content-length: 704
Hi,
Are you interested in acquiring a targeted marketing list to increase sales?
We help you connect to the decision makers from the industries you want to reach. We can customize the verified list and provide contacts from the industries and location you want to reach to promote your products and services.
Information for each contact: Contact Name, Company Name, Job Title, Direct Email address, Phone number, Website, Physical Address, City, State, Zip Code and Country.
What industries and job titles do you want to reach?
Look forward to your response.
Thanks,
Rebecca
Rebecca Harvey | Leads Market Online
Mail "NO" in the subject line to take off from the list.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-12-05 23:11 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-09-27 16:11 [Bug bootstrap/67733] New: elfdump and readelf in perl scripts should to use env vars ELFDUMP and READELF ikozhukhov at gmail dot com
2015-09-27 16:14 ` [Bug target/67733] " pinskia at gcc dot gnu.org
2015-09-27 16:22 ` ikozhukhov at gmail dot com
2015-09-27 16:25 ` pinskia at gcc dot gnu.org
2015-09-27 16:44 ` graham.stott at btinternet dot com
2019-12-05 23:11 ` [Bug target/67733] illumos needs a new target triple ikozhukhov at gmail dot com
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).