public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
[not found] ` <ab84a63d-cc85-0cfd-a3a6-d6deab95488c@gmx.com>
@ 2018-07-06 10:38 ` Richard Earnshaw (lists)
0 siblings, 0 replies; 4+ messages in thread
From: Richard Earnshaw (lists) @ 2018-07-06 10:38 UTC (permalink / raw)
To: Kamil Rytarowski, rearnsha at gcc dot gnu.org, gcc-bugs
On 06/07/18 11:32, Kamil Rytarowski wrote:
> On 04.07.2018 20:55, rearnsha at gcc dot gnu.org wrote:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
>>
>> --- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
>> I'm not sure how relevant the netbsd-elf port is these days. I believe they've
>> now moved onto an EABI based ABI. But no GCC port of that has been
>> contributed.
>>
>
> NetBSD switched on newer ARM CPUs to EABI and keeps compat with OABI. A
> user is free to build either EABI and OABI for ARMv4+ CPUs. Older pre
> ARMv4 CPUs use OABI only.
>
GCC-9 will drop support for pre-armv4 CPUs. Such support has been
marked as deprecated for about 3 years now.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
[not found] <bug-86383-4@http.gcc.gnu.org/bugzilla/>
[not found] ` <bug-86383-4-roe7g6Jp7o@http.gcc.gnu.org/bugzilla/>
@ 2018-07-06 10:39 ` richard.earnshaw at arm dot com
2018-07-06 13:26 ` richard.earnshaw at arm dot com
2018-07-10 17:51 ` richard.earnshaw at arm dot com
3 siblings, 0 replies; 4+ messages in thread
From: richard.earnshaw at arm dot com @ 2018-07-06 10:39 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
--- Comment #3 from richard.earnshaw at arm dot com ---
On 06/07/18 11:32, Kamil Rytarowski wrote:
> On 04.07.2018 20:55, rearnsha at gcc dot gnu.org wrote:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
>>
>> --- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
>> I'm not sure how relevant the netbsd-elf port is these days. I believe they've
>> now moved onto an EABI based ABI. But no GCC port of that has been
>> contributed.
>>
>
> NetBSD switched on newer ARM CPUs to EABI and keeps compat with OABI. A
> user is free to build either EABI and OABI for ARMv4+ CPUs. Older pre
> ARMv4 CPUs use OABI only.
>
GCC-9 will drop support for pre-armv4 CPUs. Such support has been
marked as deprecated for about 3 years now.
>From gcc-bugs-return-609327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 10:45:57 2018
Return-Path: <gcc-bugs-return-609327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118863 invoked by alias); 6 Jul 2018 10: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 118397 invoked by uid 55); 6 Jul 2018 10:45:35 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84711] AArch32 big-endian fails when taking subreg of a vector mode to a scalar mode.
Date: Fri, 06 Jul 2018 10: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: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tnfchris at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84711-4-j2sBjiJRcG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00432.txt.bz2
Content-length: 480
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84711
--- Comment #14 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Author: tnfchris
Date: Fri Jul 6 10:44:35 2018
New Revision: 262472
URL: https://gcc.gnu.org/viewcvs?rev=262472&root=gcc&view=rev
Log:
Require sse for testcase on i686.
PR target/84711
* gcc.dg/vect/pr84711.c: Add -msse for i686 targets.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/vect/pr84711.c
>From gcc-bugs-return-609328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 10:56:04 2018
Return-Path: <gcc-bugs-return-609328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10107 invoked by alias); 6 Jul 2018 10:56: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 10047 invoked by uid 48); 6 Jul 2018 10:55:59 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86417] [9 Regression] FAIL: libgomp.fortran/alloc-comp-3.f90 -O0 (test for excess errors)
Date: Fri, 06 Jul 2018 10:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86417-4-7UB3WOI5gs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86417-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86417-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00433.txt.bz2
Content-length: 952
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86417
--- Comment #5 from janus at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #4)
> The idea of the warning is to ensure that we have
> Location information everywhere, and that patches
> Which do not correctly set the location should cause
> something visible during testing. We do not have this for
> release.
Thanks for the explanation. Makes sense.
Do you have any idea what might have caused the regression?
> We should take care to always regression test libgomp.fortran
> as well...
Yes, I finally got into this habit, after repeatedly breaking libgomp tests
with my patches without noticing it.
I also tried to document how to do this at the bottom of this wiki page:
https://gcc.gnu.org/wiki/TestCaseWriting
It took me a while to figure out how to actually run the Fortran subset of the
libgomp suite (which is not very well documented, or I'm too stupid to find
it).
>From gcc-bugs-return-609329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 11:10:21 2018
Return-Path: <gcc-bugs-return-609329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13054 invoked by alias); 6 Jul 2018 11:10:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9746 invoked by uid 89); 6 Jul 2018 11:10:20 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,GIT_PATCH_2,KAM_SHORT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=shark, Hx-languages-length:1052
X-HELO: mout.gmx.net
Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.15.18) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 06 Jul 2018 11:10:17 +0000
Received: from [192.168.0.241] ([89.78.252.225]) by mail.gmx.com (mrgmx003 [212.227.17.184]) with ESMTPSA (Nemesis) id 0MaqqY-1fqAMJ04gE-00KP82; Fri, 06 Jul 2018 13:10:13 +0200
Subject: Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>, "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>, gcc-bugs@gcc.gnu.org
References: <bug-86383-4@http.gcc.gnu.org/bugzilla/> <bug-86383-4-roe7g6Jp7o@http.gcc.gnu.org/bugzilla/> <ab84a63d-cc85-0cfd-a3a6-d6deab95488c@gmx.com> <471e8255-162f-4cdd-45bc-274271cfe973@arm.com>
From: Kamil Rytarowski <n54@gmx.com>
Message-ID: <11bdfd68-ac9b-fd06-81b1-df39b5dae66d@gmx.com>
Date: Fri, 06 Jul 2018 11:10:00 -0000
User-Agent: Mozilla/5.0 (X11; NetBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <471e8255-162f-4cdd-45bc-274271cfe973@arm.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DPIsYBf0KjAOKoIVEjTLIhkE17YxYLjpB"
X-IsSubscribed: yes
X-SW-Source: 2018-07/txt/msg00434.txt.bz2
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--DPIsYBf0KjAOKoIVEjTLIhkE17YxYLjpB
Content-Type: multipart/mixed; boundary="aZXviM8QUDNqSmU1G6BSFsXRqRyvwHq1l";
protected-headers="v1"
From: Kamil Rytarowski <n54@gmx.com>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
"rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>,
gcc-bugs@gcc.gnu.org
Message-ID: <11bdfd68-ac9b-fd06-81b1-df39b5dae66d@gmx.com>
Subject: Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler
fails in selftests
References: <bug-86383-4@http.gcc.gnu.org/bugzilla/>
<bug-86383-4-roe7g6Jp7o@http.gcc.gnu.org/bugzilla/>
<ab84a63d-cc85-0cfd-a3a6-d6deab95488c@gmx.com>
<471e8255-162f-4cdd-45bc-274271cfe973@arm.com>
In-Reply-To: <471e8255-162f-4cdd-45bc-274271cfe973@arm.com>
--aZXviM8QUDNqSmU1G6BSFsXRqRyvwHq1l
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Content-length: 978
On 06.07.2018 12:38, Richard Earnshaw (lists) wrote:
> On 06/07/18 11:32, Kamil Rytarowski wrote:
>> On 04.07.2018 20:55, rearnsha at gcc dot gnu.org wrote:
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
>>>
>>> --- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
>>> I'm not sure how relevant the netbsd-elf port is these days. I believe they've
>>> now moved onto an EABI based ABI. But no GCC port of that has been
>>> contributed.
>>>
>>
>> NetBSD switched on newer ARM CPUs to EABI and keeps compat with OABI. A
>> user is free to build either EABI and OABI for ARMv4+ CPUs. Older pre
>> ARMv4 CPUs use OABI only.
>>
>
> GCC-9 will drop support for pre-armv4 CPUs. Such support has been
> marked as deprecated for about 3 years now.
>
We verify these ports on real hardware.
NetBSD/shark is prepared to be switched to Clang/LLVM as GCC is
obsoleting it and surprisingly LLVM soon might have support for a wider
range of ARM CPUs.
--aZXviM8QUDNqSmU1G6BSFsXRqRyvwHq1l--
--DPIsYBf0KjAOKoIVEjTLIhkE17YxYLjpB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
Content-length: 850
-----BEGIN PGP SIGNATURE-----
iQJABAEBCAAqFiEELaxVpweEzw+lMDwuS7MI6bAudmwFAls/TnkMHG41NEBnbXgu
Y29tAAoJEEuzCOmwLnZs8dQP/354pV57LSXIfbux5sAmcmdycNXijxoWL+VyutwX
CarOa46sg0lrjTD05mo0cf62m1g2gyWLedyFSPHdWaqYP/0A/4N2ipsiCfeqAcmF
OlwlwRZNqwOD8eOFYOOGjqs+z/AaI04esGlkW7x7N8NgmCEurPd9YtPmp2e4LIdJ
km14+3KH+dj5EKtsrZ/Qg9HjQ8klV2RHE8/JMGerI8Af3pZyXTzMLwn/rq+VRdzu
u3/TIEytXFDDJaGhgmZxsJnxTnIOb2HkXNnAgJnlth1lY/9fUwqDjQC05cSmWIZb
gp10Rsnv/YfZI5J7StjFC6P8NwvhipNhsP6Ce1Dcqd031YD2yG/hFnrGJxY8r8ZS
XoE+i7l6Op/khczGYUYhlGt2tZkGWTb+RWJNznnKjxmHzPnBCITvPXn3NsdvUq2I
SDURKzxmPC4RU0/F1i8/AVD7SddJhyVeTSTQu+EeDeMJ31I7cXy2hNCX7S5PN7V6
2U93vO55ug3slS/1TV5imbaZfJ9fp70pAS60JhNf3ctYkFQpEX8QvlWjdqXPrn4N
oOlwfTLoBGnzm829ZBU5ig3rUnf/n3xy1rZo4LFuXW+z5gKXRAJ9TxbUB61TdQkS
hhL0sRUePBIeOnVaGXSytG/P/No40+IrGpQk1SeZEjBEixgZxz+gM/6j2qQ9hBo2
eFJJ
=yKdd
-----END PGP SIGNATURE-----
--DPIsYBf0KjAOKoIVEjTLIhkE17YxYLjpB--
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
[not found] <bug-86383-4@http.gcc.gnu.org/bugzilla/>
[not found] ` <bug-86383-4-roe7g6Jp7o@http.gcc.gnu.org/bugzilla/>
2018-07-06 10:39 ` richard.earnshaw at arm dot com
@ 2018-07-06 13:26 ` richard.earnshaw at arm dot com
2018-07-10 17:51 ` richard.earnshaw at arm dot com
3 siblings, 0 replies; 4+ messages in thread
From: richard.earnshaw at arm dot com @ 2018-07-06 13:26 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
--- Comment #4 from richard.earnshaw at arm dot com ---
On 06/07/18 12:11, Kamil Rytarowski wrote:
> On 06.07.2018 12:38, Richard Earnshaw (lists) wrote:
>> On 06/07/18 11:32, Kamil Rytarowski wrote:
>>> On 04.07.2018 20:55, rearnsha at gcc dot gnu.org wrote:
>>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
>>>>
>>>> --- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
>>>> I'm not sure how relevant the netbsd-elf port is these days. I believe they've
>>>> now moved onto an EABI based ABI. But no GCC port of that has been
>>>> contributed.
>>>>
>>>
>>> NetBSD switched on newer ARM CPUs to EABI and keeps compat with OABI. A
>>> user is free to build either EABI and OABI for ARMv4+ CPUs. Older pre
>>> ARMv4 CPUs use OABI only.
>>>
>>
>> GCC-9 will drop support for pre-armv4 CPUs. Such support has been
>> marked as deprecated for about 3 years now.
>>
>
> We verify these ports on real hardware.
>
> NetBSD/shark is prepared to be switched to Clang/LLVM as GCC is
> obsoleting it and surprisingly LLVM soon might have support for a wider
> range of ARM CPUs.
>
Shark's use strongARM cpus, which are ARMv4. That's not been obsoleted,
but it is considered deprecated these days.
>From gcc-bugs-return-609343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 13:34:14 2018
Return-Path: <gcc-bugs-return-609343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19810 invoked by alias); 6 Jul 2018 13:34:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19774 invoked by uid 48); 6 Jul 2018 13:34:09 -0000
From: "juhmat at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86421] New: OpenMP declare simd linear ref in module causes gfortran to bail out
Date: Fri, 06 Jul 2018 13:34: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juhmat 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-86421-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00448.txt.bz2
Content-length: 1208
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86421
Bug ID: 86421
Summary: OpenMP declare simd linear ref in module causes
gfortran to bail out
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: juhmat at gmail dot com
Target Milestone: ---
Created attachment 44361
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44361&action=edit
Full compiler output and output of "-save-temps"
Using module that has subroutine containing `!$OMP DECLARE SIMD LINEAR(REF(x))`
directive will cause compiler to bail out in: "(null):0: confused by earlier
errors, bailing out"
Minimal reproducing code:
module testmodule
use iso_fortran_env
implicit none
contains
subroutine foo(x)
real(kind=real64) :: x
!$OMP DECLARE SIMD LINEAR(REF(x))
end subroutine
end module testmodule
program testprogram
use testmodule
implicit none
end program testprogram
Compilation command:
gfortran-8 -fopenmp -save-temps -v testone.F90 -o testone
>From gcc-bugs-return-609344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 14:17:00 2018
Return-Path: <gcc-bugs-return-609344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95964 invoked by alias); 6 Jul 2018 14:16: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 95835 invoked by uid 55); 6 Jul 2018 14:16:50 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/84928] std::accumulate should move the accumulator argument
Date: Fri, 06 Jul 2018 14:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 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-84928-4-GsIUYeIbYo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84928-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84928-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00449.txt.bz2
Content-length: 1428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84928
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Fri Jul 6 14:16:13 2018
New Revision: 262477
URL: https://gcc.gnu.org/viewcvs?rev=262477&root=gcc&view=rev
Log:
PR libstdc++/84928 use std::move in <numeric> algorithms
P0616R0 altered the effects of the <numeric> algorithms to use std::move
on the accumulator values (resolving LWG 2055). This implements the
change for C++2a, but retains the previous behaviour for older
standards.
* include/bits/stl_numeric.h (_GLIBCXX_MOVE_IF_20): Define macro to
conditionally move, according to __cplusplus value.
(accumulate, inner_product, partial_sum, adjacent_difference): Use
_GLIBCXX_MOVE_IF_20.
* testsuite/26_numerics/accumulate/lwg2055.cc: New test.
* testsuite/26_numerics/adjacent_difference/lwg2055.cc: New test.
* testsuite/26_numerics/inner_product/lwg2055.cc: New test.
* testsuite/26_numerics/partial_sum/lwg2055.cc: New test.
Added:
trunk/libstdc++-v3/testsuite/26_numerics/accumulate/lwg2055.cc
trunk/libstdc++-v3/testsuite/26_numerics/adjacent_difference/lwg2055.cc
trunk/libstdc++-v3/testsuite/26_numerics/inner_product/lwg2055.cc
trunk/libstdc++-v3/testsuite/26_numerics/partial_sum/lwg2055.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/stl_numeric.h
>From gcc-bugs-return-609345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 14:27:30 2018
Return-Path: <gcc-bugs-return-609345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55733 invoked by alias); 6 Jul 2018 14:27: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 55697 invoked by uid 48); 6 Jul 2018 14:27:25 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/84928] std::accumulate should move the accumulator argument
Date: Fri, 06 Jul 2018 14:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-84928-4-1fXhGXkdeY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84928-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84928-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00450.txt.bz2
Content-length: 494
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84928
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.0
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Implemented for gcc 9.
>From gcc-bugs-return-609346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 14:44:54 2018
Return-Path: <gcc-bugs-return-609346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115262 invoked by alias); 6 Jul 2018 14:44: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 115217 invoked by uid 48); 6 Jul 2018 14:44:49 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/86418] warn about mismatch in type between argument and parameter type for declaration without prototype
Date: Fri, 06 Jul 2018 14:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
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 see_also
Message-ID: <bug-86418-4-gCHOY3tJ9P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86418-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86418-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00451.txt.bz2
Content-length: 1396
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86418
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=48063
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
I got more warnings than that:
$ gcc -O2 -c 86418.c -Wall -Wextra -Wold-style-definition
-Wold-style-declaration -Wtraditional-conversion -Wdouble-promotion
-Wstrict-prototypes -Wfloat-equal -Wunsuffixed-float-constants
-Wmissing-prototypes -Wmissing-declarations
86418.c:2:1: warning: function declaration isn't a prototype
[-Wstrict-prototypes]
static void bar ();
^~~~~~
86418.c:12:1: warning: 'bar' was used with no prototype before its definition
[-Wmissing-prototypes]
bar (double i)
^~~
86418.c: In function 'bar':
86418.c:14:7: warning: comparing floating point with == or != is unsafe
[-Wfloat-equal]
if (i)
^
86418.c: In function 'bar.constprop':
86418.c:14:6: warning: 'i' is used uninitialized in this function
[-Wuninitialized]
if (i)
^
$
But I'm guessing you want one for the bar(1); call on line 7 too?
>From gcc-bugs-return-609347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 14:46:07 2018
Return-Path: <gcc-bugs-return-609347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117072 invoked by alias); 6 Jul 2018 14:46: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 116485 invoked by uid 48); 6 Jul 2018 14:45:59 -0000
From: "boris.staletic at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86422] New: G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Fri, 06 Jul 2018 14:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: boris.staletic 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-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00452.txt.bz2
Content-length: 3476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
Bug ID: 86422
Summary: G++ ICE(segmentation fault) when compiling a huge
static array of sufficiently complex structs
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: boris.staletic at gmail dot com
Target Milestone: ---
My gcc version is 8.1.0. I have not tried with the latest gcc snapshot. If
requested, I will compile a gcc snapshot and try to reproduce.
My CHOST triple is x86_64-pc-linux-gnu, but I've also managed to get g++ to ICE
with an arm-linux-gnueabihf-g++, version 7.3.0, CHOST arm-linux-gnueabihf.
My gcc has been configured with:
/var/tmp/portage/sys-devel/gcc-8.1.0-r3/work/gcc-8.1.0/configure
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/8.1.0
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/8.1.0/include
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/8.1.0
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/8.1.0/man
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/8.1.0/info
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/8.1.0/include/g++-v8
--with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/8.1.0/python
--enable-languages=c,c++ --enable-obsolete --enable-secureplt --disable-werror
--with-system-zlib --enable-nls --without-included-gettext
--enable-checking=release --with-bugurl=https://bugs.gentoo.org/
--with-pkgversion='Gentoo 8.1.0-r3 p1.3' --disable-esp --enable-libstdcxx-time
--enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-clocale=gnu --enable-multilib --with-multilib-list=m32,m64
--disable-altivec --disable-fixed-point --enable-targets=all --disable-libgcj
--enable-libgomp --disable-libmudflap --disable-libssp --disable-libmpx
--disable-systemtap --enable-vtable-verify --enable-libvtv
--disable-libquadmath --enable-lto --without-isl --enable-libsanitizer
--enable-default-pie --enable-default-ssp
The preprocessed file, while being "just" a static array within a trivial
function, it's almost 6MB, so instead of attaching the file I have to post the
link:
https://raw.githubusercontent.com/bstaletic/gcc_ice/master/gcc/CodePoint.ii
When compiled with "g++ -S CodePoint.ii -o CodePoint.s", produces an empty
"CodePoint.s" and the following error:
g++: internal compiler error: Segmentation fault signal terminated program
cc1plus
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.gentoo.org/> for instructions.
- Simple changes that avoid ICE:
- Adding "-flto".
- Changing the "std::string"s in the "RawCodePoint" (lines 19480 to 19483)
struct to a "char*".
- Makes the compile time really short, produces the assembly.
- Changing the "std::string"s in the "RawCodePoint" struct to a "char[]".
- Somewhat shorter compile time, produces the assembly.
- Moving the static array into global scope.
- Changes that caused other strange behaviour, without compiling:
- Shortening the array by 30.000 elements (from the original >132.000)
caused gcc to exhaust all ram (8GB), take half of the swap (4GB), end up not
using the CPU (only ram, went over the 12GB) and after a long while I hit
ctrl-c.
Note: Compiling takes more than 8GB of ram.
>From gcc-bugs-return-609348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 15:19:01 2018
Return-Path: <gcc-bugs-return-609348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111580 invoked by alias); 6 Jul 2018 15:19:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108498 invoked by uid 48); 6 Jul 2018 15:18:56 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Fri, 06 Jul 2018 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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-86422-4-c0cLYL6tbR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00453.txt.bz2
Content-length: 1289
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-06
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
For me with GCC 8 branch rN I have
> /usr/bin/time g++-8 CodePoint.ii -fsyntax-only
13.09user 0.86system 0:13.96elapsed 100%CPU (0avgtext+0avgdata
2270556maxresident)k
> /usr/bin/time g++-8 CodePoint.ii -S
g++-8: internal compiler error: Segmentation fault signal terminated program
cc1plus
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.opensuse.org/> for instructions.
135.05user 1.72system 2:16.78elapsed 99%CPU (0avgtext+0avgdata
4050164maxresident)k
0inputs+160outputs (0major+1514630minor)pagefaults 0swaps
so this time it's not parsing but code-generation that blows up things.
Shortening the testcase probably makes things small enough to not hit
GCCs various "limits" where it gives up "optimizing" due to too large
code and non-linear algorithms.
Confirmed.
>From gcc-bugs-return-609349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 15:38:40 2018
Return-Path: <gcc-bugs-return-609349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64686 invoked by alias); 6 Jul 2018 15:38: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 64659 invoked by uid 48); 6 Jul 2018 15:38:35 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/86420] [9 regression] nextafter(0x1p-1022,0) is constant folded
Date: Fri, 06 Jul 2018 15:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86420-4-UJgD9ifujA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86420-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86420-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00454.txt.bz2
Content-length: 362
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86420
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to nsz from comment #0)
> gcc has no flag to say 'floating-point exceptions matter' (like
> -frounding-math for non-default rounding mode)
There is -ftrapping-math (on by default), although its exact meaning is
regularly questioned.
>From gcc-bugs-return-609350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 15:42:55 2018
Return-Path: <gcc-bugs-return-609350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2805 invoked by alias); 6 Jul 2018 15:42:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125497 invoked by uid 48); 6 Jul 2018 15:42:50 -0000
From: "boris.staletic at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Fri, 06 Jul 2018 15:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: boris.staletic 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-86422-4-wcj9mJezDk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00455.txt.bz2
Content-length: 427
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #2 from Boris Staletic <boris.staletic at gmail dot com> ---
> so this time it's not parsing but code-generation that blows up things.
That makes sense, when I was playing with the file, it took between 5 to 10
seconds to report syntax errors.
Another thing that avoids the ICE is using a "RawCodePoint" with less
"std::string"s.
Anything else I should try?
>From gcc-bugs-return-609351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 15:55:11 2018
Return-Path: <gcc-bugs-return-609351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71833 invoked by alias); 6 Jul 2018 15:55: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 71776 invoked by uid 48); 6 Jul 2018 15:55:06 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Fri, 06 Jul 2018 15:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_known_to_work cf_known_to_fail
Message-ID: <bug-86422-4-o0OgK9JjAe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00456.txt.bz2
Content-length: 999
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |compile-time-hog,
| |memory-hog
Known to work| |8.1.1
Known to fail| |8.1.0
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
On the tip of the GCC 8 branch the segfault is gone (r262478). I suspect the
error is memory use (it now peaks >20GB for me) and an unchecked allocation
or some 'int' size variable that overflows.
> /usr/bin/time /abuild/rguenther/obj/gcc/cc1plus -quiet CodePoint.ii
369.55user 7.52system 6:17.08elapsed 99%CPU (0avgtext+0avgdata
25329548maxresident)k
232inputs+604864outputs (0major+6777265minor)pagefaults 0swaps
Still needs tracking down thus.
>From gcc-bugs-return-609352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 16:06:58 2018
Return-Path: <gcc-bugs-return-609352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119808 invoked by alias); 6 Jul 2018 16:06: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 117895 invoked by uid 48); 6 Jul 2018 16:06:53 -0000
From: "fdumont at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86272] [6/7/8/9 Regression] __gnu_debug::string uses undefined __glibcxx_check_insert_range2
Date: Fri, 06 Jul 2018 16:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fdumont at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: fdumont at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86272-4-yjqmwFO50y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86272-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86272-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00457.txt.bz2
Content-length: 476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86272
François Dumont <fdumont at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from François Dumont <fdumont at gcc dot gnu.org> ---
Fixed on trunk and all impacted branches.
>From gcc-bugs-return-609353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 16:10:27 2018
Return-Path: <gcc-bugs-return-609353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4959 invoked by alias); 6 Jul 2018 16:10:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4898 invoked by uid 48); 6 Jul 2018 16:10:23 -0000
From: "boris.staletic at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Fri, 06 Jul 2018 16:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: boris.staletic 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-86422-4-R2e1t3tvht@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00458.txt.bz2
Content-length: 319
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #4 from Boris Staletic <boris.staletic at gmail dot com> ---
I get the segmentations fault when running cc1plus directly. No matter if I
pass -quiet or not.
So what's the next step?
Also, I have just noticed "Known to work: 8.1.1". Is that a mistake?
>From gcc-bugs-return-609354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 16:14:46 2018
Return-Path: <gcc-bugs-return-609354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11299 invoked by alias); 6 Jul 2018 16:14: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 3592 invoked by uid 48); 6 Jul 2018 16:14:40 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/86420] [9 regression] nextafter(0x1p-1022,0) is constant folded
Date: Fri, 06 Jul 2018 16: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-86420-4-KR8B41JEKl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86420-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86420-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00459.txt.bz2
Content-length: 726
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86420
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org,
| |jakub at gcc dot gnu.org
--- Comment #2 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
I think it's intended for -ftrapping-math to cover this.
Jakub's patch adding this folding functionality handles over/underflow cases,
but looks like the situation in comment #0 is not handled:
https://gcc.gnu.org/ml/gcc-patches/2018-04/msg01027.html
>From gcc-bugs-return-609355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 16:29:45 2018
Return-Path: <gcc-bugs-return-609355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31091 invoked by alias); 6 Jul 2018 16:29: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 31044 invoked by uid 48); 6 Jul 2018 16:29:40 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86340] GCC 8.1 produces broken code for m68k with optimization levels above -O1
Date: Fri, 06 Jul 2018 16:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.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: bug_status everconfirmed
Message-ID: <bug-86340-4-qQpCxFAlIr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86340-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86340-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00460.txt.bz2
Content-length: 347
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86340
Andreas Schwab <schwab@linux-m68k.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |UNCONFIRMED
Ever confirmed|1 |0
>From gcc-bugs-return-609356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 16:38:35 2018
Return-Path: <gcc-bugs-return-609356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40694 invoked by alias); 6 Jul 2018 16:38: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 40634 invoked by uid 55); 6 Jul 2018 16:38:29 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Fri, 06 Jul 2018 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.1.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86422-4-nTt9NHhZRi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00461.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #5 from rguenther at suse dot de <rguenther at suse dot de> ---
On July 6, 2018 6:10:23 PM GMT+02:00, "boris.staletic at gmail dot com"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
>
>--- Comment #4 from Boris Staletic <boris.staletic at gmail dot com>
>---
>I get the segmentations fault when running cc1plus directly. No matter
>if I
>pass -quiet or not.
>
>So what's the next step?
>
>Also, I have just noticed "Known to work: 8.1.1". Is that a mistake?
It works for me w/o segfault on the branch head.
>From gcc-bugs-return-609357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 16:40:19 2018
Return-Path: <gcc-bugs-return-609357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42608 invoked by alias); 6 Jul 2018 16: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 42551 invoked by uid 48); 6 Jul 2018 16:40:13 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82009] [F08] ICE with block construct
Date: Fri, 06 Jul 2018 16:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
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-82009-4-t06hrs3a6x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82009-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82009-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00462.txt.bz2
Content-length: 339
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82009
--- Comment #11 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
The missing local variable exists in the fortran dump and it shows as the first
item in the namespace passed to gfc_process_block_locals. However, it has no
backend decl.
I do not understand enough to proceed
>From gcc-bugs-return-609358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 16:53:43 2018
Return-Path: <gcc-bugs-return-609358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92268 invoked by alias); 6 Jul 2018 16: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 92242 invoked by uid 48); 6 Jul 2018 16:53:38 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86423] New: Omnetpp is slower on PowerPC using -ffast-math than not using -ffast-math
Date: Fri, 06 Jul 2018 16:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: meissner at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86423-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00463.txt.bz2
Content-length: 1836
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86423
Bug ID: 86423
Summary: Omnetpp is slower on PowerPC using -ffast-math than
not using -ffast-math
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: meissner at gcc dot gnu.org
Target Milestone: ---
I did some Spec 2006 runs, and one of the runs I was comparing normal speed
with -ffast-math. As expected a lot of SpecFP benchmarks were faster using the
-ffast-math option. However, 3 of the benchmarks were slower, including
omnetpp.
In particular, cMessageHeap::shiftup(int) [clone .part.16], which is the hotest
function took 2,442,614 cycles when compiled with -ffast-math, and 2,378,917
cycles when compiled without -ffast-math.
Looking at the profile within the function, we see:
The C++ name is cMessageHeap::shiftup(int) [clone .part.16].
Percent Percent | Samples Samples | Line # Filename
slowmath fastmath | slowmath fastmath | Line # Filename
-------- -------- | -------- -------- | ------ -----------
39.3521% 40.3151% | 936,158 984,740 | 198 cmsgheap.cc
17.4123% 10.5189% | 414,223 256,938 | 200 cmsgheap.cc
4.6070% 16.3806% | 109,595 400,114 | 43 cmsgheap.cc
14.2110% 14.2290% | 338,071 347,561 | 199 cmsgheap.cc
9.0102% 7.1333% | 214,345 174,237 | 45 cmsgheap.cc
7.4063% 1.8450% | 176,191 45,066 | 44 cmsgheap.cc
3.4912% 4.9701% | 83,054 121,401 | 196 cmsgheap.cc
2.3383% 2.3092% | 55,627 56,405 | 204 cmsgheap.cc
2.1165% 2.2862% | 50,347 55,841 | 46 cmsgheap.cc
>From gcc-bugs-return-609359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 17:01:19 2018
Return-Path: <gcc-bugs-return-609359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118276 invoked by alias); 6 Jul 2018 17:01:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117460 invoked by uid 48); 6 Jul 2018 17:01:12 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86424] New: Milc is slower on PowerPC using -ffast-math than without using -ffast-math
Date: Fri, 06 Jul 2018 17:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: meissner at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86424-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00464.txt.bz2
Content-length: 3169
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86424
Bug ID: 86424
Summary: Milc is slower on PowerPC using -ffast-math than
without using -ffast-math
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: meissner at gcc dot gnu.org
Target Milestone: ---
I did some Spec 2006 runs, and one of the runs I was comparing normal speed
with -ffast-math. As expected a lot of SpecFP benchmarks were faster using the
-ffast-math option. However, 3 of the benchmarks were slower, including milc.
The two hotest functions seem to be slower using -ffast-math:
slowmath fastmath | slowmath fastmath | Function
======== ======== | ======== ======== | ========
17.5310% 17.4259% | 5,489,872 5,580,840 | mult_su3_na
13.4533% 15.6660% | 4,212,953 5,017,232 | mult_adj_su3_mat_vec
Function mult_su3_na, 17.43 - 17.53% of total in 2 files
--------------------------------------------------------
Percent Percent | Samples Samples | Line # Filename
slowmath fastmath | slowmath fastmath | Line # Filename
-------- -------- | --------- --------- | ------ ----------
9.8993% 75.9216% | 543,453 4,237,070 | 38 m_mat_na.c
65.7913% 2.8468% | 3,611,855 158,877 | 33 m_mat_na.c
6.9169% | 386,020 | 40 m_mat_na.c
1.1277% 6.8534% | 61,915 382,477 | 48 m_mat_na.c
5.6730% | 311,441 | 49 m_mat_na.c
3.8513% 2.1642% | 211,433 120,784 | 46 m_mat_na.c
3.5253% | 193,542 | 45 m_mat_na.c
2.8633% | 157,188 | 41 m_mat_na.c
2.1619% | 118,689 | 39 m_mat_na.c
1.4727% | 80,847 | 43 m_mat_na.c
1.1929% | 65,486 | 36 m_mat_na.c
1.1072% | 61,790 | 44 m_mat_na.c
Function mult_adj_su3_mat_vec, 13.45 - 15.67% of total in 2 files
-----------------------------------------------------------------
Percent Percent | Samples Samples | Line # Filename
slowmath fastmath | slowmath fastmath | Line # Filename
-------- -------- | --------- --------- | ------ -----------
71.3008% 77.9373% | 3,003,867 3,910,288 | 116 m_amatvec.c
12.1258% 13.8781% | 510,853 696,296 | 126 m_amatvec.c
11.0201% | 464,272 | 121 m_amatvec.c
3.4868% | 174,944 | 123 m_amatvec.c
2.1345% 1.4971% | 89,925 75,109 | 129 m_amatvec.c
1.3833% | 58,278 | 132 m_amatvec.c
>From gcc-bugs-return-609360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 17:06:14 2018
Return-Path: <gcc-bugs-return-609360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20130 invoked by alias); 6 Jul 2018 17:06: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 20063 invoked by uid 48); 6 Jul 2018 17:06:09 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86425] New: Spec 2006 soplex seems to be slower on PowerPC using -ffast-math than without -ffast-math
Date: Fri, 06 Jul 2018 17:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: meissner at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86425-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00465.txt.bz2
Content-length: 6333
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86425
Bug ID: 86425
Summary: Spec 2006 soplex seems to be slower on PowerPC using
-ffast-math than without -ffast-math
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: meissner at gcc dot gnu.org
Target Milestone: ---
I did some Spec 2006 runs, and one of the runs I was comparing normal speed
with -ffast-math. As expected a lot of SpecFP benchmarks were faster using the
-ffast-math option. However, 3 of the benchmarks were slower, including
soplex.
The 4 hottest functions in soplex are all slower using -ffast-math:
Percent Percent | Samples Samples |
slowmath fastmath | slowmath fastmath | Function
======== ======== | ======== ======== | ========
32.3283% 33.0005% | 4,005,273 4,344,449 |
_ZN6soplex10SPxSteepPR8entered4ENS_5SPxIdEi
10.8967% 11.2537% | 1,350,038 1,481,531 |
_ZN6soplex8SSVector20assign2product4setupERKNS_5SVSetERKS0_
10.4306% 10.9159% | 1,292,285 1,437,055 | _ZN6soplex8SSVector5setupEv
7.0912% 7.5644% | 878,557 995,832 |
_ZN6soplex9CLUFactor16vSolveUrightNoNZEPdS1_Piid
Function _ZN6soplex10SPxSteepPR8entered4ENS_5SPxIdEi, 32.33 - 33.00% of total
in 2 files
----------------------------------------------------------------------------------------
The C++ name is soplex::SPxSteepPR::entered4(soplex::SPxId, int).
Percent Percent | Samples Samples | Line # Filename
slowmath fastmath | slowmath fastmath | Line # Filename
-------- -------- | --------- --------- | ------ -------------
50.4925% 51.6016% | 2,022,362 2,241,806 | 175 svector.h
15.1681% 15.6850% | 607,528 681,424 | 161 vector.h
13.8269% 14.9673% | 553,806 650,241 | 295 svector.h
10.0395% 8.8185% | 402,106 383,111 | 293 svector.h
5.0159% 1.5512% | 200,903 67,390 | 403 spxsteeppr.cc
2.3271% | 101,098 | 409 spxsteeppr.cc
2.2996% 1.9382% | 92,107 84,204 | 346 dataset.h
1.2001% 1.2045% | 48,071 52,327 | 402 spxsteeppr.cc
Function _ZN6soplex8SSVector20assign2product4setupERKNS_5SVSetERKS0_, 10.90 -
11.25% of total in 2 files
--------------------------------------------------------------------------------------------------------
The C++ name is soplex::SSVector::assign2product4setup(soplex::SVSet const&,
soplex::SSVector const&).
Percent Percent | Samples Samples | Line # Filename
slowmath fastmath | slowmath fastmath | Line # Filename
-------- -------- | -------- -------- | ------ -----------
60.5187% 59.4371% | 817,025 880,583 | 984 ssvector.cc
29.4260% 29.5739% | 397,262 438,147 | 981 ssvector.cc
4.9556% 5.2965% | 66,903 78,469 | 983 ssvector.cc
3.9925% 4.4770% | 53,900 66,328 | 980 ssvector.cc
Function _ZN6soplex8SSVector5setupEv, 10.43 - 10.92% of total in 2 files
------------------------------------------------------------------------
The C++ name is soplex::SSVector::setup().
Percent Percent | Samples Samples | Line # Filename
slowmath fastmath | slowmath fastmath | Line # Filename
-------- -------- | -------- -------- | ------ ------------
32.1165% 35.4180% | 415,037 508,976 | 220 ssvector.cc
22.2823% 25.1495% | 287,951 361,412 | 212 ssvector.cc
21.6266% 17.6770% | 279,478 254,029 | 216 ssvector.cc
20.2979% 19.6491% | 262,308 282,368 | 214 ssvector.cc
3.6149% 2.1003% | 46,715 30,182 | 193 spxdefines.h
Function _ZN6soplex9CLUFactor16vSolveUrightNoNZEPdS1_Piid, 7.09 - 7.56% of
total in 2 files
-------------------------------------------------------------------------------------------
The C++ name is soplex::CLUFactor::vSolveUrightNoNZ(double*, double*, int*,
int, double).
Percent Percent | Samples Samples | Line # Filename
slowmath fastmath | slowmath fastmath | Line # Filename
-------- -------- | -------- -------- | ------ ---------
14.3154% 11.5548% | 125,771 115,066 | 479 vsolve.cc
8.4523% 10.0335% | 74,259 99,917 | 72 vsolve.cc
9.5626% 7.6039% | 84,013 75,722 | 470 vsolve.cc
8.0533% 9.5256% | 70,753 94,859 | 73 vsolve.cc
8.0590% 6.2612% | 70,802 62,351 | 469 vsolve.cc
5.9002% 7.1628% | 51,836 71,330 | 490 vsolve.cc
6.3017% 4.9831% | 55,364 49,624 | 474 vsolve.cc
4.5466% 2.8041% | 39,944 27,924 | 502 vsolve.cc
3.7633% 4.3653% | 33,063 43,471 | 76 vsolve.cc
3.9925% 3.2432% | 35,076 32,297 | 477 vsolve.cc
3.0480% 3.6673% | 26,779 36,520 | 89 vsolve.cc
2.9868% 3.4680% | 26,241 34,535 | 491 vsolve.cc
2.8291% | 28,173 | 499 vsolve.cc
2.3567% 2.8041% | 20,705 27,924 | 91 vsolve.cc
2.6888% 2.1113% | 23,623 21,025 | 466 vsolve.cc
2.2936% 2.6018% | 20,151 25,910 | 78 vsolve.cc
1.7462% 1.4687% | 15,342 14,626 | 478 vsolve.cc
1.4010% 1.6444% | 12,309 16,375 | 102 vsolve.cc
1.3051% 1.6403% | 11,466 16,335 | 464 vsolve.cc
1.1126% 1.2585% | 9,775 12,533 | 498 vsolve.cc
1.0127% | 10,085 | 108 vsolve.cc
>From gcc-bugs-return-609361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 17:27:08 2018
Return-Path: <gcc-bugs-return-609361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128001 invoked by alias); 6 Jul 2018 17:27:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118015 invoked by uid 48); 6 Jul 2018 17:27:03 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/86420] [9 regression] nextafter(0x1p-1022,0) is constant folded
Date: Fri, 06 Jul 2018 17:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed attachments.created
Message-ID: <bug-86420-4-xYegDFsdDS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86420-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86420-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00466.txt.bz2
Content-length: 689
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86420
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-07-06
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 44362
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44362&action=edit
gcc9-pr86420.patch
Untested fix.
>From gcc-bugs-return-609362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 18:39:16 2018
Return-Path: <gcc-bugs-return-609362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90514 invoked by alias); 6 Jul 2018 18: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 90445 invoked by uid 48); 6 Jul 2018 18:39:11 -0000
From: "helloqirun at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86426] New: g++ ICE at on valid code in tree_operand_check, at tree.h:3615
Date: Fri, 06 Jul 2018 18:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: helloqirun 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-86426-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00467.txt.bz2
Content-length: 3387
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86426
Bug ID: 86426
Summary: g++ ICE at on valid code in tree_operand_check, at
tree.h:3615
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: helloqirun at gmail dot com
Target Milestone: ---
It affects versions from 4.8 to trunk.
g++4.6 emits errors. But clang++ can compile.
$ g++-trunk -v
Using built-in specs.
COLLECT_GCC=g++-trunk
COLLECT_LTO_WRAPPER=/home/absozero/trunk/root-gcc/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc/configure --prefix=/home/absozero/trunk/root-gcc
--enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
gcc version 9.0.0 20180706 (experimental) [trunk revision 262476] (GCC)
$ g++-trunk abc.c
abc.c: In substitution of ‘template<class ... T> int {anonymous}::f1(X<T, T
...>...) [with T = <missing>]’:
abc.c:4:26: required from here
abc.c:4:26: internal compiler error: tree check: expected class ‘expression’,
have ‘type’ (integer_type) in tree_operand_check, at tree.h:3615
int a1 = f1(X<int, int>());
^
0x78c90b tree_class_check_failed(tree_node const*, tree_code_class, char
const*, int, char const*)
../../gcc/gcc/tree.c:9403
0x651e95 expr_check(tree_node*, char const*, int, char const*)
../../gcc/gcc/tree.h:3286
0x651e95 tree_operand_check(tree_node*, int, char const*, int, char const*)
../../gcc/gcc/tree.h:3615
0x651e95 unify_pack_expansion
../../gcc/gcc/cp/pt.c:21125
0x97665d unify
../../gcc/gcc/cp/pt.c:21919
0x9758b3 unify
../../gcc/gcc/cp/pt.c:22116
0x976612 unify
../../gcc/gcc/cp/pt.c:21913
0x974e92 try_class_unification
../../gcc/gcc/cp/pt.c:20907
0x9766b5 unify
../../gcc/gcc/cp/pt.c:21950
0x97bb93 unify_one_argument
../../gcc/gcc/cp/pt.c:20161
0x97c914 unify_pack_expansion
../../gcc/gcc/cp/pt.c:21156
0x97dce3 type_unification_real
../../gcc/gcc/cp/pt.c:20300
0x97ee7f fn_type_unification(tree_node*, tree_node*, tree_node*, tree_node*
const*, unsigned int, tree_node*, unification_kind_t, int, conversion**, bool,
bool)
../../gcc/gcc/cp/pt.c:19660
0x826a02 add_template_candidate_real
../../gcc/gcc/cp/call.c:3212
0x827414 add_template_candidate
../../gcc/gcc/cp/call.c:3291
0x827414 add_candidates
../../gcc/gcc/cp/call.c:5532
0x827801 add_candidates
../../gcc/gcc/cp/call.c:4225
0x827801 perform_overload_resolution
../../gcc/gcc/cp/call.c:4233
0x829722 build_new_function_call(tree_node*, vec<tree_node*, va_gc,
vl_embed>**, int)
../../gcc/gcc/cp/call.c:4306
0x9a0dad finish_call_expr(tree_node*, vec<tree_node*, va_gc, vl_embed>**, bool,
bool, int)
../../gcc/gcc/cp/semantics.c:2536
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.
$ cat abc.c
template <typename...> struct X {};
namespace {
template <typename... T> int f1(X<T, T...>...);
int a1 = f1(X<int, int>());
}
>From gcc-bugs-return-609363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 20:20:26 2018
Return-Path: <gcc-bugs-return-609363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1806 invoked by alias); 6 Jul 2018 20:20: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 1745 invoked by uid 48); 6 Jul 2018 20:20:17 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86427] New: strlen not folded after strcpy into a zeroed-out local array
Date: Fri, 06 Jul 2018 20:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86427-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00468.txt.bz2
Content-length: 1515
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86427
Bug ID: 86427
Summary: strlen not folded after strcpy into a zeroed-out local
array
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
GCC eliminates a call to strlen() on a local copy into an uninitialized array
and from a character string of known length, but doesn't do the same when local
array is first zeroed-out.
$ cat c.c && gcc -O2 -S -Wall -Wextra -fdump-tree-optimized=/dev/stdout c.c
const char a[] = "123";
int f (void)
{
char d[8];
__builtin_strcpy (d, a); // eliminated
return __builtin_strlen (d); // folded
}
int g (void)
{
char d[8] = "";
__builtin_strcpy (d, a); // not eliminated
return __builtin_strlen (d); // not folded
}
;; Function f (f, funcdef_no=0, decl_uid=1899, cgraph_uid=1, symbol_order=1)
f ()
{
<bb 2> [local count: 1073741825]:
return 3;
}
;; Function g (g, funcdef_no=1, decl_uid=1903, cgraph_uid=2, symbol_order=2)
g ()
{
char d[8];
long unsigned int _1;
int _5;
<bb 2> [local count: 1073741825]:
d = "";
MEM[(char * {ref-all})&d] = MEM[(char * {ref-all})&a];
_1 = __builtin_strlen (&d);
_5 = (int) _1;
d ={v} {CLOBBER};
return _5;
}
>From gcc-bugs-return-609364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 20:32:15 2018
Return-Path: <gcc-bugs-return-609364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11210 invoked by alias); 6 Jul 2018 20:32: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 11157 invoked by uid 48); 6 Jul 2018 20:32:10 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86428] New: strlen of const array initialized with a string of the same length not folded
Date: Fri, 06 Jul 2018 20: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86428-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00469.txt.bz2
Content-length: 1525
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86428
Bug ID: 86428
Summary: strlen of const array initialized with a string of the
same length not folded
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
GCC folds strlen() calls with constant array arguments initialized with strings
fewer elements than the size of the array, but not those initialized with
strings with either a) the same number of elements or b) more. (a) is a
missing optimization opportunity, (b) results in unsafe code (reading past the
end of the array).
Clang folds all three kinds of strlen calls.
$ cat c.c && gcc -O2 -S -Wall -Wextra -fdump-tree-strlen=/dev/stdout c.c
const char a[4] = "123";
int f (void)
{
return __builtin_strlen (a); // folded
}
const char b[4] = "123\0"; // no warning
int g (void)
{
return __builtin_strlen (b); // not folded
}
;; Function f (f, funcdef_no=0, decl_uid=1899, cgraph_uid=1, symbol_order=1)
f ()
{
<bb 2> [local count: 1073741825]:
return 3;
}
;; Function g (g, funcdef_no=1, decl_uid=1903, cgraph_uid=2, symbol_order=3)
g ()
{
long unsigned int _1;
int _3;
<bb 2> [local count: 1073741825]:
_1 = __builtin_strlen (&b);
_3 = (int) _1;
return _3;
}
>From gcc-bugs-return-609365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 20:52:20 2018
Return-Path: <gcc-bugs-return-609365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113508 invoked by alias); 6 Jul 2018 20:52: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 113441 invoked by uid 48); 6 Jul 2018 20:52:16 -0000
From: "zub at linux dot fjfi.cvut.cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86429] New: lambda capture breaks constexpr-ness
Date: Fri, 06 Jul 2018 20:52: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zub at linux dot fjfi.cvut.cz
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86429-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00470.txt.bz2
Content-length: 1670
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86429
Bug ID: 86429
Summary: lambda capture breaks constexpr-ness
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: zub at linux dot fjfi.cvut.cz
Target Milestone: ---
This issue seems similar to bug 82643 but unlike that bug, this code compiles
fine in g++ 7.3 and fails to compile in g++ 8.1. Trying it out at wandabox.org
with gcc HEAD (201807) also results in compilation error.
The code requires boost hana:
====
#include <iostream>
#include <boost/hana.hpp>
int main()
{
namespace hana = boost::hana;
constexpr auto map = hana::make_map(hana::make_pair(hana::type_c<int>,
"foo"));
[&](auto v) {
constexpr auto x = boost::hana::find(map, v);
std::cout << *x << '\n';
}(hana::type_c<int>);
return 0;
}
====
With g++ 7.3 and clang++ it compiles OK and when run, prints out "foo\n" on
stdout. With g++ 8.1 I get:
$ g++-8 -std=c++17 gcc-8.1-not_contant.cc
gcc-8.1-not_contant.cc: In instantiation of ‘main()::<lambda(auto:1)> [with
auto:1 = boost::hana::type_impl<int>::_]’:
gcc-8.1-not_contant.cc:12:21: required from here
gcc-8.1-not_contant.cc:10:18: error: ‘__closure’ is not a constant expression
constexpr auto x = boost::hana::find(map, v);
^
While I'm not 100% sure the code is correct, even the error message is strange
(__closure?).
>From gcc-bugs-return-609366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 20:57:17 2018
Return-Path: <gcc-bugs-return-609366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122822 invoked by alias); 6 Jul 2018 20:57: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 122760 invoked by uid 48); 6 Jul 2018 20:57:13 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82643] lambda capture breaks constexpr-ness of non-static const constexpr member call on non-constexpr value/variable
Date: Fri, 06 Jul 2018 20: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: 8.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-82643-4-MJPHpQH2Wr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82643-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82643-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00471.txt.bz2
Content-length: 761
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82643
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-06
Ever confirmed|0 |1
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
GCC 6 rejected that code with a more sensible diagnostic:
c.cc:14:30: error: the value of 'f' is not usable in a constant expression
GCC 7 regressed to saying:
c.cc:14:30: error: '__closure' is not a constant expression
Clang and EDG both reject the code, but diagnosing different lines.
>From gcc-bugs-return-609367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 20:58:59 2018
Return-Path: <gcc-bugs-return-609367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125687 invoked by alias); 6 Jul 2018 20:58: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 125435 invoked by uid 48); 6 Jul 2018 20:58:53 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86429] [8/9 Regression] lambda capture breaks constexpr-ness
Date: Fri, 06 Jul 2018 20: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.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cf_known_to_work blocked short_desc everconfirmed cf_known_to_fail
Message-ID: <bug-86429-4-LnNsn58XfR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86429-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86429-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00472.txt.bz2
Content-length: 1047
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86429
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-06
Known to work| |7.3.0
Blocks| |54367
Summary|lambda capture breaks |[8/9 Regression] lambda
|constexpr-ness |capture breaks
| |constexpr-ness
Ever confirmed|0 |1
Known to fail| |8.1.0, 9.0
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Started to fail with r253601
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54367
[Bug 54367] [meta-bug] lambda expressions
>From gcc-bugs-return-609368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 20:59:52 2018
Return-Path: <gcc-bugs-return-609368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128125 invoked by alias); 6 Jul 2018 20:59:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127441 invoked by uid 48); 6 Jul 2018 20:59:45 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86429] [8/9 Regression] lambda capture breaks constexpr-ness
Date: Fri, 06 Jul 2018 20:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.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:
Message-ID: <bug-86429-4-yRD5j2ZPEi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86429-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86429-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00473.txt.bz2
Content-length: 230
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86429
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The diagnostic should not mention the __closure name, as that's an
implementation details (see also PR 82643)
>From gcc-bugs-return-609369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 21:03:05 2018
Return-Path: <gcc-bugs-return-609369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 986 invoked by alias); 6 Jul 2018 21:03:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 843 invoked by uid 48); 6 Jul 2018 21:03:00 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86428] strlen of const array initialized with a string of the same length not folded
Date: Fri, 06 Jul 2018 21: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-86428-4-qMKcb2r5uO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86428-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86428-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00474.txt.bz2
Content-length: 1067
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86428
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-07-06
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Another test case for the same limitation:
const char a[4] = "123";
const char b[4] = "123";
int f (void)
{
return __builtin_memcmp (a, b, 4); // folded
}
const char c[4] = "123\0"; // sizeof "123\0" == 5
int g (void)
{
return __builtin_memcmp (a, c, 4); // not folded
}
The solution seems simple: change the string_constant() function to avoid
considering as string constants the strings of the last form, i.e., those with
more initializers than fit in the array they're stored in).
>From gcc-bugs-return-609370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 21:06:29 2018
Return-Path: <gcc-bugs-return-609370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40141 invoked by alias); 6 Jul 2018 21:06: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 40024 invoked by uid 55); 6 Jul 2018 21:06:22 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86324] testsuite test divkc3-1.c FAILs when compiling with -mabi=ieeelongdouble
Date: Fri, 06 Jul 2018 21:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86324-4-KfMpWKgLgY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86324-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86324-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00475.txt.bz2
Content-length: 1432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86324
--- Comment #6 from Peter Bergner <bergner at gcc dot gnu.org> ---
Author: bergner
Date: Fri Jul 6 21:05:48 2018
New Revision: 262484
URL: https://gcc.gnu.org/viewcvs?rev=262484&root=gcc&view=rev
Log:
gcc/
PR target/86324
* target.def (translate_mode_attribute): New hook.
* targhooks.h (default_translate_mode_attribute): Declare.
* targhooks.c (default_translate_mode_attribute): New function.
* doc/tm.texi.in (TARGET_TRANSLATE_MODE_ATTRIBUTE): New hook.
* doc/tm.texi: Regenerate.
* config/rs6000/rs6000.c (TARGET_TRANSLATE_MODE_ATTRIBUTE): Define.
(rs6000_translate_mode_attribute): New function.
gcc/c-family/
PR target/86324
* c-attribs.c (handle_mode_attribute): Call new
translate_mode_attribute
target hook.
gcc/testsuite/
PR target/86324
gcc.target/powerpc/pr86324-1.c: New test.
gcc.target/powerpc/pr86324-2.c: Likewise.
Added:
trunk/gcc/testsuite/gcc.target/powerpc/pr86324-1.c
trunk/gcc/testsuite/gcc.target/powerpc/pr86324-2.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-attribs.c
trunk/gcc/config/rs6000/rs6000.c
trunk/gcc/doc/tm.texi
trunk/gcc/doc/tm.texi.in
trunk/gcc/target.def
trunk/gcc/targhooks.c
trunk/gcc/targhooks.h
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-609371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 21:43:18 2018
Return-Path: <gcc-bugs-return-609371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124657 invoked by alias); 6 Jul 2018 21:43: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 121954 invoked by uid 55); 6 Jul 2018 21:43:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86401] The "For constants M and N, if M == (1LL << cst) - 1 && (N & M) == M,..." opts are only in fold-const.c and in RTL
Date: Fri, 06 Jul 2018 21:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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-86401-4-HO693W3bfI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86401-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86401-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00476.txt.bz2
Content-length: 1082
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86401
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jul 6 21:42:41 2018
New Revision: 262485
URL: https://gcc.gnu.org/viewcvs?rev=262485&root=gcc&view=rev
Log:
PR tree-optimization/86401
* fold-const.c (fold_binary_loc) <case BIT_AND_EXPR>: Move the
((A & N) + B) & M -> (A + B) & M etc. optimization into ...
(fold_bit_and_mask): ... here. New helper function for match.pd.
* fold-const.h (fold_bit_and_mask): Declare.
* match.pd (((A & N) + B) & M -> (A + B) & M): New optimization.
* gcc.dg/tree-ssa/pr86401-1.c: New test.
* gcc.dg/tree-ssa/pr86401-2.c: New test.
* c-c++-common/rotate-9.c: New test.
Added:
trunk/gcc/testsuite/c-c++-common/rotate-9.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr86401-1.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr86401-2.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/fold-const.c
trunk/gcc/fold-const.h
trunk/gcc/match.pd
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-609373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 22:03:38 2018
Return-Path: <gcc-bugs-return-609373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62536 invoked by alias); 6 Jul 2018 22:03: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 62456 invoked by uid 48); 6 Jul 2018 22:03:34 -0000
From: "ville.voutilainen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/79133] lambda capture shadowing parameter & decltype confusion
Date: Fri, 06 Jul 2018 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: 7.0
X-Bugzilla-Keywords: accepts-invalid
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: ville.voutilainen at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-79133-4-NJ46QAHH4M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79133-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79133-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00478.txt.bz2
Content-length: 472
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79133
Ville Voutilainen <ville.voutilainen at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |husain.255 at gmail dot com
--- Comment #5 from Ville Voutilainen <ville.voutilainen at gmail dot com> ---
*** Bug 86361 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-609372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 06 22:03:37 2018
Return-Path: <gcc-bugs-return-609372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62518 invoked by alias); 6 Jul 2018 22:03: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 62405 invoked by uid 48); 6 Jul 2018 22:03:32 -0000
From: "ville.voutilainen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86361] Compilation failed while other compiler(clang) able to compile code in question
Date: Fri, 06 Jul 2018 22:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.5
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ville.voutilainen at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-86361-4-RYEwqPDA4M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86361-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86361-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00477.txt.bz2
Content-length: 693
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86361
Ville Voutilainen <ville.voutilainen at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |ville.voutilainen at gmail dot com
Resolution|--- |DUPLICATE
--- Comment #2 from Ville Voutilainen <ville.voutilainen at gmail dot com> ---
The lambda capturing k with a parameter named k is ill-formed as per Core DR
2211. Fix coming.
*** This bug has been marked as a duplicate of bug 79133 ***
>From gcc-bugs-return-609374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 07 01:25:08 2018
Return-Path: <gcc-bugs-return-609374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128889 invoked by alias); 7 Jul 2018 01:25: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 128787 invoked by uid 48); 7 Jul 2018 01:25:02 -0000
From: "zhonghao at pku dot org.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86430] New: ambiguous overload?
Date: Sat, 07 Jul 2018 01:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zhonghao at pku dot org.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86430-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00479.txt.bz2
Content-length: 1897
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86430
Bug ID: 86430
Summary: ambiguous overload?
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: zhonghao at pku dot org.cn
Target Milestone: ---
The code is as follow:
// snip
template<typename T>
struct Const { typedef void const type; };
template<typename T>
void f(T, typename Const<T>::type*) { } // T1
template<typename T>
void f(T, void const *) { } // T2
int main() { void *p = 0; f(0, p); }
// snap
g++ produces the following errors:
error: call of overloaded 'f(int, void*&)' is ambiguous
int main() { void *p = 0; f(0, p); }
I tried clang++. It accepts the above code. My understanding is as follows:
template<typename T>
void f(T, typename Const<T>::type*) // T1
template<typename T>
void f(T, void const *) // T2
We're going to deduce
(unique-1, Const<unique-1>::type*) ->
(T, void const*) // T1 -> T2
and
(unique-1, void const*) ->
(T, Const<T>::type*) // T2 -> T1
The first one takes T = unique-1 but fails at matching "void const*" to
"Const<unique-1>::type*". So this round fails for the second parameter.
The second one takes T = unique-1. The second is a non-deduced context, thus
not compared, and this does not mismatch. So this round succeeds for parameter
2.
So we have: For parameter 1, each template is at least as specialized as the
other one. For parameter 2, T1 -> T2 did not succeed, so T1 is not at least as
specialized as T2 - but not vice versa (T2 -> T1 suceeded). Thus for parameter
2, T2 is more specialized.
It follows that T2 overall is more specialized that T1.
As a result, the overload is not ambiguous. Please correct me, if I am wrong.
>From gcc-bugs-return-609375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 07 03:05:19 2018
Return-Path: <gcc-bugs-return-609375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47550 invoked by alias); 7 Jul 2018 03:05: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 47505 invoked by uid 48); 7 Jul 2018 03:05:14 -0000
From: "zhonghao at pku dot org.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86431] New: Legal code?
Date: Sat, 07 Jul 2018 03:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zhonghao at pku dot org.cn
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86431-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00480.txt.bz2
Content-length: 724
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86431
Bug ID: 86431
Summary: Legal code?
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: zhonghao at pku dot org.cn
Target Milestone: ---
The code is as follow:
struct A {
static int const B = sizeof B;
};
g++ rejects the code:
error: 'B' was not declared in this scope
static int const B = sizeof B;
The PoD should should be immediately after "B" and before the initializer, as
far as I can see, so this is valid code. BTW, clang++ accepts the code.
>From gcc-bugs-return-609376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 07 07:49:54 2018
Return-Path: <gcc-bugs-return-609376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77306 invoked by alias); 7 Jul 2018 07:49: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 76815 invoked by uid 55); 7 Jul 2018 07:48:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84711] AArch32 big-endian fails when taking subreg of a vector mode to a scalar mode.
Date: Sat, 07 Jul 2018 07:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.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: tnfchris at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84711-4-2vu1qkWrzc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00481.txt.bz2
Content-length: 539
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84711
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sat Jul 7 07:47:10 2018
New Revision: 262493
URL: https://gcc.gnu.org/viewcvs?rev=262493&root=gcc&view=rev
Log:
PR target/84711
* gcc.dg/vect/pr84711.c: Remove unnecessary sse
dg-require-effective-target. Add -msse not just on i386-*, but
on all i?86-* and x86_64-*.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/vect/pr84711.c
>From gcc-bugs-return-609377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 07 09:21:44 2018
Return-Path: <gcc-bugs-return-609377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1996 invoked by alias); 7 Jul 2018 09:21: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 1963 invoked by uid 48); 7 Jul 2018 09:21:39 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86431] Legal code?
Date: Sat, 07 Jul 2018 09:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-86431-4-aSSOGpIbiD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86431-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86431-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00482.txt.bz2
Content-length: 570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86431
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-07
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, I think this should be accepted.
>From gcc-bugs-return-609378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 07 09:55:22 2018
Return-Path: <gcc-bugs-return-609378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71781 invoked by alias); 7 Jul 2018 09:55: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 71723 invoked by uid 48); 7 Jul 2018 09:55:09 -0000
From: "tomilovanatoliy at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86432] New: ICE on capture VLA by reference
Date: Sat, 07 Jul 2018 09:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tomilovanatoliy at yandex dot ru
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86432-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00483.txt.bz2
Content-length: 1604
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86432
Bug ID: 86432
Summary: ICE on capture VLA by reference
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: tomilovanatoliy at yandex dot ru
Target Milestone: ---
Code:
#include <iostream>
int main(int argc, char * argv[])
{
char * v[argc];
for (int c = 0; c < argc; ++c) {
v[c] = argv[c];
}
[&v]
{
std::cout << sizeof(v) << std::endl;
}();
}
Error (command line `g++ prog.cc -Wall -Wextra -std=gnu++2a`):
prog.cc: In lambda function:
prog.cc:11:30: warning: '<anonymous>' is used uninitialized in this function
[-Wuninitialized]
std::cout << sizeof(v) << std::endl;
^
during RTL pass: expand
prog.cc:11:30: internal compiler error: in expand_expr_real_1, at expr.c:9907
0x591cb6 expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
../../source/gcc/expr.c:9901
0x89c9dd expand_expr
../../source/gcc/expr.h:279
0x89c9dd expand_expr_real_2(separate_ops*, rtx_def*, machine_mode,
expand_modifier)
../../source/gcc/expr.c:8418
0x79d0c7 expand_gimple_stmt_1
../../source/gcc/cfgexpand.c:3673
0x79d0c7 expand_gimple_stmt
../../source/gcc/cfgexpand.c:3734
0x79e75f expand_gimple_basic_block
../../source/gcc/cfgexpand.c:5765
0x7a38c6 execute
../../source/gcc/cfgexpand.c:6368
>From gcc-bugs-return-609379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 07 12:28:47 2018
Return-Path: <gcc-bugs-return-609379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26068 invoked by alias); 7 Jul 2018 12:28: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 26009 invoked by uid 48); 7 Jul 2018 12:28:41 -0000
From: "floop at floop dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86274] [7/8 Regression] SEGFAULT when logging std::to_string(NAN)
Date: Sat, 07 Jul 2018 12:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: patch, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: floop at floop dot cz
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86274-4-0Tb2FutIJs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86274-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86274-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00484.txt.bz2
Content-length: 170
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86274
--- Comment #18 from Filip Matzner <floop at floop dot cz> ---
Thank you everyone. Your efficiency is breathtaking.
>From gcc-bugs-return-609380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 07 13:09:26 2018
Return-Path: <gcc-bugs-return-609380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51719 invoked by alias); 7 Jul 2018 13:09: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 51653 invoked by uid 48); 7 Jul 2018 13:09:21 -0000
From: "coypu at sdf dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
Date: Sat, 07 Jul 2018 13: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: coypu at sdf dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-86383-4-JFy9OVjYcU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86383-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86383-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00485.txt.bz2
Content-length: 761
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
coypu <coypu at sdf dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |coypu at sdf dot org
--- Comment #5 from coypu <coypu at sdf dot org> ---
(In reply to Richard Earnshaw from comment #2)
> I'm not sure how relevant the netbsd-elf port is these days. I believe
> they've now moved onto an EABI based ABI. But no GCC port of that has been
> contributed.
hi,
I have a big working patch for netbsd/arm eabi.
I didn't test it against trunk/clean it up yet.
(https://v4.freshbsd.org/commit/netbsd/pkgsrc/yfUHHZvopo2aGFGA)
can I assign this to myself?
>From gcc-bugs-return-609381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 07 19:51:41 2018
Return-Path: <gcc-bugs-return-609381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4466 invoked by alias); 7 Jul 2018 19:51: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 4430 invoked by uid 48); 7 Jul 2018 19:51:37 -0000
From: "tiagomacarios at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86433] New: Shouldn't non const hashers also be allowed?
Date: Sat, 07 Jul 2018 19:51: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tiagomacarios 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-86433-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00486.txt.bz2
Content-length: 745
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86433
Bug ID: 86433
Summary: Shouldn't non const hashers also be allowed?
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: tiagomacarios at gmail dot com
Target Milestone: ---
https://godbolt.org/g/Z1cqm9
#include <unordered_set>
struct my_hash {
std::size_t operator() (int const&) /*const*/ {
return {}; // ~~~~~~~~~
}
};
std::unordered_set<int, my_hash> temp;
Shouldn't non-const hashers also be allowed?
http://eel.is/c++draft/hash.requirements#2
>From gcc-bugs-return-609382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 07 20:54:04 2018
Return-Path: <gcc-bugs-return-609382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122881 invoked by alias); 7 Jul 2018 20:54:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122835 invoked by uid 48); 7 Jul 2018 20:53:59 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86434] New: early string folding defeats strlen optimization
Date: Sat, 07 Jul 2018 20:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86434-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00487.txt.bz2
Content-length: 1523
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86434
Bug ID: 86434
Summary: early string folding defeats strlen optimization
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
When the call to strlen() below is folded to (3 - i) it is done very early, and
without setting the range of the result of the subtraction. This early folding
prevents later optimizations from determining that the result of the strlen()
call (or that of the subtraction) cannot be greater than 3. It's an example
that illustrates why early folding should be restricted to constants and leave
more advanced optimizations to later passes that have access to the results of
data flow analyses.
$ cat d.c && gcc -S -Wall -Wextra -fdump-tree-optimized=/dev/stdout d.cconst
char a[] = "123";
const char a[] = "123";
void f (int i)
{
if (__builtin_strlen (&a[i]) > 3)
__builtin_abort ();
}
;; Function f (f, funcdef_no=0, decl_uid=1957, cgraph_uid=0, symbol_order=1)
f (int i)
{
ssizetype _1;
ssizetype _2;
long unsigned int _3;
<bb 2> :
_1 = (ssizetype) i_4(D);
_2 = 3 - _1;
_3 = (long unsigned int) _2;
if (_3 > 3)
goto <bb 3>; [INV]
else
goto <bb 4>; [INV]
<bb 3> :
__builtin_abort ();
<bb 4> :
return;
}
>From gcc-bugs-return-609383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 07 21:27:08 2018
Return-Path: <gcc-bugs-return-609383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56011 invoked by alias); 7 Jul 2018 21:27: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 55985 invoked by uid 48); 7 Jul 2018 21:27:02 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86434] early string folding defeats strlen optimization and -Warray-bounds
Date: Sat, 07 Jul 2018 21:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords short_desc
Message-ID: <bug-86434-4-37k1hEK0dm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86434-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86434-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00488.txt.bz2
Content-length: 2734
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86434
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic,
| |missed-optimization
Summary|early string folding |early string folding
|defeats strlen optimization |defeats strlen optimization
| |and -Warray-bounds
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Here's another test showing the consequences of the early folding: In f()
below, the strlen() call isn't folded and so the -Warray-bounds warning has a
chance to detect the out-of-bounds index. But because the strlen() call is not
folded, the program will behave unpredictably. Folding the call to zero
instead after the warning has been issued would be safer and result in more
predictable results. In g(), on the other hand, the early folding prevents the
warning and also leads to a result that's inconsistent with one that would be
obtained by a valid program (also unsafe and difficult to debug).
$ cat d.c && gcc -O2 -S -Wall -Wextra -fdump-tree-strlen=/dev/stdout d.c
const char a[] = "123";
void f (int i)
{
if (i < 7)
i = 7;
const char *s = &a[i]; // -Warray-bounds
if (__builtin_strlen (s) > 3) // not folded (bad)
__builtin_puts ("impossible!");
}
void g (int i)
{
if (i < 7)
i = 7;
if (__builtin_strlen (&a[i]) > 3) // no -Warray-bounds, folded to true
__builtin_puts ("impossible!");
}
d.c: In function ‘f’:
d.c:8:19: warning: array subscript 7 is above array bounds of ‘const char[4]’
[-Warray-bounds]
const char *s = &a[i]; // -Warray-bounds
^~~~~
d.c:3:6: warning: offset ‘7’ outside bounds of constant string [-Warray-bounds]
void f (int i)
^
;; Function f (f, funcdef_no=0, decl_uid=1957, cgraph_uid=0, symbol_order=1)
f (int i)
{
const char * s;
long unsigned int _1;
sizetype _2;
<bb 2> [local count: 1073741825]:
i_8 = MAX_EXPR <i_4(D), 7>;
_2 = (sizetype) i_8;
s_5 = &a + _2;
_1 = __builtin_strlen (s_5);
if (_1 > 3)
goto <bb 3>; [33.00%]
else
goto <bb 4>; [67.00%]
<bb 3> [local count: 354334802]:
__builtin_puts ("impossible!");
<bb 4> [local count: 1073741824]:
return;
}
;; Function g (g, funcdef_no=1, decl_uid=1961, cgraph_uid=1, symbol_order=2)
g (int i)
{
<bb 2> [local count: 1073741825]:
__builtin_puts ("impossible!");
return;
}
>From gcc-bugs-return-609384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jul 07 21:49:57 2018
Return-Path: <gcc-bugs-return-609384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9093 invoked by alias); 7 Jul 2018 21:49: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 9066 invoked by uid 48); 7 Jul 2018 21:49:51 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86428] strlen of const array initialized with a string of the same length not folded
Date: Sat, 07 Jul 2018 21:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-86428-4-wKO50Ggvhi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86428-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86428-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00489.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86428
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00377.html
>From gcc-bugs-return-609385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 08:01:43 2018
Return-Path: <gcc-bugs-return-609385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102187 invoked by alias); 8 Jul 2018 08:00:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101565 invoked by uid 48); 8 Jul 2018 07:59:59 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86435] New: -fsemantic-interposition does not appear to have any effect
Date: Sun, 08 Jul 2018 08:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-86435-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00490.txt.bz2
Content-length: 1006
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86435
Bug ID: 86435
Summary: -fsemantic-interposition does not appear to have any
effect
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: fw at gcc dot gnu.org
Target Milestone: ---
Target: x86_64
Consider this program:
int a;
int
f1 (int a)
{
return a;
}
int
f2 (void)
{
return f1 (a) - a;
}
Compiling it with -O2 -fsemantic-interposition or -O2
-fno-semantic-interposition (in case the sense of the options in the
documentation is reversed) both results in this:
.globl f2
.type f2, @function
f2:
.LFB1:
.cfi_startproc
xorl %eax, %eax
ret
.cfi_endproc
So interposition of f1 is not possible.
-fno-inline-functions does not make a difference.
>From gcc-bugs-return-609387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 11:44:40 2018
Return-Path: <gcc-bugs-return-609387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1030 invoked by alias); 8 Jul 2018 11:44: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 991 invoked by uid 48); 8 Jul 2018 11:44:36 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86421] OpenMP declare simd linear ref in module causes gfortran to bail out
Date: Sun, 08 Jul 2018 11: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: 8.1.0
X-Bugzilla-Keywords: error-recovery, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-86421-4-3RK7u7Rgtf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86421-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86421-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00492.txt.bz2
Content-length: 409
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86421
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-08
Ever confirmed|0 |1
>From gcc-bugs-return-609386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 11:44:29 2018
Return-Path: <gcc-bugs-return-609386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130957 invoked by alias); 8 Jul 2018 11:44: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 130920 invoked by uid 48); 8 Jul 2018 11:44:23 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86421] OpenMP declare simd linear ref in module causes gfortran to bail out
Date: Sun, 08 Jul 2018 11: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: 8.1.0
X-Bugzilla-Keywords: error-recovery, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-86421-4-xsm2MDIhZb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86421-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86421-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00491.txt.bz2
Content-length: 614
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86421
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
DECLARE SIMD has been introduced at revision r242037 and it seems that the test
is failing since then.
If GCC has been configured with --enable-checking=yes, the ICE is
in gfc_format_decoder, at fortran/error.c:947
>From gcc-bugs-return-609388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 11:51:53 2018
Return-Path: <gcc-bugs-return-609388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27768 invoked by alias); 8 Jul 2018 11:51:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27658 invoked by uid 48); 8 Jul 2018 11:51:48 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86435] -fsemantic-interposition does not appear to have any effect
Date: Sun, 08 Jul 2018 11:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-86435-4-HNl4SW7Ti4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86435-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86435-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00493.txt.bz2
Content-length: 637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86435
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |amonakov at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #1 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Without -fpic, f1 is considered not interposable. With -fpic, gcc needs
-fsemantic-interposition to optimize f2 to 'return 0;'.
>From gcc-bugs-return-609389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 12:17:29 2018
Return-Path: <gcc-bugs-return-609389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88309 invoked by alias); 8 Jul 2018 12:17: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 88255 invoked by uid 48); 8 Jul 2018 12:17:24 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86435] -fsemantic-interposition does not appear to have any effect
Date: Sun, 08 Jul 2018 12:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw 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-86435-4-LqsvBIkRAz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86435-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86435-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00494.txt.bz2
Content-length: 305
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86435
--- Comment #2 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #1)
> Without -fpic, f1 is considered not interposable.
That's an odd assumption. ld can interpose the definition with -z muldefs,
after all.
>From gcc-bugs-return-609390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 14:31:11 2018
Return-Path: <gcc-bugs-return-609390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53223 invoked by alias); 8 Jul 2018 14:31: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 52865 invoked by uid 48); 8 Jul 2018 14:30:27 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86435] -fsemantic-interposition does not appear to have any effect
Date: Sun, 08 Jul 2018 14: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.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-86435-4-m6d7K38zEf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86435-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86435-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00495.txt.bz2
Content-length: 223
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86435
--- Comment #3 from Andreas Schwab <schwab@linux-m68k.org> ---
But the assembler is allowed to resolve the reference directly without the
possibility for interposition.
>From gcc-bugs-return-609391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 15:06:15 2018
Return-Path: <gcc-bugs-return-609391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96880 invoked by alias); 8 Jul 2018 15:06: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 96809 invoked by uid 48); 8 Jul 2018 15:06:10 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86417] [9 Regression] FAIL: libgomp.fortran/alloc-comp-3.f90 -O0 (test for excess errors)
Date: Sun, 08 Jul 2018 15:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-86417-4-QZS5SOChl6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86417-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86417-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00496.txt.bz2
Content-length: 595
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86417
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-08
CC| |foreese at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Caused/exposed by revision r262442.
>From gcc-bugs-return-609392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 16:05:03 2018
Return-Path: <gcc-bugs-return-609392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51880 invoked by alias); 8 Jul 2018 16:05: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 51820 invoked by uid 48); 8 Jul 2018 16:04:57 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86435] -fsemantic-interposition does not appear to have any effect
Date: Sun, 08 Jul 2018 16: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw 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-86435-4-ORDCE179Ee@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86435-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86435-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00497.txt.bz2
Content-length: 518
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86435
--- Comment #4 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to Andreas Schwab from comment #3)
> But the assembler is allowed to resolve the reference directly without the
> possibility for interposition.
Hmm. The assembler would still produce a relocation even if there was a direct
call to a locally defined function. However, the link editor does not appear
to preserve a PLT call in the main program, preventing interposition at link
time.
>From gcc-bugs-return-609393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 17:25:21 2018
Return-Path: <gcc-bugs-return-609393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87655 invoked by alias); 8 Jul 2018 17:25: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 87596 invoked by uid 48); 8 Jul 2018 17:25:16 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86220] [9 Regression] ICE in gfc_conv_structure, at fortran/trans-expr.c:7789
Date: Sun, 08 Jul 2018 17: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-86220-4-VpDouS7lbE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86220-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86220-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00498.txt.bz2
Content-length: 689
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86220
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-08
Ever confirmed|0 |1
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> > Introduced between 20180520 and 20180527.
>
> It wasn't introduced. It was uncovered. :-)
May be r260808.
Note that the test compiles, but gives a wrong result with the patch in pr49278
comment 2.
>From gcc-bugs-return-609394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 17:29:57 2018
Return-Path: <gcc-bugs-return-609394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90296 invoked by alias); 8 Jul 2018 17:29:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90262 invoked by uid 48); 8 Jul 2018 17:29:53 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86167] allocation variable length character array in derived type incorrect
Date: Sun, 08 Jul 2018 17: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on target_milestone everconfirmed
Message-ID: <bug-86167-4-N3GCcTwxko@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86167-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86167-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00499.txt.bz2
Content-length: 920
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86167
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-08
Target Milestone|--- |9.0
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed from 6.4.0 up to trunk (9.0). Compiling the test with 5.5.0 gives
pr86167.f90:14:11:
allocate(a2,source=a1)
1
Error: Array specification required in ALLOCATE statement at (1)
pr86167.f90:16:11:
allocate(tb%a1,source=a2)
1
Error: Array specification required in ALLOCATE statement at (1)
>From gcc-bugs-return-609395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 17:34:40 2018
Return-Path: <gcc-bugs-return-609395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92725 invoked by alias); 8 Jul 2018 17:34: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 92658 invoked by uid 48); 8 Jul 2018 17:34:36 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86330] False positive warnings about uninitialized offset/lbound/ubound when allocating on assignment
Date: Sun, 08 Jul 2018 17:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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-86330-4-jWoIsChEJf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00500.txt.bz2
Content-length: 595
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86330
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Looks like a duplicate of bug 85855.
IMO it is a duplicate of pr85855 and probably other PRs.
*** This bug has been marked as a duplicate of bug 85855 ***
>From gcc-bugs-return-609396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 17:34:40 2018
Return-Path: <gcc-bugs-return-609396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92736 invoked by alias); 8 Jul 2018 17:34: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 92677 invoked by uid 48); 8 Jul 2018 17:34:37 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85855] [7/8/9 Regression] (Maybe) uninitialized descriptor fields of an allocatable array component of a function result
Date: Sun, 08 Jul 2018 17:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85855-4-Hu7WS9fMB7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00501.txt.bz2
Content-length: 456
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85855
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tomastrnka at gmx dot com
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
*** Bug 86330 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-609397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 17:39:13 2018
Return-Path: <gcc-bugs-return-609397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95599 invoked by alias); 8 Jul 2018 17:39: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 95554 invoked by uid 48); 8 Jul 2018 17:39:08 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86416] [OMPVV SOLLVE] Defaultmap issues on OpenMP 4.5
Date: Sun, 08 Jul 2018 17:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-86416-4-RLVVEzOvVE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86416-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86416-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00502.txt.bz2
Content-length: 597
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86416
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-08
CC| |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed from 7.3.0 up to trunk (9.0).
>From gcc-bugs-return-609398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 18:03:53 2018
Return-Path: <gcc-bugs-return-609398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23548 invoked by alias); 8 Jul 2018 18:03: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 23505 invoked by uid 48); 8 Jul 2018 18:03:49 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86262] allocation with non-parameter array expression as SOURCE sets LBOUND to 0
Date: Sun, 08 Jul 2018 18: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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-86262-4-wdUuC0XJCC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86262-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86262-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00503.txt.bz2
Content-length: 701
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86262
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Though I did search, right after I submitted the bug I saw it is already filed,
> e.g. as Bug 85534. Sorry for that, I guess my report does not add much.
I am not sure there is no other duplicates.
*** This bug has been marked as a duplicate of bug 85534 ***
>From gcc-bugs-return-609399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 18:03:53 2018
Return-Path: <gcc-bugs-return-609399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23590 invoked by alias); 8 Jul 2018 18:03: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 23517 invoked by uid 48); 8 Jul 2018 18:03:49 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85534] allocation of array with source give shifted index
Date: Sun, 08 Jul 2018 18: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: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85534-4-tuPVSULS4O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85534-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85534-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00504.txt.bz2
Content-length: 464
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85534
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simon.kluepfel at gmail dot com
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
*** Bug 86262 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-609400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 18:25:27 2018
Return-Path: <gcc-bugs-return-609400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42851 invoked by alias); 8 Jul 2018 18:25: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 26336 invoked by uid 48); 8 Jul 2018 18:25:04 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86248] [7/8/9 Regression] LEN_TRIM in specification expression causes link failure
Date: Sun, 08 Jul 2018 18: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: 8.1.0
X-Bugzilla-Keywords: link-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_known_to_work keywords cf_reconfirmed_on cc everconfirmed short_desc target_milestone cf_known_to_fail
Message-ID: <bug-86248-4-Q8RwBb9qhg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86248-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86248-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00505.txt.bz2
Content-length: 1171
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86248
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Known to work| |6.4.0
Keywords| |link-failure
Last reconfirmed| |2018-07-08
CC| |pault at gcc dot gnu.org
Ever confirmed|0 |1
Summary|LEN_TRIM in specification |[7/8/9 Regression] LEN_TRIM
|expression causes link |in specification expression
|failure |causes link failure
Target Milestone|--- |7.4
Known to fail| |7.3.0, 8.1.0, 9.0
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
The link failure disappear if the two files are merged in one.
Probably caused by r243478 (pr44265).
>From gcc-bugs-return-609401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 18:26:33 2018
Return-Path: <gcc-bugs-return-609401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43989 invoked by alias); 8 Jul 2018 18:26: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 43939 invoked by uid 48); 8 Jul 2018 18:26:29 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86268] [9.0] Error on correct code with PDTs
Date: Sun, 08 Jul 2018 18:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on blocked everconfirmed
Message-ID: <bug-86268-4-krV306ETUX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86268-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86268-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00506.txt.bz2
Content-length: 679
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86268
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-08
Blocks| |82173
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82173
[Bug 82173] [meta-bug] Parameterized derived type errors
>From gcc-bugs-return-609402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 18:32:00 2018
Return-Path: <gcc-bugs-return-609402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47478 invoked by alias); 8 Jul 2018 18:32:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47422 invoked by uid 48); 8 Jul 2018 18:31:56 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86417] [9 Regression] FAIL: libgomp.fortran/alloc-comp-3.f90 -O0 (test for excess errors)
Date: Sun, 08 Jul 2018 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: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86417-4-osJM8UaEa7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86417-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86417-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00507.txt.bz2
Content-length: 918
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86417
--- Comment #9 from janus at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #8)
> Caused/exposed by revision r262442.
Thanks for the info, Dominique.
The following patch seems to be sufficient to fix the regression:
Index: expr.c
===================================================================
--- expr.c (revision 262446)
+++ expr.c (working copy)
@@ -4648,6 +4648,8 @@ gfc_generate_initializer (gfc_typespec *ts, bool g
if (val == false)
return NULL;
}
+ if (!ctor->expr->where.nextc || !ctor->expr->where.lb)
+ ctor->expr->where = init->where;
}
gfc_constructor_append (&init->value.constructor, ctor);
>From gcc-bugs-return-609403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 20:33:40 2018
Return-Path: <gcc-bugs-return-609403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83746 invoked by alias); 8 Jul 2018 20:33:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77236 invoked by uid 48); 8 Jul 2018 20:33:34 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86433] Shouldn't non const hashers also be allowed?
Date: Sun, 08 Jul 2018 20:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.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-86433-4-DTYeVIPpqr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86433-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86433-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00508.txt.bz2
Content-length: 651
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86433
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> ---
No. It says "h is a value of type (possibly const) H" and that means the
requirements must be met for an object of type H, where H might be a const
type. If your hasher only has a non-const member it can not meet the
requirements.
>From gcc-bugs-return-609404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 21:33:36 2018
Return-Path: <gcc-bugs-return-609404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129508 invoked by alias); 8 Jul 2018 21:33: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 129428 invoked by uid 48); 8 Jul 2018 21:33:29 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49263] SH Target: underutilized "TST #imm, R0" instruction
Date: Sun, 08 Jul 2018 21:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: olegendo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-49263-4-0R6CtmoOax@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49263-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49263-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00509.txt.bz2
Content-length: 1119
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49263
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #27 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Oleg Endo from comment #26)
> Author: olegendo
> Date: Mon Jan 26 23:56:05 2015
> New Revision: 220144
>
> URL: https://gcc.gnu.org/viewcvs?rev=220144&root=gcc&view=rev
> Log:
> gcc/
> PR target/49263
> * config/sh/sh.c (sh_split_treg_set_expr): Invoke emit_insn before
> remove_insn.
> * config/sh/sh.md (tstsi_t): Don't try to optimize constant with right
> shifts if it already fits into K08.
>
> gcc/testsuite/
> PR target/49263
> * gcc.target/sh/pr49263-4.c: New.
>
>
> Added:
> trunk/gcc/testsuite/gcc.target/sh/pr49263-4.c
> Modified:
> trunk/gcc/ChangeLog
> trunk/gcc/config/sh/sh.c
> trunk/gcc/config/sh/sh.md
> trunk/gcc/testsuite/ChangeLog
Did this fix it?
>From gcc-bugs-return-609405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 21:37:25 2018
Return-Path: <gcc-bugs-return-609405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41502 invoked by alias); 8 Jul 2018 21:37: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 39104 invoked by uid 48); 8 Jul 2018 21:37:20 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/42047] --with-gmp= include directory is used for build targets
Date: Sun, 08 Jul 2018 21:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc see_also
Message-ID: <bug-42047-4-04GwzgVwnF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-42047-4@http.gcc.gnu.org/bugzilla/>
References: <bug-42047-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00510.txt.bz2
Content-length: 620
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42047
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=34818
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
Possibly related to bug 34818 and/or some other build bugs mentioning gmp...
>From gcc-bugs-return-609406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 22:14:23 2018
Return-Path: <gcc-bugs-return-609406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94136 invoked by alias); 8 Jul 2018 22:14:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94004 invoked by uid 48); 8 Jul 2018 22:14:16 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/44566] configuration with multiple targets / backends is not supported.
Date: Sun, 08 Jul 2018 22:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc see_also dependson everconfirmed
Message-ID: <bug-44566-4-py0T1HSSHt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-44566-4@http.gcc.gnu.org/bugzilla/>
References: <bug-44566-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00511.txt.bz2
Content-length: 1404
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44566
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-08
CC| |egallager at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=44431,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=44362
Depends on| |44512
Ever confirmed|0 |1
--- Comment #9 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jorn Wolfgang Rennecke from comment #1)
> (In reply to comment #0)
> > multi-target configurations, thus PR44362 doesn't actually block.
>
> Sorry, I meant PR44431. But then, the remaining part of PR44362 also
> doesn't block PR44566 (and not PR44433 either).
Sounds related enough for "See Also" at least. Anyways, confirmed.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44512
[Bug 44512] --enable-build-with-cxx bootstrap fails in revision 160669
>From gcc-bugs-return-609407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 22:16:38 2018
Return-Path: <gcc-bugs-return-609407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97120 invoked by alias); 8 Jul 2018 22:16:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96584 invoked by uid 48); 8 Jul 2018 22:16:28 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/52082] Memory loads not rematerialized
Date: Sun, 08 Jul 2018 22:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-52082-4-XDilTGUZZD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52082-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52082-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00512.txt.bz2
Content-length: 631
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52082
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #0)
> On the following testcase at -O2 (distilled from genautomata.c):
Missed optimizations for genautomata.c should get a higher priority, IMO, given
how slowly the genautomata executable runs...
>From gcc-bugs-return-609408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 22:19:59 2018
Return-Path: <gcc-bugs-return-609408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112930 invoked by alias); 8 Jul 2018 22:19: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 112867 invoked by uid 48); 8 Jul 2018 22:19:54 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/58489] ICE: in reload_cse_simplify_operands, at postreload.c:411
Date: Sun, 08 Jul 2018 22:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-58489-4-aF7Az8ecix@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58489-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58489-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00513.txt.bz2
Content-length: 1656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58489
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
CC| |egallager at gcc dot gnu.org
Resolution|--- |WORKSFORME
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Ramana Radhakrishnan from comment #3)
> (In reply to Timo Teräs from comment #2)
> > I got this fixed. It seems genautomata does not work properly if it is built
> > with -fPIC. Since PIE/PIC get added automatically in alpine toolchain it
> > caused this.
> >
> > For now I'm adding explicitly -fno-PIC to genautomata compilation. However,
> > it would be better if genautomata could be fixed to:
> > - abort compilation if genautomata failed to do it's job properly
> > - fix genautomata to work even if compiled with -fPIC
>
> Interesting observation and interesting that the "broken automaton" managed
> to build the whole of gcc and the run time support libraries in gcc and
> presumably glibc.
>
> If it was genautomata that doesn't work properly when built with PIC can you
> reduce the failure point in genautomata. Without more details or better
> input testcases it's very hard to reduce this in any other way or form
> especially as I cannot reproduce the issue with a new top of tree 4.8
> toolchain.
bug has been stuck in WAITING long enough without being reproduced for it to be
closed now.
>From gcc-bugs-return-609409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 22:22:10 2018
Return-Path: <gcc-bugs-return-609409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114646 invoked by alias); 8 Jul 2018 22:22: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 114584 invoked by uid 48); 8 Jul 2018 22:22:06 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/77510] genautomata memory footprint for MIPS
Date: Sun, 08 Jul 2018 22:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords: build, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc see_also everconfirmed
Message-ID: <bug-77510-4-t4dgZcywdJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77510-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77510-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00514.txt.bz2
Content-length: 845
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77510
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-08
CC| |egallager at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=70473
Ever confirmed|0 |1
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
I haven't tested for MIPS specifically but I believe it given the genautomata
memory footprint on other architectures, so I'll confirm.
>From gcc-bugs-return-609410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 22:23:41 2018
Return-Path: <gcc-bugs-return-609410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115801 invoked by alias); 8 Jul 2018 22:23:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115754 invoked by uid 48); 8 Jul 2018 22:23:37 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61807] genautomata.c fails to compile
Date: Sun, 08 Jul 2018 22: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: 4.9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-61807-4-tUNSCqY5PS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61807-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00515.txt.bz2
Content-length: 674
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61807
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2018-07-08
CC| |egallager at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
are you still seeing this issue with newer versions of GCC?
>From gcc-bugs-return-609411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 08 22:34:49 2018
Return-Path: <gcc-bugs-return-609411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23955 invoked by alias); 8 Jul 2018 22:34: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 23905 invoked by uid 48); 8 Jul 2018 22:34:44 -0000
From: "petschy at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86436] New: IPA-ICF: miissed optimization at class template member functions
Date: Sun, 08 Jul 2018 22:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: petschy 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-86436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00516.txt.bz2
Content-length: 6856
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86436
Bug ID: 86436
Summary: IPA-ICF: miissed optimization at class template member
functions
Product: gcc
Version: 8.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: petschy at gmail dot com
Target Milestone: ---
Created attachment 44363
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44363&action=edit
test case
The attached source has two class templates: NonFoldable<int> and
Foldable<int>.
The nonfoldable version uses the int template param in Bar() (a leaf function
in the call graph) to do a computation, so different template params result in
different Bar()'s, so they can't be folded, and because of that neither its
callers. So far so good.
Foldable<int> is very similar, but puts the template param into a const member
variable in the ctor and Bar() uses that member. So now the value is different,
but, the code is exacly the same.
Some asm dump of x86-64 code:
7.3.1 (9bcef54ae6c7df97b276a7fa8da4c90d2452333c):
Dump of assembler code for function nf_foo_0(NonFoldable<0>&, int):
0x00000000004004d0 <+0>: mov %esi,%edi
0x00000000004004d2 <+2>: jmp 0x4004a0 <NonFoldable<0>::Foo(int)>
Dump of assembler code for function nf_bar_0(NonFoldable<0>&, int):
0x00000000004004e0 <+0>: mov %esi,%edi
0x00000000004004e2 <+2>: jmp 0x400490 <NonFoldable<0>::Bar(int)>
Dump of assembler code for function NonFoldable<0>::Foo(int):
0x00000000004004a0 <+0>: jmp 0x400490 <NonFoldable<0>::Bar(int)>
Dump of assembler code for function NonFoldable<0>::Bar(int):
0x0000000000400490 <+0>: mov %edi,%eax
0x0000000000400492 <+2>: retq
Dump of assembler code for function nf_foo_42(NonFoldable<42>&, int):
0x00000000004004f0 <+0>: mov %esi,%edi
0x00000000004004f2 <+2>: jmp 0x4004c0 <NonFoldable<42>::Foo(int)>
Dump of assembler code for function nf_bar_42(NonFoldable<42>&, int):
0x0000000000400500 <+0>: mov %esi,%edi
0x0000000000400502 <+2>: jmp 0x4004b0 <NonFoldable<42>::Bar(int)>
Dump of assembler code for function NonFoldable<42>::Foo(int):
0x00000000004004c0 <+0>: jmp 0x4004b0 <NonFoldable<42>::Bar(int)>
Dump of assembler code for function NonFoldable<42>::Bar(int):
0x00000000004004b0 <+0>: lea 0x2a(%rdi),%eax
0x00000000004004b3 <+3>: retq
Dump of assembler code for function f_foo_0(Foldable<0>&, int):
0x0000000000400510 <+0>: jmpq 0x400560 <Foldable<0>::Foo(int)>
Dump of assembler code for function f_bar_0(Foldable<0>&, int):
0x0000000000400520 <+0>: jmpq 0x400550 <Foldable<0>::Bar(int)>
Dump of assembler code for function Foldable<0>::Foo(int):
0x0000000000400560 <+0>: jmpq 0x400550 <Foldable<0>::Bar(int)>
Dump of assembler code for function Foldable<0>::Bar(int):
0x0000000000400550 <+0>: mov (%rdi),%eax
0x0000000000400552 <+2>: add %esi,%eax
0x0000000000400554 <+4>: retq
Dump of assembler code for function f_foo_42(Foldable<42>&, int):
0x0000000000400530 <+0>: jmpq 0x400580 <Foldable<42>::Foo(int)>
Dump of assembler code for function f_bar_42(Foldable<42>&, int):
0x0000000000400540 <+0>: jmpq 0x400570 <Foldable<42>::Bar(int)>
Dump of assembler code for function Foldable<42>::Foo(int):
0x0000000000400580 <+0>: jmpq 0x400570 <Foldable<42>::Bar(int)>
Dump of assembler code for function Foldable<42>::Bar(int):
0x0000000000400570 <+0>: mov (%rdi),%eax
0x0000000000400572 <+2>: add %esi,%eax
0x0000000000400574 <+4>: retq
Under 7.3.1 no identical code folding happens at all. 8.1.1 & 9.0.0 only folds
Foldable<0>::Bar with Foldable<42>::Bar(). Foo(), and the free standing
functions calling these members are not recognized as foldable.
I haven't thought really hard about the folding rules. Checking each fn against
each fn globally by default is probably waaay too much work. However,
instantiations of class template members are easy candidates. Or, on a wider
scale, functions where the number and type of the args and the return type is
the same, OR at least the same size. The scope should be configurable, eg
compilation unit or shared lib / executable (LTO).
My quick (and probably incomplete) rules would be:
- if the functions are leaf OR call the same or foldable functions only
- the accessed global variables (incl static members) are the same
- the accessed member variables' offsets are the same, and the types are the
same, OR at least they have the same size and the computations have the same
results bitwise. Eg signed vs unsigned ints of the same size: reading a member
variable and passing it to a foldable fn. Performing some computation, eg
addition, but not doing anything that would make a difference, like checking
the sign of the result, etc.
This means that eg member functions of totally unrelated classes could be
folded, if the accessed members are the same type or similar enough in relation
to the operations performed.
Bug #80277 is also about ICF, but there are only free standing functions.
Used platform was Debian Stretch AMD64, the GCC versions tested:
$ g++-7.3.1 -v
Using built-in specs.
COLLECT_GCC=g++-7.3.1
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-linux-gnu/7.3.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../configure --enable-languages=c,c++ --disable-multilib
--program-suffix=-7.3.1 --disable-bootstrap CFLAGS='-Ofast -march=native
-mtune=native' CXXFLAGS='-Ofast -march=native -mtune=native' CC=gcc-7.3.1
CXX=g++-7.3.1
Thread model: posix
gcc version 7.3.1 20180708 (GCC)
$ g++-8.1.1 -v
Using built-in specs.
COLLECT_GCC=g++-8.1.1
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-linux-gnu/8.1.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../configure --enable-languages=c,c++ --disable-multilib
--program-suffix=-8.1.1 --disable-bootstrap CFLAGS='-O2 -march=native
-mtune=native' CXXFLAGS='-O2 -march=native -mtune=native' CC=gcc-7.3.1
CXX=g++-7.3.1
Thread model: posix
gcc version 8.1.1 20180708 (GCC)
$ g++-9.0.0 -v
Using built-in specs.
COLLECT_GCC=g++-9.0.0
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../configure --enable-languages=c,c++ --disable-multilib
--program-suffix=-9.0.0 --disable-bootstrap CFLAGS='-O2 -march=native
-mtune=native' CXXFLAGS='-O2 -march=native -mtune=native' CC=gcc-7.3.1
CXX=g++-7.3.1
Thread model: posix
gcc version 9.0.0 20180708 (experimental) (GCC)
>From gcc-bugs-return-609412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 00:11:15 2018
Return-Path: <gcc-bugs-return-609412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57791 invoked by alias); 9 Jul 2018 00:11: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 57755 invoked by uid 48); 9 Jul 2018 00:11:10 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/86436] IPA-ICF: miissed optimization at class template member functions
Date: Mon, 09 Jul 2018 00:11: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: 8.1.1
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:
Message-ID: <bug-86436-4-EvN1cegOV9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00517.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86436
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The reason Foldable are not folded is because Foldable<0> and Foldable<42>
clases are different. Yes they have the same layout but for aliasing rules
they are different.
>From gcc-bugs-return-609413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 03:35:06 2018
Return-Path: <gcc-bugs-return-609413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29551 invoked by alias); 9 Jul 2018 03:35: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 25863 invoked by uid 48); 9 Jul 2018 03:35:00 -0000
From: "vivekrao4 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/83192] ICE for printing derived type
Date: Mon, 09 Jul 2018 03:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vivekrao4 at yahoo dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83192-4-6RF3KFpQTK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83192-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83192-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00518.txt.bz2
Content-length: 297
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83192
--- Comment #2 from Vivek Rao <vivekrao4 at yahoo dot com> ---
Using GNU Fortran (GCC) 8.0.1 20180408 (experimental) from equation.com the
code now compiles, so there may have been a bug in their previous build. I
suggest closing this report.
>From gcc-bugs-return-609414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 07:13:41 2018
Return-Path: <gcc-bugs-return-609414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18764 invoked by alias); 9 Jul 2018 07:13:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18686 invoked by uid 48); 9 Jul 2018 07:13:36 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/83192] ICE for printing derived type
Date: Mon, 09 Jul 2018 07: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-83192-4-fn94JfuCO7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83192-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83192-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00519.txt.bz2
Content-length: 643
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83192
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Using GNU Fortran (GCC) 8.0.1 20180408 (experimental) from equation.com
> the code now compiles, so there may have been a bug in their previous build.
> I suggest closing this report.
Closing as INVALID.
>From gcc-bugs-return-609415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 07:26:07 2018
Return-Path: <gcc-bugs-return-609415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111409 invoked by alias); 9 Jul 2018 07:26:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110551 invoked by uid 48); 9 Jul 2018 07:26:02 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/86413] [9 regression] gcc.dg/guality/pr48437.c fail
Date: Mon, 09 Jul 2018 07:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86413-4-c9Y1zL4rEy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86413-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86413-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00520.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86413
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-609416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 07:26:11 2018
Return-Path: <gcc-bugs-return-609416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111849 invoked by alias); 9 Jul 2018 07:26: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 111382 invoked by uid 55); 9 Jul 2018 07:26:06 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/86413] [9 regression] gcc.dg/guality/pr48437.c fail
Date: Mon, 09 Jul 2018 07:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86413-4-d6dAf3xivu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86413-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86413-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00521.txt.bz2
Content-length: 509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86413
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Mon Jul 9 07:25:14 2018
New Revision: 262511
URL: https://gcc.gnu.org/viewcvs?rev=262511&root=gcc&view=rev
Log:
2018-07-09 Richard Biener <rguenther@suse.de>
PR debug/86413
* dwarf2out.c (gen_block_die): For an early generated DIE
always output high/low PC attributes.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/dwarf2out.c
>From gcc-bugs-return-609417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 07:38:53 2018
Return-Path: <gcc-bugs-return-609417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74409 invoked by alias); 9 Jul 2018 07:38: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 72793 invoked by uid 48); 9 Jul 2018 07:38:48 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86401] The "For constants M and N, if M == (1LL << cst) - 1 && (N & M) == M,..." opts are only in fold-const.c and in RTL
Date: Mon, 09 Jul 2018 07: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86401-4-M54RKGRghg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86401-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86401-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00522.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86401
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-609418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 07:40:46 2018
Return-Path: <gcc-bugs-return-609418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97361 invoked by alias); 9 Jul 2018 07:40: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 97264 invoked by uid 48); 9 Jul 2018 07:40:41 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86416] [OMPVV SOLLVE] Defaultmap issues on OpenMP 4.5
Date: Mon, 09 Jul 2018 07:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: openmp
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-86416-4-VjWspUAcaA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86416-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86416-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00523.txt.bz2
Content-length: 231
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86416
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Note, OpenMP 4.5 fortran support is incomplete, it is partially 4.0, partially
4.5. Only C/C++ are complete.
>From gcc-bugs-return-609419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 07:42:57 2018
Return-Path: <gcc-bugs-return-609419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99131 invoked by alias); 9 Jul 2018 07: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 99099 invoked by uid 48); 9 Jul 2018 07:42:52 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86412] lto1: internal compiler error: in lto_symtab_prevailing_virtual_decl, at lto/lto-symtab.c
Date: Mon, 09 Jul 2018 07:42: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: 8.1.0
X-Bugzilla-Keywords: ice-checking
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86412-4-SdOz77UOrh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86412-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86412-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00524.txt.bz2
Content-length: 146
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86412
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r231671.
>From gcc-bugs-return-609420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 08:22:31 2018
Return-Path: <gcc-bugs-return-609420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104410 invoked by alias); 9 Jul 2018 08:22: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 10614 invoked by uid 48); 9 Jul 2018 08:16:53 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86429] [8/9 Regression] lambda capture breaks constexpr-ness
Date: Mon, 09 Jul 2018 08:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone
Message-ID: <bug-86429-4-KlLAeBWoP1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86429-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86429-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00525.txt.bz2
Content-length: 345
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86429
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Target Milestone|--- |8.2
>From gcc-bugs-return-609421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 08:33:30 2018
Return-Path: <gcc-bugs-return-609421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42687 invoked by alias); 9 Jul 2018 08:33:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27446 invoked by uid 48); 9 Jul 2018 08:25:44 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/86357] -falign-{functions,loops,jumps} incorrectly reported as disabled by -Q --help=optimizers
Date: Mon, 09 Jul 2018 08:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86357-4-GC5ZhQYL4p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86357-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86357-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00526.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86357
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 in r262513.
>From gcc-bugs-return-609424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 09:14:35 2018
Return-Path: <gcc-bugs-return-609424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4018 invoked by alias); 9 Jul 2018 09:14:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1538 invoked by uid 48); 9 Jul 2018 09:14:21 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49278] ICE (segfault) when combining DATA with default initialization
Date: Mon, 09 Jul 2018 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: 4.6.1
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-49278-4-ZIKrpZiP1x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49278-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49278-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00529.txt.bz2
Content-length: 449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49278
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gscfq@t-online.de
--- Comment #17 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
*** Bug 86220 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-609423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 09:14:35 2018
Return-Path: <gcc-bugs-return-609423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3944 invoked by alias); 9 Jul 2018 09:14:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1235 invoked by uid 48); 9 Jul 2018 09:14:20 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86437] New: runtime segfault on Fortran code with large array and -Ofast
Date: Mon, 09 Jul 2018 09:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-86437-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00528.txt.bz2
Content-length: 1703
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86437
Bug ID: 86437
Summary: runtime segfault on Fortran code with large array and
-Ofast
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: janus at gcc dot gnu.org
Target Milestone: ---
Reduced test case:
program ACT
implicit none
integer, parameter :: N = 53, M = 20000
integer :: i
integer, dimension(1:2*N) :: list
real(8), dimension(:,:), allocatable :: Y1, Y2
do i=1,2*N
list(i) = min(i, N)
end do
call DoAllocate(Y1, 1,N, 1,M)
call DoAllocate(Y2, 1,2*N, 1,2*M)
call ArrayCopy(Y2(list(1:N),1:M), Y1)
contains
subroutine DoAllocate(a, l1, u1, l2, u2)
real(8), allocatable, intent(inout) :: a(:,:)
integer, intent(in) :: l1, u1, l2, u2
allocate(a(l1:u1,l2:u2), source=0.0_8)
end subroutine
subroutine ArrayCopy(arrFrom, arrTo)
real(8), dimension(:,:), intent(in) :: arrFrom
real(8), dimension(:,:), intent(inout) :: arrTo
arrTo(:,:) = arrFrom(:,:)
end subroutine
end
When compiling this with any recent gfortran version (4.7.x up to 9-trunk)
using -Ofast, I get a segfault at runtime.
Things that make the segfault disappear:
* using gfortran 4.6.4
* using smaller M (e.g. M=2000)
* using -O1, -O2 or -O3 (with these I can even make M much larger, e.g.
M=200000)
Since the optimization level changes the behavior crucially, I assume this is
more of a middle-end than a front-end issue.
>From gcc-bugs-return-609422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 09:14:34 2018
Return-Path: <gcc-bugs-return-609422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3934 invoked by alias); 9 Jul 2018 09:14: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 1027 invoked by uid 48); 9 Jul 2018 09:14:19 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86220] [9 Regression] ICE in gfc_conv_structure, at fortran/trans-expr.c:7789
Date: Mon, 09 Jul 2018 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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86220-4-a5fERCp7t0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86220-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86220-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00527.txt.bz2
Content-length: 693
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86220
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I think this is a duplicate of pr49278: mixing initialization with data is
invalid.
Replacing
real :: a = 1
with
real :: a
allows the test to compile and give the right result.
*** This bug has been marked as a duplicate of bug 49278 ***
>From gcc-bugs-return-609425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 09:21:11 2018
Return-Path: <gcc-bugs-return-609425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4891 invoked by alias); 9 Jul 2018 09:21:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130029 invoked by uid 48); 9 Jul 2018 09:21:06 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86416] [OMPVV SOLLVE] Defaultmap issues on OpenMP 4.5
Date: Mon, 09 Jul 2018 09:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86416-4-uHqteVKXCG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86416-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86416-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00530.txt.bz2
Content-length: 356
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86416
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Note, OpenMP 4.5 fortran support is incomplete, it is partially 4.0,
> partially 4.5. Only C/C++ are complete.
Does this apply also to pr86421? Would it be possible to have an error "not yet
implemented" instead of an ICE?
>From gcc-bugs-return-609426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 09:26:53 2018
Return-Path: <gcc-bugs-return-609426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116872 invoked by alias); 9 Jul 2018 09:26:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116797 invoked by uid 48); 9 Jul 2018 09:26:48 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86425] Spec 2006 soplex seems to be slower on PowerPC using -ffast-math than without -ffast-math
Date: Mon, 09 Jul 2018 09: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-86425-4-R2U99xtoEf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86425-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86425-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00531.txt.bz2
Content-length: 802
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86425
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org,
| |jamborm at gcc dot gnu.org
--- Comment #1 from Martin Jambor <jamborm at gcc dot gnu.org> ---
On AMD Zen CPUs at least, we found that the number of iterations executed by
the hottest loop is considerably higher with -ffast-math (just patch the
benchmark and see for yourself). The reason is that the benchmark iterates
until some error is smaller than a given threshold and with -ffast-math we
simply get there after more computation.
>From gcc-bugs-return-609427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 09:29:11 2018
Return-Path: <gcc-bugs-return-609427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119403 invoked by alias); 9 Jul 2018 09:29:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119335 invoked by uid 48); 9 Jul 2018 09:29:05 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86437] runtime segfault on Fortran code with large array and -Ofast
Date: Mon, 09 Jul 2018 09:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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-86437-4-uJeM89s1EC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86437-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86437-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00532.txt.bz2
Content-length: 597
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86437
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2018-07-09
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
WORKSFORME. AFAIR -Ofast implies -fstack-arrays. What is the output of
ulimit -s
(kbytes, -s) 65532 for me?
>From gcc-bugs-return-609428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 09:53:58 2018
Return-Path: <gcc-bugs-return-609428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38515 invoked by alias); 9 Jul 2018 09: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 37468 invoked by uid 48); 9 Jul 2018 09:53:48 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86437] runtime segfault on Fortran code with large array and -Ofast
Date: Mon, 09 Jul 2018 09:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86437-4-DxAFeavDW8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86437-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86437-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00533.txt.bz2
Content-length: 1250
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86437
--- Comment #2 from janus at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #1)
> WORKSFORME. AFAIR -Ofast implies -fstack-arrays.
Yeah, right, -fstack-arrays is the crucial flag here.
> What is the output of
>
> ulimit -s
>
> (kbytes, -s) 65532 for me?
8192
So, yes, I'm hitting the stack size.
However, what is a bit strange is that I get this problem only when putting the
ALLOCATE statement into a subroutine, which returns the allocated array, but
not when allocating directly in the main program. Is this intended behavior?
The documentation says:
"-fstack-arrays
Adding this option will make the Fortran compiler put all arrays of unknown
size and array temporaries onto stack memory. If your program uses very large
local arrays it is possible that you will have to extend your runtime limits
for stack memory on some operating systems."
This mentions 'local arrays', and I was also assuming that only local arrays
will be put on the stack. In my example, Y1 and Y2 are not local, but declared
in the main program. Only the allocation happens in a subroutine, but the
arrays are returned to the main program via a subroutine argument ...
>From gcc-bugs-return-609429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 10:03:11 2018
Return-Path: <gcc-bugs-return-609429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15717 invoked by alias); 9 Jul 2018 10:03: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 15607 invoked by uid 48); 9 Jul 2018 10:03:05 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86437] runtime segfault on Fortran code with large array and -Ofast
Date: Mon, 09 Jul 2018 10:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86437-4-bqT47BzOb2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86437-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86437-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00534.txt.bz2
Content-length: 498
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86437
--- Comment #3 from janus at gcc dot gnu.org ---
(In reply to janus from comment #2)
> (In reply to Dominique d'Humieres from comment #1)
> > WORKSFORME. AFAIR -Ofast implies -fstack-arrays.
>
> Yeah, right, -fstack-arrays is the crucial flag here.
Shouldn't -fmax-stack-var-size be a useful workaround then? Unfortunately
neither of those seems to help:
-fmax-stack-var-size=8192
-fmax-stack-var-size=4096
-fmax-stack-var-size=2048
>From gcc-bugs-return-609430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 10:04:54 2018
Return-Path: <gcc-bugs-return-609430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19524 invoked by alias); 9 Jul 2018 10:04: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 19439 invoked by uid 48); 9 Jul 2018 10:04:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Mon, 09 Jul 2018 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: 8.1.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86422-4-6Qhj7EZled@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00535.txt.bz2
Content-length: 1767
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
So with a debug build I can see
(gdb) run
Starting program: /home/abuild/rguenther/gcc8-g/gcc/cc1plus -quiet
/tmp/CodePoint.ii
Program received signal SIGSEGV, Segmentation fault.
0x0000000001576cf6 in verify_vssa (bb=<basic_block 0x7fff7bc081a0 (1591494)>,
current_vdef=<ssa_name 0x7fff2894d3a8>, visited=0x1389be00)
at /space/rguenther/src/svn/gcc-8-branch/gcc/tree-ssa.c:632
632 if (bitmap_bit_p (visited, bb->index))
(gdb) p bb
$1 = <basic_block 0x7fff7bc081a0 (1591494)>
(ick btw, that are many basic blocks)
and the SEGFAULT is a stack overflow due to recursion in verify_vssa which
does
/* Verify destination PHI uses and recurse. */
edge_iterator ei;
edge e;
FOR_EACH_EDGE (e, ei, bb->succs)
{
gphi *phi = get_virtual_phi (e->dest);
if (phi
&& PHI_ARG_DEF_FROM_EDGE (phi, e) != current_vdef)
{
error ("PHI node with wrong VUSE on edge from BB %d",
e->src->index);
print_gimple_stmt (stderr, phi, 0, TDF_VOPS);
fprintf (stderr, "expected ");
print_generic_expr (stderr, current_vdef);
fprintf (stderr, "\n");
err = true;
}
/* Recurse. */
err |= verify_vssa (e->dest, current_vdef, visited);
which is of course stupid. I'll fix that.
Re-running with -fno-checking now to side-step the above issue (as said,
this is a --enable-checking build).
I do know we have some algorithms that recurse to dominator sons and
very likely the CFG structure will result in big recursion depth there
as well.
So maybe a workaround for you is to do ulimit -s unlimited?
>From gcc-bugs-return-609431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 10:42:33 2018
Return-Path: <gcc-bugs-return-609431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65848 invoked by alias); 9 Jul 2018 10: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 63524 invoked by uid 48); 9 Jul 2018 10:42:28 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Mon, 09 Jul 2018 10:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-86422-4-WzXRkh0ZTE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00536.txt.bz2
Content-length: 1090
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Yeah, so there's into-SSA for example:
#63 0x0000000001368cd6 in prepare_block_for_update (
bb=<basic_block 0x7fffdd071e38 (220676)>, insert_phi_p=true)
at /space/rguenther/src/svn/gcc-8-branch/gcc/tree-into-ssa.c:2677
2677 prepare_block_for_update (son, insert_phi_p);
(gdb) l
2672
2673 /* Now visit all the blocks dominated by BB. */
2674 for (son = first_dom_son (CDI_DOMINATORS, bb);
2675 son;
2676 son = next_dom_son (CDI_DOMINATORS, son))
2677 prepare_block_for_update (son, insert_phi_p);
and there are many more in the tree.
So, can you check your stack ulimit and see if raising it solves the issue for
you (memory usage is still very high though).
>From gcc-bugs-return-609432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 10:48:52 2018
Return-Path: <gcc-bugs-return-609432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25187 invoked by alias); 9 Jul 2018 10: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 24822 invoked by uid 48); 9 Jul 2018 10:48:32 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86434] early string folding defeats strlen optimization and -Warray-bounds
Date: Mon, 09 Jul 2018 10:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86434-4-Z30ZtDpPjK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86434-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86434-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00537.txt.bz2
Content-length: 661
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86434
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Are these examples from real-world code? Because I can create examples where
early folding is necessary as well...
It's really not an easy black-and-white decision.
Consider
void f (int i)
{
if (__builtin_strlen (&a[i]) != 3 - i)
{
... large code ...
}
}
void g ()
{
f (1);
}
where not folding and eliding the conditionaly will prevent inlining from
happening.
The usual "solution" is to do value-range analysis and folding at the same
time - thus avoiding pass inter-dependences by just having a single pass.
>From gcc-bugs-return-609433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 10:57:26 2018
Return-Path: <gcc-bugs-return-609433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72294 invoked by alias); 9 Jul 2018 10:57:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72231 invoked by uid 55); 9 Jul 2018 10:57:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/86420] [9 regression] nextafter(0x1p-1022,0) is constant folded
Date: Mon, 09 Jul 2018 10: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:
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-86420-4-XEt5xMPX30@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86420-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86420-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00538.txt.bz2
Content-length: 690
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86420
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Jul 9 10:56:47 2018
New Revision: 262517
URL: https://gcc.gnu.org/viewcvs?rev=262517&root=gcc&view=rev
Log:
PR c/86420
* real.c (real_nextafter): Return true if result is denormal.
* gcc.dg/nextafter-1.c (TEST): Adjust the tests that expect denormals
to be returned and when first argument is not 0, so that they don't do
anything for NEED_EXC or NEED_ERRNO.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/real.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/nextafter-1.c
>From gcc-bugs-return-609434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 11:23:38 2018
Return-Path: <gcc-bugs-return-609434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99763 invoked by alias); 9 Jul 2018 11:23: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 99616 invoked by uid 48); 9 Jul 2018 11:23:30 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86417] [9 Regression] FAIL: libgomp.fortran/alloc-comp-3.f90 -O0 (test for excess errors)
Date: Mon, 09 Jul 2018 11: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: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86417-4-BszRNfc8Nd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86417-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86417-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00539.txt.bz2
Content-length: 975
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86417
--- Comment #10 from janus at gcc dot gnu.org ---
(In reply to janus from comment #9)
> The following patch seems to be sufficient to fix the regression:
... however, it lacks a safety check for the existence of the ctor expression.
This variant regtests cleanly:
Index: gcc/fortran/expr.c
===================================================================
--- gcc/fortran/expr.c (revision 262509)
+++ gcc/fortran/expr.c (working copy)
@@ -4650,6 +4650,10 @@ gfc_generate_initializer (gfc_typespec *ts, bool g
}
}
+ /* Make sure that locus is set. */
+ if (ctor->expr && (!ctor->expr->where.nextc || !ctor->expr->where.lb))
+ ctor->expr->where = init->where;
+
gfc_constructor_append (&init->value.constructor, ctor);
}
>From gcc-bugs-return-609435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 11:51:23 2018
Return-Path: <gcc-bugs-return-609435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82488 invoked by alias); 9 Jul 2018 11:51:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82451 invoked by uid 48); 9 Jul 2018 11:51:16 -0000
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/86438] New: [8/9 Regression] wrong code at -Os
Date: Mon, 09 Jul 2018 11:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zsojka at seznam dot cz
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcchost cf_gcctarget attachments.created
Message-ID: <bug-86438-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00540.txt.bz2
Content-length: 2469
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86438
Bug ID: 86438
Summary: [8/9 Regression] wrong code at -Os
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: zsojka at seznam dot cz
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: x86_64-pc-linux-gnu
Created attachment 44365
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44365&action=edit
reduced testcase
Output:
$ x86_64-pc-linux-gnu-gcc -Os testcase.c
$ ./a.out
Aborted
Diff between -O2 -> -Os shows:
@@ -77,15 +76,15 @@
# testcase.c:13: u32 f = __builtin_sub_overflow_p (d, (u128) d, (u64)0);
mov ebx, 0 # _2,
# testcase.c:12: u64 d = (g ? 5 : 4);
- setne al #, iftmp.0_9
- movzx eax, al # iftmp.0_9, iftmp.0_9
- add rax, 4 # iftmp.0_9,
+ cmp rax, 1 # tmp100,
+ sbb rax, rax # iftmp.0_9
+ add rax, 5 # iftmp.0_9,
# testcase.c:13: u32 f = __builtin_sub_overflow_p (d, (u128) d, (u64)0);
mov rcx, rax # _2, iftmp.0_9
setc al #, _11
The - (-O2) never sets CF (thus the last setc always sets al=0).
The + (-Os) set CF if g==0 (thus the last setc sets al=(g==0)).
The __builtin_sub_overflow_p() in fact never overflows, because it does
(u64)d-(u128)d == 0 in all cases.
$ x86_64-pc-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-262509-checking-yes-rtl-df-extra-nobootstrap-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--disable-bootstrap --with-cloog --with-ppl --with-isl
--build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
--target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-262509-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
gcc version 9.0.0 20180709 (experimental) (GCC)
>From gcc-bugs-return-609436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 12:01:34 2018
Return-Path: <gcc-bugs-return-609436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5112 invoked by alias); 9 Jul 2018 12:01: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 4786 invoked by uid 48); 9 Jul 2018 12:01:26 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86439] New: CTAD with deleted copy constructor fails due to deduction-guide taking by value
Date: Mon, 09 Jul 2018 12: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: 8.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: barry.revzin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86439-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00541.txt.bz2
Content-length: 1376
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86439
Bug ID: 86439
Summary: CTAD with deleted copy constructor fails due to
deduction-guide taking by value
Product: gcc
Version: 8.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: barry.revzin at gmail dot com
Target Milestone: ---
Reduced from: https://stackoverflow.com/q/51244047/2069064
struct NC {
NC() = default;
NC(NC const&) = delete;
NC& operator=(NC const&) = delete;
};
template <int>
struct C {
C(NC const&);
};
C(NC) -> C<0>;
int main() {
NC nc;
C c(nc);
}
clang accepts.
gcc rejects this program with:
<source>: In function 'int main()':
<source>:16:11: error: class template argument deduction failed:
C c(nc);
^
<source>:16:11: error: use of deleted function 'NC::NC(const NC&)'
<source>:3:5: note: declared here
NC(NC const&) = delete;
^~
<source>:12:1: note: initializing argument 1 of 'C(NC)-> C<0>'
C(NC) -> C<0>;
^
But nowhere do we need to copy NC here. CTAD doesn't require invoking the
function, just picking the best viable candidate. And once we pick C<0>,
actually constructing a C<0> is fine since it doesn't require a copy.
>From gcc-bugs-return-609437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 12:10:41 2018
Return-Path: <gcc-bugs-return-609437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32985 invoked by alias); 9 Jul 2018 12:10:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32703 invoked by uid 48); 9 Jul 2018 12:10:37 -0000
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49263] SH Target: underutilized "TST #imm, R0" instruction
Date: Mon, 09 Jul 2018 12: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: 4.6.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: olegendo at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: olegendo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49263-4-hPosBOxMZY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49263-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49263-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00542.txt.bz2
Content-length: 396
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49263
--- Comment #28 from Oleg Endo <olegendo at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #27)
> (In reply to Oleg Endo from comment #26)
> > Author: olegendo
> > Date: Mon Jan 26 23:56:05 2015
> > New Revision: 220144
Well, it fixed some of the cases mentioned in this PR, but not all. It's quite
a broad issue actually.
>From gcc-bugs-return-609438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 12:16:43 2018
Return-Path: <gcc-bugs-return-609438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84611 invoked by alias); 9 Jul 2018 12:16:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84227 invoked by uid 48); 9 Jul 2018 12:16:27 -0000
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82711] -Wignored-qualifiers could be moved into -Wextra
Date: Mon, 09 Jul 2018 12: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: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nightstrike at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-82711-4-1SOc8PmKTG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00543.txt.bz2
Content-length: 621
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82711
nightstrike <nightstrike at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nightstrike at gmail dot com
--- Comment #4 from nightstrike <nightstrike at gmail dot com> ---
It looks to me like this has been done, at least for g++ 8.1.0:
$ g++ a.cc -c
$ g++ a.cc -c -Wextra
a.cc:1:5: warning: type qualifiers ignored on function return type
[-Wignored-qualifiers]
int const f() { return 0; }
^~~~~
>From gcc-bugs-return-609439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 12:19:30 2018
Return-Path: <gcc-bugs-return-609439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108803 invoked by alias); 9 Jul 2018 12:19: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 108774 invoked by uid 48); 9 Jul 2018 12:19:26 -0000
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86440] New: -Wignored-qualifiers diagnostic highlights wrong token with pointer
Date: Mon, 09 Jul 2018 12:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nightstrike 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-86440-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00544.txt.bz2
Content-length: 831
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86440
Bug ID: 86440
Summary: -Wignored-qualifiers diagnostic highlights wrong token
with pointer
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nightstrike at gmail dot com
Target Milestone: ---
$ cat a.cc
int const f() { return 0; }
int * const g() { return 0; }
$ g++ a.cc -c -Wignored-qualifiers
a.cc:1:5: warning: type qualifiers ignored on function return type
[-Wignored-qualifiers]
int const f() { return 0; }
^~~~~
a.cc:3:1: warning: type qualifiers ignored on function return type
[-Wignored-qualifiers]
int * const g() { return 0; }
^~~
>From gcc-bugs-return-609440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 14:02:48 2018
Return-Path: <gcc-bugs-return-609440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104221 invoked by alias); 9 Jul 2018 14:02: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 96098 invoked by uid 48); 9 Jul 2018 14:02:40 -0000
From: "boris.staletic at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Mon, 09 Jul 2018 14: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: 8.1.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: boris.staletic at gmail dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86422-4-YoPun0PocS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00545.txt.bz2
Content-length: 463
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #8 from Boris Staletic <boris.staletic at gmail dot com> ---
> ulimit -s unlimited
After running that command and enabling swap, for a total of 16GB available
memory, until about 5 minute mark, cc1plus was consuming >4GB. After about five
minute mark, cc1plus started consuming memory rapidly, and in about a minute or
so, it consumed all 16GB. The end result is OOM killer stopping cc1plus.
>From gcc-bugs-return-609441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 14:16:42 2018
Return-Path: <gcc-bugs-return-609441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69508 invoked by alias); 9 Jul 2018 14:16: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 67597 invoked by uid 48); 9 Jul 2018 14:16:36 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/86438] [8/9 Regression] wrong code at -Os
Date: Mon, 09 Jul 2018 14:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-86438-4-x3GFT7BGG5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86438-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86438-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00546.txt.bz2
Content-length: 3265
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86438
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-09
Ever confirmed|0 |1
--- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
Looks like postreload cmp elimitation pass is at fault.
It converts:
(insn 64 63 76 2 (parallel [
(set (reg:DI 0 ax [orig:94 iftmp.0_9 ] [94])
(plus:DI (reg:DI 0 ax [orig:94 iftmp.0_9 ] [94])
(const_int 5 [0x5])))
(clobber (reg:CC 17 flags))
]) "pr86438.c":17 232 {*adddi_1}
(nil))
(insn 76 64 77 2 (set (reg:DI 4 si [orig:88 _2 ] [88])
(const_int 0 [0])) "pr86438.c":18 85 {*movdi_internal}
(nil))
(insn 77 76 14 2 (set (reg:DI 5 di [ _2+8 ])
(const_int 0 [0])) "pr86438.c":18 85 {*movdi_internal}
(nil))
(insn 14 77 15 2 (set (reg:DI 4 si [orig:88 _2 ] [88])
(reg:DI 0 ax [orig:94 iftmp.0_9 ] [94])) "pr86438.c":18 85
{*movdi_internal}
(nil))
(insn 15 14 66 2 (set (reg:DI 5 di [ _2+8 ])
(const_int 0 [0])) "pr86438.c":18 85 {*movdi_internal}
(nil))
(insn 66 15 67 2 (set (reg:CC 17 flags)
(compare:CC (reg:DI 0 ax [orig:94 iftmp.0_9 ] [94])
(reg:DI 4 si [orig:88 _2 ] [88]))) "pr86438.c":18 12 {*cmpdi_1}
(nil))
(note 67 66 78 2 NOTE_INSN_DELETED)
(insn 78 67 79 2 (set (reg:QI 2 cx [orig:96 _11+8 ] [96])
(ltu:QI (reg:CC 17 flags)
(const_int 0 [0]))) "pr86438.c":18 700 {*setcc_qi}
(nil))
to:
(insn 64 63 76 2 (parallel [
(set (reg:CCC 17 flags)
(compare:CCC (plus:DI (reg:DI 0 ax [orig:94 iftmp.0_9 ] [94])
(const_int 5 [0x5]))
(reg:DI 0 ax [orig:94 iftmp.0_9 ] [94])))
(set (reg:DI 0 ax [orig:94 iftmp.0_9 ] [94])
(plus:DI (reg:DI 0 ax [orig:94 iftmp.0_9 ] [94])
(const_int 5 [0x5])))
]) "pr86438.c":17 346 {*adddi3_cc_overflow_1}
(nil))
(insn 76 64 77 2 (set (reg:DI 4 si [orig:88 _2 ] [88])
(const_int 0 [0])) "pr86438.c":18 85 {*movdi_internal}
(nil))
(insn 77 76 14 2 (set (reg:DI 5 di [ _2+8 ])
(const_int 0 [0])) "pr86438.c":18 85 {*movdi_internal}
(nil))
(insn 14 77 15 2 (set (reg:DI 4 si [orig:88 _2 ] [88])
(reg:DI 0 ax [orig:94 iftmp.0_9 ] [94])) "pr86438.c":18 85
{*movdi_internal}
(nil))
(insn 15 14 67 2 (set (reg:DI 5 di [ _2+8 ])
(const_int 0 [0])) "pr86438.c":18 85 {*movdi_internal}
(nil))
(note 67 15 78 2 NOTE_INSN_DELETED)
(insn 78 67 79 2 (set (reg:QI 2 cx [orig:96 _11+8 ] [96])
(ltu:QI (reg:CCC 17 flags)
(const_int 0 [0]))) "pr86438.c":18 700 {*setcc_qi}
(nil))
Please note that (insn 66) is deleted and (insn 64) gets converted to an insn
that sets flags reg in CCCmode (where only carry flag is valid). The original
sequence sets flags reg in CCmode (where all flags are valid), so these two
sequences are not identical.
Adding -fno-compare-elim fixes the test.
>From gcc-bugs-return-609443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 14:17:21 2018
Return-Path: <gcc-bugs-return-609443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76565 invoked by alias); 9 Jul 2018 14:17: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 75497 invoked by uid 48); 9 Jul 2018 14:17:16 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/86438] [8/9 Regression] wrong code at -Os
Date: Mon, 09 Jul 2018 14:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-86438-4-ogzuaaRTbO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86438-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86438-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00548.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86438
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.3
>From gcc-bugs-return-609442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 14:17:09 2018
Return-Path: <gcc-bugs-return-609442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74573 invoked by alias); 9 Jul 2018 14:17: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 73614 invoked by uid 48); 9 Jul 2018 14:17:03 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Mon, 09 Jul 2018 14: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: 8.1.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc component
Message-ID: <bug-86422-4-KlGyhAhVAm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00547.txt.bz2
Content-length: 1667
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
CC| |jason at gcc dot gnu.org,
| |redi at gcc dot gnu.org
Component|c++ |libstdc++
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Thanks for confirming the crash reason.
So I wonder, quoting a small testcase:
#include <string>
struct RawCodePoint {
const std::string original;
const std::string normal;
const std::string folded_case;
const std::string swapped_case;
bool is_letter;
bool is_punctuation;
bool is_uppercase;
unsigned char break_property;
unsigned char combining_class;
};
void foo() {
static const RawCodePoint code_points[] = {
{"\x00","\x00","\x00","\x00",0,0,0,3,0},
{"^A","^A","^A","^A",0,0,0,3,0},
{"^B","^B","^B","^B",0,0,0,3,0}
};
}
why with the new std::string and its small string optimization we cannot
"constexpr" the constructor (not sure what clang does here).
I suppose one issue is that the C++ FE arranges for the constructors to
throw and thus emits cleanups for others.
But in the end the testcase doesn't look unreasonable and we should do
better (constexpr evaluation should be able to tell whether we'll throw
as well).
So, another question to the reporter - does -fno-exceptions help
for your original testcase (the preprocessed one doesn't like
-fno-exceptions)?
>From gcc-bugs-return-609444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 14:18:43 2018
Return-Path: <gcc-bugs-return-609444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87795 invoked by alias); 9 Jul 2018 14:18:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87744 invoked by uid 48); 9 Jul 2018 14:18:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/86438] [8/9 Regression] wrong code at -Os
Date: Mon, 09 Jul 2018 14:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-86438-4-RWW9ARCHdy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86438-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86438-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00549.txt.bz2
Content-length: 372
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86438
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |ebotcazou at gcc dot gnu.org
>From gcc-bugs-return-609445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 14:19:32 2018
Return-Path: <gcc-bugs-return-609445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89178 invoked by alias); 9 Jul 2018 14:19:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89100 invoked by uid 48); 9 Jul 2018 14:19:27 -0000
From: "boris at kolpackov dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86441] New: instantiate_class_template() unable to re-execute constexpr function
Date: Mon, 09 Jul 2018 14:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: boris at kolpackov dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86441-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00550.txt.bz2
Content-length: 2934
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86441
Bug ID: 86441
Summary: instantiate_class_template() unable to re-execute
constexpr function
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: boris at kolpackov dot net
Target Milestone: ---
I have a GCC plugin (ODB) that calls instantiate_class_template() to
"post-instantiate" some types that haven't been instantiated during parsing.
The code is pretty much identical to what complete_type() does to class
templates. This has been working pretty well since the GCC 4.5 days.
This also generally works in GCC 8 except it seems when the instantiation
requires re-execution of a constexpr function. Below are the details of a
specific example of this situation.
The plugin tries to instantiate a type that is declared like this:
#include <map>
#include <string>
using strmap = std::map<std::string, std::string>;
This works fine unless I have a different instantiation of std::map:
#include <map>
#include <string>
using intmap = std::map<int, int>;
struct foo
{
intmap m;
};
using strmap = std::map<std::string, std::string>;
In this case I get (during the call to instantiate_class_template(strmap)):
/usr/include/c++/8/bits/stl_tree.h: In instantiation of ‘class
std::_Rb_tree<std::__cxx11::basic_string<char>, std::pair<const
std::__cxx11::basic_string<char>, std::__cxx11::basic_string<char> >,
std::_Select1st<std::pair<const std::__cxx11::basic_string<char>,
std::__cxx11::basic_string<char> > >,
std::less<std::__cxx11::basic_string<char> >, std::allocator<std::pair<const
std::__cxx11::basic_string<char>, std::__cxx11::basic_string<char> > > >’:
/usr/include/c++/8/bits/stl_map.h:151:17: required from ‘class
std::map<std::__cxx11::basic_string<char>, std::__cxx11::basic_string<char> >’
test.hxx:11:16: required from here
/usr/include/c++/8/bits/stl_tree.h:452:21: error: non-constant condition for
static assertion
static_assert(__is_invocable<_Compare&, const _Key&, const _Key&>{},
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/c++/8/bits/stl_tree.h:452: confused by earlier errors, bailing out
If I change stl_tree.h:452 from '__is_invocable<_Compare&, const _Key&, const
_Key&>{}' to '__is_invocable<_Compare&, const _Key&, const _Key&>::value', then
the error goes away. To me this suggests it has something to do we re-executing
(it has already been executed when instantiating intmap) of a constexpr
function (operator bool() in true_type).
Providing a reproducer is challenging since the instantiation is triggered by a
plugin. But let me know if I need to provide any additional information or
test/verify a fix.
>From gcc-bugs-return-609446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 14:22:29 2018
Return-Path: <gcc-bugs-return-609446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101409 invoked by alias); 9 Jul 2018 14:22: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 101348 invoked by uid 48); 9 Jul 2018 14:22:22 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86442] New: Wrong error: global register variable follows a function definition when using LTO
Date: Mon, 09 Jul 2018 14:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
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-86442-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00551.txt.bz2
Content-length: 1165
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86442
Bug ID: 86442
Summary: Wrong error: global register variable follows a
function definition when using LTO
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org, marxin at gcc dot gnu.org
Target Milestone: ---
Following wrong error is printed with LTO:
$ cat global.cpp
register int a __asm__("r12");
class b {
public:
b();
};
b c;
int main() { a = 3; }
$ g++ global.cpp -O2 -flto
global.cpp: In function ‘main’:
global.cpp:1:14: error: global register variable follows a function definition
register int a __asm__("r12");
^
lto-wrapper: fatal error: g++ returned 1 exit status
compilation terminated.
/usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: error:
lto-wrapper failed
collect2: error: ld returned 1 exit status
>From gcc-bugs-return-609447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 14:25:23 2018
Return-Path: <gcc-bugs-return-609447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122579 invoked by alias); 9 Jul 2018 14:25: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 122545 invoked by uid 48); 9 Jul 2018 14:25:19 -0000
From: "boris at kolpackov dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86441] instantiate_class_template() unable to re-execute constexpr function
Date: Mon, 09 Jul 2018 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: boris at kolpackov 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: attachments.created
Message-ID: <bug-86441-4-oVwNkYKh4b@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86441-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86441-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00552.txt.bz2
Content-length: 370
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86441
--- Comment #1 from Boris Kolpackov <boris at kolpackov dot net> ---
Created attachment 44366
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44366&action=edit
Test case that shows the problem if compiled with ODB
For the record, a test case that triggers the error if compiled with ODB that
uses GCC 8.
>From gcc-bugs-return-609448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 15:15:49 2018
Return-Path: <gcc-bugs-return-609448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75263 invoked by alias); 9 Jul 2018 15:15:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74963 invoked by uid 48); 9 Jul 2018 15:15:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86443] New: ICEs on #pragma omp distribute parallel for with class iterators
Date: Mon, 09 Jul 2018 15:15: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.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-86443-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00553.txt.bz2
Content-length: 8648
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86443
Bug ID: 86443
Summary: ICEs on #pragma omp distribute parallel for with class
iterators
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
// { dg-do run }
// { dg-additional-options "-std=c++17" }
typedef __PTRDIFF_TYPE__ ptrdiff_t;
extern "C" void abort ();
#pragma omp declare target
template <typename T>
class I
{
public:
typedef ptrdiff_t difference_type;
I ();
~I ();
I (T *);
I (const I &);
T &operator * ();
T *operator -> ();
T &operator [] (const difference_type &) const;
I &operator = (const I &);
I &operator ++ ();
I operator ++ (int);
I &operator -- ();
I operator -- (int);
I &operator += (const difference_type &);
I &operator -= (const difference_type &);
I operator + (const difference_type &) const;
I operator - (const difference_type &) const;
template <typename S> friend bool operator == (I<S> &, I<S> &);
template <typename S> friend bool operator == (const I<S> &, const I<S> &);
template <typename S> friend bool operator < (I<S> &, I<S> &);
template <typename S> friend bool operator < (const I<S> &, const I<S> &);
template <typename S> friend bool operator <= (I<S> &, I<S> &);
template <typename S> friend bool operator <= (const I<S> &, const I<S> &);
template <typename S> friend bool operator > (I<S> &, I<S> &);
template <typename S> friend bool operator > (const I<S> &, const I<S> &);
template <typename S> friend bool operator >= (I<S> &, I<S> &);
template <typename S> friend bool operator >= (const I<S> &, const I<S> &);
template <typename S> friend typename I<S>::difference_type operator - (I<S>
&, I<S> &);
template <typename S> friend typename I<S>::difference_type operator - (const
I<S> &, const I<S> &);
template <typename S> friend I<S> operator + (typename I<S>::difference_type
, const I<S> &);
private:
T *p;
};
template <typename T> I<T>::I () : p (0) {}
template <typename T> I<T>::~I () {}
template <typename T> I<T>::I (T *x) : p (x) {}
template <typename T> I<T>::I (const I &x) : p (x.p) {}
template <typename T> T &I<T>::operator * () { return *p; }
template <typename T> T *I<T>::operator -> () { return p; }
template <typename T> T &I<T>::operator [] (const difference_type &x) const {
return p[x]; }
template <typename T> I<T> &I<T>::operator = (const I &x) { p = x.p; return
*this; }
template <typename T> I<T> &I<T>::operator ++ () { ++p; return *this; }
template <typename T> I<T> I<T>::operator ++ (int) { return I (p++); }
template <typename T> I<T> &I<T>::operator -- () { --p; return *this; }
template <typename T> I<T> I<T>::operator -- (int) { return I (p--); }
template <typename T> I<T> &I<T>::operator += (const difference_type &x) { p +=
x; return *this; }
template <typename T> I<T> &I<T>::operator -= (const difference_type &x) { p -=
x; return *this; }
template <typename T> I<T> I<T>::operator + (const difference_type &x) const {
return I (p + x); }
template <typename T> I<T> I<T>::operator - (const difference_type &x) const {
return I (p - x); }
template <typename T> bool operator == (I<T> &x, I<T> &y) { return x.p == y.p;
}
template <typename T> bool operator == (const I<T> &x, const I<T> &y) { return
x.p == y.p; }
template <typename T> bool operator != (I<T> &x, I<T> &y) { return !(x == y); }
template <typename T> bool operator != (const I<T> &x, const I<T> &y) { return
!(x == y); }
template <typename T> bool operator < (I<T> &x, I<T> &y) { return x.p < y.p; }
template <typename T> bool operator < (const I<T> &x, const I<T> &y) { return
x.p < y.p; }
template <typename T> bool operator <= (I<T> &x, I<T> &y) { return x.p <= y.p;
}
template <typename T> bool operator <= (const I<T> &x, const I<T> &y) { return
x.p <= y.p; }
template <typename T> bool operator > (I<T> &x, I<T> &y) { return x.p > y.p; }
template <typename T> bool operator > (const I<T> &x, const I<T> &y) { return
x.p > y.p; }
template <typename T> bool operator >= (I<T> &x, I<T> &y) { return x.p >= y.p;
}
template <typename T> bool operator >= (const I<T> &x, const I<T> &y) { return
x.p >= y.p; }
template <typename T> typename I<T>::difference_type operator - (I<T> &x, I<T>
&y) { return x.p - y.p; }
template <typename T> typename I<T>::difference_type operator - (const I<T> &x,
const I<T> &y) { return x.p - y.p; }
template <typename T> I<T> operator + (typename I<T>::difference_type x, const
I<T> &y) { return I<T> (x + y.p); }
template <typename T>
class J
{
public:
J(const I<T> &x, const I<T> &y) : b (x), e (y) {}
const I<T> &begin ();
const I<T> &end ();
private:
I<T> b, e;
};
template <typename T> const I<T> &J<T>::begin () { return b; }
template <typename T> const I<T> &J<T>::end () { return e; }
int a[2000];
int results[2000];
template <typename T>
void
baz (I<T> &i)
{
if (*i < 0 || *i >= 2000)
abort ();
results[*i]++;
}
void
baz (int i)
{
if (i < 0 || i >= 2000)
abort ();
results[i]++;
}
void
qux (I<int> &i)
{
if (*i != 1931)
abort ();
}
void
f1 (J<int> j)
{
#pragma omp distribute parallel for default(none)
for (I<int> i = j.begin (); i < j.end (); i += 3)
baz (*i);
}
void
f2 (J<int> j)
{
I<int> i;
#pragma omp distribute parallel for default(none)
for (i = j.begin (); i < j.end (); ++i)
baz (*i);
}
template <int N>
void
f3 (J<int> j)
{
#pragma omp distribute parallel for default(none)
for (I<int> i = j.begin (); i < j.end (); i += 6)
baz (*i);
}
template <int N>
void
f4 (J<int> j)
{
I<int> i;
#pragma omp distribute parallel for default(none)
for (i = j.begin (); i < j.end (); i += 9)
baz (*i);
}
template <typename T>
void
f5 (J<T> j)
{
#pragma omp distribute parallel for default(none)
for (I<T> i = j.begin (); i < j.end (); i += 4)
baz (*i);
}
template <typename T>
void
f6 (J<T> j)
{
I<T> i;
#pragma omp distribute parallel for default(none)
for (i = j.begin (); i < j.end (); i += 7)
baz (*i);
}
#pragma omp end declare target
#define check(expr) \
for (int i = 0; i < 2000; i++) \
if (expr) \
{ \
if (results[i] != 1) \
abort (); \
results[i] = 0; \
} \
else if (results[i]) \
abort ()
int
main ()
{
int a[2000];
for (int i = 0; i < 2000; i++)
a[i] = i;
#pragma omp target data map (to: a)
{
#pragma omp target teams map (tofrom: results)
{
J<int> j (&a[75], &a[1945]);
f1 (j);
}
check (i >= 75 && i < 1945 && (i - 75) % 3 == 0);
#pragma omp target teams map (tofrom: results)
{
J<int> j (&a[63], &a[1949]);
f2 (j);
}
check (i >= 63 && i < 1949);
#pragma omp target teams map (tofrom: results)
{
J<int> j (&a[58], &a[1979]);
f3 <2> (j);
}
check (i >= 58 && i < 1979 && (i - 58) % 6 == 0);
#pragma omp target teams map (tofrom: results)
{
J<int> j (&a[59], &a[1981]);
f4 <9> (j);
}
check (i >= 59 && i < 1981 && (i - 59) % 9 == 0);
#pragma omp target teams map (tofrom: results)
{
J<int> j (&a[52], &a[1972]);
f5 (j);
}
check (i >= 52 && i < 1972 && (i - 52) % 4 == 0);
#pragma omp target teams map (tofrom: results)
{
J<int> j (&a[31], &a[1827]);
f6 (j);
}
check (i >= 31 && i < 1827 && (i - 31) % 7 == 0);
}
}
ICEs with -fopenmp:
for-25.C: In function ‘void f1(J<int>)’:
for-25.C:121:9: internal compiler error: in gimplify_omp_for, at
gimplify.c:9621
#pragma omp distribute parallel for default(none)
^~~
0xee8310 gimplify_omp_for
../../gcc/gimplify.c:9621
0xef325c gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
../../gcc/gimplify.c:11921
0xed9b0e gimplify_stmt(tree_node**, gimple**)
../../gcc/gimplify.c:6618
0xec4cf0 gimplify_and_add(tree_node*, gimple**)
../../gcc/gimplify.c:441
0x8b0509 cp_gimplify_omp_for
../../gcc/cp/cp-gimplify.c:401
>From gcc-bugs-return-609449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 15:18:46 2018
Return-Path: <gcc-bugs-return-609449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91981 invoked by alias); 9 Jul 2018 15:18: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 91824 invoked by uid 48); 9 Jul 2018 15:18:42 -0000
From: "boris.staletic at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Mon, 09 Jul 2018 15: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: 8.1.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: boris.staletic 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-86422-4-SlLLNKXinK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00554.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #10 from Boris Staletic <boris.staletic at gmail dot com> ---
Running "g++ -S -fno-exceptions CodePoint.cpp" didn't run into OOM killer, but
gcc still hanged. The memory usage at maximum was 15.6GB. What I find strange
is that "htop" reported the g++ process as dead most of the time and the CPU
usage was 20% to 25% (or less) while that was happening.
>From gcc-bugs-return-609450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 15:25:20 2018
Return-Path: <gcc-bugs-return-609450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102365 invoked by alias); 9 Jul 2018 15:25: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 102077 invoked by uid 55); 9 Jul 2018 15:24:30 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86442] Wrong error: global register variable follows a function definition when using LTO
Date: Mon, 09 Jul 2018 15:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86442-4-Cre3MIO0Ym@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86442-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86442-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00555.txt.bz2
Content-length: 1223
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86442
--- Comment #1 from Jan Hubicka <hubicka at ucw dot cz> ---
> Following wrong error is printed with LTO:
>
> $ cat global.cpp
> register int a __asm__("r12");
>
> class b {
> public:
> b();
> };
>
> b c;
>
> int main() { a = 3; }
>
> $ g++ global.cpp -O2 -flto
> global.cpp: In function ‘main’:
> global.cpp:1:14: error: global register variable follows a function definition
> register int a __asm__("r12");
> ^
> lto-wrapper: fatal error: g++ returned 1 exit status
> compilation terminated.
> /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: error:
> lto-wrapper failed
> collect2: error: ld returned 1 exit status
Global register variables are not really working with LTO (because they should
be part of the function context since they may differ across units).
We could try to fix them for gcc 9. I was thinking a bit about it, but it
would
need to attach the information somewhere into optimization node and make
inliner
to not inline across different globally allocated registers.
It is overall questionable how global registers should interact with the symbol
table.
Honza
>From gcc-bugs-return-609451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 15:31:01 2018
Return-Path: <gcc-bugs-return-609451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5752 invoked by alias); 9 Jul 2018 15: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 5477 invoked by uid 55); 9 Jul 2018 15:30:37 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Mon, 09 Jul 2018 15:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86422-4-4XLtd4P7Vn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00556.txt.bz2
Content-length: 853
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #11 from rguenther at suse dot de <rguenther at suse dot de> ---
On July 9, 2018 5:18:40 PM GMT+02:00, "boris.staletic at gmail dot com"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
>
>--- Comment #10 from Boris Staletic <boris.staletic at gmail dot com>
>---
>Running "g++ -S -fno-exceptions CodePoint.cpp" didn't run into OOM
>killer, but
>gcc still hanged. The memory usage at maximum was 15.6GB. What I find
>strange
>is that "htop" reported the g++ process as dead most of the time and
>the CPU
>usage was 20% to 25% (or less) while that was happening.
That's to be expected when it runs into swap. GCC is bad at keeping the active
memory set small because it uses garbage collection and the mark and sweep
phase pages in everything...
>From gcc-bugs-return-609452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 15:34:55 2018
Return-Path: <gcc-bugs-return-609452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100991 invoked by alias); 9 Jul 2018 15:34: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 100947 invoked by uid 48); 9 Jul 2018 15:34:49 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86397] [7/8/9 Regression] g++ ICE at on valid code in nothrow_spec_p, at cp/except.c:1158
Date: Mon, 09 Jul 2018 15: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: 8.1.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-86397-4-TQAUxpblRi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86397-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86397-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00557.txt.bz2
Content-length: 584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86397
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-09
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed. Started with r244575.
>From gcc-bugs-return-609453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 15:35:22 2018
Return-Path: <gcc-bugs-return-609453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102071 invoked by alias); 9 Jul 2018 15:35: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 101957 invoked by uid 48); 9 Jul 2018 15:35:16 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86442] Wrong error: global register variable follows a function definition when using LTO
Date: Mon, 09 Jul 2018 15:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-86442-4-a5EUXrVN7w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86442-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86442-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00558.txt.bz2
Content-length: 891
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86442
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #2 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Indeed, I think the build system should be passing -fno-lto for such
translation units, as their ABI is different from the rest.
I'm not sure limiting the inliner is enough, there's also IPA-RA and it's not
obviously safe w.r.t global-reg-var differences.
If there's a desire to support such usage "seamlessly", I'd really like to see
the same solution for this and toplevel asms: making such input translation
unit one LTO partition (i.e. not splitting or merging it with anything else).
>From gcc-bugs-return-609454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 15:40:36 2018
Return-Path: <gcc-bugs-return-609454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107850 invoked by alias); 9 Jul 2018 15:40:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107751 invoked by uid 48); 9 Jul 2018 15:40:31 -0000
From: "boris.staletic at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Mon, 09 Jul 2018 15: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: 8.1.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: boris.staletic 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-86422-4-XQ9G8STKbk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00559.txt.bz2
Content-length: 277
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #12 from Boris Staletic <boris.staletic at gmail dot com> ---
If you're wondering about clang, it hangs too, but doesn't hog memory.
> That's to be expected when it runs into swap.
Anything else I should try?
>From gcc-bugs-return-609455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 15:46:34 2018
Return-Path: <gcc-bugs-return-609455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52072 invoked by alias); 9 Jul 2018 15: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 51957 invoked by uid 48); 9 Jul 2018 15:46:30 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86426] g++ ICE at on valid code in tree_operand_check, at tree.h:3615
Date: Mon, 09 Jul 2018 15:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-86426-4-Izz7T2NWw8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86426-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86426-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00560.txt.bz2
Content-length: 587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86426
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-09
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed, but even 4.6 ICEs for me.
>From gcc-bugs-return-609456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 15:57:19 2018
Return-Path: <gcc-bugs-return-609456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20679 invoked by alias); 9 Jul 2018 15:57: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 20606 invoked by uid 55); 9 Jul 2018 15:57:15 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86422] G++ ICE(segmentation fault) when compiling a huge static array of sufficiently complex structs
Date: Mon, 09 Jul 2018 15:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86422-4-kj4j62JumN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86422-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00561.txt.bz2
Content-length: 545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
--- Comment #13 from rguenther at suse dot de <rguenther at suse dot de> ---
On July 9, 2018 5:40:31 PM GMT+02:00, "boris.staletic at gmail dot com"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
>
>--- Comment #12 from Boris Staletic <boris.staletic at gmail dot com>
>---
>If you're wondering about clang, it hangs too, but doesn't hog memory.
>
>> That's to be expected when it runs into swap.
>
>Anything else I should try?
Nothing off my head.
>From gcc-bugs-return-609458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 17:33:46 2018
Return-Path: <gcc-bugs-return-609458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108115 invoked by alias); 9 Jul 2018 17:33:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107475 invoked by uid 48); 9 Jul 2018 17:33:39 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86421] OpenMP declare simd linear ref in module causes gfortran to bail out
Date: Mon, 09 Jul 2018 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: 8.1.0
X-Bugzilla-Keywords: error-recovery, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-86421-4-xEue9JBSbO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86421-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86421-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00563.txt.bz2
Content-length: 578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86421
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 44367
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44367&action=edit
gcc9-pr86421.patch
Untested fix.
>From gcc-bugs-return-609457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 17:33:39 2018
Return-Path: <gcc-bugs-return-609457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107134 invoked by alias); 9 Jul 2018 17:33: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 106916 invoked by uid 48); 9 Jul 2018 17:32:26 -0000
From: "craig.topper at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86444] New: [X86] Implementation of SSE comi/ucomi intrinsics does not match recent versions of icc, clang, or MSVC
Date: Mon, 09 Jul 2018 17:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: craig.topper 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-86444-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00562.txt.bz2
Content-length: 1050
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86444
Bug ID: 86444
Summary: [X86] Implementation of SSE comi/ucomi intrinsics does
not match recent versions of icc, clang, or MSVC
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: craig.topper at gmail dot com
Target Milestone: ---
It looks like gcc does not match the behavior of the most recent versions of
icc, clang, and MSVC with respect to the behavior or NaNs in the COMI
intrinsics. The other compilers are all returning 0 when the compare result is
unordered. As can be seen here: https://godbolt.org/g/xxEKqg
Clang changed to this behavior in version 3.9. According to this comment from
https://bugs.llvm.org/show_bug.cgi?id=28510#c10, the original icc behavior was
the same as gcc’s current behavior, but it was changed at least 10 years ago.
>From gcc-bugs-return-609459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 17:58:59 2018
Return-Path: <gcc-bugs-return-609459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65773 invoked by alias); 9 Jul 2018 17:58: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 65702 invoked by uid 48); 9 Jul 2018 17:58:53 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86440] -Wignored-qualifiers diagnostic highlights wrong token with pointer
Date: Mon, 09 Jul 2018 17:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-86440-4-BbUhy2nMVp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86440-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86440-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00564.txt.bz2
Content-length: 896
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86440
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-09
Ever confirmed|0 |1
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this bug.
Confirmed with trunk, gcc-8, and gcc-7.
gcc-6 and earlier put both warnings on the close-parentheses:
/tmp/test.cc:1:13: warning: type qualifiers ignored on function return type
[-Wignored-qualifiers]
int const f() { return 0; }
^
/tmp/test.cc:3:15: warning: type qualifiers ignored on function return type
[-Wignored-qualifiers]
int * const g() { return 0; }
^
>From gcc-bugs-return-609460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 18:22:53 2018
Return-Path: <gcc-bugs-return-609460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73104 invoked by alias); 9 Jul 2018 18:22:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73071 invoked by uid 48); 9 Jul 2018 18:22:49 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86445] New: [9 regression] Missing warning for test case gcc/testsuite/gcc.dg/pr84100.c starting with r262513
Date: Mon, 09 Jul 2018 18:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.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-86445-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00565.txt.bz2
Content-length: 1562
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86445
Bug ID: 86445
Summary: [9 regression] Missing warning for test case
gcc/testsuite/gcc.dg/pr84100.c starting with r262513
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
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/pr84100.c
-fno-diagnostics-show-caret -fdiagnostics-color=never -O2 -S -o pr84100.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/pr84100.c
-fno-diagnostics-show-caret -fdiagnostics-color=never -O2 -S -o pr84100.s
FAIL: gcc.dg/pr84100.c (test for warnings, line 11)
PASS: gcc.dg/pr84100.c (test for excess errors)
testcase /home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/dg.exp completed in 0
seconds
=== gcc Summary ===
# of expected passes 1
# of unexpected failures 1
It is not generating this warning now:
home/seurer/gcc/gcc-test/gcc/testsuite/gcc.dg/pr84100.c:11:1: warning: bad
option '-falign-loops=16' to attribute 'optimize' [-Wattributes]
Note the test case was updated in r262375 just last week.
>From gcc-bugs-return-609461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 18:26:21 2018
Return-Path: <gcc-bugs-return-609461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95854 invoked by alias); 9 Jul 2018 18:26: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 95808 invoked by uid 48); 9 Jul 2018 18:26:16 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86446] New: 'gmake check-fortran' broken in libgomp
Date: Mon, 09 Jul 2018 18:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00566.txt.bz2
Content-length: 3579
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
Bug ID: 86446
Summary: 'gmake check-fortran' broken in libgomp
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
=== libgomp Summary ===
# of expected passes 4021
# of unexpected failures 2
# of unsupported tests 134
gmake[4]: *** [Makefile:306: check-DEJAGNU] Error 1
gmake[4]: Leaving directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp/testsuite'
gmake[3]: *** [Makefile:350: check-am] Error 2
gmake[3]: Leaving directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp/testsuite'
gmake[3]: Entering directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp'
gmake DO=all multi-do # gmake
gmake[4]: Entering directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp'
if [ -z "" ]; then \
true; \
else \
rootpre=`${PWDCMD-pwd}`/; export rootpre; \
srcrootpre=`cd ../../../gcc/libgomp; ${PWDCMD-pwd}`/; export srcrootpre; \
lib=`echo "${rootpre}" | sed -e 's,^.*/\([^/][^/]*\)/$,\1,'`; \
compiler="/safe/sgk/gcc/obj/./gcc/xgcc -B/safe/sgk/gcc/obj/./gcc/
-B/safe/sgk/work/x/x86_64-unknown-freebsd12.0/bin/
-B/safe/sgk/work/x/x86_64-unknown-freebsd12.0/lib/ -isystem
/safe/sgk/work/x/x86_64-unknown-freebsd12.0/include -isystem
/safe/sgk/work/x/x86_64-unknown-freebsd12.0/sys-include "; \
for i in `${compiler} --print-multi-lib 2>/dev/null`; do \
dir=`echo $i | sed -e 's/;.*$//'`; \
if [ "${dir}" = "." ]; then \
true; \
else \
if [ -d ../${dir}/${lib} ]; then \
flags=`echo $i | sed -e 's/^[^;]*;//' -e 's/@/ -/g'`; \
if (cd ../${dir}/${lib}; gmake \
CFLAGS="-g -O2 ${flags}" \
CCASFLAGS=" ${flags}" \
FCFLAGS="-L. -Wall -L../libgfortran ${flags}" \
FFLAGS=" ${flags}" \
ADAFLAGS=" ${flags}" \
prefix="/safe/sgk/work/x" \
exec_prefix="/safe/sgk/work/x" \
GOCFLAGS="-O2 -g ${flags}" \
CXXFLAGS="-g -O2 ${flags}" \
LIBCFLAGS="-g -O2 ${flags}" \
LIBCXXFLAGS="-g -O2 -fno-implicit-templates ${flags}" \
LDFLAGS=" ${flags}" \
MULTIFLAGS="${flags}" \
DESTDIR="" \
INSTALL="/usr/bin/install -c" \
INSTALL_DATA="/usr/bin/install -c -m 644" \
INSTALL_PROGRAM="/usr/bin/install -c" \
INSTALL_SCRIPT="/usr/bin/install -c" \
all); then \
true; \
else \
exit 1; \
fi; \
else true; \
fi; \
fi; \
done; \
fi
gmake[4]: Leaving directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp'
:
:
:
gmake[3]: Leaving directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp'
gmake[2]: *** [Makefile:904: check-recursive] Error 1
gmake[2]: Leaving directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp'
gmake[1]: *** [Makefile:21394: check-target-libgomp] Error 2
gmake[1]: Leaving directory '/safe/sgk/gcc/obj'
gmake: *** [Makefile:22584: check-target-libgomp-fortran] Error 2
>From gcc-bugs-return-609462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 18:52:43 2018
Return-Path: <gcc-bugs-return-609462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100726 invoked by alias); 9 Jul 2018 18:52: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 100521 invoked by uid 48); 9 Jul 2018 18:52:38 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/86438] [8/9 Regression] wrong code at -Os
Date: Mon, 09 Jul 2018 18:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86438-4-kegBUIOeg6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86438-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86438-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00567.txt.bz2
Content-length: 570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86438
--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
Here is what happens:
compare operators in (insn 66) are substituted with their defs from (insn 64)
and (insn 14). The CC mode is calculated from SELECT_CC_MODE, which really
returns CCCmode. The flags reg clobber is substituted with the compare, and
insn then matches {*adddi3_cc_overflow_1}.
Unfortunately, the compare is not correct. %rax from (insn 14) is already
updated, and should not be compared with its previous value from (insn 64).
>From gcc-bugs-return-609463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 19:20:09 2018
Return-Path: <gcc-bugs-return-609463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116678 invoked by alias); 9 Jul 2018 19:20:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116577 invoked by uid 48); 9 Jul 2018 19:20:03 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86446] 'gmake check-fortran' broken in libgomp
Date: Mon, 09 Jul 2018 19:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.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-86446-4-J1ZHw4jheG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00568.txt.bz2
Content-length: 633
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
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 #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
The correct invocation of a GCC testsuite is "make -k check-blah", otherwise
the recursive Make processes will stop on errors.
>From gcc-bugs-return-609464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 19:33:53 2018
Return-Path: <gcc-bugs-return-609464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8890 invoked by alias); 9 Jul 2018 19:33: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 8830 invoked by uid 55); 9 Jul 2018 19:33:48 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86446] 'gmake check-fortran' broken in libgomp
Date: Mon, 09 Jul 2018 19:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
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-86446-4-Zw2SmwSizD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00569.txt.bz2
Content-length: 1312
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
--- Comment #2 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Mon, Jul 09, 2018 at 07:20:02PM +0000, ebotcazou at gcc dot gnu.org wrote:
>
> The correct invocation of a GCC testsuite is "make -k check-blah", otherwise
> the recursive Make processes will stop on errors.
>
Since when? I've been doing 'gmake check-fortran' and
'gmake -j6 check-fortran' for more than 15 years. There
was never an error. This broke recently.
I just did a bootstrap of the 8-branch. 'gmake -j6 check-fortran'
completes without an error. The last few line are
=== gfortran Summary ===
# of expected passes 6413
# of expected failures 18
# of unsupported tests 2
/safe/sgk/gcc/obj8/gcc/gfortran version 8.1.1 20180709 (GCC)
gmake[2]: Leaving directory '/safe/sgk/gcc/obj8/gcc'
gmake[1]: Leaving directory '/safe/sgk/gcc/obj8/gcc'
Something is broken with trunk. These do not occur on
the 8-branch.
gmake[4]: *** [Makefile:306: check-DEJAGNU] Error 1
gmake[4]: Leaving directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp/testsuite'
gmake[3]: *** [Makefile:350: check-am] Error 2
gmake[3]: Leaving directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp
>From gcc-bugs-return-609465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 19:42:44 2018
Return-Path: <gcc-bugs-return-609465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111554 invoked by alias); 9 Jul 2018 19:42:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 111525 invoked by uid 48); 9 Jul 2018 19:42:39 -0000
From: "mateuszb at poczta dot onet.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86447] New: gcc 9.0 from r262456 can't build cross compiler for mingw-w64 target
Date: Mon, 09 Jul 2018 19:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mateuszb at poczta dot onet.pl
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-86447-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00570.txt.bz2
Content-length: 2917
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86447
Bug ID: 86447
Summary: gcc 9.0 from r262456 can't build cross compiler for
mingw-w64 target
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: mateuszb at poczta dot onet.pl
Target Milestone: ---
Target: mingw-w64
>From r262456 when I compile cross compiler (in Ubuntu) for mingw-w64 target
there is a bug:
libtool: compile: /home/ma/m/build/bc_gcc/./gcc/xgcc -shared-libgcc
-B/home/ma/m/build/bc_gcc/./gcc -nostdinc++
-L/home/ma/m/build/bc_gcc/x86_64-w64-mingw32/libstdc++-v3/src
-L/home/ma/m/build/bc_gcc/x86_64-w64-mingw32/libstdc++-v3/src/.libs
-L/home/ma/m/build/bc_gcc/x86_64-w64-mingw32/libstdc++-v3/libsupc++/.libs
-L/home/ma/m/cross/x86_64-w64-mingw32/lib -L/home/ma/m/cross/mingw/lib -isystem
/home/ma/m/cross/x86_64-w64-mingw32/include -isystem
/home/ma/m/cross/mingw/include -B/home/ma/m/cross/x86_64-w64-mingw32/bin/
-B/home/ma/m/cross/x86_64-w64-mingw32/lib/ -isystem
/home/ma/m/cross/x86_64-w64-mingw32/include -isystem
/home/ma/m/cross/x86_64-w64-mingw32/sys-include
-I/home/ma/m/source/gcc-9/libstdc++-v3/../libgcc
-I/home/ma/m/build/bc_gcc/x86_64-w64-mingw32/libstdc++-v3/include/x86_64-w64-mingw32
-I/home/ma/m/build/bc_gcc/x86_64-w64-mingw32/libstdc++-v3/include
-I/home/ma/m/source/gcc-9/libstdc++-v3/libsupc++ -std=gnu++11
-fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi
-fdiagnostics-show-location=once -ffunction-sections -fdata-sections
-frandom-seed=cow-stdexcept.lo -g -O2 -c
/home/ma/m/source/gcc-9/libstdc++-v3/src/c++11/cow-stdexcept.cc -o
cow-stdexcept.o
cc1plus: warning: -Wabi won't warn about anything [-Wabi]
cc1plus: note: -Wabi warns about differences from the most up-to-date ABI,
which is also used by default
cc1plus: note: use e.g. -Wabi=11 to warn about changes from GCC 7
/home/ma/m/source/gcc-9/libstdc++-v3/src/c++11/cow-stdexcept.cc:67:3: error:
function 'std::logic_error::logic_error(std::logic_error&&)' defaulted on its
redeclaration with an exception-specification that differs from the implicit
exception-specification ''
logic_error::logic_error(logic_error&& e) noexcept = default;
^~~~~~~~~~~
/home/ma/m/source/gcc-9/libstdc++-v3/src/c++11/cow-stdexcept.cc:79:3: error:
function 'std::runtime_error::runtime_error(std::runtime_error&&)' defaulted on
its redeclaration with an exception-specification that differs from the
implicit exception-specification ''
runtime_error::runtime_error(runtime_error&& e) noexcept = default;
^~~~~~~~~~~~~
Makefile:562: recipe for target 'cow-stdexcept.lo' failed
make[5]: *** [cow-stdexcept.lo] Error 1
The bug is in phase when new compiled gcc is trying to compile libraries.
>From gcc-bugs-return-609466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 19:55:17 2018
Return-Path: <gcc-bugs-return-609466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14787 invoked by alias); 9 Jul 2018 19:55:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14697 invoked by uid 55); 9 Jul 2018 19:55:12 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86446] 'gmake check-fortran' broken in libgomp
Date: Mon, 09 Jul 2018 19:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
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-86446-4-xswwN2Vfua@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00571.txt.bz2
Content-length: 1581
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Mon, Jul 09, 2018 at 07:33:48PM +0000, sgk at troutmask dot
apl.washington.edu wrote:
>
> gmake[4]: *** [Makefile:306: check-DEJAGNU] Error 1
> gmake[4]: Leaving directory
> '/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp/testsuite'
> gmake[3]: *** [Makefile:350: check-am] Error 2
> gmake[3]: Leaving directory
> '/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libgomp
>
If I comment out lines 306-316 in
./x86_64-unknown-freebsd12.0/libgomp/testsuite/Makefile
check-DEJAGNU: site.exp
# srcdir='$(srcdir)'; export srcdir; \
# EXPECT=$(EXPECT); export EXPECT; \
# runtest=$(RUNTEST); \
# if $(SHELL) -c "$$runtest --version" > /dev/null 2>&1; then \
# exit_status=0; l='$(DEJATOOL)'; for tool in $$l; do \
# if $$runtest $(AM_RUNTESTFLAGS) $(RUNTESTDEFAULTFLAGS)
$(RUNTESTFLAGS); \
# then :; else exit_status=1; fi; \
# done; \
# else echo "WARNING: could not find \`runtest'" 1>&2; :;\
# fi; \
# exit $$exit_status
gmake -j6 check-fortran completes with
=== gfortran Summary ===
# of expected passes 8017
# of expected failures 3
# of unsupported tests 24
/safe/sgk/gcc/obj/gcc/gfortran version 9.0.0 20180709 (experimental) (GCC)
gmake[2]: Leaving directory '/safe/sgk/gcc/obj/gcc'
gmake[1]: Leaving directory '/safe/sgk/gcc/obj/gcc'
as I expect. This check is bogus.
>From gcc-bugs-return-609467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 20:22:07 2018
Return-Path: <gcc-bugs-return-609467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25969 invoked by alias); 9 Jul 2018 20:22: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 25799 invoked by uid 48); 9 Jul 2018 20:22:03 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86448] New: GCC 9 compiler generates slower code for spec 2006 milc on a power9 using -mcpu=power9 than using -mcpu=power8
Date: Mon, 09 Jul 2018 20:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: meissner at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86448-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00572.txt.bz2
Content-length: 774
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86448
Bug ID: 86448
Summary: GCC 9 compiler generates slower code for spec 2006
milc on a power9 using -mcpu=power9 than using
-mcpu=power8
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: meissner at gcc dot gnu.org
Target Milestone: ---
I built spec 2006 on a DD2.2 power9 and ran it. I noticed that the milc
benchmark was 2% slower using either the trunk or the GCC 8 branch (subversion
id 262483) if I compiled the code using -mcpu=power9 compared to -mcpu=power8.
>From gcc-bugs-return-609468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 20:29:59 2018
Return-Path: <gcc-bugs-return-609468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59233 invoked by alias); 9 Jul 2018 20:29:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59183 invoked by uid 48); 9 Jul 2018 20:29:55 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86449] New: GCC 8 compiler generates slower code for spec 2006 calculix on a power9 using -mcpu=power9 than using -mcpu=power8
Date: Mon, 09 Jul 2018 20:29: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: 8.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: meissner at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-86449-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00573.txt.bz2
Content-length: 891
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86449
Bug ID: 86449
Summary: GCC 8 compiler generates slower code for spec 2006
calculix on a power9 using -mcpu=power9 than using
-mcpu=power8
Product: gcc
Version: 8.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: meissner at gcc dot gnu.org
Target Milestone: ---
I ran spec 2006 on a DD2.2 power9, and I noticed the GCC 8.x branch (subversion
id 26248) generated slower code for calculix when compiled with a -mcpu=power9
option instead of -mcpu=power8.
Note, the trunk actually generates 2% faster code for -mcpu=power9 than for
-mcpu=power8. This issue is only a regression on the GCC 8 branch.
>From gcc-bugs-return-609469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 20:34:26 2018
Return-Path: <gcc-bugs-return-609469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88312 invoked by alias); 9 Jul 2018 20:34:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88197 invoked by uid 55); 9 Jul 2018 20:34:20 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86428] strlen of const array initialized with a string of the same length not folded
Date: Mon, 09 Jul 2018 20:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, 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-86428-4-6U3YiM4vS9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86428-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86428-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00574.txt.bz2
Content-length: 1648
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86428
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Mon Jul 9 20:33:48 2018
New Revision: 262522
URL: https://gcc.gnu.org/viewcvs?rev=262522&root=gcc&view=rev
Log:
PR middle-end/77357 - strlen of constant strings not folded
gcc/ChangeLog:
PR middle-end/77357
PR middle-end/86428
* builtins.c (c_strlen): Avoid out-of-bounds warnings when
accessing implicitly initialized array elements.
* expr.c (string_constant): Handle string initializers of
character arrays within aggregates.
* gimple-fold.c (fold_array_ctor_reference): Add argument.
Store element offset. As a special case, handle zero size.
(fold_nonarray_ctor_reference): Same.
(fold_ctor_reference): Add argument. Store subobject offset.
* gimple-fold.h (fold_ctor_reference): Add argument.
gcc/testsuite/ChangeLog:
PR middle-end/77357
* gcc.dg/strlenopt-49.c: New test.
* gcc.dg/strlenopt-50.c: New test.
* gcc.dg/strlenopt-51.c: New test.
* gcc.dg/strlenopt-52.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/strlenopt-49.c
trunk/gcc/testsuite/gcc.dg/strlenopt-50.c
trunk/gcc/testsuite/gcc.dg/strlenopt-51.c
trunk/gcc/testsuite/gcc.dg/strlenopt-52.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/builtins.c
trunk/gcc/expr.c
trunk/gcc/fold-const.c
trunk/gcc/fold-const.h
trunk/gcc/gimple-fold.c
trunk/gcc/gimple-fold.h
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.c-torture/execute/builtins/strlen-3.c
>From gcc-bugs-return-609470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 20:34:26 2018
Return-Path: <gcc-bugs-return-609470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88320 invoked by alias); 9 Jul 2018 20:34:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88195 invoked by uid 55); 9 Jul 2018 20:34:20 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/77357] strlen of constant strings not folded
Date: Mon, 09 Jul 2018 20:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: missed-optimization, patch
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77357-4-WEn590iaAJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77357-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77357-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00575.txt.bz2
Content-length: 1648
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77357
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Mon Jul 9 20:33:48 2018
New Revision: 262522
URL: https://gcc.gnu.org/viewcvs?rev=262522&root=gcc&view=rev
Log:
PR middle-end/77357 - strlen of constant strings not folded
gcc/ChangeLog:
PR middle-end/77357
PR middle-end/86428
* builtins.c (c_strlen): Avoid out-of-bounds warnings when
accessing implicitly initialized array elements.
* expr.c (string_constant): Handle string initializers of
character arrays within aggregates.
* gimple-fold.c (fold_array_ctor_reference): Add argument.
Store element offset. As a special case, handle zero size.
(fold_nonarray_ctor_reference): Same.
(fold_ctor_reference): Add argument. Store subobject offset.
* gimple-fold.h (fold_ctor_reference): Add argument.
gcc/testsuite/ChangeLog:
PR middle-end/77357
* gcc.dg/strlenopt-49.c: New test.
* gcc.dg/strlenopt-50.c: New test.
* gcc.dg/strlenopt-51.c: New test.
* gcc.dg/strlenopt-52.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/strlenopt-49.c
trunk/gcc/testsuite/gcc.dg/strlenopt-50.c
trunk/gcc/testsuite/gcc.dg/strlenopt-51.c
trunk/gcc/testsuite/gcc.dg/strlenopt-52.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/builtins.c
trunk/gcc/expr.c
trunk/gcc/fold-const.c
trunk/gcc/fold-const.h
trunk/gcc/gimple-fold.c
trunk/gcc/gimple-fold.h
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.c-torture/execute/builtins/strlen-3.c
>From gcc-bugs-return-609472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 20:35:39 2018
Return-Path: <gcc-bugs-return-609472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106188 invoked by alias); 9 Jul 2018 20:35:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106120 invoked by uid 48); 9 Jul 2018 20:35:35 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83819] [meta-bug] missing strlen optimizations
Date: Mon, 09 Jul 2018 20:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-83819-4-4xiFdqcabt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00577.txt.bz2
Content-length: 463
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819
Bug 83819 depends on bug 77357, which changed state.
Bug 77357 Summary: strlen of constant strings not folded
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77357
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-609471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 20:35:38 2018
Return-Path: <gcc-bugs-return-609471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106175 invoked by alias); 9 Jul 2018 20:35:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106101 invoked by uid 48); 9 Jul 2018 20:35:34 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/77357] strlen of constant strings not folded
Date: Mon, 09 Jul 2018 20:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: missed-optimization, patch
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-77357-4-k6ZAn2cRM6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77357-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77357-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00576.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77357
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
Committed in r262522.
>From gcc-bugs-return-609473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 20:35:51 2018
Return-Path: <gcc-bugs-return-609473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107573 invoked by alias); 9 Jul 2018 20:35:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107388 invoked by uid 48); 9 Jul 2018 20:35:47 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86428] strlen of const array initialized with a string of the same length not folded
Date: Mon, 09 Jul 2018 20:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, 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-86428-4-96BQtH0Dof@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86428-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86428-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00578.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86428
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Committed in r262522.
>From gcc-bugs-return-609474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 20:35:52 2018
Return-Path: <gcc-bugs-return-609474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107589 invoked by alias); 9 Jul 2018 20:35:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107445 invoked by uid 48); 9 Jul 2018 20:35:48 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83819] [meta-bug] missing strlen optimizations
Date: Mon, 09 Jul 2018 20:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-83819-4-FnTczBTmUr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00579.txt.bz2
Content-length: 505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819
Bug 83819 depends on bug 86428, which changed state.
Bug 86428 Summary: strlen of const array initialized with a string of the same length not folded
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86428
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-609475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 21:12:36 2018
Return-Path: <gcc-bugs-return-609475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110746 invoked by alias); 9 Jul 2018 21:12: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 110689 invoked by uid 48); 9 Jul 2018 21:12:31 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/86450] New: Bootstrap failure due to -Wabi
Date: Mon, 09 Jul 2018 21:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-86450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00580.txt.bz2
Content-length: 9192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
Bug ID: 86450
Summary: Bootstrap failure due to -Wabi
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: tkoenig at gcc dot gnu.org
Target Milestone: ---
Created attachment 44368
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44368&action=edit
config.log from failed build
Recent trunk at r262520 failed to build on, it was configured with
$ CC=/usr/bin/gcc CXX=/usr/bin/g++ ../trunk/configure --prefix=$HOME
--enable-languages=c,c++,fortran --enable-maintainer-mode
for x86_64-pc-linux-gnu and then built with
$ make -j8
which led to the errors
ibtool: compile: /home/ig25/Gcc/trunk-bin/./gcc/xgcc -shared-libgcc
-B/home/ig25/Gcc/trunk-bin/./gcc -nostdinc++
-L/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/src
-L/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/home/ig25/x86_64-pc-linux-gnu/bin/ -B/home/ig25/x86_64-pc-linux-gnu/lib/
-isystem /home/ig25/x86_64-pc-linux-gnu/include -isystem
/home/ig25/x86_64-pc-linux-gnu/sys-include -fno-checking
-I/home/ig25/Gcc/trunk/libstdc++-v3/../libgcc
-I/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu
-I/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/include
-I/home/ig25/Gcc/trunk/libstdc++-v3/libsupc++ -D_GLIBCXX_SHARED
-fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi -Werror
-fdiagnostics-show-location=once -ffunction-sections -fdata-sections
-frandom-seed=bad_array_length.lo -g -O2 -D_GNU_SOURCE -c
../../../../trunk/libstdc++-v3/libsupc++/bad_array_length.cc -fPIC -DPIC
-D_GLIBCXX_SHARED -o bad_array_length.o
cc1plus: error: -Wabi won't warn about anything [-Werror=abi]
cc1plus: error: -Wabi won't warn about anything [-Werror=abi]
cc1plus: note: -Wabi warns about differences from the most up-to-date ABI,
which is also used by default
cc1plus: note: use e.g. -Wabi=11 to warn about changes from GCC 7
cc1plus: note: -Wabi warns about differences from the most up-to-date ABI,
which is also used by default
cc1plus: note: use e.g. -Wabi=11 to warn about changes from GCC 7
libtool: compile: /home/ig25/Gcc/trunk-bin/./gcc/xgcc -shared-libgcc
-B/home/ig25/Gcc/trunk-bin/./gcc -nostdinc++
-L/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/src
-L/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/home/ig25/x86_64-pc-linux-gnu/bin/ -B/home/ig25/x86_64-pc-linux-gnu/lib/
-isystem /home/ig25/x86_64-pc-linux-gnu/include -isystem
/home/ig25/x86_64-pc-linux-gnu/sys-include -fno-checking
-I/home/ig25/Gcc/trunk/libstdc++-v3/../libgcc
-I/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu
-I/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/include
-I/home/ig25/Gcc/trunk/libstdc++-v3/libsupc++ -D_GLIBCXX_SHARED
-fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi -Werror
-fdiagnostics-show-location=once -ffunction-sections -fdata-sections
-frandom-seed=bad_array_new.lo -g -O2 -D_GNU_SOURCE -c
../../../../trunk/libstdc++-v3/libsupc++/bad_array_new.cc -fPIC -DPIC
-D_GLIBCXX_SHARED -o bad_array_new.o
cc1plus: error: -Wabi won't warn about anything [-Werror=abi]
cc1plus: note: -Wabi warns about differences from the most up-to-date ABI,
which is also used by default
cc1plus: note: use e.g. -Wabi=11 to warn about changes from GCC 7
libtool: compile: /home/ig25/Gcc/trunk-bin/./gcc/xgcc -shared-libgcc
-B/home/ig25/Gcc/trunk-bin/./gcc -nostdinc++
-L/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/src
-L/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/home/ig25/x86_64-pc-linux-gnu/bin/ -B/home/ig25/x86_64-pc-linux-gnu/lib/
-isystem /home/ig25/x86_64-pc-linux-gnu/include -isystem
/home/ig25/x86_64-pc-linux-gnu/sys-include -fno-checking
-I/home/ig25/Gcc/trunk/libstdc++-v3/../libgcc
-I/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu
-I/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/include
-I/home/ig25/Gcc/trunk/libstdc++-v3/libsupc++ -D_GLIBCXX_SHARED
-fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi -Werror
-fdiagnostics-show-location=once -ffunction-sections -fdata-sections
-frandom-seed=bad_typeid.lo -g -O2 -D_GNU_SOURCE -c
../../../../trunk/libstdc++-v3/libsupc++/bad_typeid.cc -fPIC -DPIC
-D_GLIBCXX_SHARED -o bad_typeid.o
libtool: compile: /home/ig25/Gcc/trunk-bin/./gcc/xgcc -shared-libgcc
-B/home/ig25/Gcc/trunk-bin/./gcc -nostdinc++
-L/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/src
-L/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/home/ig25/x86_64-pc-linux-gnu/bin/ -B/home/ig25/x86_64-pc-linux-gnu/lib/
-isystem /home/ig25/x86_64-pc-linux-gnu/include -isystem
/home/ig25/x86_64-pc-linux-gnu/sys-include -fno-checking
-I/home/ig25/Gcc/trunk/libstdc++-v3/../libgcc
-I/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu
-I/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/include
-I/home/ig25/Gcc/trunk/libstdc++-v3/libsupc++ -D_GLIBCXX_SHARED
-fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi -Werror
-fdiagnostics-show-location=once -ffunction-sections -fdata-sections
-frandom-seed=atexit_thread.lo -g -O2 -D_GNU_SOURCE -c
../../../../trunk/libstdc++-v3/libsupc++/atexit_thread.cc -fPIC -DPIC
-D_GLIBCXX_SHARED -o atexit_thread.o
cc1plus: error: -Wabi won't warn about anything [-Werror=abi]
cc1plus: note: -Wabi warns about differences from the most up-to-date ABI,
which is also used by default
cc1plus: note: use e.g. -Wabi=11 to warn about changes from GCC 7
cc1plus: error: -Wabi won't warn about anything [-Werror=abi]
cc1plus: note: -Wabi warns about differences from the most up-to-date ABI,
which is also used by default
cc1plus: note: use e.g. -Wabi=11 to warn about changes from GCC 7
cc1plus: error: -Wabi won't warn about anything [-Werror=abi]
cc1plus: note: -Wabi warns about differences from the most up-to-date ABI,
which is also used by default
cc1plus: note: use e.g. -Wabi=11 to warn about changes from GCC 7
cc1plus: error: -Wabi won't warn about anything [-Werror=abi]
cc1plus: note: -Wabi warns about differences from the most up-to-date ABI,
which is also used by default
cc1plus: note: use e.g. -Wabi=11 to warn about changes from GCC 7
cc1plus: error: -Wabi won't warn about anything [-Werror=abi]
cc1plus: note: -Wabi warns about differences from the most up-to-date ABI,
which is also used by default
cc1plus: note: use e.g. -Wabi=11 to warn about changes from GCC 7
cc1plus: all warnings being treated as errors
Makefile:669: recipe for target 'atexit_arm.lo' failed
make[5]: *** [atexit_arm.lo] Error 1
make[5]: *** Waiting for unfinished jobs....
cc1plus: all warnings being treated as errors
Makefile:669: recipe for target 'bad_typeid.lo' failed
make[5]: *** [bad_typeid.lo] Error 1
cc1plus: all warnings being treated as errors
Makefile:669: recipe for target 'bad_cast.lo' failed
make[5]: *** [bad_cast.lo] Error 1
cc1plus: all warnings being treated as errors
Makefile:669: recipe for target 'array_type_info.lo' failed
make[5]: *** [array_type_info.lo] Error 1
cc1plus: all warnings being treated as errors
Makefile:669: recipe for target 'bad_array_length.lo' failed
make[5]: *** [bad_array_length.lo] Error 1
cc1plus: all warnings being treated as errors
cc1plus: all warnings being treated as errors
Makefile:669: recipe for target 'bad_alloc.lo' failed
make[5]: *** [bad_alloc.lo] Error 1
Makefile:669: recipe for target 'bad_array_new.lo' failed
make[5]: *** [bad_array_new.lo] Error 1
cc1plus: all warnings being treated as errors
Makefile:669: recipe for target 'atexit_thread.lo' failed
make[5]: *** [atexit_thread.lo] Error 1
make[5]: Leaving directory
'/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++'
Makefile:511: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
'/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3'
Makefile:418: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory
'/home/ig25/Gcc/trunk-bin/x86_64-pc-linux-gnu/libstdc++-v3'
Makefile:19389: recipe for target 'all-stage1-target-libstdc++-v3' failed
make[2]: *** [all-stage1-target-libstdc++-v3] Error 2
make[2]: Leaving directory '/home/ig25/Gcc/trunk-bin'
Makefile:27025: recipe for target 'stage1-bubble' failed
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory '/home/ig25/Gcc/trunk-bin'
Makefile:959: recipe for target 'all' failed
make: *** [all] Error 2
Well, that's it for hacking gfortran this evening.
>From gcc-bugs-return-609476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 21:23:09 2018
Return-Path: <gcc-bugs-return-609476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92707 invoked by alias); 9 Jul 2018 21:23: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 92638 invoked by uid 48); 9 Jul 2018 21:23:04 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86417] [9 Regression] FAIL: libgomp.fortran/alloc-comp-3.f90 -O0 (test for excess errors)
Date: Mon, 09 Jul 2018 21: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: 9.0
X-Bugzilla-Keywords: diagnostic
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86417-4-VE8SnU73rr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86417-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86417-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00581.txt.bz2
Content-length: 1538
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86417
--- Comment #11 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to janus from comment #10)
> (In reply to janus from comment #9)
> > The following patch seems to be sufficient to fix the regression:
>
>
> ... however, it lacks a safety check for the existence of the ctor
> expression. This variant regtests cleanly:
>
>
> Index: gcc/fortran/expr.c
> ===================================================================
> --- gcc/fortran/expr.c (revision 262509)
> +++ gcc/fortran/expr.c (working copy)
> @@ -4650,6 +4650,10 @@ gfc_generate_initializer (gfc_typespec *ts, bool g
> }
> }
>
> + /* Make sure that locus is set. */
> + if (ctor->expr && (!ctor->expr->where.nextc || !ctor->expr->where.lb))
> + ctor->expr->where = init->where;
> +
> gfc_constructor_append (&init->value.constructor, ctor);
> }
If possible, I would prefer to set the locus where it is generated,
not conditionally later.
Unfortunately, I cannot currently look into this due to PR 86450 :-(
If I had a bootstrapping gcc, I would probably look at
/* Fetch or generate an initializer for the component. */
tmp = component_initializer (comp, generate);
and see if the locus is set correctly at that point, then
(possibly) go back to component_initializer to see where this is
missing.
>From gcc-bugs-return-609477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 22:05:28 2018
Return-Path: <gcc-bugs-return-609477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128183 invoked by alias); 9 Jul 2018 22:05: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 128121 invoked by uid 48); 9 Jul 2018 22:05:23 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86446] 'gmake check-fortran' broken in libgomp
Date: Mon, 09 Jul 2018 22: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: 9.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:
Message-ID: <bug-86446-4-Wi48kRq1y6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00582.txt.bz2
Content-length: 204
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Since when?
The dawn of time, see https://gcc.gnu.org/contribute.html#testing
>From gcc-bugs-return-609478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 22:18:16 2018
Return-Path: <gcc-bugs-return-609478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11533 invoked by alias); 9 Jul 2018 22:18: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 11467 invoked by uid 55); 9 Jul 2018 22:18:10 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86446] 'gmake check-fortran' broken in libgomp
Date: Mon, 09 Jul 2018 22:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
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-86446-4-rfiTexZD6i@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00583.txt.bz2
Content-length: 638
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
--- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Mon, Jul 09, 2018 at 10:05:23PM +0000, ebotcazou at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
>
> --- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> > Since when?
>
> The dawn of time, see https://gcc.gnu.org/contribute.html#testing
>
'gmake -j6 check-fortran' has never died on an error
like the one I've shown in the 15+ years that I've been
contributing to GCC. Needing -k now, means someone has
broken the build infrastructure.
>From gcc-bugs-return-609479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 22:21:24 2018
Return-Path: <gcc-bugs-return-609479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13912 invoked by alias); 9 Jul 2018 22: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 13866 invoked by uid 48); 9 Jul 2018 22:21:20 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86446] 'gmake check-fortran' broken in libgomp
Date: Mon, 09 Jul 2018 22:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.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:
Message-ID: <bug-86446-4-sLxsuFnEbF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00584.txt.bz2
Content-length: 401
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
--- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> 'gmake -j6 check-fortran' has never died on an error
> like the one I've shown in the 15+ years that I've been
> contributing to GCC. Needing -k now, means someone has
> broken the build infrastructure.
No, it's just https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01023.html
>From gcc-bugs-return-609480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 22:33:34 2018
Return-Path: <gcc-bugs-return-609480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35916 invoked by alias); 9 Jul 2018 22:33: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 35827 invoked by uid 55); 9 Jul 2018 22:33:30 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86446] 'gmake check-fortran' broken in libgomp
Date: Mon, 09 Jul 2018 22:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
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-86446-4-IKBEogvovD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00585.txt.bz2
Content-length: 1412
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
--- Comment #7 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Mon, Jul 09, 2018 at 10:21:20PM +0000, ebotcazou at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
>
> --- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> > 'gmake -j6 check-fortran' has never died on an error
> > like the one I've shown in the 15+ years that I've been
> > contributing to GCC. Needing -k now, means someone has
> > broken the build infrastructure.
>
> No, it's just https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01023.html
>
So, instead of using -k to pape over an error in the Makefile,
what is wrong with the lines
check-DEJAGNU: site.exp
srcdir='$(srcdir)'; export srcdir; \
EXPECT=$(EXPECT); export EXPECT; \
runtest=$(RUNTEST); \
if $(SHELL) -c "$$runtest --version" > /dev/null 2>&1; then \
exit_status=0; l='$(DEJATOOL)'; for tool in $$l; do \
if $$runtest $(AM_RUNTESTFLAGS) $(RUNTESTDEFAULTFLAGS)
$(RUNTESTFLAGS); \
then :; else exit_status=1; fi; \
done; \
else echo "WARNING: could not find \`runtest'" 1>&2; :;\
fi; \
exit $$exit_status
If the commands are command out, there are no errors. So,
what is the above suppose to do other that cause 2 ERRORs
in the build.
>From gcc-bugs-return-609481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jul 09 23:31:06 2018
Return-Path: <gcc-bugs-return-609481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70959 invoked by alias); 9 Jul 2018 23:31: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 70819 invoked by uid 48); 9 Jul 2018 23:30:51 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86446] 'gmake check-fortran' broken in libgomp
Date: Mon, 09 Jul 2018 23:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86446-4-xDX6Xwy5SX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00586.txt.bz2
Content-length: 525
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
--- Comment #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> > The correct invocation of a GCC testsuite is "make -k check-blah", otherwise
> > the recursive Make processes will stop on errors.
> >
>
> Since when? I've been doing 'gmake check-fortran' and
> 'gmake -j6 check-fortran' for more than 15 years. There
> was never an error. This broke recently.
Due to pr86417, there is a failure in the libgomp tests and make has to be used
with -k.
>From gcc-bugs-return-609482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 00:03:14 2018
Return-Path: <gcc-bugs-return-609482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58534 invoked by alias); 10 Jul 2018 00:03: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 58489 invoked by uid 55); 10 Jul 2018 00:03:08 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86415] strlen() not folded for substrings within constant arrays
Date: Tue, 10 Jul 2018 00: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: 9.0
X-Bugzilla-Keywords: missed-optimization, 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-86415-4-42pclqG5sq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86415-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86415-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00587.txt.bz2
Content-length: 517
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86415
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Tue Jul 10 00:02:36 2018
New Revision: 262528
URL: https://gcc.gnu.org/viewcvs?rev=262528&root=gcc&view=rev
Log:
PR tree-optimization/86415 - strlen() not folded for substrings within constant
arrays
gcc/testsuite/ChangeLog:
* gcc.dg/strlenopt-53.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/strlenopt-53.c
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-609484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 00:04:25 2018
Return-Path: <gcc-bugs-return-609484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59947 invoked by alias); 10 Jul 2018 00:04: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 59846 invoked by uid 48); 10 Jul 2018 00:04:20 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83819] [meta-bug] missing strlen optimizations
Date: Tue, 10 Jul 2018 00:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-83819-4-perMPoNVjz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00589.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83819
Bug 83819 depends on bug 86415, which changed state.
Bug 86415 Summary: strlen() not folded for substrings within constant arrays
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86415
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-609483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 00:04:24 2018
Return-Path: <gcc-bugs-return-609483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59928 invoked by alias); 10 Jul 2018 00:04: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 59831 invoked by uid 48); 10 Jul 2018 00:04:20 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86415] strlen() not folded for substrings within constant arrays
Date: Tue, 10 Jul 2018 00: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: 9.0
X-Bugzilla-Keywords: missed-optimization, 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-86415-4-WnrNGJurkk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86415-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86415-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00588.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86415
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Implemented in r262522.
>From gcc-bugs-return-609485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 00:24:35 2018
Return-Path: <gcc-bugs-return-609485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83048 invoked by alias); 10 Jul 2018 00:24:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82941 invoked by uid 48); 10 Jul 2018 00:24:25 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/86450] Bootstrap failure due to -Wabi
Date: Tue, 10 Jul 2018 00:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_severity
Message-ID: <bug-86450-4-xgj0yU4iNk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00590.txt.bz2
Content-length: 330
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Severity|normal |blocker
>From gcc-bugs-return-609486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 02:57:18 2018
Return-Path: <gcc-bugs-return-609486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113293 invoked by alias); 10 Jul 2018 02:57:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105251 invoked by uid 48); 10 Jul 2018 02:57:13 -0000
From: "foreese at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/86450] Bootstrap failure due to -Wabi
Date: Tue, 10 Jul 2018 02:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: foreese at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-86450-4-BfYic5oc81@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00591.txt.bz2
Content-length: 546
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
Fritz Reese <foreese at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-07-10
CC| |foreese at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Fritz Reese <foreese at gcc dot gnu.org> ---
+1
>From gcc-bugs-return-609487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 07:13:16 2018
Return-Path: <gcc-bugs-return-609487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85426 invoked by alias); 10 Jul 2018 07:13:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84917 invoked by uid 55); 10 Jul 2018 07:13:09 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86443] ICEs on #pragma omp distribute parallel for with class iterators
Date: Tue, 10 Jul 2018 07:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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-86443-4-KdhEFHekXa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86443-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86443-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00592.txt.bz2
Content-length: 2023
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86443
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jul 10 07:12:37 2018
New Revision: 262534
URL: https://gcc.gnu.org/viewcvs?rev=262534&root=gcc&view=rev
Log:
PR c++/86443
* gimplify.c (find_combined_omp_for): Add DATA argument, in addition
to finding the inner OMP_FOR/OMP_SIMD stmt find non-trivial wrappers,
BLOCKs with BLOCK_VARs, OMP_PARALLEL in between, OMP_FOR in between.
(gimplify_omp_for): For composite loops, move outer
OMP_{DISTRIBUTE,TASKLOOP,FOR,PARALLEL} right around innermost
OMP_FOR/OMP_SIMD if there are any non-trivial wrappers. For class
iterators add any needed clauses. Allow OMP_FOR_ORIG_DECLS to contain
TREE_LIST for both the original class iterator and the "last" helper
var. Gimplify OMP_FOR_PRE_BODY before the outermost composite
loop, remember has_decl_expr from outer composite loops for the
innermost OMP_SIMD in TREE_PRIVATE bit on OMP_FOR_INIT.
gcc/c-family/
* c-omp.c (c_omp_check_loop_iv_r, c_omp_check_loop_iv): Allow declv
to contain TREE_LIST for both the original class iterator and the
"last" helper var.
gcc/cp/
* semantics.c (handle_omp_for_class_iterator): Remove lastp argument,
instead of setting *lastp turn orig_declv elt into a TREE_LIST.
(finish_omp_for): Adjust handle_omp_for_class_iterator caller.
* pt.c (tsubst_omp_for_iterator): Allow OMP_FOR_ORIG_DECLS to contain
TREE_LIST for both the original class iterator and the "last" helper
var.
libgomp/
* testsuite/libgomp.c++/for-15.C: New test.
Added:
trunk/libgomp/testsuite/libgomp.c++/for-15.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-omp.c
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/pt.c
trunk/gcc/cp/semantics.c
trunk/gcc/gimplify.c
trunk/libgomp/ChangeLog
>From gcc-bugs-return-609488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 07:28:15 2018
Return-Path: <gcc-bugs-return-609488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58500 invoked by alias); 10 Jul 2018 07:28: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 58178 invoked by uid 55); 10 Jul 2018 07:28:10 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86421] OpenMP declare simd linear ref in module causes gfortran to bail out
Date: Tue, 10 Jul 2018 07:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: error-recovery, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86421-4-2e9RMvA3S3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86421-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86421-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00593.txt.bz2
Content-length: 754
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86421
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jul 10 07:27:37 2018
New Revision: 262535
URL: https://gcc.gnu.org/viewcvs?rev=262535&root=gcc&view=rev
Log:
PR fortran/86421
* module.c (omp_declare_simd_clauses): Add LINEAR with _REF, _VAL and
_UVAL suffixes.
(mio_omp_declare_simd): Save and restore ref, val and uval modifiers
on linear clauses. Initialize n->where to gfc_current_locus.
* gfortran.dg/vect/pr86421.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/vect/pr86421.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/module.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-609489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 07:38:03 2018
Return-Path: <gcc-bugs-return-609489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116966 invoked by alias); 10 Jul 2018 07:38: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 95812 invoked by uid 48); 10 Jul 2018 07:37:28 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86446] 'gmake check-fortran' broken in libgomp
Date: Tue, 10 Jul 2018 07:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.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:
Message-ID: <bug-86446-4-4wmz95euyF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86446-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00594.txt.bz2
Content-length: 1167
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
--- Comment #9 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> So, instead of using -k to pape over an error in the Makefile,
> what is wrong with the lines
>
> check-DEJAGNU: site.exp
> srcdir='$(srcdir)'; export srcdir; \
> EXPECT=$(EXPECT); export EXPECT; \
> runtest=$(RUNTEST); \
> if $(SHELL) -c "$$runtest --version" > /dev/null 2>&1; then \
> exit_status=0; l='$(DEJATOOL)'; for tool in $$l; do \
> if $$runtest $(AM_RUNTESTFLAGS) $(RUNTESTDEFAULTFLAGS) $(RUNTESTFLAGS);
> \
> then :; else exit_status=1; fi; \
> done; \
> else echo "WARNING: could not find \`runtest'" 1>&2; :;\
> fi; \
> exit $$exit_status
>
> If the commands are command out, there are no errors. So,
> what is the above suppose to do other that cause 2 ERRORs
> in the build.
But we are talking about errors in the testsuite, not in the Makefile! Every
testsuite of the GNU toolchain (GCC, GDB, Binutils, etc...) must be run the
same way with "make -k check" because, otherwise, the recursive Make processes
will stop on errors due the way the various testsuites are invoked.
>From gcc-bugs-return-609490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 07:55:39 2018
Return-Path: <gcc-bugs-return-609490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89073 invoked by alias); 10 Jul 2018 07:55:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89029 invoked by uid 48); 10 Jul 2018 07:55:34 -0000
From: "jan@swi-prolog.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/86451] New: Incorrect "is used uninitialized"
Date: Tue, 10 Jul 2018 07:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jan@swi-prolog.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-86451-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00595.txt.bz2
Content-length: 3671
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86451
Bug ID: 86451
Summary: Incorrect "is used uninitialized"
Product: gcc
Version: 8.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: jan@swi-prolog.org
Target Milestone: ---
Created attachment 44369
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44369&action=edit
C source file (short, no includes)
On quite a few versions I get this (I think) incorrect message:
t.c: In function ‘t’:
t.c:9:12: warning: ‘t’ is used uninitialized in this function [-Wuninitialized]
key ^= *p;
Compiled using
gcc -v -save-temps -c -Wall -O2 t.c
Below is the complete console output up to the warning. Note that this is a
simplified version of the real code. The 0.0 is normally
a function call.
Thanks --- Jan
Using built-in specs.
COLLECT_GCC=gcc
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-redhat-linux
Configured with: ../configure --enable-bootstrap
--enable-languages=c,c++,fortran,objc,obj-c++,ada,go,lto --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared
--enable-threads=posix --enable-checking=release --enable-multilib
--with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions
--enable-gnu-unique-object --enable-linker-build-id
--with-gcc-major-version-only --with-linker-hash-style=gnu --enable-plugin
--enable-initfini-array --with-isl --enable-libmpx
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-gnu-indirect-function --enable-cet --with-tune=generic
--with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
gcc version 8.1.1 20180502 (Red Hat 8.1.1-1) (GCC)
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-c' '-Wall' '-O2' '-mtune=generic'
'-march=x86-64'
/usr/libexec/gcc/x86_64-redhat-linux/8/cc1 -E -quiet -v t.c -mtune=generic
-march=x86-64 -Wall -O2 -fpch-preprocess -o t.i
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-redhat-linux/8/include-fixed"
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-redhat-linux/8/../../../../x86_64-redhat-linux/include"
#include "..." search starts here:
#include <...> search starts here:
/ufs/wielemak/include
/usr/lib/gcc/x86_64-redhat-linux/8/include
/usr/local/include
/usr/include
End of search list.
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-c' '-Wall' '-O2' '-mtune=generic'
'-march=x86-64'
/usr/libexec/gcc/x86_64-redhat-linux/8/cc1 -fpreprocessed t.i -quiet -dumpbase
t.c -mtune=generic -march=x86-64 -auxbase t -O2 -Wall -version -o t.s
GNU C17 (GCC) version 8.1.1 20180502 (Red Hat 8.1.1-1) (x86_64-redhat-linux)
compiled by GNU C version 8.1.1 20180502 (Red Hat 8.1.1-1), GMP version
6.1.2, MPFR version 3.1.6-p2, MPC version 1.0.2, isl version isl-0.16.1-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU C17 (GCC) version 8.1.1 20180502 (Red Hat 8.1.1-1) (x86_64-redhat-linux)
compiled by GNU C version 8.1.1 20180502 (Red Hat 8.1.1-1), GMP version
6.1.2, MPFR version 3.1.6-p2, MPC version 1.0.2, isl version isl-0.16.1-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: f4961d4fd1326e1750d95d53d7feee3c
t.c: In function ‘t’:
t.c:9:12: warning: ‘t’ is used uninitialized in this function [-Wuninitialized]
key ^= *p;
^~
>From gcc-bugs-return-609492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 08:04:57 2018
Return-Path: <gcc-bugs-return-609492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63904 invoked by alias); 10 Jul 2018 08:04:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63260 invoked by uid 55); 10 Jul 2018 08:04:51 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/86406] [8/9 Regression][UBSAN] -fcompare-debug failure with -fsanitize=undefined
Date: Tue, 10 Jul 2018 08:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed attachments.created
Message-ID: <bug-86406-4-S93AdMzkOT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86406-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86406-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00597.txt.bz2
Content-length: 1219
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86406
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-07-09
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 44364
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44364&action=edit
gcc9-pr86406.patch
Untested fix.
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jul 10 08:04:14 2018
New Revision: 262536
URL: https://gcc.gnu.org/viewcvs?rev=262536&root=gcc&view=rev
Log:
PR sanitizer/86406
* cp-gimplify.c (cp_maybe_instrument_return): Skip trailing
DEBUG_BEGIN_STMTs.
* g++.dg/ubsan/pr86406.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/ubsan/pr86406.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-gimplify.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-609491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 08:04:43 2018
Return-Path: <gcc-bugs-return-609491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62076 invoked by alias); 10 Jul 2018 08:04:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61389 invoked by uid 48); 10 Jul 2018 08:04:37 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/86451] Incorrect "is used uninitialized"
Date: Tue, 10 Jul 2018 08:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.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-86451-4-x1dVvXZXJM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86451-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86451-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00596.txt.bz2
Content-length: 261
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86451
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Try with -fno-strict-aliasing because I suspect you are violating the c/c++
aliasing rules in that you access a double as an unsigned long.
>From gcc-bugs-return-609493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 08:16:16 2018
Return-Path: <gcc-bugs-return-609493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102639 invoked by alias); 10 Jul 2018 08:16:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102431 invoked by uid 55); 10 Jul 2018 08:16:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/86406] [8/9 Regression][UBSAN] -fcompare-debug failure with -fsanitize=undefined
Date: Tue, 10 Jul 2018 08:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86406-4-sJmbAIKHE4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86406-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86406-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00598.txt.bz2
Content-length: 647
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86406
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jul 10 08:15:15 2018
New Revision: 262537
URL: https://gcc.gnu.org/viewcvs?rev=262537&root=gcc&view=rev
Log:
PR sanitizer/86406
* cp-gimplify.c (cp_maybe_instrument_return): Skip trailing
DEBUG_BEGIN_STMTs.
* g++.dg/ubsan/pr86406.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/ubsan/pr86406.C
Modified:
branches/gcc-8-branch/gcc/cp/ChangeLog
branches/gcc-8-branch/gcc/cp/cp-gimplify.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-609494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 08:32:33 2018
Return-Path: <gcc-bugs-return-609494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100145 invoked by alias); 10 Jul 2018 08:32: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 98979 invoked by uid 48); 10 Jul 2018 08:32:28 -0000
From: "jan@swi-prolog.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/86451] Incorrect "is used uninitialized"
Date: Tue, 10 Jul 2018 08: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: 8.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jan@swi-prolog.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-86451-4-z6GgXshMj1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86451-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86451-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00599.txt.bz2
Content-length: 532
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86451
Jan Wielemaker <jan@swi-prolog.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Jan Wielemaker <jan@swi-prolog.org> ---
Thanks. Aliasing ... after all those years ... Rewrote using a union and now
it is nice and silent. Marked as invalid.
>From gcc-bugs-return-609495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 08:51:35 2018
Return-Path: <gcc-bugs-return-609495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19566 invoked by alias); 10 Jul 2018 08:51: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 19528 invoked by uid 48); 10 Jul 2018 08:51:31 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/86452] New: ICE in force_decl_die, at dwarf2out.c:25922 with -g1 and -flto
Date: Tue, 10 Jul 2018 08:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-86452-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00600.txt.bz2
Content-length: 2650
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86452
Bug ID: 86452
Summary: ICE in force_decl_die, at dwarf2out.c:25922 with -g1
and -flto
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Target Milestone: ---
Probably similar to PR85176, I see it in libqtwebkit package:
lto1: internal compiler error: in force_decl_die, at dwarf2out.c:25922
0xe10a5a force_decl_die
../../gcc/dwarf2out.c:25922
0xe105e6 force_decl_die
../../gcc/dwarf2out.c:5799
0xe105e6 get_context_die
../../gcc/dwarf2out.c:25860
0x5f4582 gen_type_die_with_usage
../../gcc/dwarf2out.c:25371
0xe00693 gen_type_die
../../gcc/dwarf2out.c:25558
0xe00693 gen_decl_die
../../gcc/dwarf2out.c:26272
0xe093d6 gen_member_die
../../gcc/dwarf2out.c:24995
0xe093d6 gen_struct_or_union_type_die
../../gcc/dwarf2out.c:25092
0xe093d6 gen_tagged_type_die
../../gcc/dwarf2out.c:25302
0xe0276d gen_type_die_with_usage
../../gcc/dwarf2out.c:25503
0xe02895 gen_type_die_with_usage
../../gcc/dwarf2out.c:25461
0xe00693 gen_type_die
../../gcc/dwarf2out.c:25558
0xe00693 gen_decl_die
../../gcc/dwarf2out.c:26272
0xe093d6 gen_member_die
../../gcc/dwarf2out.c:24995
0xe093d6 gen_struct_or_union_type_die
../../gcc/dwarf2out.c:25092
0xe093d6 gen_tagged_type_die
../../gcc/dwarf2out.c:25302
0xe0276d gen_type_die_with_usage
../../gcc/dwarf2out.c:25503
0xe02895 gen_type_die_with_usage
../../gcc/dwarf2out.c:25461
0xe00693 gen_type_die
../../gcc/dwarf2out.c:25558
0xe00693 gen_decl_die
../../gcc/dwarf2out.c:26272
$ (gdb) p decl
$1 = (tree) 0x7ffff6787130
(gdb) p debug_tree(decl)
<namespace_decl 0x7ffff6787130 JSC
type <void_type 0x7ffff659ff18 void asm_written VOID
align:8 warn_if_not_align:0 symtab:0 alias-set -1 structural-equality
pointer_to_this <pointer_type 0x7ffff65a60a8>>
public VOID
/home/abuild/rpmbuild/BUILD/qtwebkit-5.212.0-alpha2/Source/JavaScriptCore/jit/JITCompilationEffort.h:29:11
align:1 warn_if_not_align:0 context <translation_unit_decl 0x7ffff6595168
/home/abuild/rpmbuild/BUILD/qtwebkit-5.212.0-alpha2/Source/JavaScriptCore/b3/testb3.cpp>>
Note it's a huge package, thus test-case reduction will be quite difficult.
Ideas what to do with that?
>From gcc-bugs-return-609497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 09:03:43 2018
Return-Path: <gcc-bugs-return-609497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121214 invoked by alias); 10 Jul 2018 09: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 121136 invoked by uid 48); 10 Jul 2018 09:03:39 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86421] OpenMP declare simd linear ref in module causes gfortran to bail out
Date: Tue, 10 Jul 2018 09: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: 8.1.0
X-Bugzilla-Keywords: error-recovery, ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86421-4-s0KI142clr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86421-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86421-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00602.txt.bz2
Content-length: 140
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86421
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 9+ so far.
>From gcc-bugs-return-609496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 09:03:28 2018
Return-Path: <gcc-bugs-return-609496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120413 invoked by alias); 10 Jul 2018 09:03:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120337 invoked by uid 48); 10 Jul 2018 09:03:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/86406] [8/9 Regression][UBSAN] -fcompare-debug failure with -fsanitize=undefined
Date: Tue, 10 Jul 2018 09:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86406-4-D3N8qGq3lT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86406-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86406-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00601.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86406
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-609498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 09:04:01 2018
Return-Path: <gcc-bugs-return-609498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121991 invoked by alias); 10 Jul 2018 09: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 121903 invoked by uid 48); 10 Jul 2018 09:03:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86443] ICEs on #pragma omp distribute parallel for with class iterators
Date: Tue, 10 Jul 2018 09: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-86443-4-z7F1WviadX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86443-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86443-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00603.txt.bz2
Content-length: 576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86443
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-07-10
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 9+ so far.
>From gcc-bugs-return-609499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 09:10:23 2018
Return-Path: <gcc-bugs-return-609499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5781 invoked by alias); 10 Jul 2018 09:10:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5701 invoked by uid 48); 10 Jul 2018 09:10:19 -0000
From: "zfigura at codeweavers dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/86407] Ignore function attributes in function type declarations?
Date: Tue, 10 Jul 2018 09: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: 5.4.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zfigura at codeweavers 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-86407-4-HomFjmJJDE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86407-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86407-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00604.txt.bz2
Content-length: 257
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86407
--- Comment #4 from Zebediah Figura <zfigura at codeweavers dot com> ---
So is there any sensible way to make this attribute a type attribute instead of
a function attribute? Or is this not desirable?
>From gcc-bugs-return-609500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 09:25:36 2018
Return-Path: <gcc-bugs-return-609500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57874 invoked by alias); 10 Jul 2018 09:25: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 57532 invoked by uid 48); 10 Jul 2018 09:24:49 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/81084] [8 Regression] powerpcspe port full of confusing configury / command-line options not related to SPE
Date: Tue, 10 Jul 2018 09: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: 8.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: andrewjenner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81084-4-DtvhqkF7uD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81084-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81084-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00605.txt.bz2
Content-length: 615
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81084
--- Comment #62 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Andrew Jenner from comment #61)
> Sorry, once again I have been totally swamped by other work. It's now
> looking like I should have some time to work on this in early July.
Ok, great. Let me know once you have an updated patch which can be tested.
FWIW, the current PowerPCSPE backend seems to have issues with the memory
management. At least we're observing gcc getting killed by the kernel's OOM
killer even on machines with 8 GiB RAM and enough swap.
>From gcc-bugs-return-609501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 09:52:51 2018
Return-Path: <gcc-bugs-return-609501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114226 invoked by alias); 10 Jul 2018 09:52: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 114168 invoked by uid 48); 10 Jul 2018 09:52:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/86445] [9 regression] Missing warning for test case gcc/testsuite/gcc.dg/pr84100.c starting with r262513
Date: Tue, 10 Jul 2018 09:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-86445-4-A3u36R5qUS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86445-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86445-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00606.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86445
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-609502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 09:55:20 2018
Return-Path: <gcc-bugs-return-609502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116221 invoked by alias); 10 Jul 2018 09:55: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 116102 invoked by uid 48); 10 Jul 2018 09:55:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi
Date: Tue, 10 Jul 2018 09:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords component
Message-ID: <bug-86450-4-d7NBW9EnxW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-07/txt/msg00607.txt.bz2
Content-length: 567
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
Component|bootstrap |libstdc++
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Can you check whether removing --enable-maintainer-mode fixes the build? I've
not had this issue but I see those Wabi warnings as non-error.
>From gcc-bugs-return-609503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 09:56:09 2018
Return-Path: <gcc-bugs-return-609503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118662 invoked by alias); 10 Jul 2018 09:56: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 118631 invoked by uid 89); 10 Jul 2018 09:56:07 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,GIT_PATCH_2,KAM_SHORT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=shark, sharks, surprisingly, 04.07.2018
X-HELO: mout.gmx.net
Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.17.21) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 10 Jul 2018 09:56:06 +0000
Received: from [192.168.0.241] ([89.78.252.225]) by mail.gmx.com (mrgmx103 [212.227.17.174]) with ESMTPSA (Nemesis) id 0LtZfc-1g25zB0Npk-010q6I; Tue, 10 Jul 2018 11:56:01 +0200
Subject: Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>, "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>, gcc-bugs@gcc.gnu.org
References: <bug-86383-4@http.gcc.gnu.org/bugzilla/> <bug-86383-4-roe7g6Jp7o@http.gcc.gnu.org/bugzilla/> <ab84a63d-cc85-0cfd-a3a6-d6deab95488c@gmx.com> <471e8255-162f-4cdd-45bc-274271cfe973@arm.com> <11bdfd68-ac9b-fd06-81b1-df39b5dae66d@gmx.com> <b58fe356-df19-ef9e-a0e2-00d4f1d7612b@arm.com>
From: Kamil Rytarowski <n54@gmx.com>
Message-ID: <9497aebc-934f-1277-c09a-87d633dfcabf@gmx.com>
Date: Tue, 10 Jul 2018 09:56:00 -0000
User-Agent: Mozilla/5.0 (X11; NetBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <b58fe356-df19-ef9e-a0e2-00d4f1d7612b@arm.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="z5L6dPaYKF09EM5f3YSW9qBu3wykzrc1P"
X-IsSubscribed: yes
X-SW-Source: 2018-07/txt/msg00608.txt.bz2
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--z5L6dPaYKF09EM5f3YSW9qBu3wykzrc1P
Content-Type: multipart/mixed; boundary="FpDCwCj3RQ2kC8UWnjChQOqp5RsEFmwtU";
protected-headers="v1"
From: Kamil Rytarowski <n54@gmx.com>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
"rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>,
gcc-bugs@gcc.gnu.org
Message-ID: <9497aebc-934f-1277-c09a-87d633dfcabf@gmx.com>
Subject: Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler
fails in selftests
References: <bug-86383-4@http.gcc.gnu.org/bugzilla/>
<bug-86383-4-roe7g6Jp7o@http.gcc.gnu.org/bugzilla/>
<ab84a63d-cc85-0cfd-a3a6-d6deab95488c@gmx.com>
<471e8255-162f-4cdd-45bc-274271cfe973@arm.com>
<11bdfd68-ac9b-fd06-81b1-df39b5dae66d@gmx.com>
<b58fe356-df19-ef9e-a0e2-00d4f1d7612b@arm.com>
In-Reply-To: <b58fe356-df19-ef9e-a0e2-00d4f1d7612b@arm.com>
--FpDCwCj3RQ2kC8UWnjChQOqp5RsEFmwtU
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Content-length: 1406
On 06.07.2018 15:26, Richard Earnshaw (lists) wrote:
> On 06/07/18 12:11, Kamil Rytarowski wrote:
>> On 06.07.2018 12:38, Richard Earnshaw (lists) wrote:
>>> On 06/07/18 11:32, Kamil Rytarowski wrote:
>>>> On 04.07.2018 20:55, rearnsha at gcc dot gnu.org wrote:
>>>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
>>>>>
>>>>> --- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
>>>>> I'm not sure how relevant the netbsd-elf port is these days. I believe they've
>>>>> now moved onto an EABI based ABI. But no GCC port of that has been
>>>>> contributed.
>>>>>
>>>>
>>>> NetBSD switched on newer ARM CPUs to EABI and keeps compat with OABI. A
>>>> user is free to build either EABI and OABI for ARMv4+ CPUs. Older pre
>>>> ARMv4 CPUs use OABI only.
>>>>
>>>
>>> GCC-9 will drop support for pre-armv4 CPUs. Such support has been
>>> marked as deprecated for about 3 years now.
>>>
>>
>> We verify these ports on real hardware.
>>
>> NetBSD/shark is prepared to be switched to Clang/LLVM as GCC is
>> obsoleting it and surprisingly LLVM soon might have support for a wider
>> range of ARM CPUs.
>>
>
> Shark's use strongARM cpus, which are ARMv4. That's not been obsoleted,
> but it is considered deprecated these days.
>
Shark doesn't use all instructions that are generated by GCC (I forgot
the CPU property name of it) and thus it has to be switched to Clang/LLVM.
--FpDCwCj3RQ2kC8UWnjChQOqp5RsEFmwtU--
--z5L6dPaYKF09EM5f3YSW9qBu3wykzrc1P
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
Content-length: 850
-----BEGIN PGP SIGNATURE-----
iQJABAEBCAAqFiEELaxVpweEzw+lMDwuS7MI6bAudmwFAltEgxMMHG41NEBnbXgu
Y29tAAoJEEuzCOmwLnZsyGkP/ilVRqmaXLKbOfFwNQUhNUBLjKX8JYswW/e+amFD
itz+e3Pl+Z8q+gGZQl7lkY84OOVP4LobvBnvR8zf+bkN48wC+fKLUTLlot6schzy
zKxtrRSEHKMOO4qHVViZTQ3d3ub4NZtaLJ8JI2lWd+Kqw7rnIxEMjwn4ROzCTPBy
OwdpVZTeIiPj7X5snVv24BWjtHK8Td8axFI7uZAZsgWjza/DiuYFV9vL9Pl+x7LF
cpp42UwzByaZoyfZYKvNZhy/EcEK1eATTUSkZGkZv6B9CcIs9Rkuh8qMHEY09g0l
YAKozJb4pJITkTG1AQbV0GnmjZi384MXVvQLMriXrNjgGcwZ7IO51OFbWKQsyDWG
uJvkmWuNtKkYLcibXgX4njXVR7yEsg62nVBkiI+m4VE0EC8Opabbfe+ep7GfvqJ6
mHi222IWM0Hfx39IAZ2hmqGf/MEF2d8W4BtYR4hFM+KdJObcR6iMNM6fwduz5iyK
nztpgsGFrQT73Ta/SXMF16PcqA446mpev5k54NX14/rpjKTFV2jz758UhxoUN3GH
B5KIbqQMG28l19DJY3iwgXdhhFXML00+aOZ6moZHtzppsoDFY8dHP0+uYLHkKjYX
R7zn7G128/bzl62BjGy73JSF+YlVwCKI6tAFs8PyJh7tUFgCFtKPLN1v/EoEm8r9
QB0s
9O9
-----END PGP SIGNATURE-----
--z5L6dPaYKF09EM5f3YSW9qBu3wykzrc1P--
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
[not found] <bug-86383-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2018-07-06 13:26 ` richard.earnshaw at arm dot com
@ 2018-07-10 17:51 ` richard.earnshaw at arm dot com
3 siblings, 0 replies; 4+ messages in thread
From: richard.earnshaw at arm dot com @ 2018-07-10 17:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
--- Comment #7 from richard.earnshaw at arm dot com ---
On 10/07/18 10:57, Kamil Rytarowski wrote:
> On 06.07.2018 15:26, Richard Earnshaw (lists) wrote:
>> On 06/07/18 12:11, Kamil Rytarowski wrote:
>>> On 06.07.2018 12:38, Richard Earnshaw (lists) wrote:
>>>> On 06/07/18 11:32, Kamil Rytarowski wrote:
>>>>> On 04.07.2018 20:55, rearnsha at gcc dot gnu.org wrote:
>>>>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
>>>>>>
>>>>>> --- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
>>>>>> I'm not sure how relevant the netbsd-elf port is these days. I believe they've
>>>>>> now moved onto an EABI based ABI. But no GCC port of that has been
>>>>>> contributed.
>>>>>>
>>>>>
>>>>> NetBSD switched on newer ARM CPUs to EABI and keeps compat with OABI. A
>>>>> user is free to build either EABI and OABI for ARMv4+ CPUs. Older pre
>>>>> ARMv4 CPUs use OABI only.
>>>>>
>>>>
>>>> GCC-9 will drop support for pre-armv4 CPUs. Such support has been
>>>> marked as deprecated for about 3 years now.
>>>>
>>>
>>> We verify these ports on real hardware.
>>>
>>> NetBSD/shark is prepared to be switched to Clang/LLVM as GCC is
>>> obsoleting it and surprisingly LLVM soon might have support for a wider
>>> range of ARM CPUs.
>>>
>>
>> Shark's use strongARM cpus, which are ARMv4. That's not been obsoleted,
>> but it is considered deprecated these days.
>>
>
> Shark doesn't use all instructions that are generated by GCC (I forgot
> the CPU property name of it) and thus it has to be switched to Clang/LLVM.
>
You're not making sense. Please be more explicit as to what you mean
and give an example. GCC can generate instructions for ARMv4 and
StrongARM (used by the shark) is an ARMv4 part.
I've run gcc generated code on shark boards for years and not seen problems.
R.
>From gcc-bugs-return-609563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 10 17:51:54 2018
Return-Path: <gcc-bugs-return-609563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127123 invoked by alias); 10 Jul 2018 17:51: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 127098 invoked by uid 89); 10 Jul 2018 17:51:52 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-7.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,GIT_PATCH_2,KAM_SHORT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy\x10072018, Hx-languages-length:2097, 10.07.2018
X-HELO: mout.gmx.net
Received: from mout.gmx.net (HELO mout.gmx.net) (212.227.17.20) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 10 Jul 2018 17:51:50 +0000
Received: from [192.168.0.241] ([89.78.252.225]) by mail.gmx.com (mrgmx101 [212.227.17.174]) with ESMTPSA (Nemesis) id 0M3NEK-1fuLC72S1Y-00qxrK; Tue, 10 Jul 2018 19:51:47 +0200
Subject: Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests
To: "richard.earnshaw at arm dot com" <gcc-bugzilla@gcc.gnu.org>, gcc-bugs@gcc.gnu.org
References: <bug-86383-4@http.gcc.gnu.org/bugzilla/> <bug-86383-4-6uOz5mv0yf@http.gcc.gnu.org/bugzilla/>
From: Kamil Rytarowski <n54@gmx.com>
Message-ID: <88abee64-0dba-a0f3-3fe6-2f5bc1b48338@gmx.com>
Date: Tue, 10 Jul 2018 17:58:00 -0000
User-Agent: Mozilla/5.0 (X11; NetBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <bug-86383-4-6uOz5mv0yf@http.gcc.gnu.org/bugzilla/>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="l3lP98rnts7fcqiEzEfmJCHEzylvYWjsS"
X-IsSubscribed: yes
X-SW-Source: 2018-07/txt/msg00668.txt.bz2
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--l3lP98rnts7fcqiEzEfmJCHEzylvYWjsS
Content-Type: multipart/mixed; boundary="KGzHY4kyuzOvQcp9dLJhgxVIRc80oxzTK";
protected-headers="v1"
From: Kamil Rytarowski <n54@gmx.com>
To: "richard.earnshaw at arm dot com" <gcc-bugzilla@gcc.gnu.org>,
gcc-bugs@gcc.gnu.org
Message-ID: <88abee64-0dba-a0f3-3fe6-2f5bc1b48338@gmx.com>
Subject: Re: [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler
fails in selftests
References: <bug-86383-4@http.gcc.gnu.org/bugzilla/>
<bug-86383-4-6uOz5mv0yf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86383-4-6uOz5mv0yf@http.gcc.gnu.org/bugzilla/>
--KGzHY4kyuzOvQcp9dLJhgxVIRc80oxzTK
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Content-length: 2045
On 10.07.2018 19:49, richard.earnshaw at arm dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
>
> --- Comment #7 from richard.earnshaw at arm dot com ---
> On 10/07/18 10:57, Kamil Rytarowski wrote:
>> On 06.07.2018 15:26, Richard Earnshaw (lists) wrote:
>>> On 06/07/18 12:11, Kamil Rytarowski wrote:
>>>> On 06.07.2018 12:38, Richard Earnshaw (lists) wrote:
>>>>> On 06/07/18 11:32, Kamil Rytarowski wrote:
>>>>>> On 04.07.2018 20:55, rearnsha at gcc dot gnu.org wrote:
>>>>>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86383
>>>>>>>
>>>>>>> --- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
>>>>>>> I'm not sure how relevant the netbsd-elf port is these days. I believe they've
>>>>>>> now moved onto an EABI based ABI. But no GCC port of that has been
>>>>>>> contributed.
>>>>>>>
>>>>>>
>>>>>> NetBSD switched on newer ARM CPUs to EABI and keeps compat with OABI. A
>>>>>> user is free to build either EABI and OABI for ARMv4+ CPUs. Older pre
>>>>>> ARMv4 CPUs use OABI only.
>>>>>>
>>>>>
>>>>> GCC-9 will drop support for pre-armv4 CPUs. Such support has been
>>>>> marked as deprecated for about 3 years now.
>>>>>
>>>>
>>>> We verify these ports on real hardware.
>>>>
>>>> NetBSD/shark is prepared to be switched to Clang/LLVM as GCC is
>>>> obsoleting it and surprisingly LLVM soon might have support for a wider
>>>> range of ARM CPUs.
>>>>
>>>
>>> Shark's use strongARM cpus, which are ARMv4. That's not been obsoleted,
>>> but it is considered deprecated these days.
>>>
>>
>> Shark doesn't use all instructions that are generated by GCC (I forgot
>> the CPU property name of it) and thus it has to be switched to Clang/LLVM.
>>
>
> You're not making sense. Please be more explicit as to what you mean
> and give an example. GCC can generate instructions for ARMv4 and
> StrongARM (used by the shark) is an ARMv4 part.
>
> I've run gcc generated code on shark boards for years and not seen problems.
>
> R.
>
I got a feedback that it's called: armv4t.
--KGzHY4kyuzOvQcp9dLJhgxVIRc80oxzTK--
--l3lP98rnts7fcqiEzEfmJCHEzylvYWjsS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
Content-length: 850
-----BEGIN PGP SIGNATURE-----
iQJABAEBCAAqFiEELaxVpweEzw+lMDwuS7MI6bAudmwFAltE8pUMHG41NEBnbXgu
Y29tAAoJEEuzCOmwLnZsv2sP/3a6F7DZfGbA5bMdYOe1MF0uNKhTp6bHvXwZfAhI
FKALWnvgMzcMVb2Me9j8w+fem6ZtDntkyZCWeEOz+ATu7r4KiNV4Zrds6MjrsBZd
7sHyIkPZVnDeBml9tUCGF9IBwvpS4YJkipBEVGa6jNf06yXV24if9KmlkchoxS7D
zckeo+odR5HTDWYUfXfbBv+yMaxHtTUtLVUkkeVh06RJ5lRmgm9z6mmoK2HKjdxP
vIJnnT4POYcv6TO9TFTIqZ1a+olClexgCJB6lVkb+EKVJVCCfjDFYlMvcc5IV4/G
inQFKzArWof6slb9S2WbNX6uBI921FgcDYWE7GOfMemmKYioGXLzs0TTIKIMt+rY
i4OEu681duoqVrvmJ3CqJzvnGly4YQ1Sl0Zrlb78Ha885Ojk3JU2vaYlNEyUDK+D
OBm6P8oIpd6LS6fmYq/5UfwdEfkJgLw+ykGcAIbkdeKOKLkU++uLTSluMqRaxapF
lPzTQ+M14f2LGt9mXDvY5S7N55e21jtDuo9tCXsCHg5jfZJeKlS3nRi9MCStv+Kp
7wqk+etRCjhsZ7PkXQQQa/d5arXj6+wKN3QwKOdZOjFJPUmYMxkVYasIQi3Hl1AE
KLyfwM7E80mRdaBaOp+Ii9cjjJMSsXWAWFK1xyefjseuxNIrZZUcrbz0OEY6veT4
bs0/
=NlK1
-----END PGP SIGNATURE-----
--l3lP98rnts7fcqiEzEfmJCHEzylvYWjsS--
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-07-10 17:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-86383-4@http.gcc.gnu.org/bugzilla/>
[not found] ` <bug-86383-4-roe7g6Jp7o@http.gcc.gnu.org/bugzilla/>
[not found] ` <ab84a63d-cc85-0cfd-a3a6-d6deab95488c@gmx.com>
2018-07-06 10:38 ` [Bug target/86383] [9 Regression] arm-netbsdelf cross compiler fails in selftests Richard Earnshaw (lists)
2018-07-06 10:39 ` richard.earnshaw at arm dot com
2018-07-06 13:26 ` richard.earnshaw at arm dot com
2018-07-10 17:51 ` richard.earnshaw at arm 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).